Re: [OPSEC] [IANA #1274499] expert review for draft-ietf-opsec-probe-attribution (well-known-uris)

Mark Nottingham <mnot@mnot.net> Fri, 23 June 2023 22:57 UTC

Return-Path: <mnot@mnot.net>
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 B879DC15C523 for <opsec@ietfa.amsl.com>; Fri, 23 Jun 2023 15:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="S/z/T7dE"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="JF/Y6wTy"
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 qcQQo2n3oSTR for <opsec@ietfa.amsl.com>; Fri, 23 Jun 2023 15:57:50 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 E5615C15152E for <opsec@ietf.org>; Fri, 23 Jun 2023 15:57:50 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 58EAF32009AA; Fri, 23 Jun 2023 18:57:46 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 23 Jun 2023 18:57:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1687561065; x=1687647465; bh=DLT+glTLarceWBjkjJcEsjw1H/qcc+Hi3oL GrEG9/3Y=; b=S/z/T7dEVN8b1VXgf3kYm2SIMPhvffCLNrLuPsZgjBH+rAhP5OM AHr/oEe5YuJJ1uG+yjJq2zwh7Z6rsRmGMnsMOuby7X+3PvJBkP7o3A8laPrSgoa1 286/aXt9dMqTMkCA/NAdnAlLgPkDjI4F6QVPhwcbjSmmWvtCLCu5a3tKdaGMNq3b hwXLN0+Gwli+6c880vSqZXTOEs4yBtVOJcagKGZ7z9y1lWbp4bRzhUb6Zdk7VP5l 7rFyatTowbayVg4/kS6uo0Q9U6LoDl2rA/wOSrHErbPK0+Plqh5341lOF7nferU8 vw90bLNCWzTerMD5rvNluRyo5+eYBpctgMg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1687561065; x=1687647465; bh=DLT+glTLarceWBjkjJcEsjw1H/qcc+Hi3oL GrEG9/3Y=; b=JF/Y6wTyPPHNGgu973jq6ozfDAbnOLwM76ZYH0azO8aOpRHwc0/ 2/09mfZwswvcHZpP6UYq9J14ENcN29DxFWNECExlv3QJpNI3Crj5gxvZCRRu/u3r ratz5oCT3jVfL8LDzA+BK57VexoIJzX0J2BBIKrccsmOl5iIvgsUDyCLn8+GYwJA qnJK0IjxTudZn8ZrWUXPgxyubNijoWSGWWFM9Ij+mItQ9G6K5cnnEod2WNs6y7bU dGiIJ2kawBQQs6Ywp7yP/pVPJe9Z7bqRyXI8EzOrXtmgzblua8x+vethaaE6Ta6k W9dH0zlfVb1Xes/DUYgK/bpFvj9yaGhKRbw==
X-ME-Sender: <xms:aSOWZLbGJGGOX4ogzPiiAJFHhNS_hFPCh2Bio1Lj7sOTtRVnlsI24w> <xme:aSOWZKY77rKXNTsRzohHUbioMH1GfTrgRHTmzPR0kRUBt8vvbQjnqktcQjxLP0CKJ 7Zv9flracRsDEPo8Q>
X-ME-Received: <xmr:aSOWZN_hbiEm-uGxZCa_yk6ZpHCA29xOrHa24g94dg8jVQo9NFNAH1TAPxWnH0kycdDKZ3m4YEbNzR4YX4VndfXFYKdOSMULNLFfPXPbEwNbJCRX25e73tDB>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgeeghedgudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffvefgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrth htvghrnhepveegheejledtkedtheehtdfgueevudfgffegiefgleetgeejudektdeuhfek ffdvnecuffhomhgrihhnpegvgigrmhhplhgvrdhnvghtpdhivghtfhdrohhrghdpihgrnh grrdhorhhgpdhmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:aSOWZBrym7tbmwAdoqNFz5bWgfrEy4b88G48juZ0mfJf_Rd70JXiPQ> <xmx:aSOWZGo1JfX3hGAgtmWiR8GC0FyX-YOg3cfDTZ-tV1yDqedkIWriVw> <xmx:aSOWZHSWc3lJ3wmp_NmjO3PKwEygPBW1_UNPBu8fHqrRS5f7pHOcQg> <xmx:aSOWZN3FFQGnxoIUrbHiM7j6JX_2eUKoPXcTWexcsiMZAqAQWjc19Q>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 23 Jun 2023 18:57:43 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <F7E63216-B5FD-4D68-8EEF-771CE23B5AE0@cisco.com>
Date: Sat, 24 Jun 2023 08:57:41 +1000
Cc: Justin Iurman <justin.iurman@uliege.be>, "drafts-expert-review@iana.org" <drafts-expert-review@iana.org>, "opsec@ietf.org" <opsec@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7605F63-B30C-4108-97D2-9EF6366FD151@mnot.net>
References: <RT-Ticket-1274499@icann.org> <rt-5.0.3-2205261-1686155005-884.1274499-37-0@icann.org> <rt-5.0.3-2207827-1686155260-1464.1274499-37-0@icann.org> <35684062-23D9-46F9-9EAC-329FBE7F7B11@mnot.net> <fbed81e1-8723-8f8e-2260-b03421c10bfa@uliege.be> <F924ABDE-8D59-4D78-834A-A38265F4A847@mnot.net> <5bc5be3f-19f2-ea2b-17e3-5d1b6bab9d37@uliege.be> <B52E5702-8DAA-4CA4-8972-B6D55BC936A9@mnot.net> <F7E63216-B5FD-4D68-8EEF-771CE23B5AE0@cisco.com>
To: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/rAYtX1GE04Npx6nVN-3RbsomEbk>
Subject: Re: [OPSEC] [IANA #1274499] expert review for draft-ietf-opsec-probe-attribution (well-known-uris)
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: Fri, 23 Jun 2023 22:57:55 -0000

Looks great FWIW - thanks!

> On 23 Jun 2023, at 5:25 pm, Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org> wrote:
> 
> Hello Mark,
> 
> Thank you for your suggestion, we have added some text in the just submitted revised I-D.
> 
> Regards
> 
> -éric
> 
> On 20/06/2023, 01:39, "OPSEC on behalf of Mark Nottingham" <opsec-bounces@ietf.org <mailto:opsec-bounces@ietf.org> on behalf of mnot=40mnot.net@dmarc.ietf.org <mailto:40mnot.net@dmarc.ietf.org>> wrote:
> 
> 
> Hi Justin,
> 
> 
> Thanks for that.
> 
> 
> Reading the updates, the document still assumes the reader knows what is meant by 'active measurements' and 'probes' -- it isn't clear whether these are purely IP-layer, or they might be application-layer (e.g., in HTTP or SMTP) as well, or somewhere in between. Clarifying what is and isn't an active measurement / probe -- even if the definition is expansive -- would be very helpful.
> 
> 
> Cheers,
> 
> 
> 
> 
>> On 18 Jun 2023, at 1:11 am, Justin Iurman <justin.iurman@uliege.be <mailto:justin.iurman@uliege.be>> wrote:
>> 
>> Hi Mark,
>> 
>> We just published a new version (-06) that addresses your comments.
>> 
>> Thanks,
>> Justin
>> 
>> On 6/9/23 07:34, Mark Nottingham wrote:
>>> Hi Justin,
>>>> On 9 Jun 2023, at 6:32 am, Justin Iurman <justin.iurman@uliege.be <mailto:justin.iurman@uliege.be>> wrote:
>>>> 
>>>> Hi Mark,
>>>> 
>>>> Thanks for the review. Please see inline ([JI]).
>>>> 
>>>> On 6/8/23 05:07, Mark Nottingham wrote:
>>>>> Hi Sabrina et al,
>>>>> The registration is approved.
>>>>> Feedback on the document:
>>>>> * Section 2.2 says 'As defined in Section 8, the probe description file must be made available at "https://example.net/.well-known/probing.txt"' <https://example.net/.well-known/probing.txt&quot;&#39;>. This is not correct, as it hardcodes the domain 'example.net' and the scheme 'https'. If you want to only use the scheme 'https', that should be explicitly required (remember, Well-Known URIs are defined for many URI schemes).
>>>> 
>>>> [JI] Would "/.well-known/probing.txt" be better instead?
>>> Yes.
>>>>> * It would be helpful to more clearly state the purpose of the Probe Description up front; to a new reader, it's not clear whether it's describing a particular probe, or a policy for probing (which could be implied by the normative reference to RFC9116). It might help to more clearly and definitely describe what a probe is and is not.
>>>> 
>>>> [JI] We'll craft some text to make that clearer.
>>>> 
>>>>> * What is "URI inclusion" (mentioned in Section 3)?
>>>> 
>>>> [JI] "URI inclusion" is the in-band probe attribution (the mention was removed, it was rephrased based on Peter's review).
>>>> 
>>>> Thanks,
>>>> Justin
>>>> 
>>>>> Cheers,
>>>>>> On 8 Jun 2023, at 2:27 am, Sabrina Tanamal via RT <drafts-expert-review@iana.org <mailto:drafts-expert-review@iana.org>> wrote:
>>>>>> 
>>>>>> Hi Mark (cc: opsec wg),
>>>>>> 
>>>>>> As the designated expert for the Well-Known URIs registry, can you review the proposed registration in draft-ietf-opsec-probe-attribution-05 for us? Please see
>>>>>> 
>>>>>> https://datatracker.ietf.org/doc/draft-ietf-opsec-probe-attribution/ <https://datatracker.ietf.org/doc/draft-ietf-opsec-probe-attribution/>
>>>>>> 
>>>>>> The due date is June 21st.
>>>>>> 
>>>>>> If this is OK, when the IESG approves the document for publication, we'll make the registration at:
>>>>>> 
>>>>>> https://www.iana.org/assignments/well-known-uris <https://www.iana.org/assignments/well-known-uris>
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> Sabrina Tanamal
>>>>>> Lead IANA Services Specialist
>>>>>> 
>>>>> --
>>>>> Mark Nottingham https://www.mnot.net/ <https://www.mnot.net/>
>>>>> _______________________________________________
>>>>> OPSEC mailing list
>>>>> OPSEC@ietf.org <mailto:OPSEC@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/opsec <https://www.ietf.org/mailman/listinfo/opsec>
>>> --
>>> Mark Nottingham https://www.mnot.net/ <https://www.mnot.net/>
> 
> 
> --
> Mark Nottingham https://www.mnot.net/ <https://www.mnot.net/>
> 
> 
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org <mailto:OPSEC@ietf.org>
> https://www.ietf.org/mailman/listinfo/opsec <https://www.ietf.org/mailman/listinfo/opsec>
> 
> 
> 

--
Mark Nottingham   https://www.mnot.net/