| Internet-Draft | Route Target ORF | November 2024 |
| Xu, et al. | Expires 5 May 2025 | [Page] |
This document defines a new Outbound Router Filter (ORF) type for BGP, referred to as "Route Target Outbound Route Filter", that can be used to perform route target based route filtering.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 5 May 2025.¶
Copyright (c) 2024 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Outbound Route Filtering Capability defined in [RFC5291] provides a mechanism for a BGP speaker to send to its BGP peer a set of Outbound Route Filters (ORFs) that can be used by its peer to filter its outbound routing updates to the speaker.¶
This document defines a new Outbound Router Filter (ORF) type for BGP, referred to as "Route Target Outbound Route Filter", that can be used to perform route target based route filtering.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].¶
The value of the ORF-Type for the Route Target ORF is TBD.¶
The Route Target ORF entry is encoded as follows: the "Action", "Match" and "Reserved" fields are encoded in the common part [RFC5291], while the "Route Target" field of 8 octets is encoded in the "type specific part" [RFC5291] . When the Action component of an ORF entry specifies REMOVE-ALL, the entry consists of only the common part.¶
The Route Target field is filled with a route target value used for searching matching routes. A route target value of zero，referred to as the default route target, means any route target value would be considered as matched.¶
In addition to the general procedures defined in [RFC5291], the following procedures are specified as follows:¶
When performing route matching search on VPN routes, those VPN routes are associated with the Route Target as specified in the received Route Target ORF entries would be considered as matched routes . If the Route Target as specified in the received Route Target ORF entries is filled with all zeros, all VPN routes would be considered as matched routes.¶
The value of the ORF-Type for the Route Target ORF is to be allocated by IANA.¶
This extension to BGP does not change the underlying security issues in [RFC4271]¶
The authors would like to thank xxx for their valuable comments and suggestions on this document.¶