Skip to main content

Early Review of draft-ietf-rtgwg-net2cloud-problem-statement-41
review-ietf-rtgwg-net2cloud-problem-statement-41-rtgdir-early-peng-2024-09-09-00

Request Review of draft-ietf-rtgwg-net2cloud-problem-statement
Requested revision No specific revision (document currently at 41)
Type Early Review
Team Routing Area Directorate (rtgdir)
Deadline 2024-10-11
Requested 2024-08-20
Requested by Jim Guichard
Authors Linda Dunbar , Andrew G. Malis , Christian Jacquenet , Mehmet Toy , Kausik Majumdar
I-D last updated 2024-09-09
Completed reviews Secdir Last Call review of -36 by Deb Cooley (diff)
Tsvart Last Call review of -32 by Magnus Westerlund (diff)
Intdir Early review of -26 by Benson Muite (diff)
Secdir Early review of -22 by Deb Cooley (diff)
Genart Early review of -21 by Paul Kyzivat (diff)
Opsdir Early review of -22 by Susan Hares (diff)
Rtgdir Early review of -22 by Ines Robles (diff)
Tsvart Early review of -22 by David L. Black (diff)
Dnsdir Early review of -22 by Florian Obser (diff)
Dnsdir Last Call review of -41 by David C Lawrence
Rtgdir Early review of -41 by Shuping Peng
Secdir Early review of -41 by Mike Ounsworth
Artart Last Call review of -41 by Rich Salz
Assignment Reviewer Shuping Peng
State Completed
Request Early review on draft-ietf-rtgwg-net2cloud-problem-statement by Routing Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/rtg-dir/ep9wmjyytZSsToO1PzTD9TkTfTU
Reviewed revision 41
Result Ready
Completed 2024-09-09
review-ietf-rtgwg-net2cloud-problem-statement-41-rtgdir-early-peng-2024-09-09-00
Hello

I have been selected to do a routing directorate “early” review of this draft.
https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-net2cloud-problem-statement-41

The routing directorate will, on request from the working group chair, perform
an “early” review of a draft before it is submitted for publication to the
IESG. The early review can be performed at any time during the draft’s lifetime
as a working group document. The purpose of the early review depends on the
stage that the document has reached.

As this document is in working group last call, my focus for the review was to
determine whether the document is ready to be published. Please consider my
comments along with the other working group last call comments.

For more information about the Routing Directorate, please see
​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Document: draft-ietf-rtgwg-net2cloud-problem-statement-41.txt
Reviewer: Shuping Peng
Review Date: 9-Sep-24
Intended Status: Informational

Summary:

This document is basically ready for publication, but has nits that should be
considered prior to being submitted to the IESG.

Comments:

I wonder whether it is necessary to keep the phrase "at the time of writing
this document" shown a few times in this document. Every draft is written based
on the information obtained at the time of its writing. Moreover, this draft is
stratched over seven years for now. It is hard to tell when exactly the
corresponding text was written. I noticed in the abstract that 2023 was added,
but still.

Section 2.
Page 4. Why is the term "Underlay Connectivity Services" capitalized? And
"Application Flows"?

Section 7.
Page 19.
"While this specific protocol isn't being
        suggested the risks and vulnerabilities apply to any group key
        management system."

What is "this specific protcol" being mentioned here?

Nits:
1. page 4, s/managing cloud spending/managing Cloud spending

2. page 18, s/internet/Internet