Roni, thanks for your comments
- We traditionally do not specify length, one reason being that TLV format allows sub-TLVs and hence the length
encompasses those as well
- Clarified the case a bit and added the coma
From:
Roni Even via Datatracker <noreply@xxxxxxxx>
Date: Friday, 7 October 2022 at 07:51
To: gen-art@xxxxxxxx <gen-art@xxxxxxxx>
Cc: draft-ietf-lsr-isis-flood-reflection.all@xxxxxxxx <draft-ietf-lsr-isis-flood-reflection.all@xxxxxxxx>, last-call@xxxxxxxx <last-call@xxxxxxxx>, lsr@xxxxxxxx <lsr@xxxxxxxx>
Subject: Genart last call review of draft-ietf-lsr-isis-flood-reflection-10
[External Email. Be cautious of content]
Reviewer: Roni Even
Review result: Ready with Nits
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
For more information, please see the FAQ at
<https://urldefense.com/v3/__https://trac.ietf.org/trac/gen/wiki/GenArtfaq__;!!NEt6yMaO-gk!FMPCwmdM-Z1EIR4yFEyR7C_FLew4r6SlM2STtoLgzHhAdQ1LPulnOj-UOYy0Uh52huMa_vfnmXW0$ >.
Document: draft-ietf-lsr-isis-flood-reflection-??
Reviewer: Roni Even
Review Date: 2022-10-06
IETF LC End Date: 2022-10-10
IESG Telechat date: Not scheduled for a telechat
Summary:
The documents is ready for publication as an experimental RFC with nits
Major issues:
Minor issues:
Nits/editorial comments:
1. in sections 4.2 and 4.4 I think that the length field is always 5. so why
not specify this value. 2.In section 7 second paragraph I am not sure what is
the meaning of "very very corner case". is it a unique case or a rare case or
just a corner case? also should there be a comma after "only" so it should be
"only, in which ..." otherwise I am not sure what the sentence means.
Juniper Business Use Only
|
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
