[DNSOP] Indicating ipv6only and deprecation via SVCB: draft- nygren-dnsop-ipv6only-indicator-00.txt

--===============2374715830177173724==
Content-Type: multipart/alternative; boundary="00000000000053fe9b0655f8b3a3"

--00000000000053fe9b0655f8b3a3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I've published a -00 draft proposing two new SvcParams for "ipv6only" and
for "deprecated", along with some operational examples for how they might
be used together.

Abstract:

   As the DNS is the primary mechanism for translating from hostnames to
   IP addresses, it is a logical place to signal that endpoints are
   IPv6-only.  It is thus also a logical place to signal that legacy
   endpoints supporting IPv4 are being deprecated.  This specification
   introduces two SvcParams for SVCB-compatible RR types that signal
   IPv6-only endpoints (ipv6only) as well as deprecated endpoints
   (deprecated).

The "ipv6only" SvcParam touches on V6OPS and HAPPY.  I see this not as
something we desperately need now/yet but as something we will want in a
few years and thus should standardize sooner so that the implementations
are there for when we need it.

The "deprecated" SvcParam is more generally useful. I give some other
examples of how it might be used for other purposes as well (eg, for
deprecating an http/1.1-only Service Endpoint).

I'm still the only author on this, and am happy to talk to people in Vienna
if there others interested in joining as co-authors.  This idea has been
tossed around a number of times while we were authoring RFC 9460 / SVCB
(and might have been in some early drafts and I even vaguely recall talking
about some precursors to this in sunset4 and in happy).

Best, Erik


---------- Forwarded message ---------
From: <[email protected]>
Date: Mon, Jul 6, 2026 at 5:54=E2=80=AFPM
Subject: New Version Notification for
draft-nygren-dnsop-ipv6only-indicator-00.txt
To: Erik Nygren <[email protected]>


A new version of Internet-Draft draft-nygren-dnsop-ipv6only-indicator-00.tx=
t
has been successfully submitted by Erik Nygren and posted to the
IETF repository.

Name:     draft-nygren-dnsop-ipv6only-indicator
Revision: 00
Title:    Indicating IPv6-only SVCB Endpoints and IPv4 Deprecation in the
DNS
Date:     2026-07-06
Group:    Individual Submission
Pages:    11
URL:
https://www.ietf.org/archive/id/draft-nygren-dnsop-ipv6only-indicator-00.tx=
t
Status:
https://datatracker.ietf.org/doc/draft-nygren-dnsop-ipv6only-indicator/
HTML:
https://www.ietf.org/archive/id/draft-nygren-dnsop-ipv6only-indicator-00.ht=
ml
HTMLized:
https://datatracker.ietf.org/doc/html/draft-nygren-dnsop-ipv6only-indicator


Abstract:

   As the DNS is the primary mechanism for translating from hostnames to
   IP addresses, it is a logical place to signal that endpoints are
   IPv6-only.  It is thus also a logical place to signal that legacy
   endpoints supporting IPv4 are being deprecated.  This specification
   introduces two SvcParams for SVCB-compatible RR types that signal
   IPv6-only endpoints (ipv6only) as well as deprecated endpoints
   (deprecated).

   TO BE REMOVED: This document is being collaborated on in Github at:
   https://github.com/enygren/draft-nygren-dnsop-ipv6only-indicator
   (https://github.com/enygren/draft-nygren-dnsop-ipv6only-indicator).
   The most recent working version of the document, open issues, etc.
   should all be available there.  The authors (gratefully) accept pull
   requests.



The IETF Secretariat

--00000000000053fe9b0655f8b3a3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif">I&#39;ve published a -00 draft proposing two new SvcParams for &=
quot;ipv6only&quot; and for &quot;deprecated&quot;, along with some operati=
onal examples for how they might be used together.</div><div class=3D"gmail=
_default" style=3D"font-family:tahoma,sans-serif"><br></div><div class=3D"g=
mail_default" style=3D"font-family:tahoma,sans-serif"><span class=3D"gmail_=
default" style=3D"font-family:tahoma,sans-serif"></span>Abstract:<br>
<br>
=C2=A0 =C2=A0As the DNS is the primary mechanism for translating from hostn=
ames to<br>
=C2=A0 =C2=A0IP addresses, it is a logical place to signal that endpoints a=
re<br>
=C2=A0 =C2=A0IPv6-only.=C2=A0 It is thus also a logical place to signal tha=
t legacy<br>
=C2=A0 =C2=A0endpoints supporting IPv4 are being deprecated.=C2=A0 This spe=
cification<br>
=C2=A0 =C2=A0introduces two SvcParams for SVCB-compatible RR types that sig=
nal<br>
=C2=A0 =C2=A0IPv6-only endpoints (ipv6only) as well as deprecated endpoints=
<br>=C2=A0 =C2=A0(deprecated).</div><div class=3D"gmail_default" style=3D"f=
ont-family:tahoma,sans-serif"><br></div><div class=3D"gmail_default" style=
=3D"font-family:tahoma,sans-serif">The &quot;ipv6only&quot; SvcParam touche=
s on V6OPS and HAPPY.=C2=A0 I see this not as something we desperately need=
 now/yet but as something we will want in a few years and thus should stand=
ardize sooner so that the implementations are there for when we need it.</d=
iv><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><br=
></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"=
>The &quot;deprecated&quot; SvcParam is more generally useful. I give some =
other examples of how it might be used for other purposes as well (eg, for =
deprecating an http/1.1-only Service Endpoint).</div><div class=3D"gmail_de=
fault" style=3D"font-family:tahoma,sans-serif"><br></div><div class=3D"gmai=
l_default" style=3D"font-family:tahoma,sans-serif">I&#39;m still the only a=
uthor on this, and am happy to talk to people in Vienna if there others int=
erested in joining as co-authors.=C2=A0 This idea has been tossed around a =
number of times while we were authoring RFC 9460 / SVCB (and might have bee=
n in some early drafts and I even vaguely recall talking about some precurs=
ors to this in sunset4 and in happy).</div><div class=3D"gmail_default" sty=
le=3D"font-family:tahoma,sans-serif"><br></div><div class=3D"gmail_default"=
 style=3D"font-family:tahoma,sans-serif">Best, Erik</div><div class=3D"gmai=
l_default" style=3D"font-family:tahoma,sans-serif"><br></div><br><div class=
=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr=
">---------- Forwarded message ---------<br>From: <span dir=3D"auto">&lt;<a=
 href=3D"mailto:[email protected]">[email protected]</a>&gt;<=
/span><br>Date: Mon, Jul 6, 2026 at 5:54=E2=80=AFPM<br>Subject: New Version=
 Notification for draft-nygren-dnsop-ipv6only-indicator-00.txt<br>To: Erik =
Nygren &lt;<a href=3D"mailto:erik%[email protected]">[email protected]</=
a>&gt;<br></div><br><br>A new version of Internet-Draft draft-nygren-dnsop-=
ipv6only-indicator-00.txt<br>
has been successfully submitted by Erik Nygren and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0draft-nygren-dnsop-ipv6only-indicator<br>
Revision: 00<br>
Title:=C2=A0 =C2=A0 Indicating IPv6-only SVCB Endpoints and IPv4 Deprecatio=
n in the DNS<br>
Date:=C2=A0 =C2=A0 =C2=A02026-07-06<br>
Group:=C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 11<br>
URL:=C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/archive/id/draft-n=
ygren-dnsop-ipv6only-indicator-00.txt" rel=3D"noreferrer" target=3D"_blank"=
>https://www.ietf.org/archive/id/draft-nygren-dnsop-ipv6only-indicator-00.t=
xt</a><br>
Status:=C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-nygre=
n-dnsop-ipv6only-indicator/" rel=3D"noreferrer" target=3D"_blank">https://d=
atatracker.ietf.org/doc/draft-nygren-dnsop-ipv6only-indicator/</a><br>
HTML:=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.org/archive/id/draft-n=
ygren-dnsop-ipv6only-indicator-00.html" rel=3D"noreferrer" target=3D"_blank=
">https://www.ietf.org/archive/id/draft-nygren-dnsop-ipv6only-indicator-00.=
html</a><br>
HTMLized: <a href=3D"https://datatracker.ietf.org/doc/html/draft-nygren-dns=
op-ipv6only-indicator" rel=3D"noreferrer" target=3D"_blank">https://datatra=
cker.ietf.org/doc/html/draft-nygren-dnsop-ipv6only-indicator</a><br>
<br>
<br>
<span class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"></spa=
n>Abstract:<br>
<br>
=C2=A0 =C2=A0As the DNS is the primary mechanism for translating from hostn=
ames to<br>
=C2=A0 =C2=A0IP addresses, it is a logical place to signal that endpoints a=
re<br>
=C2=A0 =C2=A0IPv6-only.=C2=A0 It is thus also a logical place to signal tha=
t legacy<br>
=C2=A0 =C2=A0endpoints supporting IPv4 are being deprecated.=C2=A0 This spe=
cification<br>
=C2=A0 =C2=A0introduces two SvcParams for SVCB-compatible RR types that sig=
nal<br>
=C2=A0 =C2=A0IPv6-only endpoints (ipv6only) as well as deprecated endpoints=
<br>
=C2=A0 =C2=A0(deprecated).<br>
<br>
=C2=A0 =C2=A0TO BE REMOVED: This document is being collaborated on in Githu=
b at:<br>
=C2=A0 =C2=A0<a href=3D"https://github.com/enygren/draft-nygren-dnsop-ipv6o=
nly-indicator" rel=3D"noreferrer" target=3D"_blank">https://github.com/enyg=
ren/draft-nygren-dnsop-ipv6only-indicator</a><br>
=C2=A0 =C2=A0(<a href=3D"https://github.com/enygren/draft-nygren-dnsop-ipv6=
only-indicator" rel=3D"noreferrer" target=3D"_blank">https://github.com/eny=
gren/draft-nygren-dnsop-ipv6only-indicator</a>).<br>
=C2=A0 =C2=A0The most recent working version of the document, open issues, =
etc.<br>
=C2=A0 =C2=A0should all be available there.=C2=A0 The authors (gratefully) =
accept pull<br>
=C2=A0 =C2=A0requests.<br>
<br>
<br>
<br>
The IETF Secretariat<br>
<br>
<br>
</div></div>

--00000000000053fe9b0655f8b3a3--


--===============2374715830177173724==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KRE5TT1AgbWFp
bGluZyBsaXN0IC0tIGRuc29wQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gZG5zb3AtbGVhdmVAaWV0Zi5vcmcK

--===============2374715830177173724==--