[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@xxxxxxxx>
Subject: RE: Request for new work item - Defining an SRV RR otherName
From: "Manger, James H" <James.H.Manger@xxxxxxxxxxxxxxxx>
Date: Fri, 20 May 2005 11:26:23 +1000
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>
Sender: owner-ietf-pkix@xxxxxxxxxxxx
Thread-index: AcVa49B3OIJ65dJPQLOybWmgvDp/swBDTguwAAWxwyAAHHGHwAAVf99Q
Thread-topic: Request for new work item - Defining an SRV RR otherName

RE: draft-santesson-pkix-srvrr-00

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


-----Original Message-----
From: Stefan Santesson [mailto:stefans@xxxxxxxxxxxxx] 
Sent: Thursday, 19 May 2005 11:53 PM
To: Manger, James H

When I talked to Russ we thought that IA5String would be sufficient so I
did put that in as a start, but I'm completely open to a change to
UTF8String.

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

Follow-Ups:
- Re: Request for new work item - Defining an SRV RR otherName
  - From: Jean-Marc Desperrier

Prev by Date: Re: key usage - key encipherment or data encipherment
Next by Date: Re: Request for new work item - Defining an SRV RR otherName
Previous by thread: 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