Eric Rescorla has entered the following ballot position for
charter-ietf-emu-04-01: Yes
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
The document, along with other
I am pleased to announce that Mohit Sethi has agreed to serve as co-chair
for EMU.
Thanks to Mohit!
-Ekr
___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu
On Mon, Jan 4, 2021 at 6:08 AM Alan DeKok wrote:
> On Jan 3, 2021, at 10:44 PM, Martin Thomson wrote:
> > # Key Schedule
> >
> > The other thing I observe is the way that this slices up the exporter
> output. This was something that old versions of TLS did, but TLS 1.3 did
> away with. Though
On Fri, Jan 29, 2021 at 12:02 PM Alan DeKok
wrote:
> This is a new message to summarize history, requirements, etc. for
> EAP-TLS and TLS 1.3. The focus here is the requirements for EAP-TLS, and
> how the 0x00 commitment message versus CloseNotify meets those. I'll
> ignore the exporter chang
On Mon, Feb 1, 2021 at 7:42 AM Alan DeKok wrote:
> On Feb 1, 2021, at 9:55 AM, Eric Rescorla wrote:
> > Let's take the second case first. If the server is sending (or
> > potentially sending) post-handshake messages after the client's second
> > flight (e.g.
On Mon, Feb 1, 2021 at 8:22 AM Alan DeKok wrote:
> On Feb 1, 2021, at 11:09 AM, Eric Rescorla wrote:
> > That's not what I'm proposing. I'm only talking about the case where the
> server says this after flight (2).
>
> OK, my misreading of the text.
>
On Thu, Feb 4, 2021 at 12:57 AM John Mattsson
wrote:
> Hi,
>
>
>
> I think the idea of a new TLS extension to make TLS 1.3 and EAP-TLS
> interact better is a very promising idea. This would probably take some
> time to get specified and implemented so it is probably a future
> optimization/simpli
On Thu, Feb 4, 2021 at 6:29 AM Eric Rescorla wrote:
>
>
> On Thu, Feb 4, 2021 at 12:57 AM John Mattsson
> wrote:
>
>> Hi,
>>
>>
>>
>> I think the idea of a new TLS extension to make TLS 1.3 and EAP-TLS
>> interact better is a very promising