Port Control Protocol (PCP) Proxy Function
draft-ietf-pcp-proxy-02
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (pcp WG)
|
|
Last updated |
|
2013-02-12
|
|
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. Penno
Expires: August 17, 2013 D. Wing
Cisco
February 13, 2013
Port Control Protocol (PCP) Proxy Function
draft-ietf-pcp-proxy-02
Abstract
This document specifies a new PCP functional element denoted as PCP
Proxy. The PCP Proxy relays PCP requests received from PCP Clients
to upstream PCP Server(s). This function is mandatory when PCP
Clients can not be configured with the address of the PCP Server
located more than one hop.
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 August 17, 2013.
Copyright Notice
Copyright (c) 2013 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 August 17, 2013 [Page 1]
Internet-Draft PCP Proxy February 2013
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. PCP Server Discovery and Provisioning . . . . . . . . . . . . 4
4. PCP Proxy as a PCP Server . . . . . . . . . . . . . . . . . . 4
5. Control of the Firewall . . . . . . . . . . . . . . . . . . . 4
6. No NAT is Co-located with the PCP Proxy . . . . . . . . . . . 4
7. PCP Proxy Co-located with a NAT Function . . . . . . . . . . . 5
8. MAP/PEER Handling . . . . . . . . . . . . . . . . . . . . . . 6
9. Mapping Repair . . . . . . . . . . . . . . . . . . . . . . . . 7
10. Advanced Functions . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Multiple PCP Servers . . . . . . . . . . . . . . . . . . 8
10.2. Epoch Handling . . . . . . . . . . . . . . . . . . . . . 8
10.3. Request/Response Caching . . . . . . . . . . . . . . . . 9
10.4. Retransmission Handling . . . . . . . . . . . . . . . . . 9
10.5. Full State . . . . . . . . . . . . . . . . . . . . . . . 9
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
12. Security Considerations . . . . . . . . . . . . . . . . . . . 9
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
14.1. Normative References . . . . . . . . . . . . . . . . . . 10
14.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Boucadair, et al. Expires August 17, 2013 [Page 2]
Internet-Draft PCP Proxy February 2013
1. Introduction
This document defines a new PCP [I-D.ietf-pcp-base] function element,
called PCP Proxy, which is meant to facilitate the communication
between a PCP Client and upstream PCP Server(s). The PCP Proxy 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 PCP Server. The PCP Server in turn sends PCP
responses to the PCP Proxy external interface which are finally
forwarded to PCP Clients. A reference architecture is depicted in
Figure 1.
A PCP Proxy can be for instance embedded in a CP (Customer Premises)
Show full document text