Extension Mechanisms for DNS (EDNS(0))
draft-ietf-dnsext-rfc2671bis-edns0-09

The information below is for an old version of the document
Document Type Active Internet-Draft (dnsext WG)
Last updated 2012-11-15 (latest revision 2012-08-13)
Replaces draft-graff-dnsext-edns0bis
Stream IETF
Intended RFC status Internet Standard
Formats plain text pdf html
Stream WG state Waiting for WG Chair Go-Ahead
Revised I-D Needed - Issue raised by WGLC
Consensus Unknown
Document shepherd None
IESG IESG state Approved-announcement to be sent::Point Raised - writeup needed
Telechat date
Responsible AD Ralph Droms
IESG note Olafur Gudmundsson (ogud at ogud.com) is the document shepherd.
Send notices to dnsext-chairs@tools.ietf.org, draft-ietf-dnsext-rfc2671bis-edns0@tools.ietf.org
DNSEXT Working Group                                            J. Damas
Internet-Draft                                                  M. Graff
Obsoletes: 2671, 2673                                           P. Vixie
(if approved)                                Internet Systems Consortium
Intended status: Standards Track                         August 13, 2012
Expires: February 14, 2013

                 Extension Mechanisms for DNS (EDNS(0))
                 draft-ietf-dnsext-rfc2671bis-edns0-09

Abstract

   The Domain Name System's wire protocol includes a number of fixed
   fields whose range has been or soon will be exhausted and does not
   allow requestors to advertise their capabilities to responders.  This
   document describes backward compatible mechanisms for allowing the
   protocol to grow.

   This document updates the EDNS(0) specification (and obsoletes RFC
   2671) based on feedback from deployment experience in several
   implementations.  It also closes the IANA registry for extended
   labels created as part of RFC 2671 and obsoletes RFC 2673 ("Binary
   Labels in the Domain Name System") which depends on the existence of
   extended labels.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 14, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Damas, et al.           Expires February 14, 2013               [Page 1]
Internet-Draft             EDNS(0) Extensions                August 2012

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Damas, et al.           Expires February 14, 2013               [Page 2]
Internet-Draft             EDNS(0) Extensions                August 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  EDNS Support Requirement . . . . . . . . . . . . . . . . . . .  5
   4.  DNS Message changes  . . . . . . . . . . . . . . . . . . . . .  5
     4.1.  Message Header . . . . . . . . . . . . . . . . . . . . . .  5
     4.2.  Label Types  . . . . . . . . . . . . . . . . . . . . . . .  5
     4.3.  UDP Message Size . . . . . . . . . . . . . . . . . . . . .  5
   5.  Extended Label Types . . . . . . . . . . . . . . . . . . . . .  6
   6.  The OPT pseudo-RR  . . . . . . . . . . . . . . . . . . . . . .  6
     6.1.  OPT Record Definition  . . . . . . . . . . . . . . . . . .  6
       6.1.1.  Basic elements . . . . . . . . . . . . . . . . . . . .  6
       6.1.2.  Wire Format  . . . . . . . . . . . . . . . . . . . . .  7
       6.1.3.  OPT Record TTL Field Use . . . . . . . . . . . . . . .  8
       6.1.4.  Flags  . . . . . . . . . . . . . . . . . . . . . . . .  9
     6.2.  Behaviour  . . . . . . . . . . . . . . . . . . . . . . . .  9
       6.2.1.  Cache behaviour  . . . . . . . . . . . . . . . . . . .  9
Show full document text