| | | | | | | | |
|
|
|
You're here: Home |
Starting on last Sunday and continuing until Friday is the 68th meeting of the IETF in Prague, Czech Republic. For those interesting in trying to find a way to listen or watch remotely, here is a link to try http://videolab.uoregon.edu/events/ietf/. The IETF is a global meeting of Internet engineers to work on tasks that build, enhance, and determine operational practices for anything involving the IP protocol.
So far there have been two DNS related sessions, apologies for not sending this earlier. One is the ENUM WG and the other is DNSOP. The latter covers operational but not protocol work in DNS. Coming up on Wednesday is the DNSEXT WG session, which is chartered to cover protocol design work.
The ENUM WG is in a state of potentially ending it's mission. There is some work to add the kinds of data in an ENUM database but the most important work is the development of instructions for extending ENUM after the WG ends.
Perhaps I should explain a little about IETF WGs. A WG in the IETF is not a permanent committee, a WG is supposed to be organized to accomplish an engineering mission. Once the engineering is done the WG disbands and the operation of the protocol moves elsewhere. In most cases, this means an IANA run registry is created, with instructions to IANA being a major deliverable.
The DNSOP WG is an ongoing effort to create documents covering the problems with running a DNS service properly. There is on document I would like to call this group's attention to:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-reverse-mapping-considerations-02.txtUpcoming is the DNSEXT WG meeting. This group was formed in the late 90's to cover extensions like DNSSEC. As much as DNSSEC is still waiting to see deployment, the engineering work over it is pretty much finished. A sign that this WG may be ready to conclude is that one of the active documents is designed to give instructions to IANA on how to assign new type codes.
At the meeting an anticipated discussion is whether the DNS protocol is "complete." There are features of DNS that are desired, but these features may not be possible with the current DNS design.
My one action item for the group is - if you have any protocol concerns you would like voiced here this week, feel free to let me know and I will see what I can do. This is the week to speak up about DNS engineering and get feedback from a world-wide body of experts.
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-571-434-5468 NeuStar Sarcasm doesn't scale.
