On Jan 14, 2008, at 4:29 PM, Peter Saint-Andre wrote:
8.5 Friendly Name
The 'name' attribute of the service discovery <identity/> element
enables a responding application to specify the "friendly name" for
its node. However, this attribute is excluded from the hash
generation method, primarily because it is human-readable text and
therefore may be provided in different localized versions. As a
result, its inclusion would needlessly multiply the number of
possible hash values and thus the time and resources required to
validate values of the 'ver' attribute. However, a receiving
application MAY send a service discovery information request to a
particularly JID+node combination in order to determine the friendly
name, then cache the result for that JID+node only.
Gr. Having email issues this morning. This is a reply to Kevin's
desire for new text.
<suggestion>
However, a receiving application MAY send a service discovery
information request to a particularly JID+node combination in order to
determine the friendly name, but if it does so then it MUST cache the
result for that JID+node combination.
</suggestion>
I really wanted to cache just based on the node, but "there's an
attack!" for people poisoning others' client names. I don't think
that's really a concern, but perhaps that is over-practical.
--
Joe Hildebrand
