Subject: RE: draft-ietf-pkix-srvsan-00

From: "Stefan Santesson" <[email-masked]>
Date: Sat, 24 Sep 2005 16:22:36 +0100

Kurt,

This new name form does not contain a DNS record. It is a name to
express a service name relative to a domain in the form of a single
string.

Stefan Santesson
Program Manager, Standards Liaison
Windows Security

> -----Original Message-----
> From: Kurt D. Zeilenga [mailto:[email-masked]]
> Sent: den 24 september 2005 17:18
> To: Russ Housley
> Cc: Stefan Santesson; Paul Hoffman; [email-masked]
> Subject: RE: draft-ietf-pkix-srvsan-00
> 
> My point is that each DNS name is a sequence of DNS
> labels, each label being an octet string.
> 
> Kurt
> 
> At 11:15 AM 9/23/2005, Russ Housley wrote:
> 
> >Kurt:
> >
> >Yes, if you want to allow the other name to represent more than one
SRV
> record.  No, if you want to include a separate other name instance for
> each SRV record, which is more consistent with the way that tow URLs
would
> be represented.
> >
> >Russ
> >
> >At 02:00 PM 9/23/2005, Kurt D. Zeilenga wrote:
> >>At 09:24 AM 9/23/2005, Paul Hoffman wrote:
> >>>>Therefore, it seems to me that the OCTET STRING is the form that
> matches the sequence of octets that will actually be provided by a DNS
> query.  Then, the ToUnicode routine is used to convert for display to
a
> human.
> >>>
> >>>Russ is completely correct: don't convert if you don't have to, DNS
is
> a binary transport, so OCTET STRING is the correct way to not lose
data.
> >>
> >>wouldn't SEQUENCE OF OCTET STRING be more appropriate?
> >>
> >>Kurt