draft-ietf-p2psip-sip-15.txt   draft-ietf-p2psip-sip-16.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: January 5, 2016 Skype Expires: July 3, 2016 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
July 4, 2015 December 31, 2015
A SIP Usage for RELOAD A SIP Usage for RELOAD
draft-ietf-p2psip-sip-15 draft-ietf-p2psip-sip-16
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 January 5, 2016. This Internet-Draft will expire on July 3, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 3, line 14 skipping to change at page 3, line 14
8.2.2. Malicious Retargeting . . . . . . . . . . . . . . . . 14 8.2.2. Malicious Retargeting . . . . . . . . . . . . . . . . 14
8.2.3. Misuse of AORs . . . . . . . . . . . . . . . . . . . 15 8.2.3. Misuse of AORs . . . . . . . . . . . . . . . . . . . 15
8.2.4. Privacy Issues . . . . . . . . . . . . . . . . . . . 15 8.2.4. Privacy Issues . . . . . . . . . . . . . . . . . . . 15
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
9.1. Data Kind-ID . . . . . . . . . . . . . . . . . . . . . . 15 9.1. Data Kind-ID . . . . . . . . . . . . . . . . . . . . . . 15
9.2. XML Name Space Registration . . . . . . . . . . . . . . . 15 9.2. XML Name Space Registration . . . . . . . . . . . . . . . 15
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
11.1. Normative References . . . . . . . . . . . . . . . . . . 16 11.1. Normative References . . . . . . . . . . . . . . . . . . 16
11.2. Informative References . . . . . . . . . . . . . . . . . 17 11.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Third Party Registration . . . . . . . . . . . . . . 17 Appendix A. Third Party Registration . . . . . . . . . . . . . . 18
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 18 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 18
B.1. Changes since draft-ietf-p2psip-sip-09 . . . . . . . . . 18 B.1. Changes since draft-ietf-p2psip-sip-09 . . . . . . . . . 18
B.2. Changes since draft-ietf-p2psip-sip-08 . . . . . . . . . 18 B.2. Changes since draft-ietf-p2psip-sip-08 . . . . . . . . . 18
B.3. Changes since draft-ietf-p2psip-sip-07 . . . . . . . . . 18 B.3. Changes since draft-ietf-p2psip-sip-07 . . . . . . . . . 18
B.4. Changes since draft-ietf-p2psip-sip-06 . . . . . . . . . 19 B.4. Changes since draft-ietf-p2psip-sip-06 . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
The REsource LOcation And Discovery (RELOAD) [RFC6940] specifies a The REsource LOcation And Discovery (RELOAD) [RFC6940] specifies a
skipping to change at page 16, line 28 skipping to change at page 16, line 28
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) Roland Bless, and reviews, in particular (in alphabetical order) Roland Bless,
Michael Chen, Marc Petit-Huguenin, Brian Rosen, and Matthias Michael Chen, Marc Petit-Huguenin, Brian Rosen, and Matthias
Waehlisch. Waehlisch.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC6940] Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., and [RFC6940] Jennings, C., Lowekamp, B., Ed., Rescorla, E., Baset, S.,
H. Schulzrinne, "REsource LOcation And Discovery (RELOAD) and H. Schulzrinne, "REsource LOcation And Discovery
Base Protocol", RFC 6940, January 2014. (RELOAD) Base Protocol", RFC 6940, DOI 10.17487/RFC6940,
January 2014, <http://www.rfc-editor.org/info/rfc6940>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>.
[RFC2533] Klyne, G., "A Syntax for Describing Media Feature Sets", [RFC2533] Klyne, G., "A Syntax for Describing Media Feature Sets",
RFC 2533, March 1999. RFC 2533, DOI 10.17487/RFC2533, March 1999,
<http://www.rfc-editor.org/info/rfc2533>.
[RFC2738] Klyne, G., "Corrections to "A Syntax for Describing Media [RFC2738] Klyne, G., "Corrections to "A Syntax for Describing Media
Feature Sets"", RFC 2738, December 1999. Feature Sets"", RFC 2738, DOI 10.17487/RFC2738, December
1999, <http://www.rfc-editor.org/info/rfc2738>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) (ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245, April Traversal for Offer/Answer Protocols", RFC 5245,
2010. DOI 10.17487/RFC5245, April 2010,
<http://www.rfc-editor.org/info/rfc5245>.
[RFC5626] Jennings, C., Mahy, R., and F. Audet, "Managing Client- [RFC5626] Jennings, C., Ed., Mahy, R., Ed., and F. Audet, Ed.,
Initiated Connections in the Session Initiation Protocol "Managing Client-Initiated Connections in the Session
(SIP)", RFC 5626, October 2009. Initiation Protocol (SIP)", RFC 5626,
DOI 10.17487/RFC5626, October 2009,
<http://www.rfc-editor.org/info/rfc5626>.
[RFC5627] Rosenberg, J., "Obtaining and Using Globally Routable User [RFC5627] Rosenberg, J., "Obtaining and Using Globally Routable User
Agent URIs (GRUUs) in the Session Initiation Protocol Agent URIs (GRUUs) in the Session Initiation Protocol
(SIP)", RFC 5627, October 2009. (SIP)", RFC 5627, DOI 10.17487/RFC5627, October 2009,
<http://www.rfc-editor.org/info/rfc5627>.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, October 2006. Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,
<http://www.rfc-editor.org/info/rfc4648>.
[IEEE-Posix] [IEEE-Posix]
"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-07 (work in progress), May draft-ietf-p2psip-concepts-07 (work in progress), May
2015. 2015.
[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,
DOI 10.17487/RFC5767, April 2010,
<http://www.rfc-editor.org/info/rfc5767>.
[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-06 (work in progress), June 2015. p2psip-share-07 (work in progress), November 2015.
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. 17 change blocks. 
22 lines changed or deleted 36 lines changed or added

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