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

Lou Berger <lberger@labn.net> Tue, 20 November 2018 22:34 UTC

Return-Path: <lberger@labn.net>
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 26C66130E5D for <detnet@ietfa.amsl.com>; Tue, 20 Nov 2018 14:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 PCeKcG9ifjPu for <detnet@ietfa.amsl.com>; Tue, 20 Nov 2018 14:34:13 -0800 (PST)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) (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 69D69130E5B for <detnet@ietf.org>; Tue, 20 Nov 2018 14:34:13 -0800 (PST)
Received: from cmgw12.unifiedlayer.com (unknown [10.9.0.12]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 0B8A31E1163 for <detnet@ietf.org>; Tue, 20 Nov 2018 15:34:11 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id PEawgsDlOVl4fPEawg2861; Tue, 20 Nov 2018 15:34:11 -0700
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=qvho1GSC1q3TUZR4lH6XVbU7gjwLtAa8qtRBxSRBOSM=; b=Q/etJu6bw0fbRtl0KUdCmb0IR6 VKSnETpyZC0hTJV0RB/JrMvQaxV9mYNeApDtCXC9Jbhwc2CsoaRiotKlcwx2kv3N20kKL1nWBegSl v96oq+CT4VKERmWkgpJr3Wf2E;
Received: from pool-100-15-106-211.washdc.fios.verizon.net ([100.15.106.211]:47416 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1gPEaw-000I3R-L3; Tue, 20 Nov 2018 15:34:10 -0700
To: Toerless Eckert <tte@cs.fau.de>
Cc: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "Andrew G. Malis" <agmalis@gmail.com>, Michael.Scharf@hs-esslingen.de, draft-ietf-detnet-architecture.all@ietf.org, "Grossman, Ethan A." <eagros@dolby.com>, detnet WG <detnet@ietf.org>
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> <20181120213422.6zitt6iqhd5rmb6k@faui48f.informatik.uni-erlangen.de>
From: Lou Berger <lberger@labn.net>
Message-ID: <fcdf4022-5891-ad10-dd51-e771d0c5e028@labn.net>
Date: Tue, 20 Nov 2018 17:34:09 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <20181120213422.6zitt6iqhd5rmb6k@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.106.211
X-Source-L: No
X-Exim-ID: 1gPEaw-000I3R-L3
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-106-211.washdc.fios.verizon.net ([IPv6:::1]) [100.15.106.211]:47416
X-Source-Auth: lberger@labn.net
X-Email-Count: 7
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/Gn_pLoQQtbzKvskqABUUfCHaoxs>
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: Tue, 20 Nov 2018 22:34:16 -0000

Hi Toreless,

On 11/20/2018 4:34 PM, Toerless Eckert wrote:
> IMHO, "Traffic Engineering" will be worse than "Transport":

FWIW David Black - suggested that "Transport Network" as another 
alternative.

> - Makes more important people confused
>
>    IMHO, the mayor group of people (rightfully) confused by the term "Transport"
>    in the DetNet context are IETF apps and transport area people, and
>    quite frankly, thats not the primary reader constituency of DetNet
>    documents. Network operators / vendors / TSN members / TSN solutoin
>    devenlopers,


> aka: the primary reader consitutency for DetNet documents will
>    IMHO be less confused by "Transport" than by "Traffic Engineering".
>
> - Creates even more inconsistent confusion
>
>    IMHO, Differnt confused people will even more likely assume through
>    name recognition a lot more different functions into "Traffic
>    Engineering". (TE means RSVP-TE, oh no, TE means network planning,
>    TE can not mean QoS, TE is jut admission control, no TE needs to be
>    per-hop, yada yada yada).
>
> I am not arguing for keeping Transport, i am just more worried about
> "Traffic Engineering" than "Transport". I think a uniue new term without
> name recognition and resulting confusion would be best.
>
> Maybe form a new term from key words like the following, eg.:
>
>   DetNet Flow SubNetwork Encapsulation and Adaption Layer (DF-SEAL)
>
I personally think we have enough terms and should go with "DetNet TE 
Sub-Layer", "DetNet TE Network Sub-Layer", or  "DetNet Transport Network 
Sub-Layer"

Lou

> Cheers
>      Toerless
>
> On Tue, Nov 20, 2018 at 04:10:58PM -0500, 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
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
>