Murray Kucherawy's No Objection on draft-ietf-6man-spring-srv6-oam-11: (with COMMENT)

Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 03 June 2021 06:49 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDB73A2CD3; Wed, 2 Jun 2021 23:49:05 -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-6man-spring-srv6-oam@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org, Ole Trøan <ot@cisco.com>
Subject: Murray Kucherawy's No Objection on draft-ietf-6man-spring-srv6-oam-11: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <162270294548.29805.15112949596995827935@ietfa.amsl.com>
Date: Wed, 02 Jun 2021 23:49:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jvyhDPyCBG2MZBQSSCejd-_E-g0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2021 06:49:06 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-6man-spring-srv6-oam-11: 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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-6man-spring-srv6-oam/



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

The shepherd writeup omits an answer to the question "Why is this the proper
type of RFC?"

Although "TC" and "IS-IS" are defined in the glossary in Section 1.2, they
appear in no other sections.  (It's "ISIS" elsewhere.")

In Section 1.3, I don't think you can start a sentence with "e.g."

In Section 2.1: It says, "The processing node SHOULD rate-limit the number of
packets ...", but no guidance is given on what a good rate might be.