[Int-dir] Intdir telechat review of draft-ietf-detnet-mpls-over-tsn-05
Tim Chown via Datatracker <noreply@ietf.org> Sun, 14 February 2021 15:33 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: int-dir@ietf.org
Delivered-To: int-dir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C80A93A0E04; Sun, 14 Feb 2021 07:33:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Tim Chown via Datatracker <noreply@ietf.org>
To: int-dir@ietf.org
Cc: detnet@ietf.org, draft-ietf-detnet-mpls-over-tsn.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161331682374.13755.15439036471779607099@ietfa.amsl.com>
Reply-To: Tim Chown <tim.chown@jisc.ac.uk>
Date: Sun, 14 Feb 2021 07:33:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/eRolN1pL4WRRppMoqnNEkSP4aLo>
Subject: [Int-dir] Intdir telechat review of draft-ietf-detnet-mpls-over-tsn-05
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Feb 2021 15:33:44 -0000
Reviewer: Tim Chown Review result: Ready with Nits Hi, Re: INT-DIR review of draft-ietf-detnet-mpls-over-tsn-06 This draft details how a DetNet MPLS data plane can run over a TSN sub-network. I have reviewed this document and believe it is Ready for publication, with Nits, as listed below. Nits: p.2 Loss rates -> loss rate Provides congestion -> provide congestion For MPLS-based -> for an MPLS-based p.3 Include MSRP and RSVP-TE? p.4 And resources -> and resource p.5 >From MPLS -> from the MPLS Does not -> do not In case of -> In the case of As per the IP doc, not being familiar with DetNet in detail it might be useful to expand on the rationale for mapping to multicast given the “directed” flow. p.7 As per the IP doc, I note it says there are no requirements stated for TSN-unaware MPLS DetNet nodes in the document, but is it worth adding something about requirements to ensure the TSN Relay can be reached? p.8 Implementations -> implementation P.9 of the document -> of this document challanges -> challenges Are member -=> are members Single hop -> a single hop In some case -> in some cases P.10 Regarding the more complicated triggering for TSN-unaware nodes, should further text be added about this? -- Tim
- [Int-dir] Intdir telechat review of draft-ietf-de… Tim Chown via Datatracker
- Re: [Int-dir] Intdir telechat review of draft-iet… Eric Vyncke (evyncke)
- Re: [Int-dir] Intdir telechat review of draft-iet… Balázs Varga A
- Re: [Int-dir] Intdir telechat review of draft-iet… Tim Chown