Hello,
Unfortunately the authors were not able to present the draft at the
IETF121 IPSECME session.
However we've just submitted a slightly updated version. The use
cases section was updated to explain how the proposed mechanism could
be used with MOBIKE.
-- Forwarded message -
F
Changed milestone "G-DOI for IKEv2 to IESG", resolved as "Done".
URL: https://datatracker.ietf.org/wg/ipsecme/about/
___
IPsec mailing list -- ipsec@ietf.org
To unsubscribe send an email to ipsec-le...@ietf.org
Tero Kivinen has requested publication of draft-ietf-ipsecme-g-ikev2-16 as
Proposed Standard on behalf of the IPSECME working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-ipsecme-g-ikev2/
___
IPsec mailing
Hi Valery,
Thank you for the comments, pls see my reply in line below
From: Valery Smyslov
Sent: Wednesday, November 6, 2024 12:31 AM
To: Jun Hu (Nokia) ; 'Wang Guilin' ;
'Daniel Van Geest' ; 'Scott Fluhrer
(sfluhrer)' ; 'tirumal reddy'
Cc: 'ipsec' ; 'Wang Guilin'
Subject: RE: [IPsec] Re: dra
I've read the draft and I support the adoption of it.
Regards & Thanks！
Wei PAN (潘伟)
> -Original Message-
> From: Antony Antony
> Sent: Wednesday, November 6, 2024 1:27 PM
> To: ipsec
> Cc: Antony Antony ; Steffen Klassert
>
> Subject: [IPsec] Re: New Versio
Hi,
I was extremely suprised that this draft claimed to have anything to do with
mobile networks. 3GPP specifications has _always_ mandated replay protection
for all 3GPP uses of IPsec, without exceptions. This has been a very clear
choice by 3GPP. I have been actively (as a delegate or backoff
