[TLS] Encrypted SNI hangout

All, Since the TLS session on Monday got canceled what would people think about using that time to talk about encrypted SNI? Bret Sent from my Commodore 128D PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050___ TLS mailing list T

[TLS] Tonight's Encrypted SNI Hangout Session

All, We had a great turnout tonight for the encrypted SNI hangout session. Everyone seemed open and willing to work together to understand the complexities that sit before us. Several interesting and important views were expressed, and I feel that the meeting was ultimately a success. In fact, I b

Re: [TLS] Tonight's Encrypted SNI Hangout Session

What I think I am more worried about right now is jumping in to designing a technological solution before we know and understand what is going to break and is a solution going to actually solve the perceived problem(s) or make them worse. Technological changes do not always make things better. Ope

Re: [TLS] Tonight's Encrypted SNI Hangout Session

Great comments and feedback. Thank you. Bret Sent from my Commodore 128D PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050 > On Nov 14, 2017, at 10:43 AM, Yoav Nir wrote: > > > >> On 14 Nov 2017, at 0:00, Tom Ritter wrote: >> >> Are you also interested in collecting r

[TLS] Encrypted SNI

From a discussion on the PATIENT list found here: https://www.ietf.org/mail-archive/web/patient/current/msg00078.html From my personal perspective, we need to be careful with all of these efforts. It feels like the pendulum

Re: [TLS] ETSI releases standards for enterprise security and data centre management

Now this WG is finally starting to talk about a solution to a real problem and need. We can either address the use case and need here in the IETF, or we can let the solutions be done else where. I would personally prefer we take this work item back and solve it here in the IETF. Finally, remem

Re: [TLS] ETSI releases standards for enterprise security and data centre management

, the only thing that can not be unscrambled is an egg." > On Dec 5, 2018, at 6:12 PM, Stephen Farrell wrote: > > > > On 05/12/2018 08:08, Bret Jordan wrote: >> Now this WG is finally starting to talk about a solution to a real >> problem and need. We can eith

Re: [TLS] ETSI releases standards for enterprise security and data centre management

Comments inline Sent from my Commodore 128D PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050 > On Dec 5, 2018, at 7:33 PM, Stephen Farrell wrote: > > > >> On 05/12/2018 10:22, Bret Jordan wrote: >> I think we should be more open minded and look at

Re: [TLS] TLS Impact on Network Security draft updated

Nancy, I support this work and think this draft should be published. This is a yet another good write up on some of the requirements that are needed for operational security. Thanks, Bret PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050 "Without cryptography vihv vivc ce xhr

Re: [TLS] TLS Impact on Network Security draft updated

Thanks Sean. It is critical that we understand and discuss all sides of an issue and address all use cases that market has. Beating people down and trying to attack people or their use cases is not something we should be doing in formal standards, especially here at the IETF. Thanks, Bret P

Re: [TLS] TLS Impact on Network Security draft updated

Informational documents do not (usually) have normative statements. If they had normative language, they would be standards track document. Thanks, Bret PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050 "Without cryptography vihv vivc ce xhrnrw, however, the only thing that c

Re: [TLS] TLS Impact on Network Security draft updated

As a professional organization and part of due diligence, we need to try and understand the risks and ramifications on the deployments of our solutions. This means, understanding exactly how the market uses and needs to use the solutions we create. When we remove or change some technology, we sh