DNS Extensions (dnsext)

Last Modified: 2007-12-26

Additional information is available at tools.ietf.org/wg/dnsext

Chair(s):

Olafur Gudmundsson <ogud@ogud.com>

Internet Area Director(s):

Jari Arkko <jari.arkko@piuha.net>

Mark Townsley <townsley@cisco.com>

Internet Area Advisor:

Mark Townsley <townsley@cisco.com>

Mailing Lists:

General Discussion: namedroppers@ops.ietf.org
To Subscribe: namedroppers-request@ops.ietf.org
Archive: http://ops.ietf.org/lists/namedroppers/

Description of Working Group:

DNS was originally specified in RFC's 1034 and 1035, with subsequent
updates. Within the scope of this WG are DNS protocol issues,
including the specification of message formats, message handling, and
data formats used for DNS client-server and server-server
communication.

This WG is focused on advancing the zone transfer, update, notify
and DNSSECbis documents to Draft standard.

The WG works on solutions for DNSSEC deployment issues that may
require protocol modifications. Two of these issues are identified
and are worked on under the umbrella of this WG. 1] (a) method(s) to
prevent the possibility of trivial zone enumeration and 2] a method
for automated rollover of trust-anchors configured in validating
resolvers.

Issues surrounding the operation of DNS, recommendations concerning
the configuration of DNS servers, and other issues with the use of
the protocol are out of scope for this Working Group. These issues
are considered in other venues, such as the DNS Operations Working
Group.

The DNSEXT Working Group sometimes uses an additional mailing list
for discussion of DNS Security related issues. This list is open to
all

Discussion: dnssec@cafax.se
To Subscribe: dnssec-request@cafax.se
Archive: http://www.cafax.se/dnssec/ and
ftp://ftp.cafax.se/pub/archives/dnssec.list

The 2535bis document set was edited by a team. This team was
chartered with making editorial changes only, with all substantiative
changes discussed on the WG list. The archive of this editors-only
mailing list is available at:

http://www.east.isi.edu/projects/DNSSEC

Specific work items are:

o Advance the DNSSECbis document set through the standards
process.

o Clarification of RFC1034/1035 relating to DNSEXT ongoing work.
+ Clarification of wildcard processing rules.

o After the work items above have been completed the working
group will continue on reviewing the following existing
proposed standard and examine if there is a possibility to
progress them on the standards track.

+ RFC1995 (IXFR) to Draft standard.
+ RFC1996 (Notify) to Draft standard.
+ RFC2136bis (Dynamic Update) to Draft Standard.
+ RFC2181 (Clarify) to IESG for advancement to Draft Standard.
+ RFC2308 (Neg Caching) to Draft Standard.
+ RFC2671 (EDNS0) to Draft Standard.
+ RFC2672 (DNAME) to Draft Standard, or revision.
+ RFC2845 (TSIG)to Draft standard.
+ RFC2930 (TKEY) to Draft standard.
+ RFC3007 (Secure Update) to Draft standard.
+ RFC3645 GSS/TSIG to Draft Standard
+ RFC3??? AXFR clarify to Draft Standard.

o Identify (a) method(s) to prevent the possibility of trivial
zone enumeration.

o Define a method for automated rollover of trust-anchors
configured in validating resolvers.

o Foster the development of Link Local Multicast Name
Resolution (LLMNR) standard. The WG has taken up this work
since LLMNR it is very similar to the DNS protocol. LLMNR is
targeted as proposed standard.

The lifetime of the group is set by the work items above but while
these are ongoing the working group has additional tasks:

o Reviewing and providing recommendations about the
specification, by other working groups, of RR types that do
not
require any special processing and that do not require any
special naming conventions.

Goals and Milestones:

Done		Forward NSEC rdata to IESG for Proposed Standard
Done		Forward RFC2535-bis to IESG for proposed standard
Done		Forward Case Insensitive to IESG for Proposed Standard
Done		Forward LLMNR to IESG for Proposed Standard
Done		Update boilerplate text on OPT-IN
Done		Forward Wildcard clarification to IESG for proposed standard
Feb 2007		Submit KEY algorithm documents RFC253[69]bis and RFC3110 to IESG for proposed standard
Done		Finalize Zone Enumeration Requirements
Jun 2007		Start of process of reviewing the following RFCs and to move them to Draft Standard status
Jul 2007		RFC2930 (TKEY) to Draft standard
Jul 2007		RFC2181 (Clarify) to Draft Standard
Jul 2007		RFC2136 (Dynamic Update) to Draft Standard
Jul 2007		RFC2308 (Neg Caching) to Draft Standard
Jul 2007		RFC3007 (Secure Update) to Draft Standard
Jul 2007		RFC2782 (SRV RR) to Draft Standard
Jul 2007		RFC2671 (EDNS0) to Draft Standard
Jul 2007		RFC1995 (IXFR) to Draft standard
Jul 2007		RFC2672 (DNAME) to Draft Standard or revision
Jul 2007		RFC1996 (Notify) to Draft Standard
Jul 2007		Submit to IESG RFC2845 (TSIG)to Draft standard
Jul 2007		RFC1982 (Serial Number Arithmetic)
Jul 2007		RFC2538 (CERT RR) to Draft Standard
Jul 2007		FRC2539 (DH Key RR) to Draft Standard
Jul 2007		RFC3226 (Message Size) to Draft Standard
Feb 2008		RFC2536bis and RFC2539bis advanced to IESG.
Mar 2008		DNAMEbis advanced to IESG
Jun 2008		Forgery Resilience advanced to IESG

Internet-Drafts:

DNS Zone Transfer Protocol (AXFR) (41768 bytes)
DNSSEC Hashed Authenticated Denial of Existence (113336 bytes)
Clarifications and Implementation Notes for DNSSECbis (22932 bytes)
Domain Name System (DNS) IANA Considerations (35303 bytes)
Use of SHA-2 algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC (16621 bytes)
Update to DNAME Redirection in the DNS (35075 bytes)
Measures for making DNS more resilient against forged answers (973 bytes)
Revised extension mechanisms for DNS (EDNS0) (17954 bytes)
The Modern DNS Implementation Guide (52420 bytes)

Request For Comments:

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to working group directory.

Return to IETF home page.