Re: [Idr] Regarding draft-vandevelde-idr-flowspec-path-redirect//??: IDR interim (10/26/2015) 10:00am - 11:30am ET update
Lucy yong <lucy.yong@huawei.com> Mon, 26 October 2015 18:49 UTC
Return-Path: <lucy.yong@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 080CE1B50A4 for <idr@ietfa.amsl.com>; Mon, 26 Oct 2015 11:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 66NV8yW4YitZ for <idr@ietfa.amsl.com>; Mon, 26 Oct 2015 11:49:13 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 273341B50A6 for <idr@ietf.org>; Mon, 26 Oct 2015 11:49:12 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CDB14345; Mon, 26 Oct 2015 18:49:09 +0000 (GMT)
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 26 Oct 2015 18:49:08 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml704-chm ([10.193.5.141]) with mapi id 14.03.0235.001; Mon, 26 Oct 2015 11:48:57 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "VAN DE VELDE, Gunter (Gunter)" <gunter.van_de_velde@alcatel-lucent.com>, Lizhenbin <lizhenbin@huawei.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Regarding draft-vandevelde-idr-flowspec-path-redirect//??: IDR interim (10/26/2015) 10:00am - 11:30am ET update
Thread-Index: AQHREAlwO8s6ONBcQEeQ1uTwpaWSm55+a1CA//+quBA=
Date: Mon, 26 Oct 2015 18:48:55 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57200661@dfweml701-chm>
References: <009b01d10f2e$5cc28820$16479860$@ndzh.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D8CA5C638@nkgeml506-mbx.china.huawei.com> <4D6BC339-51BE-4F90-8858-9B81859858F0@alcatel-lucent.com>
In-Reply-To: <4D6BC339-51BE-4F90-8858-9B81859858F0@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.156.71]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57200661dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/voUQcmvIbBHPKHeIKrS4GvS0Q6c>
Cc: "jgs@bgp.nu" <jgs@bgp.nu>
Subject: Re: [Idr] Regarding draft-vandevelde-idr-flowspec-path-redirect//??: IDR interim (10/26/2015) 10:00am - 11:30am ET update
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2015 18:49:17 -0000
Hi Gunter, Sorry to chip in here. Please see inline below. From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of VAN DE VELDE, Gunter (Gunter) Sent: Monday, October 26, 2015 11:26 AM To: Lizhenbin; Susan Hares; idr@ietf.org Cc: jgs@bgp.nu Subject: Re: [Idr] Regarding draft-vandevelde-idr-flowspec-path-redirect//??: IDR interim (10/26/2015) 10:00am - 11:30am ET update Hi Robin, Thanks for your note. A tunnel is not always going over shortest path. Some tunnels are TE tunnels and are deliberately not going over a shortest path. This is something that draft-rosen-idr-tunnel-encaps-00 will not help to signal because the tunnel-encap attribute indicates tunnel parameters used by the tail-end. [Lucy] agree. The tunnel-encaps draft is used to signal an IP tunnel, not a tunnel that is constructed by other protocol such as RSVP-TE. For a RSVP-TE tunnel, signaling the tunnel parameters used by the tail-end is not useful. It needs to signal the tunnel parameters used by the head-end, which may be hard for the tunnel tail-end to do in some use case. However, in SDN controller case where BGP is used between SDN controller and router, SDN controller has the tunnel head-end parameters and can use BGP to signal the tunnel head-end parameter info to the routers. This is what draft-li-idr-mpls-path-programmer targets the use case. If a redirect tunnel represents a particular redirect/steering service (better delay, less packet loss, non-SRLG, more BW, etc…) then it does become rather complex for BGP as signalling technology because a tunnel relationship is a unique between 'a headend' and ‘a tailed' device. It seems better to leave tunnel-setup to dedicated tunnel-setup mechanisms like PCEP, SR, etc…. [Lucy] Yes. Draft-hao-idr-flowspect-redirect-tunnel specifies two types of tunnels, one is the IP tunnel that can be signaled by the tunnel encap. attribute specified in the tunnel-encap draft; another is the non-IP tunnel that can also be signaled by the attribute specified in the mpls-path-programmer drafts. The draft redirect-to-PATH_ID is providing the means to signal a flow-based redirect/steering service, and have each recipient router identify using local recursion for the PATH_IDs the corresponding tunnels/redirect-info. This allows for tunnel setup complexity to be taken away from BGP, while at the same time BGP is doing what it is very good at doing: "It signals a policy” in reliable fashion. [Lucy] You draft introduces the PATH ID that is global and represents a tunnel that is established by other protocol/manual. As a result, Central controller, BGP, and other protocol/routers need to be aware of the PATH ID and use it to reference a tunnel. Since the proposal relates to many components, it is necessary to explore more such service framework as a whole for an optimal solution. Regards, Lucy Kind Regards, G/ From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Lizhenbin <lizhenbin@huawei.com<mailto:lizhenbin@huawei.com>> Date: Monday 26 October 2015 at 16:51 To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>, "idr@ietf.org<mailto:idr@ietf.org>" <idr@ietf.org<mailto:idr@ietf.org>> Cc: "jgs@bgp.nu<mailto:jgs@bgp.nu>" <jgs@bgp.nu<mailto:jgs@bgp.nu>> Subject: [Idr] Regarding draft-vandevelde-idr-flowspec-path-redirect//答复: IDR interim (10/26/2015) 10:00am - 11:30am ET update Hi Gunter, Regarding your presentation, I have following comments: Do you mean draft-hao-idr-flowspec-redirect-tunnel is to signal tunnel setup info? draft-hao-idr-flowspec-redirect-tunnel is to steer traffic to the tunnel instead of signal tunnel setup. I am not sure if the reuse of draft-rosen-idr-tunnel-encaps-00 in the draft make you confused? We just hope to just reuses the attributes of to specify the tunnel type to help steering the traffic to tunnel. If this is not a good way, maybe we can define new attributes. Best Regards, Robin 发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Susan Hares 发送时间: 2015年10月25日 22:07 收件人: idr@ietf.org<mailto:idr@ietf.org> 抄送: jgs@bgp.nu<mailto:jgs@bgp.nu> 主题: [Idr] IDR interim (10/26/2015) 10:00am - 11:30am ET update IDR WG members: Below is an updated agenda for the IDR interim on 10/26/2015. Sue ------------ IDR interim October 26, 2015 10:00 - 11:30am 1. Chair's slides [10:00-10:05] 1. draft-litkowski-idr-flowspec-interfaceset-01.txt speaker: Stephane Litowski Time: 10:05-10:15 https://datatracker.ietf.org/doc/draft-litkowski-idr-flowspec-interfaceset/ 2. draft-hao-idr-flowspec-redirect-tunnel-00 Speaker: Weiguo Hao Time: 10:15 - 10:25 http://datatracker.ietf.org/doc/draft-hao-idr-flowspec-redirect-tunnel/ 3. draft-vandevelde-idr-flowspec-path-redirect Speaker: Gunter Van De Velde Time: 10:25- 10:35 http://datatracker.ietf.org/doc/draft-vandevelde-idr-flowspec-path-redirect/ 4. Draft Name: draft-hao-idr-flowspec-nvo3-02 Speaker: Weiguo Hao Duration: 10:35-10:40 http://datatracker.ietf.org/doc/draft-hao-idr-flowspec-nvo3/ 5. draft-liang-idr-bgp-flowspec-label-01.txt. Speaker: Duration: 10:40-10:45 http://datatracker.ietf.org/doc/draft-liang-idr-bgp-flowspec-label/ 6. draft-liang-idr-bgp-flowspec-time presenter: Jianjie You time: 10:45-10:55 http://datatracker.ietf.org/doc/draft-liang-idr-bgp-flowspec-time/ 7. Draft Name: draft-li-idr-mpls-path-programming-02 Speaker: Zhenbin Li Duration: 10:55-11:05 http://datatracker.ietf.org/doc/draft-li-idr-mpls-path-programming/ 7. Draft Name: draft-li-idr-flowspec-rpd-01 Speaker: Shunwan Zhuang Duration: 11:05 - 11:15 http://datatracker.ietf.org/doc/draft-li-idr-flowspec-rpd/ 8. Discussion of Flowspec drafts 11:15 - 11:30am Meeting Web-ex information Monday, October 26, 2015 10:00 am | Eastern Daylight Time (New York, GMT-04:00) | 2 hrs webex infor: https://ietf.webex.com/ietf/j.php?MTID=mae6cf241d3adf214033e599c3ff3143f Meeting number: 644 964 970 Meeting password: flow.in.nets Join by phone 1-877-668-4493 Call-in toll free number (US/Canada) 1-650-479-3208 Call-in toll number (US/Canada) Access code: 644 964 970
- [Idr] IDR interim (10/26/2015) 10:00am - 11:30am … Susan Hares
- Re: [Idr] IDR interim (10/26/2015) 10:00am - 11:3… Jeffrey Haas
- Re: [Idr] IDR interim (10/26/2015) 10:00am - 11:3… Acee Lindem (acee)
- Re: [Idr] IDR interim (10/26/2015) 10:00am - 11:3… Susan Hares
- Re: [Idr] IDR interim (10/26/2015) 10:00am - 11:3… Jeffrey Haas
- [Idr] Regarding draft-vandevelde-idr-flowspec-pat… Lizhenbin
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… VAN DE VELDE, Gunter (Gunter)
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Robert Raszuk
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… VAN DE VELDE, Gunter (Gunter)
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Robert Raszuk
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Gunter Van De Velde
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Lucy yong
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Robert Raszuk
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Gunter Van De Velde
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Robert Raszuk
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Gunter Van De Velde
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Dongjie (Jimmy)
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… VAN DE VELDE, Gunter (Gunter)
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Susan Hares
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Gunter Van De Velde
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Susan Hares
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Lucy yong
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Gunter Van De Velde
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Susan Hares
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Gunter Van De Velde
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Robert Raszuk
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Gunter Van De Velde
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Robert Raszuk
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Gunter Van De Velde
- Re: [Idr] Regarding draft-vandevelde-idr-flowspec… Lucy yong