Ok, all good with me. Thanks Valery!
Sent using a virtual keyboard on a phone
> On Nov 30, 2022, at 12:03, Valery Smyslov wrote:
>
> We are converging :-)
>
>>> I'm a bit reluctant to add all this information to the abstract. It is
>>> already a bit too long
>>> (since Éric and Warren sugges
We are converging :-)
> > I'm a bit reluctant to add all this information to the abstract. It is
> > already a bit too long
> > (since Éric and Warren suggested to augment it with the explanation text of
> > how
> > this design helps in situation when PQ algorithms are less trusted). So
> > cur
On Wed, 30 Nov 2022, Valery Smyslov wrote:
Yes I meant the abstract :)
I'm a bit reluctant to add all this information to the abstract. It is already
a bit too long
(since Éric and Warren suggested to augment it with the explanation text of how
this design helps in situation when PQ algorithm
Wouters' Discuss on
draft-ietf-ipsecme-ikev2-multiple-ke-10: (with DISCUSS and COMMENT)
Hi Paul, Hi Valery
@Paul Wouters <mailto:p...@nohats.ca> Many thanks for your thorough review of
the draft, really appreciate that.
Where to put the "Design Criteria" section has
aft-ietf-ipsecme-ikev2-multiple...@ietf.org; ipsecme-cha...@ietf.org;
> ipsec@ietf.org WG; Tero Kivinen
> Subject: Re: [IPsec] Paul Wouters' Discuss on
> draft-ietf-ipsecme-ikev2-multiple-ke-10: (with DISCUSS and
> COMMENT)
>
> On Tue, 29 Nov 2022, Valery Sm
Hi Paul, Hi Valery
@Paul Wouters Many thanks for your thorough review of the
draft, really appreciate that.
Where to put the "Design Criteria" section has been bothering me for quite
a while. Personally, I prefer to have this section to be moved as an
appendix.
I'll update Valery's PR with this
On Tue, 29 Nov 2022, Valery Smyslov wrote:
### IANA entries mentions in the Introduction ?
Shouldn't the introduction mention this draft introduces the IKE_FOLLOWUP_KE
Exchange
and the STATE_NOT_FOUND Notify Message Type, along with additional entries to
the
(now renamed) Key Exchanges Method
Hi Paul,
thank you for your thorough review, please see inline.
> -Original Message-
> From: Paul Wouters via Datatracker [mailto:nore...@ietf.org]
> Sent: Tuesday, November 29, 2022 12:09 AM
> To: The IESG
> Cc: draft-ietf-ipsecme-ikev2-multiple...@ietf.org; ipsecme-cha...@ietf.org;
> i
Paul Wouters via Datatracker wrote:
> Also RFC 5723 states: ``` The keys and cryptographic protection
> algorithms should be at least 128 bits in strength. ``` IF we live in
> Grover universe, perhaps that should be 256 bits in strength? And since
> we are making things quantum s
Paul Wouters has entered the following ballot position for
draft-ietf-ipsecme-ikev2-multiple-ke-10: Discuss
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.)
Please refer
10 matches
Mail list logo
