[NCAP-Discuss] Top-level Domains for Private Internets IETF draft

Mon Jun 15 14:43:07 UTC 2020

Matthias,

Regardless of who is the intended beneficiary of the private name spaces, at the end of the day this will cause the ICANN world to "reserve" these labels from being delegated in the authoritative root.  So, I see this no differently than I see a brand TLD for example.  Brand TLDs do not have a standard registration model and in fact some of the brand TLDs may be using their TLDs for their own private intranets.

The whole point of the new gTLD process was to create new and innovative models like this one.  I understand that most of the policies are geared towards traditional uses, thatdoesnt mean that we should be thinking outside of the box to encourage new uses of the DNS.  My main point is that we need to make it easier for new and innovative uses of TLDs as opposed to encouraging entities that want to do innovative things to (a) use the IETF processes or (b) stand up an alternate root (like the Blockchain domains).  The longer it takes us to get the new TLD program off the ground, the more we are encouraging others to work around ICANN and not within it.

We need to do better than constantly getting wrapped up in policy discussions while the world works around us.  But that is my humble opinion as one that has been spending the last 25 years trying to make the multi-stakeholder model work.  Call me an optimist 😉

Jeff Neuman
Senior Vice President
Com Laude | Valideus
D: +1.703.635.7514
E: jeff.neuman at comlaude.com

-----Original Message-----
From: Matthias Pfeifer | dotBERLIN GmbH & Co. KG <pfeifer at dot.berlin>
Sent: Monday, June 15, 2020 10:16 AM
To: Jeff Neuman <jeff.neuman at comlaude.com>; Roy Arends <roy.arends at icann.org>; Dmitry Belyavsky <beldmit at gmail.com>
Cc: ncap-discuss at icann.org
Subject: AW: [NCAP-Discuss] Top-level Domains for Private Internets IETF draft

Hi,

my understanding is that the content belongs to parts on the "non-dns" it industry (hardware vendors, publishers, software developers..) rather than the DNS community .

This should/could be clarified (also in the draft) before putting it to any icann processes or agendas. IMHO.

Best, Matthias

> Roy,
>
> Why have you chosen to take this through the IETF track as opposed to
> taking it through the ICANN process.  Seems to me that this is all
> about policy and very little about technical information in this Informational RFC.
> These are the very things that should be dealt with in the ICANN
> policy processes.  The notion of creating namespaces for private use
> is purely policy and therefore dealing with this through the IETF, in
> my opinion, is not how we should be thinking about this.  Sure, it may
> be easier to get this type of thing through the IETF, but we should be
> more focused on improving the multi- stakeholder model to allow these
> types of discussions rather than trying to circumvent it.
>
> Has this been submitted to the GNSO?
>
> Jeff Neuman
> Senior Vice President
> Com Laude | Valideus
> D: +1.703.635.7514
> E: jeff.neuman at comlaude.com
>
> -----Original Message-----
> From: NCAP-Discuss <ncap-discuss-bounces at icann.org> On Behalf Of Roy
> Arends
> Sent: Friday, June 12, 2020 12:16 PM
> To: Dmitry Belyavsky <beldmit at gmail.com>
> Cc: ncap-discuss at icann.org
> Subject: Re: [NCAP-Discuss] Top-level Domains for Private Internets
> IETF draft
>
> I want to make a disclaimer here for complete transparency:
>
> I am the editor of that document. This draft is my individual
> submission and does not present an opinion, endorsement or anything
> like that from ICANN, ICANN affiliate (such as PTI) or the ICANN community.
>
> Warmly,
>
> Roy Arends
> ICANN staff member in the Office of the CTO.
>
>
> > On 12 Jun 2020, at 16:50, Dmitry Belyavsky <beldmit at gmail.com> wrote:
> >
> > Hello,
> >
> > I want to draw everybody's attention to the IETF draft "Top-level
> > Domains for Private Internets"
> > (https://datatracker.ietf.org/doc/draft-arends-private-use-tld/)
> >
> > I think it should be taken to account in the group's upcoming analysis.
> >
> > --
> > SY, Dmitry Belyavsky
> > _______________________________________________
> > NCAP-Discuss mailing list
> > NCAP-Discuss at icann.org
> > https://mm.icann.org/mailman/listinfo/ncap-discuss
> >
> > _______________________________________________
> > By submitting your personal data, you consent to the processing of
> > your
> personal data for purposes of subscribing to this mailing list
> accordance with the ICANN Privacy Policy
> (https://www.icann.org/privacy/policy) and the website Terms of
> Service (https://www.icann.org/privacy/tos). You can visit the Mailman
> link above to change your membership status or configuration,
> including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
>
> ________________________________
>  The contents of this email and any attachments are confidential to
> the intended recipient. They may not be disclosed, used by or copied
> in any way by anyone other than the intended recipient. If you have
> received this message in error, please return it to the sender
> (deleting the body of the email and attachments in your reply) and
> immediately and permanently delete it. Please note that the Com Laude
> Group does not accept any responsibility for viruses and it is your
> responsibility to scan or otherwise check this email and any
> attachments. The Com Laude Group does not accept liability for
> statements which are clearly the sender's own and not made on behalf
> of the group or one of its member entities. The Com Laude Group
> includes Nom-IQ Limited t/a Com Laude, a company registered in England
> and Wales with company number
> 5047655 and registered office at 28-30 Little Russell Street, London,
> WC1A 2HN England; Valideus Limited, a company registered in England
> and Wales with company number
>   06181291 and registered office at 28-30 Little Russell Street,
> London, WC1A 2HN England; Demys Limited, a company registered in
> Scotland with company number SC197176, having its registered office at
> 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum,
> Inc. dba Com Laude USA and Valideus USA, headquartered at 1751
> Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan)
> Corporation, a company registered in Japan having its registered
> office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan.
> For further information see www.comlaude.com<https://comlaude.com>
> _______________________________________________
> NCAP-Discuss mailing list
> NCAP-Discuss at icann.org
> https://mm.icann.org/mailman/listinfo/ncap-discuss
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of
> your personal data for purposes of subscribing to this mailing list
> accordance with the ICANN Privacy Policy
> (https://www.icann.org/privacy/policy) and the website Terms of
> Service (https://www.icann.org/privacy/tos). You can visit the Mailman
> link above to change your membership status or configuration,
> including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
________________________________
 The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see www.comlaude.com<https://comlaude.com>