Hi Marco,
Thank you for your continuous reviews!
I agree with both your suggestion and nit, and will update in the next draft.
Cheers,
Rick
On Fri, 14 Jun 2024 at 15:59, Marco Tiloca via Datatracker <noreply@xxxxxxxx> wrote:
Reviewer: Marco Tiloca
Review result: Ready with Nits
I reviewed this document as part of the Applications and Real-Time (ART) Area
Review Team's ongoing effort to review all IETF documents being processed by
the IESG. These comments were written primarily for the benefit of the ART Area
Directors. Document authors, document editors, and WG Chairs should treat these
comments just like any other IETF Last Call comments.
I previously reviewed version -09, then the following version -10 addressed my
comments. This latest version -11 looks good, I have only one minor comment
below.
Best,
/Marco
[Section 5.2]
* In Section 4, bullet point 2, there has been an understandable change from
"MUST" to "MAY", as to the omission of the '0' Allocator Identifier from the
textual encoding of an ipn URI.
Consistent with that change, I think that the last sentence in Section 5.2
should be updated as follows.
OLD:
This means that the URIs dtn:none (Section 4.2.5.1.1 of [RFC9171]) and
ipn:0.0 both refer to the BPv7 'null' endpoint.
NEW:
This means that the URIs dtn:none (Section 4.2.5.1.1 of [RFC9171]), ipn:0.0,
and ipn:0.0.0 all refer to the BPv7 'null' endpoint.
[Nits]
* Section 7.2
- s/Mitigation for/The used mitigation for
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
