[Detnet] Robert Wilton's No Objection on draft-ietf-detnet-oam-framework-10: (with COMMENT)
Robert Wilton via Datatracker <noreply@ietf.org> Wed, 03 January 2024 12:35 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: detnet@ietf.org
Delivered-To: detnet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B5AC31A60F; Wed, 3 Jan 2024 04:35:22 -0800 (PST)
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-detnet-oam-framework@ietf.org, detnet-chairs@ietf.org, detnet@ietf.org, lberger@labn.net, lberger@labn.net
X-Test-IDTracker: no
X-IETF-IDTracker: 12.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <170428532252.2552.4511196511252281398@ietfa.amsl.com>
Date: Wed, 03 Jan 2024 04:35:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/Cfr0Va5_VlUTiP9J_zZAQVl76fo>
Subject: [Detnet] Robert Wilton's No Objection on draft-ietf-detnet-oam-framework-10: (with COMMENT)
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jan 2024 12:35:22 -0000
Robert Wilton has entered the following ballot position for draft-ietf-detnet-oam-framework-10: No Objection 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-detnet-oam-framework/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi, Thanks for this document, I found it easy to read and understand. I only have some minor comments that may help improve the document: Minor level comments: (1) p 6, sec 3.1. Information Collection Information about the state of the network can be collected using several mechanisms. Some protocols, e.g., Simple Network Management Protocol, send queries. Others, e.g., YANG-based data models, generate notifications based on the publish-subscribe method. In either way, information is collected and sent using the DetNet Controller Plane. A few suggestions: 1. For SNMP, perhaps "polls for updated data" rather than "send queries". 2. YANG data models don't in themselves generate notifications, but only define notifications that could be generated when particular events occur. But really, it is protocols, such as YANG Push, that are used to setup subscriptions for the data defined in the YANG data models to be published either on a periodic basis, or when the underlying data changes. (2) p 10, sec 5.1. Replication / Elimination Figure 1: Packet Replication: S transmits twice the same data packet, to nodes A and B. I wasn't really sure what this diagram was intending to convey (i.e., the text only mentions S, A, and B and none of the other nodes in the diagram). E.g., perhaps make is clearer that the desination is R rather than A or B? (3) p 11, sec 6. Requirements 6. OAM methods MAY combine in-band monitoring or measurement in the forward direction and out-of-bound notification in the reverse direction, i.e., towards the ingress MEP. Given that this is "MAY" is doesn't appear to technically be an actual requirement, since implementations are not required (or even recommended) to support it. (4) p 11, sec 6. Requirements 8. DetNet OAM MAY support bi-directional OAM methods for bi- directional DetNet flows. OAM test packets used for monitoring and measurements MUST be in-band in both directions. Given that this is "MAY" is doesn't appear to technically be an actual requirement, since implementations are not required (or even recommended) to support it. Nit level comments: (5) p 10, sec 6. Requirements 2. It MUST be possible to initiate a DetNet OAM session from using any of DetNet Controller Plane solution, e.g., centralized controller. Perhaps "by using any of the DetNet Controller Plane solutions"? Regards, Rob
- [Detnet] Robert Wilton's No Objection on draft-ie… Robert Wilton via Datatracker
- Re: [Detnet] Robert Wilton's No Objection on draf… Greg Mirsky
- Re: [Detnet] Robert Wilton's No Objection on draf… Rob Wilton (rwilton)
- Re: [Detnet] Robert Wilton's No Objection on draf… Greg Mirsky
- Re: [Detnet] Robert Wilton's No Objection on draf… Rob Wilton (rwilton)