[sfc] Martin Duke's No Objection on draft-ietf-sfc-oam-framework-13: (with COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Tue, 05 May 2020 04:27 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sfc@ietf.org
Delivered-To: sfc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F02A3A13AE; Mon, 4 May 2020 21:27:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sfc-oam-framework@ietf.org, sfc-chairs@ietf.org, sfc@ietf.org, Tal Mizrahi <tal.mizrahi.phd@gmail.com>, tal.mizrahi.phd@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.129.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <158865287462.10835.6379624375289404130@ietfa.amsl.com>
Date: Mon, 04 May 2020 21:27:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/TVqNmczz_KGurv0f-j9tJzWr3C8>
Subject: [sfc] Martin Duke's No Objection on draft-ietf-sfc-oam-framework-13: (with COMMENT)
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2020 04:27:55 -0000

Martin Duke has entered the following ballot position for
draft-ietf-sfc-oam-framework-13: 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 IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sfc-oam-framework/



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

Please address the issues in the (detailed!) Tsvarea review, in particular the
bits from section 4 that incorrectly describe the work coming out of IPPM.

Additional nits:

Sec 3.1.1: s/extendibility/extensibility

Sec 3.1.2: there are also “hybrid” methods like IOAM that do not fit the active
and passive definitions neatly.

4.1 s/packet to be of variable length packet size/packet to be of variable
length

4.1 you are probably not trying to “verify” packet reordering and corruption! I
suggest “detect” instead.

6.3 s/is intended to/is intended

6.3 s/in NSH header/in the NSH header

6.4.1 s/describes/describe

6.4.1 s/incrementing the ttl/incrementing ttl

6.4.3 s/using NSH header/using the NSH header

8. s/Any security consideration/Any security considerations

8. Missing period at end of second paragraph

8. s/mechanism/mechanisms