draft-ietf-idr-flowspec-redirect-rt-bis-04.txt   draft-ietf-idr-flowspec-redirect-rt-bis-05.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 11, 2015 Updates: 5575 (if approved) July 27, 2015
Intended status: Standards Track Intended status: Standards Track
Expires: October 13, 2015 Expires: January 28, 2016
Clarification of the Flowspec Redirect Extended Community Clarification of the Flowspec Redirect Extended Community
draft-ietf-idr-flowspec-redirect-rt-bis-04 draft-ietf-idr-flowspec-redirect-rt-bis-05
Abstract Abstract
This document updates RFC 5575 (Dissemination of Flow Specification This document updates RFC 5575 (Dissemination of Flow Specification
Rules) to clarify the formatting of the the BGP Flowspec Redirect Rules) to clarify the formatting of the the BGP Flowspec Redirect
Extended Community. 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
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 October 13, 2015. This Internet-Draft will expire on January 28, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
2.1. Update to BGP Generic Transitive Experimental Use 2.1. BGP Transitive Extended Community Types . . . . . . . . . 4
Extended Community Sub-Types . . . . . . . . . . . . . . 4 2.2. Update to BGP Generic Transitive Experimental Use
2.2. Generic Transitive Experimental Extended Community Part 2 Extended Community Sub-Types . . . . . . . . . . . . . . 5
2.3. Generic Transitive Experimental Extended Community Part 2
Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 5 Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Generic Transitive Experimental Extended Community Part 3 2.4. Generic Transitive Experimental Extended Community Part 3
Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 5 Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 6 3. Security Considerations . . . . . . . . . . . . . . . . . . . 6
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
5. Normative References . . . . . . . . . . . . . . . . . . . . 6 5. Normative References . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 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
skipping to change at page 4, line 36 skipping to change at page 4, line 36
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 2.1. BGP Transitive Extended Community Types
IANA is requested to update the "BGP Transitive Extended Community
Types" registry as follows:
0x81 - Generic Transitive Experimental Use Extended Community
Part 2 (Sub-Types are defined in the "Generic Transitive
Experimental Extended Community Part 2 Sub-Types" Registry)
0x82 - Generic Transitive Experimental Use Extended Community
Part 3 (Sub-Types are defined in the "Generic Transitive
Experimental Extended Community Part 3 Sub-Types" Registry)
2.2. Update to BGP Generic Transitive Experimental Use Extended
Community Sub-Types 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. [RFC5575, RFC-to-be] 0x08 - Flow spec redirect AS-2byte format. [RFC5575, RFC-to-be]
(Note to RFC Editor - replace RFC-to-be with this RFC number.) (Note to RFC Editor - replace RFC-to-be with this RFC number.)
IANA is requested to update the "BGP Transitive Extended Community 2.3. Generic Transitive Experimental Extended Community Part 2 Sub-
Types" registry as follows:
0x81 - Generic Transitive Experimental Use Extended Community
Part 2 (Sub-Types are defined in the "Generic Transitive
Experimental Extended Community Part 2 Sub-Types" Registry)
0x82 - Generic Transitive Experimental Use Extended Community
Part 3 (Sub-Types are defined in the "Generic Transitive
Experimental Extended Community Part 3 Sub-Types" Registry)
2.2. Generic Transitive Experimental Extended Community Part 2 Sub-
Types 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. This registry should Extended Community Part 2 Sub-Types" registry. This registry should
be created under the BGP Extended Communities registry. It will be created under the BGP Extended Communities registry. It will
contain the following note: contain the following note:
This registry contains values of the second octet (the "Sub-Type" This registry contains values of the second octet (the "Sub-Type"
field) of an extended community when the value of the first octet field) of an extended community when the value of the first octet
(the "Type" field) is 0x81. (the "Type" field) is 0x81.
Registry Name: Generic Transitive Experimental Use Extended Community Registry Name: Generic Transitive Experimental Use Extended Community
Part 2 Sub-Types Part 2 Sub-Types
RANGE REGISTRATION PROCEDURE REFERENCE RANGE REGISTRATION PROCEDURE REFERENCE
0x00-0xBF First Come First Served 0x00-0xBF First Come First Served
0xC0-0xFF IETF Review 0xC0-0xFF IETF Review
SUB-TYPE VALUE NAME SUB-TYPE VALUE NAME
0x00-0x07 Unassigned 0x00-0x07 Unassigned
0x08 Flow spec redirect IPv4 format. [RFC-to-be] 0x08 Flow spec redirect IPv4 format. [RFC-to-be]
0x09-0xff Unassigned 0x09-0xff Unassigned
(Note to RFC Editor - replace RFC-to-be with this RFC number.) (Note to RFC Editor - replace RFC-to-be with this RFC number.)
2.3. Generic Transitive Experimental Extended Community Part 3 Sub- 2.4. Generic Transitive Experimental Extended Community Part 3 Sub-
Types 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. This registry should Extended Community Part 3 Sub-Types" registry. This registry should
be created under the BGP Extended Communities registry. It will be created under the BGP Extended Communities registry. It will
contain the following note: contain the following note:
This registry contains values of the second octet (the "Sub-Type" This registry contains values of the second octet (the "Sub-Type"
field) of an extended community when the value of the first octet field) of an extended community when the value of the first octet
(the "Type" field) is 0x82. (the "Type" field) is 0x82.
 End of changes. 13 change blocks. 
29 lines changed or deleted 32 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/