[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DN Encoding by UTF8String

To: shimaoka@xxxxxxxxxxx
Subject: Re: DN Encoding by UTF8String
From: Russ Housley <housley@xxxxxxxxxxxx>
Date: Wed, 17 Dec 2003 10:45:42 -0500
Cc: ietf-pkix@xxxxxxx
In-reply-to: <>
List-archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-id: <ietf-pkix.imc.org>
List-unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
References: <> <> <>
Sender: owner-ietf-pkix@xxxxxxxxxxxx

It is not clear that a son-of-rfc3280 is needed. I believe that an update addressing this one aspect of the document can be generated much more quickly than reopening the whole document. I believe that speedy resolution is desirable for all concerned.

Russ

At 11:39 AM 12/17/2003 +0900, Masaki SHIMAOKA wrote:

How will son of RFC3280 address this UTF8Sting issue which is described
at clause 4.1.2.4 in RFC3280?

References:
- Re: DN Encoding by UTF8String
  - From: Tim Polk
- Re: DN Encoding by UTF8String
  - From: Richard Levitte - VMS Whacker
- Re[2]: DN Encoding by UTF8String
  - From: Masaki SHIMAOKA

Prev by Date: RE: Last Call: Qualified Certificates
Next by Date: RE: IDPKC
Previous by thread: Re[2]: DN Encoding by UTF8String
Next by thread: Re: DN Encoding by UTF8String
Index(es):
- Date
- Thread