[pcp] RFC 7723 on Port Control Protocol (PCP) Anycast Addresses

rfc-editor@rfc-editor.org Sat, 23 January 2016 00:27 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 888791B2DCC; Fri, 22 Jan 2016 16:27:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 5J_5b8MerZ9l; Fri, 22 Jan 2016 16:27:10 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id DCC991B2DC4; Fri, 22 Jan 2016 16:27:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C94FD18045A; Fri, 22 Jan 2016 16:25:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160123002551.C94FD18045A@rfc-editor.org>
Date: Fri, 22 Jan 2016 16:25:51 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/pcp/YvoqGFMXS2jd4ljdUPyb-JwTrGk>
Cc: drafts-update-ref@iana.org, pcp@ietf.org, rfc-editor@rfc-editor.org
Subject: [pcp] RFC 7723 on Port Control Protocol (PCP) Anycast Addresses
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2016 00:27:12 -0000

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

        
        RFC 7723

        Title:      Port Control Protocol (PCP) Anycast 
                    Addresses 
        Author:     S. Kiesel, R. Penno
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2016 
        Mailbox:    ietf-pcp@skiesel.de, 
                    repenno@cisco.com
        Pages:      9
        Characters: 20663
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pcp-anycast-08.txt

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

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

The Port Control Protocol (PCP) anycast addresses enable PCP clients
to transmit signaling messages to their closest PCP-aware on-path
NAT, firewall, or other middlebox without having to learn the IP
address of that middlebox via some external channel.  This document
establishes one well-known IPv4 address and one well-known IPv6
address to be used as PCP anycast addresses.

This document is a product of the Port Control Protocol Working Group of the IETF.

This is now a Proposed 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  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