Dear Dhruv Dhody,
The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request.
pce Session 1 (1:30 requested)
Friday, 11 November 2022, Session II 1200-1330
Room Name: Kensington 2 size: 350
Thanks Russ & Adrian!
I have updated the working copy with this commit ->
https://github.com/dhruvdhody/draft-dhody-pce-pceps-tls13/commit/05027a5251a0290bd8c960b2c03aa2b13ae01c79
Dhruv
On Fri, Oct 14, 2022 at 8:10 PM Adrian Farrel wrote:
> Wfm, thnx
>
> -Original Message-
> From:
Wfm, thnx
-Original Message-
From: Russ Housley
Sent: 14 October 2022 14:58
To: Adrian Farrel
Cc: draft-dhody-pce-pceps-tl...@ietf.org; pce@ietf.org
Subject: Re: Thinking about draft-dhody-pce-pceps-tls13
Maybe the phrase should be: PCEP implementations that support TLS 1.3 MUST
...
Maybe the phrase should be: PCEP implementations that support TLS 1.3 MUST ...
Russ
> On Oct 14, 2022, at 9:28 AM, Adrian Farrel wrote:
>
> Thanks, Rus.
>
> What I didn't express well (don't write emails when you have been doing hard
> concentration work for 9.5 hours straight!) is that it is
Thanks, Rus.
What I didn't express well (don't write emails when you have been doing hard
concentration work for 9.5 hours straight!) is that it is possible to think
that this work is telling all PCEP implementations what they must do. I have
spoken to one person who was very worried that this
Adrian:
TLS 1.2 does not have early data, and the algorithm registries arefor TLS 1.2
and TLS 1.3 are separate, o I do not think there is confusion. That said, I do
not object to adding the phrase.
Russ
> On Oct 13, 2022, at 5:42 PM, Adrian Farrel wrote:
>
> Hi,
>
> Thanks for kicking off
