Re: [irs-discuss] Suggestions for IRS Way Forward

Susan Hares <susan.hares@huawei.com> Thu, 02 August 2012 23:38 UTC

Return-Path: <susan.hares@huawei.com>
X-Original-To: irs-discuss@ietfa.amsl.com
Delivered-To: irs-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA43C11E80F0 for <irs-discuss@ietfa.amsl.com>; Thu, 2 Aug 2012 16:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.641
X-Spam-Level:
X-Spam-Status: No, score=-4.641 tagged_above=-999 required=5 tests=[AWL=1.358, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZPelfvO4IVZU for <irs-discuss@ietfa.amsl.com>; Thu, 2 Aug 2012 16:38:41 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1E30311E8072 for <irs-discuss@ietf.org>; Thu, 2 Aug 2012 16:38:41 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIQ40065; Thu, 02 Aug 2012 15:38:40 -0800 (PST)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 2 Aug 2012 16:37:04 -0700
Received: from dfweml509-mbs.china.huawei.com ([169.254.12.123]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.003; Thu, 2 Aug 2012 16:36:58 -0700
From: Susan Hares <susan.hares@huawei.com>
To: Thomas Nadeau <tnadeau@juniper.net>, James Kempf <james.kempf@ericsson.com>, "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Thread-Topic: [irs-discuss] Suggestions for IRS Way Forward
Thread-Index: Ac1w/aRFxquJYy0LSJCFfpb4MILlegAO51CAAA0BS4D//6fIgIAAc/XQ
Date: Thu, 02 Aug 2012 23:36:57 +0000
Message-ID: <728F9B956B2C48439CA9294B1723B14623755EA0@dfweml509-mbs.china.huawei.com>
References: <728F9B956B2C48439CA9294B1723B14623755E3C@dfweml509-mbs.china.huawei.com> <CC405A5A.2DDA%tnadeau@juniper.net>
In-Reply-To: <CC405A5A.2DDA%tnadeau@juniper.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.212.245.215]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [irs-discuss] Suggestions for IRS Way Forward
X-BeenThere: irs-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <irs-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/irs-discuss>
List-Post: <mailto:irs-discuss@ietf.org>
List-Help: <mailto:irs-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 23:38:41 -0000

Tom:

Knowing authors of these drafts, this is true. They believe there is more to do. They proposed initial work and provide running code to test the ideas. 

Love to hear about where you think the holes are in each of these protocols. 

Sue 

-----Original Message-----
From: Thomas Nadeau [mailto:tnadeau@juniper.net] 
Sent: Thursday, August 02, 2012 4:28 PM
To: Susan Hares; James Kempf; irs-discuss@ietf.org
Subject: Re: [irs-discuss] Suggestions for IRS Way Forward



On 8/2/12 4:21 PM, "Susan Hares" <susan.hares@huawei.com> wrote:

>Tom:
>
>So, is ALTO, PCE, Yang modules with topology in scope.

	I think those are very good and important components yes.

>Are you stating that we do not re-inventing the ALTO functions topology
>(see previous note)?

	I'd definitely prefer to not reinvent those functions unless there are
good reasons to do so.
However, as Alia explained during the meeting, they are incomplete.


	--Tom



> 
>
>Sue 
>
>-----Original Message-----
>From: irs-discuss-bounces@ietf.org [mailto:irs-discuss-bounces@ietf.org]
>On Behalf Of Thomas Nadeau
>Sent: Thursday, August 02, 2012 3:32 PM
>To: James Kempf; irs-discuss@ietf.org
>Subject: Re: [irs-discuss] Suggestions for IRS Way Forward
>
>
>	I agree that one of the top work items for this effort should be a
>standardized topology function, and one that is accessible via a
>non-routing protocol.  While not exactly "low hanging fruit", it is
>something that (to me) is a clear work item with clear goals that should
>be tackled straight away.
>
>	--Tom
>
>
>
>On 8/2/12 3:24 PM, "James Kempf" <james.kempf@ericsson.com> wrote:
>
>>So after seeing part of Alia's talk this morning (I had to leave in the
>>middle unfortunately), I'd like to make a couple suggestions. There were
>>a lot of ideas presented in the talk, enough for an entire IETF Area. I
>>think to make tangible progress, the work needs to be focussed on a small
>>subset that would be of immediate interest and usability.
>>
>>There are a couple areas that suggest themselves, but one that would be
>>useful in work that I've been involved in is a standardized format for
>>network topology representation and a protocol for exchanging it. The
>>Onix OpenFlow controller has a network information base with a
>>specialized format for network topology, and every OpenFlow controller
>>requires this. Having a standardized way to represent it might foster a
>>common topology database package. Another application is network
>>management. Every network management system needs some kind of topology
>>representation. Finally, though I am not an expert in PCE construction,
>>it would seem to me that a PCE would need some kind of topology
>>representation in order to perform path calculations. Having a way,for
>>example, for the OpenFlow controller and the PCE to exchange topology
>>information would be really useful.  I would say to start with physical
>>topology because that is fundamental, but make the format flexible enough
>>to support 
>> virtual topology representation.
>>
>>			jak
>>_______________________________________________
>>irs-discuss mailing list
>>irs-discuss@ietf.org
>>https://www.ietf.org/mailman/listinfo/irs-discuss
>
>_______________________________________________
>irs-discuss mailing list
>irs-discuss@ietf.org
>https://www.ietf.org/mailman/listinfo/irs-discuss