Hi Éric, About this point:
## Section 3.5
AFAIK, the ".internal" is not a special-use domain name listed by IANA (and
AFAIK not yet approved by ICANN), so, please be clear about this status
(i.e.,
squatting a domain) in the document.
It isn't registered, but ICANN did approve it:
https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-07-2024-en
Kim Davies is writing an I-D, should the IETF want to document this. He has an
-00, but plans a revision before reaching out in Dublin. If there's a need to
clarify this sooner, he could also write a blog article for ICANN in the
meantime.
Opinions differ as to whether to add .internal to the special-use domain names
registry (Verisign, for one, may support this), but IANA is working on a new
root zone database that will include reserved domains (.internal, .local,
etc.).
A note from Kim: "perhaps some useful history here is, going back many years,
there was an attempt to reserve a domain like .INTERNAL in the IETF, including
by Warren in 2017
(https://datatracker.ietf.org/doc/html/draft-wkumari-dnsop-internal-00). There
were debates about whether it was needed, whether .alt was needed. I wasn't
party to all those discussions but the basic resolution was it was a namespace
issue not a technical issue, and therefore belonged in ICANN, not in IETF. That
lead to SAC113 and ultimately ICANN reserving .INTERNAL."
Thanks,
Amanda
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
