[gtld-tech] An on-going IETF discussion

Edward Lewis edlewis.subscriber at cox.net
Mon Apr 7 19:23:54 UTC 2014


Hi folks,

(First time I’ve been on this list…but I think a few on the list already know me - I looked at some of the archives.  I used to work with one gTLD, now I’m doing leg work for ICANN.)

There’s a discussion in the IETF’s DNS Operations Working Group that people here might want to tune into and perhaps provide input.

The message setting this up is here:

http://www.ietf.org/mail-archive/web/dnsop/current/msg11543.html

(And BTW, check this out too: http://www.ietf.org/mail-archive/web/dnsop/current/msg11542.html)

The discussion is around an IETF *standards track* proposal to define a mechanism for how a registrant would signal to a registry that it has changed it’s NS set and/or glue records.

The reason I’m bringing this up is:

1) The IETF believes that documenting this approach is better than not documenting, because they are concerned about delegations that do not fit the “ICANN model.”
2) The IETF wants and needs to hear from real operators.
3) In my opinion, this mechanism isn’t be workable for the gTLD environment.

But, what do I know?  So, I’m asking for those who have the time to take a look at the document and make comments on it - if not to the DNSOP list, to the DNSOP chairs or listed authors/editors.

I don’t think the effort is dangerous, per se, but there are times that RFCs are pulled into RFPs for registry services.  IMHO, I wouldn’t want this to become something asked of large registries.  Perhaps I’m being paranoid, I say this to perhaps motivate people to read and comment. ;)  Deadline is April 16 for the last call in the message (11543) above.

Ed Lewis (aka edward.lewis at icann.org)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gtld-tech/attachments/20140407/ba29cc83/attachment.html>


More information about the gtld-tech mailing list