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

Toerless Eckert <tte@cs.fau.de> Wed, 21 November 2018 16:56 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 13FAC128AFB; Wed, 21 Nov 2018 08:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 0-rDwLWUV9hX; Wed, 21 Nov 2018 08:56:14 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15CE7123FFD; Wed, 21 Nov 2018 08:56:13 -0800 (PST)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id AADC5548028; Wed, 21 Nov 2018 17:56:08 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 95B47440210; Wed, 21 Nov 2018 17:56:08 +0100 (CET)
Date: Wed, 21 Nov 2018 17:56:08 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Lou Berger <lberger@labn.net>
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>
Message-ID: <20181121165608.z7zpoh72jdnf4ybm@faui48f.informatik.uni-erlangen.de>
References: <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> <fcdf4022-5891-ad10-dd51-e771d0c5e028@labn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <fcdf4022-5891-ad10-dd51-e771d0c5e028@labn.net>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/CEdFzSkeEdN-otY-PC_p49ER2TI>
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: Wed, 21 Nov 2018 16:56:17 -0000

Thanks, Lou, inline

On Tue, Nov 20, 2018 at 05:34:09PM -0500, Lou Berger wrote:
> > 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"

AFAIK, TE classically does include protection, such as in RSVP-TE. Yet
in DetNet, protection is specifically part of the service sub-layer,
and arguably you probably won't want to reuse pre-existing protection
mechanism of the transport/TE sub-layer without a lot of further design
considerations if you're using the DetNet Service sub-layer
protection, so that TE/transport sub-layer is not really doing full TE.

Toerless

> 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
> > 
> 
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet