Sean Turner has requested publication of
draft-ietf-tls-exported-authenticator-13 as Proposed Standard on behalf of the
TLS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-tls-exported-authenticator/
Great! This document is now ready to progress to the AD.
spt
> On Jun 26, 2020, at 20:00, Nick Sullivan wrote:
>
> TLSWG and Chairs,
>
> I've submitted draft -13 with the appropriate changes.
>
> Best,
> Nick
>
> On Tue, Jun 16, 2020 at 10:23 AM Sean Turner wrote:
> Hi!
>
> This message cl
Just a reminder to please have a look at this draft.
spt
> On Jun 19, 2020, at 23:39, Sean Turner wrote:
>
> Thanks to Chris for uploading the WG version of the draft.
>
> If you have some time over the next couple of weeks please take the time to
> review this draft. The intent is to issue a
Dear Joseph Salowey,
The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request.
tls Session 1 (1:40 requested)
Tuesday, 28 July 2020, Session III 1410-1550
Room Name: Room 6 size: 6
---
On Thu, Jul 2, 2020 at 10:21 AM Jonathan Hoyland
wrote:
> Hi All,
>
> For those interested, I've been working on a formal analysis of DCs the
> results of which should appear online in the next few days.
> I'll post to the list when it's up.
>
> Great! Thanks.
> In summary I managed to prove a s
Hi All,
For those interested, I've been working on a formal analysis of DCs the
results of which should appear online in the next few days.
I'll post to the list when it's up.
In summary I managed to prove a server only version of DCs secure (i.e.
does not violate any of the properties in Appendi
Hi Yoav,
> If that’s something the group wants, we can add it, but it’s not generally a
> good thing for a protocol to have two ways of expressing the same thing.
I saw it more as a "compression" mechanism for those cases where an extension
doesn't carry additional content.
Ciao
Hannes
Yoav
>
