Skip to main content

Last Call Review of draft-ietf-babel-rtt-extension-04
review-ietf-babel-rtt-extension-04-genart-lc-even-2023-10-02-00

Request Review of draft-ietf-babel-rtt-extension
Requested revision No specific revision (document currently at 07)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2023-10-11
Requested 2023-09-27
Authors Baptiste Jonglez, Juliusz Chroboczek
I-D last updated 2023-10-02
Completed reviews Secdir Telechat review of -05 by Shivan Kaul Sahib (diff)
Iotdir Telechat review of -05 by Pascal Thubert (diff)
Intdir Telechat review of -05 by Antoine Fressancourt (diff)
Secdir Last Call review of -04 by Shivan Kaul Sahib (diff)
Genart Last Call review of -04 by Roni Even (diff)
Opsdir Last Call review of -04 by Sheng Jiang (diff)
Rtgdir Early review of -03 by Joel M. Halpern (diff)
Assignment Reviewer Roni Even
State Completed
Request Last Call review on draft-ietf-babel-rtt-extension by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/BIWhclkK1hI96ObDPTboQkVAJhA
Reviewed revision 04 (document currently at 07)
Result Ready w/nits
Completed 2023-10-02
review-ietf-babel-rtt-extension-04-genart-lc-even-2023-10-02-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-babel-rtt-extension-??
Reviewer: Roni Even
Review Date: 2023-10-02
IETF LC End Date: 2023-10-11
IESG Telechat date: Not scheduled for a telechat

Summary:
The document is ready for publication as a standard track rfc but i have a
question that i defined as a nit

Major issues:

Minor issues:

Nits/editorial comments:
The document was changed in 02 from experimental to standard track. There is
text in the end of section 4 about the algorithm being experimental and from
the mailing list i noticed that the reason to make it standard track is to
allow using the TLVs by other WGs.  As an external observer i have no problem
and noticed that the wg chairs approved it and made a comment that it is open
to discussion on the mailing list. Personally i did not see much discussion so
i am curious if this type of document with an experimental section is OK. Of
course you could split the document to two documents one standard track and the
other experimental but as i said this is up to the group and i have no real
objection to publish the document as is.