> On Sep 7, 2021, at 3:13 AM, Paul Wouters <paul.wout...@aiven.io> wrote: > > > On Mon, Sep 6, 2021 at 11:27 PM Christian Hopps <cho...@chopps.org > <mailto:cho...@chopps.org>> wrote: >> On Sep 6, 2021, at 4:16 PM, Tero Kivinen <kivi...@iki.fi >> <mailto:kivi...@iki.fi>> wrote: >> >> Christian Hopps writes: >>> At this point please suggest the text that you would like changed or >>> added to this document. I object to having to add it, but you are >>> the chair and you are blocking this document so we must accept. >> >> I am not talking here as chair, I am talking here as an developer who >> see no point of making crappy protocol. Thats why I said you either > > You are asking for the changes after WGLC before you send the document to the > IESG otherwise it would already be at the IESG. This is specifically a > chair-only action you are taking. > > Process note: Tero has been vocal about this issue all through the process. I > do not think it is fair to say this appeared after WGLC. And it was also > raised by the transport area expert review.
Unfortunately this is not true. This point was only raised after WGLC was completed (otherwise it wouldn’t have completed :) and after I submitted the shepherd write-up. The fact that the document has been blocked on this for more than 1 IETF cycle is perhaps creating some fog here. > I'd prefer to see this discussed out properly. Not just "submit text to make > the document go forward". It seems rather a core issue of the protocol. It was resolved with the transport area by adding the drop timer. I added more text to highlight and even recommend the drop timer in the latest revision, but it is apparently not enough. I believe Tero really wants to allow for sending packets as soon as he can, even if it means complexity in the implementation (keeping 1/2 processed outer packets around), I believe this is unneeded, but see no reason to disallow it either — and certainly not to block the document. I’m just asking Tero to provide text that will make him happy, rather than keep going around and around with me not getting the text correct. Thanks, Chris. > > Paul
_______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
