draft-ietf-manet-dymo-mib-00.txt   draft-ietf-manet-dymo-mib-01.txt 
Internet Engineering Task Force S. Harnedy, Ed. Internet Engineering Task Force S. Harnedy, Ed.
Internet-Draft Booze Allen Hamilton Internet-Draft Booze Allen Hamilton
Intended status: Standards Track R. Cole Intended status: Standards Track R. Cole
Expires: November 16, 2008 Johns Hopkins University Expires: May 7, 2009 Johns Hopkins University
I. Chakeres I. Chakeres
Motorola CenGen
May 15, 2008 November 3, 2008
Definition of Managed Objects for the DYMO Manet Routing Protocol Definition of Managed Objects for the DYMO Manet Routing Protocol
draft-ietf-manet-dymo-mib-00 draft-ietf-manet-dymo-mib-01
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 16, 2008. This Internet-Draft will expire on May 7, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the In particular, it describes objects for configuring aspects of the
skipping to change at page 2, line 29 skipping to change at page 2, line 29
5.3.1. Peers Table . . . . . . . . . . . . . . . . . . . . . 6 5.3.1. Peers Table . . . . . . . . . . . . . . . . . . . . . 6
5.3.2. Routing Table . . . . . . . . . . . . . . . . . . . . 6 5.3.2. Routing Table . . . . . . . . . . . . . . . . . . . . 6
5.4. The Statistics Group . . . . . . . . . . . . . . . . . . . 6 5.4. The Statistics Group . . . . . . . . . . . . . . . . . . . 6
5.5. The Notifications Group . . . . . . . . . . . . . . . . . 7 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 7
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7
6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7
6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 29 8. Security Considerations . . . . . . . . . . . . . . . . . . . 29
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 31 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 32
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
12.1. Normative References . . . . . . . . . . . . . . . . . . . 31 12.1. Normative References . . . . . . . . . . . . . . . . . . . 32
12.2. Informative References . . . . . . . . . . . . . . . . . . 32 12.2. Informative References . . . . . . . . . . . . . . . . . . 33
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 32 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 33
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 32 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of a In particular, it describes objects for configuring aspects of a
Dynamic MANET On-demand (DYMO) routing [I-D.ietf-manet-dymo] process. Dynamic MANET On-demand (DYMO) routing [I-D.ietf-manet-dymo] process.
The DYMO MIB also reports state information, performance metrics, and The DYMO MIB also reports state information, performance metrics, and
notifications. In addition to configuration, this additional state notifications. In addition to configuration, this additional state
and performance information is useful to management stations and performance information is useful to management stations
skipping to change at page 8, line 42 skipping to change at page 8, line 42
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetAddressPrefixLength InetAddressPrefixLength
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
InterfaceIndex InterfaceIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
; ;
manetDymoMIB MODULE-IDENTITY manetDymoMIB MODULE-IDENTITY
LAST-UPDATED "200805141200Z" -- May 14, 2008 LAST-UPDATED "200811031200Z" -- November 03, 2008
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Sean Harnedy Editors: Sean Harnedy
Booz Allen Hamilton Booz Allen Hamilton
333 City Boulevard West 333 City Boulevard West
skipping to change at page 9, line 41 skipping to change at page 9, line 41
the Dynamic MANET On-demand (DYMO) routing protocol as the Dynamic MANET On-demand (DYMO) routing protocol as
defined in: Charkeres,I., and C. Perkins, Dynamic MANET defined in: Charkeres,I., and C. Perkins, Dynamic MANET
On-demand (DYMO) Routing, draft-ietf-manet-dymo-13, On-demand (DYMO) Routing, draft-ietf-manet-dymo-13,
April 10, 2008. April 10, 2008.
Copyright (C) The IETF Trust (2008). This version Copyright (C) The IETF Trust (2008). This version
of this MIB module is part of RFC xxxx; see the RFC of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices." itself for full legal notices."
-- Revision History -- Revision History
REVISION "200811031200Z" -- November 03, 2008
DESCRIPTION
"Second draft of this MIB module published as
draft-ietf-manet-dymo-mib-01.txt. Minor changes to
dymoInterfacesTable and dymoResponsibleAddrTable."
REVISION "200805141200Z" -- May 14, 2008 REVISION "200805141200Z" -- May 14, 2008
DESCRIPTION DESCRIPTION
"Initial draft of this MIB module published as "Initial draft of this MIB module published as
draft-ietf-manet-dymo-mib-00.txt." draft-ietf-manet-dymo-mib-00.txt."
-- RFC-Editor assigns XXXX -- RFC-Editor assigns XXXX
::= { mib-2 999 } -- to be assigned by IANA ::= { mib-2 999 } -- to be assigned by IANA
-- --
-- TEXTUAL CONVENTIONs -- TEXTUAL CONVENTIONs
-- --
-- Note: Need to determine the appropriate set of states
-- for the DymoInterfacesOperStatus textual convention.
DymoInterfaceOperStatus ::= TEXTUAL-CONVENTION DymoInterfaceOperStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational status of the "The current operational status of the
DYMO interface." DYMO interface."
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
down(2), down(2),
waiting(3), waiting(3),
loopback(4), loopback(4),
skipping to change at page 14, line 27 skipping to change at page 14, line 36
"The DYMO interface entry describes one DYMO "The DYMO interface entry describes one DYMO
interface as indexed by its ifIndex." interface as indexed by its ifIndex."
INDEX { dymoIfIndex } INDEX { dymoIfIndex }
::= { dymoInterfaceTable 1 } ::= { dymoInterfaceTable 1 }
DymoInterfaceEntry ::= DymoInterfaceEntry ::=
SEQUENCE { SEQUENCE {
dymoIfIndex dymoIfIndex
InterfaceIndex, InterfaceIndex,
dymoIfOperStatus dymoIfOperStatus
DymoInterfaceOperStatus DymoInterfaceOperStatus,
dymoIfRowStatus
RowStatus
} }
dymoIfIndex OBJECT-TYPE dymoIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex for this DYMO interface." "The ifIndex for this DYMO interface."
::= { dymoInterfaceEntry 1 } ::= { dymoInterfaceEntry 1 }
dymoIfOperStatus OBJECT-TYPE dymoIfOperStatus OBJECT-TYPE
SYNTAX DymoInterfaceOperStatus SYNTAX DymoInterfaceOperStatus
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational status of this "The current operational status of this
DYMO interface. The default value is DYMO interface. The default value is
down(2)." down(2)."
::= { dymoInterfaceEntry 2 } ::= { dymoInterfaceEntry 2 }
dymoIfRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object permits management of the table
by facilitating actions such as row creation,
construction, and destruction. The value of
this object has no effect on whether other
objects in this conceptual row can be
modified."
::= { dymoInterfaceEntry 3 }
-- --
-- DYMO Responsible Address Table -- DYMO Responsible Address Table
-- --
dymoResponsibleAddrTable OBJECT-TYPE dymoResponsibleAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF DymoResponsibleAddrEntry SYNTAX SEQUENCE OF DymoResponsibleAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS current
DESCRIPTION DESCRIPTION
"The DYMO Responsible Address Table is a "The DYMO Responsible Address Table is a
list of IP address prefixes, and their list of IP address prefixes, and their
associated prefix length for which the associated prefix length for which the
DYMO router is responsible." DYMO router is responsible."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, April 2008. Table 3 Important
Settings." Settings."
::= { dymoConfigurationGroup 3 } ::= { dymoConfigurationGroup 3 }
skipping to change at page 15, line 32 skipping to change at page 16, line 9
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A single host address range. Information "A single host address range. Information
in this table is persistent and when this object in this table is persistent and when this object
is written, the entity SHOULD save the change to is written, the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, April 2008. Table 3 Important
Settings." Settings."
INDEX { dymoResponsibleAddrType, INDEX { dymoResponsibleAddrIndex }
dymoResponsibleAddr,
dymoResponsibleAddrPrefixLen }
::= { dymoResponsibleAddrTable 1 } ::= { dymoResponsibleAddrTable 1 }
DymoResponsibleAddrEntry ::= DymoResponsibleAddrEntry ::=
SEQUENCE { SEQUENCE {
dymoResponsibleAddrIndex
Unsigned32,
dymoResponsibleAddrType dymoResponsibleAddrType
InetAddressType, InetAddressType,
dymoResponsibleAddr dymoResponsibleAddr
InetAddress, InetAddress,
dymoResponsibleAddrPrefixLen dymoResponsibleAddrPrefixLen
InetAddressPrefixLength, InetAddressPrefixLength,
dymoResponsibleAddrRowStatus dymoResponsibleAddrRowStatus
RowStatus RowStatus
} }
dymoResponsibleAddrIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is the index into this table."
::= { dymoResponsibleAddrEntry 1 }
dymoResponsibleAddrType OBJECT-TYPE dymoResponsibleAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the dymoResponsibleAddr, as defined "The type of the dymoResponsibleAddr, as defined
in the InetAddress MIB [RFC 4001]." in the InetAddress MIB [RFC 4001]."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, April 2008. Table 3 Important
Settings." Settings."
::= { dymoResponsibleAddrEntry 1 } ::= { dymoResponsibleAddrEntry 2 }
dymoResponsibleAddr OBJECT-TYPE dymoResponsibleAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination IP address of this route. The type "The destination IP address of this route. The type
of this address is determined by the value of the of this address is determined by the value of the
dymoResponsibleAddrType object." dymoResponsibleAddrType object."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, April 2008. Table 3 Important
Settings." Settings."
::= { dymoResponsibleAddrEntry 2 } ::= { dymoResponsibleAddrEntry 3 }
dymoResponsibleAddrPrefixLen OBJECT-TYPE dymoResponsibleAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of leading one bits that form the "Indicates the number of leading one bits that form the
mask to be logical-ANDed with the destination address mask to be logical-ANDed with the destination address
before being compared to the value in the dymoResonsibleAddr before being compared to the value in the dymoResonsibleAddr
field." field."
REFERENCE REFERENCE
"Dynamic MANET On-demand (DYMO) Routing, Chakeres, "Dynamic MANET On-demand (DYMO) Routing, Chakeres,
I., and C. Perkins, April 2008. Table 3 Important I., and C. Perkins, April 2008. Table 3 Important
Settings." Settings."
::= { dymoResponsibleAddrEntry 3 } ::= { dymoResponsibleAddrEntry 4 }
dymoResponsibleAddrRowStatus OBJECT-TYPE dymoResponsibleAddrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object permits management of the table "This object permits management of the table
by facilitating actions such as row creation, by facilitating actions such as row creation,
construction, and destruction. The value of construction, and destruction. The value of
this object has no effect on whether other this object has no effect on whether other
objects in this conceptual row can be objects in this conceptual row can be
modified." modified."
::= { dymoResponsibleAddrEntry 4 } ::= { dymoResponsibleAddrEntry 5 }
-- --
-- dymoStateGroup -- dymoStateGroup
-- --
-- Contains information describing the current state of the DYMO -- Contains information describing the current state of the DYMO
-- process such as the DYMO routing table. -- process such as the DYMO routing table.
-- --
dymoStateGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 2 } dymoStateGroup OBJECT IDENTIFIER ::= { dymoMIBObjects 2 }
skipping to change at page 32, line 21 skipping to change at page 33, line 7
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for Schoenwaelder, Ed., "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2580] McCloghrie, K., Perkins, D., and J.
Schoenwaelder, "Conformance Statements for Schoenwaelder, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[I-D.ietf-manet-dymo] Chakeres, I. and C. Perkins, "Dynamic MANET [I-D.ietf-manet-dymo] Chakeres, I. and C. Perkins, "Dynamic MANET
On-demand (DYMO) Routing", On-demand (DYMO) Routing",
draft-ietf-manet-dymo-13 (work in progress), draft-ietf-manet-dymo-14 (work in progress),
April 2008. June 2008.
12.2. Informative References 12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. [RFC3410] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction and Applicability Stewart, "Introduction and Applicability
Statements for Internet-Standard Management Statements for Internet-Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
Appendix A. Change Log Appendix A. Change Log
skipping to change at page 34, line 25 skipping to change at page 35, line 4
Robert G. Cole Robert G. Cole
Johns Hopkins University Johns Hopkins University
11100 Johns Hopkins Road, Room 257 11100 Johns Hopkins Road, Room 257
Laurel, Maryland 21073 Laurel, Maryland 21073
USA USA
Phone: +1 443 778 6951 Phone: +1 443 778 6951
EMail: robert.cole@jhuapl.edu EMail: robert.cole@jhuapl.edu
URI: http://www.cs.jhu.edu/~rgcole/ URI: http://www.cs.jhu.edu/~rgcole/
Ian D Chakeres Ian D Chakeres
Motorola CenGen
Bagmane Tech Park 9250 Bendix Road North
66/1, Plot 5, CV Raman Nagar Columbia, Maryland 21045
Bangalore, Karnataka 560093 USA
India
EMail: ian.chakeres@gmail.com EMail: ian.chakeres@gmail.com
URI: http://www.ianchak.com/ URI: http://www.ianchak.com/
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
 End of changes. 27 change blocks. 
36 lines changed or deleted 65 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/