[SPKM] DName canonicalization rules in draft-adamson-rfc2847-bis
Martin Rex <martin.rex@sap.com> Mon, 06 November 2006 20:08 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhAlw-0007tw-2r; Mon, 06 Nov 2006 15:08:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhAlu-0007qW-Or for spkm@ietf.org; Mon, 06 Nov 2006 15:08:42 -0500
Received: from smtpde03.sap-ag.de ([155.56.68.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhAlt-0000zs-CX for spkm@ietf.org; Mon, 06 Nov 2006 15:08:42 -0500
Received: from sap-ag.de (smtpde03) by smtpde03.sap-ag.de (out) with ESMTP id VAA16779 for <spkm@ietf.org>; Mon, 6 Nov 2006 21:08:28 +0100 (MEZ)
From: Martin Rex <martin.rex@sap.com>
Message-Id: <200611062008.VAA27797@uw1048.wdf.sap.corp>
To: spkm@ietf.org
Date: Mon, 06 Nov 2006 21:08:28 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
X-Spam-Score: 1.1 (+)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [SPKM] DName canonicalization rules in draft-adamson-rfc2847-bis
X-BeenThere: spkm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: martin.rex@sap.com
List-Id: Low Infrastructure Public Key GSS mechanism <spkm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/spkm>, <mailto:spkm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/spkm>
List-Post: <mailto:spkm@ietf.org>
List-Help: <mailto:spkm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/spkm>, <mailto:spkm-request@ietf.org?subject=subscribe>
Errors-To: spkm-bounces@ietf.org
The canonicalization rules in draft-adamson-rfc2847-bis-01.txt currently
says
2.5.1.4 Exported Name Object Form
-- DirectoryString attribute values of type PrintableString and
UTF8String are not in hexadecimal format
-- DirectoryString attribute values of types other than
PrintableString and UTF8String are output in hexadecimal format
What about IA5String? I don't think that IA5String has ever been
(ab)used in a controversial fashion, and since it is a subset of
UTF8String, I would prefer to see then NOT hexencoded as well.
-Martin
_______________________________________________
SPKM mailing list
SPKM@ietf.org
https://www1.ietf.org/mailman/listinfo/spkm