[RTG-DIR]Rtgdir early review of draft-ietf-rtgwg-net2cloud-problem-statement-41

Shuping Peng via Datatracker <noreply@ietf.org> Mon, 09 September 2024 07:52 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rtg-dir@ietf.org
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from [10.244.2.118] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 25DE9C1519B8; Mon, 9 Sep 2024 00:52:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Shuping Peng via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172586835774.2647504.2906454583536619008@dt-datatracker-68b7b78cf9-q8rsp>
Date: Mon, 09 Sep 2024 00:52:37 -0700
Message-ID-Hash: UILOHG7OK5E3GPKB2EGOEC76BDUZDRRD
X-Message-ID-Hash: UILOHG7OK5E3GPKB2EGOEC76BDUZDRRD
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-dir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-rtgwg-net2cloud-problem-statement.all@ietf.org, rtgwg@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Shuping Peng <pengshuping@huawei.com>
Subject: [RTG-DIR]Rtgdir early review of draft-ietf-rtgwg-net2cloud-problem-statement-41
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/ep9wmjyytZSsToO1PzTD9TkTfTU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-dir-owner@ietf.org>
List-Post: <mailto:rtg-dir@ietf.org>
List-Subscribe: <mailto:rtg-dir-join@ietf.org>
List-Unsubscribe: <mailto:rtg-dir-leave@ietf.org>

Reviewer: Shuping Peng
Review result: Ready

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