[Standards-JIG] Jingle: tracking stanzas
ogorman at gmail.com
Tue Feb 14 22:50:49 UTC 2006
thats what i had reccommended before, however joe is right, that one should
respond correctly with the right id that you sent out, and if the other end
does not you shouldnt regard it as accepted or not.
On 2/14/06, Jean-Louis Seguineau <jean-louis.seguineau at laposte.net> wrote:
> What are we trying to achieve? Stanza tracking or session tracking? I am
> under the impression session tracking is more appropriate in many
> voice/media use cases. Similar to a call refrence.
> IMHO embedding any logic in an identifier is not very scalable. I
> prefer having the sid as the only meaningful Jingle reference. And frankly
> speaking it is not going to create that much of an overhead if we limit
> ourseleves to the sid only in result or error.
> <iq from='gw.shakespeare.lit' to='juliet at capulet.com' type='result'
> <jingle xmlns='http://jabber.org/protocol/jingle'
> -----Original Message-----
> Message: 1
> Date: Tue, 14 Feb 2006 12:12:18 -0700
> From: Peter Saint-Andre <stpeter at jabber.org>
> Subject: [Standards-JIG] Jingle: tracking stanzas
> To: standards-jig at jabber.org
> Message-ID: <43F22B92.2060208 at jabber.org>
> Content-Type: text/plain; charset="iso-8859-1"
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> In XMPP, you track packets based on the 'id' attribute. However, those
> are generated by a client. If an intermediary (such as Asterisk) wants
> to keep track of all the Jingle traffic flowing around, it may want
> something more advanced. Many Jingle-related stanzas include a <jingle/>
> child element with a session ID ('sid') attribute. However, that does
> not normally apply to IQ-results and IQ-errors because RFC 3920 says
> it's optional to include the original child element(s) when sending IQ
> stanzas of type "result" and "error". While it might be nice for
> intermediaries to have that 'sid' on each and every stanza, it would get
> quite verbose. I think we probably have the 'sid' on the packets that
> matter, but discussion is welcome from implementors on the topic.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Standards