IETF Logo Mail Archive

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

Justin Iurman <justin.iurman@uliege.be> Thu, 08 June 2023 20:32 UTC

Return-Path: <justin.iurman@uliege.be>
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 22F41C151063 for <opsec@ietfa.amsl.com>; Thu, 8 Jun 2023 13:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.395
X-Spam-Level:
X-Spam-Status: No, score=-4.395 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uliege.be
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 AN8WMDurxDn6 for <opsec@ietfa.amsl.com>; Thu, 8 Jun 2023 13:32:17 -0700 (PDT)
Received: from serv108.segi.ulg.ac.be (serv108.segi.ulg.ac.be [139.165.32.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAFDBC151089 for <opsec@ietf.org>; Thu, 8 Jun 2023 13:32:17 -0700 (PDT)
Received: from [192.168.1.62] (125.179-65-87.adsl-dyn.isp.belgacom.be [87.65.179.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by serv108.segi.ulg.ac.be (Postfix) with ESMTPSA id 1D3F3200BE51; Thu, 8 Jun 2023 22:32:15 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 serv108.segi.ulg.ac.be 1D3F3200BE51
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uliege.be; s=ulg20190529; t=1686256335; bh=CJ5OPJLqd2HL0z2Q5TvgstflnGAynuzX2YFE+8PXxOc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=P6+FzDV9IrPYQh+MNBXu1XsfYBtO0ajixKuhh/nAF1nRAr8BPaKwYQC9iFY1PDNuD PJnXjozouvTUZpNfRMcpB8wHGexqqeL9gAYER8+E0cYiq+MFQx9e09oz+WQymtERq4 xAYXQjJPu6UGPWUZXPxjUy4GBnV5ZbFRbWpyQkpiVP8fEkY4W0pTw3LrDVfItrx0zj 1jIpcP7i3lAj1GlJ/+ndfrymB9slBq86/6D2U1gH9cy06fGstjlCzbcAlb75ux0aD/ pYkDoOkzxGRNLpfCvUrDWJJnVj31vULe3rlPGAwKSsyo10gZZpGSI0YaaCskUyp8XH IQk4+ahucfEgQ==
Message-ID: <fbed81e1-8723-8f8e-2260-b03421c10bfa@uliege.be>
Date: Thu, 08 Jun 2023 22:32:14 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US
To: Mark Nottingham <mnot=40mnot.net@dmarc.ietf.org>, drafts-expert-review@iana.org
Cc: opsec@ietf.org
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>
From: Justin Iurman <justin.iurman@uliege.be>
In-Reply-To: <35684062-23D9-46F9-9EAC-329FBE7F7B11@mnot.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/q1DtdmijSWq7wY72M8VfRfh58PY>
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: Thu, 08 Jun 2023 20:32:22 -0000

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"'. 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?

> * 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> 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/
>>
>> 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
>>
>> Thanks,
>>
>> Sabrina Tanamal
>> Lead IANA Services Specialist
>>
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec

v2.23.0 | Report a Bug | By Email