Re: [TLS] NewSessionTicketFormat - for PSK

2016-04-25 Thread Eric Rescorla
On Mon, Apr 25, 2016 at 12:13 PM, Jim Schaad wrote: > > > > > *From:* TLS [mailto:tls-boun...@ietf.org] *On Behalf Of *Eric Rescorla > *Sent:* Monday, April 25, 2016 11:10 AM > *To:* Jim Schaad > *Cc:* tls@ietf.org > *Subject:* Re: [TLS] NewSessionTicketFormat - for PSK > > > > > > > > On Mon, A

Re: [TLS] Call for WG adoption of draft-mattsson-tls-ecdhe-psk-aead

2016-04-25 Thread Andrei Popov
I support adoption of this draft. No reason to limit ECDHE_PSK to CBC. Cheers, Andrei -Original Message- From: TLS [mailto:tls-boun...@ietf.org] On Behalf Of Sean Turner Sent: Monday, April 25, 2016 8:22 AM To: tls Subject: Re: [TLS] Call for WG adoption of draft-mattsson-tls-ecdhe-psk

Re: [TLS] Call for WG adoption of draft-shore-tls-dnssec-chain-extension

2016-04-25 Thread Daniel Migault
I support the adoption of the draft. On Mon, Apr 25, 2016 at 1:53 PM, Salz, Rich wrote: > I support adoption. > > -- > Senior Architect, Akamai Technologies > IM: richs...@jabber.at Twitter: RichSalz > > > ___ > TLS mailing list > TLS@ietf.org > https:

Re: [TLS] NewSessionTicketFormat - for PSK

2016-04-25 Thread Jim Schaad
From: TLS [mailto:tls-boun...@ietf.org] On Behalf Of Eric Rescorla Sent: Monday, April 25, 2016 11:10 AM To: Jim Schaad Cc: tls@ietf.org Subject: Re: [TLS] NewSessionTicketFormat - for PSK On Mon, Apr 25, 2016 at 11:07 AM, Jim Schaad mailto:i...@augustcellars.com> > wrote: I was l

Re: [TLS] NewSessionTicketFormat - for PSK

2016-04-25 Thread Eric Rescorla
On Mon, Apr 25, 2016 at 11:07 AM, Jim Schaad wrote: > I was looking at how TLS 1.3 was going to fit into an upgrade from the > existing 1.2 version that is used for RADIUS and having vague memories of > what was going on during the F2F meeting and I ended up with the following > question. > > We

[TLS] NewSessionTicketFormat - for PSK

2016-04-25 Thread Jim Schaad
I was looking at how TLS 1.3 was going to fit into an upgrade from the existing 1.2 version that is used for RADIUS and having vague memories of what was going on during the F2F meeting and I ended up with the following question. We are planning to indicate in the NewSessionTicket items such as if

Re: [TLS] Call for WG adoption of draft-shore-tls-dnssec-chain-extension

2016-04-25 Thread Salz, Rich
I support adoption. -- Senior Architect, Akamai Technologies IM: richs...@jabber.at Twitter: RichSalz ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] Call for WG adoption of draft-shore-tls-dnssec-chain-extension

2016-04-25 Thread Aaron Zauner
> On 25 Apr 2016, at 22:12, Sean Turner wrote: > - Support adoption and are willing to review/comment on the draft by > 201600429. Note that the extensions is pretty straight forward, but the > chairs still need people to comment on the draft as we’re processing it down > the path. ... > >

Re: [TLS] Call for WG adoption of draft-shore-tls-dnssec-chain-extension

2016-04-25 Thread Viktor Dukhovni
On Mon, Apr 25, 2016 at 08:12:17AM -0700, Sean Turner wrote: > - Support adoption and are willing to review/comment on the draft I support the adoption of this draft. -- Viktor. ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/l

[TLS] Actions and issues from the IETF 95 TLS meeting

2016-04-25 Thread Joseph Salowey
Below are some of the more significant issues discussed at the meeting in Buenos Aires: 1. Adopt David Benjamin's signature and hash algorithm negotiation structure that ties both together. New code points to define signature algorithm, curve and hash as a unit. - PR incorporated into draft - h

Re: [TLS] Call for WG adoption of draft-shore-tls-dnssec-chain-extension

2016-04-25 Thread Russ Housley
On Apr 25, 2016, at 11:19 AM, Paul Wouters wrote: > On Mon, 25 Apr 2016, Sean Turner wrote: > >> draft-shore-tls-dnssec-chain-extension was originally discussed at IETF 93 >> [0], and the authors have been biding their time while the WG thrashed out >> TLS1.3s' issues. At IETF 95, they prese

Re: [TLS] Call for WG adoption of draft-shore-tls-dnssec-chain-extension

2016-04-25 Thread Sean Turner
I got the dates wrong. They should both have been 20160510. spt > On Apr 25, 2016, at 08:12, Sean Turner wrote: > > All, > > draft-shore-tls-dnssec-chain-extension was originally discussed at IETF 93 > [0], and the authors have been biding their time while the WG thrashed out > TLS1.3s' iss

Re: [TLS] Call for WG adoption of draft-shore-tls-dnssec-chain-extension

2016-04-25 Thread Paul Wouters
On Mon, 25 Apr 2016, Sean Turner wrote: draft-shore-tls-dnssec-chain-extension was originally discussed at IETF 93 [0], and the authors have been biding their time while the WG thrashed out TLS1.3s' issues. At IETF 95, they presented again [1], but this time the chairs took a sense of the ro

Re: [TLS] Call for WG adoption of draft-mattsson-tls-ecdhe-psk-aead

2016-04-25 Thread Sean Turner
sigh and here as well - they should have been 20160510. spt > On Apr 25, 2016, at 08:17, Sean Turner wrote: > > All, > > draft-mattsson-tls-ecdhe-psk-aead includes some cipher suites that are needed > for TLS1.3. We need to get these officially registered so the chairs would > like to hear

[TLS] Call for WG adoption of draft-mattsson-tls-ecdhe-psk-aead

2016-04-25 Thread Sean Turner
All, draft-mattsson-tls-ecdhe-psk-aead includes some cipher suites that are needed for TLS1.3. We need to get these officially registered so the chairs would like to hear whether there is WG support for adopting draft-mattsson-tls-ecdhe-psk-aead. Please let us know whether you: - Support adop

[TLS] Call for WG adoption of draft-shore-tls-dnssec-chain-extension

2016-04-25 Thread Sean Turner
All, draft-shore-tls-dnssec-chain-extension was originally discussed at IETF 93 [0], and the authors have been biding their time while the WG thrashed out TLS1.3s' issues. At IETF 95, they presented again [1], but this time the chairs took a sense of the room about whether the WG was in favor