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

Re: Request for new work item - Defining an SRV RR otherName

To: ietf-pkix@xxxxxxx
Subject: Re: Request for new work item - Defining an SRV RR otherName
From: Jean-Marc Desperrier <jmdesp@xxxxxxx>
Date: Fri, 20 May 2005 10:42:28 +0200
In-reply-to: <73388857A695D31197EF00508B08F29816B38C88@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <73388857A695D31197EF00508B08F29816B38C88@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-ietf-pkix@xxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.8b2) Gecko/20050517


Manger, James H wrote:

How about using UTF8String, instead of IA5String?  The latter does not gain much (it can still include chars such as 0x00, newline, bell that are presumably not valid in SRV RR names), while the former should be more future-proof.

     SRVRRName ::= UTF8String

Could you post the suggestion to the pkix list to see if there are any
other reactions?

It's already really a pity that dNSName forces us to store SAN in ACEencoding, instead of being able to put the real unicode value, so I'mall for not doing the mistake again.

References:
- RE: Request for new work item - Defining an SRV RR otherName
  - From: Manger, James H

Prev by Date: RE: Request for new work item - Defining an SRV RR otherName
Next by Date: Re: key usage - key encipherment or data encipherment
Previous by thread: RE: Request for new work item - Defining an SRV RR otherName
Next by thread: RE: Request for new work item - Defining an SRV RR otherName
Index(es):
- Date
- Thread