IETF Logo Mail Archive

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

"Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com> Wed, 19 July 2017 16:47 UTC

Return-Path: <michael.scharf@nokia.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 2358312EC3F for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 09:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level:
X-Spam-Status: No, score=-2.91 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_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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=nokia.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 2d5nza1Rfkqa for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 09:47:16 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0122.outbound.protection.outlook.com [104.47.2.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECDD2129482 for <teas@ietf.org>; Wed, 19 Jul 2017 09:47:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=IpxnEgbW/gnKrrmDcCYkoDwLInt7Rwj27Jcw0184Ir4=; b=Fl6hVxwTLLMw9SIgF7740D646tiYbOQkBrQN/SQNwk8d3J6FhLcdRFQ6GD+QTLviyEWSCxPCoUeO2QXQLti1+zO4qCuBULuvcwRzZLjTq/I76fuEeCfjfp7Lsauie2Apr3J1TSG1KmH+d4q5g6umlMQYlVz8qIcxXCRMMDUMKWc=
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com (10.173.92.15) by AM5PR0701MB1796.eurprd07.prod.outlook.com (10.167.215.155) 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 16:47:13 +0000
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com ([fe80::b4f5:bfaf:bef6:e736]) by AM5PR0701MB2547.eurprd07.prod.outlook.com ([fe80::b4f5:bfaf:bef6:e736%17]) with mapi id 15.01.1282.011; Wed, 19 Jul 2017 16:47:13 +0000
From: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>
To: Lou Berger <lberger@labn.net>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, TEAS WG <teas@ietf.org>
Thread-Topic: [Teas] "Hierarchical T-SDN Controller"
Thread-Index: AdMAY31MhKwsTD/KSDOTWzU1Cn4gEgABBRRgABEXAYAAAAiOUA==
Date: Wed, 19 Jul 2017 16:47:13 +0000
Message-ID: <AM5PR0701MB25479974442A24A70618A76693A60@AM5PR0701MB2547.eurprd07.prod.outlook.com>
References: <AM5PR0701MB25472B2B1574786C4C4FF12E93A60@AM5PR0701MB2547.eurprd07.prod.outlook.com> <AM2PR07MB099427639587A98BA6E36061F0A60@AM2PR07MB0994.eurprd07.prod.outlook.com> <15d5bad10d8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <15d5bad10d8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: labn.net; dkim=none (message not signed) header.d=none;labn.net; dmarc=none action=none header.from=nokia.com;
x-originating-ip: [135.245.212.21]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB1796; 7:74kyuvH4wMF3TW6FIIIV0OFDmH9LbPLTdpVXhlAL4Lu660LVBxbw//p03+wraYc8l5WNXl1b8GLZk83nq7JFAERilvyDQFrW1se6CwGhjsBqz9u4OCWyAPjClmZVWqtqo7y/Gtw6tBHNu0TfNFuFrELQFZu9gWAADjmSgL0RMQmpDkLYHXpSjYkGMldDPVv2G+lHXI3xCe7rCA2iZ0mxiiPKGNSnUh839zApMbGRFgM/7IRPY+ECRWVw4wNYjkzL8dioGxs+vJNZB+NlvZ0xq4jOL5Wf1DXOeIlDduoyFaGLeVjKzr+3TAlyEoCzVWUa8yKjrir5LjSZ3KgPLyhxYrud2nxmrYjdMcjz/c7ka8pf7QOv2tRdwCF6HM7br76wkSFL3aYmCOXRTiFPmn7oO76wUuAii7pqEQ9/Rfak5vObxrtzmC9JT1NQYIDpS70qZzMX+Q0WY0pZXYFUu8V1GYVCe70wOYl4SU6mpl2U3c9Y9JOol/fdIMohu7BaURYc/y11fUQdRtkhYvd5IRKC84m5gvxtT85b9EQuNiv/sxbrQmNshYcD9jfa9pAkPfd8Bjq2vqRn5PXY7kmEuW1zGNGOk8M6RNm8k5bsAtvmfn12s2mEoyxtfkZwVqqPHVI54/RaCjfj3nk6QKVYtinngBre8emZ1bxMr830mrjp6mz1168o8TmVukM/5PD/NPvvkZzddZYJBxx4up03GPBqz0wg71aih3CUTn3KWBT4sOC+V1OGn622MaklIiZnKaKJlPQY4Zsy9YZZlSsAlBKwEFSxWLkiuo32d6A2+tRTqLw=
x-ms-office365-filtering-correlation-id: f9089bec-95e1-434f-b8dd-08d4cec5ce6e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(48565401081)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:AM5PR0701MB1796;
x-ms-traffictypediagnostic: AM5PR0701MB1796:
x-exchange-antispam-report-test: UriScan:(151999592597050)(37575265505322)(26388249023172)(236129657087228)(82608151540597)(148574349560750)(21748063052155)(247924648384137)(17755550239193);
x-microsoft-antispam-prvs: <AM5PR0701MB17960F449FA00F921C1C128893A60@AM5PR0701MB1796.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(2017060910075)(10201501046)(93006095)(93001095)(3002001)(100000703101)(100105400095)(6055026)(6041248)(20161123564025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123560025)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM5PR0701MB1796; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM5PR0701MB1796;
x-forefront-prvs: 0373D94D15
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39400400002)(39850400002)(39410400002)(39840400002)(39860400002)(39450400003)(52314003)(377454003)(24454002)(6436002)(50986999)(229853002)(9686003)(33656002)(66066001)(6306002)(2950100002)(54896002)(7696004)(5250100002)(790700001)(6116002)(7736002)(53936002)(74316002)(3846002)(966005)(38730400002)(236005)(8936002)(76176999)(54356999)(6246003)(102836003)(189998001)(8676002)(25786009)(53546010)(606006)(81166006)(2900100001)(3280700002)(86362001)(3660700001)(2906002)(19609705001)(478600001)(99286003)(5660300001)(6506006)(14454004)(55016002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB1796; H:AM5PR0701MB2547.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM5PR0701MB25479974442A24A70618A76693A60AM5PR0701MB2547_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2017 16:47:13.1918 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB1796
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/sFFOtjmY-CVw1dUBNJzeqS6SVR8>
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 16:47:19 -0000

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>; Scharf, Michael (Nokia - DE/Stuttgart) <michael.scharf@nokia.com>; TEAS WG <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