Jingle user location
Edward Tie via Standards <[email protected]> Tue, 30 Jun 2026 23:38:15 +0200
| Newsgroups | gmane.network.jabber.standards-jig |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============1035299546529404708==
Content-Type: multipart/alternative;
boundary="------------TYe0V8kzhmIu6T9wSQKMTUOO"
Content-Language: nl
This is a multi-part message in MIME format.
--------------TYe0V8kzhmIu6T9wSQKMTUOO
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
|Thank you for the feedback. Could you please clarify the main objection
to the Jingle User Location proposal? I would like to understand what
should be changed before revising it. Is the objection about the use of
Jingle, the relation to XEP-0080, privacy/consent, emergency-use
wording, scope, or something else? I do not want to assume the reason.
If you can point to the specific part that is problematic, I can make
the next revision more focused.|
greetings,
Edward Tie .
--------------TYe0V8kzhmIu6T9wSQKMTUOO
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<pre><code>Thank you for the feedback.
Could you please clarify the main objection to the Jingle User Location proposal?
I would like to understand what should be changed before revising it.
Is the objection about the use of Jingle, the relation to XEP-0080, privacy/consent, emergency-use wording, scope, or something else?
I do not want to assume the reason. If you can point to the specific part that is problematic, I can make the next revision more focused.</code></pre>
<p><br>
</p>
<p>greetings,</p>
<p>Edward Tie .</p>
<p><br>
</p>
</body>
</html>
--------------TYe0V8kzhmIu6T9wSQKMTUOO--
--===============1035299546529404708==
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]
--===============1035299546529404708==--