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

["Eric Vyncke (evyncke)" <[e-mail]>]

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" <[e-mail] <mailto:[e-mail]> on behalf of mnot=[e-mail] <mailto:[e-mail]>> 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 <[e-mail] <mailto:[e-mail]>> 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 <[e-mail] <mailto:[e-mail]>> 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 <[e-mail] <mailto:[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/ <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
>>>> [e-mail] <mailto:[e-mail]>
>>>> 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
[e-mail] <mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/opsec <https://www.ietf.org/mailman/listinfo/opsec>