It looks like we have consensus to adopt this draft as a working group
item. Please submit the current draft as a working group item with the
filename draft-ietf-tls-exported-authenticator-00.txt. It is OK to apply
pull request #11 before submitting this document.
Thanks,
J&S
On Thu, Apr 13,
On Tue, Apr 18, 2017 at 10:18:03PM +, Nick Sullivan wrote:
> On Sat, Apr 15, 2017 at 6:42 AM Ilari Liusvaara
> wrote:
> >
> > How do certificate type extensions (#9, #19 and #20) work with exported
> > authenticators?
> >
> > Where other extensions are either meaningless or are edditional info
Thanks for the review. I'm open to adding text indicating that the exported
authenticator SHOULD be sent using an application protected by the TLS
stream in question, but I don't want to remove the possibility of sending
the data over a secure secondary channel, depending on the application.
Nick
On Sat, Apr 15, 2017 at 6:42 AM Ilari Liusvaara
wrote:
> On Fri, Apr 14, 2017 at 02:44:25PM +0300, Ilari Liusvaara wrote:
> > On Thu, Apr 13, 2017 at 09:29:27PM -0700, Joseph Salowey wrote:
> > > Hey Folks,
> > >
> > > At the IETF 98 meeting in Chicago there was support in the room to
> adopt
> >
Thanks for the review.
Comments/questions inline. I put together a pull request with your
suggested changes here if you would like to review:
https://github.com/grittygrease/tls-exported-authenticator/pull/11
On Fri, Apr 14, 2017 at 4:44 AM Ilari Liusvaara
wrote:
> On Thu, Apr 13, 2017 at 09:29
On Thu, Apr 13, 2017 at 09:29:27PM -0700, Joseph Salowey wrote:
> At the IETF 98 meeting in Chicago there was support in the room to adopt
> draft-sullivan-tls-exported-authenticator [0]. We are looking for feedback
> on adopting this draft form the list. Please respond if you support the
> draft a
On Tue, Apr 18, 2017 at 11:29:31AM -0400, Victor Vasiliev wrote:
> I've read the draft, and I support its adoption. I believe that the
> mechanism
> is sound for its stated use.
>
> The second issue I have is with the question of when does authentication
> succeed. In TLS, by the time any party
On Fri, Apr 14, 2017 at 02:44:25PM +0300, Ilari Liusvaara wrote:
> On Thu, Apr 13, 2017 at 09:29:27PM -0700, Joseph Salowey wrote:
> > Hey Folks,
> >
> > At the IETF 98 meeting in Chicago there was support in the room to adopt
> > draft-sullivan-tls-exported-authenticator [0]. We are looking for f
I have read this draft and believe the final consensus version of this
function will be of high value to the HTTP ecosystem in particular - I
support TLS-WG adopting it.
On Fri, Apr 14, 2017 at 12:29 AM, Joseph Salowey wrote:
> Hey Folks,
>
> At the IETF 98 meeting in Chicago there was support i
I've also been reviewing this draft and support its adoption.
-Ben
On 04/14/2017 12:45 PM, Andrei Popov wrote:
>
> I’ve been reviewing this draft and support its adoption.
>
>
>
> Cheers,
>
>
>
> Andrei
>
>
>
> *From:* TLS [mailto:tls-boun...@ietf.org] *On Behalf Of *Joseph Salowey
> *Sent:
I’ve been reviewing this draft and support its adoption.
Cheers,
Andrei
From: TLS [mailto:tls-boun...@ietf.org] On Behalf Of Joseph Salowey
Sent: Thursday, April 13, 2017 9:29 PM
To: tls@ietf.org
Subject: [TLS] Call for adoption of draft-sullivan-tls-exported-authenticator
Hey Folks,
At the IE
On Thu, Apr 13, 2017 at 09:29:27PM -0700, Joseph Salowey wrote:
> Hey Folks,
>
> At the IETF 98 meeting in Chicago there was support in the room to adopt
> draft-sullivan-tls-exported-authenticator [0]. We are looking for feedback
> on adopting this draft form the list. Please respond if you suppo
12 matches
Mail list logo
