Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript.
Please enable Javascript for full functionality.
IPv6 Anycast Binding using Return Routability
draft-haberman-ipv6-anycast-rr-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|---|---|---|
| Authors | Brian Haberman , Erik Nordmark | |
| Last updated | 2002年10月04日 | |
| RFC stream | (None) | |
| Intended RFC status | (None) | |
| Formats | ||
| Stream | Stream state | (No stream defined) |
| Consensus boilerplate | Unknown | |
| RFC Editor Note | (None) | |
| IESG | IESG state | Expired |
| 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
Today, the use of IPv6 anycast is limited. This document proposes a mechanism by which TCP/SCTP and stateful protocols using UDP can securely discover the mapping from an anycast address to a unicast address that can be used until a failure is detected. The mechanism reuses the Mobile IPv6 Return Routability and Binding Update mechanism.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)