[irs-discuss] 答复: 答复: IRS comments

Mach Chen <mach.chen@huawei.com> Fri, 17 August 2012 02:39 UTC

Return-Path: <mach.chen@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 E0AF221F84D1 for <irs-discuss@ietfa.amsl.com>; Thu, 16 Aug 2012 19:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.771
X-Spam-Level:
X-Spam-Status: No, score=0.771 tagged_above=-999 required=5 tests=[AWL=-2.017, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yNOt16GpCvL for <irs-discuss@ietfa.amsl.com>; Thu, 16 Aug 2012 19:39:46 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5EED521F84B6 for <irs-discuss@ietf.org>; Thu, 16 Aug 2012 19:39:37 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath) with ESMTP id AJM11439; Thu, 16 Aug 2012 18:39:36 -0800 (PST)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 16 Aug 2012 19:38:00 -0700
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 16 Aug 2012 19:38:06 -0700
Received: from SZXEML511-MBS.china.huawei.com ([169.254.4.86]) by szxeml420-hub.china.huawei.com ([10.82.67.159]) with mapi id 14.01.0323.003; Fri, 17 Aug 2012 10:38:03 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Alia Atlas <akatlas@gmail.com>
Thread-Topic: 答复: [irs-discuss] IRS comments
Thread-Index: Ac1utoJXMLn1Fv5cTmO9ZkEBmEbA7gABwUJeAhOezIAAAeHBAAABnwCAAHz4WAAAYnx4AAADAtaAAAFAFIAAAWTiAAACsjgAAABFcQAAA0u0AAAADucAAAA1foAAAckFAAAHy5EAAAHV1YAAAdkdAAAEme+AAAUvGYAAFVTUAAADbfoAAAUkXwAADptygAARQljg//994gD//3mk8A==
Date: Fri, 17 Aug 2012 02:38:02 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE22CA3B61E@SZXEML511-MBS.china.huawei.com>
References: <812700A304640D4292205D5E83FC59E1061C211D@p-embx01-eq.jnpr.net> <CAG=JvvjYk_E6+Qdidyyjc5oDss9HeA2aq2pt5ciQeX06fuiWsQ@mail.gmail.com> <CAG4d1reLL2_4KRb6yseJK9WTB47YzumMBGdu+UwcOWXxmE0M8Q@mail.gmail.com> <CAG=JvvjVhGsVcSzEFxDKKfNckQxgQiWeezWvwpcoAOSgOP--Nw@mail.gmail.com> <CAG4d1rd_p6x_+PsHWtsYU=oOCT-GnmnZNL+MHcJf4NEG5boP7A@mail.gmail.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33BC4A@MDWEXGMB02.ciena.com> <CAG4d1reWGjUU-z=9Gx_MvetAWF6wM8oUMpQRc9hxOg1MU37X_w@mail.gmail.com> <A3C4E51A53661B4EBEE7C5F5E6FCDEB5025AB94FE6D2@USEXCHANGE.corp.extremenetworks.com> <CAG4d1rfD8_0WgzRqH-OVAxfn1RYNfY_ynwkcmqN3MBYyrn5TnQ@mail.gmail.com> <3512BB31280C39448A9880F61DD54CEB09C07E@xmb-aln-x09.cisco.com> <CAG4d1rcvk1RmRmrpCwiAGx9s0v3X9aPECdeF1Wz7WSuYwzdFKA@mail.gmail.com> <CACKN6JH8eiYty3QOZ+E5Nt0wO3nYn87yB3pKixJK-3dnaOXfLQ@mail.gmail.com> <CACKN6JFMZqOnHU=vEkx8WxwSLjg5MYY=-VoJ7uOt8SAzvbAT6Q@mail.gmail.com> <A3C4E51A53661B4EBEE7C5F5E6FCDEB5025AB94FE847@USEXCHANGE.corp.extremenetworks.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C0A0@MDWEXGMB02.ciena.com> <CAG4d1rehfWk-HX27eysze8zdDzjNk4h4wwj2zV6_WJWxoNxY8Q@mail.gmail.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C26F@MDWEXGMB02.ciena.com> <B17A6910EEDD1F45980687268941550FB7B7B6@MISOUT7MSGUSR9I.ITServices.sbc.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C2BD@MDWEXGMB02.ciena.com> <C584046466ED224CA92C1BC3313B963E09F22C5413@INBANSXCHMBSA3.in.alcatel-lucent.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C554@MDWEXGMB02.ciena.com> <CAG4d1rdkT3C9tyuzY+Q8rCQJQ1C419xHTj_jCY5h1YXBMAbi3g@mail.gmail.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C7ED@MDWEXGMB02.ciena.com> <CAG4d1rcni-kpOqKmwX=371m62yJu8fGkGn_neBJ28VbqftA83g@mail.gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE22CA3B5CE@SZXEML511-MBS.china.huawei.com> <CAG4d1rfU5djTXrTuW3XbMUFAjsK598nnqzSRFH3yfxOLOgQVzg@mail.gmail.com>
In-Reply-To: <CAG4d1rfU5djTXrTuW3XbMUFAjsK598nnqzSRFH3yfxOLOgQVzg@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.96.190]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "UTTARO, JAMES" <ju1738@att.com>, "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>, "Shah, Himanshu" <hshah@ciena.com>, "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Subject: [irs-discuss] 答复: 答复: IRS comments
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: Fri, 17 Aug 2012 02:39:47 -0000

Hi Alia,

It's great to define uniform interfaces to the applications, but I am not sure whether the IRS interfaces could be directly used by the applications, in the IRS framework, the applications talk to the IRS agents, IMHO, the IRS agent (it may be the controller or orchestrator role from the SDN point of view, and the IRS interfaces are the southbound interfaces ) should shield the variety of the IRS interfaces.  

And I agree that we should currently focus on the use cases and then define a clear scope. Here is a rough SDN related use case draft (http://tools.ietf.org/html/draft-mm-sdn-vc-vn-on-demand-use-case-01), I am not sure this is related to IRS. 

Best regards,
Mach

> -----邮件原件-----
> 发件人: Alia Atlas [mailto:akatlas@gmail.com]
> 发送时间: 2012年8月17日 10:13
> 收件人: Mach Chen
> 抄送: Shah, Himanshu; UTTARO, JAMES; Dutta, Pranjal K (Pranjal);
> irs-discuss@ietf.org
> 主题: Re: 答复: [irs-discuss] IRS comments
> 
> Hi Mach,
> 
> Right - that is one reason why I'm not sure that a CSPF computation
> piece is needed for the RSVP sub-interface.  On the other side,
> there's benefit to not requiring an application to understand too many
> different protocols.
> 
> We need to discuss what scope makes sense for the sub-interfaces.  I
> think the use-cases will drive this.
> 
> Alia
> 
> On Thu, Aug 16, 2012 at 10:06 PM, Mach Chen <mach.chen@huawei.com>
> wrote:
> > Hi Alia,
> >
> > I am a little confused, the said RSVP sub-interface (on-demand CSPF interface)
> seems what exactly PCEP does today. My understanding of IRS is that it may be
> complementary on topology discovery.
> >
> > Best regards,
> > Mach
> >
> >> -----邮件原件-----
> >> 发件人: irs-discuss-bounces@ietf.org [mailto:irs-discuss-bounces@ietf.org]
> 代
> >> 表 Alia Atlas
> >> 发送时间: 2012年8月17日 9:45
> >> 收件人: Shah, Himanshu
> >> 抄送: UTTARO, JAMES; Dutta, Pranjal K (Pranjal); irs-discuss@ietf.org
> >> 主题: Re: [irs-discuss] IRS comments
> >>
> >> I'm not entirely clear on the model or question you are asking.  An
> >> application could learn topology via IRS to the appropriate IRS
> >> agents, do CSPF computations, and support a signaling/CSPF-like
> >> sub-interface (if we define such for IRS) as an IRS agent.  Another
> >> application could query the first for the CSPF results and then use
> >> IRS to trigger signaling on the appropriate device.
> >>
> >> I'm not sure if it makes sense to have an IRS sub-interface that
> >> requests CSPF computation, but it might come as part of an RSVP
> >> sub-interface to trigger signaling.  We'll have to see about
> >> use-cases.
> >>
> >> I don't see a strong motivation to duplicate existing work.
> >>
> >> Alia
> >>
> >> On Thu, Aug 16, 2012 at 2:46 PM, Shah, Himanshu <hshah@ciena.com>
> wrote:
> >> > I was wondering if PCE and IRS could have overlapping functionality.
> >> >
> >> > Meaning, can an IRS interface user at both ends (node and controller) be a
> >> non-PCE entity and perform
> >> > the same service as what PCE does?
> >> >
> >> > It seems like you are saying that could work co-operatively...
> >> >
> >> > Thanks,
> >> > himanshu
> >>
> >> ==snip===
> >> _______________________________________________
> >> irs-discuss mailing list
> >> irs-discuss@ietf.org
> >> https://www.ietf.org/mailman/listinfo/irs-discuss