BCP 40, RFC 7720 on DNS Root Name Service Protocol and Deployment Requirements

rfc-editor@rfc-editor.org Thu, 10 December 2015 00:23 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 217041A1EF2 for <ietf-announce@ietfa.amsl.com>; Wed, 9 Dec 2015 16:23:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zrEbg6mDRQNq for <ietf-announce@ietfa.amsl.com>; Wed, 9 Dec 2015 16:23:29 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id B17EA1A1F02 for <ietf-announce@ietf.org>; Wed, 9 Dec 2015 16:23:14 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E6ACA180471; Wed, 9 Dec 2015 16:21:07 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 40, RFC 7720 on DNS Root Name Service Protocol and Deployment Requirements
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151210002107.E6ACA180471@rfc-editor.org>
Date: Wed, 09 Dec 2015 16:21:07 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/Yrw5W9r5xWA0i8z-Jxz3udeQyUk>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 00:23:31 -0000

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

        BCP 40        
        RFC 7720

        Title:      DNS Root Name Service Protocol 
                    and Deployment Requirements 
        Author:     M. Blanchet,
                    L-J. Liman
        Status:     Best Current Practice
        Stream:     IAB
        Date:       December 2015
        Mailbox:    Marc.Blanchet@viagenie.ca, 
                    liman@netnod.se
        Pages:      6
        Characters: 10552
        Obsoletes:  RFC 2870
        See Also:   BCP 40

        I-D Tag:    draft-iab-2870bis-03.txt

        URL:        https://www.rfc-editor.org/info/rfc7720

        DOI:        http://dx.doi.org/10.17487/RFC7720

The DNS root name service is a critical part of the Internet
architecture.  The protocol and deployment requirements for the DNS
root name service are defined in this document.  Operational
requirements are out of scope.

This document is a product of the Internet Architecture Board.


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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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