Dissemination of Flow Specification Rules for IPv6
RFC 8956
Document | Type |
RFC - Proposed Standard
(December 2020; No errata)
Updates RFC 8955
|
|
---|---|---|---|
Authors | Christoph Loibl , Robert Raszuk , Susan Hares | ||
Last updated | 2020-12-31 | ||
Replaces | draft-raszuk-idr-flow-spec-v6 | ||
Stream | IETF | ||
Formats | plain text html xml pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Jie Dong | ||
Shepherd write-up | Show (last changed 2020-06-23) | ||
IESG | IESG state | RFC 8956 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alvaro Retana | ||
Send notices to | Jie Dong <jie.dong@huawei.com>, aretana.ietf@gmail.com | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) C. Loibl, Ed. Request for Comments: 8956 next layer Telekom GmbH Updates: 8955 R. Raszuk, Ed. Category: Standards Track NTT Network Innovations ISSN: 2070-1721 S. Hares, Ed. Huawei December 2020 Dissemination of Flow Specification Rules for IPv6 Abstract "Dissemination of Flow Specification Rules" (RFC 8955) provides a Border Gateway Protocol (BGP) extension for the propagation of traffic flow information for the purpose of rate limiting or filtering IPv4 protocol data packets. This document extends RFC 8955 with IPv6 functionality. It also updates RFC 8955 by changing the IANA Flow Spec Component Types registry. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8956. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction 1.1. Definitions of Terms Used in This Memo 2. IPv6 Flow Specification Encoding in BGP 3. IPv6 Flow Specification Components 3.1. Type 1 - Destination IPv6 Prefix 3.2. Type 2 - Source IPv6 Prefix 3.3. Type 3 - Upper-Layer Protocol 3.4. Type 7 - ICMPv6 Type 3.5. Type 8 - ICMPv6 Code 3.6. Type 12 - Fragment 3.7. Type 13 - Flow Label (new) 3.8. Encoding Examples 4. Ordering of Flow Specifications 5. Validation Procedure 6. IPv6 Traffic Filtering Action Changes 6.1. Redirect IPv6 (rt-redirect-ipv6) Type 0x000d 7. Security Considerations 8. IANA Considerations 8.1. Flow Spec IPv6 Component Types 8.2. IPv6-Address-Specific Extended Community Flow Spec IPv6 Actions 9. Normative References Appendix A. Example Python Code: flow_rule_cmp_v6 Acknowledgments Contributors Authors' Addresses 1. Introduction The growing amount of IPv6 traffic in private and public networks requires the extension of tools used in IPv4-only networks to also support IPv6 data packets. This document analyzes the differences between describing IPv6 [RFC8200] flows and those of IPv4 packets. It specifies new Border Gateway Protocol [RFC4271] encoding formats to enable "Dissemination of Flow Specification Rules" [RFC8955] for IPv6. This specification is an extension of the base established in [RFC8955]. It only defines the delta changes required to support IPv6, while all other definitions and operation mechanisms of "Dissemination of Flow Specification Rules" will remain in the main specification and will not be repeated here. 1.1. Definitions of Terms Used in This Memo AFI: Address Family Identifier AS: Autonomous System NLRI: Network Layer Reachability Information SAFI: Subsequent Address Family Identifier VRF: Virtual Routing and Forwarding The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 2. IPv6 Flow Specification Encoding in BGP [RFC8955] defines SAFIs 133 (Dissemination of Flow Specification rules) and 134 (L3VPN Dissemination of Flow Specification rules) in order to carry the corresponding Flow Specification. Implementations wishing to exchange IPv6 Flow Specifications MUST use BGP's Capability Advertisement facility to exchange the Multiprotocol Extension Capability Code (Code 1), as defined in [RFC4760]. TheShow full document text