BCP 153, RFC 8190 on Updates to the Special-Purpose IP Address Registries

rfc-editor@rfc-editor.org Tue, 27 June 2017 21:58 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 9288B12EB0A for <ietf-announce@ietfa.amsl.com>; Tue, 27 Jun 2017 14:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 C4423i6PyIew for <ietf-announce@ietfa.amsl.com>; Tue, 27 Jun 2017 14:58:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26A4D1200C5 for <ietf-announce@ietf.org>; Tue, 27 Jun 2017 14:58:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 37079B81521; Tue, 27 Jun 2017 14:57:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 153, RFC 8190 on Updates to the Special-Purpose IP Address Registries
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170627215744.37079B81521@rfc-editor.org>
Date: Tue, 27 Jun 2017 14:57:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/rpmSRkCtgU8Bn9x72SgQemNTU_U>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 27 Jun 2017 21:58:13 -0000

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

        BCP 153        
        RFC 8190

        Title:      Updates to the Special-Purpose
                    IP Address Registries 
        Author:     R. Bonica,
                    M. Cotton,
                    B. Haberman,
                    L. Vegoda
        Status:     Best Current Practice
        Stream:     IETF
        Date:       June 2017
        Mailbox:    rbonica@juniper.net, 
                    michelle.cotton@iana.org, 
                    brian@innovationslab.net,
                    leo.vegoda@icann.org
        Pages:      6
        Characters: 10158
        Updates:    RFC 6890
        See Also:   BCP 153

        I-D Tag:    draft-bchv-rfc6890bis-07.txt

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

        DOI:        10.17487/RFC8190

This memo updates the IANA IPv4 and IPv6 Special-Purpose Address
Registries to address issues raised by the definition of a "global"
prefix.  It also corrects several errors in registry entries to
ensure the integrity of the IANA Special-Purpose Address Registries.

This memo updates RFC 6890.


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