On 1/15/2024 2:49 PM, Paul Wouters wrote:
I think this might have been part of a list used to "reserve" the names
of (transport) protocols, so that constructs like _25._quic.example.com
could be constructed where the _name denotes the protocol and not the
name of something. I think dccp got added to this list because it is
references as a "transport protocol" in RFC4340 and the author wanted
to make sure transport protocol names were not accidentally squatted
by newly invented things with a clashing name/acronym.
That's a rather more thoughtful and pleasing explanation. I think it is
also correct.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
mast:@dcrocker@mastodon.social
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
