Port Control Protocol (PCP) Authentication Mechanism
RFC 7652
| Document | Type |
RFC - Proposed Standard
(September 2015; Errata)
Updates RFC 6887
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Replaces | draft-wasserman-pcp-authentication | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Dave Thaler | ||
| Shepherd write-up | Show (last changed 2015-05-29) | ||
| IESG | IESG state | RFC 7652 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Brian Haberman | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) M. Cullen
Request for Comments: 7652 S. Hartman
Updates: 6887 Painless Security
Category: Standards Track D. Zhang
ISSN: 2070-1721
T. Reddy
Cisco
September 2015
Port Control Protocol (PCP) Authentication Mechanism
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7652.
Cullen, et al. Standards Track [Page 1]
RFC 7652 PCP Authentication September 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Cullen, et al. Standards Track [Page 2]
RFC 7652 PCP Authentication September 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Protocol Details . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Session Initiation . . . . . . . . . . . . . . . . . . . 6
3.1.1. Authentication Triggered by the Client . . . . . . . 6
3.1.2. Authentication Triggered by the Server . . . . . . . 7
3.1.3. Authentication Using EAP . . . . . . . . . . . . . . 8
3.2. Recovery from Lost PA Session . . . . . . . . . . . . . . 10
3.3. Session Termination . . . . . . . . . . . . . . . . . . . 11
3.4. Session Re-authentication . . . . . . . . . . . . . . . . 11
4. PA Security Association . . . . . . . . . . . . . . . . . . . 12
5. Packet Format . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1. Packet Format of PCP Auth Messages . . . . . . . . . . . 14
5.2. Opcode-Specific Information of AUTHENTICATION Opcode . . 16
5.3. NONCE Option . . . . . . . . . . . . . . . . . . . . . . 16
5.4. AUTHENTICATION_TAG Option . . . . . . . . . . . . . . . . 17
5.5. PA_AUTHENTICATION_TAG Option . . . . . . . . . . . . . . 18
5.6. EAP_PAYLOAD Option . . . . . . . . . . . . . . . . . . . 19
5.7. PRF Option . . . . . . . . . . . . . . . . . . . . . . . 19
5.8. MAC_ALGORITHM Option . . . . . . . . . . . . . . . . . . 20
5.9. SESSION_LIFETIME Option . . . . . . . . . . . . . . . . . 20
5.10. RECEIVED_PAK Option . . . . . . . . . . . . . . . . . . . 21
5.11. ID_INDICATOR Option . . . . . . . . . . . . . . . . . . . 21
6. Processing Rules . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Authentication Data Generation . . . . . . . . . . . . . 22
6.2. Authentication Data Validation . . . . . . . . . . . . . 23
6.3. Retransmission Policies for PA Messages . . . . . . . . . 24
6.4. Sequence Numbers for PCP Auth Messages . . . . . . . . . 25
Show full document text