Things To Be Considered for RFC 3484 Revision
draft-arifumi-ipv6-rfc3484-revise-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Arifumi Matsumoto , Tomohiro Fujisaki | ||
| Last updated | 2007-02-28 | ||
| 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
RFC 3484 has several known descriptions to be modified mainly because of the deprecation of IPv6 site-local unicast address and the coming of ULA. This document covers these essential points to be modified and also possible useful changes to be included in the revision of RFC 3484.
Authors
Arifumi Matsumoto
Tomohiro Fujisaki
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)