IPv6 Formal Anycast Addresses and Functional Anycast Addresses
draft-smith-6man-form-func-anycast-addresses-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-04-25 (latest revision 2018-10-22) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-smith-6man-form-func-anycast-addresses-00.txt
https://www.ietf.org/archive/id/draft-smith-6man-form-func-anycast-addresses-00.txt
Abstract
IPv6 anycast addresses are chosen from within the existing IPv6 unicast address space, with the addresses nominated as anycast addresses through configuration. An alternative scheme is to have a special class of addresses for use as anycast addresses. This memo proposes a distinct general anycast addressing class and a more specific scheme for functional anycast addresses.
Authors
Mark Smith (markzzzsmith@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)