One document matched: draft-ietf-pppext-bridgemib-01.txt
Differences from draft-ietf-pppext-bridgemib-00.txt
Internet Draft
The Definitions of Managed Objects for
the Bridge Network Control Protocol of
the Point-to-Point Protocol
27 July 1992
Frank Kastenholz
FTP Software, Inc
26 Princess Street
Wakefield, Mass 01880 USA
kasten@ftp.com
Status of this Memo
This document is an Internet Draft. Internet Drafts are
working documents of the Internet Engineering Task Force
(IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet
Drafts.
Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or
obsoleted by other documents at any time. It is not
appropriate to use Internet Drafts as reference material or to
cite them other than as a ``working draft'' or ``work in
progress.'' Please check the 1id-abstracts.txt listing
contained in the internet-drafts Shadow Directories on
nic.ddn.mil, nnsc.nsf.net, nic.nordu.net, ftp.nisc.sri.com, or
munnari.oz.au to learn the current status of any Internet
Draft.
Internet Draft PPP/Bridge MIB July 1992
This document will be submitted to the Internet Activities
Board as a Draft Standard. This document defines an
experimental extension to the SNMP MIB. Upon publication as a
Draft Standard, a new MIB number will be assigned. This is a
working document only, it should neither be cited nor quoted
in any formal document.
This document will expire before 1 Feb. 1993.
Distribution of this document is unlimited.
Please send comments to the author.
1. Abstract
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management
protocols in TCP/IP-based internets. In particular, it
describes managed objects used for managing the bridge Network
Control Protocol[10] on subnetwork interfaces using the family
of Point-to-Point Protocols.
This memo does not specify a standard for the Internet
community.
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 2]
Internet Draft PPP/Bridge MIB July 1992
2. The Network Management Framework
The Internet-standard Network Management Framework consists of
three components. They are:
RFC 1155 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of
management. RFC 1212 defines a more concise description
mechanism, which is wholly consistent with the SMI.
RFC 1156 which defines MIB-I, the core set of managed
objects for the Internet suite of protocols. RFC 1213,
defines MIB-II, an evolution of MIB-I based on
implementation experience and new operational
requirements.
RFC 1157 which defines the SNMP, the protocol used for
network access to managed objects.
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 3]
Internet Draft PPP/Bridge MIB July 1992
3. Objects
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the
MIB are defined using the subset of Abstract Syntax Notation
One (ASN.1) [3] defined in the SMI. In particular, each
object has a name, a syntax, and an encoding. The name is an
object identifier, an administratively assigned name, which
specifies an object type. The object type together with an
object instance serves to uniquely identify a specific
instantiation of the object. For human convenience, we often
use a textual string, termed the OBJECT DESCRIPTOR, to also
refer to the object type.
The syntax of an object type defines the abstract data
structure corresponding to that object type. The ASN.1
language is used for this purpose. However, the SMI [1]
purposely restricts the ASN.1 constructs which may be used.
These restrictions are explicitly made for simplicity.
The encoding of an object type is simply how that object type
is represented using the object type's syntax. Implicitly
tied to the notion of an object type's syntax and encoding is
how the object type is represented when being transmitted on
the network.
The SMI specifies the use of the basic encoding rules of ASN.1
[4], subject to the additional requirements imposed by the
SNMP.
3.1. Format of Definitions
Section 5 contains the specification of all object types
contained in this MIB module. The object types are defined
using the conventions defined in the SMI, as amended by the
extensions specified in [5,6].
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 4]
Internet Draft PPP/Bridge MIB July 1992
4. Overview
4.1. Object Selection Criteria
To be consistent with IAB directives and good engineering
practice, an explicit attempt was made to keep this MIB as
simple as possible. This was accomplished by applying the
following criteria to objects proposed for inclusion:
(1) Require objects be essential for either fault or
configuration management. In particular, objects for
which the sole purpose was to debug implementations were
explicitly excluded from the MIB.
(2) Consider evidence of current use and/or utility.
(3) Limit the total number of objects.
(4) Exclude objects which are simply derivable from others in
this or other MIBs.
4.2. Structure of the PPP
This section describes the basic model of PPP used in
developing the PPP MIB. This information should be useful to
the implementor in understanding some of the basic design
decisions of the MIB.
The PPP is not one single protocol but a large family of
protocols. Each of these is, in itself, a fairly complex
protocol. The PPP protocols may be divided into three rough
categories:
Control Protocols
The Control Protocols are used to control the operation
of the PPP. The Control Protocols include the Link
Control Protocol (LCP), the Password Authentication
Protocol (PAP), the Link Quality Report (LQR), and the
Challenge Handshake Authentication Protocol (CHAP).
Network Protocols
The Network Protocols are used to move the network
traffic over the PPP interface. A Network Protocol
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 5]
Internet Draft PPP/Bridge MIB July 1992
encapsulates the datagrams of a specific higher-layer
protocol that is using the PPP as a data link. Note that
within the context of PPP, the term "Network Protocol"
does not imply an OSI Layer-3 protocol; for instance,
there is a Bridging network protocol.
Network Control Protocols (NCPs)
The NCPs are used to control the operation of the Network
Protocols. Generally, each Network Protocol has its own
Network Control Protocol; thus, the IP Network Protocol
has its IP Control Protocol, the Bridging Network
Protocol has its Bridging Network Control Protocol and so
on.
This document specifies the objects used in managing one of
these protocols, namely the Bridge Network Control Protocol.
4.3. MIB Groups
Objects in this MIB are arranged into several MIB groups.
Each group is organized as a set of related objects.
These groups are the basic unit of conformance: if the
semantics of a group is applicable to an implementation then
all objects in the group must be implemented.
The PPP MIB is organized into several MIB Groups, including,
but not limited to, the following groups:
o The PPP Link Group
o The PPP LQR Group
o The PPP LQR Extensions Group
o The PPP IP Group
o The PPP Bridge Group
o The PPP Security Configuration Group
o The PPP CHAP Group
o The PPP PAP Group
This document specifies the following group:
The PPP Bridge Group
The PPP Bridge Group contains configuration, status, and
control variables that apply to the operation of Bridging
over PPP.
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 6]
Internet Draft PPP/Bridge MIB July 1992
Implementation of this group is mandatory for all
implementations of PPP that support the Bridging over
PPP.
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 7]
Internet Draft PPP/Bridge MIB July 1992
5. Definitions
RFCpppbr-MIB DEFINITIONS ::= BEGIN
IMPORTS
experimental, Counter
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
pppBridge
FROM RFC-ppp
TRAP-TYPE
FROM RFC-1215;
--
-- The PPP Bridge NCP Group.
-- Implementation of this group is mandatory for all
-- PPP implementations that support MAC Bridging over
-- PPP (RFC1220).
--
pppBridgeTable OBJECT-TYPE
SYNTAX SEQUENCE OF PppBridgeEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Table containing the parameters and statistics
for the local PPP entity that are related to
the operation of Bridging over the PPP."
::= { pppBridge 1 }
pppBridgeEntry OBJECT-TYPE
SYNTAX PppBridgeEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Bridging information for a particular PPP
link."
INDEX { pppBridgeIndex }
::= { pppBridgeTable 1 }
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 8]
Internet Draft PPP/Bridge MIB July 1992
PppBridgeEntry ::= SEQUENCE {
pppBridgeIndex
INTEGER,
pppBridgeOperStatus
INTEGER,
pppBridgeLocalToRemoteTinygramCompression
INTEGER,
pppBridgeRemoteToLocalTinygramCompression
INTEGER,
pppBridgeLocalToRemoteLanId
INTEGER,
pppBridgeRemoteToLocalLanId
INTEGER
}
pppBridgeIndex OBJECT-TYPE
SYNTAX INTEGER(1..2147483648)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of ifIndex that identifies the entry
in the interface table that is associated with
the PPP-Link entity over which this Bridge
Network Protocol is operating."
::= { pppBridgeEntry 1 }
pppBridgeOperStatus OBJECT-TYPE
SYNTAX INTEGER {opened(1), not-opened(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The operational status of the Bridge network
protocol. If the value of this object is up
then the finite state machine for the Bridge
network protocol has reached the Opened state."
::= { pppBridgeEntry 2 }
pppBridgeLocalToRemoteTinygramCompression OBJECT-TYPE
SYNTAX INTEGER { false(1), true(2) }
ACCESS read-only
STATUS mandatory
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 9]
Internet Draft PPP/Bridge MIB July 1992
DESCRIPTION
"Indicates whether the local node will perform
Tinygram Compression when sending packets to
the remote entity. If false then the local
entity will not perform Tinygram Compression.
If true then the local entity will perform
Tinygram Compression."
REFERENCE
"Section 6.7, Tinygram Compression Option, of
RFC1220"
::= { pppBridgeEntry 3 }
pppBridgeRemoteToLocalTinygramCompression OBJECT-TYPE
SYNTAX INTEGER { false(1), true(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"If false(1) then the remote entity is not
expected to perform Tinygram Compression. If
true then the remote entity is expected to
perform Tinygram Compression."
REFERENCE
"Section 6.7, Tinygram Compression Option, of
RFC1220"
::= { pppBridgeEntry 4 }
pppBridgeLocalToRemoteLanId OBJECT-TYPE
SYNTAX INTEGER { false(1), true(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether the local node will include
the LAN Identification field in transmitted
packets or not. If false(1) then the local node
will not transmit this field, true(2) means
that the field will be transmitted."
REFERENCE
"Section 6.8, LAN Identification Option, of
RFC1220"
::= { pppBridgeEntry 5 }
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 10]
Internet Draft PPP/Bridge MIB July 1992
pppBridgeRemoteToLocalLanId OBJECT-TYPE
SYNTAX INTEGER { false(1), true(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether the remote node has
indicated that it will include the LAN
Identification field in transmitted packets or
not. If false(1) then the field will not be
transmitted, if true(2) then the field will be
transmitted."
REFERENCE
"Section 6.8, LAN Identification Option, of
RFC1220"
::= { pppBridgeEntry 6 }
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 11]
Internet Draft PPP/Bridge MIB July 1992
--
-- The PPP Bridge Configuration table
--
pppBridgeConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF PppBridgeConfigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Table containing the parameters and statistics
for the local PPP entity that are related to
the operation of Bridging over the PPP."
::= { pppBridge 2 }
pppBridgeConfigEntry OBJECT-TYPE
SYNTAX PppBridgeConfigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Bridging Configuration information for a
particular PPP link."
INDEX { pppBridgeConfigIndex }
::= { pppBridgeConfigTable 1 }
PppBridgeConfigEntry ::= SEQUENCE {
pppBridgeConfigIndex
INTEGER,
pppBridgeConfigAdminStatus
INTEGER,
pppBridgeConfigTinygram
INTEGER,
pppBridgeConfigRingId
INTEGER,
pppBridgeConfigLineId
INTEGER,
pppBridgeConfigLanId
INTEGER
}
pppBridgeConfigIndex OBJECT-TYPE
SYNTAX INTEGER(1..2147483648)
ACCESS read-only
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 12]
Internet Draft PPP/Bridge MIB July 1992
STATUS mandatory
DESCRIPTION
"The value of ifIndex that identifies the entry
in the interface table that is associated with
the local PPP Bridging NCP entity."
::= { pppBridgeConfigEntry 1 }
pppBridgeConfigAdminStatus OBJECT-TYPE
SYNTAX INTEGER { open(1), close(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The immediate desired status of the Bridging
network protocol. Setting this object to open
will inject an administrative open event into
the Bridging network protocol's finite state
machine. Setting this object to close will
inject an administrative close event into the
Bridging network protocol's finite state
machine."
::= { pppBridgeConfigEntry 2 }
pppBridgeConfigTinygram OBJECT-TYPE
SYNTAX INTEGER { false(1), true(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"If false then the local BNCP entity will not
initiate the Tinygram Compression Option
Negotiation. If true then the local BNCP entity
will initiate negotiation of this option."
REFERENCE
"Section 6.7, Tinygram Compression Option, of
RFC1220"
DEFVAL { true }
::= { pppBridgeConfigEntry 3 }
pppBridgeConfigRingId OBJECT-TYPE
SYNTAX INTEGER { false(1), true(2) }
ACCESS read-write
STATUS mandatory
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 13]
Internet Draft PPP/Bridge MIB July 1992
DESCRIPTION
"If false then the local PPP Entity will not
initiate a Remote Ring Identification Option
negotiation. If true then the local PPP entity
will intiate this negotiation. This MIB object
is relevant only if the interface is for 802.5
Token Ring bridging."
REFERENCE
"Section 6.4, IEEE 802.5 Remote Ring
Identification Option, of RFC1220"
DEFVAL { false }
::= { pppBridgeConfigEntry 4 }
pppBridgeConfigLineId OBJECT-TYPE
SYNTAX INTEGER { false(1), true(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"If false then the local PPP Entity is not to
initiate a Line Identification Option
negotiation. If true then the local PPP entity
will intiate this negotiation. This MIB object
is relevant only if the interface is for 802.5
Token Ring bridging."
REFERENCE
"Section 6.5, IEEE 802.5 Line Identification
Option, of RFC1220"
DEFVAL { false }
::= { pppBridgeConfigEntry 5 }
pppBridgeConfigLanId OBJECT-TYPE
SYNTAX INTEGER { false(1), true(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"If false then the local BNCP entity will not
initiate the LAN Identification Option
Negotiation. If true then the local BNCP entity
will initiate negotiation of this option."
REFERENCE
"Section 6.8, LAN Identification Option, of
RFC1220"
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 14]
Internet Draft PPP/Bridge MIB July 1992
DEFVAL { false }
::= { pppBridgeConfigEntry 6 }
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 15]
Internet Draft PPP/Bridge MIB July 1992
--
-- The PPP Bridge Media Status Table
--
pppBridgeMediaTable OBJECT-TYPE
SYNTAX SEQUENCE OF PppBridgeMediaEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Table identifying which MAC media types are
enabled for the Bridging NCPs."
::= { pppBridge 3 }
pppBridgeMediaEntry OBJECT-TYPE
SYNTAX PppBridgeMediaEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Status of a specific MAC Type for a specific
PPP Link."
INDEX { pppBridgeMediaIndex, pppBridgeMediaMacType }
::= { pppBridgeMediaTable 1 }
PppBridgeMediaEntry ::= SEQUENCE {
pppBridgeMediaIndex
INTEGER,
pppBridgeMediaMacType
INTEGER,
pppBridgeMediaLocalStatus
INTEGER,
pppBridgeMediaRemoteStatus
INTEGER
}
pppBridgeMediaIndex OBJECT-TYPE
SYNTAX INTEGER(1..2147483648)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of ifIndex that identifies the entry
in the interface table that is associated with
this entry in the pppBridgeMediaTable."
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 16]
Internet Draft PPP/Bridge MIB July 1992
::= { pppBridgeMediaEntry 1 }
pppBridgeMediaMacType OBJECT-TYPE
SYNTAX INTEGER(0..2147483648)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The MAC type for which this entry in the
pppBridgeMediaTable is providing status
information. Valid values for this object are
defined in Section 6.6 MAC Type Support
Selection of RFC1220 (Bridging Point-to-Point
Protocol)."
REFERENCE
"Section 6.6, MAC Type Support Selection, of
RFC1212."
::= { pppBridgeMediaEntry 2 }
pppBridgeMediaLocalStatus OBJECT-TYPE
SYNTAX INTEGER { accept(1), dont-accept(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether the local PPP Bridging
Entity will accept packets of the protocol type
identified in pppBridgeMediaMacType on the PPP
link identified by pppBridgeMediaPortIndex or
not. If this object is accept then any packets
of the indicated MAC type will be received and
properly processed. If this object is dont-
accept then received packets of the indicated
MAC type will not be properly processed."
REFERENCE
"Section 6.6, MAC Type Support Selection, of
RFC1212."
::= { pppBridgeMediaEntry 3 }
pppBridgeMediaRemoteStatus OBJECT-TYPE
SYNTAX INTEGER { accept(1), dont-accept(2) }
ACCESS read-only
STATUS mandatory
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 17]
Internet Draft PPP/Bridge MIB July 1992
DESCRIPTION
"Indicates whether the local PPP Bridging
Entity believes that the remote PPP Bridging
Entity will accept packets of the protocol type
identified in pppBridgeMediaMacType on the PPP
link identified by pppBridgeMediaPortIndex or
not."
REFERENCE
"Section 6.6, MAC Type Support Selection, of
RFC1212."
::= { pppBridgeMediaEntry 4 }
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 18]
Internet Draft PPP/Bridge MIB July 1992
--
-- The PPP Bridge Media Configuration Table
--
pppBridgeMediaConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF PppBridgeMediaConfigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Table identifying which MAC media types are
enabled for the Bridging NCPs."
::= { pppBridge 4 }
pppBridgeMediaConfigEntry OBJECT-TYPE
SYNTAX PppBridgeMediaConfigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Status of a specific MAC Type for a specific
PPP Link."
INDEX { pppBridgeMediaConfigIndex,
pppBridgeMediaConfigMacType }
::= { pppBridgeMediaConfigTable 1 }
PppBridgeMediaConfigEntry ::= SEQUENCE {
pppBridgeMediaConfigIndex
INTEGER,
pppBridgeMediaConfigMacType
INTEGER,
pppBridgeMediaConfigLocalStatus
INTEGER
}
pppBridgeMediaConfigIndex OBJECT-TYPE
SYNTAX INTEGER(1..2147483648)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The value of ifIndex that identifies the entry
in the interface table that is associated with
this entry in the pppBridgeMediaConfigTable."
::= { pppBridgeMediaConfigEntry 1 }
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 19]
Internet Draft PPP/Bridge MIB July 1992
pppBridgeMediaConfigMacType OBJECT-TYPE
SYNTAX INTEGER(0..2147483648)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The MAC type for which this entry in the
pppBridgeMediaConfigTable is providing status
information. Valid values for this object are
defined in Section 6.6 MAC Type Support
Selection of RFC1220 (Bridging Point-to-Point
Protocol)."
REFERENCE
"Section 6.6, MAC Type Support Selection, of
RFC1212."
::= { pppBridgeMediaConfigEntry 2 }
pppBridgeMediaConfigLocalStatus OBJECT-TYPE
SYNTAX INTEGER { accept(1), dont-accept(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Indicates whether the local PPP Bridging
Entity should accept packets of the protocol
type identified in pppBridgeMediaConfigMacType
on the PPP link identified by
pppBridgeMediaConfigPortIndex or not. Setting
this object to the value dont-accept has the
affect of invalidating the corresponding entry
in the pppBridgeMediaConfigTable object. It is
an implementation-specific matter as to whether
the agent removes an invalidated entry from the
table. Accordingly, management stations must be
prepared to receive tabular information from
agents that corresponds to entries not
currently in use. Changing this object will
have effect when the link is next restarted."
REFERENCE
"Section 6.6, MAC Type Support Selection, of
RFC1212."
::= { pppBridgeMediaConfigEntry 3 }
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 20]
Internet Draft PPP/Bridge MIB July 1992
END
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 21]
Internet Draft PPP/Bridge MIB July 1992
6. Acknowledgements
This document was produced by the PPP working group. In
addition to the working group, the author wishes to thank the
following individuals for their comments and contributions:
Bill Simpson -- Daydreamer
Glenn McGregor -- Merit
Jesse Walker -- DEC
Chris Gunner -- DEC
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 22]
Internet Draft PPP/Bridge MIB July 1992
7. Security Considerations
The PPP MIB affords the network operator the ability to
configure and control the PPP links of a particular system,
including the PPP authentication protocols. This represents a
security risk.
These risks are addressed in the following manners:
(1) All variables which represent a significant security risk
are placed in separate, optional, MIB Groups. As the MIB
Group is the quantum of implementation within a MIB, the
implementor of the MIB may elect not to implement these
groups.
(2) The implementor may choose to implement the variables
which present a security risk so that they may not be
written, i.e., the variables are READ-ONLY. This method
still presents a security risk, and is not recommended,
in that the variables, specifically the PPP
Authentication Protocols' variables, may be easily read.
(3) Using the new SNMP administrative framework[13,14], the
operator can place the variables into MIB views which are
protected in that the parties which have access to those
MIB views use authentication and privacy protocols, or
the operator may elect to make these views not accessible
to any party. In order to facilitate this placement, all
security-related variables are placed in separate MIB
Tables. This eases the identification of the necessary
MIB View Subtree.
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 23]
Internet Draft PPP/Bridge MIB July 1992
8. References
[1] M.T. Rose and K. McCloghrie, Structure and Identification
of Management Information for TCP/IP-based internets,
Internet Working Group Request for Comments 1155.
Network Information Center, SRI International, Menlo
Park, California, (May, 1990).
[2] K. McCloghrie and M.T. Rose, Management Information Base
for Network Management of TCP/IP-based internets - MIB-2,
Internet Working Group Request for Comments 1213.
Network Information Center, SRI International, Menlo
Park, California, (March, 1991).
[3] Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax
Notation One (ASN.1), International Organization for
Standardization. International Standard 8824, (December,
1987).
[4] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules
for Abstract Notation One (ASN.1), International
Organization for Standardization. International Standard
8825, (December, 1987).
[5] Rose, M., and K. McCloghrie, Editors, Concise MIB
Definitions, RFC 1212, Performance Systems International,
Hughes LAN Systems, March 1991.
[6] Rose, M., Editor, A Convention for Defining Traps for use
with the SNMP, RFC 1215, Performance Systems
International, March 1991.
[7] K. McCloghrie, Extensions to the Generic-Interface MIB,
RFC1229, Hughes LAN Systems, May 1991.
[8] W. Simpson, The Point-to-Point Protocol for the
Transmission of Multi-protocol Datagrams over Point-to-
Point Links, RFC 1331, May 1992.
[9] G. McGregor, The PPP Internet Protocol Control Protocol,
RFC 1332, Merit, May 1992.
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 24]
Internet Draft PPP/Bridge MIB July 1992
[10] F. Baker, Point-to-Point Protocol Extensions for
Bridging, RFC1220, ACC, April 1991.
[11] PPP Authentication Protocols, Work In Progress
[12] W. Simpson, PPP Link Quality Monitoring, RFC 1333, May
1992.
[13] New SNMP Administrative Model, Work In Progress.
[14] SNMP Security Protocols, Work In Progress.
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 25]
Internet Draft PPP/Bridge MIB July 1992
Table of Contents
Status of this Memo .................................... 1
1 Abstract .............................................. 2
2 The Network Management Framework ...................... 3
3 Objects ............................................... 4
3.1 Format of Definitions ............................... 4
4 Overview .............................................. 5
4.1 Object Selection Criteria ........................... 5
4.2 Structure of the PPP ................................ 5
4.3 MIB Groups .......................................... 6
5 Definitions ........................................... 8
6 Acknowledgements ...................................... 22
7 Security Considerations ............................... 23
8 References ............................................ 24
Frank J. Kastenholz Exp. 1 Feb. 1993 [Page 26]
| PAFTECH AB 2003-2026 | 2026-04-22 15:08:17 |