Re: [Idr] Regarding draft-vandevelde-idr-flowspec-path-redirect//答复: IDR interim (10/26/2015) 10:00am - 11:30am ET update

"VAN DE VELDE, Gunter (Gunter)" <gunter.van_de_velde@alcatel-lucent.com> Mon, 26 October 2015 16:26 UTC

Return-Path: <gunter.van_de_velde@alcatel-lucent.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 8CC0F1B4E5D for <idr@ietfa.amsl.com>; Mon, 26 Oct 2015 09:26:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.61
X-Spam-Level:
X-Spam-Status: No, score=-6.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, 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 W7ctJUFdEtek for <idr@ietfa.amsl.com>; Mon, 26 Oct 2015 09:26:14 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 E3B711B4E5B for <idr@ietf.org>; Mon, 26 Oct 2015 09:26:13 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id DB84E328E1194; Mon, 26 Oct 2015 16:26:08 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t9QGQ9uO004257 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 Oct 2015 17:26:11 +0100
Received: from FR711WXCHMBA06.zeu.alcatel-lucent.com ([169.254.2.12]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Mon, 26 Oct 2015 17:26:10 +0100
From: "VAN DE VELDE, Gunter (Gunter)" <gunter.van_de_velde@alcatel-lucent.com>
To: 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: AdEPLjwmiBqrPowgTjmyznhupF0S+gA1qfZwAAGIU4A=
Date: Mon, 26 Oct 2015 16:26:09 +0000
Message-ID: <4D6BC339-51BE-4F90-8858-9B81859858F0@alcatel-lucent.com>
References: <009b01d10f2e$5cc28820$16479860$@ndzh.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D8CA5C638@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8CA5C638@nkgeml506-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: multipart/alternative; boundary="_000_4D6BC33951BE4F9088589B81859858F0alcatellucentcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/bHtmJW6tdIzSc08lq4HjhYq-Lmo>
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 16:26:17 -0000

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] 代表 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