Subject: Re: [Idr] FW: New Version Notification for draft-simpson-idr-flowspec-redirect-01.txt

From: "Shyam Sethuram (shsethur)" <[email-masked]>
Date: Thu, 16 Aug 2012 06:51:40 +0000

Adam,
One clarification - I guess, a nit:

Towards the end of Sec 3, you mention:
  "This means that a flow-spec route with a
   destination prefix subcomponent SHOULD NOT be accepted from an EBGP
   peer unless that peer also advertised the best path for the matching
   unicast route."

It should instead say something to the effect of "... such a flow-spec
route should not be selected as best-path / installed as a filtering rule".
We can certainly accept those flow-spec routes from peer ?

thanks--shyam

>-----Original Message-----
>From: [email-masked] [mailto:[email-masked]] On Behalf Of Simpson, Adam
>(Adam)
>Sent: Thursday, July 26, 2012 9:20 AM
>To: [email-masked]
>Subject: [Idr] FW: New Version Notification for draft-simpson-idr-flowspec-redirect-01.txt
>
>This individual submission was posted last week and will be presented at the IDR meeting
>next week. Any feedback you have before or after the meeting would be welcome.
>
>Thanks,
>Adam
>
>
>-----Original Message-----
>From: [email-masked] [mailto:[email-masked]]
>Sent: Monday, July 16, 2012 10:33 AM
>To: Simpson, Adam (Adam)
>Cc: [email-masked]; [email-masked]; [email-masked]; Henderickx, Wim (Wim)
>Subject: New Version Notification for draft-simpson-idr-flowspec-redirect-01.txt
>
>
>A new version of I-D, draft-simpson-idr-flowspec-redirect-01.txt
>has been successfully submitted by Adam Simpson and posted to the
>IETF repository.
>
>Filename:	 draft-simpson-idr-flowspec-redirect
>Revision:	 01
>Title:		 BGP Flow-Spec Extended Community for Traffic Redirect to IP Next Hop
>Creation date:	 2012-07-16
>WG ID:		 Individual Submission
>Number of pages: 7
>URL:             http://www.ietf.org/internet-drafts/draft-simpson-idr-flowspec-redirect-01.txt
>Status:          http://datatracker.ietf.org/doc/draft-simpson-idr-flowspec-redirect
>Htmlized:        http://tools.ietf.org/html/draft-simpson-idr-flowspec-redirect-01
>Diff:            http://tools.ietf.org/rfcdiff?url2=draft-simpson-idr-flowspec-redirect-01
>
>Abstract:
>   Flow-spec is an extension to BGP that allows for the dissemination of
>   traffic flow specification rules. This has many possible applications
>   but the primary one for many network operators is the distribution of
>   traffic filtering actions for DDoS mitigation. The flow-spec standard
>   [RFC 5575] defines a redirect-to-VRF action for policy-based
>   forwarding but this mechanism can be difficult to use, particularly
>   in networks without L3 VPNs.
>
>   This draft proposes a new redirect-to-IP flow-spec action that
>   provides a simpler method of policy-based forwarding. This action is
>   indicated by the presence of a new BGP extended community in the
>   flow-spec route. Many routers already support a redirect-to-IP filter
>   action and, in this case, the only new functionality implied by this
>   draft is the ability to signal the action using flow-spec.
>
>
>
>
>The IETF Secretariat
>_______________________________________________
>Idr mailing list
>[email-masked]
>https://www.ietf.org/mailman/listinfo/idr