--- 1/draft-ietf-p2psip-sip-03.txt 2010-03-09 02:11:00.000000000 +0100 +++ 2/draft-ietf-p2psip-sip-04.txt 2010-03-09 02:11:00.000000000 +0100 @@ -1,79 +1,85 @@ P2PSIP C. Jennings Internet-Draft Cisco Intended status: Standards Track B. Lowekamp, Ed. -Expires: April 25, 2010 MYMIC LLC +Expires: September 9, 2010 MYMIC LLC E. Rescorla Network Resonance S. Baset H. Schulzrinne Columbia University - October 22, 2009 + March 8, 2010 A SIP Usage for RELOAD - draft-ietf-p2psip-sip-03 + draft-ietf-p2psip-sip-04 + +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 + messages are exchanged. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the - provisions of BCP 78 and BCP 79. This document may contain material - from IETF Documents or IETF Contributions published or made publicly - available before November 10, 2008. The person(s) controlling the - copyright in some of this material may not have granted the IETF - Trust the right to allow modifications of such material outside the - IETF Standards Process. Without obtaining an adequate license from - the person(s) controlling the copyright in such materials, this - document may not be modified outside the IETF Standards Process, and - derivative works of it may not be created outside the IETF Standards - Process, except to format it for publication as an RFC or to - translate it into languages other than English. + provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on April 25, 2010. + This Internet-Draft will expire on September 9, 2010. Copyright Notice - Copyright (c) 2009 IETF Trust and the persons identified as the + Copyright (c) 2010 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 in effect on the date of - publication of this document (http://trustee.ietf.org/license-info). - Please review these documents carefully, as they describe your rights - and restrictions with respect to this document. - -Abstract + 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 BSD License. - 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 - messages are exchanged. + This document may contain material from IETF Documents or IETF + Contributions published or made publicly available before November + 10, 2008. The person(s) controlling the copyright in some of this + material may not have granted the IETF Trust the right to allow + modifications of such material outside the IETF Standards Process. + Without obtaining an adequate license from the person(s) controlling + the copyright in such materials, this document may not be modified + outside the IETF Standards Process, and derivative works of it may + not be created outside the IETF Standards Process, except to format + it for publication as an RFC or to translate it into languages other + 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 @@ -340,21 +346,24 @@ Kind IDs The Resource Name for the SIP-REGISTRATION Kind-ID is the AOR of the user. The data stored is a SipRegistrationData, which can contain either another URI or a destination list to the peer which is acting for the user. Data Model The data model for the SIP-REGISTRATION Kind-ID is dictionary. The dictionary key is the Node-ID of the storing peer. This allows each peer (presumably corresponding to a single device) to store a single route mapping. - Access Control USER-NODE-MATCH. + Access Control USER-NODE-MATCH. Note that this matches the SIP AOR + against the rfc822Name in the X509v3 certificate. The rfc822Name + does not include the scheme so that "sip:" prefix needs to be + removed from the SIP AOR before matching. Data stored under the SIP-REGISTRATION kind is of type SipRegistration. This comes in two varieties: sip_registration_uri a URI which the user can be reached at. sip_registration_route a destination list which can be used to reach the user's peer.