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

Re: [TLS] Server name extension extensibility problem

To: "Pasi.Eronen@xxxxxxxxx" <Pasi.Eronen@xxxxxxxxx>
Subject: Re: [TLS] Server name extension extensibility problem
From: Eric Rescorla <ekr@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 09 May 2008 11:35:48 -0700
Cc: tls@xxxxxxxx
Delivered-to: tls@xxxxxxxxxxxxxx
In-reply-to: <1696498986EFEC4D9153717DA325CB72924691@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:tls-request@ietf.org?subject=help>
List-id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-post: <mailto:tls@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
References: <4821C4A1.6030102@xxxxxxxxx> <1696498986EFEC4D9153717DA325CB72924691@xxxxxxxxxxxxxxxxxxxxxx>
Sender: tls-bounces@xxxxxxxx
User-agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)

At Thu, 8 May 2008 14:40:06 +0300,
Pasi.Eronen@xxxxxxxxx wrote:
> Good catch! 
> 
> 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.

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

Follow-Ups:
- Re: [TLS] Server name extension extensibility problem
  - From: Mike

References:
- [TLS] Server name extension extensibility problem
  - From: Mike
- Re: [TLS] Server name extension extensibility problem
  - From: Pasi.Eronen@xxxxxxxxx

Prev by Date: Re: [TLS] draft-nir-tls-eap-03
Next by Date: Re: [TLS] Server name extension extensibility problem
Previous by thread: Re: [TLS] Server name extension extensibility problem
Next by thread: Re: [TLS] Server name extension extensibility problem
Index(es):
- Date
- Thread