BCP 42, RFC 5395 on Domain Name System (DNS) IANA Considerations

rfc-editor@rfc-editor.org Wed, 26 November 2008 22:17 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1053C28C24A; Wed, 26 Nov 2008 14:17:47 -0800 (PST)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 124A528C240 for <ietf-announce@core3.amsl.com>; Wed, 26 Nov 2008 14:17:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.625
X-Spam-Level:
X-Spam-Status: No, score=-16.625 tagged_above=-999 required=5 tests=[AWL=0.974, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrDJn-lilTot for <ietf-announce@core3.amsl.com>; Wed, 26 Nov 2008 14:17:45 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 4E62828C24A for <ietf-announce@ietf.org>; Wed, 26 Nov 2008 14:17:45 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 1C83E1870F9; Wed, 26 Nov 2008 14:17:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 42, RFC 5395 on Domain Name System (DNS) IANA Considerations
From: rfc-editor@rfc-editor.org
Message-Id: <20081126221743.1C83E1870F9@bosco.isi.edu>
Date: Wed, 26 Nov 2008 14:17:43 -0800
Cc: namedroppers@ops.ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        BCP 42        
        RFC 5395

        Title:      Domain Name System (DNS) IANA 
                    Considerations 
        Author:     D. Eastlake 3rd
        Status:     Best Current Practice
        Date:       November 2008
        Mailbox:    d3e3e3@gmail.com
        Pages:      17
        Characters: 33725
        Obsoletes:  RFC2929
        Updates:    RFC1183, RFC3597
        See Also:   BCP0042

        I-D Tag:    draft-ietf-dnsext-2929bis-07.txt

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

Internet Assigned Number Authority (IANA) parameter assignment
considerations are specified for the allocation of Domain Name System
(DNS) resource record types, CLASSes, operation codes, error codes,
DNS protocol message header bits, and AFSDB resource record subtypes.  
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

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


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. 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
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce