NOTE: This charter is a snapshot of that in effect at the time of the 38th IETF Meeting in Memphis, Tennessee. It may now be out-of-date.
Randy Bush <randy@psg.com>
Frank Kastenholz <kasten@ftp.com>
Jeffrey Burgan <jburgan@baynetworks.com>
General Discussion:namedroppers@internic.net
To Subscribe: namedroppers-request@internic.net
Archive: ftp://ftp.merit.edu/internet/documents/ietf/dns
The DNS Incremental Transfer, Notification, and Dynamic Update Working Group is concerned with three areas of future DNS protocol development:
1. Incremental Zone Transfer - As the sizes of some zone files have grown quite large, it is believed that a protocol addition to allow the transfer of only the changed subset of a zone will reduce net traffic and the load on critical servers. 2. Change Notification - There can be large time intervals during which at least one secondary has data that is inconsistent with the primary. The proposed ``notify'' mechanism (where the primary sends a message to known secondaries) facilitates fast convergence of servers vis-a-vis consistency of data in the zones. 3. Dynamic Update - The need to frequently update small portions of a large zone and to have those updates propagate is perceived.Goals and Milestones:
· Dynamic Updates in the Domain Name System (DNS UPDATE)
· Selection and Operation of Secondary DNS Servers
· Clarifications to the DNS Specification
· Secret Key Transaction Signatures for DNS (TSIG)
· Negative Caching of DNS Queries (DNS NCACHE)
Request For Comments:
|
RFC |
Status |
Title |
|
RFC1995 |
PS |
Incremental Zone Transfer in DNS |
|
RFC1996 |
PS |
A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY) |
|
RFC1982 |
PS |
Serial Number Arithmetic |
Minutes of the DNS IXFR, Notification, and Dynamic Update (DNSIND) Working Group
Reported by: Alan Barret
draft-ietf-dnsind-classless-inaddr-{00,01}.txt
The -00 draft passed Working Group last call some time ago, and was passed on to the IESG. Comments received from the IESG and other parties have been incorporated by the authors into a -01 draft which was posted too late for ID for this meeting.
No major changes. People should be aware that nameservers which delegate zones in this fashion should be authoritative for both the parent and child zones, in order to reduce problems in old software with CNAME records crossing zone boundaries.
draft-ietf-dnsind-2ndry-04.txt
This draft relies on the Clarify Draft and will progress with it.
draft-ietf-dnsind-clarify-{07,08}.txt
The -07 draft is available, and the -08 draft is nearly ready. There have been no recent requests for additions to this document.
The major change in the upcoming -08 draft is clarification of what should appear in the MNAME field of the SOA record: the name of the master host.
Working Group last call will be issued when 08 is published.
draft-ietf-dnsind-ncache-03.txt
This draft is not yet ready. See recent comments on the mailing list.
The following documents are on the standards track, and the group intends to move them to draft standard.
RFC 1995 - IXFR (currently Proposed Standard) RFC 1996 - Notify (currently Proposed Standard) RFC 1982 - Serial Number Arithmetic (currently Proposed Standard) draft-ietf-dnsind-dynDNS-11.txt - Dynamic Update (about to be PS)
In order for the documents to be advanced to Draft Standard, there must be at least two interoperable, independently developed implementations. BIND and an implementation for OS/2 are available (except that there is no IXFR implementation for BIND).
In the case of Serial Number Arithmetic, Randy Bush will attempt to locate or perform a formal proof of correctness and proposes to use that in lieu of one of the implementations. The IESG and POISSON have not encouraged this.
Stuart Kwan from Microsoft may be interested in sponsoring an interoperability testing bake-off.
Robert Elz has an implementation of Sequence Space Arithmetic that works with an arbitrary number of bits. This could be tested against the 32-bit implementations in various nameservers.
It was decided that different people will organize and report on the testing of different components.
Masataka Ohta will organize interoperability testing of IXFR; Michael Patton and Olafur Gudmundsson will organize interoperability testing of Dynamic Update and Secure Dynamic Update; Michael Patton will organize interoperability testing of Notify; Robert Elz will organize interoperability testing of Serial Number Arithmetic.
It was noted that there's no strict need to perform interoperability testing of classless in-addr delegation, because that draft is intended to become a BCP, not a Draft Standard.
III. Status of DNSSEC Drafts that Effect DNSIND Drafts
The Secure Dynamic Update Draft (draft-ietf-dnssec-update-04.txt) has been approved by the IESG and should go to Proposed Standard. There will be at least a six-month delay before a Proposed Standard can move to Draft Standard. It is expected that the Non-secure Dynamic Update Draft (draft-ietf-dnsind-dynDNS-11.txt) will be able to move forward on the standards track together.
IV. Future of the DNSIND Working Group
I, N and D (IXFR, Notify, and Dynamic update) are essentially completed. There are some items, such as TSIG (draft-ietf-dnsind-tsig-01.txt) and the Kitchen Sink RR (draft-eastlake-kitchen-sink-01.txt) that can conveniently be handled by DNSIND. There are other issues, such as negative cacheing and future evolution of the DNS, that might be better handled elsewhere. It is not clear what the most appropriate course would be.
The chair indicated that he was waiting for guidance from the IESG on what should be done with the TSIG draft. If guidance is not forthcoming within a week or so, a Working Group last call will be issued. The authors may make a quick update first.