Document Action: 'A Session Identifier for the Session Initiation Protocol (SIP)' to Informational RFC (draft-kaplan-insipid-session-id-04.txt)

The IESG <> Thu, 19 June 2014 17:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9AE9B1A0083 for <>; Thu, 19 Jun 2014 10:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vXVHNwnqyeQF; Thu, 19 Jun 2014 10:54:53 -0700 (PDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 7D1B71A0291; Thu, 19 Jun 2014 10:54:51 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'A Session Identifier for the Session Initiation Protocol (SIP)' to Informational RFC (draft-kaplan-insipid-session-id-04.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.0.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 19 Jun 2014 10:54:51 -0700
Cc: RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 19 Jun 2014 17:54:54 -0000

The IESG has approved the following document:
- 'A Session Identifier for the Session Initiation Protocol (SIP)'
  (draft-kaplan-insipid-session-id-04.txt) as Informational RFC

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Richard Barnes.

A URL of this Internet Draft is:

        Technical Summary:

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 originally proposed a new SIP header
(Session-ID) to carry such a value, which is now being defined by the

        Working Group Summary:

        Was the document considered in any WG, and if so, why was
        it not adopted as a work item there? Was there controversy
        about particular points that caused the WG to not adopt the
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
the work currently being defined in the INSIPID WG.  The INSIPID WG
Session-ID solution replaces the 'legacy' solution presented in
draft-ietf-insipid-session-id-03 and intends to ensure
interoperability and backwards compatibility with such legacy
Session-ID entities.

         Document Quality:
         Are there existing implementations of the protocol? Have a 
         significant number of vendors indicated their plan to 
         implement the specification? Are there any reviewers that 
         merit special mention as having done a thorough review, 
         e.g., one that resulted in important changes or a 
         conclusion that the document had no substantive issues? If 
         there was a MIB Doctor, Media Type or other expert review, 
         what was its course (briefly)? In the case of a Media Type 
         review, on what date was the request posted?

The legacy Session-ID solution described in this document is very
widely deployed, especially by Service Providers providing 3GPP IMS.
The ubiquity of this legacy solution and the requirement that the
current INSIPID WG work be backwards compatible with it is the primary
driver for its publications as an Informational RFC that can be
referenced by the current INSIPID WG documents. This document does not
meet the requirements defined in

         Who is the Document Shepherd? Who is the Responsible Area
Gonzalo Salgueiro (INSIPID WG co-chair) is the Document Shepherd.
Richard Barnes is the Responsible AD.