[pcp] RFC 7753 on Port Control Protocol (PCP) Extension for Port-Set Allocation
rfc-editor@rfc-editor.org Fri, 05 February 2016 00:13 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 6FDC21AC3A6; Thu, 4 Feb 2016 16:13:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 QQLIU6VmWurN; Thu, 4 Feb 2016 16:13:52 -0800 (PST)
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 66CC71AC3FF; Thu, 4 Feb 2016 16:13:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 57901180005; Thu, 4 Feb 2016 16:13:33 -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: <20160205001333.57901180005@rfc-editor.org>
Date: Thu, 04 Feb 2016 16:13:33 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/pcp/-AgtvRX1grfowRhlMWFNYsST9Hs>
Cc: drafts-update-ref@iana.org, pcp@ietf.org, rfc-editor@rfc-editor.org
Subject: [pcp] RFC 7753 on Port Control Protocol (PCP) Extension for Port-Set Allocation
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: Fri, 05 Feb 2016 00:13:55 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7753 Title: Port Control Protocol (PCP) Extension for Port-Set Allocation Author: Q. Sun, M. Boucadair, S. Sivakumar, C. Zhou, T. Tsou, S. Perreault Status: Standards Track Stream: IETF Date: February 2016 Mailbox: sunqiong@ctbri.com.cn, mohamed.boucadair@orange.com, ssenthil@cisco.com, cathy.zhou@huawei.com, tina.tsou@philips.com, sperreault@jive.com Pages: 19 Characters: 34550 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pcp-port-set-13.txt URL: https://www.rfc-editor.org/info/rfc7753 DOI: http://dx.doi.org/10.17487/RFC7753 In some use cases, e.g., Lightweight 4over6, the client may require not just one port, but a port set. This document defines an extension to the Port Control Protocol (PCP) that allows clients to manipulate a set of ports as a whole. This is accomplished using a new MAP option: PORT_SET. 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