[Edm] Few comments on draft-edm-protocol-greasing-02

Cullen Jennings <fluffy@iii.ca> Tue, 31 October 2023 00:57 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: edm@ietfa.amsl.com
Delivered-To: edm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27121C14CF1B for <edm@ietfa.amsl.com>; Mon, 30 Oct 2023 17:57:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qdUSHV-CVTQa for <edm@ietfa.amsl.com>; Mon, 30 Oct 2023 17:57:48 -0700 (PDT)
Received: from smtp83.iad3b.emailsrvr.com (smtp83.iad3b.emailsrvr.com [146.20.161.83]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81DB9C15107F for <edm@iab.org>; Mon, 30 Oct 2023 17:57:48 -0700 (PDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp3.relay.iad3b.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 38022400B7; Mon, 30 Oct 2023 20:57:47 -0400 (EDT)
From: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.100.2.1.4\))
Date: Mon, 30 Oct 2023 18:57:36 -0600
Cc: Tommy Pauly <tpauly@apple.com>
To: edm@iab.org
Message-Id: <E601A23F-D22A-422E-9739-E04BF85EFB46@iii.ca>
X-Mailer: Apple Mail (2.3774.100.2.1.4)
X-Classification-ID: 3577e199-373c-4c49-852c-b0dff2035475-1-1
Archived-At: <https://mailarchive.ietf.org/arch/msg/edm/a4QTl3gBqJo6n3d4uK5vdAb-pTI>
Subject: [Edm] Few comments on draft-edm-protocol-greasing-02
X-BeenThere: edm@iab.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Evolvability, Deployability, & Maintainability \(Proposed\) Program" <edm.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/edm>, <mailto:edm-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/edm/>
List-Post: <mailto:edm@iab.org>
List-Help: <mailto:edm-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/edm>, <mailto:edm-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2023 00:57:53 -0000

At a high level this document looks fine and I have no complaints with publishing it more or less as is. However, I do see one significant area that I think would improve it. I imagine this has been discussed before so take with large grain of salt. 

My experience with interoperability problems across a wide range of protocols is mishandling of code points is far less often the problem that breaks the future and a much more common issue is:

1) incorrect assumptions on ordering of options and/or,
2) incorrect assumptions that the bits will forever land in the same location in the packet. 

I view both designing and exercising the protocol to deal with these issues as a form of “greasing”. I wish the draft talked about that.

I think the draft could be a bit more concrete on exactly how to write IANA sections. 

On the trivial nits category, it seems like this draft could be much shorter and be very concrete about the recommendations. To put it bluntly, one of the LLM summary tools I used made content that I liked better. I’m not volunteering to do it but it might be worth of pass of “how much can be removed” from the draft. This is deeply an editorial comment and not something I care much about one way or the other.

No change needed for just as FWIW feedback, the draft failed to convince me that a large range of code points for greasing was going to offer much benefit over a very small number of code points.