[alto] Opsdir early review of draft-ietf-alto-oam-yang-06

Dan Romascanu via Datatracker <noreply@ietf.org> Fri, 21 April 2023 08:00 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: alto@ietf.org
Delivered-To: alto@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7459BC15E406; Fri, 21 Apr 2023 01:00:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: alto@ietf.org, draft-ietf-alto-oam-yang.all@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 10.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <168206401546.30918.7998792221903169633@ietfa.amsl.com>
Reply-To: Dan Romascanu <dromasca@gmail.com>
Date: Fri, 21 Apr 2023 01:00:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/-m_Qplqcw_SeJDIzrdfPXqZJKIg>
Subject: [alto] Opsdir early review of draft-ietf-alto-oam-yang-06
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2023 08:00:15 -0000

Reviewer: Dan Romascanu
Review result: Has Nits

Ready with Nits

This document defines YANG data models for Operations, Administration, and
Maintenance (OAM) & Management of ALTO. The operator can use these data models
to set up an ALTO server, create, update and remove ALTO information resources,
manage the access control, configure server discovery, and collect statistical
data.

I like this document. It is clearly written and very well structured. I liked
the description of requirements, the information model corresponding to the
requirements, and the extension example modules in the Appendices. These are
all very useful for operators who need to understand and use the YANG modules.

Understanding and using this document requires a good knowledge of ALTO.

My review is focused on the design and data modelling issues relevant for
operations and manageability. I did not perform a YANG review, I assume that
YANG Doctors review is performed separately.

This document is Ready with a couple of editorial comments.

Editorial & Nits:

1. There are many more acronyms not included in Section 3 or expanded at first
occurrence. Maybe the respective acronyms sections in the ALTO documents should
be mentioned / referred

2. In Section 5.3.1.2

> In practice, multiple ALTO servers can be deployed for scalability.
   That may require communication among different ALTO servers.

   The "ietf-alto" module does not contain any configuration for the
   communication between peer ALTO servers.  Instead, it provides the
   configuration for how an ALTO server can be discovered by another
   ALTO server on demand (Figure 6).

I understand that the communication between ALTO servers is out of scope.
However, I do not understand how is the scalability requirement met. Is there /
Will there be another YANG module to define this data model? Something else
than YANG? Maybe this is described in another ALTO document that I did not find.