Port Control Protocol (PCP) Proxy Function
draft-ietf-pcp-proxy-05
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (pcp WG) | |
| Last updated | 2014-08-08 (latest revision 2014-02-04) | ||
| Replaces | draft-bpw-pcp-proxy | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-pcp-proxy-05.txt
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
Simon Perreault
(simon.perreault@viagenie.ca)
Mohamed Boucadair
(mohamed.boucadair@orange.com)
Reinaldo Penno
(repenno@cisco.com)
Dan Wing
(dwing@cisco.com)
Stuart Cheshire
(cheshire@apple.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)