On Tue, Feb 27, 2024 at 6:07 AM, Toerless Eckert <t...@cs.fau.de> wrote:

> Thanks, Paul
>
> My comment:
>
> https://www.icann.org/en/public-comment/proceeding/
> proposed-top-level-domain-string-for-private-use-24-01-2024/submissions/
> eckert-toerless-27-02-2024 Summary of Submission:
> I would like to see a BCP RFC on the use of the "internal" TLD, and ICANN
> should not finalize availability of the TLD unless that RFC exists.
>


Some history: This was started in the IETF, as
https://www.ietf.org/archive/id/draft-wkumari-dnsop-internal-00.txt , and
this was presented at IETF 100 —
https://datatracker.ietf.org/meeting/100/materials/slides-100-dnsop-sessa-draft-wkumari-dnsop-internal

The message from the DNSOP participants was very clear (and, IMO,
correct):  this is not IETF work, and should be discussed in ICANN[0]... and
so the draft / idea was taken to ICANN SSAC, and progressed through that.

I'll point out that there isn't really a "availability of the TLD" - it is
simply a commitment to not delegate a strong, and so people can use a part
of the namespace for their internal use, secure in the knowledge that it
won't be delegated…

W
[0]: I knew this when I wrote the draft — but, the IETF is a nicer place to
work :-)


> Cheers
> Toerless
>
> On Sun, Jan 28, 2024 at 02:42:09AM +0000, Paul Hoffman wrote:
>
> Wearing my ICANN hat:
>
> When a topic is in a public comment period, it is very appropriate and
> appreciated for community members to send comments in, as Paul Marks has.
> Having a discussion on an external forum will have no effect on the public
> comment period because the comment from Paul Marks is already logged. When
> the comment period is over, IANA will read all the comments and respond in
> a single large report.
>
> (In case you want to comment: https://www.icann.org/en/public-comment/
> proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024)
>
> --Paul Hoffman
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to