Skip to main content

Corresponding Auto Names for IPv6 Addresses
draft-kitamura-ipv6-auto-name-03

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Hiroshi Kitamura , Shingo Ata
Last updated 2013-04-19 (Latest revision 2012-10-16)
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 document discusses notion and actual mechanisms of "Corresponding Auto Names" for IPv6 Addresses. With this mechanism, all IPv6 addresses (even if they are link-local scoped addresses) can obtain their own Names, and it will be able to use Names anywhere instead of IPv6 Addresses. IPv6 address is too long and complicated to remember, and it is very nuisance to type a literal IPv6 address manually as an argument of applications. Also, it is very difficult for human beings to tell which IPv6 address is set to which actual IPv6 node. In this sense, literal IPv6 address information can be called meaningless information for human beings. In order to solve above problems and to provide annotated meaningful information to IPv6 addresses, mechanisms called Corresponding Auto Names for IPv6 addresses is introduced. They will become human friendly information. By applying a simple naming rule to the Auto Names (e.g., use the same Auto Name Suffix for IPv6 addresses that are set to the same interface (node)), this will contribute to help people to understand which IPv6 address / Name indicates which actual IPv6 node and provide meaningful information.

Authors

Hiroshi Kitamura
Shingo Ata

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)