draft-ietf-idr-flowspec-redirect-rt-bis-02.txt   draft-ietf-idr-flowspec-redirect-rt-bis-03.txt 
Internet Engineering Task Force J. Haas, Ed. Internet Engineering Task Force J. Haas, Ed.
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Updates: 5575 (if approved) October 24, 2014 Updates: 5575 (if approved) November 24, 2014
Intended status: Standards Track Intended status: Standards Track
Expires: April 27, 2015 Expires: May 28, 2015
Clarification of the Flowspec Redirect Extended Community Clarification of the Flowspec Redirect Extended Community
draft-ietf-idr-flowspec-redirect-rt-bis-02 draft-ietf-idr-flowspec-redirect-rt-bis-03
Abstract Abstract
This document clarifies the formatting of the the BGP Flowspec This document clarifies the formatting of the the BGP Flowspec
Redirect Extended Community, originally documented in RFC 5575 Redirect Extended Community, originally documented in RFC 5575
(Dissemination of Flow Specification Rules). (Dissemination of Flow Specification Rules).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 27, 2015. This Internet-Draft will expire on May 28, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 17 skipping to change at page 3, line 17
low-order (Sub-Type) octet to 0x02. The Value field of the Route low-order (Sub-Type) octet to 0x02. The Value field of the Route
Target Extended Community is intended to be interpreted in the Target Extended Community is intended to be interpreted in the
context of its format. context of its format.
Since the Redirect Extended Community only registered a single code- Since the Redirect Extended Community only registered a single code-
point in the IANA BGP Extended Community registry, a common point in the IANA BGP Extended Community registry, a common
interpretation of the redirect extended community's "6-byte route interpretation of the redirect extended community's "6-byte route
target" has been to look, at a receiving router, for a route target target" has been to look, at a receiving router, for a route target
value that matches the route target value in the received redirect value that matches the route target value in the received redirect
extended community, and import the advertised route to the extended community, and import the advertised route to the
corresponding VRF instance subject to the rules defined in RFC 5575 corresponding VRF instance subject to the rules defined in [RFC5575].
[RFC 5575]. However, because the route target format in the redirect However, because the route target format in the redirect extended
extended community is not clearly defined, the wrong match may occur. community is not clearly defined, the wrong match may occur.
This "value wildcard" matching behavior, that does not take into This "value wildcard" matching behavior, that does not take into
account the format of the route target defined for a local VRF and account the format of the route target defined for a local VRF and
may result in the wrong matching decision, does not match deployed may result in the wrong matching decision, does not match deployed
implementations of BGP flowspec. Deployed implementations of BGP implementations of BGP flowspec. Deployed implementations of BGP
flowspec solve this problem by defining different redirect extended flowspec solve this problem by defining different redirect extended
communities that are specific to the format of the route target communities that are specific to the format of the route target
value. This document defines the following redirect extended value. This document defines the following redirect extended
communities: communities:
 End of changes. 5 change blocks. 
7 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/