draft-ietf-idr-flow-spec-v6-17.txt   draft-ietf-idr-flow-spec-v6-18.txt 
IDR Working Group C. Loibl, Ed. IDR Working Group C. Loibl, Ed.
Internet-Draft next layer Telekom GmbH Internet-Draft next layer Telekom GmbH
Updates: I-D.ietf-idr-rfc5575bis (if R. Raszuk, Ed. Updates: I-D.ietf-idr-rfc5575bis (if R. Raszuk, Ed.
approved) Bloomberg LP approved) Bloomberg LP
Intended status: Standards Track S. Hares, Ed. Intended status: Standards Track S. Hares, Ed.
Expires: April 23, 2021 Huawei Expires: May 5, 2021 Huawei
October 20, 2020 November 1, 2020
Dissemination of Flow Specification Rules for IPv6 Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-17 draft-ietf-idr-flow-spec-v6-18
Abstract Abstract
Dissemination of Flow Specification Rules provides a Border Gateway Dissemination of Flow Specification Rules I-D.ietf-idr-rfc5575bis
Protocol extension for the propagation of traffic flow information provides a Border Gateway Protocol extension for the propagation of
for the purpose of rate limiting or filtering IPv4 protocol data traffic flow information for the purpose of rate limiting or
packets. filtering IPv4 protocol data packets.
This document extends I-D.ietf-idr-rfc5575bis with IPv6 This document extends I-D.ietf-idr-rfc5575bis with IPv6
functionality. It also updates I-D.ietf-idr-rfc5575bis by changing functionality. It also updates I-D.ietf-idr-rfc5575bis by changing
the IANA Flow Spec Component Types registry. the IANA Flow Spec Component Types registry.
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 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 23, 2021. This Internet-Draft will expire on May 5, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
skipping to change at page 2, line 19 skipping to change at page 2, line 19
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Definitions of Terms Used in This Memo . . . . . . . . . 3 1.1. Definitions of Terms Used in This Memo . . . . . . . . . 3
2. IPv6 Flow Specification encoding in BGP . . . . . . . . . . . 3 2. IPv6 Flow Specification encoding in BGP . . . . . . . . . . . 3
3. IPv6 Flow Specification components . . . . . . . . . . . . . 3 3. IPv6 Flow Specification components . . . . . . . . . . . . . 3
3.1. Type 1 - Destination IPv6 Prefix . . . . . . . . . . . . 4 3.1. Type 1 - Destination IPv6 Prefix . . . . . . . . . . . . 4
3.2. Type 2 - Source IPv6 Prefix . . . . . . . . . . . . . . . 4 3.2. Type 2 - Source IPv6 Prefix . . . . . . . . . . . . . . . 4
3.3. Type 3 - Upper-Layer Protocol . . . . . . . . . . . . . . 4 3.3. Type 3 - Upper-Layer Protocol . . . . . . . . . . . . . . 5
3.4. Type 7 - ICMPv6 Type . . . . . . . . . . . . . . . . . . 5 3.4. Type 7 - ICMPv6 Type . . . . . . . . . . . . . . . . . . 5
3.5. Type 8 - ICMPv6 Code . . . . . . . . . . . . . . . . . . 5 3.5. Type 8 - ICMPv6 Code . . . . . . . . . . . . . . . . . . 5
3.6. Type 12 - Fragment . . . . . . . . . . . . . . . . . . . 6 3.6. Type 12 - Fragment . . . . . . . . . . . . . . . . . . . 6
3.7. Type 13 - Flow Label (new) . . . . . . . . . . . . . . . 6 3.7. Type 13 - Flow Label (new) . . . . . . . . . . . . . . . 6
3.8. Encoding Example . . . . . . . . . . . . . . . . . . . . 7 3.8. Encoding Example . . . . . . . . . . . . . . . . . . . . 7
4. Ordering of Flow Specifications . . . . . . . . . . . . . . . 8 4. Ordering of Flow Specifications . . . . . . . . . . . . . . . 9
5. Validation Procedure . . . . . . . . . . . . . . . . . . . . 9 5. Validation Procedure . . . . . . . . . . . . . . . . . . . . 9
6. IPv6 Traffic Filtering Action changes . . . . . . . . . . . . 9 6. IPv6 Traffic Filtering Action changes . . . . . . . . . . . . 9
6.1. Redirect IPv6 (rt-redirect-ipv6) Type/Sub-Type 0x80/TBD . 9 6.1. Redirect IPv6 (rt-redirect-ipv6) Type/Sub-Type 0x80/TBD . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8.1. Flow Spec IPv6 Component Types . . . . . . . . . . . . . 10 8.1. Flow Spec IPv6 Component Types . . . . . . . . . . . . . 10
8.1.1. Registry Template . . . . . . . . . . . . . . . . . . 10 8.1.1. Registry Template . . . . . . . . . . . . . . . . . . 10
8.1.2. Registry Contents . . . . . . . . . . . . . . . . . . 10 8.1.2. Registry Contents . . . . . . . . . . . . . . . . . . 10
8.2. Extended Community Flow Spec IPv6 Actions . . . . . . . . 12 8.2. Extended Community Flow Spec IPv6 Actions . . . . . . . . 12
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
11.1. Normative References . . . . . . . . . . . . . . . . . . 13 11.1. Normative References . . . . . . . . . . . . . . . . . . 13
11.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 14 11.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 14
skipping to change at page 4, line 14 skipping to change at page 4, line 14
Spec Component Types" registry in order to contain both IPv4 and IPv6 Spec Component Types" registry in order to contain both IPv4 and IPv6
Flow Specification component type numbers in a single registry Flow Specification component type numbers in a single registry
(Section 8). (Section 8).
3.1. Type 1 - Destination IPv6 Prefix 3.1. Type 1 - Destination IPv6 Prefix
Encoding: <type (1 octet), length (1 octet), offset (1 octet), Encoding: <type (1 octet), length (1 octet), offset (1 octet),
pattern (variable), padding(variable) > pattern (variable), padding(variable) >
Defines the destination prefix to match. The offset has been defined Defines the destination prefix to match. The offset has been defined
to allow for flexible matching on part of the IPv6 address where it to allow for flexible matching to portions of an IPv6 address where
is required to skip (don't care) of N first bits of the address. one is required to skip over the first N bits of the address (these
This can be especially useful where part of the IPv6 address consists bits skipped are often indicated as "don't care" bits). This can be
of an embedded IPv4 address and matching needs to happen only on the especially useful where part of the IPv6 address consists of an
embedded IPv4 address and matching needs to happen only on the
embedded IPv4 address. The encoded pattern contains enough octets embedded IPv4 address. The encoded pattern contains enough octets
for the bits used in matching (length minus offset bits). for the bits used in matching (length minus offset bits).
length - The length field indicates the N-th most significant bit in length - The length field indicates the N-th most significant bit in
the address where bitwise pattern matching stops. the address where bitwise pattern matching stops.
offset - The offset field indicates the number of most significant offset - The offset field indicates the number of most significant
address bits to skip before bitwise pattern matching starts. address bits to skip before bitwise pattern matching starts.
pattern - Contains the matching pattern. The length of the pattern pattern - Contains the matching pattern. The length of the pattern
skipping to change at page 7, line 47 skipping to change at page 8, line 5
| 0x56 | pattern | | | 0x56 | pattern | |
| 0x78 | pattern | | | 0x78 | pattern | |
| 0x9A | pattern | (no padding needed) | | 0x9A | pattern | (no padding needed) |
| 0x03 | type | Type 3 - upper-layer-proto | | 0x03 | type | Type 3 - upper-layer-proto |
| 0x81 | numeric_op | end-of-list, value size=1, == | | 0x81 | numeric_op | end-of-list, value size=1, == |
| 0x06 | value | 06 | | 0x06 | value | 06 |
+-------+------------+-------------------------------+ +-------+------------+-------------------------------+
This constitutes a NLRI with a NLRI length of 18 octets. This constitutes a NLRI with a NLRI length of 18 octets.
Neither for the destination prefix pattern (length - offset = 32 bit) Padding is not needed either for the destination prefix pattern
nor for the source prefix pattern (length - offset = 40 bit) any (length - offset = 32 bit) or for the source prefix pattern (length -
padding is needed (both patterns end on a octet boundary). offset = 40 bit), as both patterns end on an octet boundary.
3.8.2. Example 2 3.8.2. Example 2
The following example demonstrates the prefix encoding for: "all The following example demonstrates the prefix encoding for: "all
packets from ::1234:5678:9A00:0/65-104 to 2001:DB8::/32". packets from ::1234:5678:9A00:0/65-104 to 2001:DB8::/32".
+--------+----------------------+-------------------------+ +--------+----------------------+-------------------------+
| length | destination | source | | length | destination | source |
+--------+----------------------+-------------------------+ +--------+----------------------+-------------------------+
| 0x0f | 01 20 00 20 01 0D B8 | 02 68 41 24 68 ac f1 34 | | 0x0f | 01 20 00 20 01 0D B8 | 02 68 41 24 68 ac f1 34 |
 End of changes. 9 change blocks. 
18 lines changed or deleted 19 lines changed or added

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