Re: [IPsec] Artart last call review of draft-ietf-ipsecme-rfc8229bis-06

2022-05-23 Thread Valery Smyslov
Hi Mark, thank you for your review! Regards, Valery. > -Original Message- > From: Mark Nottingham via Datatracker [mailto:nore...@ietf.org] > Sent: Sunday, May 22, 2022 7:12 AM > To: a...@ietf.org > Cc: draft-ietf-ipsecme-rfc8229bis@ietf.org; ipsec@ietf.org; > last-c...@ietf.org > S

Re: [IPsec] Tsvart last call review of draft-ietf-ipsecme-rfc8229bis-06

2022-05-23 Thread Valery Smyslov
Hi Joseph, thank for your review, much appreciated. More inline. > Reviewer: Joseph Touch > Review result: Ready with Issues > > This document has been reviewed as part of the transport area review team's > ongoing effort to review key IETF documents. These comments were written > primarily for

Re: [IPsec] ESP Signally to higher layers

2022-05-23 Thread Robert Moskowitz
Thanks Chris. Helps a bit. On 5/20/22 20:27, Christian Hopps wrote: Robert Moskowitz writes: This is an item that goes back to the beginning of ESP work: Minimally, how does the higher level 'learn' that it is secure: E2E or TE2TE? Encrypted/Authenticated/CrCed...  ? And as ESP has a se

Re: [IPsec] ESP Signally to higher layers

2022-05-23 Thread Robert Moskowitz
On 5/21/22 07:13, Michael Richardson wrote: Robert Moskowitz wrote: > This is an item that goes back to the beginning of ESP work: > Minimally, how does the higher level 'learn' that it is secure: Are you asking how *TCP* learns of this, or how an application with an open socket(2)

Re: [IPsec] [Tsv-art] Tsvart last call review of draft-ietf-ipsecme-rfc8229bis-06

2022-05-23 Thread to...@strayalpha.com
Hi Valery, Notes below. Joe > On May 23, 2022, at 4:53 AM, Valery Smyslov wrote: > > Hi Joseph, > > thank for your review, much appreciated. More inline. > >> Reviewer: Joseph Touch >> Review result: Ready with Issues >> >> This document has been reviewed as part of the transport area revie