[Witarea] draft-martin-retry-over-ipv6-02 requesting review/ad ditional comments
Franck Martin <[email protected]> Tue, 30 Jun 2026 13:46:42 -0500 (CDT)
| Newsgroups | gmane.ietf.tsv-area,gmane.ietf.v6ops |
|---|---|
| Message-ID | <124038112.24831839.1782845202866.JavaMail.zimbra@zmcc-3-mailbox-1.zmailcloud.com> |
--===============3557145604274876936== Content-Type: multipart/alternative; boundary="Apple-Mail=_A3E5F61C-16A8-48CF-A2C7-160C6FD66406" --Apple-Mail=_A3E5F61C-16A8-48CF-A2C7-160C6FD66406 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi all, Some suggested that a 4xx code could be better, so I checked the pros = and cons and added language in this draft on the various aspects of 566 = vs 466. Also checked if there is any current behavior for common = software for retrying after any HTTP error code. Spolier alert: 566 still seems better.it is not an error on the client = part, It is the server that refuses to honor the connection. This new draft has this added language: https://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/ To be noted, I implemented this draft on my site: = https://pacific.ipv6forum.com/ so that on the 6th of every month, IPv4 = is not served. I had some implementation nits that prevented me from = getting good logs. I hope this time I will have better logs, therefore = better reports to share with folks. In a couple of days, the site will show a banner announcing the IPv4 = outage. At the moment, I have not convinced a WG to formally =E2=80=9Chost=E2=80=9D= the discussion. I won=E2=80=99t be able to attend IETF Vienna as to = gather more support, but appreciate if some folks could be a proxy. Franck Martin https://www.peachymango.org <https://www.peachymango.org/>=20= --Apple-Mail=_A3E5F61C-16A8-48CF-A2C7-160C6FD66406 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" = content=3D"text/html; charset=3Dutf-8"></head><body = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;">Hi all,<div><br></div><div>Some = suggested that a 4xx code could be better, so I checked the pros and = cons and added language in this draft on the various aspects of 566 vs = 466. Also checked if there is any current behavior for common software = for retrying after any HTTP error code.</div><div><br></div><div>Spolier = alert: 566 still seems better.it is not an error on the client part, It = is the server that refuses to honor the = connection.</div><div><br></div><div>This new draft has this added = language:</div><div><br></div><div><a = href=3D"https://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/">ht= tps://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/</a></div><div= ><br></div><div>To be noted, I implemented this draft on my = site: <a = href=3D"https://pacific.ipv6forum.com/">https://pacific.ipv6forum.com/</a>= so that on the 6th of every month, IPv4 is not served. I had some = implementation nits that prevented me from getting good logs. I hope = this time I will have better logs, therefore better reports to share = with folks.</div><div><br></div><div>In a couple of days, the site will = show a banner announcing the IPv4 outage.</div><div><br></div><div>At = the moment, I have not convinced a WG to formally =E2=80=9Chost=E2=80=9D = the discussion. I won=E2=80=99t be able to attend IETF Vienna as to = gather more support, but appreciate if some folks could be a = proxy.</div><div><br></div><div>Franck Martin</div><div><a = href=3D"https://www.peachymango.org">https://www.peachymango.org</a> = </div></body></html>= --Apple-Mail=_A3E5F61C-16A8-48CF-A2C7-160C6FD66406-- --===============3557145604274876936== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0gCldpdGFyZWEgbWFpbGluZyBsaXN0IC0tIHdpdGFyZWFAaWV0Zi5vcmcKVG8gdW5zdWJzY3Jp YmUgc2VuZCBhbiBlbWFpbCB0byB3aXRhcmVhLWxlYXZlQGlldGYub3JnCg== --===============3557145604274876936==--