--- 1/draft-ietf-p2psip-sip-06.txt 2012-01-18 04:14:35.206671492 +0100 +++ 2/draft-ietf-p2psip-sip-07.txt 2012-01-18 04:14:35.230670973 +0100 @@ -1,24 +1,24 @@ P2PSIP C. Jennings Internet-Draft Cisco Intended status: Standards Track B. Lowekamp, Ed. -Expires: January 8, 2012 Skype +Expires: July 20, 2012 Skype E. Rescorla RTFM, Inc. S. Baset H. Schulzrinne Columbia University - July 7, 2011 + January 17, 2012 A SIP Usage for RELOAD - draft-ietf-p2psip-sip-06 + draft-ietf-p2psip-sip-07 Abstract This document defines a SIP Usage for REsource LOcation And Discovery (RELOAD), The SIP Usage provides the functionality of a SIP proxy or registrar in a fully-distributed system. The SIP Usage provides lookup service for AoRs stored in the overlay. The SIP Usage also defines GRUUs that allow the registrations to map an AoR to a specific node reachable through the overlay. The AppAttach method is used to establish a direct connection between nodes through which SIP @@ -32,25 +32,25 @@ 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 January 8, 2012. + This Internet-Draft will expire on July 20, 2012. Copyright Notice - Copyright (c) 2011 IETF Trust and the persons identified as the + Copyright (c) 2012 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 @@ -69,34 +69,34 @@ than English. Table of Contents 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Registering AORs . . . . . . . . . . . . . . . . . . . . . . . 6 4. Looking up an AOR . . . . . . . . . . . . . . . . . . . . . . 8 5. Forming a Direct Connection . . . . . . . . . . . . . . . . . 9 6. GRUUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 7. SIP-REGISTRATION Kind Definition . . . . . . . . . . . . . . . 9 + 7. SIP-REGISTRATION Kind Definition . . . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 10 8.2. SIP-Specific Issues . . . . . . . . . . . . . . . . . . . 10 8.2.1. Fork Explosion . . . . . . . . . . . . . . . . . . . . 10 8.2.2. Malicious Retargeting . . . . . . . . . . . . . . . . 11 8.2.3. Privacy Issues . . . . . . . . . . . . . . . . . . . . 11 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11.1. Normative References . . . . . . . . . . . . . . . . . . . 11 11.2. Informative References . . . . . . . . . . . . . . . . . . 12 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 12 - A.1. Changes since draft-ietf-p2psip-reload-00 . . . . . . . . 12 + A.1. Changes since draft-ietf-p2psip-sip-06 . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 1. Overview The SIP Usage of RELOAD allows SIP user agents to provide a peer-to- peer telephony service without the requirement for permanent proxy or registration servers. In such a network, the RELOAD overlay itself performs the registration and rendezvous functions ordinarily associated with such servers. @@ -295,20 +295,23 @@ dictionary keys, so that it will fetch all the stored values. 3. If any of the results of the Fetch are non-GRUU AORs, then repeat step 1 for that AOR. 4. Once only GRUUs and destination lists remain, the peer removes duplicate destination lists and GRUUs from the list and forms a SIP connection to the appropriate peers as described in the following sections. If there are also external AORs, the peer follows the appropriate procedure for contacting them as well. + Open Issue: Does the RHS of the AORs stored ina given overlay have + to match the overlay name? + 5. Forming a Direct Connection Once the peer has translated the AOR into a set of destination lists, it then uses the overlay to route AppAttach messages to each of those peers. The "application" field MUST be 5060 to indicate SIP. If certificate-based authentication is in use, the responding peer MUST present a certificate with a Node-ID matching the terminal entry in the route list. Note that it is possible that the peers already have a RELOAD connection between them. This MUST NOT be used for SIP messages. However, if a SIP connection already exists, that MAY be @@ -422,36 +425,36 @@ 11. References 11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [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-16 (work in - progress), July 2011. + Base Protocol", draft-ietf-p2psip-base-19 (work in + progress), October 2011. 11.2. Informative References [I-D.ietf-p2psip-concepts] Bryan, D., Matthews, P., Shim, E., Willis, D., and S. Dawkins, "Concepts and Terminology for Peer to Peer SIP", - draft-ietf-p2psip-concepts-03 (work in progress), - October 2010. + draft-ietf-p2psip-concepts-04 (work in progress), + October 2011. Appendix A. Change Log -A.1. Changes since draft-ietf-p2psip-reload-00 +A.1. Changes since draft-ietf-p2psip-sip-06 - o Split SIP Usage from combined draft into new draft. + o Added Open Issue Authors' Addresses Cullen Jennings Cisco 170 West Tasman Drive MS: SJC-21/2 San Jose, CA 95134 USA