PCP Anycast Address
draft-ietf-pcp-anycast-01
The information below is for an old version of the document | |||||
---|---|---|---|---|---|
Document | Type | Expired Internet-Draft (pcp WG) | |||
Last updated | 2014-08-18 (latest revision 2014-02-14) | ||||
Replaces | draft-kiesel-pcp-ip-based-srv-disc, draft-cheshire-pcp-anycast | ||||
Stream | IETF | ||||
Intended RFC status | (None) | ||||
Formats |
Expired & archived
pdf
htmlized
bibtex
|
||||
Reviews | |||||
Additional URLs |
|
||||
Stream | WG state | WG Document | |||
Document shepherd | None | ||||
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-anycast-01.txt
Abstract
The Port Control Protocol (PCP) Anycast Address enables PCP clients to transmit signaling 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. This document establishes one well-known IPv4 address and one well-known IPv6 address to be used as PCP Anycast Address.
Authors
Sebastian Kiesel
(ietf-pcp@skiesel.de)
Reinaldo Penno
(repenno@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.)