draft-ietf-idr-flowspec-redirect-rt-bis-01.txt   draft-ietf-idr-flowspec-redirect-rt-bis-02.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 20, 2014 Updates: 5575 (if approved) October 24, 2014
Intended status: Standards Track Intended status: Standards Track
Expires: April 23, 2015 Expires: April 27, 2015
Clarification of the Flowspec Redirect Extended Community Clarification of the Flowspec Redirect Extended Community
draft-ietf-idr-flowspec-redirect-rt-bis-01 draft-ietf-idr-flowspec-redirect-rt-bis-02
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 23, 2015. This Internet-Draft will expire on April 27, 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 40 skipping to change at page 3, line 40
+--------+--------------------+-------------------------------------+ +--------+--------------------+-------------------------------------+
| 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 4 plus [RFC5668], Sec.
low order octet (Sub-Type) of the Redirect Extended Community remains 2.) The low order octet (Sub-Type) of the Redirect Extended
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
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 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)
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. 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 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. 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
 End of changes. 9 change blocks. 
15 lines changed or deleted 15 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/