1 / 4

RFC 5575 Update: Redirect Extended Community for VRF Traffic Redirection

This draft proposes an update to RFC 5575 regarding the Redirect Extended Community, essential for routing traffic to specified VRF instances based on route targets. The update clarifies that the Type field for the Redirect Extended Community uses the same format specifier as the Route Target extended community, enabling proper interpretation and implementation. The draft addresses existing confusion among implementers by providing precise encoding details and requesting IANA to update its registry for appropriate allocations to ensure smooth deployment and functionality of the feature.

chione
Télécharger la présentation

RFC 5575 Update: Redirect Extended Community for VRF Traffic Redirection

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-haas-idr-flowspec-redirect-rt-bis Jeffrey Haas, Ed. jhaas@juniper.net

  2. RFC 5575 Redirect Extended Community “Redirect: The redirect extended community allows the traffic to be redirected to a VRF routing instance that lists the specified route-target in its import policy. If several local instances match this criteria, the choice between them is a local matter (for example, the instance with the lowest Route Distinguisher value can be elected). This extended community uses the same encoding as the Route Target extended community [RFC4360].”

  3. The Issue • A Route Target is not only the 6 bytes of Value field but uses the Type-high octet as a “format specifier”. • The Flowspec RFC only shows a single type/sub-type allocated: 0x8008 • This has lead several implementers to the conclusion that you simply try out all RT types using the Value field. • This is not how the feature is deployed.

  4. The fix • A small draft updating RFC 5575 noting that the type field for the Redirect Extended Community is used the same as the Route Target extended Community, just ORed with 0x80. • IANA is requested to update its registry to make the appropriate allocations.

More Related