One document matched: draft-snell-dnsepduri-00.txt

Internet-Draft                                                  J. Snell
draft-snell-dnsepduri-00                                       A. Donoho
Expires: April 15, 2005                                              IBM
                                                            October 2004



            The "ws:" URI Scheme for DNS Endpoint Discovery


Status of this Memo


   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   and any of which I 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.


   This document may not be modified, and derivative works of it may
   not be created, except to publish it as an RFC and to translate it
   into languages other than English.


   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 April 15, 2005.


Copyright Notice


   Copyright (C) The Internet Society (2004).  All Rights Reserved.


Abstract


   This memo introduces the "ws:" URI scheme for use in conjunction with
   DNS-Based Web Services Discovery.  The URI is used to identify Web
   services that have been advertised in DNS.







Snell & Donoho           Expires April 15, 2005                 [Page 1]
Internet-Draft                DNS-EPD URI                   October 2004



Table of Contents


   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.   URI Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.   URI Semantics  . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.   Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
   5.   Security Considerations  . . . . . . . . . . . . . . . . . . . 4
   6.   IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 4
   7.   Normative References . . . . . . . . . . . . . . . . . . . . . 4
        Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 5
   A.   Registration Template  . . . . . . . . . . . . . . . . . . . . 5
        Intellectual Property and Copyright Statements . . . . . . . . 6








































Snell & Donoho           Expires April 15, 2005                 [Page 2]
Internet-Draft                DNS-EPD URI                   October 2004



1.  Introduction


   The DNS Endpoint Discovery (DNS-EPD) specification [5] defines two
   new DNS resource records types that may be used to advertise
   references to Web service endpoints deployed within a given DNS
   domain.  The goal of the ws: URI scheme is to provide a means of
   identifying and referencing endpoint references advertised in DNS
   using the DNS-EPD mechanisms.


   URI's conforming to the ws: URI Scheme are hereafter referred to as
   DNS-EPD URIs.


   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 [1].


2.  URI Syntax


   A DNS-EPD URI has the following syntax:


   dnsepdURI        ::= "ws:" eprName
   eprName          ::= subdomain | " "
   subdomain        ::= label | subdomain "." label
   label            ::= letter [ [ ldh-str ] let-dig ]
   ldh-str          ::= let-dig-hyp | let-dig-hyp ldh-str
   let-dig-hyp      ::= let-dig | "-"
   let-dig          ::= letter | digit
   letter           ::= a-zA-Z
   digit            ::= 0-9


   eprName is subject the exact construction and encoding rules as DNS
   domain names as specified in RFC 1035 [4] and MUST reference EPR
   resource records as defined in [5].


   DNS-EPD URI's are case insensitive.  DNS-EPD URI's are lexically
   equivalent if the eprName for each are identical in a
   case-insensitive character-by-character comparison.


3.  URI Semantics


   Unlike URI schemes that reference specific network hosts, DNS-EPD
   URI's reference records contained in DNS.  The eprName portion of the
   URI is the DNS name of either an EPR resource record as defined by
   [5] or a CNAME record used to specify an alias for an EPR resource
   record.







Snell & Donoho           Expires April 15, 2005                 [Page 3]
Internet-Draft                DNS-EPD URI                   October 2004



   DNS-EPD URIs are dereferencable by submitting a DNS query for all EPR
   resource records associated with the name specified in the eprName
   portion of the URI.


4.  Examples


     ws:inquire.uddi._ws.example.com


   This example references an EPR resource record advertising UDDI
   services within the example.com DNS domain.


   The eprName given above would be used to retrieve zero or more EPR
   records from DNS as in the following example query.


     >nslookup -q=EPR inquire.uddi._ws.example.com
     inquire.uddi._ws.example.com EPR 100 0 0 uddi.example.com
                                              /services/inquire
                                              {urn:uddi-v2}Inquire


   Following resolution of the EPR resource record, clients would use
   the information returned by DNS to connect to and invoke the
   advertised Web service endpoint.


5.  Security Considerations


   The security considerations for DNS-EPD are discussed in the Security
   Considerations section of [5].  Beyond those discussed in the DNS-EPD
   specification, the DNS-EPD URI introduces no new security
   considerations.


6.  IANA Considerations


   The IANA is asked to register the URL registration template found in
   Appendix A in accordance with [3]


7  Normative References


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


   [2]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
        Identifiers (URI): Generic Syntax", RFC 2396, August 1998.


   [3]  Petke, R. and I. King, "Registration Procedures for URL Scheme
        Names", BCP 35, RFC 2717, November 1999.


   [4]  Mockapetris, P., "Domain names - implementation and
        specification", STD 13, RFC 1035, November 1987.




Snell & Donoho           Expires April 15, 2005                 [Page 4]
Internet-Draft                DNS-EPD URI                   October 2004



   [5]  Snell, J. and A. Donoho, "DNS-Based Web Service Discovery
        (DNS-EPD)",October 2004.



Authors' Addresses


   James M Snell
   IBM
   3039 Cornwallis Rd., P.O. Box 12195
   Research Triangle Park, NC  27709
   US


   Phone: +1  877 511 5082
   EMail: jasnell@us.ibm.com
   URI:   http://www.ibm.com



   Andrew W Donoho
   IBM
   11501 Burnet Road
   Austin, TX  78758
   US


   Phone: +1  877 220 0659
   EMail: awd@us.ibm.com
   URI:   http://www.ibm.com


Appendix A.  Registration Template


      URL scheme name: ws
      URL scheme syntax: Section 2
      Character encoding considerations: Section 2
      Intended usage: Section 3
      Applications and/or protocols which use this scheme:
   [5]


      Interoperability considerations: None
      Security considerations: Section 5
      Relevant publications:
   [5]


      Contact: The author, Section 8
      Author/Change Controller: This scheme would be registered under 
      the IETF tree, therefore the IETF will maintain change control.








Snell & Donoho           Expires April 15, 2005                 [Page 5]
Internet-Draft                DNS-EPD URI                   October 2004



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 (2004).  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.





Snell & Donoho           Expires April 15, 2005                 [Page 6]