draft-ietf-idr-flow-spec-v6-18.txt   draft-ietf-idr-flow-spec-v6-19.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 5, 2021 Huawei Expires: May 6, 2021 Huawei
November 1, 2020 November 2, 2020
Dissemination of Flow Specification Rules for IPv6 Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-18 draft-ietf-idr-flow-spec-v6-19
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 5, 2021. This Internet-Draft will expire on May 6, 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 . . . . . . . . . . . . . . 5 3.3. Type 3 - Upper-Layer Protocol . . . . . . . . . . . . . . 4
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 . . . . . . . . . . . . . . . 9 4. Ordering of Flow Specifications . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
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 36 skipping to change at page 4, line 36
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
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.
In the case Length minus Offset is 0 every address matches. Length Length = Offset = 0 matches every address, otherwise Length MUST be
MUST always be in the range 0-128 and Length minus Offset MUST always in the range Offset < Length < 129 or the component is malformed.
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
 End of changes. 7 change blocks. 
10 lines changed or deleted 9 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/