draft-ietf-idr-flow-spec-v6-16.txt   draft-ietf-idr-flow-spec-v6-17.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 15, 2021 Huawei Expires: April 23, 2021 Huawei
October 12, 2020 October 20, 2020
Dissemination of Flow Specification Rules for IPv6 Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-16 draft-ietf-idr-flow-spec-v6-17
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 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 April 15, 2021. This Internet-Draft will expire on April 23, 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 40 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 . . . . . . . 15 Appendix A. Example python code: flow_rule_cmp_v6 . . . . . . . 14
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 3, line 51 skipping to change at page 3, line 51
MUST be: (AFI=2, SAFI=133) for IPv6 Flow Specification, and (AFI=2, MUST be: (AFI=2, SAFI=133) for IPv6 Flow Specification, and (AFI=2,
SAFI=134) for VPNv6 Flow Specification. SAFI=134) for VPNv6 Flow Specification.
3. IPv6 Flow Specification components 3. IPv6 Flow Specification components
The encoding of each of the components begins with a type field (1 The encoding of each of the components begins with a type field (1
octet) followed by a variable length parameter. The following octet) followed by a variable length parameter. The following
sections define component types and parameter encodings for IPv6. sections define component types and parameter encodings for IPv6.
Types 4, 5, 6, 9, 10 and 11, as defined in [I-D.ietf-idr-rfc5575bis], Types 4, 5, 6, 9, 10 and 11, as defined in [I-D.ietf-idr-rfc5575bis],
also apply to IPv6. Note that even if the definitions are the same also apply to IPv6. Note that IANA is requested to update the "Flow
(and not repeated here), the number space is managed separately Spec Component Types" registry in order to contain both IPv4 and IPv6
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 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.
skipping to change at page 6, line 27 skipping to change at page 6, line 29
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+
| 0 | 0 | 0 | 0 |LF |FF |IsF| 0 | | 0 | 0 | 0 | 0 |LF |FF |IsF| 0 |
+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+
Figure 1: Fragment Bitmask Operand Figure 1: Fragment Bitmask Operand
Bitmask values: Bitmask values:
IsF - Is a fragment - match if IPv6 Fragment Header ([RFC8200] IsF - Is a fragment other than the first - match if IPv6 Fragment
Section 4.5) Fragment Offset is not 0 Header ([RFC8200] Section 4.5) Fragment Offset is not 0
FF - First fragment - match if IPv6 Fragment Header ([RFC8200] FF - First fragment - match if IPv6 Fragment Header ([RFC8200]
Section 4.5) Fragment Offset is 0 AND M flag is 1 Section 4.5) Fragment Offset is 0 AND M flag is 1
LF - Last fragment - match if IPv6 Fragment Header ([RFC8200] LF - Last fragment - match if IPv6 Fragment Header ([RFC8200]
Section 4.5) Fragment Offset is not 0 AND M flag is 0 Section 4.5) Fragment Offset is not 0 AND M flag is 0
0 - MUST be set to 0 on NLRI encoding, and MUST be ignored during 0 - MUST be set to 0 on NLRI encoding, and MUST be ignored during
decoding decoding
skipping to change at page 14, line 34 skipping to change at page 14, line 34
<https://www.rfc-editor.org/info/rfc4760>. <https://www.rfc-editor.org/info/rfc4760>.
[RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community [RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community
Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009, Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009,
<https://www.rfc-editor.org/info/rfc5701>. <https://www.rfc-editor.org/info/rfc5701>.
[RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP [RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP
Extended Communities", RFC 7153, DOI 10.17487/RFC7153, Extended Communities", RFC 7153, DOI 10.17487/RFC7153,
March 2014, <https://www.rfc-editor.org/info/rfc7153>. March 2014, <https://www.rfc-editor.org/info/rfc7153>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", STD 86, RFC 8200, (IPv6) Specification", STD 86, RFC 8200,
DOI 10.17487/RFC8200, July 2017, DOI 10.17487/RFC8200, July 2017,
<https://www.rfc-editor.org/info/rfc8200>. <https://www.rfc-editor.org/info/rfc8200>.
11.2. URIs 11.2. URIs
 End of changes. 7 change blocks. 
14 lines changed or deleted 10 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/