[sig-dns] DNS at IETF68

  • To: sig-dns at apnic dot net
  • Subject: [sig-dns] DNS at IETF68
  • From: Edward Lewis <Ed.Lewis at neustar dot biz>
  • Date: Sun, 25 Mar 2007 18:35:20 -0400
  • Cc:
  • List-archive: <http://www.apnic.net/mailing-lists/sig-dns>
  • List-help: <mailto:sig-dns-request@lists.apnic.net?subject=help>
  • List-id: APNIC SIG on DNS issues <sig-dns.lists.apnic.net>
  • List-post: <mailto:sig-dns@lists.apnic.net>
  • List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-dns>, <mailto:sig-dns-request@lists.apnic.net?subject=subscribe>
  • List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-dns>, <mailto:sig-dns-request@lists.apnic.net?subject=unsubscribe>
    • The 68th meeting of the IETF was held last week in Prague, Czech Republic.
      Meeting materials can be found here, likely in the next few weeks this page will change as presentations are updated, notes assembled and so on.
      There were three sessions involving DNS. The three are DNSOP, DNSEXT, and ENUM.
      DNSOP WG is chartered to discuss and develop operating practices for the DNS. This group was formed in the spring of 2000 and has met just about every IETF meeting since. Originally it was chartered to develop root server requirements and DNSSEC, now it covers most DNS operations.
      DNSEXT WG is chartered with making a few changes to the DNS protocol, the most recent is DNSSEC. This group differs from DNSOP by focusing on the protocol and not the use of software that speaks the protocol. The group was chartered in 1999 after merging two previous DNS protocol groups.
      ENUM WG is chartered with developing the Telephone Number Mapping. I don't know much of the history of this group, I only recently became active in it.
      Of the three groups, DNSOP is one with the most future life in it. There is a lot of work being covered in the group, one topic that would be of interest is the document on reverse map zones.
      These are the documents presented/discussed at last week's meeting:
         3.1) draft-ietf-dnsop-reflectors-are-evil-03.txt
         3.2) draft-ietf-dnsop-default-local-zones-01.txt
         3.3) draft-ietf-dnsop-respsize-07.txt
         3.4) draft-ietf-dnsop-reverse-mapping-considerations-02.txt
         3.5) draft-ietf-dnsop-as112-ops-00.txt
         5.1) draft-regnauld-ns-communication-00.txt
         5.2) draft-larson-dnsop-trust-anchor-01.txt
         5.3) draft-koch-dnsop-resolver-priming-00.txt
         6.1) SRV underscore registry
         6.2) TTL considerations
      The numbering is from the agenda. To keep this summary from being too long, I will leave it as an exercise for the reader to decide what topics are interesting enough to generate a discussion on this list (or the DNSOP list). IN particular though, 3.4 is certainly on-topic for this list.
      DNSEXT is a working group that is lively to become dormant, effectively shutting down. This is a reflection that there is no new protocol work being done on DNS - at least not significant new work. There are some issues in the final stages, such as the NSEC3 modification to DNSSEC. There are plenty of issues in DNS operations and plenty of implementation details to work out, but no new protocol issues.
      This isn't to say that there are no new features desired of DNS, but at this time there are no practical extension proposals. Shutting down this group is significant, it shows that DNS has become a mature protocol. You can take that to be a sign of "it's good" or a sign of "we've given up working on it." It depends on your point of view.
      ENUM is also thinking of becoming dormant or shutting down. ENUM is a subset of DNS use - it is a protocol in its own right in that it specifies how to convert a phone number into information about that number. There are new proposals for information to be stored in an ENUM (DNS) directory but the process of proposing has been reduced to submitting forms and getting expert review.
      There is one issue that is hot in this group and that is the issue of public and infrastructure ENUM. Public ENUM uses the e164.arpa DNS tree, which is administered by RIPE NCC for the ITU. Other "widespread" ENUM uses are proposed, but that discussion may take place outside of the ENUM WG as it doesn't change the protocol.
      If you have any questions about the summary , feel free to voice them.
      Edward Lewis                                                +1-571-434-5468
      Sarcasm doesn't scale.