Re: [Idr] Regarding draft-vandevelde-idr-flowspec-path-redirect//答复: IDR interim (10/26/2015) 10:00am - 11:30am ET update
Gunter Van De Velde <guntervandeveldecc@icloud.com> Wed, 28 October 2015 09:37 UTC
Return-Path: <guntervandeveldecc@icloud.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 4FE651B3759 for <idr@ietfa.amsl.com>; Wed, 28 Oct 2015 02:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 giTyWLxwO0Gv for <idr@ietfa.amsl.com>; Wed, 28 Oct 2015 02:37:53 -0700 (PDT)
Received: from st13p11im-asmtp003.me.com (st13p11im-asmtp003.me.com [17.164.40.218]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A04FD1B3758 for <idr@ietf.org>; Wed, 28 Oct 2015 02:37:53 -0700 (PDT)
Received: from [192.168.0.247] (d8D8705F8.access.telenet.be [141.135.5.248]) by st13p11im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NWX00925C323830@st13p11im-asmtp003.me.com> for idr@ietf.org; Wed, 28 Oct 2015 09:37:52 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-10-28_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=0 kscore.compositescore=1 compositescore=0.9 suspectscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 rbsscore=0 spamscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510090000 definitions=main-1510280165
Content-type: multipart/alternative; boundary="Apple-Mail=_7F64ADB9-3694-4C56-8C3C-A6612A35746C"
MIME-version: 1.0 (Mac OS X Mail 9.0 \(3094\))
From: Gunter Van De Velde <guntervandeveldecc@icloud.com>
In-reply-to: <009a01d1110f$7117ecb0$5347c610$@ndzh.com>
Date: Wed, 28 Oct 2015 10:37:49 +0100
Message-id: <03EDACDC-7C93-479C-9BB3-A11F2ECD3181@icloud.com>
References: <009b01d10f2e$5cc28820$16479860$@ndzh.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D8CA5C638@nkgeml506-mbx.china.huawei.com> <4D6BC339-51BE-4F90-8858-9B81859858F0@alcatel-lucent.com> <042101d110e5$439e2d50$cada87f0$@ndzh.com> <7BFD3160-0576-4AC7-919B-B73FA61BBB51@icloud.com> <009a01d1110f$7117ecb0$5347c610$@ndzh.com>
To: Susan Hares <shares@ndzh.com>
X-Mailer: Apple Mail (2.3094)
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/gdKd88O7bq-Ejo808hJzNGFqo-w>
Cc: idr wg <idr@ietf.org>, 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: Wed, 28 Oct 2015 09:37:57 -0000
Hi Sue, [Please indicate when you are speaking as IDR chair or when you are speaking as contributor/affiliation… i am confused] I did a search for forwarding ID in the referenced document and i do not see it? You clearly understand that draft-vandevelde-idr-flowspec-path-redirect and draft-li-idr-mpls-path-programming are orthogonal to each other, not? “draft-li-idr-mpls-path-programming " specifies how BGP uses attributes to signal a tunnel and how a tunnel is constructed through the network, while on the other end of the spectrum draft-vandevelde-idr-flowspec-path-redirect specifies flowspec based traffic steering onto a redirect path and signals no tunnel attributes at all. In draft-vandevelde-idr-flowspec-path-redirect the local PATH_ID table can be constructed by many means and is outside the scope of the document: * draft-li-idr-mpls-path-programming * manual config * netconf/yang * traditional routing * voodoo * etc... The end result: redirect-to-path and draft-li-idr-mpls-path-programming are orthogonal to each other. Kind Regards, G/ > On 28 Oct 2015, at 00:30, Susan Hares <shares@ndzh.com> wrote: > > Gunter: > > Robin’s proposal is http://datatracker.ietf.org/doc/draft-li-idr-mpls-path-programming/ <http://datatracker.ietf.org/doc/draft-li-idr-mpls-path-programming/> > > See my attached comparison from the interim. You can also download Robin’s slides from the interim. > > Sue > > From: Idr [mailto:idr-bounces@ietf.org <mailto:idr-bounces@ietf.org>] On Behalf Of Gunter Van De Velde > Sent: Tuesday, October 27, 2015 4:12 PM > To: Susan Hares > Cc: idr wg; jgs@bgp.nu <mailto: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 Sue, > > Would you know where to find Forwarding ID described in draft-hao-idr-flowspec-redirect-tunnel to make assessment? > There is no mentioning of this concept at all in the document? Alternatively, what i found is signalling of tunnel end-point (IPv4/IPv6) and > some tunnel setup information (tunnel encap attribute and a new MPP TE tunnel attribute). > > Brgds, > G/ > > > > > > >> On 27 Oct 2015, at 19:28, Susan Hares <shares@ndzh.com <mailto:shares@ndzh.com>> wrote: >> >> Gunter: >> >> Can you let me know the difference between the Path ID in your proposal and Robin’s Forwarding ID that is a generalized segment ID? >> >> Sue Hares >> >> From: VAN DE VELDE, Gunter (Gunter) [mailto:gunter.van_de_velde@alcatel-lucent.com <mailto:gunter.van_de_velde@alcatel-lucent.com>] >> Sent: Monday, October 26, 2015 12:26 PM >> To: Lizhenbin; Susan Hares; idr@ietf.org <mailto:idr@ietf.org> >> Cc: jgs@bgp.nu <mailto: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. >> >> 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…. >> >> 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. >> >> 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 <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/ <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/ <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/ <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/ <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/ <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/ <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/ <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/ <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 <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 mailing list >> Idr@ietf.org <mailto:Idr@ietf.org> >> https://www.ietf.org/mailman/listinfo/idr <https://www.ietf.org/mailman/listinfo/idr> > > <Hares-Discussion of Flowspec.pdf>
- [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