While I do appreciate your concern, the idea is to have as a robust system as possible regardless of what the problem is. That means (among other things), we want to bypass problems to the extent we can. As it sits, we can’t. I agree, it’s totally a configuration problem in DNS, server, or both. I have seen this before. That doesn’t mean we should tolerate getting the client stuck when a working  alternative exists. Sure, that likely means the admin won’t be aware of the problem until they actually look and wonder why no one is using IPv6 (I’ve seen that one before as well). I don’t believe we should put users through agony to force them to complain to the site admin when we can get around the problem. Hence, the patch.<br>
<br>
Andy<br>
<br>
From: Lukasz Janyst <br>
Sent: Tuesday, November 21, 2017 1:24 AM<br>
To: xrootd/xrootd <br>
Cc: Subscribed <br>
Subject: Re: [xrootd/xrootd] Should xrdcp try IPv4 connection if IPv6 connection failed? (#625)<br>
<br>
If you get an ICMP response, the failure is almost immediate and the client has enough time to retry another address.<br>
<br>
—<br>
You are receiving this because you are subscribed to this thread.<br>
Reply to this email directly, view it on GitHub, or mute the thread.<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/xrootd/xrootd/issues/625#issuecomment-346174818">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AD7Yjr3fM72wIYH7dyyuEiLD4Dzrk9Rmks5s40elgaJpZM4QevFH">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AD7YjujQi9l8fCk8uCBocvF7GDeNJyCqks5s40elgaJpZM4QevFH.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/xrootd/xrootd/issues/625#issuecomment-346174818"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<!cript type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@abh3 in #625: While I do appreciate your concern, the idea is to have as a robust system as possible regardless of what the problem is. That means (among other things), we want to bypass problems to the extent we can. As it sits, we can’t. I agree, it’s totally a configuration problem in DNS, server, or both. I have seen this before. That doesn’t mean we should tolerate getting the client stuck when a working  alternative exists. Sure, that likely means the admin won’t be aware of the problem until they actually look and wonder why no one is using IPv6 (I’ve seen that one before as well). I don’t believe we should put users through agony to force them to complain to the site admin when we can get around the problem. Hence, the patch.\n\nAndy\n\nFrom: Lukasz Janyst \nSent: Tuesday, November 21, 2017 1:24 AM\nTo: xrootd/xrootd \nCc: Subscribed \nSubject: Re: [xrootd/xrootd] Should xrdcp try IPv4 connection if IPv6 connection failed? (#625)\n\nIf you get an ICMP response, the failure is almost immediate and the client has enough time to retry another address.\n\n—\nYou are receiving this because you are subscribed to this thread.\nReply to this email directly, view it on GitHub, or mute the thread.\n"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/625#issuecomment-346174818"}}}</script><br>
<hr>
<p align="left">
Use REPLY-ALL to reply to list</p>
<p align="center">To unsubscribe from the XROOTD-DEV list, click the following link:<br>
<a href="https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1" target="_blank">https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1</a>
</p>