Port Control Protocol (PCP) Proxy Function
draft-ietf-pcp-proxy-04
| Document | Type | This is an older version of an Internet-Draft that was ultimately published as an RFC. | |
|---|---|---|---|
| Authors | Mohamed Boucadair , Reinaldo Penno , Dan Wing | ||
| Last updated | 2014-01-29 (Latest revision 2013-07-28) | ||
| Replaces | draft-bpw-pcp-proxy | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
|
||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Mohamed Boucadair
Reinaldo Penno
Dan Wing
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)