[Tsv-art] Tsvart last call review of draft-ietf-detnet-mpls-over-udp-ip-06

Joerg Ott via Datatracker <noreply@ietf.org> Thu, 10 September 2020 15:34 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 5076C3A0911; Thu, 10 Sep 2020 08:34:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Joerg Ott via Datatracker <noreply@ietf.org>
To: <tsv-art@ietf.org>
Cc: last-call@ietf.org, draft-ietf-detnet-mpls-over-udp-ip.all@ietf.org, detnet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.16.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159975206822.20137.12087047270168117389@ietfa.amsl.com>
Reply-To: Joerg Ott <jo@acm.org>
Date: Thu, 10 Sep 2020 08:34:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/a5d2eA2HqgSdJGJ4CkFLK2s_-8E>
Subject: [Tsv-art] Tsvart last call review of draft-ietf-detnet-mpls-over-udp-ip-06
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 10 Sep 2020 15:34:28 -0000

Reviewer: Joerg Ott
Review result: Ready

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

The document defines the transmission and reception behaviour as well as
the configuration information for encapsulating DetNet MPLS packets over UDP.
The draft provides an explicit applicability statement concerning carrying
non-congestion controlled traffic.

With the latter in mind, the document seems to be complete.
(Fragmentation and reassembly seem to be already covered with MPLS-over-UDP
in RFC7510 and RFC4023)

One quick question to the authors:
Section 5 provides the necessary information to be configured for flow mapping
and makes reference to IP source and destination addresses. Is the presence of
network (and port) address translation devices/functions covered elsewhere in
the many specs to ensure proper transmission at a sender and proper reverse
mapping at a receiver? It would be up to the control plane to determine the
appropriate addresses. Does this need explicit mentioning?