Diff: draft-ietf-ion-nhrp-mib-08.txt - draft-ietf-ion-nhrp-mib-09.txt

	< draft-ietf-ion-nhrp-mib-08.txt	draft-ietf-ion-nhrp-mib-09.txt >


	Definitions of Managed Objects for	Definitions of Managed Objects for
	the NBMA Next Hop Resolution Protocol (NHRP)	the NBMA Next Hop Resolution Protocol (NHRP)

	May 1999	May 1999


	<draft-ietf-ion-nhrp-mib-08.txt>	<draft-ietf-ion-nhrp-mib-09.txt>

	Maria Greene Joan Cucchiara James V. Luciani	Maria Greene Joan Cucchiara James V. Luciani
	Contractor IronBridge Networks Bay Networks	Contractor IronBridge Networks Bay Networks
	maria@xedia.com joan@ironbridgenetworks.com luciani@baynetworks.com	maria@xedia.com joan@ironbridgenetworks.com luciani@baynetworks.com

	Status of this Memo	Status of this Memo

	This document is an Internet-Draft and is in full conformance with	This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC 2026. Internet-Drafts are	all provisions of Section 10 of RFC 2026. Internet-Drafts are
	working documents of the Internet Engineering Task Force (IETF), its	working documents of the Internet Engineering Task Force (IETF), its

	skipping to change at page 4, line 41 ¶	skipping to change at page 4, line 41 ¶

	3.1.1. The NHRP Cache Table	3.1.1. The NHRP Cache Table

	The NHRP Cache Table represents the internetwork layer address to	The NHRP Cache Table represents the internetwork layer address to
	NBMA address cache that is maintained by both NHRP clients and NHRP	NBMA address cache that is maintained by both NHRP clients and NHRP
	servers.	servers.

	The NHRP Cache Table contains an ifIndex as part of the Index Clause.	The NHRP Cache Table contains an ifIndex as part of the Index Clause.
	This ifIndex represents the use of a generic ifIndex, such that the	This ifIndex represents the use of a generic ifIndex, such that the
	value of this ifIndex SHOULD reflect a specific NBMA subnetwork	value of this ifIndex SHOULD reflect a specific NBMA subnetwork

	related interface as determined by an implementation. For example,	related interface as determined by an implementation. For example,
	assuming that the NBMA subnetwork is ATM, then it is up to the	assuming that the NBMA subnetwork is ATM, then it is up to the
	implementors of this MIB to determine their own ATM interface	implementors of this MIB to determine their own ATM interface
	layering (assuming compliance with the IF-MIB, RFC 2233 [18] and the	layering (assuming compliance with the IF-MIB, RFC 2233 [18] and the
	ATM-MIB, RFC 2515 [19]). In other words, assuming that the NBMA	ATM-MIB, RFC 2515 [19]). In other words, assuming that the NBMA
	subnetwork is ATM, the ifIndex in the NHRP Cache Table would	subnetwork is ATM, the ifIndex in the NHRP Cache Table would
	represent the ifIndex containing or consisting of the VC (or	represent the ifIndex containing or consisting of the VC (or
	shortcut) denoted by this Table entry.	shortcut) denoted by this Table entry.

	The indexing scheme for the NHRP Cache Table is very similar to the	The indexing scheme for the NHRP Cache Table is very similar to the
	MPC Ingress Cache Table and the MPS Ingress Cache Table in the	MPC Ingress Cache Table and the MPS Ingress Cache Table in the

	skipping to change at page 7, line 4 ¶	skipping to change at page 7, line 4 ¶
	The NHRP Server Statistics Table contains NHRP statistics maintained	The NHRP Server Statistics Table contains NHRP statistics maintained
	by a server. These statistics include counters on requests and	by a server. These statistics include counters on requests and
	replies, as well as counters for errors which are encountered by the	replies, as well as counters for errors which are encountered by the
	Servers.	Servers.

	4. NBMA Next Hop Resolution Protocol MIB Definitions	4. NBMA Next Hop Resolution Protocol MIB Definitions

	NHRP-MIB DEFINITIONS ::= BEGIN	NHRP-MIB DEFINITIONS ::= BEGIN

	IMPORTS	IMPORTS

	OBJECT-TYPE, MODULE-IDENTITY, experimental, Integer32,	OBJECT-TYPE, MODULE-IDENTITY, mib-2, Integer32,
	Counter32, Unsigned32	Counter32, Unsigned32
	FROM SNMPv2-SMI	FROM SNMPv2-SMI
	MODULE-COMPLIANCE, OBJECT-GROUP	MODULE-COMPLIANCE, OBJECT-GROUP
	FROM SNMPv2-CONF	FROM SNMPv2-CONF
	TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,	TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,
	TimeStamp	TimeStamp
	FROM SNMPv2-TC	FROM SNMPv2-TC
	ifIndex	ifIndex
	FROM IF-MIB	FROM IF-MIB
	AddressFamilyNumbers	AddressFamilyNumbers

	skipping to change at page 7, line 33 ¶	skipping to change at page 7, line 33 ¶
	Contractor	Contractor

	Joan Cucchiara (joan@ironbridgenetworks.com)	Joan Cucchiara (joan@ironbridgenetworks.com)
	IronBridge Networks	IronBridge Networks

	James V. Luciani (luciani@baynetworks.com)	James V. Luciani (luciani@baynetworks.com)
	Bay Networks"	Bay Networks"
	DESCRIPTION	DESCRIPTION
	"This MIB contains managed object definitions for the Next	"This MIB contains managed object definitions for the Next
	Hop Resolution Procol, NHRP, as defined in RFC 2332 [17]."	Hop Resolution Procol, NHRP, as defined in RFC 2332 [17]."

	::= { experimental XXX } -- to be assigned
		-- revision history

		REVISION "9905191200Z" -- May 19, 1999
		-- RFC-Editor assigns RFC xxxx
		DESCRIPTION "Initial version, published as RFC xxxx."

		::= { mib-2 XXX } -- to be assigned by IANA

	--****************************************************************	--****************************************************************
	-- NHRP Textual Conventions	-- NHRP Textual Conventions
	--****************************************************************	--****************************************************************

	NhrpGenAddr ::= TEXTUAL-CONVENTION	NhrpGenAddr ::= TEXTUAL-CONVENTION
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"The value of an internetwork layer or NBMA address."	"The value of an internetwork layer or NBMA address."
	SYNTAX OCTET STRING (SIZE (0..64))	SYNTAX OCTET STRING (SIZE (0..64))

	skipping to change at page 59, line 10 ¶	skipping to change at page 59, line 10 ¶
	"Objects that apply only to NHRP servers."	"Objects that apply only to NHRP servers."
	::= { nhrpGroups 3 }	::= { nhrpGroups 3 }

	END	END

	5. IANA Considerations	5. IANA Considerations

	The Internet Assigned Numbers Authority (IANA) has been and continues	The Internet Assigned Numbers Authority (IANA) has been and continues
	to be responsible for maintaining the ADDRESS FAMILY NUMBERS	to be responsible for maintaining the ADDRESS FAMILY NUMBERS
	(http://www.isi.edu/in-notes/iana/assignments/address-family-numbers)	(http://www.isi.edu/in-notes/iana/assignments/address-family-numbers)

	name space assignments. The request made here is for the IANA to	name space assignments. The request made here is for the IANA to
	place this list in a MIB module, such that it may be imported into	place this list in a MIB module, such that it may be imported into
	other MIBs. The motivation for doing this is to allow MIBs to not	other MIBs. The motivation for doing this is to allow MIBs to not
	have to change when a new assignment is made to the ADDRESS FAMILY	have to change when a new assignment is made to the ADDRESS FAMILY
	NUMBERS. This is very similar to the motivation behind the	NUMBERS. This is very similar to the motivation behind the
	IANAifType-MIB.	IANAifType-MIB.

	An example of what the MIB would look like is included in this	An example of what the MIB would look like is included in this
	document.	document.

	Any additions or changes to the list of ADDRESS FAMILY NUMBERS	Any additions or changes to the list of ADDRESS FAMILY NUMBERS

	skipping to change at page 65, line 5 ¶	skipping to change at page 65, line 5 ¶
	[20] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA	[20] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA
	Considerations Section in RFCs.", BCP 26, RFC 2434, IBM, Maxware,	Considerations Section in RFCs.", BCP 26, RFC 2434, IBM, Maxware,
	October 1998	October 1998

	[21] Bradner, S., "Key words for use in RFCs to Indicate Requirement	[21] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, Harvard University, March 1997	Levels", BCP 14, RFC 2119, Harvard University, March 1997

	[22] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9,	[22] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9,
	RFC 2026, Harvard University, October 1996	RFC 2026, Harvard University, October 1996


	[23] Cucchiara, J., editor, "Mulitprotocol Over ATM Version 1.0 MIB",	[23] Cucchiara, J., editor, "Multiprotocol Over ATM Version 1.0 MIB",
	af-mpoa-0092.000, ATM Forum, July 1998	af-mpoa-0092.000, ATM Forum, July 1998


	[24] Fredette, A., editor, "Mulitprotocol Over ATM Version 1.0", af-	[24] Fredette, A., editor, "Multiprotocol Over ATM Version 1.0", af-
	mpoa-0087.000, ATM Forum, May 1997	mpoa-0087.000, ATM Forum, May 1997

	[25] Laubach, M., and J. Halpern, "Classical IP and ARP over ATM", RFC	[25] Laubach, M., and J. Halpern, "Classical IP and ARP over ATM", RFC
	2225, Com21, Newbridge Networks, April 1998	2225, Com21, Newbridge Networks, April 1998

	[26] Greene, M., J. Luciani, K. White, and T. Kuo, "Definitions of	[26] Greene, M., J. Luciani, K. White, and T. Kuo, "Definitions of
	Managed Objects for Classical IP and ARP Over ATM Using SMIv2", RFC	Managed Objects for Classical IP and ARP Over ATM Using SMIv2", RFC
	2320, Xedia, Bay Networks, April 1998	2320, Xedia, Bay Networks, April 1998

	10. Authors' Addresses	10. Authors' Addresses

	skipping to change at page 67, line 14 ¶	skipping to change at page 67, line 14 ¶

	This document and the information contained herein is provided on an	This document and the information contained herein is provided on an
	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
	HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF	HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

	12. IANA Address Family Numbers MIB	12. IANA Address Family Numbers MIB


	This appendix defines the initial content of the IANA-ADDRESS-	This appendix defines the initial content of the IANA-ADDRESS-FAMILY-
	FAMILY-NUMBERS-MIB. This section should be removed from this	NUMBERS-MIB. This section should be removed from this document prior
	document prior to its approval, at which time this MIB will be	to its approval, at which time this MIB will be administered by IANA.
	administered by IANA.

	The branch for this MIB needs to be determined, and an appropriate	The branch for this MIB needs to be determined, and an appropriate
	number should be added where XXX is currently.	number should be added where XXX is currently.

	IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS ::= BEGIN	IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS ::= BEGIN

	IMPORTS	IMPORTS
	MODULE-IDENTITY,	MODULE-IDENTITY,
	mib-2 FROM SNMPv2-SMI	mib-2 FROM SNMPv2-SMI
	TEXTUAL-CONVENTION FROM SNMPv2-TC;	TEXTUAL-CONVENTION FROM SNMPv2-TC;

	ianaAddressFamilyNumbers MODULE-IDENTITY	ianaAddressFamilyNumbers MODULE-IDENTITY

	LAST-UPDATED "9905191200Z"	LAST-UPDATED "9905191200Z" -- May 19, 1999
	ORGANIZATION "IANA"	ORGANIZATION "IANA"
	CONTACT-INFO	CONTACT-INFO
	"Postal: Internet Assigned Numbers Authority	"Postal: Internet Assigned Numbers Authority
	USC/Information Sciences Institute	USC/Information Sciences Institute
	4676 Admiralty Way	4676 Admiralty Way
	Marina del Rey, CA 90292-6695	Marina del Rey, CA 90292-6695
	USA	USA

	Tel: +1 310-822-1511	Tel: +1 310-822-1511
	E-Mail: iana@isi.edu"	E-Mail: iana@isi.edu"
	DESCRIPTION	DESCRIPTION
	"The MIB module defines the AddressFamilyNumbers	"The MIB module defines the AddressFamilyNumbers
	textual convention."	textual convention."

	::= { mib-2 XXX } -- to be assigned
		-- revision history

		REVISION "9905191200Z" -- May 19, 1999
		-- RFC-Editor assigns RFC xxxx
		DESCRIPTION "Initial version, published as RFC xxxx."

		::= { mib-2 XXX } -- to be assigned by IANA

	AddressFamilyNumbers ::= TEXTUAL-CONVENTION	AddressFamilyNumbers ::= TEXTUAL-CONVENTION
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"The definition of this textual convention with the	"The definition of this textual convention with the
	addition of newly assigned values is published	addition of newly assigned values is published
	periodically by the IANA, in either the Assigned	periodically by the IANA, in either the Assigned
	Numbers RFC, or some derivative of it specific to	Numbers RFC, or some derivative of it specific to
	Internet Network Management number assignments.	Internet Network Management number assignments.
	(The latest arrangements can be obtained by	(The latest arrangements can be obtained by

End of changes. 11 change blocks.
	13 lines changed or deleted	27 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/