Port Control Protocol (PCP) Proxy Function
draft-ietf-pcp-proxy-06
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (pcp WG)
|
|
Last updated |
|
2015-02-05
(latest revision 2014-12-17)
|
|
Replaces |
|
draft-bpw-pcp-proxy
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
In WG Last Call
|
|
Document shepherd |
|
Dave Thaler
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
"Dave Thaler" <dthaler@microsoft.com>
|
Network Working Group S. Perreault, Ed.
Internet-Draft Viagenie
Intended status: Standards Track M. Boucadair
Expires: June 20, 2015 France Telecom
R. Penno
D. Wing
Cisco
S. Cheshire
Apple
December 17, 2014
Port Control Protocol (PCP) Proxy Function
draft-ietf-pcp-proxy-06
Abstract
This document specifies a new PCP functional element denoted as a 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 can not be configured with the address of a PCP server
located more than one hop away.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 20, 2015.
Copyright Notice
Copyright (c) 2014 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
Perreault, et al. Expires June 20, 2015 [Page 1]
Internet-Draft PCP Proxy December 2014
(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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Use Case: the NAT Cascade . . . . . . . . . . . . . . . . 3
1.2. Use Case: the PCP Relay . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Operation of the PCP Proxy . . . . . . . . . . . . . . . . . 5
3.1. Optimized Hairpin Routing . . . . . . . . . . . . . . . . 7
3.2. Termination of Recursion . . . . . . . . . . . . . . . . 8
3.3. Source Address for PCP Requests Sent Upstream . . . . . . 8
3.4. Unknown OpCodes and Options . . . . . . . . . . . . . . . 9
3.4.1. No NAT is Co-located with the PCP Proxy . . . . . . . 9
3.4.2. PCP Proxy Co-located with a NAT Function . . . . . . 9
3.5. Mapping Repair . . . . . . . . . . . . . . . . . . . . . 9
3.6. Multiple PCP Servers . . . . . . . . . . . . . . . . . . 10
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
This document defines a new PCP [RFC6887] functional element: the PCP
Proxy. As shown in Figure 1, the PCP proxy is logically equivalent
to a PCP client back-to-back with a PCP server. The "glue" between
the two is what is specified in this document. Other than that
"glue", the server and the client behave exactly like their regular
counterparts.
.................
+------+ : +------+------+ : +------+
|Client|-------:-|Server|Client|-:----|Server|
+------+ : +------+------+ : +------+
: Proxy :
.................
Figure 1: Reference Architecture
Perreault, et al. Expires June 20, 2015 [Page 2]
Show full document text