IPv6 and Neighbor Discovery over ATM
draft-ietf-ion-ipv6nd-00
| Document | Type |
Expired Internet-Draft
(ion WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Grenville Armitage | ||
| Last updated | 1996-06-13 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
This document attempts to describe and summarize some current proposals for running IPv6 over ATM, and identifies open issues that require resolution by one or more IETF working groups. The frame formats for unicast and multicast transmission of IPv6 packets in a UNI3.1 based ATM environment are specified. Some issues regarding the construction of IPv6 link-local addresses are identified, and a proposal made. A format for source and target link-layer address options in Neighbor Discovery messages is suggested, and the interactions between IPv6 Neighbor Discovery and existing IP over ATM models are outlined. This revision looks at the three models that were presented at the Los Angeles IETF in March 1996, in a joint session of the IPATM, IPNG, and ROLC working groups. No firm decisions were made at this joint meeting. Readers are encouraged to locate and review the Internet Drafts describing each model in greater detail. Further discussion of the issues raised in this document is requested, as not all questions are currently answered satisfactorily.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)