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

["Stefan Santesson" <stefans@xxxxxxxxxxxxx>]

Yes,

The initial background thought was that more demanding encodings would
be more of an issue for host labels rather than service resource records
and thus IA5String would be sufficient, but I agree at this point to the
suggestions to specify UTF8String instead.


Stefan Santesson
Program Manager, Standards Liaison
Windows Security
 

> -----Original Message-----
> From: owner-ietf-pkix@xxxxxxxxxxxx
[mailto:owner-ietf-pkix@xxxxxxxxxxxx]
> On Behalf Of Jean-Marc Desperrier
> Sent: den 20 maj 2005 01:42
> To: ietf-pkix@xxxxxxx
> Subject: Re: Request for new work item - Defining an SRV RR otherName
> 
> 
> 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 ACE
> encoding, instead of being able to put the real unicode value, so I'm
> all for not doing the mistake again.