Skip to main content

Last Call Review of draft-ietf-detnet-ip-over-mpls-05
review-ietf-detnet-ip-over-mpls-05-tsvart-lc-trammell-2020-04-22-00

Request Review of draft-ietf-detnet-ip-over-mpls
Requested revision No specific revision (document currently at 09)
Type Last Call Review
Team Transport Area Review Team (tsvart)
Deadline 2020-04-23
Requested 2020-04-09
Authors Balazs Varga , Lou Berger , Don Fedyk , Stewart Bryant , Jouni Korhonen
Draft last updated 2020-04-22
Completed reviews Rtgdir Last Call review of -04 by Tomonori Takeda (diff)
Genart Last Call review of -05 by Tim Evens (diff)
Secdir Last Call review of -07 by Vincent Roca (diff)
Tsvart Last Call review of -05 by Brian Trammell (diff)
Assignment Reviewer Brian Trammell
State Completed
Review review-ietf-detnet-ip-over-mpls-05-tsvart-lc-trammell-2020-04-22
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/bu_oySrM24L2pJ5eaUtagFN8K0U
Reviewed revision 05 (document currently at 09)
Result Ready with Nits
Completed 2020-04-22
review-ietf-detnet-ip-over-mpls-05-tsvart-lc-trammell-2020-04-22-00
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.

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.