draft-ietf-idr-flowspec-redirect-rt-bis-00.txt   draft-ietf-idr-flowspec-redirect-rt-bis-01.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) April 1, 2014 Updates: 5575 (if approved) October 20, 2014
Intended status: Standards Track Intended status: Standards Track
Expires: October 3, 2014 Expires: April 23, 2015
Clarification of the Flowspec Redirect Extended Community Clarification of the Flowspec Redirect Extended Community
draft-ietf-idr-flowspec-redirect-rt-bis-00 draft-ietf-idr-flowspec-redirect-rt-bis-01
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).
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 October 3, 2014. This Internet-Draft will expire on April 23, 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
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
5. Normative References . . . . . . . . . . . . . . . . . . . . . 5 5. Normative References . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
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 44 skipping to change at page 3, line 4
: allocated by IANA from the "BGP Extended Communities Type - : allocated by IANA from the "BGP Extended Communities Type -
: Experimental Use" registry as follows: : Experimental Use" registry as follows:
: [...] : [...]
: :
: 0x8008 - Flow spec redirect : 0x8008 - Flow spec redirect
The IANA registry of BGP Extended Communities clearly identifies The IANA registry of BGP Extended Communities clearly identifies
communities of specific formats. For example, "Two-octet AS Specific communities of specific formats. For example, "Two-octet AS Specific
Extended Community" [RFC4360], "Four-octet AS Specific Extended Extended Community" [RFC4360], "Four-octet AS Specific Extended
Community" [RFC5668] and "IPv4 Address Specific Extended Community" Community" [RFC5668] and "IPv4 Address Specific Extended Community"
[RFC4360]. Route Targets [RFC4360] identify this format in the high- [RFC4360]. Route Targets [RFC4360] identify this format in the high-
order (Type) octet of the Extended Community and set the value of the order (Type) octet of the Extended Community and set the value of the
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 for any matching Route Target sharing the target" has been to look, at a receiving router, for a route target
same Value portion of its Extended Community. Thus, multiple Route value that matches the route target value in the received redirect
Targets provisioned in a router's VRFs might match even though the extended community, and import the advertised route to the
format was different. corresponding VRF instance subject to the rules defined in RFC 5575
[RFC 5575]. However, because the route target format in the redirect
extended community is not clearly defined, the wrong match may occur.
This "Value wildcard" behavior does not matched deployed This "value wildcard" matching behavior, that does not take into
implementations of BGP Flowspec. Deployed implementations of BGP account the format of the route target defined for a local VRF and
Flowspec use the following formatting for the Redirect Extended may result in the wrong matching decision, does not match deployed
Community: implementations of BGP flowspec. Deployed implementations of BGP
flowspec solve this problem by defining different redirect extended
communities that are specific to the format of the route target
value. This document defines the following redirect extended
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 nybble 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 [RFC5668], Sec. 2.) The (Type). (See [RFC4360], Secs. 3.1, 3.2 and [RFC5668], Sec. 2.) The
low order octet (Sub-Type) of the Redirect Extended Community remains low order octet (Sub-Type) of the Redirect Extended Community remains
0x08, contrasted to 0x02 for Route Targets. 0x08, contrasted to 0x02 for Route Targets.
The IANA Registries for BGP Extended Communities The IANA Registries for BGP Extended Communities [RFC7153] document
[I-D.ietf-idr-extcomm-iana] document was written to update the was written to update the previously-mentioned IANA registries to
previously-mentioned IANA registries to better document BGP Extended better document BGP Extended Community formats. The IANA
Community formats. The IANA Considerations section below further Considerations section below further amends those registry updates in
amends those registry updates in order to properly document the order to properly document the flowspec redirect communities.
flowspec redirect communities.
2. IANA Considerations 2. IANA Considerations
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.
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 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 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)
IANA is requested to create the GENERIC TRANSITIVE EXPERIMENTAL 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. It should be seeded
with the following Sub-Type: with the following Sub-Type:
0x08 - Flow spec redirect IPv4 format. 0x08 - Flow spec redirect IPv4 format.
IANA is requested to create the GENERIC TRANSITIVE EXPERIMENTAL 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. It should be seeded
with the following Sub-Type: with the following Sub-Type:
0x08 - Flow spec redirect AS-4byte format. 0x08 - Flow spec redirect AS-4byte format.
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].
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 (NTT I3) Robert Raszuk
Adam Simpson (Alcatel-Lucent) Adam Simpson (Alcatel-Lucent)
Matthieu Texier (Arbor Networks) Matthieu Texier (Arbor Networks)
Kaliraj Vairavakkalai (Juniper) Kaliraj Vairavakkalai (Juniper)
5. Normative References 5. Normative References
[I-D.ietf-idr-extcomm-iana]
Rosen, E. and Y. Rekhter, "IANA Registries for BGP
Extended Communities", draft-ietf-idr-extcomm-iana-02
(work in progress), December 2013.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, February 2006. Communities Attribute", RFC 4360, February 2006.
[RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., [RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J.,
and D. McPherson, "Dissemination of Flow Specification and D. McPherson, "Dissemination of Flow Specification
Rules", RFC 5575, August 2009. Rules", RFC 5575, August 2009.
[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
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. 1194 N. Mathida Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
US US
Email: jhaas@juniper.net Email: jhaas@juniper.net
 End of changes. 18 change blocks. 
37 lines changed or deleted 42 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/