draft-ietf-idr-flow-spec-v6-15.txt   draft-ietf-idr-flow-spec-v6-16.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
Intended status: Standards Track R. Raszuk, Ed. Updates: I-D.ietf-idr-rfc5575bis (if R. Raszuk, Ed.
Expires: March 25, 2021 Bloomberg LP approved) Bloomberg LP
S. Hares, Ed. Intended status: Standards Track S. Hares, Ed.
Huawei Expires: April 15, 2021 Huawei
September 21, 2020 October 12, 2020
Dissemination of Flow Specification Rules for IPv6 Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-15 draft-ietf-idr-flow-spec-v6-16
Abstract Abstract
Dissemination of Flow Specification Rules provides a Border Gateway Dissemination of Flow Specification Rules provides a Border Gateway
Protocol extension for the propagation of traffic flow information Protocol extension for the propagation of traffic flow information
for the purpose of rate limiting or filtering IPv4 protocol data for the purpose of rate limiting or filtering IPv4 protocol data
packets. packets.
This specification extends I-D.ietf-idr-rfc5575bis with IPv6 This document extends I-D.ietf-idr-rfc5575bis with IPv6
functionality. functionality. It also updates I-D.ietf-idr-rfc5575bis by changing
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 March 25, 2021. This Internet-Draft will expire on April 15, 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 39 skipping to change at page 2, line 40
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
Appendix A. Example python code: flow_rule_cmp_v6 . . . . . . . 14 Appendix A. Example python code: flow_rule_cmp_v6 . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
The growing amount of IPv6 traffic in private and public networks The growing amount of IPv6 traffic in private and public networks
requires the extension of tools used in IPv4-only networks to be also requires the extension of tools used in IPv4-only networks to be also
capable of supporting IPv6 data packets. capable of supporting IPv6 data packets.
This document analyzes the differences of IPv6 [RFC8200] flows This document analyzes the differences of IPv6 [RFC8200] flows
description from those of traditional IPv4 packets and propose a description from those of traditional IPv4 packets and propose a
skipping to change at page 4, line 20 skipping to change at page 4, line 20
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 on part of the IPv6 address where it
is required to skip (don't care) of N first bits of the address. is required to skip (don't care) of N first bits of the address.
This can be especially useful where part of the IPv6 address consists This can be especially useful where part of the IPv6 address consists
of an embedded IPv4 address and matching needs to happen only on the 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 leftmost bit in the length - The length field indicates the N-th most significant bit in
address where bitwise pattern matching stops. the address where bitwise pattern matching stops.
offset - The offset field indicates the number of leftmost address offset - The offset field indicates the number of most significant
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
is defined by the number of bits needed for pattern matching is defined by the number of bits needed for pattern matching
(length minus offset). (length minus offset).
padding - The minimum number of bits required to pad the component padding - The minimum number of bits required to pad the component
to an octet boundary. Padding bits MUST be 0 on encoding and MUST to an octet boundary. Padding bits MUST be 0 on encoding and MUST
be ignored on decoding. be ignored on decoding.
Length minus offset must always be 0 or more, otherwise this In the case Length minus Offset is 0 every address matches. Length
component is malformed. MUST always be in the range 0-128 and Length minus Offset MUST always
be 0 or more, otherwise this component is malformed.
3.2. Type 2 - Source IPv6 Prefix 3.2. Type 2 - Source 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 source prefix to match. The length, offset, pattern and Defines the source prefix to match. The length, offset, pattern and
padding are the same as in Section 3.1 padding are the same as in Section 3.1
3.3. Type 3 - Upper-Layer Protocol 3.3. Type 3 - Upper-Layer Protocol
skipping to change at page 10, line 17 skipping to change at page 10, line 17
8. IANA Considerations 8. IANA Considerations
This section complies with [RFC7153]. This section complies with [RFC7153].
8.1. Flow Spec IPv6 Component Types 8.1. Flow Spec IPv6 Component Types
IANA has created and maintains a registry entitled "Flow Spec IANA has created and maintains a registry entitled "Flow Spec
Component Types". IANA is requested to add [this document] to the Component Types". IANA is requested to add [this document] to the
reference for this registry. Furthermore the registry should be reference for this registry. Furthermore the registry should be
rewritten to also contain the IPv6 Flow Specification Component Types rewritten to also contain the IPv6 Flow Specification Component Types
as described below. as described below. The registration procedure should remain
unchanged.
8.1.1. Registry Template 8.1.1. Registry Template
Type Value: Type Value:
Contains the assigned Flow Specification component type value. Contains the assigned Flow Specification component type value.
IPv4 Name: IPv4 Name:
Contains the associated IPv4 Flow Specification component name Contains the associated IPv4 Flow Specification component name
as specified in [I-D.ietf-idr-rfc5575bis]. as specified in [I-D.ietf-idr-rfc5575bis].
skipping to change at page 10, line 40 skipping to change at page 10, line 41
as specified in this document. as specified in this document.
Reference: Reference:
Contains referenced to the specifications. Contains referenced to the specifications.
8.1.2. Registry Contents 8.1.2. Registry Contents
+ Type Value: 0 + Type Value: 0
+ IPv4 Name: Reserved + IPv4 Name: Reserved
+ IPv6 Name: Reserved + IPv6 Name: Reserved
+ Reference: [I-D.ietf-idr-rfc5575bis] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 1 + Type Value: 1
+ IPv4 Name: Destination Prefix + IPv4 Name: Destination Prefix
+ IPv6 Name: Destination IPv6 Prefix + IPv6 Name: Destination IPv6 Prefix
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 2 + Type Value: 2
+ IPv4 Name: Source Prefix + IPv4 Name: Source Prefix
+ IPv6 Name: Source IPv6 Prefix + IPv6 Name: Source IPv6 Prefix
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 3 + Type Value: 3
+ IPv4 Name: IP Protocol + IPv4 Name: IP Protocol
+ IPv6 Name: Upper-Layer Protocol + IPv6 Name: Upper-Layer Protocol
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 4 + Type Value: 4
+ IPv4 Name: Port + IPv4 Name: Port
+ IPv6 Name: Port + IPv6 Name: Port
+ Reference: [I-D.ietf-idr-rfc5575bis] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 5 + Type Value: 5
+ IPv4 Name: Destination Port + IPv4 Name: Destination Port
+ IPv6 Name: Destination Port + IPv6 Name: Destination Port
+ Reference: [I-D.ietf-idr-rfc5575bis] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 6 + Type Value: 6
+ IPv4 Name: Source Port + IPv4 Name: Source Port
+ IPv6 Name: Source Port + IPv6 Name: Source Port
+ Reference: [I-D.ietf-idr-rfc5575bis] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ 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] + 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] + 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] + 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
+ Reference: [I-D.ietf-idr-rfc5575bis] [this document] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
+ Type Value: 13 + Type Value: 13
+ IPv4 Name: Unassigned + IPv4 Name: Unassigned
+ IPv6 Name: Flow Label + IPv6 Name: Flow Label
+ Reference: [this document] + Reference: [this document]
+ 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] + Reference: [I-D.ietf-idr-rfc5575bis] [this document]
8.2. Extended Community Flow Spec IPv6 Actions 8.2. Extended Community Flow Spec IPv6 Actions
IANA maintains a registry entitled "Generic Transitive Experimental IANA maintains a registry entitled "Generic Transitive Experimental
Use Extended Community Sub-Types". For the purpose of this work, Use Extended Community Sub-Types". For the purpose of this work,
IANA is requested to assign a new value: IANA is requested to assign a new value:
+----------------+--------------------------------+-----------------+ +----------------+--------------------------------+-----------------+
| Sub-Type Value | Name | Reference | | Sub-Type Value | Name | Reference |
+----------------+--------------------------------+-----------------+ +----------------+--------------------------------+-----------------+
 End of changes. 17 change blocks. 
25 lines changed or deleted 28 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/