[Search] [txt|pdf|bibtex] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 11                           
Internet Draft                                            R. Atkinson
draft-rja-ilnp-dns-01.txt                            Extreme Networks
Category: Experimental
Expires: 10 JUN 2009                                 10 December 2008




                    Additional DNS Resource Records
                       draft-rja-ilnp-dns-01.txt





STATUS OF THIS MEMO

   Distribution of this memo is unlimited.

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of 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/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This document is a contribution to the IRTF Routing Research
   Group.  It is NOT a contribution to the IETF or to any IETF
   Working Group or to any IETF Area.

ABSTRACT

   This note describes two additional optional Resource Records for use
   with the Domain Name System (DNS).  At present these optional resource
   records are subject of experimentation in certain IPv6 networks.



Atkinson                   Expires in 6 months                  [Page 1]


Internet Draft                  ILNP DNS                     10 DEC 2008


   Limited deployment is anticipated in the near future.


















































Atkinson                   Expires in 6 months                  [Page 2]


Internet Draft                  ILNP DNS                     10 DEC 2008


1. INTRODUCTION

        The Domain Name System (DNS) is the standard way that Internet
   nodes locate information about addresses, mail exchangers, and other
   data relating to remote Internet nodes. [Mock87a, Mock87b] More
   recently, the IETF have defined standards-track security extensions
   to the DNS. [AALMR05] These security extensions can be used to
   authenticate signed DNS data records and can also be used to store
   signed public keys in the DNS.  Further, the IETF have defined a
   standards-track approach to enable secure dynamic update of DNS
   records over the network. [Well00]

        This document defines two new optional Resource Records.
   This note specifies the syntax and other items required for
   independent implementations of these two DNS resource records.
   The reader is assumed to be familiar with the basics of DNS,
   including familiarity with [Mock87a] [Mock87b].

        This document is not on the IETF standards-track
   and does not specify any level of standard.  This document
   merely provides information for the Internet community.

2. NEW RESOURCE RECORDS

        This document specifies two new and closely related
   DNS Resource Records (RRs).  The two new RR types have the
   mnemonics "L" and "I".  The L and I records are associated
   with a fully-qualified domain name.

        These resource records are not on the IETF standards
   track and are not standards of any sort.  Instead, these
   records are defined for use in limited deployment and
   experimental work within certain existing IP-based networks.

2.1 "L" Resource Record

     An "L" record has the DNS TYPE of "L" and a numeric value
   of <to be assigned by IANA>.  An "L" record is a member of
   the Internet ("IN") CLASS in the DNS.  Each L record is
   associated with a <domain-name> entry in the DNS.  The
   Preference field indicates the domain-name's relative
   preference for this particular L record among other L
   records for the same domain-name.

   An L record has the following logical components:
        <domain-name>  IN  L  <preference>   <L>





Atkinson                   Expires in 6 months                  [Page 3]


Internet Draft                  ILNP DNS                     10 DEC 2008


        In the above, <domain-name> is any valid domain name
   string, <preference> is an unsigned 16-bit value, while <L>
   is an unsigned 64-bit value that names a subnetwork where
   <domain-name> is directly attached.

        A given <domain-name> may have zero or more L values
   at a given time.  A multi-homed host will, by definition,
   have multiple L values while multi-homed.  A domain-name
   that is not a host may have an "L" record as a wild-card
   entry, in this case the domain-name must be naming a
   subnetwork.  This last usage is most common operationally
   when the named subnetwork is, was, or might become, mobile.

        The Preference field indicates the domain-name's
   relative preference for this L record among other L records
   associated with this domain-name.  Lower values are
   preferred.

     The L DNS record has the following RDATA format:

       +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
       |               Preference                      |
       +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
       |                                               |
       |                   L                           |
       |                                               |
       |                                               |
       +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+


   where:

   Preference     A 16-bit unsigned integer which specifies the
                   preference given to this RR among others at
                   the same owner.  Lower values are preferred.

   L               A 64-bit unsigned integer that names a
                   subnetwork.

   L records cause additional section processing to lookup all
   I records for the same domain-name target. All I records
   located are returned by the DNS server as additional data
   present in the L record reply.

2.2 "I" Resource Record

   An I record has the following logical components:
        <domain-name>  IN  I  <preference>   <I>



Atkinson                   Expires in 6 months                  [Page 4]


Internet Draft                  ILNP DNS                     10 DEC 2008


        An "I" record has the DNS TYPE of "I" and a numeric
   value of <to be assigned by IANA>.  An "I" record is a
   member of the Internet ("IN") CLASS in the DNS.  Each I
   record is associated with a <domain-name> entry in the DNS.
   Only a <domain-name> that is associated with an Internet
   node may have an "I" record.  Any <domain-name> that is not
   a node on the Internet must not have an "I" record.

        The Preference field indicates the domain-name's
   relative preference for this I record among other I records
   associated with this domain-name.  Lower values are
   preferred.

        In the above <domain-name> is any valid domain name
   string, while <I> is an unsigned 64-bit value.  A given
   <domain-name> may have zero or more I records at a given
   time.  In normal operation, nodes that support the
   Identifier-Locator Network Protocol (ILNP) will have at
   least one valid I record.

     The I DNS record has the following RDATA format:

       +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
       |               Preference                      |
       +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
       |                                               |
       |                   I                           |
       |                                               |
       |                                               |
       +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+


   where:

   Preference     A 16-bit unsigned integer which specifies the
                   preference given to this RR among others at
                   the same owner.  Lower values are preferred.

   I               A 64-bit unsigned integer.


   I records cause additional section processing which looks up all L
   records for the same domain-name target. All L records located are
   returned by the DNS server as additional data present in the L record
   reply.






Atkinson                   Expires in 6 months                  [Page 5]


Internet Draft                  ILNP DNS                     10 DEC 2008


3. Usage Example

        Given a domain-name, one can use the Domain Name System (DNS)
   to discover the set of I records and the set of L records associated
   with that domain-name.  A given domain-name might have zero or more
   I records at a time and might have zero or more L records at a time.
   This lookup process is considered to be in the "forward" direction.

        The preference fields associated with the I and L records
   are used to indicate the domain-name's preference for others to use
   one particular I or L record, rather than use another I or L record
   also associated with that domain-name.

        When a DNS server that implements this specification receives
   an AAAA record query, the server perform additional section processing
   to locate all I and L records associated with the target domain-name.
   If found, these I and L records will be returned as additional data
   in the AAAA record reply.

4. SECURITY CONSIDERATIONS


        These new DNS resource record types do not create any new
   vulnerabilities.  Existing mechanisms for DNS security can be used
   unchanged with these record types.

        In situations where authentication of DNS data is a concern,
   the DNS Security extensions should be used.[AALMR05]

        If these DNS records are updated dynamically over the network,
   then the Secure Dynamic DNS Update [Well00] mechanism should be used
   to secure such transactions.


5. IANA CONSIDERATIONS

        IANA is requested to allocate each of these two DNS
   Resource Records a value from the "Specification Required"
   block (32768 - 65279) according to the procedures of Section
   3.1 on page 7 of RFC-2929 for "Specification Required".
   [EBM00]

5. INFORMATIVE REFERENCES

   [EBM00] D. Eastlake 3rd, E. Brunner-Williams, & B. Manning,
           "Domain Name System IANA Considerations", RFC-2929,
           RFC-Editor, September 2000.




Atkinson                   Expires in 6 months                  [Page 6]


Internet Draft                  ILNP DNS                     10 DEC 2008


   [AALMR05] R. Arends, R. Austein, M. Larson, D. Massey, &
           S. Rose, "DNS Security Introduction & Requirements",
           RFC-4033, RFC Editor, March 2005.

   [Well00] B. Wellington, "Secure Domain Name System Dynamic
            Update", RFC-3007, RFC Editor, November 2000.

   [Mock87a] P. Mockapetris, "Domain names - Implementation and
        Specification", RFC-1035, 1 November 1987.

   [Mock87b] P. Mockapetris, "Domain names - Concepts and
        Facilities", RFC-1036, 1 November 1987


AUTHOR'S ADDRESS:

   R. Atkinson
   Extreme Networks
   3585 Monroe Street
   Santa Clara, CA
   95051  USA

   Email: rja@extremenetworks.com
   Telephone: +1 (408)579-2800



























Atkinson                   Expires in 6 months                  [Page 7]


Internet Draft                  ILNP DNS                     10 DEC 2008


Full Copyright Statement

Copyright (C) The IETF Trust (2008).

  This document is subject to the rights, licenses and restrictions
  contained in BCP 78, and except as set forth therein, the authors
  retain all their rights.

  This document and the information contained herein are provided
  on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
  REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY,
  THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM
  ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
  ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
  INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
  OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology
described in this document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights.  Information on the procedures with respect to
rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository
at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention
any copyrights, patents or patent applications, or other
proprietary rights that may cover technology that may be required
to implement this standard.  Please address the information to the
IETF at ietf-ipr@ietf.org.

This document may not be modified, and derivative works of it
may not be created.

This document may only be posted in an Internet-Draft.

Expires: 10 June 2009




Atkinson                   Expires in 6 months                  [Page 8]