| 1 |
|
|---|
| 2 | IANA-RTPROTO-MIB DEFINITIONS ::= BEGIN
|
|---|
| 3 |
|
|---|
| 4 | IMPORTS
|
|---|
| 5 | MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
|
|---|
| 6 | TEXTUAL-CONVENTION FROM SNMPv2-TC;
|
|---|
| 7 |
|
|---|
| 8 | ianaRtProtoMIB MODULE-IDENTITY
|
|---|
| 9 | LAST-UPDATED "200009260000Z" -- September 26, 2000
|
|---|
| 10 | ORGANIZATION "IANA"
|
|---|
| 11 | CONTACT-INFO
|
|---|
| 12 | " Internet Assigned Numbers Authority
|
|---|
| 13 | Internet Corporation for Assigned Names and Numbers
|
|---|
| 14 | 4676 Admiralty Way, Suite 330
|
|---|
| 15 | Marina del Rey, CA 90292-6601
|
|---|
| 16 |
|
|---|
| 17 | Phone: +1 310 823 9358
|
|---|
| 18 | EMail: iana&iana.org"
|
|---|
| 19 | DESCRIPTION
|
|---|
| 20 | "This MIB module defines the IANAipRouteProtocol and
|
|---|
| 21 | IANAipMRouteProtocol textual conventions for use in MIBs
|
|---|
| 22 | which need to identify unicast or multicast routing
|
|---|
| 23 | mechanisms.
|
|---|
| 24 |
|
|---|
| 25 | Any additions or changes to the contents of this MIB module
|
|---|
| 26 | require either publication of an RFC, or Designated Expert
|
|---|
| 27 | Review as defined in RFC 2434, Guidelines for Writing an
|
|---|
| 28 | IANA Considerations Section in RFCs. The Designated Expert
|
|---|
| 29 | will be selected by the IESG Area Director(s) of the Routing
|
|---|
| 30 | Area."
|
|---|
| 31 |
|
|---|
| 32 | REVISION "200009260000Z" -- September 26, 2000
|
|---|
| 33 | DESCRIPTION "Original version, published in coordination
|
|---|
| 34 | with RFC 2932."
|
|---|
| 35 |
|
|---|
| 36 | ::= { mib-2 84 }
|
|---|
| 37 |
|
|---|
| 38 | IANAipRouteProtocol ::= TEXTUAL-CONVENTION
|
|---|
| 39 | STATUS current
|
|---|
| 40 |
|
|---|
| 41 | DESCRIPTION
|
|---|
| 42 | "A mechanism for learning routes. Inclusion of values for
|
|---|
| 43 | routing protocols is not intended to imply that those
|
|---|
| 44 | protocols need be supported."
|
|---|
| 45 | SYNTAX INTEGER {
|
|---|
| 46 | other (1), -- not specified
|
|---|
| 47 | local (2), -- local interface
|
|---|
| 48 | netmgmt (3), -- static route
|
|---|
| 49 | icmp (4), -- result of ICMP Redirect
|
|---|
| 50 |
|
|---|
| 51 | -- the following are all dynamic
|
|---|
| 52 | -- routing protocols
|
|---|
| 53 |
|
|---|
| 54 | egp (5), -- Exterior Gateway Protocol
|
|---|
| 55 | ggp (6), -- Gateway-Gateway Protocol
|
|---|
| 56 | hello (7), -- FuzzBall HelloSpeak
|
|---|
| 57 | rip (8), -- Berkeley RIP or RIP-II
|
|---|
| 58 | isIs (9), -- Dual IS-IS
|
|---|
| 59 | esIs (10), -- ISO 9542
|
|---|
| 60 | ciscoIgrp (11), -- Cisco IGRP
|
|---|
| 61 | bbnSpfIgp (12), -- BBN SPF IGP
|
|---|
| 62 | ospf (13), -- Open Shortest Path First
|
|---|
| 63 | bgp (14), -- Border Gateway Protocol
|
|---|
| 64 | idpr (15), -- InterDomain Policy Routing
|
|---|
| 65 | ciscoEigrp (16), -- Cisco EIGRP
|
|---|
| 66 | dvmrp (17) -- DVMRP
|
|---|
| 67 | }
|
|---|
| 68 |
|
|---|
| 69 | IANAipMRouteProtocol ::= TEXTUAL-CONVENTION
|
|---|
| 70 | STATUS current
|
|---|
| 71 | DESCRIPTION
|
|---|
| 72 | "The multicast routing protocol. Inclusion of values for
|
|---|
| 73 | multicast routing protocols is not intended to imply that
|
|---|
| 74 | those protocols need be supported."
|
|---|
| 75 | SYNTAX INTEGER {
|
|---|
| 76 | other(1), -- none of the following
|
|---|
| 77 | local(2), -- e.g., manually configured
|
|---|
| 78 | netmgmt(3), -- set via net.mgmt protocol
|
|---|
| 79 | dvmrp(4),
|
|---|
| 80 | mospf(5),
|
|---|
| 81 | pimSparseDense(6), -- PIMv1, both DM and SM
|
|---|
| 82 | cbt(7),
|
|---|
| 83 | pimSparseMode(8), -- PIM-SM
|
|---|
| 84 | pimDenseMode(9), -- PIM-DM
|
|---|
| 85 | igmpOnly(10),
|
|---|
| 86 | bgmp(11),
|
|---|
| 87 | msdp(12)
|
|---|
| 88 | }
|
|---|
| 89 |
|
|---|
| 90 | END
|
|---|
| 91 |
|
|---|
| 92 |
|
|---|
![(please configure the [header_logo] section in trac.ini)](/trac_user/contrib/chrome/site/your_project_logo.png){kind=logo}
