CHARSET-POLICY Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.txt
"Kurt D. Zeilenga" <Kurt@OpenLDAP.org> Wed, 08 October 2003 06:54 UTC
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h986spKP098288 for <ietf-sasl-bks@above.proper.com>; Tue, 7 Oct 2003 23:54:51 -0700 (PDT) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h986spsu098287 for ietf-sasl-bks; Tue, 7 Oct 2003 23:54:51 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from pretender.boolean.net (root@router.boolean.net [198.144.206.49]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h986soKP098275 for <ietf-sasl@imc.org>; Tue, 7 Oct 2003 23:54:50 -0700 (PDT) (envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1]) by pretender.boolean.net (8.12.9/8.12.9) with ESMTP id h986smlg075769; Wed, 8 Oct 2003 06:54:48 GMT (envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.0.0.22.0.20031008112004.02b2a0b8@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 08 Oct 2003 11:54:31 -0700
To: Jeffrey Hutzelman <jhutz@cmu.edu>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: CHARSET-POLICY Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.txt
Cc: ietf-sasl@imc.org
In-Reply-To: <2070817856.1065023014@mariner.pc.cs.cmu.edu>
References: <5.2.0.9.0.20030915103818.03b51a88@127.0.0.1> <6.0.0.22.0.20031001100505.03e9ffd0@127.0.0.1> <2070817856.1065023014@mariner.pc.cs.cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>
My main gripe here is that the I-D implied incorrectly that the IETF character set policy RECOMMENDs protocols be able to use UTF-8 when the police that protocols are REQUIRED to be able to use UTF-8. I think both these "Per IETF character set policy" statements should be deleted. Inserting a note like shown below might be appropriate. > The character encoding scheme used (see [CHARSET-POLICY] for IETF policy regarding character sets in IETF protocols) for > transmitting an authorization identity over protocol is > specified in each authentication mechanism (with the > authentication mechanism's blob being further > restricted/encoded by the protocol profile). At 08:43 AM 10/1/2003, Jeffrey Hutzelman wrote: >>> Per IETF character set >>> policy [CHARSET-POLICY], authentication mechanisms SHOULD encode >>> these and other strings in UTF-8 [UTF-8]. >> >>This seems counter to [CHARSET-POLICY] as it allows a mechanism to >>not support UTF-8 transfer of character data. >>[CHARSET-POLICY] says: >> Protocols MUST be able to use the UTF-8 charset, which consists of >> the ISO 10646 coded character set combined with the UTF-8 character >> encoding scheme, as defined in [10646] Annex R (published in >> Amendment 2), for all text. > >It would probably be appropriate to require applications to deal, though the truth is that CHARSET-POLICY already does that without our help. >While we can impose requirements on SASL mechanisms, we really can't impose requirements on the authentication technologies upon which they are built. > Requiring mechanisms to use UTF-8 might impose an impossible burden on the SASL mechansim designer, forcing them to do transformations between Unicode and some other character set. > >So, it is appropriate to REQUIRE that authorization identities (which are not really owned by the mechanism anyway) be encoded as UTF-8, and I think we should do so. But it may not be appropriate for "other strings".
- WG Last Call: draft-ietf-sasl-rfc2222bis-02.txt Kurt D. Zeilenga
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Alexey Melnikov
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Alexey Melnikov
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Kurt D. Zeilenga
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Alexey Melnikov
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Kurt D. Zeilenga
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Hallvard B Furuseth
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Jeffrey Hutzelman
- CHARSET-POLICY Re: WG Last Call: draft-ietf-sasl-… Kurt D. Zeilenga
- Re: CHARSET-POLICY Re: WG Last Call: draft-ietf-s… Alexey Melnikov
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Alexey Melnikov
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Jeffrey Hutzelman
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Alexey Melnikov
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Kurt D. Zeilenga
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Sam Hartman
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Rob Siemborski
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Alexey Melnikov
- Proxy authentication (was WG Last Call: draft-iet… Alexey Melnikov
- Re: WG Last Call: draft-ietf-sasl-rfc2222bis-02.t… Alexey Melnikov