idnits 2.17.1 draft-ymbk-bgp-origin-validation-mib-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 4, 2011) is 4652 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) == Unused Reference: 'I-D.ietf-sidr-pfx-validate' is defined on line 243, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 252, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 256, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 260, but no explicit reference was found in the text == Unused Reference: 'RFC2842' is defined on line 264, but no explicit reference was found in the text == Unused Reference: 'RFC3410' is defined on line 267, but no explicit reference was found in the text == Unused Reference: 'RFC4271' is defined on line 276, but no explicit reference was found in the text == Outdated reference: A later version (-10) exists of draft-ietf-sidr-pfx-validate-01 ** Obsolete normative reference: RFC 2842 (Obsoleted by RFC 3392) ** Downref: Normative reference to an Informational RFC: RFC 3410 Summary: 2 errors (**), 0 flaws (~~), 11 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Secure Inter-Domain Routing Working R. Bush 3 Group Internet Initiative Japan 4 Internet-Draft B. Wijnen 5 Intended status: Standards Track RIPE/NCC 6 Expires: January 5, 2012 K. Patel 7 Cisco Systems 8 M. Baer 9 SPARTA 10 July 4, 2011 12 Definitions of Managed Objects for BGP Origin Validation 13 draft-ymbk-bgp-origin-validation-mib-00 15 Abstract 17 This document extends the current Management Information Base (MIB) 18 defined for BGP in RFC 4273 to provide support for BGP Origin 19 Validation. In particular, it describes manage objects used for 20 managing BGP Origin validation state within BGP protocol. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on January 5, 2012. 39 Copyright Notice 41 Copyright (c) 2011 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 This document may contain material from IETF Documents or IETF 55 Contributions published or made publicly available before November 56 10, 2008. The person(s) controlling the copyright in some of this 57 material may not have granted the IETF Trust the right to allow 58 modifications of such material outside the IETF Standards Process. 59 Without obtaining an adequate license from the person(s) controlling 60 the copyright in such materials, this document may not be modified 61 outside the IETF Standards Process, and derivative works of it may 62 not be created outside the IETF Standards Process, except to format 63 it for publication as an RFC or to translate it into languages other 64 than English. 66 Table of Contents 68 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 4 70 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 4. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 7 73 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 74 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 75 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 76 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 77 8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 78 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 81 1. Introduction 83 This document extends a portion of the BGP4 Management Information 84 Base (MIB) for use with network management protocols in the Internet 85 community. In particular, it describes managed objects used for 86 managing BGP Origin validation within BGP protocol. 88 1.1. Requirements Language 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 92 document are to be interpreted as described in RFC 2119 [RFC2119]. 94 2. Overview 96 3. Definitions 98 BGP-ORIG-VAL-MIB DEFINITIONS ::= BEGIN 100 IMPORTS 102 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, 103 Unsigned32, mib-2 104 FROM SNMPv2-SMI 106 InetAddressType, InetAddress, InetAddressPrefixLength 107 FROM INET-ADDRESS-MIB 109 TEXTUAL-CONVENTION, DateAndTime, TruthValue 110 FROM SNMPv2-TC; 112 bgpOrigVal MODULE-IDENTITY 113 LAST-UPDATED "201106280000Z" 115 ORGANIZATION "IETF Secure Inter-Domain Routing Working Group 116 (SIDR)" 117 CONTACT-INFO "N/A" 119 DESCRIPTION "This MIB contains management objects to support 120 the Border Gateway Protocol's (BGP) Origin 121 Validation. 123 Copyright (c) 2011 IETF Trust and the persons 124 identified as authors of the code. All rights 125 reserved. 127 Redistribution and use in source and binary forms, 128 with or without modification, is permitted pursuant 129 to, and subject to the license terms contained in, 130 the Simplified BSD License set forth in Section 4.c 131 of the IETF Trust's Legal Provisions Relating to 132 IETF Documents 133 (http://trustee.ietf.org/license-info)." 135 REVISION "201106280000Z" 136 DESCRIPTION "Initial version of BGP Origin Validation MIB." 138 ::= { mib-2 XXX } -- XXX to be assigned by IANA 140 bgpValMIB OBJECT IDENTIFIER ::= { bgpOrigVal 1 } 141 bgpValNotifications OBJECT IDENTIFIER ::= { bgpValMIB 0 } 142 bgpValGen OBJECT IDENTIFIER ::= { bgpValMIB 1 } 143 bgpValROA OBJECT IDENTIFIER ::= { bgpValMIB 2 } 144 bgpValRPKI OBJECT IDENTIFIER ::= { bgpValMIB 3 } 145 bgpValPFX OBJECT IDENTIFIER ::= { bgpValMIB 4 } 146 bgpValGhost OBJECT IDENTIFIER ::= { bgpValMIB 5 } 147 bgpValRepos OBJECT IDENTIFIER ::= { bgpValMIB 6 } 149 bgpValROATable OBJECT-TYPE 150 SYNTAX SEQUENCE OF BgpValROATableEntry 151 MAX-ACCESS not-accessible 152 STATUS current 153 DESCRIPTION 154 "This table lists the ROAs on this system." 155 ::= { bgpValROA 1 } 157 bgpValROATableEntry OBJECT-TYPE 158 SYNTAX BgpValROATableEntry 159 MAX-ACCESS not-accessible 160 STATUS current 161 DESCRIPTION 162 "An entry in the bgpValROATable." 163 INDEX { bgpVRTasNum } 164 ::= { bgpValROATable 1 } 166 BgpValROATableEntry ::= SEQUENCE { 167 bgpVRTasNum Unsigned32, 168 bgpVRTPrefixType InetAddressType, 169 bgpVRTPrefix InetAddress, 170 bgpVRTPrefixLength InetAddressPrefixLength, 171 bgpVRTValid INTEGER 173 } 175 bgpVRTasNum OBJECT-TYPE 176 SYNTAX Unsigned32 177 MAX-ACCESS not-accessible 178 STATUS current 179 DESCRIPTION 180 "This value represents the AS number for this row in the 181 table." 182 ::= { bgpValROATableEntry 1 } 184 bgpVRTPrefixType OBJECT-TYPE 185 SYNTAX InetAddressType 186 MAX-ACCESS read-create 187 STATUS current 188 DESCRIPTION 189 "This is the address type of the prefix in this row." 190 ::= { bgpValROATableEntry 2 } 192 bgpVRTPrefix OBJECT-TYPE 193 SYNTAX InetAddress 194 MAX-ACCESS read-create 195 STATUS current 196 DESCRIPTION 197 "This is the prefix of the ROA indicated by this row." 198 ::= { bgpValROATableEntry 3 } 200 bgpVRTPrefixLength OBJECT-TYPE 201 SYNTAX InetAddressPrefixLength 202 MAX-ACCESS read-create 203 STATUS current 204 DESCRIPTION 205 "This is the length of the prefix for the ROA." 206 ::= { bgpValROATableEntry 4 } 208 bgpVRTValid OBJECT-TYPE 209 SYNTAX INTEGER { unknown(1), valid(2), invalid(3) } 210 MAX-ACCESS read-create 211 STATUS current 212 DESCRIPTION 213 "This is indicates if the state of the roa associated with 214 this row." 215 DEFVAL { unknown } 216 ::= { bgpValROATableEntry 5 } 218 END 220 4. Contributors 222 5. Acknowledgements 224 6. IANA Considerations 226 The MIB module in this document will required an IANA assigned OBJECT 227 IDENTIFIER within the SMI Numbers registry. For example, replacing 228 XXX below: 230 Descriptor OBJECT IDENTIFIER value 231 ---------- ----------------------- 232 bgpOrigVal { mib-2 XXX } 234 7. Security Considerations 236 This extension to [RFC4273] does not change the underlying security 237 issues inherent in the existing BGP and [RFC4273]. 239 8. References 241 8.1. Normative References 243 [I-D.ietf-sidr-pfx-validate] 244 Mohapatra, P., Scudder, J., Ward, D., Bush, R., and R. 245 Austein, "BGP Prefix Origin Validation", 246 draft-ietf-sidr-pfx-validate-01 (work in progress), 247 February 2011. 249 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 250 Requirement Levels", BCP 14, RFC 2119, March 1997. 252 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 253 Schoenwaelder, Ed., "Structure of Management Information 254 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 256 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 257 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 258 STD 58, RFC 2579, April 1999. 260 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 261 "Conformance Statements for SMIv2", STD 58, RFC 2580, 262 April 1999. 264 [RFC2842] Chandra, R. and J. Scudder, "Capabilities Advertisement 265 with BGP-4", RFC 2842, May 2000. 267 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 268 "Introduction and Applicability Statements for Internet- 269 Standard Management Framework", RFC 3410, December 2002. 271 [RFC4273] Haas, J. and S. Hares, "Definitions of Managed Objects for 272 BGP-4", RFC 4273, January 2006. 274 8.2. Informative References 276 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 277 Protocol 4 (BGP-4)", RFC 4271, January 2006. 279 Authors' Addresses 281 Randy Bush 282 Internet Initiative Japan 283 5147 Crystal Springs 284 Bainbridge Island, Washington 98110 285 US 287 Phone: +1 206 780 0431 x1 288 Email: randy@psg.com 290 Bert Wijnen 291 RIPE/NCC 292 Schagen 33 293 3461 GL Linschoten 294 Netherlands 296 Email: bwijnen@bwijnen.net 298 Keyur Patel 299 Cisco Systems 300 170 W. Tasman Drive 301 San Jose, CA 95134 302 USA 304 Email: keyupate@cisco.com 305 Michael Baer 306 SPARTA 307 P.O. Box 72682 308 Davis, CA 95617 309 USA 311 Email: michael.baer@sparta.com