Subject: Re: [dispatch] FW: I-D Action:draft-jones-ipmc-session-id-00.txt

From: Cullen Jennings <[email-masked]>
Date: Thu, 13 Jan 2011 19:35:37 -0700

Keeping track of the roster of device on a conference call is not trivial and it needs to be able to dynamically track changes - often pretty fast. We already have ways of doing this with XCON and the conferencing package. I think we would have to think carefully about if we wanted to introduce another way to do that. 

On Nov 29, 2010, at 5:28 AM, Paul E. Jones wrote:

> 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:[email-masked]]
>> Sent: Monday, November 29, 2010 1:39 AM
>> To: Paul E. Jones; [email-masked]
>> Cc: [email-masked]
>> 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: [email-masked] [[email-masked]] On Behalf Of
>> Paul E. Jones [[email-masked]]
>> Sent: Monday, November 29, 2010 12:23 AM
>> To: [email-masked]
>> Cc: [email-masked]
>> 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: [email-masked] [mailto:i-d-announce-
>>> [email-masked]] On Behalf Of [email-masked]
>>> Sent: Sunday, November 28, 2010 5:15 PM
>>> To: [email-masked]
>>> 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
>> [email-masked]
>> https://www.ietf.org/mailman/listinfo/dispatch
> 
> _______________________________________________
> dispatch mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/dispatch