Internet Draft H. Kitamura <draft-kitamura-ipv6-auto-name-00.txt> NEC Corporation S. Ata Osaka City University Expires April 2012 October 24, 2011 Corresponding Auto Names for IPv6 Addresses draft-kitamura-ipv6-auto-name-00.txt> BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on September 2011. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. H. Kitamura Expires April 2012 [Page 1]

Internet Draft Corresponding Auto Names for IPv6 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 thing 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 make the information meaningful, mechanisms called Corresponding Auto Names for IPv6 addresses is introduced. They will become gentle information for human beings. By applying a simple naming rule to the Auto Names (e.g., use the same name-prefix 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. 1 . Introduction H. Kitamura Expires April 2012 [Page 2]

Internet Draft Corresponding Auto Names for IPv6 So, there are strong desires to use Name information (that is gentle for human beings) instead of literal IPv6 Address information and to use meaningful information that can easily show which IPv6 address / name indicates which actual IPv6 node. The Corresponding Auto Names for IPv6 Addresses is introduced to solve above problems and to satisfy the above desires. 2 . Goals (What can be achieved) 2.1 Assumed typical IPv6 communication environment: H. Kitamura Expires April 2012 [Page 3]

Internet Draft Corresponding Auto Names for IPv6 2.2 Auto Names examples 2.3 Auto Name Prefix for Grouped Addresses H. Kitamura Expires April 2012 [Page 4]

Internet Draft Corresponding Auto Names for IPv6 2.4 Contribution in Regular Resolving (Name -> Address) 2.5 Contribution in Reverse Resolving (Address -> Name) H. Kitamura Expires April 2012 [Page 5]

Internet Draft Corresponding Auto Names for IPv6 'ndp -a' (on Node A) shows neighbor cache status as followed: Neighbor Linklayer Addr. Netif Expire S fe80::20d:5eff:feb8:807b%fxp0 0:0d:5e:b8:80:7b fxp0 permanent R fd01:2345:6789::20d:5eff:feb8:807b 0:0d:5e:b8:80:7b fxp0 permanent R fd01:2345:6789::1234 0:0d:5e:b8:80:7b fxp0 permanent R 2001:DB8::20d:5eff:feb8:807b 0:0d:5e:b8:80:7b fxp0 permanent R 2001:DB8::1234 0:0d:5e:b8:80:7b fxp0 permanent R fe80::221:85ff:fea7:82ff%fxp0 0:21:85:a7:82:ff fxp0 23h50m51s S fe80::20c:76ff:fed9:14e3%fxp0 0:0c:76:d9:14:e3 fxp0 23h51m56s S fd01:2345:6789::20c:76ff:fed9:14e3 0:0c:76:d9:14:e3 fxp0 23h52m50s S fd01:2345:6789::5678 0:0c:76:d9:14:e3 fxp0 23h53m51s S 2001:DB8::20c:76ff:fed9:14e3 0:0c:76:d9:14:e3 fxp0 23h54m53s S 2001:DB8::5678 0:0c:76:d9:14:e3 fxp0 23h55m54s S People almost can not tell which shown literal IPv6 address indicates which IPv6 node. In this sense, shown information is meaningless and useless. By introducing the Corresponding Auto Names, above complicated information is converted into simple and meaningful information and shown as followed. 'netstat -a' (on Node A) shows connection status as followed: Local Address Foreign Address (state) n7bz-l1.8722 ne3z-l1.23 ESTABLISH n7bz-u1.16258 ne3z-u1..23 TIME_WAIT 'ndp -a' (on Node A) shows neighbor cache status as followed: Neighbor Linklayer Addr. Netif Expire S n7bz-l1%fxp0 0:0d:5e:b8:80:7b fxp0 permanent R n7bz-u1 0:0d:5e:b8:80:7b fxp0 permanent R n7bz-u2 0:0d:5e:b8:80:7b fxp0 permanent R n7bz-g1 0:0d:5e:b8:80:7b fxp0 permanent R n7bz-g2 0:0d:5e:b8:80:7b fxp0 permanent R nffz-l1%fxp0 0:21:85:a7:82:ff fxp0 23h50m51s S n3ez-l1%fxp0 0:0c:76:d9:14:e3 fxp0 23h51m56s S n3ez-l1 0:0c:76:d9:14:e3 fxp0 23h52m50s S n3ez-l2 0:0c:76:d9:14:e3 fxp0 23h53m51s S n3ez-g1 0:0c:76:d9:14:e3 fxp0 23h54m53s S n3ez-g2 0:0c:76:d9:14:e3 fxp0 23h55m54s S H. Kitamura Expires April 2012 [Page 6]

Internet Draft Corresponding Auto Names for IPv6 Other examples where the Auto Name technique can contributes: In log files of a server application, accesses from clients are recoded into them in literal IPv6 address format. It is almost impossible to read and understand the log files effectively without this Auto Name technique. Also, in packet dumping applications, address information is shown in literal IPv6 address format. This Auto Name technique can significantly help for human beings to analyze and understand dumped packets. Shown communication related status information in Auto Name format is simple and easy enough for human beings to understand. As shown above, troublesome IPv6 literal Address information can be converted into meaningful information by using the Corresponding Auto Names technique, and we can achieve our goals. 3 Deployed Notions and Functions that are used in Auto Names 3.1 . Stateless Name 3.2 Scoped Name H. Kitamura Expires April 2012 [Page 7]

Internet Draft Corresponding Auto Names for IPv6 Scope of Auto Name for IPv6 address is the same to the scope of its IPv6 address. For example, scope of the Auto Name for the link- local IPv6 address is link-local. They are only effective within the link-local scope. 3.3 Target IPv6 Addresses 4 . Design of Auto Names 4.1 Conceptual Design on Naming Rules H. Kitamura Expires April 2012 [Page 8]

Internet Draft Corresponding Auto Names for IPv6 4.1.1 Value: 4.1.2 Value: 4.1.3 Value: H. Kitamura Expires April 2012 [Page 9]

Internet Draft Corresponding Auto Names for IPv6 4.2 IPv6 Address Appearance Detection and Auto Name Registration 4.2.1 IPv6 Address Appearance Detection mechanism 4.2.2 Auto Names Generation and Registration mechanism H. Kitamura Expires April 2012 [Page 10]

Internet Draft Corresponding Auto Names for IPv6 Finally, Registrar registers both Regular and Reverse resolving entries for the address and prepared Auto Name are registered to the name server. 4.2.3 Placement of Detector and Registrar H. Kitamura Expires April 2012 [Page 11]

Internet Draft Corresponding Auto Names for IPv6 4.2.4 Detection and Registration Procedures H. Kitamura Expires April 2012 [Page 12]

Internet Draft Corresponding Auto Names for IPv6 [RFC4620] M. Crawford and B. Haberman, "IPv6 Node Information Queries," RFC4620, August 2006 [mDNS] S. Cheshire and M. Krochmal, "Multicast DNS" <draft-cheshire- dnsext-multicastdns-14.txt> work in progress, February 2011 [RFC3849] G. Huston, A. Lord and P. Smith, "IPv6 Address Prefix Reserved for Documentation," RFC3849, July 2004 Authors' Addresses Hiroshi Kitamura Service Platform Research Laboratories, NEC Corporation (SC building 12F)1753, Shimonumabe, Nakahara-Ku, Kawasaki, Kanagawa 211-8666, JAPAN Graduate School of Information Systems, University of Electro-Communications 5-1 Chofugaoka 1-Chome, Chofu-shi, Tokyo 182-8585, JAPAN Phone: +81 44 431 7686 Fax: +81 44 431 7680 Email: kitamura@da.jp.nec.com Shingo Ata Graduate School of Engineering, Osaka City University 3-3-138, Sugimoto, Sumiyoshi-Ku, Osaka 558-8585, JAPAN Phone: +81 6 6605 2191 Fax: +81 6 6605 2191 Email: ata@info.eng.osaka-cu.ac.jp H . Kitamura Expires April 2012 [Page 14]