IETF Logo Mail Archive

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

Daniele Ceccarelli <daniele.ceccarelli@ericsson.com> Wed, 19 July 2017 18:09 UTC

Return-Path: <daniele.ceccarelli@ericsson.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 AE1CA131A62 for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 11:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.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 N8QKvCZDlwA2 for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 11:09:50 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 B2EA4131B88 for <teas@ietf.org>; Wed, 19 Jul 2017 11:09:49 -0700 (PDT)
X-AuditID: c1b4fb30-703ff70000001664-23-596fa06b8c9e
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 84.52.05732.B60AF695; Wed, 19 Jul 2017 20:09:48 +0200 (CEST)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.72) with Microsoft SMTP Server (TLS) id 14.3.352.0; Wed, 19 Jul 2017 20:09:47 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=X745l13PIyJm9wp02F+uCR6EoUO/nxhFK/CttFtZT4Q=; b=JbpN5iNCpsZe4QssCUlzEaKrXE2tDtQTleHM+8EHP+EQ/jiQjM6e1B5TjH2ArwKZttqxeO5RydbJhoFw+pAs/+5jsXIS63urowKWRF2+A2lOuFQNF9ZPFdB4Ui42a5k+q1m5JjR4e6kdBkvqBqin3IYU2NSKLJ0B0f7PEf0Y02g=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB1010.eurprd07.prod.outlook.com (10.162.37.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1282.4; Wed, 19 Jul 2017 18:09:46 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([fe80::8512:cee5:a76e:ebf7]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([fe80::8512:cee5:a76e:ebf7%13]) with mapi id 15.01.1282.008; Wed, 19 Jul 2017 18:09:46 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>, Lou Berger <lberger@labn.net>, TEAS WG <teas@ietf.org>
Thread-Topic: [Teas] "Hierarchical T-SDN Controller"
Thread-Index: AdMAY31MhKwsTD/KSDOTWzU1Cn4gEgABBRRgABEXAYAAAAiOUAADdbUA
Date: Wed, 19 Jul 2017 18:09:46 +0000
Message-ID: <AM2PR07MB099469853D8F9128C38C4A2FF0A60@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <AM5PR0701MB25472B2B1574786C4C4FF12E93A60@AM5PR0701MB2547.eurprd07.prod.outlook.com> <AM2PR07MB099427639587A98BA6E36061F0A60@AM2PR07MB0994.eurprd07.prod.outlook.com> <15d5bad10d8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <AM5PR0701MB25479974442A24A70618A76693A60@AM5PR0701MB2547.eurprd07.prod.outlook.com>
In-Reply-To: <AM5PR0701MB25479974442A24A70618A76693A60@AM5PR0701MB2547.eurprd07.prod.outlook.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: nokia.com; dkim=none (message not signed) header.d=none;nokia.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2001:67c:1232:144:357c:e046:79bc:24bb]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM2PR07MB1010; 7:Bg7Aftvu+SKA8w2fzdnK9NwwLwszl1ka8GL/Eho5CrI9C1/EPgjjLdWYnQPvrFaeoNFwCPLr7d8FdEyyjI/q2dZo54StrCa1USmrYS4DxgBOlErb5K8agc7+9TV6K/dLxD8r0bIi8xeV/YduLE8VYgFxIWbSN+T6Sk+NZMhCEjR4FPdZrW6Ssz7x5fhbUjx4EocxgS2t9JbcES65JB9PScX/AgfQjC0bk0NIM9uQBg0xwUxdTyWvlNUtfAL/XJtCpHUp7ECnc+s1wIffzWPz8rXG8VgN98j9UbXQ0rOCQldwEuiscP8/LBm4mrl+iHKxAWQFHxkjnXMcCvNHuWw3n8CjfB2zbse8a41ovMvgCqN2+9NVjlyxmGivIRpdF6Zxa/yGqO1HPA9xb8SbMsQVgzIn39Dpw1vT5rVAN7eRcEbKhMQrOvIp4z2+hF0whBipqxBU77tiOB8TgvY2xCizoqcl9Cv3B1+Z0sa7Feuh0MjH9oc6DxIuoLOEJZLc3GH40qZyzyDzA9tbFhS2WkbXIE+QGXtupsTHDjg7L7zA1MzBjl6P81YpjBs+Do8YLOAxPIrF7/m9ylns8hu7msKgofZ6SSgv5hI8n+A3132bzwzvIZgbpk1XoMgWjT//NR+FlYFwuJ0iUAZnnpsxAP6YP8Zd6c2jLQUEZBcsflCJdxrdpnlWUkeXQiJuHaeG5J1nBNm2mrupmY8/TUWtcPvY4r0pKZeAea1Ewr/MTWk24nh7fuv8sO2CxagTOZTEB+AbDNCyrbvkYz7HwMd2wwSKWriSsRsTTtS1ZOD6rZM6uUg=
x-ms-office365-filtering-correlation-id: 5c845d17-e241-465e-d3f7-08d4ced156bb
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:AM2PR07MB1010;
x-ms-traffictypediagnostic: AM2PR07MB1010:
x-exchange-antispam-report-test: UriScan:(151999592597050)(37575265505322)(26388249023172)(236129657087228)(82608151540597)(148574349560750)(21748063052155)(247924648384137)(17755550239193);
x-microsoft-antispam-prvs: <AM2PR07MB1010CE7A9B4367956122D5B0F0A60@AM2PR07MB1010.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(2017060910075)(10201501046)(100000703101)(100105400095)(93006095)(93001095)(3002001)(6041248)(20161123562025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123555025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM2PR07MB1010; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM2PR07MB1010;
x-forefront-prvs: 0373D94D15
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(39840400002)(39410400002)(39400400002)(39450400003)(39850400002)(24454002)(52314003)(377454003)(33656002)(25786009)(6436002)(76176999)(54356999)(38730400002)(50986999)(236005)(54896002)(6306002)(9686003)(99286003)(55016002)(53936002)(2950100002)(2900100001)(229853002)(6246003)(93886004)(6506006)(7736002)(966005)(81166006)(3280700002)(5250100002)(7696004)(2906002)(189998001)(86362001)(14454004)(3660700001)(5660300001)(6116002)(102836003)(8676002)(790700001)(478600001)(606006)(53546010)(74316002)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB1010; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM2PR07MB099469853D8F9128C38C4A2FF0A60AM2PR07MB0994eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2017 18:09:46.2287 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB1010
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SbUhTYRTHee7LdhUXTzbxYPnBgaADnVrRCkkliBUVRl80tJp5UXNusrss i8Kc4tyaKailmBtppob5gqDOF9TKVDBfkD5IpuHIxCwTI00bbbsL/PY/53fO8z/n8DCkbw8d wGSodaxWrVRJBN5UVUKXIkxl1SRGvC1DcoN+jZJvT0vlhVvdVCypqK/fJhTrHXqBYn5uhogn L3tHp7KqjBxWKzt5zTvd3N8nzP7UiW6PGlbpPLTViozIiwF8BGbK84RG5M344jcIJr5aSD4Y RWD9aKJcAYXNJKybbR5SQYCjYpXggyUEec3fBEbEMAJ8AuzD51x5MdYjGDJ00S6TA/gwfKmz urXYaVg7tUnx+jQ0jJS4B6FwMNhGzQKXFuEksC/98hiMEdDYX0i4gBdWQn5Lk7sZ4UAo7X3m biaxP8zZLQS/EYb6vkmS136wsuSgXQ8hbEZQsWuieHAcJoaee4oCYcZiQq4iwIsCeG1dFvDg PDzKr6F5ME3AQEebB0hhqM4i4MEAggX7B493JnRurZGeDhpsP58IeXAIGn7bPB7tNGyWLQr5 0wTA/GwxKkWh1XsW4bUGXvU4yGr3RfbDWJWdqnZemcSh0GqT8SVBUG76LOR1CBTWPBXuzVuR sBn5cSyXkpUWFRXOajOuc5xGHa5mdR3I+aGGOnciutHKctwwwgyS+Ij2FWgSfWllDpebNYyA ISVikazWmRKlKnPvsFrNVe1NFcsNo4MMJfEXxQ1MJfjiNKWOzWTZbFb7nxKMV0Aeai4Pe/Bj LLuoRqdvOhPXmHw52KqRxrxfd1zRxRtuvZh7KC63RR8dD0yc9ZELLyWtzBYW91S2hYzIuHtr g0GnNnYW/iZOLI4aYi+2NH1/Z/J5WZVuPNteuVITbC4puOCAmMe723HJCSl/NvrvF0X0bt4d lE7SkSbmRpYl9Nj4jlhCcenKSCmp5ZT/AKyNDqRMAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/ZIaIEj4at3TAULkNKLDdxcNmbhg>
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 18:09:55 -0000

I agree,

and this is also the major change in the latest version of the framework.

IMO it is correct to say that the MDSC is a functionality of the Orchestrator and that the PNC is a functionality of the domain T-SDN controller, hence speaking about Orchestration and T-SDN is not inappropriate.

BR
Daniele

From: Scharf, Michael (Nokia - DE/Stuttgart) [mailto:michael.scharf@nokia.com]
Sent: mercoledì 19 luglio 2017 18:47
To: Lou Berger <lberger@labn.net>; Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>; TEAS WG <teas@ietf.org>
Subject: RE: [Teas] "Hierarchical T-SDN Controller"

I have the impression that the TEAS YANG models may be implemented by a (TE) function/component/entity/… inside what others in industry may call (T-SDN) domain controller or (T-SDN) hierarchical controller. Orchestrator or coordinator may also work for the latter.

Specifically, I find it confusing to use the term “controller” for a (TE) function/component/entity/… *inside* of what may be called a domain controller, e.g., outside the IETF.

Anyway, I have no particular opinion on whether to use “T-SDN” or another term as long as those terms are not too far away from what somebody outside the IETF would typically enter into a search engine.

Michael




From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Lou Berger
Sent: Wednesday, July 19, 2017 6:28 PM
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com<mailto:daniele.ceccarelli@ericsson.com>>; Scharf, Michael (Nokia - DE/Stuttgart) <michael.scharf@nokia.com<mailto:michael.scharf@nokia.com>>; TEAS WG <teas@ietf.org<mailto:teas@ietf.org>>
Subject: Re: [Teas] "Hierarchical T-SDN Controller"


TE-SDN? SDN-TE? SDN4TE?

TE orchistrator?
TE controller?

...

On July 19, 2017 10:28:40 AM Daniele Ceccarelli <daniele.ceccarelli@ericsson.com<mailto:daniele.ceccarelli@ericsson.com>> wrote:
+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<mailto: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<mailto:Teas%40ietf.org>
https://www.ietf.org/mailman/listinfo/teas

v2.23.0 | Report a Bug | By Email