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

"Susan Hares" <shares@ndzh.com> Fri, 03 July 2015 19:39 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 143291A7005; Fri, 3 Jul 2015 12:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=no
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 qd_brI25Worl; Fri, 3 Jul 2015 12:39:26 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (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 DAC061A7000; Fri, 3 Jul 2015 12:39:25 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.185.134;
From: Susan Hares <shares@ndzh.com>
To: "'BELOTTI, SERGIO (SERGIO)'" <sergio.belotti@alcatel-lucent.com>, 'Mahesh Jethanandani' <mjethanandani@gmail.com>
References: <00d901d0ade1$194280e0$4bc782a0$@ndzh.com> <D8FF75B2-4BB4-4A98-989B-10A2E480EBEF@gmail.com> <007501d0b37a$02d6fbd0$0884f370$@ndzh.com> <B9FEE68CE3A78C41A2B3C67549A96F48B75EA34E@FR711WXCHMBA05.zeu.alcatel-lucent.com>
In-Reply-To: <B9FEE68CE3A78C41A2B3C67549A96F48B75EA34E@FR711WXCHMBA05.zeu.alcatel-lucent.com>
Date: Fri, 03 Jul 2015 15:39:23 -0400
Message-ID: <01c801d0b5c7$f7058d80$e510a880$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01C9_01D0B5A6.6FF65E80"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQISFdXuYb8FEw5zRd6nzKGMwfXW3QKbN0DLAkJXomwCOt7Bop0On+6Q
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/5r-oBjxb6BTIMlMRPNUunG5_cBQ>
Cc: Rtg-yang-coord@ietf.org, i2rs@ietf.org, "'BRUNGARD, DEBORAH A'" <db3546@att.com>, 'Netconf' <netconf@ietf.org>, 'NETMOD Working Group' <netmod@ietf.org>
Subject: Re: [i2rs] [Rtg-yang-coord] [netmod] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jul 2015 19:39:28 -0000

Sergio: 

 

Just in case you missed in the rest of the email threads: 

 

Yes – I2RS plans to coordinate the topology model with the TEAS Topology model.  The work began with the authors last week, and will continue in a discussion of the TEAS And Topology authors next week (7/8)  in a conference call, and at IETF on Sunday (7/19 from 6-7pm). 

 

The I2RS WG will provide an update on the merging of these two models.  If you are a TEAS author, please let me know.   If you wish to help on an I2RS Topology model, the I2RS working group would appreciate your review of any model. 

 

I am personally working on the service layer model. 

 

Sue Hares 

From: BELOTTI, SERGIO (SERGIO) [mailto:sergio.belotti@alcatel-lucent.com] 
Sent: Wednesday, July 01, 2015 5:28 AM
To: Susan Hares; 'Mahesh Jethanandani'
Cc: Rtg-yang-coord@ietf.org; i2rs@ietf.org; 'NETMOD Working Group'; 'Netconf'; 'BRUNGARD, DEBORAH A'
Subject: RE: [Rtg-yang-coord] [netmod] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)

 

Hello Susan,

-          Topology model which is a composite of:

o   Generic topology model:  <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo/> draft-ietf-i2rs-yang-network-topo-01 

o   L3 topology model:  <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology/> draft-ietf-i2rs-yang-l3-topology-00 

o   L2 topology model:  <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology/> draft-ietf-i2rs-yang-l2-network-topology-00 

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