draft-ietf-idr-rfc5575bis-06.txt   draft-ietf-idr-rfc5575bis-07.txt 
IDR Working Group S. Hares IDR Working Group S. Hares
Internet-Draft Huawei Internet-Draft Huawei
Obsoletes: 5575,7674 (if approved) C. Loibl Obsoletes: 5575,7674 (if approved) C. Loibl
Intended status: Standards Track Next Layer Communications Intended status: Standards Track Next Layer Communications
Expires: April 27, 2018 R. Raszuk Expires: October 22, 2018 R. Raszuk
Bloomberg LP Bloomberg LP
D. McPherson D. McPherson
Verisign Verisign
M. Bacher M. Bacher
T-Mobile Austria T-Mobile Austria
October 24, 2017 April 20, 2018
Dissemination of Flow Specification Rules Dissemination of Flow Specification Rules
draft-ietf-idr-rfc5575bis-06 draft-ietf-idr-rfc5575bis-07
Abstract Abstract
This document updates [RFC5575] which defines a Border Gateway This document updates [RFC5575] which defines a Border Gateway
Protocol Network Layer Reachability Information (BGP NLRI) encoding Protocol Network Layer Reachability Information (BGP NLRI) encoding
format that can be used to distribute traffic Flow Specifications. format that can be used to distribute traffic Flow Specifications.
This allows the routing system to propagate information regarding This allows the routing system to propagate information regarding
more specific components of the traffic aggregate defined by an IP more specific components of the traffic aggregate defined by an IP
destination prefix. destination prefix.
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 27, 2018. This Internet-Draft will expire on October 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 5, line 49 skipping to change at page 5, line 49
as IPv6 families [I-D.ietf-idr-flow-spec-v6], as IPv6 families [I-D.ietf-idr-flow-spec-v6],
2. Definitions of Terms Used in This Memo 2. Definitions of Terms Used in This Memo
NLRI - Network Layer Reachability Information. NLRI - Network Layer Reachability Information.
RIB - Routing Information Base. RIB - Routing Information Base.
Loc-RIB - Local RIB. Loc-RIB - Local RIB.
AS - Autonomous System number. AS - Autonomous System.
VRF - Virtual Routing and Forwarding instance. VRF - Virtual Routing and Forwarding instance.
PE - Provider Edge router PE - Provider Edge router
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119] document are to be interpreted as described in [RFC2119]
3. Flow Specifications 3. Flow Specifications
skipping to change at page 7, line 29 skipping to change at page 7, line 29
+------------------------------+ +------------------------------+
| NLRI value (variable) | | NLRI value (variable) |
+------------------------------+ +------------------------------+
Figure 1: Flow-spec NLRI for IPv4 Figure 1: Flow-spec NLRI for IPv4
Implementations wishing to exchange Flow Specification rules MUST use Implementations wishing to exchange Flow Specification rules MUST use
BGP's Capability Advertisement facility to exchange the Multiprotocol BGP's Capability Advertisement facility to exchange the Multiprotocol
Extension Capability Code (Code 1) as defined in [RFC4760]. The Extension Capability Code (Code 1) as defined in [RFC4760]. The
(AFI, SAFI) pair carried in the Multiprotocol Extension Capability (AFI, SAFI) pair carried in the Multiprotocol Extension Capability
MUST be the same as the one used to identify a particular application MUST be (AFI=1, SAFI=133) for IPv4 Flow Specification, and (AFI=1,
that uses this NLRI-type. SAFI=134) for VPNv4 Flow Specification.
4.1. Length Encoding 4.1. Length Encoding
o If the NLRI length value is smaller than 240 (0xf0 hex), the o If the NLRI length value is smaller than 240 (0xf0 hex), the
length field can be encoded as a single octet. length field can be encoded as a single octet.
o Otherwise, it is encoded as an extended-length 2-octet value in o Otherwise, it is encoded as an extended-length 2-octet value in
which the most significant nibble of the first byte is all ones. which the most significant nibble of the first byte is all ones.
In figure 1 above, values less-than 240 are encoded using two hex In figure 1 above, values less-than 240 are encoded using two hex
skipping to change at page 14, line 28 skipping to change at page 14, line 28
downstream AS wishes to drop. downstream AS wishes to drop.
In order to achieve this goal, this draft specifies two application In order to achieve this goal, this draft specifies two application
specific NLRI identifiers that provide traffic filters, and a set of specific NLRI identifiers that provide traffic filters, and a set of
actions encoding in BGP Extended Communities. The two application actions encoding in BGP Extended Communities. The two application
specific NLRI identifiers are: specific NLRI identifiers are:
o IPv4 Flow Specification identifier (AFI=1, SAFI=133) along with o IPv4 Flow Specification identifier (AFI=1, SAFI=133) along with
specific semantic rules for IPv4 routes, and specific semantic rules for IPv4 routes, and
o BGP NLRI type (AFI=1, SAFI=134) value, which can be used to o VPNv4 Flow Specification identifier (AFI=1, SAFI=134) value, which
propagate traffic filtering information in a BGP/MPLS VPN can be used to propagate traffic filtering information in a BGP/
environment. MPLS VPN environment.
Distribution of the IPv4 Flow Specification is described in section Distribution of the IPv4 Flow Specification is described in section
6, and distibution of BGP/MPLS traffic Flow Specification is 6, and distibution of BGP/MPLS traffic Flow Specification is
described in section 8. The traffic filtering actions are described described in section 8. The traffic filtering actions are described
in section 7. in section 7.
5.1. Ordering of Traffic Filtering Rules 5.1. Ordering of Traffic Filtering Rules
With traffic filtering rules, more than one rule may match a With traffic filtering rules, more than one rule may match a
particular traffic flow. Thus, it is necessary to define the order particular traffic flow. Thus, it is necessary to define the order
skipping to change at page 27, line 5 skipping to change at page 27, line 5
this document consist of two parts: this document consist of two parts:
Type (BGP Transitive Extended Community Type) Type (BGP Transitive Extended Community Type)
Sub-Type Sub-Type
For the type-part, IANA maintains a registry entitled "BGP Transitive For the type-part, IANA maintains a registry entitled "BGP Transitive
Extended Community Types". For the purpose of this work (Section 7), Extended Community Types". For the purpose of this work (Section 7),
IANA updated the registry to contain the values listed below: IANA updated the registry to contain the values listed below:
+----------+--------------------------------------------+-----------+ +-------+-----------------------------------------------+-----------+
| Sub-Type | Name | Reference | | Type | Name | Reference |
| Value | | | | Value | | |
+----------+--------------------------------------------+-----------+ +-------+-----------------------------------------------+-----------+
| 0x80 | Generic Transitive Experimental Use | [RFC7153] | | 0x80 | Generic Transitive Experimental Use Extended | [RFC7153] |
| | Extended Community (Sub-Types are defined | | | | Community (Sub-Types are defined in the | |
| | in the "Generic Transitive Experimental | | | | "Generic Transitive Experimental Use Extended | |
| | Use Extended Community Sub-Types" | | | | Community Sub-Types" registry) | |
| | registry) | | | 0x81 | Generic Transitive Experimental Use Extended | [this |
| 0x81 | Generic Transitive Experimental Use | [this | | | Community Part 2 (Sub-Types are defined in | document] |
| | Extended Community Part 2 (Sub-Types are | document] | | | the "Generic Transitive Experimental Use | [See |
| | defined in the "Generic Transitive | [See | | | Extended Community Part 2 Sub-Types" | Note-1] |
| | Experimental Use Extended Community Part 2 | Note-1] | | | Registry) | |
| | Sub-Types" Registry) | | | 0x82 | Generic Transitive Experimental Use Extended | [this |
| 0x82 | Generic Transitive Experimental Use | [this | | | Community Part 3 (Sub-Types are defined in | document] |
| | Extended Community Part 3 (Sub-Types are | document] | | | the "Generic Transitive Experimental Use | [See |
| | defined in the "Generic Transitive | [See | | | Extended Community Part 3 Sub-Types" | Note-1] |
| | Experimental Use Extended Community Part 3 | Note-1] | | | Registry) | |
| | Sub-Types" Registry) | | +-------+-----------------------------------------------+-----------+
+----------+--------------------------------------------+-----------+
Table 6: Registry: Generic Transitive Experimental Use Extended Table 6: Registry: Generic Transitive Experimental Use Extended
Community Types Community Types
Note-1: This document replaces [RFC7674]. Note-1: This document replaces [RFC7674].
For the sub-type part of the extended community actions IANA For the sub-type part of the extended community actions IANA
maintains and updated the following registries: maintains and updated the following registries:
+----------+-----------------------------------------+--------------+ +----------+-----------------------------------------+--------------+
skipping to change at page 31, line 39 skipping to change at page 31, line 39
[RFC7674] Haas, J., Ed., "Clarification of the Flowspec Redirect [RFC7674] Haas, J., Ed., "Clarification of the Flowspec Redirect
Extended Community", RFC 7674, DOI 10.17487/RFC7674, Extended Community", RFC 7674, DOI 10.17487/RFC7674,
October 2015, <https://www.rfc-editor.org/info/rfc7674>. October 2015, <https://www.rfc-editor.org/info/rfc7674>.
15.2. Informative References 15.2. Informative References
[I-D.ietf-idr-flow-spec-v6] [I-D.ietf-idr-flow-spec-v6]
McPherson, D., Raszuk, R., Pithawala, B., McPherson, D., Raszuk, R., Pithawala, B.,
akarch@cisco.com, a., and S. Hares, "Dissemination of Flow akarch@cisco.com, a., and S. Hares, "Dissemination of Flow
Specification Rules for IPv6", draft-ietf-idr-flow-spec- Specification Rules for IPv6", draft-ietf-idr-flow-spec-
v6-08 (work in progress), March 2017. v6-09 (work in progress), November 2017.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, DOI 10.17487/RFC4303, December 2005, RFC 4303, DOI 10.17487/RFC4303, December 2005,
<https://www.rfc-editor.org/info/rfc4303>. <https://www.rfc-editor.org/info/rfc4303>.
15.3. URIs 15.3. URIs
[1] https://github.com/stoffi92/flowspec-cmp [1] https://github.com/stoffi92/flowspec-cmp
Appendix A. Comparison with RFC 5575 Appendix A. Comparison with RFC 5575
 End of changes. 10 change blocks. 
32 lines changed or deleted 31 lines changed or added

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