[jdev] service banners?

[Peter Saint-Andre]

Jefferson Ogata wrote:
> On 2006-07-19 15:49, Peter Saint-Andre wrote:
>> The question is not whether certain organizations need this, the
>> question is how to best do this in XMPP. IMHO we have two alternatives:
>>
>> 1. A new, optional attribute in the stream header. This informs the
>> receiving party of the service policy but does not require the receiving
>> party to affirm that they accept the service policy. Plus the client may
>>
>> 2. A new stream feature. This would involve a request-response model,
>>
>> The second option seems preferable to me, especially since it doesn't
>> require any changes to RFC 3920 (we can define stream features to our
>> heart's content, e.g. in a JEP). Naturally this is all XMPP 1.0 stuff,
>> older ("XMPP 0.9") clients might not be able to connect depending on how
>> much the service admins have locked things down. But I take it that is
>> the point.
> 
> Either would suit my particular purposes, I think. I see the logic of
> preferring option 2, although offhand I think it might require a bit
> more work to implement both on the client and the server side. In the
> lazy case, clients are free to ignore the message and simply send back
> the confirming reply automatically. The server has one more state to track.

Well, my understanding of your requirements is that you (may) need to
know if the end user has seen the banner and agreed to its terms before
allowing the user to authenticate. If so, (2) is the only way to go. If
your requirements are more lax, (1) might be acceptable (although I
really don't like anything that requires changes to RFC 3920).

In any case, working on this is not especially a high priority for me,
but if you'd like to collaborate, contact me off-list.

Peter

-- 
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20060720/5bf19b42/attachment-0002.bin>