Re: [Detnet] Transport sub-layer name change (Was Re: Tsvart last call review of draft-ietf-detnet-architecture-08)

János Farkas <janos.farkas@ericsson.com> Fri, 07 December 2018 15:45 UTC

Return-Path: <Janos.Farkas@ericsson.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D36130DD7 for <detnet@ietfa.amsl.com>; Fri, 7 Dec 2018 07:45:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.758
X-Spam-Level:
X-Spam-Status: No, score=-5.758 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_RED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dt1z0TKtzmZa for <detnet@ietfa.amsl.com>; Fri, 7 Dec 2018 07:45:48 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4FCF130DE8 for <detnet@ietf.org>; Fri, 7 Dec 2018 07:45:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1544197545; x=1546789545; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Z3U3YwpJdd7wdHxMjrs2jJHr15kak4UeFTF3HtpJxXw=; b=ei+3lWmW97RCynXorB3dJOxLTnw3UDRzEZTgVMaJH4Pxi1DvYzCq56sMd61TyESV RVMtv5Rv6MgwTo5OGJ1IjWWTPl/djl2uB8fvvhzxqrg3lEW+AAAExHZDWDIjAr/c 7SRgoCvh1oOgc4tQmb6W/L5zo8/wFA1MT60qeA3ukAI=;
X-AuditID: c1b4fb25-a68609e00000191f-53-5c0a95a9387b
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 0A.E6.06431.9A59A0C5; Fri, 7 Dec 2018 16:45:45 +0100 (CET)
Received: from ESESSMB503.ericsson.se (153.88.183.164) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 7 Dec 2018 16:45:43 +0100
Received: from [131.160.181.217] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.191) with Microsoft SMTP Server id 15.1.1466.3 via Frontend Transport; Fri, 7 Dec 2018 16:45:43 +0100
To: Lou Berger <lberger@labn.net>, "Andrew G. Malis" <agmalis@gmail.com>, "Grossman, Ethan A." <eagros@dolby.com>
CC: draft-ietf-detnet-architecture.all@ietf.org, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, detnet WG <detnet@ietf.org>, Michael.Scharf@hs-esslingen.de
References: <153817345967.27205.135001179751151278@ietfa.amsl.com> <fdf872d6-08a6-2c33-de21-9dd1506c1d21@labn.net> <6EC6417807D9754DA64F3087E2E2E03E2D16A4D3@rznt8114.rznt.rzdir.fht-esslingen.de> <e38ab4d6-0924-ab60-b1dc-4ac26600044c@labn.net> <16c050e436f342bb94b1ec9d1a38da3e@XCH-RCD-001.cisco.com> <3adfa63a-e6de-b899-f7ce-79d8f668d40f@labn.net> <dfea900c1cb54ee88a953f22a9c7e639@XCH-RCD-001.cisco.com> <BL0PR06MB4548D6E06909D74F227C84E6C4D90@BL0PR06MB4548.namprd06.prod.outlook.com> <CAA=duU3uw2kb1cMT9ys-WQ23=VDhOm3YO+rC1pbmksNC5pRcVQ@mail.gmail.com> <2086b964-4115-21b4-00d1-079f22d0a399@labn.net>
From: János Farkas <janos.farkas@ericsson.com>
Message-ID: <38afc693-1a98-50e4-907a-6cc5ec178ac6@ericsson.com>
Date: Fri, 07 Dec 2018 16:45:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <2086b964-4115-21b4-00d1-079f22d0a399@labn.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupgkeLIzCtJLcpLzFFi42KZGbG9XHflVK4YgysbjS1OPz/FZvH702wW i32zNrFY9D3ezm7R0fwWyF3czG4xY8o7Rgd2jym/N7J67Jt4hMVj56y77B5Nr/6xeixZ8pPJ 48OmZrYAtigum5TUnMyy1CJ9uwSujOUXzrMWzNWq2Na5jrWBsVO5i5GTQ0LAROLNywlMXYxc HEICRxglDn68zw7hfGWUWPF7KxuEc5RR4nn/eWaQFmGBOonJKzrYQWwRgWKJHZd3s4AUMQss Y5TYMX8tWJGQwBsWiXsbbUFsNgF7ibuXNoDFeYHsCY83sIDYLAIqEj82HQCzRQViJT5dWQxV IyhxcuYTsDingI3EjsW3wGxmAQuJmfPPM0LY8hLNW2czQ9jiEreezGeC2Ksm8entQ/YJjEKz kIyahaR9FpL2WUjaFzCyrGIULU4tTspNNzLWSy3KTC4uzs/Ty0st2cQIjJ+DW36r7mC8/Mbx EKMAB6MSD+/7Jq4YIdbEsuLK3EOMEhzMSiK8SjlAId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rwM jUApgfTEktTs1NSC1CKYLBMHp1QDo4atle/7yp4b2wR2p65a3b33tMVDVwX5N4sTNJexPjm2 R7CE1Xa3oZVIQXTKDLvrN/hN0+RNPbonrw+sV3szZ1l06mtpmfQX67IDDrcWJm9/84KB37af 3dojsyFhL/8a8bVvKox0J9q/lWFZH6odn/wk7viKYrNMS5+ieZNFp1aH3E7pXXRaiaU4I9FQ i7moOBEAMHEG2psCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/osXSekaONw3fIatAUkJ_u3hTg3g>
Subject: Re: [Detnet] Transport sub-layer name change (Was Re: Tsvart last call review of draft-ietf-detnet-architecture-08)
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2018 15:45:50 -0000

Hi,

I have a similar concern with the change. It of course depends on the 
definition of Traffic Engineering, but the term "DetNet TE sub-layer" 
may imply to the reader that Traffic Engineering is a must even for 
DetNet transit nodes. As far as I recall, the intention is to make 
possible that DetNet transit nodes can be kept simple. Depending on the 
actual DetNet service provided, DetNet transit nodes can be actually simple.

The idea behind the introduction of the two DetNet sub-layers was to 
make it easier to tackle the problem. The lower layer provides simpler 
packet forwarding related functions, the higher DetNet Service sub-layer 
provides more complex DetNet service related functions.

In order to have another alternative on the table I propose renaming 
"DetNet Transport sub-layer" to "DetNet Forwarding sub-layer"

Best regards,
Janos


On 11/20/2018 10:10 PM, Lou Berger wrote:
>
> On 11/20/2018 3:11 PM, Andrew G. Malis wrote:
>> This terminology is certainly appropriate for TEAS. For DetNet, this 
>> seems to make the assertion that the DetNet underlay is always 
>> traffic-engineered, even if IPv4 or IPv6 (which is certainly possible 
>> using TE extensions for the IGPs).
>
> This is certainly a fair point and one that does lead me to have a 
> slight reservation about the change, that said, it seems the benefit 
> out ways the downsides.
>
>>
>> As long as people are OK with this assertion, then I'm OK with it as 
>> well. That should be made clear in the architecture spec where the 
>> term "DetNet TE sub-layer" is introduced/defined.
>
> agreed.
>
> Lou
>
>>
>> Cheers,
>> Andy
>>
>> On Tue, Nov 20, 2018 at 1:29 PM Grossman, Ethan A. <eagros@dolby.com 
>> <mailto:eagros@dolby.com>> wrote:
>>
>>     I like it.
>>     Ethan.
>>
>>     -----Original Message-----
>>     From: Pascal Thubert (pthubert) <pthubert@cisco.com
>>     <mailto:pthubert@cisco.com>>
>>     Sent: Tuesday, November 20, 2018 10:27 AM
>>     To: Lou Berger <lberger@labn.net <mailto:lberger@labn.net>>;
>>     Scharf, Michael <Michael.Scharf@hs-esslingen.de
>>     <mailto:Michael.Scharf@hs-esslingen.de>>
>>     Cc: detnet@ietf.org <mailto:detnet@ietf.org>;
>>     draft-ietf-detnet-architecture.all@ietf.org
>>     <mailto:draft-ietf-detnet-architecture.all@ietf.org>
>>     Subject: RE: Transport sub-layer name change (Was Re: [Detnet]
>>     Tsvart last call review of draft-ietf-detnet-architecture-08)
>>
>>     I support this change;
>>
>>     Pascal
>>
>>     > -----Original Message-----
>>     > From: Lou Berger <lberger@labn.net <mailto:lberger@labn.net>>
>>     > Sent: mardi 20 novembre 2018 19:19
>>     > To: Pascal Thubert (pthubert) <pthubert@cisco.com
>>     <mailto:pthubert@cisco.com>>; Scharf, Michael
>>     > <Michael.Scharf@hs-esslingen.de
>>     <mailto:Michael.Scharf@hs-esslingen.de>>
>>     > Cc: detnet@ietf.org <mailto:detnet@ietf.org>;
>>     draft-ietf-detnet-architecture.all@ietf.org
>>     <mailto:draft-ietf-detnet-architecture.all@ietf.org>
>>     > Subject: Transport sub-layer name change (Was Re: [Detnet]
>>     Tsvart last
>>     > call review of draft-ietf-detnet-architecture-08)
>>     >
>>     > ALL,
>>     >
>>     > There is a desire to replace the word "Transport" from the DetNet
>>     > Transport sub-layer to avoid confusion with L$ Transport 
>> protocols.
>>     >
>>     > In the TEAS WG we had a similar discussion and we replaced
>>     "Transport"
>>     > with "Traffic Engineered (TE) ".
>>     >
>>     > While a bit more verbose, what do people think about this change?
>>     >
>>     > To be clear, the suggestion is:
>>     >
>>     > OLD
>>     >
>>     >                     .
>>     >                     .
>>     >       +----------------------------+
>>     >       |  DetNet Service sub-layer  | PW, UDP, GRE
>>     >       +----------------------------+
>>     >       | DetNet Transport sub-layer | IPv6, IPv4, MPLS TE LSPs,
>>     MPLS SR
>>     >       +----------------------------+
>>     >                     .
>>     >                     .
>>     >
>>     >                   Figure 4: DetNet adaptation to data plane
>>     >
>>     > NEW
>>     >
>>     >                     .
>>     >                     .
>>     >       +----------------------------+
>>     >       |  DetNet Service sub-layer  | PW, UDP, GRE
>>     >       +----------------------------+
>>     >       |      DetNet TE sub-layer   | IPv6, IPv4, MPLS TE LSPs,
>>     MPLS SR
>>     >       +----------------------------+
>>     >                     .
>>     >                     .
>>     >
>>     >                   Figure 4: DetNet adaptation to data plane
>>     >
>>     > Lou
>>
>
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet