Clarification of the Flowspec Redirect Extended Community
draft-ietf-idr-flowspec-redirect-rt-bis-03
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (idr WG)
|
|
Author |
|
Jeffrey Haas
|
|
Last updated |
|
2015-04-09
(latest revision 2014-11-24)
|
|
Replaces |
|
draft-haas-idr-flowspec-redirect-rt-bis
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Mach Chen
|
|
Shepherd write-up |
|
Show
(last changed 2015-02-02)
|
IESG |
IESG state |
|
Waiting for Writeup
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alvaro Retana
|
|
Send notices to |
|
idr@ietf.org, idr-chairs@ietf.org, mach@huawei.com
|
IANA |
IANA review state |
|
IANA - Not OK
|
Internet Engineering Task Force J. Haas, Ed.
Internet-Draft Juniper Networks
Updates: 5575 (if approved) November 24, 2014
Intended status: Standards Track
Expires: May 28, 2015
Clarification of the Flowspec Redirect Extended Community
draft-ietf-idr-flowspec-redirect-rt-bis-03
Abstract
This document clarifies the formatting of the the BGP Flowspec
Redirect Extended Community, originally documented in RFC 5575
(Dissemination of Flow Specification Rules).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 28, 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Haas Expires May 28, 2015 [Page 1]
Internet-Draft draft-ietf-idr-flowspec-redirect-rt-bis November 2014
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
5. Normative References . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
Dissemination of Flow Specification Rules [RFC5575], commonly known
as BGP Flowspec, provided for a BGP Extended Community [RFC4360] that
served to redirect traffic to a VRF routing instance that matched the
flow specification NLRI. In that RFC, the Redirect Extended
Community was documented as follows:
: +--------+--------------------+--------------------------+
: | type | extended community | encoding |
: +--------+--------------------+--------------------------+
: | 0x8008 | redirect | 6-byte Route Target |
: +--------+--------------------+--------------------------+
:
: [...]
:
: 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].
: [...]
:
: 11. IANA Considerations
: [...]
:
: The following traffic filtering flow specification rules have been
: allocated by IANA from the "BGP Extended Communities Type -
: Experimental Use" registry as follows:
: [...]
:
: 0x8008 - Flow spec redirect
The IANA registry of BGP Extended Communities clearly identifies
communities of specific formats. For example, "Two-octet AS Specific
Extended Community" [RFC4360], "Four-octet AS Specific Extended
Community" [RFC5668] and "IPv4 Address Specific Extended Community"
Haas Expires May 28, 2015 [Page 2]
Internet-Draft draft-ietf-idr-flowspec-redirect-rt-bis November 2014
[RFC4360]. Route Targets [RFC4360] identify this format in the high-
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
Target Extended Community is intended to be interpreted in the
context of its format.
Since the Redirect Extended Community only registered a single code-
point in the IANA BGP Extended Community registry, a common
interpretation of the redirect extended community's "6-byte route
Show full document text