Re: Proposed XMPP Extension: Jingle User Location
"Marvin W. via Standards" <[email protected]> Tue, 02 Jun 2026 17:31:06 +0300
| Newsgroups | gmane.network.jabber.standards-jig |
|---|---|
| Message-ID | <[email protected]> |
--===============0352680294299456177== Content-Type: multipart/alternative; boundary="=-reLK6XdtikfGR3tOMSW4" --=-reLK6XdtikfGR3tOMSW4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2026-06-02 at 13:35 +0100, Dave Cridland wrote: >=20 >=20 > On Tue, 2 Jun 2026 at 10:54, Daniel Gultsch <[email protected]> > wrote: > > Title: Jingle User Location > > Abstract: > > This specification defines a Jingle application extension for > > negotiating and updating user location inside an active Jingle > > session > > using the XEP-0080 User Location payload. > >=20 > > URL: https://xmpp.org/extensions/inbox/jingle-geoloc.html > >=20 >=20 >=20 > I'm not wholly sure why this would need to be encapsulated in the > Jingle content description? >=20 > Why wouldn't this be simply sent alongside in a message? (And, in > general, I'd like this - the WhatsApp location sharing in a chat > feature is very useful!) This is not only a question of why, but also this is directly contradicting and incompatible to the nature of Jingle. Jingle is to initiate and maintain peer-to-peer session in form of specific application data transferred via a datagram or streaming transport between entities. Jingle has mandatory requirements for conformance and this specification does not comply with any of them=C2=A0https://xmpp.org/extensions/xep-0166.html#conformance If sending the location via actual Jingle is desirable (which is what the abstract claims the XEP specifies, but doesn't actually do), one option is to use XEP-0080 via XEP-0247. Alternatively, if Jingle is not really a requirement and inband is a good option, either the use of XEP-0080 via a PEP node with access restrictions could be an option, or a new specification to transfer XEP-0080 via <message/> as Dave suggested could also be interesting. Marvin --=-reLK6XdtikfGR3tOMSW4 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html><head><style>pre,code,address { margin: 0px; } h1,h2,h3,h4,h5,h6 { margin-top: 0.2em; margin-bottom: 0.2em; } ol,ul { margin-top: 0em; margin-bottom: 0em; } blockquote { margin-top: 0em; margin-bottom: 0em; } </style></head><body><div>On Tue, 2026-06-02 at 13:35 +0100, Dave Cridland = wrote:</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; border-le= ft:2px #729fcf solid;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><b= r></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"lt= r" class=3D"gmail_attr">On Tue, 2 Jun 2026 at 10:54, Daniel Gultsch <<a = href=3D"mailto:[email protected]">[email protected]</a>> wrote:<br></div= ><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; border-left:2px #729= fcf solid;padding-left:1ex"><div>Title: Jingle User Location<br>Abstract:<b= r>This specification defines a Jingle application extension for<br>negotiat= ing and updating user location inside an active Jingle session<br>using the= XEP-0080 User Location payload.<br></div><div><br>URL: <a href=3D"https://= xmpp.org/extensions/inbox/jingle-geoloc.html" rel=3D"noreferrer" target=3D"= _blank">https://xmpp.org/extensions/inbox/jingle-geoloc.html</a></div><br><= /blockquote><div><br></div><div>I'm not wholly sure why this would need to = be encapsulated in the Jingle content description?</div><div><br></div><div= >Why wouldn't this be simply sent alongside in a message? (And, in general,= I'd like this - the WhatsApp location sharing in a chat feature is very us= eful!)</div></div></div></blockquote><div><br></div><div>This is not only a= question of why, but also this is directly contradicting and incompatible = to the nature of Jingle.</div><div>Jingle is to initiate and maintain peer-= to-peer session in form of specific application data transferred via a data= gram or streaming transport between entities.</div><div>Jingle has mandator= y requirements for conformance and this specification does not comply with = any of them <a href=3D"https://xmpp.org/extensions/xep-0166.html#confo= rmance">https://xmpp.org/extensions/xep-0166.html#conformance</a></div><div= ><br></div><div>If sending the location via actual Jingle is desirable (whi= ch is what the abstract claims the XEP specifies, but doesn't actually do),= one option is to use XEP-0080 via XEP-0247.</div><div><br></div><div>Alter= natively, if Jingle is not really a requirement and inband is a good option= , either the use of XEP-0080 via a PEP node with access restrictions could = be an option, or a new specification to transfer XEP-0080 via <message/&= gt; as Dave suggested could also be interesting.</div><div><br></div><div>M= arvin</div><div><span></span></div></body></html> --=-reLK6XdtikfGR3tOMSW4-- --===============0352680294299456177== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected] --===============0352680294299456177==--