[Tsv-art] Tsvart early review of draft-ietf-idr-bgp-ct-srv6-03

Joseph Touch via Datatracker <noreply@ietf.org> Fri, 29 March 2024 02:25 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: tsv-art@ietf.org
Delivered-To: tsv-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 869E5C1840D0; Thu, 28 Mar 2024 19:25:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joseph Touch via Datatracker <noreply@ietf.org>
To: tsv-art@ietf.org
Cc: draft-ietf-idr-bgp-ct-srv6.all@ietf.org, idr@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171167913153.49561.12665977852724224115@ietfa.amsl.com>
Reply-To: Joseph Touch <touch@strayalpha.com>
Date: Thu, 28 Mar 2024 19:25:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/SRAij72hL5k96QuE3GZQqX75eB0>
Subject: [Tsv-art] Tsvart early review of draft-ietf-idr-bgp-ct-srv6-03
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2024 02:25:31 -0000

Reviewer: Joseph Touch
Review result: Not Ready

This document was reviewed as per the following request:

TSV-DIR - Please look at this draft from the viewpoint of having intent (color)
aware customer traffic forwarded over a VPN overlay (tunnels) that forwarded
over a set of intent (color) aware underlay of tunnels.  Please consider the
problems with tunnels in your review of this text.

The document refers to these tunnels in a manner that appears consistent with
draft-ietf-idr-bgp-ct. As a side note, it would be preferable for this document
to refer to the terminology of this bgp-ct draft rather than repeating it, so
it would be more clear which terms are introduced herein. Avoiding duplication
also avoids the need to align the two sets of definitions upon publication.

TSV-DIR area of concern appears to originate in the bgp-ct draft rather than
herein. There are a variety of issues with tunnels not addressed in either
document, many of which are described in draft-ietf-intarea-tunnels (though not
refreshed, this remains an active INTAREA doc), notably the difference between
tunnel path MTU, tunnel egress MTU, and overall path MTU of the tunneling
service (which is dependent on the latter rather than the former), especially
the difficulty in determining the tunnel path MTU. The way in which both
documents refer to tunneling as (IMO) 'do a tunnel, whatever that involves' is
a bit of a disconnect with the idea that these tunnels, when deployed, provide
service assurances on which upper layers can plan. In particular, Section 4.1
of the bgp-ct doc gives some potentially relevant examples, but only for a
subset of the tunneling technologies described in the definition.

Both documents would benefit from a more precise definition of the tunnel
technologies that have properties needed to support these methods. In
particular, a tunnel cannot provide "transport class aware" services unless
that can be assured by the layer over which the tunnel operates or by the
tunnel protocol itself. E.g., a tunnel cannot provide guaranteed BW over a
best-effort network, but a tunnel can create assured in-order delivery over an
underlay without such ordering guarantees.