draft-ietf-idr-flowspec-redirect-rt-bis-03.txt   draft-ietf-idr-flowspec-redirect-rt-bis-04.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) November 24, 2014 Updates: 5575 (if approved) April 11, 2015
Intended status: Standards Track Intended status: Standards Track
Expires: May 28, 2015 Expires: October 13, 2015
Clarification of the Flowspec Redirect Extended Community Clarification of the Flowspec Redirect Extended Community
draft-ietf-idr-flowspec-redirect-rt-bis-03 draft-ietf-idr-flowspec-redirect-rt-bis-04
Abstract Abstract
This document clarifies the formatting of the the BGP Flowspec This document updates RFC 5575 (Dissemination of Flow Specification
Redirect Extended Community, originally documented in RFC 5575 Rules) to clarify the formatting of the the BGP Flowspec Redirect
(Dissemination of Flow Specification Rules). Extended Community.
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 May 28, 2015. This Internet-Draft will expire on October 13, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 2.1. Update to BGP Generic Transitive Experimental Use
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 Extended Community Sub-Types . . . . . . . . . . . . . . 4
5. Normative References . . . . . . . . . . . . . . . . . . . . 5 2.2. Generic Transitive Experimental Extended Community Part 2
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Generic Transitive Experimental Extended Community Part 3
Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 6
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
5. Normative References . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Dissemination of Flow Specification Rules [RFC5575], commonly known Dissemination of Flow Specification Rules [RFC5575], commonly known
as BGP Flowspec, provided for a BGP Extended Community [RFC4360] that as BGP Flowspec, provided for a BGP Extended Community [RFC4360] that
served to redirect traffic to a VRF routing instance that matched the served to redirect traffic to a VRF routing instance that matched the
flow specification NLRI. In that RFC, the Redirect Extended flow specification NLRI. In that RFC, the Redirect Extended
Community was documented as follows: Community was documented as follows:
: +--------+--------------------+--------------------------+ : +--------+--------------------+--------------------------+
skipping to change at page 3, line 21 skipping to change at page 4, line 5
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 [RFC5575]. corresponding VRF instance subject to the rules defined in [RFC5575].
However, because the route target format in the redirect extended However, because the route target format in the redirect 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, which 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:
+--------+--------------------+-------------------------------------+ +--------+--------------------+-------------------------------------+
| type | extended community | encoding | | type | extended community | encoding |
+--------+--------------------+-------------------------------------+ +--------+--------------------+-------------------------------------+
| 0x8008 | redirect AS-2byte | 2-octet AS, 4-octet Value | | 0x8008 | redirect AS-2byte | 2-octet AS, 4-octet Value |
| 0x8108 | redirect IPv4 | 4-octet IPv4 Address, 2-octet Value | | 0x8108 | redirect IPv4 | 4-octet IPv4 Address, 2-octet Value |
| 0x8208 | redirect AS-4byte | 4-octet AS, 2-octet Value | | 0x8208 | redirect AS-4byte | 4-octet AS, 2-octet Value |
+--------+--------------------+-------------------------------------+ +--------+--------------------+-------------------------------------+
It should be noted that the low-order nybble of the Redirect's Type It should be noted that the low-order nibble of the Redirect's Type
field corresponds to the Route Target Extended Community format field field corresponds to the Route Target Extended Community format field
(Type). (See [RFC4360], Secs. 3.1, 3.2, and 4 plus [RFC5668], Sec. (Type). (See [RFC4360], Secs. 3.1, 3.2, and 4 plus [RFC5668], Sec.
2.) The low order octet (Sub-Type) of the Redirect Extended 2.) The low order octet (Sub-Type) of the Redirect Extended
Community remains 0x08, contrasted to 0x02 for Route Targets. Community remains 0x08, contrasted to 0x02 for Route Targets.
The IANA Registries for BGP Extended Communities [RFC7153] document The IANA Registries for BGP Extended Communities [RFC7153] document
was written to update the previously-mentioned IANA registries to was written to update the previously-mentioned IANA registries to
better document BGP Extended Community formats. The IANA better document BGP Extended Community formats. The IANA
Considerations section below further amends those registry updates in Considerations section below further amends those registry updates in
order to properly document the flowspec redirect communities. order to properly document the Flowspec redirect communities.
2. IANA Considerations 2. IANA Considerations
2.1. Update to BGP Generic Transitive Experimental Use Extended
Community Sub-Types
IANA is requested to update the "BGP Generic Transitive Experimental IANA is requested to update the "BGP Generic Transitive Experimental
Use Extended Community Sub-Types" registry as follows: Use Extended Community Sub-Types" registry as follows:
0x08 - Flow spec redirect AS-2byte format. 0x08 - Flow spec redirect AS-2byte format. [RFC5575, RFC-to-be]
(Note to RFC Editor - replace RFC-to-be with this RFC number.)
IANA is requested to update the "BGP Transitive Extended Community IANA is requested to update the "BGP Transitive Extended Community
Types" registry as follows: Types" registry as follows:
0x81 - Generic Transitive Experimental Use Extended Community 0x81 - Generic Transitive Experimental Use Extended Community
Part 2 (Sub-Types are defined in the "Generic Transitive Part 2 (Sub-Types are defined in the "Generic Transitive
Experimental Extended Community Part 2 Sub-Types" Registry) Experimental Extended Community Part 2 Sub-Types" Registry)
0x82 - Generic Transitive Experimental Use Extended Community 0x82 - Generic Transitive Experimental Use Extended Community
Part 3 (Sub-Types are defined in the "Generic Transitive Part 3 (Sub-Types are defined in the "Generic Transitive
Experimental Extended Community Part 3 Sub-Types" Registry) Experimental Extended Community Part 3 Sub-Types" Registry)
2.2. Generic Transitive Experimental Extended Community Part 2 Sub-
Types
IANA is requested to create the "Generic Transitive Experimental Use IANA is requested to create the "Generic Transitive Experimental Use
Extended Community Part 2 Sub-Types" registry. It should be seeded Extended Community Part 2 Sub-Types" registry. This registry should
with the following Sub-Type: be created under the BGP Extended Communities registry. It will
contain the following note:
0x08 - Flow spec redirect IPv4 format. This registry contains values of the second octet (the "Sub-Type"
field) of an extended community when the value of the first octet
(the "Type" field) is 0x81.
Registry Name: Generic Transitive Experimental Use Extended Community
Part 2 Sub-Types
RANGE REGISTRATION PROCEDURE REFERENCE
0x00-0xBF First Come First Served
0xC0-0xFF IETF Review
SUB-TYPE VALUE NAME
0x00-0x07 Unassigned
0x08 Flow spec redirect IPv4 format. [RFC-to-be]
0x09-0xff Unassigned
(Note to RFC Editor - replace RFC-to-be with this RFC number.)
2.3. Generic Transitive Experimental Extended Community Part 3 Sub-
Types
IANA is requested to create the "Generic Transitive Experimental Use IANA is requested to create the "Generic Transitive Experimental Use
Extended Community Part 3 Sub-Types" registry. It should be seeded Extended Community Part 3 Sub-Types" registry. This registry should
with the following Sub-Type: be created under the BGP Extended Communities registry. It will
contain the following note:
0x08 - Flow spec redirect AS-4byte format. This registry contains values of the second octet (the "Sub-Type"
field) of an extended community when the value of the first octet
(the "Type" field) is 0x82.
Registry Name: Generic Transitive Experimental Use Extended Community
Part 2 Sub-Types
RANGE REGISTRATION PROCEDURE REFERENCE
0x00-0xBF First Come First Served
0xC0-0xFF IETF Review
SUB-TYPE VALUE NAME
0x00-0x07 Unassigned
0x08 Flow spec redirect AS-4byte format. [RFC-to-be]
0x09-0xff Unassigned
(Note to RFC Editor - replace RFC-to-be with this RFC number.)
3. Security Considerations 3. Security Considerations
This document introduces no additional security considerations than This document introduces no additional security considerations than
those already covered in [RFC5575]. those already covered in [RFC5575]. It should be noted that if the
wildcard behavior were actually implemented, this ambiguity may lead
to the installation of Flowspec rules in an incorrect VRF and may
lead to traffic to be incorrectly delivered.
4. Acknowledgements 4. Acknowledgements
The contents of this document was raised as part of implementation The contents of this document was raised as part of implementation
discussions of BGP Flowspec with the following individuals: discussions of BGP Flowspec with the following individuals:
Andrew Karch (Cisco) Andrew Karch (Cisco)
Robert Raszuk Robert Raszuk
skipping to change at page 5, line 24 skipping to change at page 7, line 12
[RFC5668] Rekhter, Y., Sangli, S., and D. Tappan, "4-Octet AS [RFC5668] Rekhter, Y., Sangli, S., and D. Tappan, "4-Octet AS
Specific BGP Extended Community", RFC 5668, October 2009. Specific BGP Extended Community", RFC 5668, October 2009.
[RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP [RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP
Extended Communities", RFC 7153, March 2014. Extended Communities", RFC 7153, March 2014.
Author's Address Author's Address
Jeffrey Haas (editor) Jeffrey Haas (editor)
Juniper Networks Juniper Networks
1194 N. Mathida Ave.
Sunnyvale, CA 94089
US
Email: jhaas@juniper.net Email: jhaas@juniper.net
 End of changes. 20 change blocks. 
34 lines changed or deleted 86 lines changed or added

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