Route Target ORF
draft-xu-idr-route-target-orf-01
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Xiaohu Xu , Shraddha Hegde , Srihari R. Sangli , Shunwan Zhuang , Jie Dong | ||
| Last updated | 2024-04-25 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-xu-idr-route-target-orf-01
Network Working Group X. Xu
Internet-Draft China Mobile
Intended status: Standards Track S. Hegde
Expires: 27 October 2024 S. Sangli
Juniper
S. Zhang
J. Dong
Huawei
25 April 2024
Route Target ORF
draft-xu-idr-route-target-orf-01
Abstract
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.
Status of This Memo
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 27 October 2024.
Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
Xu, et al. Expires 27 October 2024 [Page 1]
Internet-Draft Route Target ORF April 2024
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Route Target ORF Entry Encoding . . . . . . . . . . . . . . . 2
3. Route Target ORF Matching . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
7.1. Normative References . . . . . . . . . . . . . . . . . . 3
7.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
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.
1.1. Requirements Language
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].
2. Route Target ORF Entry Encoding
The value of the ORF-Type for the Route Target ORF is TBD.
Xu, et al. Expires 27 October 2024 [Page 2]
Internet-Draft Route Target ORF April 2024
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.
3. Route Target ORF Matching
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.
4. IANA Considerations
The value of the ORF-Type for the Route Target ORF is to be allocated
by IANA.
5. Security Considerations
This extension to BGP does not change the underlying security issues
in [RFC4271]
6. Acknowledgements
The authors would like to thank xxx for their valuable comments and
suggestions on this document.
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
Xu, et al. Expires 27 October 2024 [Page 3]
Internet-Draft Route Target ORF April 2024
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur,
"BGP-MPLS IP Virtual Private Network (VPN) Extension for
IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006,
<https://www.rfc-editor.org/info/rfc4659>.
[RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,
R., Patel, K., and J. Guichard, "Constrained Route
Distribution for Border Gateway Protocol/MultiProtocol
Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual
Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684,
November 2006, <https://www.rfc-editor.org/info/rfc4684>.
[RFC5291] Chen, E. and Y. Rekhter, "Outbound Route Filtering
Capability for BGP-4", RFC 5291, DOI 10.17487/RFC5291,
August 2008, <https://www.rfc-editor.org/info/rfc5291>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
7.2. Informative References
Authors' Addresses
Xiaohu Xu
China Mobile
Email: xuxiaohu_ietf@hotmail.com
Shraddha Hegde
Juniper
Email: shraddha@juniper.net
Srihari Sangli
Juniper
Email: ssangli@juniper.net
Xu, et al. Expires 27 October 2024 [Page 4]
Internet-Draft Route Target ORF April 2024
Shunwan
Huawei
Email: zhuangshunwan@huawei.com
Jie
Huawei
Email: jie.dong@huawei.com
Xu, et al. Expires 27 October 2024 [Page 5]