Visualizing Change; Re-Defining the Role of the IPv6 Protocol Specification
draft-terrell-visual-change-redefining-role-ipv6-01
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
|
|
---|---|---|---|
Author | Eugene Terrell | ||
Last updated | 2002-04-03 | ||
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
This paper attempts an exploration of the reasons that supports or offers a viable justification for an IP Addressing Protocol which must be Manually Configured using HEX Notation. I mean, why use HEX Numbers, and why not use an Integer?
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)