IETF Logo Mail Archive

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

Lou Berger <lberger@labn.net> Wed, 19 July 2017 16:27 UTC

Return-Path: <lberger@labn.net>
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 681FE12F3CB for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 09:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.699
X-Spam-Level:
X-Spam-Status: No, score=-4.699 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_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 nuuEuFXhpum1 for <teas@ietfa.amsl.com>; Wed, 19 Jul 2017 09:27:45 -0700 (PDT)
Received: from outbound-ss-1812.hostmonster.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) (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 B39DB12EA95 for <teas@ietf.org>; Wed, 19 Jul 2017 09:27:45 -0700 (PDT)
Received: from cmgw3 (cmgw4 [10.0.90.84]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id 29672175A79 for <teas@ietf.org>; Wed, 19 Jul 2017 10:27:45 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id mgTh1v00C2SSUrH01gTkvP; Wed, 19 Jul 2017 10:27:45 -0600
X-Authority-Analysis: v=2.2 cv=UM2tJGXy c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=G3gG6ho9WtcA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=0FD05c-RAAAA:8 a=48vgC7mUAAAA:8 a=_hDiSngTt8rgpdH6-uAA:9 a=UhVDmCrOWi02qMFK:21 a=osYLCc8fgD6e2eff:21 a=QEXdDO2ut3YA:10 a=GEZNxZAR3QCbIAV6ulwA:9 a=DNw09DOyXI7uhQWj:21 a=vRr1cjl1yL-C-S9G:21 a=hdMd6bnnhW4TqWTz:21 a=UiCQ7L4-1S4A:10 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=l1rpMCqCXRGZwUSuRcM3:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:MIME-Version:Subject:References:In-Reply-To: Message-ID:Date:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=fbeUimS7N45OUgR/DiPtjbkpDgsoQV3UGWvh5XRCqS0=; b=qsNa/hvuQ8504w9YwIa4u3+rXI 3vpZmVK4gO0G+KSV20tGkvo292plKB3+Hez2HoN2JA+pgLGJazii4vZKFqZ+A1GxVRkAsv3hn45LA PY4Vrt1tND7iNiDxrrB8z9Nw6;
Received: from dhcp-8d1b.meeting.ietf.org ([31.133.141.27]:48049) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1dXrp6-003n4W-RL; Wed, 19 Jul 2017 10:27:41 -0600
From: Lou Berger <lberger@labn.net>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>, TEAS WG <teas@ietf.org>
Date: Wed, 19 Jul 2017 18:27:35 +0200
Message-ID: <15d5bad10d8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <AM2PR07MB099427639587A98BA6E36061F0A60@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <AM5PR0701MB25472B2B1574786C4C4FF12E93A60@AM5PR0701MB2547.eurprd07.prod.outlook.com> <AM2PR07MB099427639587A98BA6E36061F0A60@AM2PR07MB0994.eurprd07.prod.outlook.com>
User-Agent: AquaMail/1.10.0-403 (build: 101000001)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------15d5bad12552fea27d365cddcf"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 31.133.141.27
X-Exim-ID: 1dXrp6-003n4W-RL
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: dhcp-8d1b.meeting.ietf.org [31.133.141.27]:48049
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/DHNK9-MwuyjJz25Dm5DAHSyUvc0>
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:27:47 -0000

TE-SDN? SDN-TE? SDN4TE?

TE orchistrator?
TE controller?

...


On July 19, 2017 10:28:40 AM Daniele Ceccarelli 
<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>
> 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
>

v2.23.0 | Report a Bug | By Email