PCP Anycast Address
draft-cheshire-pcp-anycast-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Stuart Cheshire | ||
| Last updated | 2014-01-15 (Latest revision 2013-07-14) | ||
| Replaced by | draft-ietf-pcp-anycast | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pcp-anycast | |
| 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
The Port Control Protocol Anycast Address enables PCP clients to transmit messages to their closest on-path NAT, Firewall, or other middlebox, without having to learn the IP address of that middlebox via some external channel.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)