[Last-Call] Opsdir last call review of draft-ietf-lsr-ospf-l2bundles-06

Dan Romascanu via Datatracker <noreply@ietf.org> Sat, 24 September 2022 07:55 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: last-call@ietf.org
Delivered-To: last-call@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE97C14CF15; Sat, 24 Sep 2022 00:55:01 -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: draft-ietf-lsr-ospf-l2bundles.all@ietf.org, last-call@ietf.org, lsr@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <166400610162.62680.12901821351127538136@ietfa.amsl.com>
Reply-To: Dan Romascanu <dromasca@gmail.com>
Date: Sat, 24 Sep 2022 00:55:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/QZoQshjH7hQdIEJe_r0rci94Q6E>
Subject: [Last-Call] Opsdir last call review of draft-ietf-lsr-ospf-l2bundles-06
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2022 07:55:01 -0000

Reviewer: Dan Romascanu
Review result: Has Issues

Ready with Issues.

This document defines the protocol extensions for OSPF to advertise the link
attributes of L2 interface bundle members such as instances of a IEEE 802.1AX
Link Aggregation Group (LAG).

This is a very useful document. It's clear and well-written. Operators that
deploy OSPF in environments where IEEE 802.1AX or other L2 bundle interfaces
may be present in routers will find this document very relevant.

My main issue is related to the lack of any operational or management
considerations. I believe that the following should be mentioned explicitly or
by reference in a short Operational and Manageability Issues section:

- any backwards compatibility or transition issues at deployment
- any impact on traffic
- any configuration parameters and default values
- management including possible extensions of YANG or MIB modules

I agree with the issues raised by the Gen-ART reviewer concerning the
references, with the difference that I believe that [IEEE 802.1AX] should
remain a Normative Reference. It's a full IEEE 802.1 standard, so referencing
as Normative is fine.

I would also suggest sending the document for review to the IEEE 802.1 WG via
the IETF-IEEE coordination team.