Your latest addition is good for me
Thank you
-éric
From: Valery Smyslov
Date: Monday, 15 April 2024 at 09:43
To: Eric Vyncke (evyncke) , 'The IESG'
Cc: draft-ietf-ipsecme-ikev2-auth-annou...@ietf.org
, ipsecme-cha...@ietf.org
, ipsec@ietf.org , kivi...@iki.fi
Subject: RE: Éric Vyncke's
Thank you, Valery, for your 2nd reply and for allowing me to reply w/o on-line
access to the I-D when I replied.
One last comment below as EVY2>
All comments were non-blocking anyway :)
-éric
From: Valery Smyslov
Date: Friday, 12 April 2024 at 09:40
To: Eric Vyncke (evyncke) , 'The IESG'
Thank you, Valery, for the prompt reply.
See below for EVY>
Regards
-éric
From: Valery Smyslov
Date: Thursday, 11 April 2024 at 15:23
To: Eric Vyncke (evyncke) , 'The IESG'
Cc: draft-ietf-ipsecme-ikev2-auth-annou...@ietf.org
, ipsecme-cha...@ietf.org
, ipsec@ietf.org , kivi...@iki
Let me reply to Hannes’ statement: “Integrating the functionality into SCHC
alone is not enough.”
I consider SCHC as a technical mean and not an end. I.e., it is not about
adding IPsec to SCHC but rather about using SCHC to compress IPsec (= ESP &
IKE). The SCHC WG did a similar work with
that this is not the favorite solution for everyone
[2] Med has already acted ;)
From: Eric Vyncke (evyncke)
Date: Wednesday, 4 October 2023 at 16:51
To: Erik Nygren , mohamed.boucad...@orange.com
Cc: Chris Box , ADD Mailing list
Subject: Re: [Add] Summary & Next Steps RE: DNR's SvcParams encoding
H
Hello Valery
Thanks for your prompt reply. Please look below for EV>
Regards
-éric
On 27/04/2023, 08:53, "Valery Smyslov" mailto:s...@elvis.ru>>
wrote:
Hi Éric,
thank you for your comments. Please see inline
(I will only address some of your comments).
>
Valery, it works fine for me.
Obtenir Outlook pour Android<https://aka.ms/AAb9ysg>
De : Valery Smyslov
Envoyé : jeudi 1 décembre 2022, 12:25
À : Eric Vyncke (evyncke) ; 'The IESG'
Cc : draft-ietf-ipsecme-ikev2-multiple...@ietf.org
; ipsecme-cha...@ie
Hello Valery,
Thanks for your suggested text for the abstract, may I suggest a little more
concise (albeit less precise) text for the 2nd paragraph (up to the authors of
course):
The primary application of this feature in IKEv2 is the ability to
perform one or more
Hello Valery,
TL;DR: Thanks for your reply and your comments. I agree with them ;-)
If you want a more detailed reply, then look for EV> below
Regards
-éric
On 29/11/2022, 18:47, "Valery Smyslov" wrote:
Hi Éric,
thank you for your comments. Please see inline.
>
Don
You were faster than the light ;-)
Indeed, the changes are ok for me and, more important, I do believe that they
have improved the document. I also noticed that the tree is not updated, but I
will trust you (and your AD) on this point. I will clear my DISCUSS shortly.
Thank you for your
Thank you, Don, as you may have seen I have cleared by DISCUSS
Regards
-éric
On 31/08/2022, 14:48, "Don Fedyk" wrote:
Hi Eric, I have posted the -10 version with the changes.
Thanks
Don
-Original Message-
From: Eric Vyncke (evyncke)
Sent: Wednesd
Don,
Thank you for your email. Indeed, IETF drafts must use the documentation
prefixes and the new ones fit this rule ;-)
I am clearing my DISCUSS as soon as a revised I-D is published.
Regards
-éric
On 30/08/2022, 23:19, "Don Fedyk" wrote:
Hi Eric
I have addressed your comments
Chris,
The -17 version indeed addresses one of the 4 DISCUSS points, namely the hop
limit vs. TTL. Thank you for this.
I am far from being convinced that the added text about ICMP handling is rock
solid though. While I cannot point a specific issue, I fear that aggregating
and fragmenting
Thank you,
As you may have seen, I have referred to your review when balloting on this I-D.
Regards
-éric
On 19/08/2022, 00:49, "Int-dir on behalf of Tatuya Jinmei via Datatracker"
wrote:
Reviewer: Tatuya Jinmei
Review result: Ready
I've reviewed version 13 of
or, and we would *not* benefit from delaying this work, or making the
encapsulation more generic.
Thanks,
Chris.
"Eric Vyncke (evyncke)" writes:
> Dear intarea/int-dir,
>
>
>
> I have a request for you about https://datatracker.ietf.org/
Dear intarea/int-dir,
I have a request for you about
https://datatracker.ietf.org/doc/draft-ietf-ipsecme-iptfs/
While the draft name looks like it is about IPsec, it appears to me as an
“aggregation and fragmentation” tunneling mechanism [1], i.e., it uses the ESP
Next-header field (an IP
Goedendag Paul, ;-)
Thank you for your reply, Valery has also replied to my comments (and I agree
with Valery's reply).
Have a look below for EV>
Regards
-éric
On 10/08/2022, 02:40, "Paul Wouters" wrote:
On Tue, 9 Aug 2022, Éric Vyncke via Datatracker wrote:
> ### Section 3 No
Hello Valery,
Thanks again for the discussion, it should help improving the I-D.
Look below for EV2>
Cheers
-éric
On 09/08/2022, 18:03, "Valery Smyslov" wrote:
Éric, please see my comments below.
For readability I removed some of the stuff we agreed upon.
> Hello Valery,
>
Hello Valery,
Thank you for the prompt reply.
It looks like Erik Kline could be my twin brother as we often emit the same
comments. FYI, I never read other ADs' ballot to avoid being biased.
I agree with all your replies and explanations except when there is EV>
Regards
-éric
On
Valery
Thank you for such a prompt reply.
I agree with all your comments and suggestions for new text.
Regards
-éric
-Original Message-
From: Valery Smyslov
Date: Wednesday, 2 March 2022 at 08:10
To: Eric Vyncke , 'The IESG'
Cc: "draft-ietf-ipsecme-ikev2-intermedi...@ietf.org"
,
Re-bonjour Med,
The suggested text sounds good to me. About the "MUST" in section 5, let's
agree that we disagree on this one but this is NOT blocking.
There is another "repsonder" at the end of section 5 and I loved your reference
to RFC 8801 (Monday morning smile!)
Regards
-éric
Tero,
Indeed, I should have checked the IANA IKEv2 registry before writing my
comment. The IANA table has already the relevant entries for USE_PPK and others
(you probably asked separately before).
My bad, sorry about that
-éric
On 04/01/2020, 03:11, "iesg on behalf of Tero Kivinen" wrote:
Yoav,
Thank you for your quick reply, the explanations and the actions. Obviously, I
will clear my DISCUSS upon a new revision of the document.
About the nonce / IIV, may I suggest to add the explanation below to the
terminology section?
Regards
-éric
PS: thank you for using a É in my first
23 matches
Mail list logo
