Port Control Protocol (PCP) Proxy Function
draft-ietf-pcp-proxy-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (pcp WG)
|
|
Last updated |
|
2012-04-21
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
PCP Working Group M. Boucadair
Internet-Draft France Telecom
Intended status: Standards Track R. Dupont
Expires: September 30, 2012 Internet Systems Consortium
R. Penno
Juniper Networks
D. Wing
Cisco
March 29, 2012
Port Control Protocol (PCP) Proxy Function
draft-ietf-pcp-proxy-00
Abstract
This document specifies the behavior of a PCP Proxy element, for
instance embedded in Customer Premise routers.
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 September 30, 2012.
Copyright Notice
Copyright (c) 2012 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
Boucadair, et al. Expires September 30, 2012 [Page 1]
Internet-Draft PCP Proxy March 2012
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. PCP Server Discovery and Provisioning . . . . . . . . . . . . 3
3. PCP Proxy as a PCP Server . . . . . . . . . . . . . . . . . . 4
4. Control of the Firewall . . . . . . . . . . . . . . . . . . . 4
5. Embedded NAT in the CP Router . . . . . . . . . . . . . . . . 4
6. Simple PCP Proxy . . . . . . . . . . . . . . . . . . . . . . . 6
7. Advanced Functions . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Multiple PCP Servers . . . . . . . . . . . . . . . . . . . 7
7.2. Epoch Handling . . . . . . . . . . . . . . . . . . . . . . 8
7.3. Request/Response Caching . . . . . . . . . . . . . . . . . 8
7.4. Retransmission Handling . . . . . . . . . . . . . . . . . 9
7.5. Full State . . . . . . . . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
10.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Boucadair, et al. Expires September 30, 2012 [Page 2]
Internet-Draft PCP Proxy March 2012
1. Introduction
PCP [I-D.ietf-pcp-base] discusses the implementation of NAT control
features that rely upon Carrier Grade NAT (CGN) devices such as DS-
Lite AFTR [RFC6333].
The Customer Premise router, the B4 element in DS-Lite, is in charge
to enforce some security controls on PCP requests so implements a PCP
Proxy function: it acts as a PCP server receiving PCP requests on
internal interfaces, and as a PCP client forwarding accepted PCP
requests on an external interface to a CGN PCP server. The CGN PCP
server in turn send replies (PCP responses) to the PCP Proxy external
interface which are finally forwarded to PCP clients.
The PCP Proxy can be simple, i.e., implement as transparent/minimal
processing as possible, or it can be smart, i.e., handle multiple CGN
PCP servers, cache requests/responses, etc. A smart Proxy can be
associated with UPnP IGD [I-D.ietf-pcp-upnp-igd-interworking] or/and
Show full document text