--- 1/draft-ietf-p2psip-service-discovery-04.txt 2012-04-01 17:13:58.202923503 +0200 +++ 2/draft-ietf-p2psip-service-discovery-05.txt 2012-04-01 17:13:58.230922766 +0200 @@ -1,18 +1,18 @@ P2PSIP Working Group J. Maenpaa Internet-Draft G. Camarillo Intended status: Standards Track Ericsson -Expires: July 9, 2012 January 6, 2012 +Expires: October 3, 2012 April 1, 2012 Service Discovery Usage for REsource LOcation And Discovery (RELOAD) - draft-ietf-p2psip-service-discovery-04.txt + draft-ietf-p2psip-service-discovery-05.txt Abstract REsource LOcation and Discovery (RELOAD) does not define a generic service discovery mechanism as part of the base protocol. This document defines how the Recursive Distributed Rendezvous (ReDiR) service discovery mechanism used in OpenDHT can be applied to RELOAD overlays to provide a generic service discovery mechanism. Status of this Memo @@ -23,21 +23,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." - This Internet-Draft will expire on July 9, 2012. + This Internet-Draft will expire on October 3, 2012. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -50,32 +50,32 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Introduction to ReDiR . . . . . . . . . . . . . . . . . . . . 4 4. Using ReDiR in a RELOAD Overlay Instance . . . . . . . . . . . 6 4.1. Data Structure . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Selecting the Starting Level . . . . . . . . . . . . . . . 7 4.3. Service Provider Registration . . . . . . . . . . . . . . 7 4.4. Refreshing Registrations . . . . . . . . . . . . . . . . . 8 - 4.5. Service Lookups . . . . . . . . . . . . . . . . . . . . . 8 + 4.5. Service Lookups . . . . . . . . . . . . . . . . . . . . . 9 4.6. Removing Registrations . . . . . . . . . . . . . . . . . . 9 5. Access Control Rules . . . . . . . . . . . . . . . . . . . . . 9 6. REDIR Kind Definition . . . . . . . . . . . . . . . . . . . . 10 7. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Overlay Configuration Document Extension . . . . . . . . . . . 12 - 9. Security Considerations . . . . . . . . . . . . . . . . . . . 12 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 13 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 10.1. Access Control Policies . . . . . . . . . . . . . . . . . 13 10.2. Data Kind-ID . . . . . . . . . . . . . . . . . . . . . . . 13 10.3. ReDiR Namespaces . . . . . . . . . . . . . . . . . . . . . 13 - 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 + 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 12.1. Normative References . . . . . . . . . . . . . . . . . . . 14 12.2. Informative References . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 1. Introduction REsource LOcation And Discovery (RELOAD) [I-D.ietf-p2psip-base] is a peer-to-peer signaling protocol that can be used to maintain an overlay network, and to store data in and retrieve data from the @@ -229,41 +229,44 @@ ReDiR tree nodes are stored using the dictionary data model defined in RELOAD base [I-D.ietf-p2psip-base]. The data stored is a RedirServiceProvider Resource Record: enum { none(0), (255) } RedirServiceProviderExtType; struct { RedirServiceProviderExtType type; - NodeId serviceProvider; + Destination destination_list<0..2^16-1>; opaque namespace<0..2^16-1>; uint16 level; uint16 node; uint16 length; select (type) { /* This type may be extended */ } extension; } RedirServiceProvider; The contents of the RedirServiceProvider Resource Record are as follows: type The type of an extension to the RedirServiceProvider Resource Record. Unknown types are allowed. - serviceProvider - The Node-ID of a service provider. + detination_list + A list of IDs through which a message is to be routed to reach the + service provider. The destination list consists of a sequence of + Destination values. The contents of the Destination structure are + as defined in RELOAD base [I-D.ietf-p2psip-base]. namespace An opaque string containing the namespace. level The level in the ReDiR tree. node The position of the node storing this RedirServiceProvider record at the current level in the ReDiR tree. @@ -570,30 +573,30 @@ The authors would like to thank Marc Petit-Huguenin for his comments on the draft. 12. References 12.1. Normative References [I-D.ietf-p2psip-base] Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., and H. Schulzrinne, "REsource LOcation And Discovery (RELOAD) - Base Protocol", draft-ietf-p2psip-base-19 (work in - progress), October 2011. + Base Protocol", draft-ietf-p2psip-base-21 (work in + progress), March 2012. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 12.2. Informative References [I-D.ietf-p2psip-concepts] - Bryan, D., Matthews, P., Shim, E., Willis, D., and S. + Bryan, D., Willis, D., Shim, E., Matthews, P., and S. Dawkins, "Concepts and Terminology for Peer to Peer SIP", draft-ietf-p2psip-concepts-04 (work in progress), October 2011. [Redir] Rhea, S., Godfrey, P., Karp, B., Kubiatowicz, J., Ratnasamy, S., Shenker, S., Stoica, I., and H. Yu, "Open DHT: A Public DHT Service and Its Uses". Authors' Addresses