idnits 2.17.1 draft-xu-bess-l3vpn-prefix-orf-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 22, 2015) is 3324 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Xu 3 Internet-Draft Huawei 4 Intended status: Standards Track C. Jacquenet 5 Expires: September 21 2015 Orange 6 March 22, 2015 8 L3VPN Address Prefix Based Outbound Route Filter for BGP-4 9 draft-xu-bess-l3vpn-prefix-orf-01 11 Abstract 13 This document defines a new Outbound Router Filter (ORF) type for 14 BGP, refered to as "L3VPN Address Prefix Outbound Route Filter", that 15 can be used to perform L3VPN address-prefix-based route filtering. 16 This ORF-type supports prefix-length- or range-based matching, wild- 17 card-based address prefix matching, as well as the exact address 18 prefix matching for L3VPN address families. The L3VPN Address Prefix 19 ORF is applicable in the Virtual Subnet context. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on September 21, 2015. 38 Copyright Notice 40 Copyright (c) 2015 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. L3VPN Address Prefix ORF Encoding . . . . . . . . . . . . . . 3 59 4. L3VPN Address Prefix ORF Matching . . . . . . . . . . . . . . 4 60 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 62 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 63 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 65 8.2. Informative References . . . . . . . . . . . . . . . . . 5 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 68 1. Introduction 70 The Outbound Route Filtering (ORF) Capability defined in [RFC5291] 71 provides a mechanism for a BGP speaker to send to its BGP peer a set 72 of ORFs that can be used by its peer to filter its outbound routing 73 updates to the speaker. The Address Prefix ORF defined in [RFC5292] 74 is used to perform address-prefix-based route filtering. However, 75 the Address Prefix ORF is not much suitable for L3VPN [RFC4364] route 76 filtering since there is no Route-Target (RT) field contained in the 77 Address Prefix ORF entry. 79 This document builds on [RFC5292] and defines a new ORF-type for BGP, 80 referred to as "L3VPN Address Prefix Outbound Route Filter (L3VPN 81 Address Prefix ORF)", that can be used to perform L3VPN address 82 prefix-based route filtering. The L3VPN Address Prefix ORF supports 83 prefix-length- or range-based matching, wild-card-based address 84 prefix matching, as well as the exact address prefix matching for 85 L3VPN address families. The L3VPN Address Prefix ORF is applicable 86 to reduce the RIB size of PE routers in the Virtual Subnet 87 [I-D.ietf-l3vpn-virtual-subnet] context. 89 1.1. Requirements Language 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in RFC 2119 [RFC2119]. 95 2. Terminology 97 This memo makes use of the terms defined in [RFC5292] and [RFC4364]. 99 3. L3VPN Address Prefix ORF Encoding 101 The ORF-Type for the L3VPN Address Prefix ORF-Type is TBD. 103 A L3VPN Address Prefix ORF entry includes a Route Target field in 104 addition to those fields which have been contained in the Address 105 Prefix ORF [RFC5292]. That's to say, a L3VPN Address Prefix ORF 106 entry consists of the following fields . Note that 108 the Prefix field here doesn't include the Route Distinguisher (RD) 109 part of a L3VPN address prefix. For example, in the case of a VPNv4 110 address prefix, only the IPv4 address prefix part of that VPNv4 111 address prefix is contained in that Prefix field. 113 A L3VPN Address Prefix ORF entry is encoded as follows: the "Action", 114 "Match" and "Reserved" fields of the entry are encoded in the common 115 part [RFC5291], while the remaining fields of the entry are encoded 116 in the "type specific part" [RFC5291], as shown in Figure 1. When 117 the Action component of an ORF entry specifies REMOVE-ALL, the entry 118 consists of only the common part. 120 +--------------------------------+ 121 | Sequence (4 octets) | 122 +--------------------------------+ 123 | Route Target (8 octets) | 124 +--------------------------------+ 125 | Minlen (1 octet) | 126 +--------------------------------+ 127 | Maxlen (1 octet) | 128 +--------------------------------+ 129 | Length (1 octet) | 130 +--------------------------------+ 131 | Prefix (variable length) | 132 +--------------------------------+ 134 Figure 1: Type Specific Part of L3VPN Address Prefix ORF Entry 135 Encoding 137 4. L3VPN Address Prefix ORF Matching 139 When performing route matching search on those L3VPN routes which are 140 associated with the Route Target as specified in the received L3VPN 141 Address Prefix ORF entries, the Address-Prefix-ORF-specific matching 142 rules as defined in [RFC5292] are almost preserved except that the RD 143 SHOULD be ignored. 145 5. Acknowledgements 147 The authors would like to thank Mach Chen and Shunwan Zhuang for 148 their comments on this document. 150 6. IANA Considerations 152 The ORF-type for the L3VPN Address Prefix ORF needs to be assigned by 153 the IANA. 155 7. Security Considerations 157 This document does not introduce any new security considerations. 159 8. References 161 8.1. Normative References 163 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 164 Requirement Levels", BCP 14, RFC 2119, March 1997. 166 [RFC5291] Chen, E. and Y. Rekhter, "Outbound Route Filtering 167 Capability for BGP-4", RFC 5291, August 2008. 169 [RFC5292] Chen, E. and S. Sangli, "Address-Prefix-Based Outbound 170 Route Filter for BGP-4", RFC 5292, August 2008. 172 8.2. Informative References 174 [I-D.ietf-l3vpn-virtual-subnet] 175 Xu, X., Raszuk, R., Hares, S., Yongbing, F., Jacquenet, 176 C., Boyes, T., and B. Fee, "Virtual Subnet: A L3VPN-based 177 Subnet Extension Solution", draft-ietf-l3vpn-virtual- 178 subnet-03 (work in progress), December 2014. 180 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 181 Networks (VPNs)", RFC 4364, February 2006. 183 Authors' Addresses 185 Xiaohu Xu 186 Huawei 188 Email: xuxiaohu@huawei.com 190 Christian Jacquenet 191 Orange 193 Email: christian.jacquenet@orange.com