Manuel Castelo Branco
From: [EMAIL PROTECTED]
Reply-To: [email protected]
To: [email protected]
Subject: Standards Digest, Vol 44, Issue 72
Date: Thu, 26 Jul 2007 12:00:05 -0500 (CDT)
>Send Standards mailing list submissions to
> [email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.jabber.org/mailman/listinfo/standards
>or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
>
>You can reach the person managing the list at
> [EMAIL PROTECTED]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Standards digest..."
>
>
>Today's Topics:
>
> 1. UPDATED: XEP-0084 (User Avatar) (XMPP Extensions Editor)
> 2. Re: SASL protocol errors reporting (Tomasz Sterna)
> 3. Re: SASL protocol errors reporting (Peter Saint-Andre)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Wed, 25 Jul 2007 19:03:27 -0500 (CDT)
>From: XMPP Extensions Editor <[EMAIL PROTECTED]>
>Subject: [Standards] UPDATED: XEP-0084 (User Avatar)
>To: [email protected]
>Message-ID: <[EMAIL PROTECTED]>
>
>Version 0.11 of XEP-0084 (User Avatar) has been released.
>
>Abstract: This document defines an XMPP protocol extension for exchanging user avatars.
>
>Changelog: Removed image size requirements. (psa)
>
>Diff: http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0084.xml?r1=966&r2=1094
>
>URL: http://www.xmpp.org/extensions/xep-0084.html
>
>
>
>------------------------------
>
>Message: 2
>Date: Thu, 26 Jul 2007 08:09:44 +0200
>From: Tomasz Sterna <[EMAIL PROTECTED]>
>Subject: Re: [Standards] SASL protocol errors reporting
>To: XMPP Extension Discussion List <[email protected]>
>Message-ID: <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset=utf-8
>
>Dnia 25-07-2007, Åro o godzinie 09:32 -0700, Peter Saint-Andre
>napisaÅ(a):
> > We have a malformed-request error here:
> > http://www.xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-03.html#sasl-errors-malformed-request
>
>My concern is that we do not have it here:
>http://www.xmpp.org/rfcs/rfc3920.html#rfc.section.6.4
>So if I do report malformed-request error, my implementation will be no
>longer RFC3920 compliant.
>
>
>--
>Tomasz Sterna
>Xiaoka Grp. http://www.xiaoka.com/
>
>
>
>------------------------------
>
>Message: 3
>Date: Thu, 26 Jul 2007 00:16:47 -0700
>From: Peter Saint-Andre <[EMAIL PROTECTED]>
>Subject: Re: [Standards] SASL protocol errors reporting
>To: XMPP Extension Discussion List <[email protected]>
>Message-ID: <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset="utf-8"
>
>Tomasz Sterna wrote:
> > Dnia 25-07-2007, Åro o godzinie 09:32 -0700, Peter Saint-Andre
> > napisaÅ(a):
> >> We have a malformed-request error here:
> >> http://www.xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-03.html#sasl-errors-malformed-request
> >
> > My concern is that we do not have it here:
> > http://www.xmpp.org/rfcs/rfc3920.html#rfc.section.6.4
> > So if I do report malformed-request error, my implementation will be no
> > longer RFC3920 compliant.
>
>Correct. You would no longer be compliant with RFC 3920. Instead, you
>would be compliant with rfc3920bis, which (compared to RFC 3920)
>incorporates errata, corrections, best practices learned from 3+ years
>of implementation experience, and modifications to track specifications
>on which XMPP depends. RFC 3920 referred to RFC 2222, whereas rfc3920bis
>refers to RFC 4422. Both RFC 2222 and RFC 4422 define SASL, but RFC 4422
>is the most up-to-date definition of SASL, since it too incorporates
>errata and corrections and so on. RFC 4422 talks about malformed
>requests. RFC 2222 did not. Therefore in rfc3920bis we have added a way
>to properly handle malformed SASL requests. Naturally, no one is forcing
>you to comply with rfc3920bis. You can do that now, you can wait until
>rfc3920bis is approved by the IESG, you can wait until it is published
>with a nice new number by the RFC Editor, you can ignore RFC 3920
>forever. The choice is yours.
>
>/psa
>
>
>-------------- next part --------------
>A non-text attachment was scrubbed...
>Name: smime.p7s
>Type: application/x-pkcs7-signature
>Size: 7354 bytes
>Desc: S/MIME Cryptographic Signature
>Url : http://mail.jabber.org/pipermail/standards/attachments/20070726/814c5636/smime-0001.bin
>
>------------------------------
>
>_______________________________________________
>Standards mailing list
>[email protected]
>http://mail.jabber.org/mailman/listinfo/standards
>
>
>End of Standards Digest, Vol 44, Issue 72
>*****************************************
Verificador de Segurança do Windows Live OneCare: verifique já a segurança do seu PC!
