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

"Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com> Wed, 19 July 2017 09:02 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 DE87C131C21 for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 02:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MANY_SPAN_IN_TEXT=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 kUM7pB_BYCuG for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 02:02:29 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30092.outbound.protection.outlook.com [40.107.3.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0EF712ECC0 for <teas@ietf.org>; Wed, 19 Jul 2017 02:02:28 -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=3CHqknnggN3BGPfnnZsQAiAWs9Tg5Auq6xOTSmNWpwg=; b=Wh3C7PxPp+/InkAxkZspDZGUz2my4xojWnnlKmDD3fegRDJvUnBJoA7MmBAVNLinHinfsFEUp5IsSGb2Rw5R3jUiRor3obOakwvH83pKWIp6LhF8mA0gZx6e/m1Zo2/EX4XCwiqnXJTI5rflhf82nwqzfJRdZwh035IdRygeQo4=
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com (10.173.92.15) by AM5PR0701MB1777.eurprd07.prod.outlook.com (10.167.215.148) 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 09:02:26 +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 09:02:26 +0000
From: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, TEAS WG <teas@ietf.org>
Thread-Topic: [Teas] "Hierarchical T-SDN Controller"
Thread-Index: AQHTAG0ot1+JK+/FoE6IvgGfOTApSqJa2biw
Date: Wed, 19 Jul 2017 09:02:26 +0000
Message-ID: <AM5PR0701MB25471846696D1505C5082AA893A60@AM5PR0701MB2547.eurprd07.prod.outlook.com>
References: <3C7F96DB-0ADE-42F6-BD1E-D1FF184EF72D@gmail.com>
In-Reply-To: <3C7F96DB-0ADE-42F6-BD1E-D1FF184EF72D@gmail.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=nokia.com;
x-originating-ip: [135.245.212.17]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB1777; 7:bRb+MRpNJtZCcLk++uaLIu3R1KvLQ3LG7+V6F+WstKvvqbXU/DYyYP2nfM61ir5KwD5Cv0THBS1bAQmD0gtxQyCTb2U6UIAnI9UUkQNPs2wWz4KGj+j/mZ8IiCar8jLNTEbOCEuZbKNJ5HKBBXWRRE0DB6o4w6U02wVrPn2q8kT5oezCrE8X0CgifrUUKUJHY2aAZ2/A0CumCj99/L9+K/zeMuGf13jXujPTMt/kYuTRZOYPei5nzL4KZAB46WZws6o74nWsf+SslhdsrYkVj4sHmFoL4w2LypCZfUTq7pubsv+6yeJJESaCn60Ee7ABU8+8qoPSM3GrVK7ykoejzmQT6O+zoikA16MNaFUaxPDGbASE1VCqhf+PdmAD1SFUgp21t6GHm7h4/AS4iG8Tdk4aZ9Eb4bYqriDvfOnY0BpW7q5OZjlX5aqAbHt8Qjb3x87H/daUj/cyIDYvYpY63gfcSLzDNcUm9tEBEespJytVQ2zSXtkHLaAawq7LGbJo54B1Vgvhm3vxXVMt9fKWGyxJXRvMMtcnb1dUXTwC7v5GloluPU+3NNc9H9EPCXev9LvkJngDuFSqylWLmXsqyesxAAe4m4JAExWczVpHArTxQmu9/fcl/63YhbNlRP37sK5liuRM4UdQJpWz5uX7mi0bNnjpzrFh7USq0em5cnYYe0vCnIdDeQZG90136XMm35h+AsXGiiehwiSJdOxHn6g3CpLE5Xm8cQvpCjn9I1EySYHIH61elTwPvU2OyfGsgwxkkMHuD5BpaONRosZ81wQ45fU1EUxt1np/c3bvxiQ=
x-ms-office365-filtering-correlation-id: dda100e7-5c74-4379-e471-08d4ce84e083
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)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:AM5PR0701MB1777;
x-ms-traffictypediagnostic: AM5PR0701MB1777:
x-exchange-antispam-report-test: UriScan:(151999592597050)(37575265505322)(26388249023172)(236129657087228)(82608151540597)(148574349560750)(21748063052155)(247924648384137)(17755550239193);
x-microsoft-antispam-prvs: <AM5PR0701MB1777B74BE03F9EE4D7D857C793A60@AM5PR0701MB1777.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(2017060910075)(8121501046)(5005006)(100000703101)(100105400095)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041248)(20161123562025)(20161123564025)(20161123558100)(20161123560025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM5PR0701MB1777; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM5PR0701MB1777;
x-forefront-prvs: 0373D94D15
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39450400003)(39850400002)(39840400002)(39860400002)(39410400002)(39400400002)(377454003)(52314003)(55016002)(229853002)(236005)(9686003)(6306002)(54896002)(7736002)(3660700001)(478600001)(966005)(74316002)(38730400002)(6506006)(7696004)(54356999)(53546010)(6246003)(606006)(53936002)(6116002)(5250100002)(2900100001)(39060400002)(102836003)(3846002)(76176999)(50986999)(790700001)(6436002)(99286003)(25786009)(5660300001)(33656002)(14454004)(86362001)(189998001)(8676002)(2950100002)(2906002)(3280700002)(8936002)(81166006)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB1777; H:AM5PR0701MB2547.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM5PR0701MB25471846696D1505C5082AA893A60AM5PR0701MB2547_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2017 09:02:26.2577 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB1777
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Wm_QWwwFA1lzhMpDqfUy37e7jHk>
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 09:02:31 -0000

As a chair in TSV, I can confirm that “transport” is used for L4 “stuff”.

As far as I can tell, the term “transport network” is not used for L4 “stuff”.

Michael



From: Jeff Tantsura [mailto:jefftant.ietf@gmail.com]
Sent: Wednesday, July 19, 2017 10:58 AM
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"

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<mailto:teas-bounces@ietf.org>> on behalf of Daniele Ceccarelli <daniele.ceccarelli@ericsson.com<mailto:daniele.ceccarelli@ericsson.com>>
Date: Wednesday, July 19, 2017 at 10:49
To: "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"

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<mailto:daniele.ceccarelli@ericsson.com>>; TEAS WG <teas@ietf.org<mailto: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<mailto:michael.scharf@nokia.com>>; TEAS WG <teas@ietf.org<mailto: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<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@ietf.org> https://www.ietf.org/mailman/listinfo/teas