One document matched: draft-ietf-ipngwg-dns-rr-rgadd-00.txt

Internet-Draft                                                 Jim Bound
IPng Working Group                                Digital Equipment Corp
March 1997



         Synthesis of Routing Goop and AAAA Records in IPv6

                <draft-ietf-ipngwg-dns-rr-rgadd-00.txt>


Status of this Memo

   This document is a submission to the IPng Working Group of the
   Internet Engineering Task Force (IETF).  Comments should be submitted
   to the ipng@sunroof.eng.sun.com mailing list.  This document is not
   at this time a product of the IPng Working Group, but a proposal to
   become a product of the IPng Working Group.

   This document is an Internet-Draft.  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.''

   To learn the current status of any Internet-Draft, please check the
   ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
   Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
   munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
   ftp.isi.edu (US West Coast).

   Distribution of this document is unlimited.

Abstract

   This document is a proposal to redefine the existing DNS AAAA
   resource record into two resource records: an RG record to define the
   routing topology of an IPv6 address and an aAA record to define the
   End System Identifier of an IPv6 address.  The document will define
   the synthesis of the RG and aAA record at the DNS primary server,
   which will return an AAAA record to DNS resolvers.  The objective of
   this work is to split the AAAA record in the DNS into location and
   identifier to provide future capabilities for dynamic renumbering of
   addresses.  This work was spawned by the GSE - Alternate Addressing
   Architecture Proposal for IPv6.













Bound           Expires September 1997                          [Page 1]


Internet-Draft   draft-ietf-ipngwg-dns-rr-rgadd-00.txt        March 1997


Table of Contents:

1. Introduction.................................................3
2. Terminology and Definitions..................................3
3. New Resource Record Definitions..............................3
3.1 aAA record type.............................................3
3.2 RG record type..............................................4
3.3 aAA data format.............................................4
3.4 RG data format..............................................4
3.5 AAAA query..................................................4
3.6 Textual format of aAA and RG records........................4
4. Modifications to existing Query Types........................4
5. Security Considerations......................................5
Acknowledgements................................................5
References......................................................5
Authors' Address................................................5












































Bound           Expires September 1997                          [Page 2]


Internet-Draft   draft-ietf-ipngwg-dns-rr-rgadd-00.txt        March 1997


1. Introduction

   This document is a proposal to redefine the existing DNS AAAA
   resource record [3,4] into two resource records: an RG record to
   define the routing topology of an IPv6 address and an aAA record to
   define the End System Identifier of an IPv6 address.  The document
   will define the synthesis of the RG and aAA record at the DNS primary
   server, which will return an AAAA record to DNS resolvers.  The
   objective of this work is to split the AAAA record in the DNS into
   location and identifier to provide future capabilities for dynamic
   renumbering of addresses.  This work was spawned by the GSE -
   Alternate Addressing Architecture Proposal for IPv6 [5].

   The design objective of these two record types is to make it
   transparent to existing DNS resolvers and the DNS protocol used  to
   query for AAAA records.

   This proposal is dependent on the IPng WG buying into new definitions
   via a new addressing architecture proposal, support for clear
   boundaries for an end system identifier, and the definition of the
   routing goop to define location for the end system identifier.  Upon
   completion of that work in the WG if it moves forward the author can
   finish this specification where "????" and "TBD" exists presently.



2. Terminology and Definitions

   node         - A device that implements IPv6.

   interface    - A node's attachment to the link.

   address      - An IP layer identifier for an interface or a set
                  of interfaces.




3. New Resource Record Definitions

   Two new record types are defined to store a node's IPv6 address. A
   node that has more than one IPv6 address must have more than one such
   record or record combinations.



3.1 aAA record type

   The aAA resource record type is a new record specific to the Internet
   class that stores a single IPv6 address for a nodes interface.  It is
   an ESD as defined in TBD.

   The value of the type is TBD (decimal).







Bound           Expires September 1997                          [Page 3]


Internet-Draft   draft-ietf-ipngwg-dns-rr-rgadd-00.txt        March 1997


3.2 RG record type

   The RG resource record type is a new record specific to the Internet
   class that stores a single IPv6 address for a nodes location within a
   routing domain.  It is RG as defined in TBD.

   The value of the type is TBD (decimal).



3.3 aAA data format

   A ??? bit IPv6 ESD address is encoded in the data portion of an aAA
   resource record in network byte order (high-order byte first).



3.4 RG data format

   A ??? bit IPv6 RG address is encoded in the data portion of an RG
   resource record in network byte order (high-order byte first).



3.5 AAAA query

   An AAAA [1,2,4] query for a specified domain name in the Internet
   class returns all associated AAAA resource records in the answer
   section of a response.  The DNS primary server [2] will synthesize
   the RG and aAA records to produce an AAAA record in the answer
   section of the response for a query for an AAAA record.

   A type AAAA query does not perform additional section processing.




3.6 Textual format of aAA and RG records

   The textual representation of the data portion of an aAA and RG
   resource record used in a master database file is the textual
   representation of a IPv6 address as defined in [3 + update for aAA
   and RG TBD].



4. Modifications to existing Query Types

   Query processing as defined for AAAA records [4] would continue to be
   processed as defined presently for IPv6.  The DNS primary server
   would bee responsible for concatentating the RG and aAA records to
   respond to an AAAA query from resolvers.  There may be multiple RG's
   defined for each aAA record, and in those cases the DNS primary
   server after synthesis of RG's to a specific aAA record must return
   muliple AAAA record types in the answer section of a query response
   for AAAA records.

   The exception for the present AAAA records as defined is the IP6.INT


Bound           Expires September 1997                          [Page 4]


Internet-Draft   draft-ietf-ipngwg-dns-rr-rgadd-00.txt        March 1997


   domain.  The IPng WG at present is discussing a new methodology to
   obtain addresses for names in a query but use of an ICMP message to
   determine the name for an address.  This needs further investigation
   to determine it if has an affect on AAAA records.

   But the same synthesis of RG + aAA records can be done for the
   reverse address requirement for DNS PTR records [2], to process AAAA
   reverse lookups in the DNS.



5. Security Considerations

   Security issues are not discussed in this memo.



Acknowledgements

   The attendees at the IPng Interim WG meeting to review the GSE
   proposal at Sun Microsystems in Palo Alto, CA on February 27/28,
   1997.



References

   [1]  Mockapetris, P., "Domain Names - Concepts and Facilities", STD
        13, RFC 1034, USC/Information Sciences Institute, November 1987.

   [2]  Mockapetris, P., "Domain Names - Implementation and Specifica-
        tion", STD 13, RFC 1035, USC/Information Sciences Institute,
        November 1987.

   [3]  Hinden, R., and S. Deering, Editors, "IP Version 6 Addressing
        Architecture", RFC 1884, Ipsilon Networks, Xerox PARC, December
        1995.

   [4]  Tompson, S., and Huitema, C. "DNS Extensions to Support IP
        version 6", RFC 1886, Bellcore, December 1995.

   [5]  O'dell, M. "GSE - An Alternate Addressing Architecture for IPv6"
        draft-ipngwg-gseaddr-00.txt, UUNET Technologies, Februrary 1997.


Authors' Address

    Jim Bound
    Digital Equipment Corporation
    110 Spitbrook Road, ZKO3-3/U14
    Nashua, NH 03062
    Phone: (603) 881-0400
    Email: bound@zk3.dec.com







Bound           Expires September 1997                          [Page 5]