BCP 163, RFC 7793 on Adding 100.64.0.0/10 Prefixes to the IPv4 Locally-Served DNS Zones Registry

rfc-editor@rfc-editor.org Fri, 13 May 2016 02:35 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 6DEFE12B077; Thu, 12 May 2016 19:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 3Lzc_fnDJqmH; Thu, 12 May 2016 19:35:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDCB312B053; Thu, 12 May 2016 19:35:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 16A66180004; Thu, 12 May 2016 19:34:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 163, RFC 7793 on Adding 100.64.0.0/10 Prefixes to the IPv4 Locally-Served DNS Zones Registry
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160513023429.16A66180004@rfc-editor.org>
Date: Thu, 12 May 2016 19:34:29 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/73Pglt2KfW3NHSUJr6nsptvTOxw>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: <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: Fri, 13 May 2016 02:35:31 -0000

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

        BCP 163        
        RFC 7793

        Title:      Adding 100.64.0.0/10 Prefixes to the 
                    IPv4 Locally-Served DNS Zones Registry 
        Author:     M. Andrews
        Status:     Best Current Practice
        Stream:     IETF
        Date:       May 2016
        Mailbox:    marka@isc.org
        Pages:      6
        Characters: 7713
        See Also:   BCP0163

        I-D Tag:    draft-ietf-dnsop-rfc6598-rfc6303-05.txt

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

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

RFC 6598 specifies that "Reverse DNS queries for Shared Address Space
addresses [100.64.0.0/10] MUST NOT be forwarded to the global DNS
infrastructure."

This document formally directs IANA to add the associated zones to
the "IPv4 Locally-Served DNS Zones Registry" to prevent such queries
from accidentally leaking to the global DNS infrastructure.

This document is a product of the Domain Name System Operations 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
  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/retrieve/bulk

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