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

"Susan Hares" <shares@ndzh.com> Tue, 07 July 2015 14:26 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC7511ACC7F for <rtg-yang-coord@ietfa.amsl.com>; Tue, 7 Jul 2015 07:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.055
X-Spam-Level:
X-Spam-Status: No, score=-99.055 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 3mC643jWqDgr for <rtg-yang-coord@ietfa.amsl.com>; Tue, 7 Jul 2015 07:26:46 -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 5A2061AC41F for <rtg-yang-coord@ietf.org>; Tue, 7 Jul 2015 07:26:22 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.124.203.226;
From: "Susan Hares" <shares@ndzh.com>
To: "'Tom Taylor'" <tom.taylor.stds@gmail.com>, <rtg-yang-coord@ietf.org>
References: <00d901d0ade1$194280e0$4bc782a0$@ndzh.com> <5594097C.70607@labn.net> <00d801d0b450$250e4560$6f2ad020$@ndzh.com> <CA+YzgTsJOptCtNqqccsFxGR6y+-kua2dW6NBsPru4fZY4PxnOg@mail.gmail.com> <559AE19E.9090004@gmail.com>
In-Reply-To: <559AE19E.9090004@gmail.com>
Date: Tue, 7 Jul 2015 10:26:21 -0400
Message-ID: <04e801d0b8c0$e5c0e500$b142af00$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQISFdXuYb8FEw5zRd6nzKGMwfXW3QL4Xs+nAlcpWbYBg5KlhQHndmfSnQeA4pA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/bYaP7P7nFuzLn6EilTSPpokBSoo>
Subject: Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS protocol and I2RS interim (6/24/2015 at 10:00 - 11:30am ET)
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2015 14:26:47 -0000

Tom:

We should chat.  Lime, TEAS, and I2RS are looking at multiple layer topology
models. 

LIME is looking at the configuration of OAM. 
TEAS is looking at traffic engineering. 
I2RS is looking at  Virtual topology that are created by the I2RS protocol. 
  
 I2RS topology protocol independent topologies are composites from
 other protocol-dependent topologies.   OAM could be consider one
 of those other protocol dependent.

Sue 

-----Original Message-----
From: Rtg-yang-coord [mailto:rtg-yang-coord-bounces@ietf.org] On Behalf Of
Tom Taylor
Sent: Monday, July 06, 2015 4:14 PM
To: rtg-yang-coord@ietf.org
Subject: Re: [Rtg-yang-coord] [i2rs] Requirements for I2RS protocol and I2RS
interim (6/24/2015 at 10:00 - 11:30am ET)

In theory, at least, LIME needs a topology model, but it has to cover
multiple layers. I'll keep an eye on this work.

Tom Taylor

On 01/07/2015 8:41 PM, Vishnu Pavan Beeram wrote:
> + Alex
> + <te-topo-model> authors
>
> Sue, Jeff,
>
> The authors of the <te-topo-model> draft had a meeting today with one 
> of the authors (Alex) of the <network-topo-model> draft and discussed 
> ways to align the topo models. The consensus so far is that the 
> <te-topo-model> WILL augment the <network-topo-model>. There are some 
> issues that need to be worked out (mapping identifiers, 
> termination-points), but those should get resolved in due course of time.
>
> I'll sync up with you (Sue) and coordinate a meeting between the 
> authors of the <te-topo-model> and the authors of the I2RS topo 
> model(s) at the IETF
> --- hopefully early in the week.
>
> Regards,
> -Pavan
>
...

_______________________________________________
Rtg-yang-coord mailing list
Rtg-yang-coord@ietf.org
https://www.ietf.org/mailman/listinfo/rtg-yang-coord