[pcp] RFC 7648 on Port Control Protocol (PCP) Proxy Function

rfc-editor@rfc-editor.org Wed, 30 September 2015 21:12 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 51A971A904D; Wed, 30 Sep 2015 14:12:36 -0700 (PDT)
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 wa_0bbskQDwF; Wed, 30 Sep 2015 14:12:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 69ED31A904C; Wed, 30 Sep 2015 14:12:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C947C187F2F; Wed, 30 Sep 2015 14:11:41 -0700 (PDT)
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: <20150930211141.C947C187F2F@rfc-editor.org>
Date: Wed, 30 Sep 2015 14:11:41 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/pcp/6uwFvzLQCV3SSyFYLYYO-2QFHes>
Cc: pcp@ietf.org, rfc-editor@rfc-editor.org
Subject: [pcp] RFC 7648 on Port Control Protocol (PCP) Proxy Function
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: Wed, 30 Sep 2015 21:12:36 -0000

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

        
        RFC 7648

        Title:      Port Control Protocol (PCP) Proxy Function 
        Author:     S. Perreault,
                    M. Boucadair,
                    R. Penno,
                    D. Wing,
                    S. Cheshire
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2015
        Mailbox:    sperreault@jive.com, 
                    mohamed.boucadair@orange.com, 
                    repenno@cisco.com,
                    dwing@cisco.com, 
                    cheshire@apple.com
        Pages:      14
        Characters: 31233
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pcp-proxy-09.txt

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

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

This document specifies a new Port Control Protocol (PCP) functional
element: the PCP proxy.  The PCP proxy relays PCP requests received
from PCP clients to upstream PCP server(s).  A typical deployment
usage of this function is to help establish successful PCP
communications for PCP clients that cannot be configured with the
address of a PCP server located more than one hop away.

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