Network Working Group Ning. Kong Internet-Draft Xiaodong. Li Intended status: Experimental CNNIC Expires: April 28, 2009 Seung Jai. Yi NIDA Oct 25, 2008 Object Naming Service (ONS) Extension for Extensible Supply-chain Discovery Service (ESDS) draft-nkong-esds-ons-00.txt Status of this Memo 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/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 28, 2009. Abstract Object Naming Service (ONS) is a network service that leverages Domain Name System (DNS) to discover information about a product and related services from the Electronic Product Code (EPC). Extensible Supply-chain Discovery Service (ESDS) is an application layer protocol for the distributed sharing and discovery of notification events between associated partners within a supply chain. Unlike DNS or ONS, where there is a known set of root servers, ESDS will have numerous roots for various supply chains operating globally. ONS can be used in collaboration with ESDS to make the multiple ESDS roots be Kong, et al. Expires April 28, 2009 [Page 1] Internet-Draft ESDS naptr Oct 2008 found easily. This document is intended to extend the ONS to support ESDS by defining a new Naming Authority PoinTeR (NAPTR) service type of ONS for ESDS. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. The Relationship Between The ESDS and ONS . . . . . . . . . . 4 4. The Working Flow of The Query For ESDS . . . . . . . . . . . . 4 5. The NAPTR Service Type of ONS For ESDS . . . . . . . . . . . . 5 6. The Service Registration of ONS For ESDS . . . . . . . . . . . 6 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 9. Additional Consideration . . . . . . . . . . . . . . . . . . . 7 10. Security considerations . . . . . . . . . . . . . . . . . . . 7 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 11.1. Normative References . . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . . . 10 Kong, et al. Expires April 28, 2009 [Page 2] Internet-Draft ESDS naptr Oct 2008 1. Introduction ONS [10] is a network service that leverages Domain Name System (DNS) to discover information about a product and related services from the Electronic Product Code (EPC). The most common example is where ONS is used to discover an EPCIS [11] service that contains product data from a manufacturer for a given EPC. ONS may also be used to discover an EPCIS service that has master data pertaining to a particular EPCIS location identifier (this use case is not yet fully addressed in the ONS specification [10]). EPCIS Discovery Service (EPCIS DS) [11] refers to a mechanism, not yet defined by EPCglobal, for locating all EPCIS-enabled Repositories that might have data about a particular EPC. This is useful when the relevant EPCIS services might not otherwise be known to the party who wishes to query them, such as when the handling history of an object is desired but not known (e.g. in support of track-and-trace across a multi-party supply chain). The volumes of serial-level records generated by the supply chains would place an unreasonable burden on the DNS roots if ONS were used as EPCIS DS for holding ONS records for each serial number. ESDS [12][13][14][15] is an application layer protocol for the distributed sharing and discovery of notification events between associated partners within a supply chain. To avoid traffic flat and walking up the Internet root hierarchy, ESDS might use peer-to-peer lookup protocols (such as JXTA [16]) as an alternative to hierarchical lookup protocols such as DNS and ONS. So unlike DNS or ONS, where there is a known set of root servers, ESDS will have numerous roots for various supply chains operating globally. ONS can be used in collaboration with ESDS to make the multiple ESDS roots be found easily. Since ONS contains pointers to services, a simple A record (or IP address) is insufficient for today's more advanced web services based systems. Therefore ONS uses the Naming Authority PoinTeR (NAPTR) DNS record type [3]. This record type contains several fields for denoting the protocol, services and features that a given service endpoint exposes. It also allows the service end point to be expressed as a URI, thus allowing complex services to be encoded in a standard way.This document is intended to define a new NAPTR service type of ONS for ESDS. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this Kong, et al. Expires April 28, 2009 [Page 3] Internet-Draft ESDS naptr Oct 2008 document are to be interpreted as described in BCP 14, RFC 2119 [4]. 3. The Relationship Between The ESDS and ONS As set forth, it is expected that there will be multiple competitively ESDS roots and that some of them will have limited scope (regional, facility wide, etc). So different product may be in the domain of different ESDS root. It is necessary for the inquirer to get the address of the ESDS root in advance. ONS provide pointers to authoritative information about an EPC. ONS may also be used to discover an ESDS root that has correlative data pertaining to a particular EPC. The relationship between the ESDS and ONS is shown in Figure 1. +---+ |ONS| +---+ / | \ / | \ / | \ v v v +-----------+ +-----------+ +-----------+ |ESDS root 1| |ESDS root 2| .... |ESDS root n| +-----------+ +-----------+ +-----------+ Figure 1 Each ESDS root can store its address information into the ONS, and the ONS can provide pointers to each ESDS root for the inquirer. 4. The Working Flow of The Query For ESDS The working flow of the query for ESDS is given as follows. Kong, et al. Expires April 28, 2009 [Page 4] Internet-Draft ESDS naptr Oct 2008 Inquirer ONS ESDS EPCISs | | | | | ONS Query | | | |-------------------->| | | | | | | | Return ESDS Address | | | |---------------------| | | | | | | | ESDS Query | | |----------------------------------->| | | | | | | Return EPCIS Address List | | |------------------------------------| | | | | | | EPCIS Query/Response | |=================================================>| | | | | Figure 2 The inquirer needs to query the ONS for the address of the ESDS before making query to the ESDS. 5. The NAPTR Service Type of ONS For ESDS The use of NAPTR records is governed by a series of RFCs that define something called the Dynamic Delegation Discovery Service [5][6][7][8][9]. In order to safely use NAPTR records on the public network a specification must exist that describes the values of the various fields. As defined in [10], Figure 3 is a template covering information needed for the registration of the NAPTR service type of ONS for ESDS specified in this document. +-------+-------+-------+-----------+------------+-------------+ | Order | Pref | Flags | Service | Regexp | Replacement | +-------+-------+-------+-----------+------------+-------------+ | 0 | value | u | ESDS+name | !^.*$!URI! | . | +-------+-------+-------+-----------+------------+-------------+ Figure 3 o Order: The Order field SHALL be zero. o Pref: The Pref field SHALL be a non-negative integer.The value of the Pref field is an ordinal 438 that specifies that the service in one record is preferred to the service in another record having the same Service field. An ONS Client SHOULD use attempt to use a Kong, et al. Expires April 28, 2009 [Page 5] Internet-Draft ESDS naptr Oct 2008 service having a lower Pref number before using an equivalent service having a higher Pref number. o Flags: The Flags field SHALL be set to 'u', indicating that the Regexp field contains a URI. o Service: The Service field contains an indicator of the type of service that can be found at the URI in question. The value of the Service field SHALL consist of the string ESDS+ followed by the name of a ESDS service. The Service field identifies what type of service is accessible through the URI provided by the Regexp field of this record. See Section "4. The Service Registration of ONS For ESDS" for examples of service types. o Regexp: The Regexp field specifies a URI for the service being described. The value of this field SHALL be the string !^.*$! (the six character sequence consisting of an exclamation point, a caret, a period, an asterisk, a dollar sign, and another exclamation point), followed by a URI, followed by an exclamation point (!) character. o Replacement: The Replacement field is set to a single period ('.'). 6. The Service Registration of ONS For ESDS As defined in [10], the following is a template covering information needed for the registration of the ONS service specified in this document. o Service Name: "ESDS+html" o Functional Specification: Simply returns a URI that will resolve to an HTML page on some server. o Valid URI schemes: http, https, ftp o Security considerations: None not already inherent in the use of the WorldWideWeb. o Service Name: "ESDS+xmlrpc" o Functional Specification: A URI that denotes an HTTP POST capable service on some server that is expecting XML-RPC [17] compliant connection. o Valid URI schemes: http, https o Security considerations: None not already inherent in the use of the WorldWideWeb. o Service Name: "ESDS+ws" o Functional Specification: A generic Web Services [18] based service where the application must negotiate what services are available by investigating the WSDL file found at the URI in the Regexp. Kong, et al. Expires April 28, 2009 [Page 6] Internet-Draft ESDS naptr Oct 2008 o Valid URI schemes: http, https o Security considerations: Web Services utilize a great deal of existing Internet infrastructure and protocols. It is very easy to use some of them in insecure ways. Any usage of Web Services should be done in the context of a thorough understanding of the dependencies, especially as it relates to the DNS and HTTP. NOTE: There will be more types of ONS service for ESDS. 7. Examples NOTE: These are examples only. They are taken from ongoing work and may not represent the end result of that work. They are here for pedagogical reasons only. ;; order pref flags service regexp replacement IN NAPTR 0 0 "u" "ESDS+html" "!^.*$!http://esdstest.com/ds.jsp!" . ;; order pref flags service regexp replacement IN NAPTR 0 10 "u" "ESDS+xmlrpc" "!^.*$!http://esdstest.com/ds.com!" . ;; order pref flags service regexp replacement IN NAPTR 0 20 "u" "ESDS+ws" "!^.*$!http://esdstest.com/ds.wsdl!" . 8. IANA Considerations This document has no actions for IANA. 9. Additional Consideration Besides the ONS, this document can also be applicable to the other naming system using DNS for the addressing of RFID objects. 10. Security considerations This document raises no security issues. Security considerations related to the ONS and DNS can be found in [19]. 11. References Kong, et al. Expires April 28, 2009 [Page 7] Internet-Draft ESDS naptr Oct 2008 11.1. Normative References [1] Mockapetris, P., "Domain names - concepts and facilities", RFC 1034, November 1987. [2] Mockapetris, P., "Domain names - implementation and specification", RFC 1035, November 1987. [3] Mealling, M. and R. Daniel, "The Naming Authority Pointer (NAPTR) DNS Resource Record", RFC 2915, September 2000. [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. [5] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS", RFC 3401, October 2002. [6] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm", RFC 3402, October 2002. [7] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403, October 2002. [8] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)", RFC 3404, October 2002. [9] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures", RFC 3405, October 2002. 11.2. Informative References [10] EPCglobal, "EPCglobal Object Name Service (ONS) 1.0.1", May 2008. [11] EPCglobal, "EPC Information Services (EPCIS) Version 1.0.1 Specification", September 2007. [12] Rezafard, A., "Extensible Supply-chain Discovery Service Problem Statement", Work in Progress. [13] Young, M., "Extensible Supply-chain Discovery Service Concepts", Work in Progress. [14] Thompson, F., "Extensible Supply-chain Discovery Service Schema", Work in Progress. Kong, et al. Expires April 28, 2009 [Page 8] Internet-Draft ESDS naptr Oct 2008 [15] Thompson, F., "Extensible Supply-chain Discovery Service Commands", Work in Progress. [16] Duigou, M., "JXTA v2.0 Protocols Specification", June 2004. [17] Winer, D., "XML-RPC Specification", 1999. [18] (WorldWideWeb Consortium), "Web Services Activity", 2000. [19] Arends, R., "Protocol Modifications for the DNS Security Extensions", Work in Progress. Authors' Addresses Ning,Kong CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3147 Email: nkong@cnnic.cn Xiaodong,Li CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3020 Email: lee@cnnic.cn Seung Jai,Yi NIDA 3f,398,Seochoro,Seocho-gu Seoul, Seoul 137-857 Korea Phone: +82 2 2186 4551 Email: sjlee@nida.or.kr Kong, et al. Expires April 28, 2009 [Page 9] Internet-Draft ESDS naptr Oct 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. Kong, et al. Expires April 28, 2009 [Page 10]