draft-ietf-p2psip-sip-12.txt   draft-ietf-p2psip-sip-13.txt 
P2PSIP C. Jennings P2PSIP C. Jennings
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track B. Lowekamp Intended status: Standards Track B. Lowekamp
Expires: July 31, 2014 Skype Expires: January 22, 2015 Skype
E. Rescorla E. Rescorla
RTFM, Inc. RTFM, Inc.
S. Baset S. Baset
H. Schulzrinne H. Schulzrinne
Columbia University Columbia University
T. Schmidt, Ed. T. Schmidt, Ed.
HAW Hamburg HAW Hamburg
January 27, 2014 July 21, 2014
A SIP Usage for RELOAD A SIP Usage for RELOAD
draft-ietf-p2psip-sip-12 draft-ietf-p2psip-sip-13
Abstract Abstract
This document defines a SIP Usage for REsource LOcation And Discovery This document defines a SIP Usage for REsource LOcation And Discovery
(RELOAD). The SIP Usage provides the functionality of a SIP proxy or (RELOAD). The SIP Usage provides the functionality of a SIP proxy or
registrar in a fully-distributed system and includes a lookup service registrar in a fully-distributed system and includes a lookup service
for Address of Records (AORs) stored in the overlay. It also defines for Address of Records (AORs) stored in the overlay. It also defines
Globally Routable User Agent Uris (GRUUs) that allow the Globally Routable User Agent Uris (GRUUs) that allow the
registrations to map an AOR to a specific node reachable through the registrations to map an AOR to a specific node reachable through the
overlay. After such initial contact of a peer, the AppAttach method overlay. After such initial contact of a peer, the AppAttach method
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 July 31, 2014. This Internet-Draft will expire on January 22, 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 15, line 48 skipping to change at page 15, line 48
Registrant Contact: The IESG Registrant Contact: The IESG
XML: N/A, the requested URI is an XML namespace XML: N/A, the requested URI is an XML namespace
10. Acknowledgments 10. Acknowledgments
This document was generated in parts from initial drafts and This document was generated in parts from initial drafts and
discussions in the early specification phase of the P2PSIP base discussions in the early specification phase of the P2PSIP base
protocol. Significant contributions (in alphabetical order) were protocol. Significant contributions (in alphabetical order) were
from David A. Bryan, James Deverick, Marcin Matuszewski, Jonathan from David A. Bryan, James Deverick, Marcin Matuszewski, Jonathan
Rosenberg, and Marcia Zangrilli, which is gratefully acknowledged. Rosenberg, and Marcia Zangrilli, which is gratefully acknowledged.
Additional thanks go to all those who helped with ideas, discussions, Additional thanks go to all those who helped with ideas, discussions,
and reviews, in particular (in alphabetical order) Michael Chen, Marc and reviews, in particular (in alphabetical order) Michael Chen, Marc
Petit-Huguenin, Brian Rosen, and Matthias Waehlisch. Petit-Huguenin, Brian Rosen, and Matthias Waehlisch.
11. References 11. References
11.1. Normative References 11.1. Normative References
skipping to change at page 17, line 16 skipping to change at page 17, line 16
"IEEE Standard for Information Technology - Portable "IEEE Standard for Information Technology - Portable
Operating System Interface (POSIX) - Part 2: Shell and Operating System Interface (POSIX) - Part 2: Shell and
Utilities (Vol. 1)", IEEE Std 1003.2-1992, ISBN Utilities (Vol. 1)", IEEE Std 1003.2-1992, ISBN
1-55937-255-9, January 1993. 1-55937-255-9, January 1993.
11.2. Informative References 11.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.
[RFC5767] Munakata, M., Schubert, S., and T. Ohba, "User-Agent- [RFC5767] Munakata, M., Schubert, S., and T. Ohba, "User-Agent-
Driven Privacy Mechanism for SIP", RFC 5767, April 2010. Driven Privacy Mechanism for SIP", RFC 5767, April 2010.
[I-D.ietf-p2psip-share] [I-D.ietf-p2psip-share]
Knauf, A., Schmidt, T., Hege, G., and M. Waehlisch, "A Knauf, A., Schmidt, T., Hege, G., and M. Waehlisch, "A
Usage for Shared Resources in RELOAD (ShaRe)", draft-ietf- Usage for Shared Resources in RELOAD (ShaRe)", draft-ietf-
p2psip-share-02 (work in progress), August 2013. p2psip-share-03 (work in progress), March 2014.
Appendix A. Third Party Registration Appendix A. Third Party Registration
In traditional SIP, the mechanism of a third party registration In traditional SIP, the mechanism of a third party registration
(i.e., an assistant acting for a boss, changing users register a (i.e., an assistant acting for a boss, changing users register a
role-based AOR, ...) is defined in Section 10.2 of [RFC3261]. This role-based AOR, ...) is defined in Section 10.2 of [RFC3261]. This
is a REGISTER which uses the URI of the third-party in its From is a REGISTER which uses the URI of the third-party in its From
header and cannot be translated directly into a P2PSIP registration, header and cannot be translated directly into a P2PSIP registration,
because only the owner of the certificate can store a SIP- because only the owner of the certificate can store a SIP-
REGISTRATION in a RELOAD overlay. REGISTRATION in a RELOAD overlay.
 End of changes. 7 change blocks. 
8 lines changed or deleted 8 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/