RFC 7488 on Port Control Protocol (PCP) Server Selection

rfc-editor@rfc-editor.org Wed, 11 March 2015 00:50 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 5DFF21A9145; Tue, 10 Mar 2015 17:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 yMho4jxQnsjw; Tue, 10 Mar 2015 17:50:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1CB1A9139; Tue, 10 Mar 2015 17:49:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6602B180463; Tue, 10 Mar 2015 17:49:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7488 on Port Control Protocol (PCP) Server Selection
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150311004912.6602B180463@rfc-editor.org>
Date: Tue, 10 Mar 2015 17:49:12 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/va5ENzdoBhP7aIN9PrFO1g1KzOQ>
Cc: pcp@ietf.org, 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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Mar 2015 00:50:02 -0000

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

        
        RFC 7488

        Title:      Port Control Protocol (PCP) Server 
                    Selection 
        Author:     M. Boucadair, R. Penno,
                    D. Wing, P. Patil,
                    T. Reddy
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2015
        Mailbox:    mohamed.boucadair@orange.com, 
                    repenno@cisco.com, 
                    dwing@cisco.com, 
                    praspati@cisco.com, 
                    tireddy@cisco.com
        Pages:      12
        Characters: 22577
        Updates:    RFC 6887

        I-D Tag:    draft-ietf-pcp-server-selection-10.txt

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

This document specifies the behavior to be followed by a Port Control
Protocol (PCP) client to contact its PCP server(s) when one or
several PCP server IP addresses are configured.

This document updates RFC 6887.

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