--- 1/draft-ietf-p2psip-disco-00.txt 2013-07-12 10:14:40.718482951 -0700 +++ 2/draft-ietf-p2psip-disco-01.txt 2013-07-12 10:14:40.794484867 -0700 @@ -1,124 +1,124 @@ Network Working Group A. Knauf -Internet-Draft T C. Schmidt, Ed. +Internet-Draft T. Schmidt, Ed. Intended status: Standards Track HAW Hamburg -Expires: April 12, 2013 G. Hege +Expires: January 13, 2014 G. Hege daviko GmbH M. Waehlisch link-lab & FU Berlin - October 9, 2012 + July 12, 2013 A RELOAD Usage for Distributed Conference Control (DisCo) - draft-ietf-p2psip-disco-00 + draft-ietf-p2psip-disco-01 Abstract This document defines a RELOAD Usage for Distributed Conference Control (DisCo) with SIP. DisCo preserves conference addressing through a single SIP URI by splitting its semantic of identifier and locator using a new Kind data structure. Conference members are enabled to select conference controllers based on proximity awareness and to recover from failures of individual resource instances. DisCo proposes call delegation to balance the load at focus peers. -Status of this Memo +Status of This Memo This Internet-Draft is submitted 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 April 12, 2013. + This Internet-Draft will expire on January 13, 2014. Copyright Notice - Copyright (c) 2012 IETF Trust and the persons identified as the + 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. Table of Contents - 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 3. Overview of DisCo . . . . . . . . . . . . . . . . . . . . . . 6 - 3.1. Reference Scenario . . . . . . . . . . . . . . . . . . . . 6 - 3.2. Initiating a Distributed Conference . . . . . . . . . . . 7 - 3.3. Joining a Conference . . . . . . . . . . . . . . . . . . . 8 - 3.4. Conference State Synchronization . . . . . . . . . . . . . 9 - 3.5. Call delegation . . . . . . . . . . . . . . . . . . . . . 10 - 3.6. Resilience . . . . . . . . . . . . . . . . . . . . . . . . 10 - 3.7. Topology Awareness . . . . . . . . . . . . . . . . . . . . 10 - 4. RELOAD Usage for Distributed Conference Control . . . . . . . 11 - 4.1. Shared Resource DisCo-Registration . . . . . . . . . . . . 11 - 4.2. Kind Data Structure . . . . . . . . . . . . . . . . . . . 11 - 4.3. Variable Conference Identifier . . . . . . . . . . . . . . 12 - 4.4. Conference Creation . . . . . . . . . . . . . . . . . . . 12 - 4.5. Advertising Focus Ability . . . . . . . . . . . . . . . . 13 - 4.6. Determining Coordinates . . . . . . . . . . . . . . . . . 14 - 4.7. Proximity-aware Conference Participation . . . . . . . . . 14 - 4.8. Configuration Document Extension . . . . . . . . . . . . . 16 - 5. Conference State Synchronization . . . . . . . . . . . . . . . 18 - 5.1. Event Package Overview . . . . . . . . . . . . . . . . . . 18 - 5.2. . . . . . . . . . . . . . . . . . 20 - 5.3. / . . . . . . . . . . . . . . . . 20 - 5.4. . . . . . . . . . . . . . . . . . 21 - 5.5. . . . . . . . . . . . . . . . . . . . . . . . . . 22 - 5.5.1. . . . . . . . . . . . . . . . . . . . . 23 - 5.5.2. / . . . . . . . . . . . . . . . . . . . . 23 - 5.5.3. / . . . . . . . . . . . . . . . . 24 - 5.6. Distribution of Change Events . . . . . . . . . . . . . . 24 - 5.7. Translation to Conference-Info Event Package . . . . . . . 25 - 5.7.1. . . . . . . . . . . . . . . . . . . 26 - 5.7.2. . . . . . . . . . . . . . . . 26 - 5.7.3. . . . . . . . . . . . . . . . . . . . . . 26 - 5.7.4. . . . . . . . . . . . . . . . . . . 26 - 5.7.5. / . . . . . . . . . . . . . . . . . . . . 27 - 5.7.6. / . . . . . . . . 27 - 6. Distributed Conference Control with SIP . . . . . . . . . . . 28 - 6.1. Call delegation . . . . . . . . . . . . . . . . . . . . . 28 - 6.2. Conference Access . . . . . . . . . . . . . . . . . . . . 29 - 6.3. Media Negotiation and Distribution . . . . . . . . . . . . 30 - 6.3.1. Offer/Answer . . . . . . . . . . . . . . . . . . . . . 30 - 6.3.2. New Peers Joining . . . . . . . . . . . . . . . . . . 31 - 6.4. Restructuring a Conference . . . . . . . . . . . . . . . . 31 - 6.4.1. On Graceful Leave . . . . . . . . . . . . . . . . . . 31 - 6.4.2. On Unexpected Leave . . . . . . . . . . . . . . . . . 32 - 7. DisCo Kind Definition . . . . . . . . . . . . . . . . . . . . 33 - 8. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 34 - 9. Relax NG Grammar . . . . . . . . . . . . . . . . . . . . . . . 38 - 10. Security Considerations . . . . . . . . . . . . . . . . . . . 39 - 10.1. Trust Aspects . . . . . . . . . . . . . . . . . . . . . . 39 - 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 - 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 41 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 42 - 13.1. Normative References . . . . . . . . . . . . . . . . . . . 42 - 13.2. Informative References . . . . . . . . . . . . . . . . . . 43 - Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 44 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 46 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 + 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 3. Overview of DisCo . . . . . . . . . . . . . . . . . . . . . . 4 + 3.1. Reference Scenario . . . . . . . . . . . . . . . . . . . 4 + 3.2. Initiating a Distributed Conference . . . . . . . . . . . 6 + 3.3. Joining a Conference . . . . . . . . . . . . . . . . . . 6 + 3.4. Conference State Synchronization . . . . . . . . . . . . 7 + 3.5. Call delegation . . . . . . . . . . . . . . . . . . . . . 8 + 3.6. Resilience . . . . . . . . . . . . . . . . . . . . . . . 8 + 3.7. Topology Awareness . . . . . . . . . . . . . . . . . . . 8 + 4. RELOAD Usage for Distributed Conference Control . . . . . . . 8 + 4.1. Shared Resource DisCo-Registration . . . . . . . . . . . 9 + 4.2. Kind Data Structure . . . . . . . . . . . . . . . . . . . 9 + 4.3. Variable Conference Identifier . . . . . . . . . . . . . 10 + 4.4. Conference Creation . . . . . . . . . . . . . . . . . . . 10 + 4.5. Advertising Focus Ability . . . . . . . . . . . . . . . . 11 + 4.6. Determining Coordinates . . . . . . . . . . . . . . . . . 12 + 4.7. Proximity-aware Conference Participation . . . . . . . . 12 + 4.8. Configuration Document Extension . . . . . . . . . . . . 14 + 5. Conference State Synchronization . . . . . . . . . . . . . . 15 + 5.1. Event Package Overview . . . . . . . . . . . . . . . . . 15 + 5.2. . . . . . . . . . . . . . . . . 16 + 5.3. / . . . . . . . . . . . . . . . 17 + 5.4. . . . . . . . . . . . . . . . . 18 + 5.5. . . . . . . . . . . . . . . . . . . . . . . . . . 18 + 5.5.1. . . . . . . . . . . . . . . . . . . . . 19 + 5.5.2. / . . . . . . . . . . . . . . . . . . . 20 + 5.5.3. / . . . . . . . . . . . . . . . 20 + 5.6. Distribution of Change Events . . . . . . . . . . . . . . 21 + 5.7. Translation to Conference-Info Event Package . . . . . . 22 + 5.7.1. . . . . . . . . . . . . . . . . . . 22 + 5.7.2. . . . . . . . . . . . . . . 23 + 5.7.3. . . . . . . . . . . . . . . . . . . . . . 23 + 5.7.4. . . . . . . . . . . . . . . . . . 23 + 5.7.5. / . . . . . . . . . . . . . . . . . . . 24 + 5.7.6. / . . . . . . . . 24 + 6. Distributed Conference Control with SIP . . . . . . . . . . . 24 + 6.1. Call delegation . . . . . . . . . . . . . . . . . . . . . 24 + 6.2. Conference Access . . . . . . . . . . . . . . . . . . . . 26 + 6.3. Media Negotiation and Distribution . . . . . . . . . . . 26 + 6.3.1. Offer/Answer . . . . . . . . . . . . . . . . . . . . 26 + 6.3.2. New Peers Joining . . . . . . . . . . . . . . . . . . 27 + 6.4. Restructuring a Conference . . . . . . . . . . . . . . . 27 + 6.4.1. On Graceful Leave . . . . . . . . . . . . . . . . . . 27 + 6.4.2. On Unexpected Leave . . . . . . . . . . . . . . . . . 28 + 7. DisCo Kind Definition . . . . . . . . . . . . . . . . . . . . 28 + 8. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 29 + 9. Relax NG Grammar . . . . . . . . . . . . . . . . . . . . . . 32 + 10. Security Considerations . . . . . . . . . . . . . . . . . . . 33 + 10.1. Trust Aspects . . . . . . . . . . . . . . . . . . . . . 33 + 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 + 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 + 13.1. Normative References . . . . . . . . . . . . . . . . . . 33 + 13.2. Informative References . . . . . . . . . . . . . . . . . 34 + Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 35 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 1. Introduction This document describes a RELOAD Usage for distributed conference control (DisCo) in a tightly coupled model with SIP [RFC3261]. The Usage provides self-organizing and scalable signaling that allows RELOAD peers, clients and plain SIP user agents to participate in a managed P2P conference. DisCo defines the following functions: o A SIP protocol scheme for distributed conference control @@ -1042,44 +1041,43 @@ events of remote focus peer. 5.7.2. The element exists in both event packages, conference-info and distributed-conference. Thus, the following elements are seamlessly translatable: , , , and . The sub elements , and in conference-info have there counterparts below the - \focus\focus-state element of the distributed-conference event - package. Each describes a local state of a focus peer in the - conference. Hence, the intersection of every disco., - disco. and the sum over each disco. element of each disco. element in distributed- - conference, specifies the content of the corresponding conference- - info elements. + media> in conference-info have there counterparts below the \focus + \focus-state element of the distributed-conference event package. + Each describes a local state of a focus peer in the conference. + Hence, the intersection of every disco., disco. and the sum over each disco. element of + each disco. element in distributed-conference, specifies the + content of the corresponding conference-info elements. 5.7.3. According to [RFC4575] the ci. element contains information about the entity hosting the conference. For participants in a distributed conference, the hosting entity is their focus peer. Thus, the ci. element contains information about a focus peer. 5.7.4. The ci. element allows subscribers obtain - information about overall state of a conference. Its sub elements - ci., ci. and ci. are reused as sub - elements of \focus\focus-state to describe the local state of a focus - peer in a distributed conference. The translation rules from the + information about overall state of a conference. Its sub elements ci + ., ci. and ci. are reused as sub elements + of \focus\focus-state to describe the local state of a focus peer in + a distributed conference. The translation rules from the distributed-conference to the conference-info event package are the following: : The sum over each value of the disco. element defines the corresponding ci.. : The boolean ci. element is the logical concatenation over all disco. elements by an OR-operator. The boolean ci. element is the logical @@ -1489,38 +1486,42 @@ + Figure 7 + 9. Relax NG Grammar The grammar for the Landmark configuration document extension is: parameter &= element landmarks { attribute version { xsd:int } element landmark-host { attribute address { xsd:string }, attribute port { xsd:int } }* }? + Figure 8 + 10. Security Considerations 10.1. Trust Aspects TODO 11. IANA Considerations TODO: register Kind-ID code point at the IANA @@ -1533,118 +1534,118 @@ David Bryan, Toerless Eckert, Lothar Grimm, Cullen Jennings, Peter Musgrave, Joerg Ott, Peter Pogrzeba, Brian Rosen, and Jan Seedorf. 13. References 13.1. Normative References [I-D.ietf-p2psip-base] Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., and H. Schulzrinne, "REsource LOcation And Discovery (RELOAD) - Base Protocol", draft-ietf-p2psip-base-22 (work in - progress), July 2012. + Base Protocol", draft-ietf-p2psip-base-26 (work in + progress), February 2013. [I-D.knauf-p2psip-share] Knauf, A., Hege, G., Schmidt, T., and M. Waehlisch, "A - Usage for Shared Resources in RELOAD (ShaRe)", - draft-knauf-p2psip-share-03 (work in progress), - April 2012. + Usage for Shared Resources in RELOAD (ShaRe)", draft- + knauf-p2psip-share-03 (work in progress), April 2012. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002. [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model - with Session Description Protocol (SDP)", RFC 3264, - June 2002. + with Session Description Protocol (SDP)", RFC 3264, June + 2002. [RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific Event Notification", RFC 3265, June 2002. [RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer Method", RFC 3515, April 2003. [RFC4574] Levin, O. and G. Camarillo, "The Session Description Protocol (SDP) Label Attribute", RFC 4574, August 2006. [RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session Initiation Protocol (SIP) Event Package for Conference State", RFC 4575, August 2006. [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006. [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) - Traversal for Offer/Answer Protocols", RFC 5245, - April 2010. + Traversal for Offer/Answer Protocols", RFC 5245, April + 2010. 13.2. Informative References [I-D.ietf-p2psip-concepts] Bryan, D., Willis, D., Shim, E., Matthews, P., and S. Dawkins, "Concepts and Terminology for Peer to Peer SIP", - draft-ietf-p2psip-concepts-04 (work in progress), - October 2011. + draft-ietf-p2psip-concepts-04 (work in progress), October + 2011. [I-D.ietf-p2psip-sip] - Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., and - H. Schulzrinne, "A SIP Usage for RELOAD", - draft-ietf-p2psip-sip-07 (work in progress), January 2012. + Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., + Schulzrinne, H., and T. Schmidt, "A SIP Usage for RELOAD", + draft-ietf-p2psip-sip-09 (work in progress), February + 2013. [RFC4353] Rosenberg, J., "A Framework for Conferencing with the - Session Initiation Protocol (SIP)", RFC 4353, - February 2006. + Session Initiation Protocol (SIP)", RFC 4353, February + 2006. [landmarks-infocomm02] - Ratnasamy, Handley, Karp, and Shenker, "Topologically- - Aware Overlay Construction and Server Selection", Proc. of - 21st Annual Joint Conference of the IEEE Computer and - Communications Societies (INFOCOM '02) pp. 1190-1199, - 2002. + Ratnasamy, ., Handley, ., Karp, ., and . Shenker, + "Topologically-Aware Overlay Construction and Server + Selection", Proc. of 21st Annual Joint Conference of the + IEEE Computer and Communications Societies (INFOCOM '02) + pp. 1190-1199, 2002. [timestamps-acsc88] Fidge, C., "Timestamps in Message-Passing Systems that Preserve the Partial Ordering", Proceedings of 11th Australian Computer Science Conference, pp. 56-66, February 1988. Appendix A. Change Log - The following changes have been made from version - draft-knauf-p2psip-disco-04. + The following changes have been made from version draft-knauf-p2psip- + disco-04. 1. Editorial improvements. 2. Updated references. - The following changes have been made from version - draft-knauf-p2psip-disco-03. + The following changes have been made from version draft-knauf-p2psip- + disco-03. 1. Adapted mechanisms for storing DisCo-Registrations to new requirements of Shared Resources draft [I-D.knauf-p2psip-share] - The following changes have been made from version - draft-knauf-p2psip-disco-02. + The following changes have been made from version draft-knauf-p2psip- + disco-02. 1. DisCo-Registration uses now only the USER-CHAIN-ACL access control policy. 2. Adapted mechanisms for storing DisCo-Registrations to new requirements of Shared Resources draft [I-D.knauf-p2psip-share] - The following changes have been made from version - draft-knauf-p2psip-disco-01. + The following changes have been made from version draft-knauf-p2psip- + disco-01. 1. The conference registration is now based on the Shared Resources draft [I-D.knauf-p2psip-share]: * DisCo-Registration Kind now meets the requirements for ShaRe. * Conference creation procedure now uses the ShaRe Access List. * Replaced USER-CHAIN-MATCH access policy for DisCo- Registration. Now uses USER-CHAIN-ACL or USER-PATTERN-MATCH. @@ -1655,22 +1656,22 @@ element. 4. Added a 'node-id' attribute to the event package XML element. 5. Added a 'coordinate' child element to the event package XML element. 6. Corrected typos/wording - The following changes have been made from version - draft-knauf-p2psip-disco-00. + The following changes have been made from version draft-knauf-p2psip- + disco-00. 1. Updated references. 2. Corrected typos. 3. New Section: Conference State Synchronization 4. XML Event Package for Distributed Conferences 5. New mechanism for generating chained conference certificates @@ -1685,39 +1686,36 @@ Authors' Addresses Alexander Knauf HAW Hamburg Berliner Tor 7 Hamburg D-20099 Germany Phone: +4940428758067 Email: alexanderknauf@gmail.com - URI: Thomas C. Schmidt HAW Hamburg Berliner Tor 7 Hamburg D-20099 Germany Email: schmidt@informatik.haw-hamburg.de URI: http://inet.cpt.haw-hamburg.de/members/schmidt - Gabriel Hege daviko GmbH Am Borsigturm 50 Berlin D-13507 Germany Phone: +493043004344 Email: hege@daviko.com - URI: Matthias Waehlisch link-lab & FU Berlin Hoenower Str. 35 Berlin D-10318 Germany Email: mw@link-lab.net URI: http://www.inf.fu-berlin.de/~waehl