draft-ietf-p2psip-service-discovery-12.txt   draft-ietf-p2psip-service-discovery-13.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 10, 2014 June 8, 2014 Expires: December 16, 2014 June 14, 2014
Service Discovery Usage for REsource LOcation And Discovery (RELOAD) Service Discovery Usage for REsource LOcation And Discovery (RELOAD)
draft-ietf-p2psip-service-discovery-12.txt draft-ietf-p2psip-service-discovery-13.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 10, 2014. This Internet-Draft will expire on December 16, 2014.
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 18, line 43 skipping to change at page 18, line 43
IANA is requested to create a "ReDiR Namespaces" Registry. Entries IANA is requested to create a "ReDiR Namespaces" Registry. Entries
in this registry are strings denoting ReDiR namespace values. The in this registry are strings denoting ReDiR namespace values. The
initial contents of this registry are: initial contents of this registry are:
+----------------+----------+ +----------------+----------+
| Namespace | RFC | | Namespace | RFC |
+----------------+----------+ +----------------+----------+
| turn-server | RFC-AAAA | | turn-server | 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
providers of a TURN relay service in the RELOAD overlay and by nodes providers of a TURN relay service in the RELOAD overlay and by nodes
that wish to discover providers of a TURN relay service from the that wish to discover providers of a TURN relay service from the
RELOAD overlay. RELOAD overlay. In the TURN server discovery use case, the ReDiR-
based service discovery and registration mechanism specified in this
document can be used as an alternative to the TURN server discovery
mechanism specified in the RELOAD base specification [RFC6940]. The
namespace 'voice-mail' is intended for a voice mail service
implemented on top of a RELOAD overlay.
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.
11. Acknowledgments 11. Acknowledgments
The authors would like to thank Marc Petit-Huguenin, Joscha The authors would like to thank Marc Petit-Huguenin, Joscha
Schneider, and Carlos Bernardos for their comments on the document. Schneider, and Carlos Bernardos for their comments on the document.
12. References 12. References
 End of changes. 5 change blocks. 
4 lines changed or deleted 11 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/