idnits 2.17.1 draft-retana-sidr-origin-validation-cost-community-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 (October 24, 2014) is 3472 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 (-08) exists of draft-ietf-idr-custom-decision-05 == Outdated reference: A later version (-11) exists of draft-ietf-sidr-origin-validation-signaling-04 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Retana 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Standards Track A. Weher 5 Expires: April 27, 2015 TelVGG 6 October 24, 2014 8 Use of the Cost Community to Propagate BGP Origin Validation State 9 draft-retana-sidr-origin-validation-cost-community-00 11 Abstract 13 This document explains the use of the Cost Community to provide 14 flexibility in the application of routing policy related to the 15 origin validation state of a route. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on April 27, 2015. 34 Copyright Notice 36 Copyright (c) 2014 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 53 3. Use of the Cost Community to Propagate BGP Origin Validation 54 State . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 55 4. Operational Considerations . . . . . . . . . . . . . . . . . 3 56 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 57 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 58 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 59 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 61 8.2. Informative References . . . . . . . . . . . . . . . . . 4 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 64 1. Introduction 66 The BGP Origin Validation mechanism [RFC6811] defines the route 67 validation states as "Valid", "NotFound" and "Invalid". The Origin 68 Validation State Extended Community 69 [I-D.ietf-sidr-origin-validation-signaling] has been defined so that 70 this state can be considered prior to any of the steps defined in the 71 BGP decision process [RFC4271]. 73 It has been suggested that the LOCAL_PREF attribute [RFC4271] may 74 also be used to indicate the degree of preference of a route 75 according to its origin validation state. [RFC7115] also suggests 76 the need to consider the origin validation state at other steps in 77 the selection process, for example after considering the AS_PATH 78 length. 80 The Cost Community [I-D.ietf-idr-custom-decision] can provide a 81 flexible mechanism to propagate the origin validation state, without 82 overloading existing attributes that may already be used to set other 83 types of local policy (such as the LOCAL_PREF). 85 2. Requirements Language 87 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 89 document are to be interpreted as described in [RFC2119]. 91 3. Use of the Cost Community to Propagate BGP Origin Validation State 93 It is RECOMMENDED that the values defined in 94 [I-D.ietf-sidr-origin-validation-signaling] also be used to assign 95 the Cost: 97 +------+------------------+ 98 | Cost | Validation State | 99 +------+------------------+ 100 | 0 | Valid | 101 | 1 | NotFound | 102 | 2 | Invalid | 103 +------+------------------+ 105 Cost vs Validation State 107 The Point of Insertion (POI) can be set to any of the values defined 108 in [I-D.ietf-idr-custom-decision]. Note that the use of the 109 ABSOLUTE_VALUE POI is equivalent to using the Origin Validation State 110 Extended Community. 112 If the Cost Community is used to propagate the origin validation 113 state, then the Origin Validation State Extended Community SHOULD NOT 114 be used. If used, then it will always take precendence over the Cost 115 Community, regardless of the POI used. 117 4. Operational Considerations 119 The use of the origin validation state as part of the BGP decision 120 process is a matter of local policy. 122 The policy mechanism chosen to propagate the origin validation state 123 SHOULD be implemented uniformly across the local autonomous system to 124 guarantee a consistent decision process and reduce the risk of 125 routing loops. 127 5. Security Considerations 129 This document explains the use of the Cost Community to provide 130 flexibility in the application of routing policy related to the 131 origin validation state of a route. As such, it does not introduce 132 new security risks beyond the ones considered in 133 [I-D.ietf-idr-custom-decision] or [RFC6811]. 135 6. IANA Considerations 137 This document has no IANA actions. 139 7. Acknowledgements 141 The authors would like to thank Keyur Patel. 143 8. References 145 8.1. Normative References 147 [I-D.ietf-idr-custom-decision] 148 Retana, A. and R. White, "BGP Custom Decision Process", 149 draft-ietf-idr-custom-decision-05 (work in progress), 150 October 2014. 152 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 153 Requirement Levels", BCP 14, RFC 2119, March 1997. 155 [RFC6811] Mohapatra, P., Scudder, J., Ward, D., Bush, R., and R. 156 Austein, "BGP Prefix Origin Validation", RFC 6811, January 157 2013. 159 8.2. Informative References 161 [I-D.ietf-sidr-origin-validation-signaling] 162 Mohapatra, P., Patel, K., Scudder, J., Ward, D., and R. 163 Bush, "BGP Prefix Origin Validation State Extended 164 Community", draft-ietf-sidr-origin-validation-signaling-04 165 (work in progress), February 2014. 167 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 168 Protocol 4 (BGP-4)", RFC 4271, January 2006. 170 [RFC7115] Bush, R., "Origin Validation Operation Based on the 171 Resource Public Key Infrastructure (RPKI)", BCP 185, RFC 172 7115, January 2014. 174 Authors' Addresses 176 Alvaro Retana 177 Cisco Systems, Inc. 178 7025 Kit Creek Rd. 179 Research Triangle Park, NC 27709 180 USA 182 Email: aretana@cisco.com 183 Ariel Weher 184 Cooperativa Telefonica de Villa Gdor. Galvez Ltda. 185 Av. Mitre 1028 186 Villa Gdor. Galvez, Santa Fe S2124HEB 187 Argentina 189 Email: ariel@weher.net