Dissemination of Flow Specification Rules
RFC 8955
Document | Type |
RFC - Proposed Standard
(December 2020; No errata)
Updated by RFC 8956
|
|
---|---|---|---|
Authors | Christoph Loibl , Susan Hares , Robert Raszuk , Danny McPherson , Martin Bacher | ||
Last updated | 2020-12-31 | ||
Replaces | draft-hr-idr-rfc5575bis | ||
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-04-13) | ||
IESG | IESG state | RFC 8955 (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 | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) C. Loibl Request for Comments: 8955 next layer Telekom GmbH Obsoletes: 5575, 7674 S. Hares Category: Standards Track Huawei ISSN: 2070-1721 R. Raszuk NTT Network Innovations D. McPherson Verisign M. Bacher T-Mobile Austria December 2020 Dissemination of Flow Specification Rules Abstract This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute (intra-domain and inter-domain) traffic Flow Specifications for IPv4 unicast and IPv4 BGP/MPLS VPN services. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix. It also specifies BGP Extended Community encoding formats, which can be used to propagate Traffic Filtering Actions along with the Flow Specification NLRI. Those Traffic Filtering Actions encode actions a routing system can take if the packet matches the Flow Specification. This document obsoletes both RFC 5575 and RFC 7674. 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/rfc8955. 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 2. Definitions of Terms Used in This Memo 3. Flow Specifications 4. Dissemination of IPv4 Flow Specification Information 4.1. Length Encoding 4.2. NLRI Value Encoding 4.2.1. Operators 4.2.2. Components 4.2.2.1. Type 1 - Destination Prefix 4.2.2.2. Type 2 - Source Prefix 4.2.2.3. Type 3 - IP Protocol 4.2.2.4. Type 4 - Port 4.2.2.5. Type 5 - Destination Port 4.2.2.6. Type 6 - Source Port 4.2.2.7. Type 7 - ICMP Type 4.2.2.8. Type 8 - ICMP Code 4.2.2.9. Type 9 - TCP Flags 4.2.2.10. Type 10 - Packet Length 4.2.2.11. Type 11 - DSCP (Diffserv Code Point) 4.2.2.12. Type 12 - Fragment 4.3. Examples of Encodings 5. Traffic Filtering 5.1. Ordering of Flow Specifications 6. Validation Procedure 7. Traffic Filtering Actions 7.1. Traffic Rate in Bytes (traffic-rate-bytes) Sub-Type 0x06 7.2. Traffic Rate in Packets (traffic-rate-packets) Sub-Type 0x0c 7.3. Traffic-Action (traffic-action) Sub-Type 0x07 7.4. RT Redirect (rt-redirect) Sub-Type 0x08 7.5. Traffic Marking (traffic-marking) Sub-Type 0x09 7.6. Interaction with Other Filtering Mechanisms in Routers 7.7. Considerations on Traffic Filtering Action Interference 8. Dissemination of Traffic Filtering in BGP/MPLS VPN Networks 9. Traffic Monitoring 10. Error Handling 11. IANA Considerations 11.1. AFI/SAFI Definitions 11.2. Flow Component Definitions 11.3. Extended Community Flow Specification Actions 12. Security Considerations 13. References 13.1. Normative References 13.2. Informative References Appendix A. Example Python code: flow_rule_cmp Appendix B. Comparison with RFC 5575 Acknowledgments Contributors Authors' Addresses 1. Introduction This document obsoletes "Dissemination of Flow Specification Rules" [RFC5575] (see Appendix B for the differences). This document alsoShow full document text