[alto] Robert Wilton's Yes on draft-ietf-alto-oam-yang-15: (with COMMENT)
Robert Wilton via Datatracker <noreply@ietf.org> Thu, 26 October 2023 10:03 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 C566AC16F3FF; Thu, 26 Oct 2023 03:03:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-alto-oam-yang@ietf.org, alto-chairs@ietf.org, alto@ietf.org, mohamed.boucadair@orange.com, mohamed.boucadair@orange.com
X-Test-IDTracker: no
X-IETF-IDTracker: 11.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <169831459879.49521.16704759357966916139@ietfa.amsl.com>
Date: Thu, 26 Oct 2023 03:03:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/cziG1tBSfKzwv0xYA9bESzibTOM>
Subject: [alto] Robert Wilton's Yes on draft-ietf-alto-oam-yang-15: (with COMMENT)
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: Thu, 26 Oct 2023 10:03:18 -0000
Robert Wilton has entered the following ballot position for draft-ietf-alto-oam-yang-15: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi, Thank you for this well written document and YANG module. I have a few minor, non-blocking comments, that the authors can address as they wish. Minor level comments: (1) p 8, sec 5.1. Overview of ALTO O&M Data Model module: ietf-alto +--rw alto! Making alto a top level presence container isn't a problem, but given the clients are a list anyway, I would have probably just have made alto-server a presence container instead of the top level container. (2) p 62, sec Appendix A. Examples of Extending the ALTO O&M Data Model The case peeringdb allows the ALTO server to update the server URI to the org object of the organization record in PeeringDB. Perhaps include an informative reference to PeeringDB, or briefly explain what it is. Nit level comments: (3) p 3, sec 1. Introduction The basic structure of this YANG data model is guided by Section 16 of [RFC7285] and [RFC7971]. Although the scope of the YANG data model in this document mainly focuses on the support of the base ALTO protocol [RFC7285] and the existing ALTO standard extensions: [RFC8189], [RFC8895], [RFC8896], [RFC9240], [RFC9241], [RFC9275], and [RFC9439]. I'm not sure the second sentence quite scans, perhaps drop "Although"? Regards, Rob
- [alto] Robert Wilton's Yes on draft-ietf-alto-oam… Robert Wilton via Datatracker