Re: [Teas] "Hierarchical T-SDN Controller"

Jeff Tantsura <jefftant.ietf@gmail.com> Wed, 19 July 2017 08:58 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3C1131A85 for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 01:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 knD7C8K_d1ab for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 01:58:13 -0700 (PDT)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9266131A4C for <teas@ietf.org>; Wed, 19 Jul 2017 01:58:12 -0700 (PDT)
Received: by mail-wm0-x243.google.com with SMTP id p204so2674360wmg.1 for <teas@ietf.org>; Wed, 19 Jul 2017 01:58:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version; bh=t6fyrDGV7T0Wf3Pw6twpoyIWIGm2hR/7mjHy89yKY0U=; b=LP8LuPt/7HgOW2VwQVIjmlAm/yt2exdEEELxRomCvbuK+c17P1tx5txU3PMVxP31MA TzqrJ9KJu3D+4gZwJwPAO7bGD/Coo7x+jQE+7Oc9H2cVImtmiW1Req1PDdhngHQcp+t1 SteIOH+ATj7Vpo6C0jDdDKK3XhFKPsY+m0m/sm7yQKh3V7ZuhnZBme30YbJhfcheo1Yh JLQcm2Lzo62snK+aaEx3EPnROLpD1hql0+veXAqGLMZWIDuL0VRkbjlImCuUQloeFzmD keuCU0xCGLlIECZDmp1NrUwKm9NY7dQzVxZjHeDiQcrQqZGWrMHdrcLCpomixhx3zyL4 Yoxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version; bh=t6fyrDGV7T0Wf3Pw6twpoyIWIGm2hR/7mjHy89yKY0U=; b=aIoKFhCvzzEHulO3AjogkLT3wlsEZe2RHE6HBwb78gpIwJkx0j3hEVD/vKbLiCM70k Cv30NomlxRzHQZ6AmR7TIghgwoWG+cADSA86zwP/ihby8iGgjt5FIYJfhINIDGKcf5oK 1NevghzRzm+tEHi0d8OeEAlIegeTF09eeM8Smef1SQ9eV5TUI91OUI2a35YmcWnaMRzC iOcW/X9NIevu17KDOeCVk08s2bc26mnVQzlSSLyqZ1/4zS+kWNKbNxU30UoWFNrIZsCg KIf6mr5vNyaohWhdSzS9ZJVBOmKerSMOw/7wel1g7hc2XRdX32/PUUOiiyMo0Jweg8gB 8ZeA==
X-Gm-Message-State: AIVw111Ur9xAxWHlzYr0hEXr4HyVIxlcv1pyxlzfEDZe2uPXI870TdIJ unskiHT+vKtm+Q==
X-Received: by 10.28.136.147 with SMTP id k141mr5161726wmd.14.1500454691304; Wed, 19 Jul 2017 01:58:11 -0700 (PDT)
Received: from [31.133.131.152] ([2001:67c:370:128:310a:a8f0:9987:582b]) by smtp.gmail.com with ESMTPSA id j76sm7679805wmg.14.2017.07.19.01.58.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Jul 2017 01:58:10 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.24.0.170702
Date: Wed, 19 Jul 2017 10:58:09 +0200
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>, TEAS WG <teas@ietf.org>
Message-ID: <3C7F96DB-0ADE-42F6-BD1E-D1FF184EF72D@gmail.com>
Thread-Topic: [Teas] "Hierarchical T-SDN Controller"
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3583306690_746751106"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/FsARJSAdk5WmgbNeqzYqMoxBTmU>
Subject: Re: [Teas] "Hierarchical T-SDN Controller"
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 08:58:15 -0000

dealing with this on daily bases, outside of our, rather small world, transport is commonly understood as L4 “stuff”

 

Cheers,

Jeff

 

From: Teas <teas-bounces@ietf.org> on behalf of Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Date: Wednesday, July 19, 2017 at 10:49
To: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>, TEAS WG <teas@ietf.org>
Subject: Re: [Teas] "Hierarchical T-SDN Controller"

 

And on that i totally agree with you.

 

…and yes, on the netslices mailing list I was reprimanded by the transport ADs for using the term transport for non layer 4 stuff 😊

 

BR
Daniele  

 

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Scharf, Michael (Nokia - DE/Stuttgart)
Sent: mercoledì 19 luglio 2017 10:41
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>; TEAS WG <teas@ietf.org>
Subject: Re: [Teas] "Hierarchical T-SDN Controller"

 

Well, the IETF has an area called “TSV” and so in the IETF “transport” has yet another meaning ;-)

 

Given that, such terminology would have to be defined in IETF documents anyway. A definition of these terms could clarify the meaning for MPLS-TE and SR-TE.

 

Anyway, my key point is that I think the terminology used by draft-bryskin-te-topo-and-tunnel-modeling-00 is easy to understand by people outside the IETF.

 

Michael

 

 

 

From: Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com] 
Sent: Wednesday, July 19, 2017 10:28 AM
To: Scharf, Michael (Nokia - DE/Stuttgart) <michael.scharf@nokia.com>; TEAS WG <teas@ietf.org>
Subject: RE: "Hierarchical T-SDN Controller"

 

+1 , BUT…

 

We need to be careful with the word “transport”. In some contexts it refers to pure transport technologies (e.g. OTN, WDM) and does not include other upper layer TE technologies (e.g. MPLS-TE and SR-TE), in other contexts it includes also the latter. 
I’m more than happy to use the term transport SDN controller provided we’re all on the same page (which should be the second).

 

BR
Daniele  

 

 

 

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Scharf, Michael (Nokia - DE/Stuttgart)
Sent: mercoledì 19 luglio 2017 10:01
To: TEAS WG <teas@ietf.org>
Subject: [Teas] "Hierarchical T-SDN Controller"

 

In the (useful) I-D draft-bryskin-te-topo-and-tunnel-modeling-00, Section 1.9. “Multi-Domain Transport Service Coordination” uses the following wording:

 

   A client of multiple TE network domains may need to

   orchestrate/coordinate its transport service setup/manipulation

   across some or all the domains. One example of such a client is a

   Hierarchical T-SDN Controller, HC, managing a connected multi-domain

   transport network where each of the domains is controlled by a

   separate Domain T-SDN Controller, DC.

 

Outside the IETF, I have the impression that this terminology is quite common when discussing TEAS YANG models. I wonder whether we could use this terminology more frequently inside in TEAS.

 

Michael

_______________________________________________ Teas mailing list Teas@ietf.org https://www.ietf.org/mailman/listinfo/teas