RFC 6887 on Port Control Protocol (PCP)
rfc-editor@rfc-editor.org Mon, 29 April 2013 22:39 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 B74D421F9B6E; Mon, 29 Apr 2013 15:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.129
X-Spam-Level:
X-Spam-Status: No, score=-102.129 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LxCC9mzBZW3N; Mon, 29 Apr 2013 15:39:25 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 57F4321F9B8D; Mon, 29 Apr 2013 15:39:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BD9D7B1E010; Mon, 29 Apr 2013 15:38:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6887 on Port Control Protocol (PCP)
From: rfc-editor@rfc-editor.org
Message-Id: <20130429223859.BD9D7B1E010@rfc-editor.org>
Date: Mon, 29 Apr 2013 15:38:59 -0700
Cc: pcp@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Mon, 29 Apr 2013 22:39:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6887
Title: Port Control Protocol (PCP)
Author: D. Wing, Ed.,
S. Cheshire, M. Boucadair,
R. Penno, P. Selkirk
Status: Standards Track
Stream: IETF
Date: April 2013
Mailbox: dwing@cisco.com,
cheshire@apple.com,
mohamed.boucadair@orange.com,
repenno@cisco.com,
pselkirk@isc.org
Pages: 88
Characters: 221314
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pcp-base-29.txt
URL: http://www.rfc-editor.org/rfc/rfc6887.txt
The Port Control Protocol allows an IPv6 or IPv4 host to control how
incoming IPv6 or IPv4 packets are translated and forwarded by a
Network Address Translator (NAT) or simple firewall, and also allows
a host to optimize its outgoing NAT keepalive messages.
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 Internet
Official Protocol Standards (STD 1) 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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://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
- RFC 6887 on Port Control Protocol (PCP) rfc-editor