Re: [OPSEC] Genart last call review of draft-ietf-opsec-probe-attribution-05

Peter Yee <peter@akayla.com> Tue, 20 June 2023 06:25 UTC

Return-Path: <peter@akayla.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 523FDC13AE37; Mon, 19 Jun 2023 23:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 woVbhbUted9y; Mon, 19 Jun 2023 23:25:38 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27D5CC13AE36; Mon, 19 Jun 2023 23:25:37 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 1F1F7184EE4; Tue, 20 Jun 2023 02:25:37 -0400 (EDT)
Received: from [172.23.200.39] (p5522049-ipxg00v01osakachuo.osaka.ocn.ne.jp [180.29.71.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id D645B184FC9; Tue, 20 Jun 2023 02:25:35 -0400 (EDT)
User-Agent: Microsoft-MacOutlook/16.74.23061100
Date: Tue, 20 Jun 2023 15:25:31 +0900
From: Peter Yee <peter@akayla.com>
To: Justin Iurman <justin.iurman@uliege.be>, gen-art@ietf.org
CC: draft-ietf-opsec-probe-attribution.all@ietf.org, last-call@ietf.org, opsec@ietf.org
Message-ID: <245689FF-838E-4B7F-A73C-A77CD8CF6C3C@akayla.com>
Thread-Topic: Genart last call review of draft-ietf-opsec-probe-attribution-05
References: <168615663634.33016.16335583889761548966@ietfa.amsl.com> <a899795b-8d5b-b77c-acc8-edc2eb26fe7c@uliege.be>
In-Reply-To: <a899795b-8d5b-b77c-acc8-edc2eb26fe7c@uliege.be>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/sY4BZ3IjU-zxS3Ho_tNh6gTnfpY>
Subject: Re: [OPSEC] Genart last call review of draft-ietf-opsec-probe-attribution-05
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsec/>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2023 06:25:42 -0000

Hi, Justin,

	The changes are acceptable to me. None of my points were strongly enough held to be considered more than nits. Thank you for considering them.

		Kind regards,
		-Peter

On 6/18/23, 12:13 AM, "Justin Iurman" <justin.iurman@uliege.be> wrote:

    Hi Peter,

    We just published a new version (-06) that should address your review.

    Thanks,
    Justin

    On 6/7/23 18:50, Peter Yee via Datatracker wrote:
    > Reviewer: Peter Yee
    > Review result: Ready with Nits
    > 
    > I am the assigned Gen-ART reviewer for this draft. The General Area
    > Review Team (Gen-ART) reviews all IETF documents being processed
    > by the IESG for the IETF Chair.  Please treat these comments just
    > like any other last call comments.
    > 
    > For more information, please see the FAQ at
    > 
    > <https://wiki.ietf.org/en/group/gen/GenArtFAQ>.
    > 
    > Document: draft-ietf-opsec-probe-attribution-05
    > Reviewer: Peter Yee
    > Review Date: 2023-06-07
    > IETF LC End Date: 2023-06-08
    > IESG Telechat date: Not scheduled for a telechat
    > 
    > Summary: This informative specification indicates how good-intentioned
    > researchers may alert receivers (or intermediaries) of their probe traffic as
    > to what the probes are and how to contact the researchers. The document is
    > reasonably well written, but it has some nits that should be corrected prior to
    > publication. [Ready with nits]
    > 
    > Major issues: None
    > 
    > Minor issues: None
    > 
    > Nits/editorial comments:
    > 
    > Page 1, Abstract, last sentence: rearrange “what is its purpose” to “what its
    > purpose is” for parallel construction and ease of reading.
    > 
    > Page 3, 1st paragraph, 1st sentence: change “parties” to “parties’” (if this
    > should be plural) or “party’s” (if this should be singular).
    > 
    > Page 3, 1st paragraph, 2nd sentence: change “where” to “that”.
    > 
    > Page 3, 2nd bullet item: change “what is its purpose” to “what its purpose is”
    > for the same reasons as in the abstract.
    > 
    > Page 4, 1st paragraph after the two bullet items: change “one line” to
    > “one-line”.
    > 
    > Page 3, section 3, 1st paragraph, 1st sentence: Probe inclusion hasn’t even
    > been discussed at this point, so “As an alternative” is not appropriate here.
    > Either swap the in-band and out-of-band sections or reword. I prefer swapping,
    > but it’s possible this already happened once and hence the odd phrasing
    > considering the current ordering.
    > 
    > Page 5, 1st, 2nd, and 5th bullet items: change the first “a” to “an” if the
    > [RFCxxxx] reference is considered silent or all of them to “an” if the
    > reference is expected to be read as part of the sentence.
    > 
    > Page 6, 1st paragraph, last sentence at “multiple possibilities”: Are multiple
    > in-band options allowed or suggested? Is there “concatenation” of multiple
    > probe methods applied by different probe generators or for different research
    > purposes? If so or even if not, a discussion here might be worthwhile.
    > 
    > Page 6, section 5, 1st paragraph, 1st sentence: I’m not sure what is meant by
    > “will”. Do you mean “intent”?
    > 
    > Page 6, section 5, 2nd paragraph, last sentence: regarding “dynamic source
    > addresses”, why would this be a problem? The web server would presumably be on
    > the same IP address as probe generation, so, as the IP address changes, the web
    > server would appear on the new address. There might be a short period where
    > this isn’t the case, but it seems the overall inability to reach a web server
    > for the out-of-band option is small unless the address changes frequently.
    > 
    > Page 7, section 6, 1st paragraph: move “unsolicited” before “transit”.
    > 
    > Page 7, section 6, 2nd paragraph: change “identity” to “identify”.
    > 
    > Page 7, section 6, 2nd paragraph: It’s not clear to me that unsolicited transit
    > parties necessarily have much recourse or that the probe sender can effect much
    > change in their use other than not sending probes at all.
    > 
    > Page 7, section 6, 3rd paragraph, 1st sentence: remove the space between
    > “valid” and “?”.
    > 
    > Page 7, section 7, 2nd paragraph, 3rd sentence: move “would” before “this”.
    > 
    > 
    >