draft-ietf-idr-flow-spec-v6-21.txt   draft-ietf-idr-flow-spec-v6-22.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: May 28, 2021 Huawei Expires: June 17, 2021 Huawei
November 24, 2020 December 14, 2020
Dissemination of Flow Specification Rules for IPv6 Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-21 draft-ietf-idr-flow-spec-v6-22
Abstract Abstract
Dissemination of Flow Specification Rules I-D.ietf-idr-rfc5575bis Dissemination of Flow Specification Rules I-D.ietf-idr-rfc5575bis
provides a Border Gateway Protocol extension for the propagation of provides a Border Gateway Protocol extension for the propagation of
traffic flow information for the purpose of rate limiting or traffic flow information for the purpose of rate limiting or
filtering IPv4 protocol data 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
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 May 28, 2021. This Internet-Draft will expire on June 17, 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 28 skipping to change at page 2, line 28
3.2. Type 2 - Source IPv6 Prefix . . . . . . . . . . . . . . . 4 3.2. Type 2 - Source IPv6 Prefix . . . . . . . . . . . . . . . 4
3.3. Type 3 - Upper-Layer Protocol . . . . . . . . . . . . . . 5 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) . . . . . . . . . . . . . . . 7 3.7. Type 13 - Flow Label (new) . . . . . . . . . . . . . . . 7
3.8. Encoding Example . . . . . . . . . . . . . . . . . . . . 7 3.8. Encoding Example . . . . . . . . . . . . . . . . . . . . 7
4. Ordering of Flow Specifications . . . . . . . . . . . . . . . 9 4. Ordering of Flow Specifications . . . . . . . . . . . . . . . 9
5. Validation Procedure . . . . . . . . . . . . . . . . . . . . 10 5. Validation Procedure . . . . . . . . . . . . . . . . . . . . 10
6. IPv6 Traffic Filtering Action changes . . . . . . . . . . . . 10 6. IPv6 Traffic Filtering Action changes . . . . . . . . . . . . 10
6.1. Redirect IPv6 (rt-redirect-ipv6) Type/Sub-Type 0x80/TBD . 10 6.1. Redirect IPv6 (rt-redirect-ipv6) Type TBD . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8.1. Flow Spec IPv6 Component Types . . . . . . . . . . . . . 11 8.1. Flow Spec IPv6 Component Types . . . . . . . . . . . . . 11
8.1.1. Registry Template . . . . . . . . . . . . . . . . . . 11 8.1.1. Registry Template . . . . . . . . . . . . . . . . . . 11
8.1.2. Registry Contents . . . . . . . . . . . . . . . . . . 11 8.1.2. Registry Contents . . . . . . . . . . . . . . . . . . 11
8.2. Extended Community Flow Spec IPv6 Actions . . . . . . . . 13 8.2. IPv6-Address-Specific Extended Community Flow Spec IPv6
Actions . . . . . . . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
11.1. Normative References . . . . . . . . . . . . . . . . . . 14 11.1. Normative References . . . . . . . . . . . . . . . . . . 14
11.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 16 11.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Appendix A. Example python code: flow_rule_cmp_v6 . . . . . . . 16 Appendix A. Example python code: flow_rule_cmp_v6 . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
skipping to change at page 10, line 17 skipping to change at page 10, line 17
The validation procedure is the same as specified in The validation procedure is the same as specified in
[I-D.ietf-idr-rfc5575bis] Section 6 with the exception that item a) [I-D.ietf-idr-rfc5575bis] Section 6 with the exception that item a)
of the validation procedure should now read as follows: of the validation procedure should now read as follows:
a) A destination prefix component with offset=0 is embedded in the a) A destination prefix component with offset=0 is embedded in the
Flow Specification Flow Specification
6. IPv6 Traffic Filtering Action changes 6. IPv6 Traffic Filtering Action changes
Traffic Filtering Actions from [I-D.ietf-idr-rfc5575bis] Section 7 Traffic Filtering Actions from [I-D.ietf-idr-rfc5575bis] Section 7
can also be applied to IPv6 Flow Specifications. To allow an IPv6 can also be applied to IPv6 Flow Specifications. To allow an IPv6-
address specific route-target, a new Traffic Filtering Action IPv6 Address-Specific Route-Target, a new Traffic Filtering Action IPv6-
address specific extended community is specified in Section 6.1 Address-Specific Extended Community [RFC5701] is specified in
below. Section 6.1 below.
6.1. Redirect IPv6 (rt-redirect-ipv6) Type/Sub-Type 0x80/TBD 6.1. Redirect IPv6 (rt-redirect-ipv6) Type TBD
The redirect IPv6 address specific extended community allows the The redirect IPv6-Address-Specific Extended Community allows the
traffic to be redirected to a VRF routing instance that lists the traffic to be redirected to a VRF routing instance that lists the
specified IPv6 address specific route-target in its import policy. specified IPv6-Address-Specific Route-Target in its import policy.
If several local instances match this criteria, the choice between If several local instances match this criteria, the choice between
them is a local matter (for example, the instance with the lowest them is a local matter (for example, the instance with the lowest
Route Distinguisher value can be elected). Route Distinguisher value can be elected).
This extended community uses the same encoding as the IPv6 address This IPv6-Address-Specific Extended Community uses the same encoding
specific Route Target extended community [RFC5701] Section 2 with the as the IPv6-Address-Specific Route-Target Extended Community
high-order octet of the Type always set to 0x80 and the Sub-Type [RFC5701] Section 2 with the Type value always TBD.
always TBD.
The Local Administrator sub-field contains a number from a numbering The Local Administrator sub-field contains a number from a numbering
space that is administered by the organization to which the IP space that is administered by the organization to which the IP
address carried in the Global Administrator sub-field has been address carried in the Global Administrator sub-field has been
assigned by an appropriate authority. assigned by an appropriate authority.
Interferes with: All BGP Flow Specification redirect Traffic Interferes with: All BGP Flow Specification redirect Traffic
Filtering Actions (with itself and those specified in Filtering Actions (with itself and those specified in
[I-D.ietf-idr-rfc5575bis] Section 7.4). [I-D.ietf-idr-rfc5575bis] Section 7.4).
skipping to change at page 13, line 4 skipping to change at page 12, line 41
+ Type Value: 7 + Type Value: 7
+ IPv4 Name: ICMP Type + IPv4 Name: ICMP Type
+ IPv6 Name: ICMPv6 Type + IPv6 Name: ICMPv6 Type
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 8 + Type Value: 8
+ IPv4 Name: ICMP Code + IPv4 Name: ICMP Code
+ IPv6 Name: ICMPv6 Code + IPv6 Name: ICMPv6 Code
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 9 + Type Value: 9
+ IPv4 Name: TCP flags + IPv4 Name: TCP Flags
+ IPv6 Name: TCP flags + IPv6 Name: TCP Flags
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 10 + Type Value: 10
+ IPv4 Name: Packet length + IPv4 Name: Packet Length
+ IPv6 Name: Packet length + IPv6 Name: Packet Length
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 11 + Type Value: 11
+ IPv4 Name: DSCP + IPv4 Name: DSCP
+ IPv6 Name: DSCP + IPv6 Name: DSCP
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 12 + Type Value: 12
+ IPv4 Name: Fragment + IPv4 Name: Fragment
+ IPv6 Name: Fragment + IPv6 Name: Fragment
skipping to change at page 13, line 39 skipping to change at page 13, line 37
+ Type Value: 14-254 + Type Value: 14-254
+ IPv4 Name: Unassigned + IPv4 Name: Unassigned
+ IPv6 Name: Unassigned + IPv6 Name: Unassigned
+ Reference: + Reference:
+ Type Value: 255 + Type Value: 255
+ IPv4 Name: Reserved + IPv4 Name: Reserved
+ IPv6 Name: Reserved + IPv6 Name: Reserved
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
8.2. Extended Community Flow Spec IPv6 Actions 8.2. IPv6-Address-Specific Extended Community Flow Spec IPv6 Actions
IANA maintains a registry entitled "Generic Transitive Experimental IANA maintains a registry entitled "Transitive IPv6-Address-Specific
Use Extended Community Sub-Types". For the purpose of this work, Extended Community Types". For the purpose of this work, IANA is
IANA is requested to assign a new value: requested to assign a new value:
+----------------+--------------------------------+-----------------+ +------------+-----------------------------------+-----------------+
| Sub-Type Value | Name | Reference | | Type Value | Name | Reference |
+----------------+--------------------------------+-----------------+ +------------+-----------------------------------+-----------------+
| TBD | Flow spec rt-redirect-ipv6 | [this document] | | TBD | Flow spec rt-redirect-ipv6 format | [this document] |
| | format | | +------------+-----------------------------------+-----------------+
+----------------+--------------------------------+-----------------+
Table 1: Registry: Generic Transitive Experimental Use Extended Table 1: Registry: Transitive IPv6-Address-Specific Extended
Community Sub-Types Community Types
9. Acknowledgements 9. Acknowledgements
Authors would like to thank Pedro Marques, Hannes Gredler, Bruno Authors would like to thank Pedro Marques, Hannes Gredler, Bruno
Rijsman, Brian Carpenter, and Thomas Mangin for their valuable input. Rijsman, Brian Carpenter, and Thomas Mangin for their valuable input.
10. Contributors 10. Contributors
Danny McPherson Danny McPherson
Verisign, Inc. Verisign, Inc.
 End of changes. 17 change blocks. 
33 lines changed or deleted 33 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/