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

[Mark Nottingham <[e-mail]>]

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).

* 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.

* What is "URI inclusion" (mentioned in Section 3)?

Cheers,


> On 8 Jun 2023, at 2:27 am, Sabrina Tanamal via RT <[e-mail]> 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/