Joe Hildebrand wrote: > > On Dec 18, 2007, at 12:03 PM, Peter Saint-Andre wrote: > >> The disco#info request is sent by the requesting entity to the >> generating entity. The value of the 'to' attribute MUST be the exact JID >> of the generating entity, which in the case of a client will be the full >> JID (<[EMAIL PROTECTED]/resource>). >> >> The disco 'node' attribute MUST be included for backwards-compatibility. >> The value of the 'node' attribute SHOULD be generated by concatenating >> the value of the caps 'node' attribute (e.g., >> "http://code.google.com/p/exodus";) as provided by the generating entity, >> the "#" character, and the value of the caps 'ver' attribute (e.g., >> "8RovUdtOmiAjzj+xI7SK5BCw3A8=") as provided by the generating entity. > > +1 > >>> Section 6.3 is really cool. >> >> Perhaps because that was your suggestion. :) > > Heh. Perhaps the idea was better than person that suggested it, then. :) > >>> Is it always going to be clear what the >>> associated JID will be for the stream? >> >> I would think it's the 'from' address from the response stream header. > > Did we decide those would always be there? Even for multi-homed hosts? > That makes sense. Perhaps there should be a note of that in section > 6.3, then.
RFC 3920 said: The 'from' attribute SHOULD be used only in the XML stream header from the receiving entity to the initiating entity, and MUST be set to a hostname serviced by the receiving entity that is granting access to the initiating entity. rfc3920bis current says: In both client-to-server and server-to-server communications, the 'from' attribute MUST be included in the response stream header and MUST be set to a hostname serviced by the receiving entity that is granting access to the initiating entity. I've adjusted XEP-0115 to read: When a connected client or peer server sends a service discovery information request to determine the entity capabilities of a server that advertises capabilities via the stream feature, the requesting entity MUST send the disco#info request to the server's JID as provided in the 'from' attribute of the response stream header, if any (the 'from' attribute was recommended by RFC 3920 and is required by rfc3920bis). Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
