[Detnet] Tsvart last call review of draft-ietf-detnet-ip-over-mpls-05
Brian Trammell via Datatracker <email@example.com> Wed, 22 April 2020 11:52 UTC
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A7513A0A38; Wed, 22 Apr 2020 04:52:47 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
From: Brian Trammell via Datatracker <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org, email@example.com
Reply-To: Brian Trammell <firstname.lastname@example.org>
Date: Wed, 22 Apr 2020 04:52:47 -0700
Subject: [Detnet] Tsvart last call review of draft-ietf-detnet-ip-over-mpls-05
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2020 11:52:48 -0000
Reviewer: Brian Trammell Review result: Ready with Nits 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 email@example.com if you reply to or forward this review. This document presents a fairly straightforward mapping of DetNet IP flows to DetNet over MPLS, and as such raises no concerns for transport beyond those raised by its referent documents (draft-ietf-detnet-ip, draft-ietf-detnet-mpls, and RFC8655); transport issues in those documents should be addressed before this document can be published. Note that the flow aggregation procedures in section 4.4 of draft-ietf-detnet-ip, which are essentially included by reference in section 5.1 of this document, run counter to present and future developments in the transport layer, specifically the deployment of multipath transports. Transport layer protocols that split flows across multiple IP-layer N-tuples appear to break the assumptions made about flow aggregation in these documents, and as such it should be noted that this architecture is not apparently compatible with multipath transport. Whether this limitation is important for DetNet's target use cases is unclear to this reviewer, so it may have been considered by the WG and declared out of scope.
- [Detnet] Tsvart last call review of draft-ietf-de… Brian Trammell via Datatracker
- Re: [Detnet] Tsvart last call review of draft-iet… Balázs Varga A