[RTG-DIR] Rtgdir early review of draft-ietf-teas-yang-l3-te-topo-16

Shuping Peng via Datatracker <noreply@ietf.org> Sun, 28 April 2024 10:22 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rtg-dir@ietf.org
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 30A4FC14F6B0; Sun, 28 Apr 2024 03:22:36 -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
Cc: draft-ietf-teas-yang-l3-te-topo.all@ietf.org, teas@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171429975618.62172.5445723277313406833@ietfa.amsl.com>
Reply-To: Shuping Peng <pengshuping@huawei.com>
Date: Sun, 28 Apr 2024 03:22:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/IlBBzxksWta86ZOU2Rdql5dQ2YE>
Subject: [RTG-DIR] Rtgdir early review of draft-ietf-teas-yang-l3-te-topo-16
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Apr 2024 10:22:36 -0000

Reviewer: Shuping Peng
Review result: Has Issues

Hello

I have been selected to do a routing directorate “early” review of this draft.
https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-l3-te-topo-16

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-teas-yang-l3-te-topo-16.txt
Reviewer: Shuping Peng
Review Date: 28-Apr-2024
Intended Status: Standards

Summary:

I have some minor concerns about this document that I think should be resolved
before it is submitted to the IESG.

Comments:

This document assumes that the TE topology model is already supported together
with layer 3 unicast topology model in a network, right? What if the TE
topology model is not supported? Can the layer 3 unicast topology model be
directly extended to implement traffic engineering? For example, the IP network
can obtain the L3 TE topology through BGP LS, which is much simpler. The TE
topology model is more complex, including IP/MPLS network attributes and
optical network attributes, and does not have the SR attributes. Could the
description of this option of direct extension from layer 3 unicast topology
model be also added in the document?

As stated in Figure 3 and Section 2.2, YANG data type leafref is used to model
the association relationship. Would the title be more accurate to be changed as
"YANG Data Model for Layer 3 TE Topology References"?

Nits:

1. Section 2.2.1, in the last paragraph,
s/can still be used to specified TE parameters/can still be used to specify TE
parameters