Initial version.
Publish-Subscribe (XEP-0060)
Time zone information can also be obtained through Entity Time (XEP-0202)
The numeric time zone offset from UTC for the user is expressed as the textual content of the <tzo/> element qualified by the 'urn:xmpp:timezone:0' namespace.
When a user wishes to share time zone information, its client may publish that fact to a PEP node whose NodeID is "urn:xmpp:timezone:0" (see Protocol Namespaces regarding issuance of one or more permanent namespaces). Because time zone information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the <presence/> stanza type.
The time zone offset is then delivered to all subscribers:
When the user wishes to stop broadcasting its time zone offset, the user's client SHOULD send an empty <tzo/> element with the same ItemID:
Revealing an entity's numeric time zone offset may leak limited information about the entity's current location. If the entity's understanding of UTC is far off from actual UTC, revealing that discrepancy may make it possible for an attacker to send XML stanzas that appear to be in the past or future even though they are not; therefore an entity should use the Network Time Protocol (RFC 958
This document requires no interaction with the Internet Assigned Numbers Authority (IANA)
The XMPP Registrar
If the protocol defined in this specification undergoes a revision that is not fully backwards-compatible with an older version, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.
The protocol documented by this schema is defined in
XEP-xxxx: http://www.xmpp.org/extensions/xep-xxxx.html
]]>