NOTE: This charter is a snapshot of the 39th IETF Meeting in Munich, Bavaria, Germany. It may now be out-of-date.
Chair(s):
Randy Bush <randy@psg.com>
Internet Area Director(s):
Jeffrey Burgan <burgan@home.net>
Thomas Narten <narten@raleigh.ibm.com>
Internet Area Advisor:
Jeffrey Burgan <burgan@home.net>
Mailing Lists:
General Discussion: namedroppers@internic.net
To Subscribe: namedroppers-request@internic.net
Archive: ftp://ftp.merit.edu/internet/documents/ietf/dns
Description of Working Group:
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:
Done |
|
Consolidated review of draft-ietf-dns-ixfr-01.txt. |
Done |
|
Submit Incremental Transfer and Notify Internet-Drafts. |
Done |
|
Submit revised Incremental Transfer and Notify Internet-Drafts. |
Apr 96 |
|
Submit Dynamic Update, Incremental Transfer, and Notify Internet-Drafts to the IESG for consideration as Proposed Standards. |
Internet-Drafts:
· Classless IN-ADDR.ARPA delegation
· The Kitchen Sink Resource Record
· Negative Caching of DNS Queries (DNS NCACHE)
· Test and Example Top Level Domain Names
· Local DNS Names
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 |
RFC2136 |
PS |
Dynamic Updates in the Domain Name System (DNS UPDATE) |
RFC2181 |
PS |
Clarifications to the DNS Specification |
RFC2182 |
Selection and Operation of Secondary DNS Servers | |
Minutes of the DNSIND Working Group
I. DynUpd Testing
· Insecure Dynamic Update being coordinated by map
· Secure Dynamic Update being coordinated by Olafur
· Soliciting implementations, send mail to ogud@tis.com or map@pobox.com
· Plan to run over the open internet
· Prefer authors
· Private mailing list
· Methodology being developed. based on old mail to list
· Three insecure servers known: BIND, American Internet, Keio Univ (thinks it is complete)
· Some more clients
· TIS is working on a secure server
II. Notify Testing
· map@pobox.com is coordinating testing
· in BIND 8.1.1 4.9.6, IBM OS/2 has notify
· Andreas has a primary server
· will write up methodology
III. IXFR Testing
· Ohta-san coordinating testing, but too busy
· Implementations: IBM OS/2, MetaInfo on NT, possibly Inria too
· No methodology yet, will write up
IV. draft-ietf-dnsind-tsig-01.txt
· Making specification more strict
· TCP connection support
· Include timer values included in digest
· Error generation model is now specified
· Will come out soon after dnssec release
· Andreas has tsig-01, and will update to 02 version
· Secret exchange should be a separate draft
· We should have a WG last call
V. draft-ietf-dnsind-ncache-04.txt
· No one here to speak for it
· It needs work, spec getting closer but language problems
VI. draft-eastlake-kitchen-sink-02.txt
· Recent criticism regarding ASN.1 examples will be cleaned up
· If too successful, there may be a problem of many parts of the type then returning too many data, might resolve by bucket hashing
VII. draft-ietf-dnsind-test-tlds-01.txt
· Reserved names for testing and examples would be useful
· Some opinion that one is sufficient and English based ones might be ill advised
· Suggestion that we look at the ISO reserved list
· Suggest WG last call
VIII. draft-watson-dns-error-00.txt
· Ran out of RCODEs while doing tsig work
· Hence reserve one for indicating more error codes
· Need for more detail by some protocols, e.g. dynamic update also needs error detail
· Need a time indicator for when generator does not know what time it is
IX. Domain name compression in new RR types
· Description of the problem
· Recommends that ranges of RR numbers for compressible and uncompressible
· Dnssec's NXT RR bitmap would make this difficult
· Alternative: new style compression which is local to the RR, not for the entire message
X. draft-eastlake-local-names-00.txt
· See the draft
· Has been no significant objection
None Received