Internet Engineering Task Force

DNS Extensions (dnsext)

Last Modified: 2010-01-11

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

Chair(s):

Internet Area Director(s):

Internet Area Advisor:

Ralph Droms <rdroms@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:

The DNS has a large installed base and repertoire of protocol
specifications. The DNSEXT WG group will actively advance DNS
protocol-related RFCs on the standards track while thoroughly
reviewing further proposed extensions. The scope of the DNSEXT WG is
confined to the DNS protocol, particularly changes that affect DNS
protocols "on the wire" or the internal processing of DNS data. DNS
operations are out of scope for the WG.

The WG will limit itself to review of proposals for new extensions
and clarification to the DNS protocol, including DNSSEC. Adoption of
new work targeted for standards track will require changes to this
charter.

The working group can nevertheless undertake work in following
subjects without a charter change:
DNSSEC and TSIG/TKEY algorithm maintenance
Hardening DNS protocol and providing guidance to implementors
Advancing existing Proposed Standard RFCs to Draft/Full Standard
Obsoleting RFCs.
Maintaining a Wiki containing a guide to DNS protocol RFC's.
Improving DNS zone synchronization mechanisms
Examining transport protocols, possibly adding new ones.

Before formal adoption of any such items at least 5 working group
participants must publicly state that the item is within charter and is
worthwhile item for further study.

The DNSEXT WG will conduct the specified RFC5395 review of RR
templates as they are posted, and EDNS0 Option templates if EDNS0-bis
updates registration requirements.

The WG will review DNS protocol related work which may originate
elsewhere in the IETF, including AD-sponsored submissions or drafts
in other working group. The WG does not intend to hold face to face
meetings, though may do so if deemed necessary for resolution of a
specific issue at hand.

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
Done		Finalize Zone Enumeration Requirements
Done		RFC2538 (CERT RR) to Draft Standard
Done		Forgery Resilience advanced to IESG
Done		GOST DNSKEY and DS support advanced to IESG
Jan 2010		DNSKEY Registry fixes and allocation procedure advanced to IESG
Jan 2010		AXFR Clarify to IESG
Feb 2010		DNS existing transport protocol recommendations/clarifications to IESG
Feb 2010		RFC3597-bis Unknown RR advanced to IESG for PS
Feb 2010		TSIG/MD5 Obsoleting to IESG.
Feb 2010		DNSSEC Errata document to IESG
Mar 2010		EDNS0-bis update advanced to IESG

Internet-Drafts:

DNS Zone Transfer Protocol (AXFR) (63668 bytes)
Clarifications and Implementation Notes for DNSSECbis (26051 bytes)
Update to DNAME Redirection in the DNS (36141 bytes)
Extension Mechanisms for DNS (EDNS0) (21704 bytes)
Cryptographic Algorithm Identifier Allocation for DNSSEC (10933 bytes)
Use of GOST signature algorithms in DNSKEY and RRSIG Resource Records for DNSSEC (17314 bytes)
Handling of Unknown DNS Resource Record (RR) Types (13292 bytes)
DNS Transport over TCP (15249 bytes)
DNS Security (DNSSEC) DNSKEY IANA Registry Algorithm Status Addition (12654 bytes)

Request For Comments: