Secure Inter-Domain Routing Working R. Bush Group IIJ Internet-Draft B. Wijnen Intended status: Standards Track Lucent Technologies Expires: January 6, 2012 K. Patel Cisco Systems M. Baer SPARTA July 5, 2011 Definitions of Managed Objects for RPKI Router Protocol draft-ymbk-rpki-rtr-protocol-mib-00 Abstract This document defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing the RPKI Router protocol. 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 http://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 January 6, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://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 Bush, et al. Expires January 6, 2012 [Page 1] Internet-Draft MIB Extension for RPKI Router Protocol July 2011 to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Bush, et al. Expires January 6, 2012 [Page 2] Internet-Draft MIB Extension for RPKI Router Protocol July 2011 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 4 2. Internet-Standard Management Framework . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Bush, et al. Expires January 6, 2012 [Page 3] Internet-Draft MIB Extension for RPKI Router Protocol July 2011 1. Introduction This document defines a portion of the BGP4 Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it extends SNMP MIB and defines objects used for managing the RPKI Router protocol. 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. Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This document specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. 3. Overview The objects defined in this document are used to control and manage RPKI Router protocol. The MIB defined in this draft is broken into two tables: the RPKI Router Peer Table, and the RPKI Router Rceived Record Table. The RPKI Router PeerTable contains information about state and current activity of connections with the RPKI Router peers. The RPKI Router Received Record Table contains IP prefixes and its record information received from all peers running RPKI Router protocol. 4. Definitions RPKI-ROUTER-MIB DEFINITIONS ::= BEGIN IMPORTS Bush, et al. Expires January 6, 2012 [Page 4] Internet-Draft MIB Extension for RPKI Router Protocol July 2011 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, Unsigned32, mib-2 FROM SNMPv2-SMI InetAddressType, InetAddress, InetAddressPrefixLength FROM INET-ADDRESS-MIB TEXTUAL-CONVENTION, DateAndTime, TruthValue FROM SNMPv2-TC; rpkiRouter MODULE-IDENTITY LAST-UPDATED "201107010000Z" ORGANIZATION "IETF Secure Inter-Domain Routing Working Group (SIDR)" CONTACT-INFO "N/A" DESCRIPTION "This MIB contains management objects to support the Resource Public Key Infrastructure (RPKI) protocol on routers. Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)." REVISION "201107010000Z" DESCRIPTION "Initial version of RPKI Router MIB." ::= { mib-2 XXX } -- XXX to be assigned by IANA rpkiRouterMIB OBJECT IDENTIFIER ::= { rpkiRouter 1 } rpkiRouterNotifications OBJECT IDENTIFIER ::= { rpkiRouterMIB 0 } rpkiRPeerTable OBJECT-TYPE SYNTAX SEQUENCE OF RpkiRPeerTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the RPKI peers known to this system." Bush, et al. Expires January 6, 2012 [Page 5] Internet-Draft MIB Extension for RPKI Router Protocol July 2011 ::= { rpkiRouterMIB 1 } rpkiRPeerTableEntry OBJECT-TYPE SYNTAX RpkiRPeerTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the rpkiPeerTable. It holds management objects associated with a RPKI Peer." INDEX { rpkiRPTRemoteAddressType, rpkiRPTRemoteAddress, rpkiRPTRemoteAddressPort } ::= { rpkiRPeerTable 1 } RpkiRPeerTableEntry ::= SEQUENCE { rpkiRPTRemoteAddressType InetAddressType, rpkiRPTRemoteAddress InetAddress, rpkiRPTRemoteAddressPort Integer32, rpkiRPTLocalAddressType InetAddressType, rpkiRPTLocalAddress InetAddress, rpkiRPTLocalAddressPort Integer32 } -- XXX needs more objects, see Keyurs email S:first cut, RFC4273 rpkiRPTRemoteAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "The network address type of the remote peer." ::= { rpkiRPeerTableEntry 1 } rpkiRPTRemoteAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The network address of the remote peer." ::= { rpkiRPeerTableEntry 2 } rpkiRPTRemoteAddressPort OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The network address port of the remote peer." ::= { rpkiRPeerTableEntry 3 } Bush, et al. Expires January 6, 2012 [Page 6] Internet-Draft MIB Extension for RPKI Router Protocol July 2011 rpkiRPTLocalAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "The network address type of the local connection to the remote peer." ::= { rpkiRPeerTableEntry 4 } rpkiRPTLocalAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The network address of the local connection to the remote peer." ::= { rpkiRPeerTableEntry 5 } rpkiRPTLocalAddressPort OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The network address port of local connection to the remote peer." ::= { rpkiRPeerTableEntry 6 } END 5. Contributors 6. Acknowledgements 7. IANA Considerations 8. Security Considerations 9. References Bush, et al. Expires January 6, 2012 [Page 7] Internet-Draft MIB Extension for RPKI Router Protocol July 2011 9.1. Normative References [I-D.ietf-sidr-rpki-rtr] Bush, R. and R. Austein, "The RPKI/Router Protocol", draft-ietf-sidr-rpki-rtr-13 (work in progress), June 2011. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2842] Chandra, R. and J. Scudder, "Capabilities Advertisement with BGP-4", RFC 2842, May 2000. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. 9.2. Informative References [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006. Authors' Addresses Randy Bush IIJ 5147 Crystal Springs Bainbridge Island, Washington 98110 USA Email: randy@psg.com Bush, et al. Expires January 6, 2012 [Page 8] Internet-Draft MIB Extension for RPKI Router Protocol July 2011 Bert Wijnen Lucent Technologies Schagen 33 3461 GL Linschoten Netherlands Email: bwijnen@lucent.com Keyur Patel Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 USA Email: keyupate@cisco.com Michael Baer SPARTA P.O. Box 72682 Davis, CA 95617 USA Email: michael.baer@sparta.com Bush, et al. Expires January 6, 2012 [Page 9]