Hello, I have updated the Jingle User Location ProtoXEP with clearer wording after the Council discussion. The updated draft is here: https://github.com/xsf/xeps/pull/1550 The main clarification is that this proposal does not replace XEP-0080. XEP-0080 remains the location payload. The problem this proposal tries to solve is the call/session binding: XEP-0080 tells where the user is, but it does not reliably tell for which active Jingle call that location was shared. PEP/PubSub is useful for general user-location publication, but for an active call it does not clearly answer: - which Jingle session / sid the location belongs to; - whether the location was explicitly shared for this call; - whether it is fresh, stale, one-time, or live; - when call-scoped location sharing stops; - whether a relay, accessibility assistant or future emergency gateway may treat it as the location for the active call. The revised direction is therefore narrower: A small Jingle binding for XEP-0080 during an active call. It reuses the existing XEP-0080 geoloc payload and adds Jingle session context, stop-sharing/expiry wording, fallback wording and privacy wording. It also explicitly avoids claiming to be an emergency-service protocol by itself. The reason I think this matters is accessibility and 112/911-readiness. A deaf or speech-impaired user may be in a Total Conversation call with audio, video, RTT, captions, relay/interpreter services or a future emergency gateway. In that situation the peer or gateway should not have to guess whether the latest XEP-0080/PEP item belongs to the current call. Feedback is welcome, especially on whether this narrower “Jingle binding for XEP-0080” direction is the right shape. Kind regards, Edward