IETF Last Call Review of draft-ietf-lsr-ospf-flex-algo-yang-06
review-ietf-lsr-ospf-flex-algo-yang-06-genart-lc-bryant-2026-04-09-00

Request Review of draft-ietf-lsr-ospf-flex-algo-yang
Requested revision No specific revision (document currently at 08)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2026-03-30
Requested 2026-03-09
Authors Yingzhen Qu , Acee Lindem
I-D last updated 2026-05-03 (Latest revision 2026-05-03)
Completed reviews Rtgdir Early review of -00 by Zheng Zhang (diff)
Yangdoctors Early review of -00 by Dhruv Dhody (diff)
Genart IETF Last Call review of -06 by Stewart Bryant (diff)
Opsdir IETF Last Call review of -06 by Adrian Farrel (diff)
Assignment Reviewer Stewart Bryant
State Completed
Request IETF Last Call review on draft-ietf-lsr-ospf-flex-algo-yang by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/7TOIW8_jcrCam_xvDo9umlE4FZ0
Reviewed revision 06 (document currently at 08)
Result Ready w/nits
Completed 2026-04-09
review-ietf-lsr-ospf-flex-algo-yang-06-genart-lc-bryant-2026-04-09-00
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://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-lsr-ospf-flex-algo-yang-06
Reviewer: Stewart Bryant
Review Date: 2026-04-09
IETF LC End Date: 2026-03-30
IESG Telechat date: Not scheduled for a telechat

Summary:From a GENART perspective this is ready bar one easily addressed nit. 

Major issues:None

Minor issues:None

Nits/editorial comments:

The Nits checker picked up the following:

  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  -- No information found for draft-ietf-yang-te - is the name correct?

SB> This looks like an incorrect reference. Should it be draft-ietf-teas-yang?

  -- Possible downref: Normative reference to a draft: ref.
     'I-D.ietf-yang-te’ 

SB> This would be resolved if draft-ietf-teas-yang is the correct reference