Re: [Detnet] Comments on ip-over-tsn, mpls-over-tsn, tsn-vpn-over-mpls

"BRUNGARD, DEBORAH A" <> Wed, 14 October 2020 15:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 484F53A0F7C; Wed, 14 Oct 2020 08:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nsVcPFruETFq; Wed, 14 Oct 2020 08:56:27 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5872E3A0F74; Wed, 14 Oct 2020 08:56:27 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id 09EFqm5W043812; Wed, 14 Oct 2020 11:56:26 -0400
Received: from ( []) by with ESMTP id 345fk941qf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 14 Oct 2020 11:56:26 -0400
Received: from (localhost []) by (8.14.5/8.14.5) with ESMTP id 09EFuN7J010165; Wed, 14 Oct 2020 11:56:25 -0400
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id 09EFuKro010041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 14 Oct 2020 11:56:20 -0400
Received: from ( []) by (Service) with ESMTP id 4F300400B578; Wed, 14 Oct 2020 15:56:20 +0000 (GMT)
Received: from (unknown []) by (Service) with ESMTPS id 34782400B579; Wed, 14 Oct 2020 15:56:20 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Wed, 14 Oct 2020 11:56:19 -0400
Received: from ([]) by ([]) with mapi id 15.01.2044.006; Wed, 14 Oct 2020 11:56:19 -0400
To: Lou Berger <>, DetNet WG <>
CC: "" <>, "" <>, "" <>
Thread-Topic: [Detnet] Comments on ip-over-tsn, mpls-over-tsn, tsn-vpn-over-mpls
Thread-Index: AQHWobea73zYwVhVEkyZBRfF9G6AwamXPqMg
Date: Wed, 14 Oct 2020 15:56:19 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-snts-smtp: 371C0F4826E31EB8CF0EFA85C88F00AB9F62D09F1232E8A4A04C3077629AD9B32
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-10-14_09:2020-10-14, 2020-10-14 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 clxscore=1011 spamscore=0 malwarescore=0 mlxscore=0 impostorscore=0 suspectscore=0 priorityscore=1501 phishscore=0 adultscore=0 lowpriorityscore=0 mlxlogscore=999 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2010140112
Archived-At: <>
Subject: Re: [Detnet] Comments on ip-over-tsn, mpls-over-tsn, tsn-vpn-over-mpls
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 14 Oct 2020 15:56:36 -0000


Following up on Lou's comment on the status - my view - PS would be used when defining new extensions or if there was something specifically needed for interworking. A BCP is when there are already deployments and is used to define the best current practice. An informational would apply if there are no new protocol extensions needed and the document is describing "how to use".

Looking at mpls-over-tsn, I would say the current text fits more as an informational. It doesn't really "specify", it is more a description on "how to use". Here's another document somewhat similar:

Usually one of the following are included in the abstract:
" This informational document follows well-established xxxx procedures and does not require any actions by IANA or any new protocol extensions."
"This document does not define new procedures or processes.  Whenever this document makes requirements statements or recommendations, these are taken from normative text in the referenced RFCs."

IF the above statements apply, I'd recommend it be Informational.


-----Original Message-----
From: detnet <> On Behalf Of Lou Berger
Sent: Tuesday, October 13, 2020 7:21 PM
To: DetNet WG <>
Subject: [Detnet] Comments on ip-over-tsn, mpls-over-tsn, tsn-vpn-over-mpls


     As I mentioned on the LC thread, I have some comments on these 
drafts as Shepherd that I think should be addressed before passing the 
documents along to the IESG.

Major comment:

In reviewing the other DetNet data plane documents, some members of the 
IESG asked what unique protocol processing was defined in those 
documents that justified those documents being on the Standards Track vs 
Informational.  I reviewed the three TSN related documents with this in 
mind. (FWIW my view of goes in a standard can be found in;!!BhdT!wNUN9uklYMF-4hszjL-VTzsSw6XgPLx9ohRxBqxY4T8Sm_MT7HljNHyL6Y4RTKY$  , albeit a bit dated.)

I found that, as written, both draft-ietf-detnet-ip-over-tsn-03 and 
draft-ietf-detnet-mpls-over-tsn-03 say basically the same thing: That an 
mpls or ip over TSN node behaves as a TSN unaware talker combined with 
an internal TSN-relay.  This is covered in section 4.2 and Figure 3 of 
each document.

The text of these section do have conformance language, but the language 
relates to TSN standardized operation. So, for me use of IETF 
conformance language is not appropriate.  As far as I read it, there is 
no protocol processing defined beyond what is in the referenced TSN 
documents.  For this reason, I think these documents should be revised 
to remove conformance language and be published as BCPs (or even 
informational) .  I'd like to confer with our AD to see if she has a 
preference on which.

draft-ietf-detnet-tsn-vpn-over-mpls-03 is in a slightly different 
position.  This document also contains some TSN-specific conformance 
language that should be removed (e.g., see section 5.1), but it also 
defines TSN over MPLS specific behaviors in section 5.2.  I think this 
definition as a PS is pretty thin and basically comes down to saying TSN 
Steams are mapped to DetNet AppFlows.  This said, there is a real 
interoperability issue being addressed as without even this thin 
definition, different implementations would not necessarily 
interoperate.    I recommend that this document also be revised to

(a) ensure it is not using conformance language for any TSN behaviors  
-- describing what an IEEE reference requires is fine, but that's just 
informative text, and

(b) clearly define what processing/protocol behavior is required, and 
what management/controller information must be supported, to be 
conformant the the new proposed standard.

Minor comments:

- All the documents state that there are required mappings between 
DetNet and TSN management and control planes, but no details are given.  
Rather then make unsubstantiated comments, I suggest stating that such 
mappings are out of scope of the document.

- All three documents repeat/summarize behaviors from the other data 
plane documents in overview sections.  I suggest deleting these and just 
point the readers and these normative documents.

- somewhat related, conformance language from the detnet-mpls is 
partially repeated in section 5.3 of tsn-vpn-over-mpls.  It would be 
better to just point to required processing in detnet-mpls than do a 
partial repetition.

I'm happy to work with the authors, on list or in an informal meeting 
announced on the list,to review these comments and any proposed changes 
they may propose to resolve these  comments. (I'll also provide some 
additional less important nits.)


(as doc Shepherd)

detnet mailing list;!!BhdT!wNUN9uklYMF-4hszjL-VTzsSw6XgPLx9ohRxBqxY4T8Sm_MT7HljNHyLNYfs2Eg$