draft-ietf-p2psip-service-discovery-13.txt   draft-ietf-p2psip-service-discovery-14.txt 
P2PSIP Working Group J. Maenpaa P2PSIP Working Group J. Maenpaa
Internet-Draft G. Camarillo Internet-Draft G. Camarillo
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: December 16, 2014 June 14, 2014 Expires: January 30, 2015 July 29, 2014
Service Discovery Usage for REsource LOcation And Discovery (RELOAD) Service Discovery Usage for REsource LOcation And Discovery (RELOAD)
draft-ietf-p2psip-service-discovery-13.txt draft-ietf-p2psip-service-discovery-14.txt
Abstract Abstract
REsource LOcation and Discovery (RELOAD) does not define a generic REsource LOcation and Discovery (RELOAD) does not define a generic
service discovery mechanism as a part of the base protocol. This service discovery mechanism as a part of the base protocol. This
document defines how the Recursive Distributed Rendezvous (ReDiR) document defines how the Recursive Distributed Rendezvous (ReDiR)
service discovery mechanism used in OpenDHT can be applied to RELOAD service discovery mechanism used in OpenDHT can be applied to RELOAD
overlays to provide a generic service discovery mechanism. overlays to provide a generic service discovery mechanism.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 16, 2014. This Internet-Draft will expire on January 30, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
6. REDIR Kind Definition . . . . . . . . . . . . . . . . . . . . 13 6. REDIR Kind Definition . . . . . . . . . . . . . . . . . . . . 13
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. Service Registration . . . . . . . . . . . . . . . . . . 14 7.1. Service Registration . . . . . . . . . . . . . . . . . . 14
7.2. Service Lookup . . . . . . . . . . . . . . . . . . . . . 16 7.2. Service Lookup . . . . . . . . . . . . . . . . . . . . . 16
8. Overlay Configuration Document Extension . . . . . . . . . . 17 8. Overlay Configuration Document Extension . . . . . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17 9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
10.1. Access Control Policies . . . . . . . . . . . . . . . . 17 10.1. Access Control Policies . . . . . . . . . . . . . . . . 17
10.2. A New IETF XML Registry . . . . . . . . . . . . . . . . 18 10.2. A New IETF XML Registry . . . . . . . . . . . . . . . . 18
10.3. Data Kind-ID . . . . . . . . . . . . . . . . . . . . . . 18 10.3. Data Kind-ID . . . . . . . . . . . . . . . . . . . . . . 18
10.4. ReDiR Namespaces . . . . . . . . . . . . . . . . . . . . 18 10.4. RELOAD Services Registry . . . . . . . . . . . . . . . . 18
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
12.1. Normative References . . . . . . . . . . . . . . . . . . 19 12.1. Normative References . . . . . . . . . . . . . . . . . . 19
12.2. Informative References . . . . . . . . . . . . . . . . . 19 12.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
REsource LOcation And Discovery (RELOAD) [RFC6940] is a peer-to-peer REsource LOcation And Discovery (RELOAD) [RFC6940] is a peer-to-peer
signaling protocol that can be used to maintain an overlay network, signaling protocol that can be used to maintain an overlay network,
and to store data in and retrieve data from the overlay. Although and to store data in and retrieve data from the overlay. Although
RELOAD defines a Traversal Using Relays around Network Address RELOAD defines a Traversal Using Relays around Network Address
Translation (TURN) specific service discovery mechanism, it does not Translation (TURN) specific service discovery mechanism, it does not
define a generic service discovery mechanism as a part of the base define a generic service discovery mechanism as a part of the base
protocol. This document defines how the Recursive Distributed protocol. This document defines how the Recursive Distributed
skipping to change at page 18, line 24 skipping to change at page 18, line 24
XML: N/A, the requested URI is an XML namespace XML: N/A, the requested URI is an XML namespace
10.3. Data Kind-ID 10.3. Data Kind-ID
This document introduces one additional data Kind-ID to the "RELOAD This document introduces one additional data Kind-ID to the "RELOAD
Data Kind-ID" Registry: Data Kind-ID" Registry:
+--------------+------------+----------+ +--------------+------------+----------+
| Kind | Kind-ID | RFC | | Kind | Kind-ID | RFC |
+--------------+------------+----------+ +--------------+------------+----------+
| REDIR | 104 | RFC-AAAA | | REDIR | 0x104 | RFC-AAAA |
+--------------+------------+----------+ +--------------+------------+----------+
This Kind-ID was defined in Section 6. This Kind-ID was defined in Section 6.
Note to RFC Editor: please replace AAAA with the RFC number for this Note to RFC Editor: please replace AAAA with the RFC number for this
specification. specification.
10.4. ReDiR Namespaces 10.4. RELOAD Services Registry
IANA is requested to create a "ReDiR Namespaces" Registry. Entries IANA is requested to create a new registry for ReDiR namespaces.
in this registry are strings denoting ReDiR namespace values. The
initial contents of this registry are: Registry Name: RELOAD Services Registry
Reference: RFC-AAAA
Registration Procedure: Specification Required
[TO BE REMOVED: The registry should be located under
http://www.iana.org/assignments/reload and be called: RELOAD Services
Registry].
Entries in this registry are strings denoting ReDiR namespace values.
The initial contents of this registry are:
+----------------+----------+ +----------------+----------+
| Namespace | RFC | | Namespace | RFC |
+----------------+----------+ +----------------+----------+
| turn-server | RFC-AAAA | | turn-server | RFC-AAAA |
+----------------+----------+ +----------------+----------+
| voice-mail | RFC-AAAA | | voice-mail | RFC-AAAA |
+----------------+----------+ +----------------+----------+
The namespace 'turn-server' is used by nodes that wish to register as The namespace 'turn-server' is used by nodes that wish to register as
skipping to change at page 19, line 36 skipping to change at page 19, line 50
[RFC6940] Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., and [RFC6940] Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., and
H. Schulzrinne, "REsource LOcation And Discovery (RELOAD) H. Schulzrinne, "REsource LOcation And Discovery (RELOAD)
Base Protocol", RFC 6940, January 2014. Base Protocol", RFC 6940, January 2014.
12.2. Informative References 12.2. Informative References
[I-D.ietf-p2psip-concepts] [I-D.ietf-p2psip-concepts]
Bryan, D., Matthews, P., Shim, E., Willis, D., and S. Bryan, D., Matthews, P., Shim, E., Willis, D., and S.
Dawkins, "Concepts and Terminology for Peer to Peer SIP", Dawkins, "Concepts and Terminology for Peer to Peer SIP",
draft-ietf-p2psip-concepts-05 (work in progress), July draft-ietf-p2psip-concepts-06 (work in progress), June
2013. 2014.
[Redir] Rhea, S., Godfrey, P., Karp, B., Kubiatowicz, J., [Redir] Rhea, S., Godfrey, P., Karp, B., Kubiatowicz, J.,
Ratnasamy, S., Shenker, S., Stoica, I., and H. Yu, "Open Ratnasamy, S., Shenker, S., Stoica, I., and H. Yu, "Open
DHT: A Public DHT Service and Its Uses", October 2005. DHT: A Public DHT Service and Its Uses", October 2005.
Authors' Addresses Authors' Addresses
Jouni Maenpaa Jouni Maenpaa
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
 End of changes. 9 change blocks. 
12 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/