The Use of End System Designators in IPv6
draft-thomas-ipv6-esd-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Matt Thomas | ||
| Last updated | 1997-03-27 | ||
| 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
There is a proposal to split unicast IPv6 addresses into two 8 byte quantities. The first 8 bytes will contain routing information which is used to reach a subnetwork. The last 8 bytes will contain a identifier of a node on that subnet. This identifier is globally unique and is called an End System Designator (ESD). The ESD (not the entire 16 byte address) will be used to accept packets and identify connections, among other things.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)