[pcp] RFC 7652 on Port Control Protocol (PCP) Authentication Mechanism
rfc-editor@rfc-editor.org Wed, 30 September 2015 23:41 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 B431B1ACD43; Wed, 30 Sep 2015 16:41:04 -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 vrZJTWV7WkXd; Wed, 30 Sep 2015 16:41:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4D87B1ACD2D; Wed, 30 Sep 2015 16:40:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5ED11188D0A; Wed, 30 Sep 2015 16:40:03 -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: <20150930234004.5ED11188D0A@rfc-editor.org>
Date: Wed, 30 Sep 2015 16:40:03 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/pcp/Uohjjwysoqvhfk9CW1VOIjvWK9k>
Cc: drafts-update-ref@iana.org, pcp@ietf.org, rfc-editor@rfc-editor.org
Subject: [pcp] RFC 7652 on Port Control Protocol (PCP) Authentication Mechanism
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 23:41:04 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7652 Title: Port Control Protocol (PCP) Authentication Mechanism Author: M. Cullen, S. Hartman, D. Zhang, T. Reddy Status: Standards Track Stream: IETF Date: September 2015 Mailbox: margaret@painless-security.com, hartmans@painless-security.com, zhang_dacheng@hotmail.com, tireddy@cisco.com Pages: 34 Characters: 78237 Updates: RFC 6887 I-D Tag: draft-ietf-pcp-authentication-14.txt URL: https://www.rfc-editor.org/info/rfc7652 DOI: http://dx.doi.org/10.17487/RFC7652 An IPv4 or IPv6 host can use the Port Control Protocol (PCP) to flexibly manage the IP address-mapping and port-mapping information on Network Address Translators (NATs) or firewalls to facilitate communication with remote hosts. However, the uncontrolled generation or deletion of IP address mappings on such network devices may cause security risks and should be avoided. In some cases, the client may need to prove that it is authorized to modify, create, or delete PCP mappings. This document describes an in-band authentication mechanism for PCP that can be used in those cases. The Extensible Authentication Protocol (EAP) is used to perform authentication between PCP devices. 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