W3C home > Mailing lists > Public > public-usable-authentication@w3.org > March 2007

RE: Produce material on name-based virtual hosting and TLS

From: Hallam-Baker, Phillip <pbaker@verisign.com>
Date: Wed, 7 Mar 2007 10:29:20 -0800
Message-ID: <198A730C2044DE4A96749D13E167AD3701147C97@MOU1WNEXMB04.vcorp.ad.vrsn.com>
To: "Eric Rescorla" <ekr@networkresonance.com>, "Mary Ellen Zurko" <Mary_Ellen_Zurko@notesdev.ibm.com>
Cc: <beltzner@mozilla.com>, "public-usable-authentication" <public-usable-authentication@w3.org>

More IP address consumption is one consequence, another is that parties may not be able to deploy proposed security enhancements due to lack of available IP space.

> -----Original Message-----
> From: Eric Rescorla [mailto:ekr@networkresonance.com] 
> Sent: Wednesday, March 07, 2007 12:29 PM
> To: Mary Ellen Zurko
> Cc: Hallam-Baker, Phillip; beltzner@mozilla.com; 
> public-usable-authentication
> Subject: Re: Produce material on name-based virtual hosting and TLS 
> 
> Mary Ellen Zurko <Mary_Ellen_Zurko@notesdev.ibm.com> wrote:
> > OK. But what effect does the "protocol limitations" have on 
> usable and 
> > robust security context information (which was also part of 
> what I was 
> > trying to get clarity on). Did I get the effect right (increase in 
> > errors on cert processing, so setting user expectations that errors 
> > are not a problem)?
> 
> More IP address consumption? :)
> 
> -Ekr
> 
Received on Wednesday, 7 March 2007 18:31:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:14 GMT