Martin Duke's Discuss on draft-ietf-6man-spring-srv6-oam-10: (with DISCUSS and COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Mon, 24 May 2021 18:52 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 B9CAD3A326B; Mon, 24 May 2021 11:52:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke 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>, ot@cisco.com
Subject: Martin Duke's Discuss on draft-ietf-6man-spring-srv6-oam-10: (with DISCUSS and COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <162188236573.11854.4853541115172766349@ietfa.amsl.com>
Date: Mon, 24 May 2021 11:52:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KvLLAzqqJuiA1XESulqDieRumJQ>
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: Mon, 24 May 2021 18:52:46 -0000

Martin Duke has entered the following ballot position for
draft-ietf-6man-spring-srv6-oam-10: Discuss

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/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I would like to clarify that when the pseudocode says "Send the copied packet,
along with a timestamp to the OAM process for telemetry data collection and
export," that this "process" is colocated on the router, and that this process
further digests the data so that there is much less than 1 packet going out of
the box per O-bit packet processed.

If there is a case where each O-bit packet generates an entire packet going off
the router to a controller or external OAM process, there are extremely
unfortunate corner cases that are not sufficiently mitigated by rate-limiting.


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

Thank you for addressing the TSVART comments (and to Magnus for the review)

I see that some of the contributors are in common, but this would appear to
have substantial overlap with
https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-direct-export/.