Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

Hi, First of all thanks to the WG chairs for the request and Joe for the review. It is much better to catch things earlier as it is often less disruptiove for the WG to deal with the feedback at this stage. So I don't see any way the reviewer can change their review ones it has been posted. The

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

Joseph Touch writes: > I’m not aware that it’s possible for me to do this. It might be the > transport chairs who do. That is not normally done during the reviews. If the reviewer is happy with the changes authors have done, then thats it. The document will get rereviewed during the last call and

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

HI, Christian, I’m not aware that it’s possible for me to do this. It might be the transport chairs who do. Joe > On Jan 5, 2021, at 1:36 AM, Christian Hopps wrote: > > Hi Joe, > > Could you also clear the not-ready mark in the datatracker? > > Thanks, > Chris. > >> On Dec 23, 2020, at 5:3

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

Hi Joe, Could you also clear the not-ready mark in the datatracker? Thanks, Chris. > On Dec 23, 2020, at 5:33 PM, Joseph Touch wrote: > > Looks good - thanks. > > Joe > >> On Dec 19, 2020, at 8:44 PM, Christian Hopps > > wrote: >> >> Hi Joe, >> >> Thanks so much

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

Looks good - thanks. Joe > On Dec 19, 2020, at 8:44 PM, Christian Hopps wrote: > > Hi Joe, > > Thanks so much for your review and feedback. I have just published a new > version of the draft that I believe covers the concerns you raised in the > review. > > New: https://tools.ietf.org/html

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

Hi Joe, Thanks so much for your review and feedback. I have just published a new version of the draft that I believe covers the concerns you raised in the review. New: https://tools.ietf.org/html/draft-ietf-ipsecme-iptfs-05 Changes: ht

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

> On Dec 19, 2020, at 7:41 PM, Joseph Touch wrote: > > > >> On Dec 19, 2020, at 1:17 AM, Christian Hopps > > wrote: >> >> Changes are underway. One comments inline. >> >>> On Dec 4, 2020, at 11:42 AM, Joseph Touch >> > wrote: >>> >>> H

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

> On Dec 19, 2020, at 2:16 PM, Christian Hopps wrote: > > > >> On Dec 4, 2020, at 3:14 AM, Christian Hopps > > wrote: > > Looking through this list I realized one thing. We are not technically > defining a new tunnel here. We are defining a new payload for the alre

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

> On Dec 19, 2020, at 1:17 AM, Christian Hopps wrote: > > Changes are underway. One comments inline. > >> On Dec 4, 2020, at 11:42 AM, Joseph Touch > > wrote: >> >> Hi, Christian, > > [...] > There is no clear utility in having the blockoffset point past th

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

Changes are underway. One comments inline. > On Dec 4, 2020, at 11:42 AM, Joseph Touch wrote: > > Hi, Christian, [...] >>> There is no clear utility in having the blockoffset point past the end of >>> the >>> current packet. It serves – at best – as only a partially useful check on >>> the >

Re: [IPsec] [Tsv-art] Tsvart early review of draft-ietf-ipsecme-iptfs-03

Hi, Christian, > On Dec 4, 2020, at 12:14 AM, Christian Hopps wrote: > > Hi Joseph, > > First, thanks for your review. This is an initial reply to clarify a couple > points [inline]. > >> On Dec 4, 2020, at 1:26 AM, Joseph Touch via Datatracker >> wrote: >> >> Reviewer: Joseph Touch >> Rev