Print

Print

Just to amplify @bbockelm point (that this is unlikely to be a problem in HTTP-TPC), by mentioning that adding a control mechanism (through FTS) would mean selectively disabling IPv6 on a transfer-by-transfer basis.

I suppose this could be needed, but I'm struggling to see when it would be needed (or appropriate, even).

Therefore, I suggest we should wait to see some concrete use-cases for this functionality, before updating the protocol.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: <xrootd/xrootd/issues/1472/1266570629@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1472#issuecomment-1266570629", "url": "https://github.com/xrootd/xrootd/issues/1472#issuecomment-1266570629", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1