Hi Sal, What I want is that the dialog correlation method also also works without end devices contribution (for non-compliant end devices). Hadriel's Session-ID ( 5.5.1) fulfills this requirement. REQ3 doesn't cover this issue. Laura > -----Original Message----- > From: Salvatore Loreto [mailto:salvatore.loreto@xxxxxxxxxxxx] > Sent: Tuesday, March 10, 2009 1:59 PM > To: Liess, Laura > Cc: sipping@xxxxxxxx > Subject: Re: I-D > Action:draft-loreto-sipping-context-id-requirements-02.txt > > Hi Laura, > > the draft already contains in the section "4.3 Common > requirements" the > following one: > > REQ3 UAs that do not implement the correlation mechanism > and, thus, > do not understand the correlation information they > received should > be able to handle the individual SIP dialogs that were > supposed to > be correlated as well as possible. That is, the correlation > mechanism should not keep them from trying to handle the SIP > dialogs. > > > I don't know if it enough for your case, please let me know if this > requirement fulfils yours or not. > > best regards > Sal > > L.Liess@xxxxxxxxxx wrote: > > > > > > Sal, > > > > I would like to see a second requirement for the dialog correlation, > > which ensures that upgrading network elements is enough to > enable dialog > > correlation also for end devices which were not ungraded. > E.g. "Dialog > > correlation must be possible also if end devices were not > upgraded." > > > > Regards > > Laura > > > > > >>> > >>> > >>>> -----Original Message----- > >>>> From: i-d-announce-bounces@xxxxxxxx > >>>> [mailto:i-d-announce-bounces@xxxxxxxx] On Behalf Of > >>>> Internet-Drafts@xxxxxxxx > >>>> Sent: 06 March 2009 07:15 > >>>> To: i-d-announce@xxxxxxxx > >>>> Subject: I-D > >>>> Action:draft-loreto-sipping-context-id-requirements-02.txt > >>>> > >>>> A New Internet-Draft is available from the on-line > >>>> Internet-Drafts directories. > >>>> > >>>> Title : Requirements for Dialog Correlation > >>>> in the Session Initiation Protocol (SIP) > >>>> Author(s) : G. Camarillo, S. Loreto > >>>> Filename : > >>>> draft-loreto-sipping-context-id-requirements-02.txt > >>>> Pages : 10 > >>>> Date : 2009-03-05 > >>>> > >>>> This document justifies the need and lists the requirements for > >>>> correlating SIP (Session Initiation Protocol) dialogs. The > >>>> correlated dialogs may or may not be related to the same > multimedia > >>>> session. Being able to logically correlate multiple SIP > dialogs is > >>>> useful for applications that, for different reasons, need to > >>>> establish several SIP dialogs to provide a given service. The > >>>> logical correlation of two SIP dialogs is also useful, for > >>>> > >> instance, > >> > >>>> to correlate an incoming with an outgoing dialog at a B2BUA. > >>>> > >>>> A URL for this Internet-Draft is: > >>>> http://www.ietf.org/internet-drafts/draft-loreto-sipping-conte > >>>> xt-id-requirements-02.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. > >>>> > >>>> > >>>> > >>> _______________________________________________ > >>> Sipping mailing list > https://www.ietf.org/mailman/listinfo/sipping > >>> This list is for NEW development of the application of SIP > >>> Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip > >>> Use sip@xxxxxxxx for new developments of core SIP > >>> > >>> > >>> > >> _______________________________________________ > >> Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping > >> This list is for NEW development of the application of SIP > >> Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip > >> Use sip@xxxxxxxx for new developments of core SIP > >> > >> > > > > > > _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
