[dispatch] charter proposal: SIP end-to-end Session Identifier
Salvatore Loreto <salvatore.loreto@ericsson.com> Mon, 23 May 2011 06:49 UTC
Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B792E070C for <dispatch@ietfa.amsl.com>; Sun, 22 May 2011 23:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level:
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZdE8DAFR365 for <dispatch@ietfa.amsl.com>; Sun, 22 May 2011 23:49:47 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 1971AE0720 for <dispatch@ietf.org>; Sun, 22 May 2011 23:49:46 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-ca-4dda0389c277
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 32.F3.20773.9830ADD4; Mon, 23 May 2011 08:49:45 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Mon, 23 May 2011 08:49:45 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 01821232B; Mon, 23 May 2011 09:49:44 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id ABB7A50C32; Mon, 23 May 2011 09:49:44 +0300 (EEST)
Received: from n211.nomadiclab.com (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 55B5850A44; Mon, 23 May 2011 09:49:44 +0300 (EEST)
Message-ID: <4DDA0388.60702@ericsson.com>
Date: Mon, 23 May 2011 09:49:44 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: "dispatch@ietf.org" <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="------------010509060602070006050303"
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: AAAAAA==
Subject: [dispatch] charter proposal: SIP end-to-end Session Identifier
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2011 06:49:49 -0000
Hi there, below a charter proposal for a new wg working on End-to-end Session Identifier in SIP. In an effort to make progress and to facilitate the discussion we have also created an Internet Draft that captures, at a high level, the requirements and use cases. (It was submitted by Paul E. Jones last Friday; here the link: http://www.ietf.org/id/draft-jones-ipmc-session-id-reqts-00.txt ) cheers /Sal End-to-end Session Identifier in SIP (charter proposal ) ---------------------------------------------- The end-to-end Session Identifier in an SIP-based multimedia communication refers to the ability for endpoints, intermediate devices, and management and monitoring system to identify and correlate SIP messages and dialogs of the same higher-level end-to-end "communication session" across multiple SIP devices and hops. Unfortunately, there are a number of factors that contribute to the fact that the current dialog identifiers as defined in SIP is not suitable for end-to-end session identification. Perhaps the most important factor worth describing is that in real-world deployments devices like Session Border Controllers (SBC) often change the current call identifiers (e.g., the From-tag and To-tag that are used in conjunction with the Call-ID header to make the dialog-id) as the session signaling passes through. An end-to-end Session Identifier should allow the possibility to identify the communication session from the point of origin, passing through any number of intermediaries, to the ultimate point of termination. It should have the same aim as the From-tag, To-tag and Call-ID conjunction, but should not be mangled by intermediaries. A SIP end-to-end Session Identifier has been consideredas possible solution of different use cases like troubleshooting, billing, session tracking, session recording, media and signaling correlation, and so forth. Some of these requirements have also been identified and come directly from other existing working group within the RAI area (e.g. SIPRec, Splices). Moreover, otherSDOs have identified the need for SIP and H.323 to carry the same "session ID" value(s) so that it is possible identify a call end-to end even when performing inter working between protocols. This group will first focus on adocument that will identify, collect and discuss all the requirements and the use cases that have been identified. The document may identify the possibility to design a general mechanism or the need to design multiple purpose built identifiers. Once the needs are clear and identified, the working group will specify the mechanism(s). Specifically, the proposed working group will develop the following deliverable: 1. A requirement and use case document with key consideration for SIP Session End-to-End identifier. The document will discuss the possibility of designing a general mechanism or the needs to design multiple purpose build identifier. 2. Specification of new mechanism(s). Goal and Milestone: October 2011 - Requirement and use case document sent to the IESG (Information)
- [dispatch] charter proposal: SIP end-to-end Sessi… Salvatore Loreto
- Re: [dispatch] charter proposal: SIP end-to-end S… Simon Pietro Romano
- Re: [dispatch] charter proposal: SIP end-to-end S… Georg Mayer
- Re: [dispatch] charter proposal: SIP end-to-end S… DOLLY, MARTIN C (ATTSI)
- Re: [dispatch] charter proposal: SIP end-to-end S… Christer Holmberg
- Re: [dispatch] charter proposal: SIP end-to-end S… Richard Shockey
- Re: [dispatch] charter proposal: SIP end-to-end S… Peter Musgrave
- Re: [dispatch] charter proposal: SIP end-to-end S… Laura Liess
- Re: [dispatch] charter proposal: SIP end-to-end S… Xavier Marjou
- Re: [dispatch] charter proposal: SIP end-to-end S… R.Jesske
- Re: [dispatch] charter proposal: SIP end-to-end S… Salvatore Loreto