Re: [TLS] Fwd: New Version Notification for draft-moriarty-tls-oldversions-diediedie-00.txt

2018-07-13 Thread nalini elkins
us data. I am at a loss as to how to proceed. I am open to any constructive suggestions. Thanks, Nalini On Wed, Jul 11, 2018 at 5:50 AM, Stephen Farrell wrote: > > Hiya, > > On 11/07/18 06:45, nalini elkins wrote: > > Stephen, > > > >> I'd love to add more d

Re: [TLS] Fwd: New Version Notification for draft-moriarty-tls-oldversions-diediedie-00.txt

2018-07-10 Thread nalini elkins
e: > > Hi Nalini, > > On 10/07/18 04:50, nalini elkins wrote: > > It would be nice to see some of this reflected in the draft rather than > > only statistics on browsers. The real usage of these protocols is far > > more complex. > > I didn't have time before th

Re: [TLS] Fwd: New Version Notification for draft-moriarty-tls-oldversions-diediedie-00.txt

2018-07-09 Thread nalini elkins
dB9sQ8mzRHY04Blyx%2BIYjlFC%2Fo0dw%3D=0> > . > > The IETF Secretariat > > > > -- > > Best regards, > Kathleen > > _______ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > <https://na01.safelinks.protecti

Re: [TLS] Encrypted SNI

2018-07-03 Thread nalini elkins
9FA5880072BBB51E42 > > _______ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > -- Thanks, Nalini Elkins President Enterprise Data Center Operators www.e-dco.com ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] Breaking into TLS to protect customers

2018-03-15 Thread nalini elkins
ing TLS? And what >> benefits and increased protection will customers see? >> >> >> >> >> ___ >> TLS mailing list >> TLS@ietf.org >> https://www.ietf.org/mailm

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-15 Thread nalini elkins
On 15/03/18 00:05, nalini elkins wrote: >> There is no question of a smokey back room. >I'm sorry to disagree so bluntly, but while I was an >AD some of the people involved here requested that I >meet them in private to discuss this topic before it >had been raised on the

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-14 Thread nalini elkins
PM, Stephen Farrell <stephen.farr...@cs.tcd.ie> wrote: > > > On 14/03/18 23:32, nalini elkins wrote: > > But, it is a very difficult issue. If I can use a different analogy, if > > the City of Monterey built a new sewer system and told me that to connect > &g

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-14 Thread nalini elkins
r 14, 2018 at 4:30 PM, Ryan Sleevi <ryan-ietf...@sleevi.com> wrote: > > > On Wed, Mar 14, 2018 at 7:17 PM, nalini elkins <nalini.elk...@e-dco.com> > wrote: > >> >>>- > Nalini, why don't you (the consortium) define the standard, then? >>> >>

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-14 Thread nalini elkins
key > exchange. And they would rather not pay for a solution to that problem. > > > -- Thanks, Nalini Elkins President Enterprise Data Center Operators www.e-dco.com ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-14 Thread nalini elkins
k to each other quietly and reasonably. This is a very, very difficult problem. Nalini On Wed, Mar 14, 2018 at 4:16 PM, Stephen Farrell <stephen.farr...@cs.tcd.ie> wrote: > > > On 14/03/18 23:00, nalini elkins wrote: > > The simple explanation is that people think they will

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-14 Thread nalini elkins
ability between TLS and Consortium-TLS? > TLS is designed to be secure and reliable, and it's clear that > Consortium-TLS finds such goals problematic. Yet I fail to see why that's a > problem, since the claimed goal is that Consortium-TLS would only be used > within a single enterprise/datacenter, and thus would never need to > interoperate with a world that valued security and privacy. > -- Thanks, Nalini Elkins President Enterprise Data Center Operators www.e-dco.com ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-14 Thread nalini elkins
name for that tactics, it's called "consensus by exhaustion". > (On the recent GNSO meeting this was briefly discussed as an issue within > ICANN.) > >> > _______ > TLS mailing list > TLS@ietf.org > h

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-14 Thread nalini elkins
s to be defined, it would make > sense for the consortium (rather than the TLS WG) to define it. > > > > Cheers, > > > > Andrei > -- Thanks, Nalini Elkins President Enterprise Data Center Operators www.e-dco.com ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-13 Thread nalini elkins
> I have heard concerns that it is necessary to have a “speedy” solution. > Again, I strongly disagree with this. The standard organizations haven’t > even made TLS 1.0 illegal yet, as I said last time. What makes you think > that something is needed in under five years? I asked that quest

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-13 Thread nalini elkins
ers provide services to hundreds of thousands or millions of end users, so uptime is critical. Nalini On Tue, Mar 13, 2018 at 9:37 AM, nalini elkins <nalini.elk...@e-dco.com> wrote: > *>>* I hope that we can all work together to craft a solution. We don't > want fragmentation and m

Re: [TLS] TLS@IETF101 Agenda Posted

2018-03-13 Thread nalini elkins
oint solutions that were only sold and > deployed in an enterprise because, as I said last time, this is too risky > for the public Internet. > > > > So then, who is “we”? ☺ > > > -- Thanks, Nalini Elkins President Enterprise Data Center Operators www.e-dco.com __