STD 75, RFC 6891 on Extension Mechanisms for DNS (EDNS(0))

rfc-editor@rfc-editor.org Tue, 16 April 2013 23:41 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBFF221F9768; Tue, 16 Apr 2013 16:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.116
X-Spam-Level:
X-Spam-Status: No, score=-102.116 tagged_above=-999 required=5 tests=[AWL=-0.116, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x13yuD3sWpzI; Tue, 16 Apr 2013 16:41:04 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 41AD521F9757; Tue, 16 Apr 2013 16:41:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 62AD4B1E003; Tue, 16 Apr 2013 16:40:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: STD 75, RFC 6891 on Extension Mechanisms for DNS (EDNS(0))
From: rfc-editor@rfc-editor.org
Message-Id: <20130416234005.62AD4B1E003@rfc-editor.org>
Date: Tue, 16 Apr 2013 16:40:05 -0700
Cc: dnsext@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 23:41:04 -0000

A new Request for Comments is now available in online RFC libraries.

        STD 75        
        RFC 6891

        Title:      Extension Mechanisms for DNS (EDNS(0)) 
        Author:     J. Damas,
                    M. Graff,
                    P. Vixie
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2013
        Mailbox:    joao@bondis.org, 
                    explorer@flame.org, 
                    vixie@isc.org
        Pages:      16
        Characters: 32856
        Obsoletes:  RFC 2671, RFC 2673
        See Also:   STD 75

        I-D Tag:    draft-ietf-dnsext-rfc2671bis-edns0-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6891.txt

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 Extension Mechanisms for DNS (EDNS(0))
specification (and obsoletes RFC 2671) based on feedback from
deployment experience in several implementations.  It also obsoletes
RFC 2673 ("Binary Labels in the Domain Name System") and adds
considerations on the use of extended labels in the DNS.

This document is a product of the DNS Extensions Working Group of the IETF.

This is now an Internet Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC