IETF Logo Mail Archive

Re: [netmod] [Rtg-yang-coord] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)

"BELOTTI, SERGIO (SERGIO)" <sergio.belotti@alcatel-lucent.com> Wed, 01 July 2015 09:27 UTC

Return-Path: <sergio.belotti@alcatel-lucent.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 055A21B2AD6; Wed, 1 Jul 2015 02:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 gPLO1qQ0pzsg; Wed, 1 Jul 2015 02:27:42 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (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 300BA1B2AA3; Wed, 1 Jul 2015 02:27:42 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 0B80BDE2F33D9; Wed, 1 Jul 2015 09:27:39 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id t619RaID028893 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Jul 2015 11:27:37 +0200
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.213]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Wed, 1 Jul 2015 11:27:36 +0200
From: "BELOTTI, SERGIO (SERGIO)" <sergio.belotti@alcatel-lucent.com>
To: Susan Hares <shares@ndzh.com>, 'Mahesh Jethanandani' <mjethanandani@gmail.com>
Thread-Topic: [Rtg-yang-coord] [netmod] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
Thread-Index: AQHQs3iywoO7BP7k/EicVuTrMAAx6p3Fa4wAgADr2RA=
Date: Wed, 01 Jul 2015 09:27:35 +0000
Message-ID: <B9FEE68CE3A78C41A2B3C67549A96F48B75EA34E@FR711WXCHMBA05.zeu.alcatel-lucent.com>
References: <00d901d0ade1$194280e0$4bc782a0$@ndzh.com> <D8FF75B2-4BB4-4A98-989B-10A2E480EBEF@gmail.com> <007501d0b37a$02d6fbd0$0884f370$@ndzh.com>
In-Reply-To: <007501d0b37a$02d6fbd0$0884f370$@ndzh.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: multipart/alternative; boundary="_000_B9FEE68CE3A78C41A2B3C67549A96F48B75EA34EFR711WXCHMBA05z_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/66SswWZtwThQejTs5Xi0ghVAEko>
X-Mailman-Approved-At: Wed, 01 Jul 2015 02:56:23 -0700
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, "i2rs@ietf.org" <i2rs@ietf.org>, "'BRUNGARD, DEBORAH A'" <db3546@att.com>, 'Netconf' <netconf@ietf.org>, 'NETMOD Working Group' <netmod@ietf.org>
Subject: Re: [netmod] [Rtg-yang-coord] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jul 2015 09:27:44 -0000

Hello Susan,
-          Topology model which is a composite of:
o   Generic topology model: draft-ietf-i2rs-yang-network-topo-01<https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo/>
o   L3 topology model: draft-ietf-i2rs-yang-l3-topology-00<https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology/>
o   L2 topology model: draft-ietf-i2rs-yang-l2-network-topology-00<https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology/>
o   L1 Topology model: draft-zhang-i2rs-l1-topo-yang-model-01 (-02 released later this week).
o   Service topology model: draft-hares-i2rs-service-topo-yang-model-00 (released on Wednesday)

At this time, none of the Topology models utilize Traffic engineering.  It is anticipated that these models will support traffic engineering.

Reading this , my question is whether there is intention for Traffic Engineering part of topology model to exploit/coordinate with Teas , and particularly with
 draft-liu-teas-yang-te-topo or to proceed with distinct contributions internal to I2RS.

Thanks
Sergio

v2.23.0 | Report a Bug | By Email