draft-ietf-idr-flow-spec-v6-20.txt   draft-ietf-idr-flow-spec-v6-21.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 20, 2021 Huawei Expires: May 28, 2021 Huawei
November 16, 2020 November 24, 2020
Dissemination of Flow Specification Rules for IPv6 Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-20 draft-ietf-idr-flow-spec-v6-21
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 20, 2021. This Internet-Draft will expire on May 28, 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 39
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. 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 15 11.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Appendix A. Example python code: flow_rule_cmp_v6 . . . . . . . 15 Appendix A. Example python code: flow_rule_cmp_v6 . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
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 also requires the extension of tools used in IPv4-only networks to also
support IPv6 data packets. support IPv6 data packets.
This document analyzes the differences between describing IPv6 This document analyzes the differences between describing IPv6
[RFC8200] flows and those of IPv4 packets. It specifies new Border [RFC8200] flows and those of IPv4 packets. It specifies new Border
Gateway Protocol [RFC4271] encoding formats to enable Dissemination Gateway Protocol [RFC4271] encoding formats to enable Dissemination
skipping to change at page 10, line 50 skipping to change at page 10, line 50
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).
7. Security Considerations 7. Security Considerations
This document extends the functionality in [I-D.ietf-idr-rfc5575bis] This document extends the functionality in [I-D.ietf-idr-rfc5575bis]
to be applicable to IPv6 data packets. The same Security to be applicable to IPv6 data packets. The same Security
Considerations from [I-D.ietf-idr-rfc5575bis] now also apply to IPv6 Considerations from [I-D.ietf-idr-rfc5575bis] now also apply to IPv6
networks. Otherwise, no new security issues are added to the BGP networks.
protocol.
[RFC7112] describes the impact of oversized IPv6 header chains when
trying to match on the transport header; [RFC8200] Section 4.5 also
requires that the first fragment must include the upper-layer header
but there could be wrongly formatted packets not respecting
[RFC8200]. IPv6 Flow Specification component type 3 (Section 3.3)
will not be enforced for those illegal packets. Moreover, there are
hardware limitations in several routers ([RFC8883] Section 1) that
may make it impossible to enforce a policy signaled by a type 3 Flow
Specification component or Flow Specification components that match
on upper-layer properties of the packet.
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
skipping to change at page 15, line 20 skipping to change at page 15, line 30
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760,
DOI 10.17487/RFC4760, January 2007, DOI 10.17487/RFC4760, January 2007,
<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>.
[RFC7112] Gont, F., Manral, V., and R. Bonica, "Implications of
Oversized IPv6 Header Chains", RFC 7112,
DOI 10.17487/RFC7112, January 2014,
<https://www.rfc-editor.org/info/rfc7112>.
[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>.
[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>.
[RFC8883] Herbert, T., "ICMPv6 Errors for Discarding Packets Due to
Processing Limits", RFC 8883, DOI 10.17487/RFC8883,
September 2020, <https://www.rfc-editor.org/info/rfc8883>.
11.2. URIs 11.2. URIs
[1] https://github.com/stoffi92/draft-ietf-idr-flow-spec- [1] https://github.com/stoffi92/draft-ietf-idr-flow-spec-
v6/tree/master/flowspec-cmp v6/tree/master/flowspec-cmp
Appendix A. Example python code: flow_rule_cmp_v6 Appendix A. Example python code: flow_rule_cmp_v6
<CODE BEGINS> <CODE BEGINS>
""" """
Copyright (c) 2020 IETF Trust and the persons identified as authors Copyright (c) 2020 IETF Trust and the persons identified as authors
 End of changes. 7 change blocks. 
9 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/