P2PSIP Working Group J. Maenpaa
Internet-Draft G. Camarillo
Intended status: Standards Track Ericsson
Expires: August 27, 2013 February 23, 2013
Service Discovery Usage for REsource LOcation And Discovery (RELOAD)
draft-ietf-p2psip-service-discovery-08.txt
Abstract
REsource LOcation and Discovery (RELOAD) does not define a generic
service discovery mechanism as a 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
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
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 August 27, 2013.
Copyright Notice
Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Maenpaa & Camarillo Expires August 27, 2013 [Page 1]
Internet-Draft Service Discovery Usage for RELOAD February 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Introduction to ReDiR . . . . . . . . . . . . . . . . . . . . 4
4. Using ReDiR in a RELOAD Overlay Instance . . . . . . . . . . . 7
4.1. Data Structure . . . . . . . . . . . . . . . . . . . . . . 7
4.2. Selecting the Starting Level . . . . . . . . . . . . . . . 8
4.3. Service Provider Registration . . . . . . . . . . . . . . 9
4.4. Refreshing Registrations . . . . . . . . . . . . . . . . . 9
4.5. Service Lookups . . . . . . . . . . . . . . . . . . . . . 10
4.6. Removing Registrations . . . . . . . . . . . . . . . . . . 11
5. Access Control Rules . . . . . . . . . . . . . . . . . . . . . 12
6. REDIR Kind Definition . . . . . . . . . . . . . . . . . . . . 12
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1. Service Registration . . . . . . . . . . . . . . . . . . . 13
7.2. Service Lookup . . . . . . . . . . . . . . . . . . . . . . 15
8. Overlay Configuration Document Extension . . . . . . . . . . . 15
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
10.1. Access Control Policies . . . . . . . . . . . . . . . . . 16
10.2. Data Kind-ID . . . . . . . . . . . . . . . . . . . . . . . 16
10.3. ReDiR Namespaces . . . . . . . . . . . . . . . . . . . . . 16
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
12.1. Normative References . . . . . . . . . . . . . . . . . . . 17
12.2. Informative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Maenpaa & Camarillo Expires August 27, 2013 [Page 2]
Internet-Draft Service Discovery Usage for RELOAD February 2013
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
overlay. Although RELOAD defines a Traversal Using Relays around
Network Address Translation (TURN) specific service discovery