idnits 2.17.1 draft-xu-l3vpn-prefix-orf-00.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 (January 23, 2014) is 3746 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) == Outdated reference: A later version (-03) exists of draft-xu-l3vpn-virtual-subnet-02 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 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 January 23, 2014 5 Expires: July 27, 2014 7 VPN Address Prefix Based Outbound Route Filter for BGP-4 8 draft-xu-l3vpn-prefix-orf-00 10 Abstract 12 This document defines a new Outbound Router Filter (ORF) type for 13 BGP, refered to as "VPN Address Prefix Outbound Route Filter", that 14 can be used to perform VPN address-prefix-based route filtering. 15 This ORF-type supports prefix-length- or range-based matching, wild- 16 card-based address prefix matching, as well as the exact address 17 prefix matching for VPN address families. The VPN Address Prefix ORF 18 is applicable in the context of Virtual Subnet and may also be 19 applicable in other BGP/MPLS IP VPN environments. 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 July 27, 2014. 38 Copyright Notice 40 Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . 2 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. VPN Address Prefix ORF Encoding . . . . . . . . . . . . . . . 3 59 4. VPN Address Prefix ORF Matching . . . . . . . . . . . . . . . 3 60 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 62 7. Security Considerations . . . . . . . . . . . . . . . . . . . 3 63 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 8.1. Normative References . . . . . . . . . . . . . . . . . . 3 65 8.2. Informative References . . . . . . . . . . . . . . . . . 4 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 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 VPN route filting 76 since there is no Route-Target (RT) field contained in the Address 77 Prefix ORF entry. 79 This document builds on [RFC5292] and defines a new ORF-type for BGP, 80 refered to as "VPN Address Prefix Outbound Route Filter (VPN Address 81 Prefix ORF)", that can be used to perform VPN address-prefix-based 82 route filtering. The VPN Address Prefix ORF supports prefix-length- 83 or range-based matching, wild-card-based address prefix matching, as 84 well as the exact address prefix matching for VPN address families. 85 The VPN Address Prefix ORF is applicable in the context of Virtual 86 Subnet [I-D.xu-l3vpn-virtual-subnet] and may also be applicable in 87 other BGP/MPLS IP VPN [RFC4364] environments. 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. VPN Address Prefix ORF Encoding 101 A VPN Address Prefix ORF entry includes a Route Target field in 102 addition to those fields which have been contained in the Address 103 Prefix ORF. That's to say, the VPN Address Prefix ORF entry consists 104 of the fields . Note that the Prefix field here doesn't include the Route 106 Distinguisher (RD) part of a VPN address prefix. For example, in the 107 case of VPNv4 address prefix, only the IPv4 address prefix part is 108 contained in that Prefix field. 110 4. VPN Address Prefix ORF Matching 112 When performing route matching search on those VPN routes which are 113 assocaited with the Route Target as specified in the received VPN 114 Adress Prefix ORF, the Address-Prefix-ORF-specific matching rules 115 defined in [RFC5292] are almost preserved except that the RD SHOULD 116 be ingored. 118 5. Acknowledgements 120 The authors would like to thank Mach Chen and Shunwan Zhuang for 121 their comments on this document. 123 6. IANA Considerations 125 The type code of the VPN Address Prefix ORF needs to be assigned by 126 the IANA. 128 7. Security Considerations 130 This document does not introduce any new security considerations. 132 8. References 134 8.1. Normative References 136 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 137 Requirement Levels", BCP 14, RFC 2119, March 1997. 139 [RFC5291] Chen, E. and Y. Rekhter, "Outbound Route Filtering 140 Capability for BGP-4", RFC 5291, August 2008. 142 [RFC5292] Chen, E. and S. Sangli, "Address-Prefix-Based Outbound 143 Route Filter for BGP-4", RFC 5292, August 2008. 145 8.2. Informative References 147 [I-D.xu-l3vpn-virtual-subnet] 148 Building, K., Hares, S., Yongbing, F., Jacquenet, C., 149 Boyes, T., and B. Fee, "Virtual Subnet: A L3VPN-based 150 Subnet Extension Solution", draft-xu-l3vpn-virtual- 151 subnet-02 (work in progress), November 2013. 153 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 154 Networks (VPNs)", RFC 4364, February 2006. 156 Author's Address 158 Xiaohu Xu 159 Huawei 161 Email: xuxiaohu@huawei.com