[Teas] Murray Kucherawy's No Objection on draft-ietf-lsr-isis-rfc5316bis-04: (with COMMENT)

Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 22 September 2022 06:17 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C2BC2C1527A7; Wed, 21 Sep 2022 23:17:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lsr-isis-rfc5316bis@ietf.org, lsr-chairs@ietf.org, lsr@ietf.org, chopps@chopps.org, teas@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.16.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <166382744579.12168.9250850794860251135@ietfa.amsl.com>
Date: Wed, 21 Sep 2022 23:17:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/JpA0XzxFMNkMYrEdGDZJxrQZAmw>
Subject: [Teas] Murray Kucherawy's No Objection on draft-ietf-lsr-isis-rfc5316bis-04: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Sep 2022 06:17:25 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-lsr-isis-rfc5316bis-04: 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-lsr-isis-rfc5316bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I support Alvaro's DISCUSS, and add my own comments related to his first point:

The first two SHOULDs in Section 3.1 would benefit from some guidance about
when an implementer might opt to deviate from that advice.  This occurs again
Sections 3.3.4, 3.4.1, 3.4.2, the top of Section 4 (two SHOULDs) and the bottom
of Section 4 (two SHOULD NOTs).

Given Section 6.3, I think RFC7981 should be a normative reference rather than
an informative one.

I think RFC4271 also needs to be normative since it's referenced by a SHOULD.