draft-ietf-sidr-rpki-rtr-protocol-mib-05.txt		draft-ietf-sidr-rpki-rtr-protocol-mib-06.txt
	Network Working Group R. Bush		Network Working Group R. Bush
	Internet-Draft Internet Initiative Japan		Internet-Draft Internet Initiative Japan
	Intended status: Standards Track B. Wijnen		Intended status: Standards Track B. Wijnen
	Expires: August 11, 2013 RIPE NCC		Expires: August 15, 2013 RIPE NCC
	K. Patel		K. Patel
	Cisco Systems		Cisco Systems
	M. Baer		M. Baer
	SPARTA		SPARTA
	February 7, 2013		February 11, 2013
	Definitions of Managed Objects for the RPKI-Router Protocol		Definitions of Managed Objects for the RPKI-Router Protocol
	draft-ietf-sidr-rpki-rtr-protocol-mib-05		draft-ietf-sidr-rpki-rtr-protocol-mib-06
	Abstract		Abstract
	This document defines a portion of the Management Information Base		This document defines a portion of the Management Information Base
	(MIB) for use with network management protocols in the Internet		(MIB) for use with network management protocols in the Internet
	community. In particular, it describes objects used for monitoring		community. In particular, it describes objects used for monitoring
	the RPKI Router protocol.		the RPKI Router protocol.
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 38		skipping to change at page 1, line 38
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on August 11, 2013.		This Internet-Draft will expire on August 15, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 20		skipping to change at page 2, line 20
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
	2. Internet-Standard Management Framework . . . . . . . . . . . . 3		2. Internet-Standard Management Framework . . . . . . . . . . . . 3
	3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4		4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 21		6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22		7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
	7.1. Normative References . . . . . . . . . . . . . . . . . . . 22		7.1. Normative References . . . . . . . . . . . . . . . . . . . 22
	7.2. Informative References . . . . . . . . . . . . . . . . . . 22		7.2. Informative References . . . . . . . . . . . . . . . . . . 23
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
	1. Introduction		1. Introduction
	This document defines a portion of the Management Information Base		This document defines a portion of the Management Information Base
	(MIB) for use with network management protocols in the Internet		(MIB) for use with network management protocols in the Internet
	community. In particular, it defines objects used for monitoring the		community. In particular, it defines objects used for monitoring the
	RPKI Router protocol [RFC6810].		RPKI Router protocol [RFC6810].
	1.1. Requirements Language		1.1. Requirements Language
	skipping to change at page 4, line 5		skipping to change at page 4, line 5
	Servers. It also contains counters for the number of messages		Servers. It also contains counters for the number of messages
	received and sent plus the number of announcements, withdrawals and		received and sent plus the number of announcements, withdrawals and
	active records. The RPKI Router Cache Server Errors Table contains		active records. The RPKI Router Cache Server Errors Table contains
	counters of occurrences of errors on the connections (if any). The		counters of occurrences of errors on the connections (if any). The
	RPKI Router Prefix Origin Table contains IP prefixes with their		RPKI Router Prefix Origin Table contains IP prefixes with their
	minimum and maximum prefix lengths and the Origin AS. This data is		minimum and maximum prefix lengths and the Origin AS. This data is
	the collective set of information received from all RPKI Cache		the collective set of information received from all RPKI Cache
	Servers that the router is connected with. The Cache Servers are		Servers that the router is connected with. The Cache Servers are
	running the RPKI Router protocol.		running the RPKI Router protocol.
	Two Notification have been defined to inform a Network Management		Two Notifications have been defined to inform a Network Management
	Station (NMS) or operators about changes in the connection state of		Station (NMS) or operators about changes in the connection state of
	the connections listed in the RPKI Cache Server (Connection) Table.		the connections listed in the RPKI Cache Server (Connection) Table.
	4. Definitions		4. Definitions
	The Following MIB module imports definitions from [RFC2578], STD 58,		The Following MIB module imports definitions from [RFC2578], STD 58,
	[RFC2579] STD 58, [RFC2580], [RFC4001], [RFC2287]. That means we		[RFC2579] STD 58, [RFC2580], [RFC4001], [RFC2287]. That means we
	have a normative reference to those documents.		have a normative reference to those documents.
	The MIB module also has a normative reference to the RPKI Router		The MIB module also has a normative reference to the RPKI Router
	skipping to change at page 4, line 43		skipping to change at page 4, line 43
	FROM SNMPv2-TC -- RFC2579		FROM SNMPv2-TC -- RFC2579
	MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP		MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
	FROM SNMPv2-CONF -- RFC2580		FROM SNMPv2-CONF -- RFC2580
	LongUtf8String FROM SYSAPPL-MIB -- RFC2287		LongUtf8String FROM SYSAPPL-MIB -- RFC2287
	;		;
	rpkiRtrMIB MODULE-IDENTITY		rpkiRtrMIB MODULE-IDENTITY
	LAST-UPDATED "201302050000Z"		LAST-UPDATED "201302110000Z"
	ORGANIZATION "IETF Secure Inter-Domain Routing (SIDR)		ORGANIZATION "IETF Secure Inter-Domain Routing (SIDR)
	Working Group		Working Group
	"		"
	CONTACT-INFO "Working Group Email: sidr@ietf.org		CONTACT-INFO "Working Group Email: sidr@ietf.org
	Randy Bush		Randy Bush
	Internet Initiative Japan		Internet Initiative Japan
	5147 Crystal Springs		5147 Crystal Springs
	Bainbridge Island, Washington, 98110		Bainbridge Island, Washington, 98110
	USA		USA
	skipping to change at page 6, line 5		skipping to change at page 6, line 5
	license terms contained in, the Simplified BSD		license terms contained in, the Simplified BSD
	License set forth in Section 4.c of the IETF		License set forth in Section 4.c of the IETF
	Trust's Legal Provisions Relating to IETF		Trust's Legal Provisions Relating to IETF
	Documents (http://trustee.ietf.org/license-info).		Documents (http://trustee.ietf.org/license-info).
	This version of this MIB module is part of		This version of this MIB module is part of
	RFCxxxx; see the RFC itself for full legal		RFCxxxx; see the RFC itself for full legal
	notices.		notices.
	"		"
	REVISION "201302050000Z"		REVISION "201302110000Z"
	DESCRIPTION "Initial version, published as RFCxxxx."		DESCRIPTION "Initial version, published as RFCxxxx."
	-- Note to RFC Editor: pls fill in above (2 times) RFC		-- Note to RFC Editor: pls fill in above (2 times) RFC
	-- number for xxxx and delete these 2 lines.		-- number for xxxx and delete these 2 lines.
	::= { mib-2 XXX } -- XXX to be assigned by IANA		::= { mib-2 XXX } -- XXX to be assigned by IANA
	rpkiRtrNotifications OBJECT IDENTIFIER ::= { rpkiRtrMIB 0 }		rpkiRtrNotifications OBJECT IDENTIFIER ::= { rpkiRtrMIB 0 }
	rpkiRtrObjects OBJECT IDENTIFIER ::= { rpkiRtrMIB 1 }		rpkiRtrObjects OBJECT IDENTIFIER ::= { rpkiRtrMIB 1 }
	rpkiRtrConformance OBJECT IDENTIFIER ::= { rpkiRtrMIB 2 }		rpkiRtrConformance OBJECT IDENTIFIER ::= { rpkiRtrMIB 2 }
	-- ==============================================================		-- ==============================================================
	skipping to change at page 7, line 7		skipping to change at page 7, line 7
	-- ==============================================================		-- ==============================================================
	rpkiRtrDiscontinuityTimer OBJECT-TYPE		rpkiRtrDiscontinuityTimer OBJECT-TYPE
	SYNTAX TimeStamp		SYNTAX TimeStamp
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION "This timer represents the timestamp (value		DESCRIPTION "This timer represents the timestamp (value
	of sysUpTime) at which time any of the		of sysUpTime) at which time any of the
	Counter32 objects in this MIB module		Counter32 objects in this MIB module
	encountered a discontinuity.		encountered a discontinuity.
			For objects that use rpkiRtrDiscontinuityTimer to
			indicate discontinuity, only values received since
			the time indicated by rpkiRtrDiscontinuityTimer are
			comparable to each other. A manager should take the
			possibility of rollover into account when
			calculating difference values.
	In principle that should only happen if the		In principle that should only happen if the
	SNMP agent or the instrumentation for this		SNMP agent or the instrumentation for this
	MIB module (re-)starts."		MIB module (re-)starts."
	::= { rpkiRtrObjects 1 }		::= { rpkiRtrObjects 1 }
	-- ==============================================================		-- ==============================================================
	-- RPKI Router Cache Server Connection Table		-- RPKI Router Cache Server Connection Table
	-- ==============================================================		-- ==============================================================
	rpkiRtrCacheServerTable OBJECT-TYPE		rpkiRtrCacheServerTable OBJECT-TYPE
	skipping to change at page 13, line 16		skipping to change at page 13, line 25
	SYNTAX Unsigned32 (1..4294967295)		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION "The unique ID for this connection.		DESCRIPTION "The unique ID for this connection.
	An implementation must make sure this ID is unique		An implementation must make sure this ID is unique
	within this table. It is this ID that can be used		within this table. It is this ID that can be used
	to find entries in the rpkiRtrPrefixOriginTable		to find entries in the rpkiRtrPrefixOriginTable
	that were created by announcements received on this		that were created by announcements received on this
	connection from this cache server."		connection from this cache server."
			REFERENCE "RFC6810 section 4"
	::= { rpkiRtrCacheServerTableEntry 22 }		::= { rpkiRtrCacheServerTableEntry 22 }
	-- ==============================================================		-- ==============================================================
	-- Errors Table		-- Errors Table
	-- ==============================================================		-- ==============================================================
	rpkiRtrCacheServerErrorsTable OBJECT-TYPE		rpkiRtrCacheServerErrorsTable OBJECT-TYPE
	SYNTAX SEQUENCE OF RpkiRtrCacheServerErrorsTableEntry		SYNTAX SEQUENCE OF RpkiRtrCacheServerErrorsTableEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	skipping to change at page 22, line 28		skipping to change at page 22, line 40
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level		[RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level
	Managed Objects for Applications", RFC 2287,		Managed Objects for Applications", RFC 2287,
	February 1998.		February 1998.
	[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,		[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
	"Structure of Management Information Version 2 (SMIv2)",		"Structure of Management Information Version 2 (SMIv2)",
	STD 58, RFC 2578, April 1999.		RFC 2578, April 1999.
	[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,		[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
	"Textual Conventions for SMIv2", STD 58, RFC 2579,		"Textual Conventions for SMIv2", RFC 2579, April 1999.
	April 1999.
	[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,		[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
	"Conformance Statements for SMIv2", STD 58, RFC 2580,		"Conformance Statements for SMIv2", RFC 2580, April 1999.
	April 1999.
	[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.		[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
	Schoenwaelder, "Textual Conventions for Internet Network		Schoenwaelder, "Textual Conventions for Internet Network
	Addresses", RFC 4001, February 2005.		Addresses", RFC 4001, February 2005.
	[RFC6810] Bush, R. and R. Austein, "The Resource Public Key		[RFC6810] Bush, R. and R. Austein, "The Resource Public Key
	Infrastructure (RPKI) to Router Protocol", RFC 6810,		Infrastructure (RPKI) to Router Protocol", RFC 6810,
	January 2013.		January 2013.
	7.2. Informative References		7.2. Informative References
	[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,		[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,
	August 1996.		August 1996.
	[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,		[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
	"Introduction and Applicability Statements for Internet-		"Introduction and Applicability Statements for Internet-
	Standard Management Framework", RFC 3410, December 2002.		Standard Management Framework", RFC 3410, December 2002.
	[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model		[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
	(USM) for version 3 of the Simple Network Management		(USM) for version 3 of the Simple Network Management
	Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.		Protocol (SNMPv3)", RFC 3414, December 2002.
	[RFC3591] Lam, H-K., Stewart, M., and A. Huynh, "Definitions of		[RFC3591] Lam, H-K., Stewart, M., and A. Huynh, "Definitions of
	Managed Objects for the Optical Interface Type", RFC 3591,		Managed Objects for the Optical Interface Type", RFC 3591,
	September 2003.		September 2003.
	[RFC3592] Tesink, K., "Definitions of Managed Objects for the		[RFC3592] Tesink, K., "Definitions of Managed Objects for the
	Synchronous Optical Network/Synchronous Digital Hierarchy		Synchronous Optical Network/Synchronous Digital Hierarchy
	(SONET/SDH) Interface Type", RFC 3592, September 2003.		(SONET/SDH) Interface Type", RFC 3592, September 2003.
	[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using		[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
End of changes. 14 change blocks.
	14 lines changed or deleted		20 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/