[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01

Network Working Group                                          E. Gunduz
Internet-Draft                                                  RIPE NCC
Expires: August 20, 2005                               February 19, 2005


     IRIS - URI Resolution for AREG Type for the Internet Registry
                          Information Service
                  draft-ietf-crisp-iris-areg-urires-01

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of section 3 of RFC 3667.  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 become aware will be disclosed, in accordance with
   RFC 3668.

   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 August 20, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document describes a URI Resolution method for the IRIS registry
   schema for IP address and Autonomous System Number information.








Gunduz                  Expires August 20, 2005                 [Page 1]


Internet-Draft              iris-areg-urires               February 2005


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Document Terminology . . . . . . . . . . . . . . . . . . . . .  4
   3.  URI Resolution for AREG  . . . . . . . . . . . . . . . . . . .  5
     3.1   Application Service Label  . . . . . . . . . . . . . . . .  5
     3.2   Top-Down Resolution  . . . . . . . . . . . . . . . . . . .  5
     3.3   Discussion . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Internationalization Considerations  . . . . . . . . . . . . .  7
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   6.1   Normative References . . . . . . . . . . . . . . . . . . . .  9
   6.2   Informative References . . . . . . . . . . . . . . . . . . .  9
       Author's Address . . . . . . . . . . . . . . . . . . . . . . .  9
   A.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
       Intellectual Property and Copyright Statements . . . . . . . . 11



































Gunduz                  Expires August 20, 2005                 [Page 2]


Internet-Draft              iris-areg-urires               February 2005


1.  Introduction

   This document describes a URI resolution method for AREG [4] (Address
   Registry) type in the IRIS [2] namespace.  URI resolution is the
   process of determining which directory server to query for a given
   resource.













































Gunduz                  Expires August 20, 2005                 [Page 3]


Internet-Draft              iris-areg-urires               February 2005


2.  Document Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC2119 [1].














































Gunduz                  Expires August 20, 2005                 [Page 4]


Internet-Draft              iris-areg-urires               February 2005


3.  URI Resolution for AREG

3.1  Application Service Label

   The application service label associated with AREG registry type MUST
   be "AREG1".  This is the abbreviated form the URN for this registry
   type, urn:ietf:params:xml:ns:areg1.

3.2  Top-Down Resolution

   The top-down alternative resolution method MUST be identified as
   'top' in IRIS URI's.

   The client SHOULD start every query from the IRIS server
   iris.nro.net, the top of the hierarchy, and follow the referrals to
   find the authoritative server to actually query.  The client MAY
   start from any other IRIS server in the hierarchy, in which case,
   that IRIS server MAY choose to refer the client to the top of the
   hierarchy if it does not have the authoritative information, or if it
   has an up-to-date map of the current delegation status, it MAY choose
   to refer the client to the IRIS server it believes to be the
   authoritative server for the information sought for.

3.3  Discussion

   AREG URI resolution does not use DNS unlike DREG URI resolution [6].

   Using DNS makes sense in two cases:
   o  When the directory already has natural links to DNS,
   o  When the entities involved do not have the resources or intention
      to maintain the top of the hierarchy.

   In the case of AREG, the entities involved are RIRs (Regional
   Internet Registries) and NRO (Number Resource Organisation), which
   have enough resources and intention to maintain the top of the
   hierarchy.  In fact, RIRs have to keep the global distribution map of
   address allocation, which makes them, or the NRO, which is formed by
   the RIRs to formalize their co-operative efforts, the natural
   candidate to maintain the top of the hierarchy.

   Address registry does not have natural links to DNS either.  Using
   reverse DNS tree presents problems for IP address delegation (for
   example, delegations do not fall into byte boundaries, unlike reverse
   DNS), and DNS does not currently contain any information regarding
   autonomous system delegation.

   As a result, this memo suggests not using DNS for AREG URI
   resolution.



Gunduz                  Expires August 20, 2005                 [Page 5]


Internet-Draft              iris-areg-urires               February 2005


   DNS could perhaps be used to point to the top of the IRIS server
   hierarcy, but this is considered unnecessary indirection.

















































Gunduz                  Expires August 20, 2005                 [Page 6]


Internet-Draft              iris-areg-urires               February 2005


4.  Internationalization Considerations

   This document lays out no new considerations for internationalization
   beyond that specified in IRIS [2].















































Gunduz                  Expires August 20, 2005                 [Page 7]


Internet-Draft              iris-areg-urires               February 2005


5.  Security Considerations

   This document lays out no new considerations for security precautions
   beyond that specified in IRIS [2].















































Gunduz                  Expires August 20, 2005                 [Page 8]


Internet-Draft              iris-areg-urires               February 2005


6.  References

6.1  Normative References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", RFC 2119, BCP 14, March 1997.

   [2]  Newton, A. and M. Sanz, "Internet Registry Information Service",
        RFC 3981, January 2005.

   [3]  Newton, A., "Cross Registry Internet Service Protocol (CRISP)
        Requirements", RFC 3707, February 2004.

   [4]  Gunduz, E., Newton, A. and S. Kerr, "IRIS - An Address Registry
        (areg) Type for the Internet Registry Information Service",
        draft-ietf-crisp-iris-areg-10 (work in progress), February 2005.

6.2  Informative References

   [5]  Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
        Considerations Section in RFCs", RFC 2434, BCP 26, October 1998.

   [6]  Newton, A. and M. Sanz, "IRIS: A Domain Registry (dreg) Type for
        the Internet Registry Information Service (IRIS)", RFC 3982,
        January 2005.


Author's Address

   Engin Gunduz
   RIPE NCC
   Singel 258
   Amsterdam  1016AB
   The Netherlands

   Phone: +31 20 535 4444
   EMail: e.gunduz@computer.org














Gunduz                  Expires August 20, 2005                 [Page 9]


Internet-Draft              iris-areg-urires               February 2005


Appendix A.  Acknowledgements

   Andy Newton, David Blacka, Tim Christensen, Eric Hall, William
   Leibzon, April Marine, George Michaelson, Cathy Murphy, Andrei
   Robachevsky, Shane Kerr, Marcos Sanz, Frederico Neves, Leslie Daigle,
   Rick Wesson and many others contributed constructively in the mailing
   list discussions and IETF Meeting sessions.












































Gunduz                  Expires August 20, 2005                [Page 10]


Internet-Draft              iris-areg-urires               February 2005


Intellectual Property Statement

   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.


Disclaimer of Validity

   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 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.


Copyright Statement

   Copyright (C) The Internet Society (2005).  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.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Gunduz                  Expires August 20, 2005                [Page 11]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/