Re: [dispatch] FW: I-D Action:draft-jones-ipmc-session-id-00.txt
Salvatore Loreto <salvatore.loreto@ericsson.com> Mon, 29 November 2010 14:29 UTC
Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 623003A6BC1 for <dispatch@core3.amsl.com>; Mon, 29 Nov 2010 06:29:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level:
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xvy1MJrIW5sK for <dispatch@core3.amsl.com>; Mon, 29 Nov 2010 06:29:18 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 3DE5428C126 for <dispatch@ietf.org>; Mon, 29 Nov 2010 06:29:17 -0800 (PST)
X-AuditID: c1b4fb3d-b7b8cae0000016b1-d0-4cf3b9016217
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id BC.95.05809.109B3FC4; Mon, 29 Nov 2010 15:30:26 +0100 (CET)
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.2.234.1; Mon, 29 Nov 2010 15:30:25 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 4A79B25B5 for <dispatch@ietf.org>; Mon, 29 Nov 2010 16:30:25 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 1159950339 for <dispatch@ietf.org>; Mon, 29 Nov 2010 16:30:25 +0200 (EET)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id BD37B4FE7F for <dispatch@ietf.org>; Mon, 29 Nov 2010 16:30:24 +0200 (EET)
Message-ID: <4CF3B900.8000301@ericsson.com>
Date: Mon, 29 Nov 2010 16:30:24 +0200
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.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: dispatch@ietf.org
References: <20101128221502.13473.41922.idtracker@localhost>, <00e401cb8f4a$e28a56e0$a79f04a0$@packetizer.com> <7F2072F1E0DE894DA4B517B93C6A058502C71899@ESESSCMS0356.eemea.ericsson.se> <018901cb8fc0$eb42fdc0$c1c8f940$@packetizer.com>
In-Reply-To: <018901cb8fc0$eb42fdc0$c1c8f940$@packetizer.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [dispatch] FW: I-D Action:draft-jones-ipmc-session-id-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 29 Nov 2010 14:29:50 -0000
Hi Paul, I find the approach of endpoints exchange of a unique value to form the session-id quite interesting. your description of how to use it in a multipoint conference (section 6) actually can be easily adapted also for disaggregated media scenario described in SPLICES wg and in draft: http://tools.ietf.org/id/draft-loreto-splices-disaggregated-media-00.txt not completly sure that UUID and using Contact to exchange it are the right/safe way to do it. cheers /Sal > Christer, > > Most significantly, the Session-ID is not constructed by one endpoint and > passed to the other. Rather, the Session-ID is formed through the > concatenation of UUIDs provided by both parties. At any time during the > call, an intermediary can redirect the call (which often happens) and a new > session ID is constructed when the transferred party sees that the > session-uuid from the remote end has changed. I believe with Hadriel's, > there is a question lingering as to who assigns the session ID when there > are session transfers, joins, etc. In our draft, there will always be a > unique session ID constructed from UUID components from each device. > > By constructing the Session-ID from two UUIDs, we can also determine which > of several devices are participating in the same multipoint conference. If > A, B, C, and D are all connected to and MCU, M, then all of those devices > would receive the same UUID value from M and would form a part of the > Session-ID used by each device. > > The goal of Hadriel's draft and ours are the same. We even considered using > the same header name, but ultimately decided to place the UUID in the > Contact header. We have not particular attachment to use of UUIDs (versus > any other unique value like a hash). What we think is important is > addressing the issues of who assigns the Session ID and how it evolves when > the session is transferred, joined, etc. and how we can associate devices > participating in multipoint conferences. > > Paul > >> -----Original Message----- >> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] >> Sent: Monday, November 29, 2010 1:39 AM >> To: Paul E. Jones; dispatch@ietf.org >> Cc: cherp@cisco.com >> Subject: RE: [dispatch] FW: I-D Action:draft-jones-ipmc-session-id- >> 00.txt >> >> Hi, >> >> Other than the syntax, what is the difference between this and Hadriel's >> session-id draft (draft-kaplan-dispatch-session-id)? >> >> Regards, >> >> Christer >> >> ________________________________________ >> From: dispatch-bounces@ietf.org [dispatch-bounces@ietf.org] On Behalf Of >> Paul E. Jones [paulej@packetizer.com] >> Sent: Monday, November 29, 2010 12:23 AM >> To: dispatch@ietf.org >> Cc: cherp@cisco.com >> Subject: [dispatch] FW: I-D Action:draft-jones-ipmc-session-id-00.txt >> >> Folks, >> >> I want to bring to your attention this new draft some colleagues and I >> put together to try to address the need for a "session identifier" that >> allows for end-to-end session identification. We also see utility that >> goes beyond just identifying the session end-to-end, as outlined in the >> document. We believe this approach will satisfy those needs and do so >> in a very simple, straight-forward way. Equally important, this >> approach will work with SIP, H.323, and other session signaling >> protocols. >> >> We welcome any feedback you'd like to provide. >> >> Thanks! >> Paul >> >>> -----Original Message----- >>> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce- >>> bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org >>> Sent: Sunday, November 28, 2010 5:15 PM >>> To: i-d-announce@ietf.org >>> Subject: I-D Action:draft-jones-ipmc-session-id-00.txt >>> >>> A New Internet-Draft is available from the on-line Internet-Drafts >>> directories. >>> >>> Title : End-to-End Session Identification in IP-Based >>> Multimedia Communication Networks >>> Author(s) : P. Jones, et al. >>> Filename : draft-jones-ipmc-session-id-00.txt >>> Pages : 8 >>> Date : 2010-11-28 >>> >>> This document describes an end-to-end Session Identifier for use in >>> IP- based Multimedia Communication systems that enables endpoints, >>> intermediate devices, and management systems to identify a session >>> end- to-end, associate multiple endpoints with a given multipoint >>> conference, track communication sessions when they are redirected, and >>> associate one or more media flows with a given communication session. >>> >>> A URL for this Internet-Draft is: >>> http://www.ietf.org/internet-drafts/draft-jones-ipmc-session-id-00.txt >>> >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>> >>> Below is the data which will enable a MIME compliant mail reader >>> implementation to automatically retrieve the ASCII version of the >>> Internet-Draft. >> _______________________________________________ >> dispatch mailing list >> dispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/dispatch > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch >
- [dispatch] FW: I-D Action:draft-jones-ipmc-sessio… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Christer Holmberg
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Hadriel Kaplan
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Peter Musgrave
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Spencer Dawkins
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Roni Even
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul Kyzivat
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Hadriel Kaplan
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Hadriel Kaplan
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Salvatore Loreto
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Elwell, John
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Spencer Dawkins
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Elwell, John
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Parthasarathi R (partr)
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Parthasarathi R (partr)
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Hadriel Kaplan
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Kevin P. Fleming
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Laura Liess
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Laura Liess
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul Kyzivat
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Richard Shockey
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Henry Sinnreich
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Laura Liess
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Worley, Dale R (Dale)
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Paul E. Jones
- Re: [dispatch] FW: I-D Action:draft-jones-ipmc-se… Cullen Jennings