A Session Identifier for the Session Initiation Protocol (SIP)
draft-kaplan-insipid-session-id-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rai area)
Last updated 2013-10-30 (latest revision 2013-08-02)
Replaces draft-kaplan-dispatch-session-id
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state (None)
Consensus No
Document shepherd Gonzalo Salgueiro
Shepherd write-up Show (last changed 2013-08-02)
IESG IESG state Waiting for AD Go-Ahead::Revised I-D Needed
Telechat date
Responsible AD Richard Barnes
Send notices to hadriel.kaplan@oracle.com, draft-kaplan-insipid-session-id@tools.ietf.org, insipid-chairs@tools.ietf.org
IANA IANA review state IANA - Not OK
IANA action state None
INSIPID Working Group                                         H. Kaplan 
Internet Draft                                                   Oracle 
Intended status: Informational                                          
Expires: February 2, 2014                                August 2, 2013 
    
    
      A Session Identifier for the Session Initiation Protocol (SIP) 
                    draft-kaplan-insipid-session-id-03 
    
Abstract 
    
   This RFC, which contains the text of an individual Internet Draft 
   that was submitted originally to the DISPATCH Working Group, is 
   being published now as an Informational document to provide a 
   reference for later RFCs.  The mechanism defined in this document 
   has been widely deployed, and is being followed in a backward-
   compatible fashion for a new Standards Track RFC in the INSIPID 
   Working Group.  The original Abstract follows. 
    
   There is a need for having a globally unique session identifier for 
   the same SIP session, which can be consistently maintained across 
   Proxies, B2BUAs and other SIP middle-boxes, for the purpose of 
   Troubleshooting.  This draft proposes a new SIP header to carry such 
   a value: Session-ID. 
    
Status of this Memo 
    
   This document is not an Internet Standards Track specification; it 
   is published for the historical record. 
    
   This Internet-Draft is submitted to IETF in full conformance with 
   the 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. 
 

 
 
Kaplan                 Expires February 2, 2014               [Page 1] 

Internet-Draft          SIP Session Identifier             August 2013 
 
 
   This Internet-Draft will expire on February 2, 2014.  
    
Copyright and License Notice 
    
   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..................................................3 
      1.1. Requirements.............................................4 
   2. Terminology...................................................4 
   3. Overview of Operation.........................................4 
   4. Session-ID Behavior...........................................5 
      4.1. Generating a Session-ID value............................5 
      4.2. UAC Behavior.............................................6 
      4.3. UAS Behavior.............................................6 
      4.4. Proxy Behavior...........................................6 
      4.5. B2BUA Behavior...........................................7 
         4.5.1 B2BUA Generation of New Session-ID  7 
         4.5.2 B2BUA Insertion of Saved Session-ID 8 
   5. Handling SIP Transfer Scenarios...............................8 
      5.1. Out-of-Dialog REFER......................................9 
      5.2. Refer-To URI.............................................9 
      5.3. Out-of-Dialog INVITE with Replaces.......................9 
   6. Session-ID Migration and Failure Scenarios...................10 
   7. New 'Session-ID' Header......................................10 
      7.1. Augmented BNF Definitions...............................10 
   8. Example Exchange.............................................11 
   9. Security Considerations......................................11 
      9.1. Security considerations for administrators..............11 
      9.2. Security considerations for Session-ID extensions.......11 
   10. IANA Considerations.........................................12 
   11. Acknowledgments.............................................12 
   12. References..................................................13 
Show full document text