Re: draft-kaplan-sip-session-id-00.txt

I use the word "match" because the property of "matching" is what I mean.  "A" does have to equal "B" symmetrically, but the thing that is symmetric is the Session-ID ("A" and "B" are Session-IDs).
The "Reference" portion is to the general concept of a SIP session (or "dialog-set if you prefer), not the specific dialog leg defined by a call-id+tag set, so you could say a Session-ID is a reference to a collection of dialog legs.
The Session-ID alone does NOT really reference a specific call-id+tag set, for example.
For some cases that's all you need to match to get an action/property you desire, for example for correlating SIP messages in a wireshark trace.
In other cases you need to match both a Session-ID and a remote-tag, in order to "reference" a specific dialog leg - for example in a Replaces case.

-hadriel


> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Dale
> Worley
> Sent: Wednesday, December 03, 2008 12:29 PM
> To: SIP
> Subject: [Sip] draft-kaplan-sip-session-id-00.txt
>
> I'm getting a bit confused by this discussion, and I think part of the
> problem is terminology:
>
> Let's avoid using the word "match" unless we mean a process which has
> the usual properties of "match":  (1) If A matches B, then B matches A.
> (2) If A matches B, then A and B are considered to some degree to be the
> same thing.  Thus, if two requests have the same Via branch parameters,
> they "match" because they are (should be) identical.  And if two
> requests have the same call-id and tags, then they "match" because they
> are part of the same dialog.  (And that relationship is symmetric.)
>
> I think what people want is the concept "references".  If A references
> B, then B does not necessarily reference A.  Thus, a dialog event
> package references a dialog, but the dialog does not reference the
> dialog event package.
>
> I believe that we intend for two message to have the same Session-Id if
> and only if they are legs of the same dialog (in the sense that each leg
> was generated by a B2BUA as a continuation of another leg).  (Actually,
> that should be "dialog set", as created by one out-of-dialog request.)
>
> Dale
>
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [email protected] for questions on current sip
> Use [email protected] for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip