Re: [TLS] Server name extension extensibility problem

[Mike <mike-list@xxxxxxxxx>]

>> I think this could be solved by requiring that all future
>> name types start with two-byte length field (same as
>> host_name), so implementations would be able to skip 
>> past it.
> 
> This sounds good to me as well.

Then the definition could be changed to:

   struct {
       NameType name_type;
       Name     server_name;
   } ServerName;

   enum {
       host_name(0), (255)
   } NameType;

   opaque Name<1..2^16-1>;

   struct {
       ServerName server_name_list<1..2^16-1>
   } ServerNameList;

With text along the lines of, "when name_type is host_name,
server_name is interpreted as an ASCII domain name...."

Mike
_______________________________________________
TLS mailing list
TLS@xxxxxxxx
https://www.ietf.org/mailman/listinfo/tls