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

Re: Remaining open issues for RFC-2401bis

To: Charlie Kaufman <charliek@microsoft.com>
Subject: Re: Remaining open issues for RFC-2401bis
From: Nicolas Williams <Nicolas.Williams@sun.com>
Date: Wed, 24 Mar 2004 14:37:45 -0600
Cc: Stephen Kent <kent@bbn.com>, Tero Kivinen <kivinen@iki.fi>, ipsec@lists.tislabs.com
In-reply-to: <F5F4EC6358916448A81370AF56F211A5023E4BE5@RED-MSG-51.redmond.corp.microsoft.com>
Mail-followup-to: Charlie Kaufman <charliek@microsoft.com>,Stephen Kent <kent@bbn.com>, Tero Kivinen <kivinen@iki.fi>,ipsec@lists.tislabs.com
References: <F5F4EC6358916448A81370AF56F211A5023E4BE5@RED-MSG-51.redmond.corp.microsoft.com>
Sender: owner-ipsec@lists.tislabs.com
User-agent: Mutt/1.4i

On Wed, Mar 24, 2004 at 11:05:20AM -0800, Charlie Kaufman wrote:
> We could add yet another ID Type option for UTF-8 string, but does
> anyone actually have a use for it?

When the rfc822 subjectAltName is internationalized then the
corresponding ID should be also by extension (one hopes).  If the matter
is addressed by adding additional cert extensions or by adding to the
general name CHOICE (why is it not marked extensible?) then we may need
a new ID type to go with it.

Nico
--

Follow-Ups:
- Re: Remaining open issues for RFC-2401bis
  - From: Stephen Kent <kent@bbn.com>

References:
- RE: Remaining open issues for RFC-2401bis
  - From: "Charlie Kaufman" <charliek@microsoft.com>

Prev by Date: RE: Remaining open issues for RFC-2401bis
Next by Date: RE: Temporary version of the new IKEv2 draft
Previous by thread: RE: Remaining open issues for RFC-2401bis
Next by thread: Re: Remaining open issues for RFC-2401bis
Index(es):
- Date
- Thread