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

Warren Kumari warren at kumari.net
Mon Jun 15 16:33:35 UTC 2020


I would like to point at an email I sent to the IETF DNSOP list on
Mon, 18 May 2020:
https://mailarchive.ietf.org/arch/msg/dnsop/7AzjYP3XoLaPYKPjPzQzEn6k7L4/

I would note that this proposal has different properties, but as
mentioned in the above, confidentiality prevents me saying more at
this point.

W



On Mon, Jun 15, 2020 at 11:05 AM Jeff Neuman <jeff.neuman at comlaude.com> wrote:
>
> And at the end of the day, I want to note that I don’t oppose this type of proposal.  I am just perplexed why the appropriate venue is considered the IETF as opposed to ICANN.
>
>
>
> Jeff Neuman
>
> Senior Vice President
>
> Com Laude | Valideus
>
> D: +1.703.635.7514
>
> E: jeff.neuman at comlaude.com
>
>
>
> From: NCAP-Discuss <ncap-discuss-bounces at icann.org> On Behalf Of Jeff Neuman
> Sent: Monday, June 15, 2020 11:03 AM
> To: David Conrad <david.conrad at icann.org>
> Cc: ncap-discuss at icann.org
> Subject: Re: [NCAP-Discuss] Top-level Domains for Private Internets IETF draft
>
>
>
> ICANN, as far as I can tell, does not have a consensus policy that states that once ISO-3166 codes are created anyone can use it for any purpose.  If there is such a policy, I would love to see it.  ISO assigns to character codes, yes.  But ISO does not assign 2 character domains?  That is within ICANN’s purview.  Yes, we through the ICANN processes have acknowledged the right of ccTLDs to use their assigned codes as ccTLDs, but to my knowledge, ICANN has never discussed the ability to use other ISO code lists for other purposes.
>
>
>
> Why should anyone be averse to having this discussion within the ICANN community and why did Roy and Ed decide that the right venue to discuss this issue was the IETF.  To me this is policy issue and not a technical issue?
>
>
>
>
>
>
>
> Jeff Neuman
>
> Senior Vice President
>
> Com Laude | Valideus
>
> D: +1.703.635.7514
>
> E: jeff.neuman at comlaude.com
>
>
>
> From: David Conrad <david.conrad at icann.org>
> Sent: Monday, June 15, 2020 10:55 AM
> To: Jeff Neuman <jeff.neuman at comlaude.com>
> Cc: Roy Arends <roy.arends at icann.org>; ncap-discuss at icann.org
> Subject: Re: [NCAP-Discuss] Top-level Domains for Private Internets IETF draft
>
>
>
> Jeff,
>
>
>
> On Jun 15, 2020, at 7:43 AM, Jeff Neuman <jeff.neuman at comlaude.com> wrote:
>
> 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.
>
>
>
> AFAIK, 2-letter codes have been reserved since (before) RFC 1591 as assigned by ISO-3166/MA, not ICANN.  Once ISO-3166/MA assigns the 2-letter code, it can (but does not have to be) delegated in the DNS. Since ISO-3166/MA has indicated certain codes will be user defined, they can’t be assigned. Roy/Ed’s draft is suggesting the fact that ISO-3166/MA has indicated a set of 2-letter codes be "user defined" be taken as that those domains are safe for use in a user defined (i.e., private) context.
>
>
>
> This seems very different to me than brand domains, which are assigned by ICANN.
>
>
>
> Regards,
>
> -drc
>
>
>
> ________________________________
>
> 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
>
> ________________________________
> 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
> _______________________________________________
> 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.



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


More information about the NCAP-Discuss mailing list