draft-ietf-hubmib-etherif-mib-v3-01.txt   draft-ietf-hubmib-etherif-mib-v3-02.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
INTERNET DRAFT J. Flick INTERNET DRAFT J. Flick
Hewlett-Packard Company Hewlett-Packard Company
Editors of previous versions: Editors of previous versions:
J. Flick J. Flick
Hewlett-Packard Company Hewlett-Packard Company
J. Johnson J. Johnson
RedBack Networks RedBack Networks
F. Kastenholz F. Kastenholz
Unisphere Networks Unisphere Networks
February 2002 May 2002
Definitions of Managed Objects for Definitions of Managed Objects for
the Ethernet-like Interface Types the Ethernet-like Interface Types
<draft-ietf-hubmib-etherif-mib-v3-01.txt> <draft-ietf-hubmib-etherif-mib-v3-02.txt>
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 RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 4, line 41 skipping to change at page 4, line 41
Instances of these object types represent attributes of an interface Instances of these object types represent attributes of an interface
to an ethernet-like communications medium. At present, ethernet-like to an ethernet-like communications medium. At present, ethernet-like
media are identified by the value ethernetCsmacd(6) of the ifType media are identified by the value ethernetCsmacd(6) of the ifType
object in the Interfaces MIB [RFC2863]. Some older implementations object in the Interfaces MIB [RFC2863]. Some older implementations
may return the values iso88023Csmacd(7) or starLan(11) for ifType for may return the values iso88023Csmacd(7) or starLan(11) for ifType for
ethernet-like media. ethernet-like media.
The definitions presented here are based on Section 30, "10 Mb/s, 100 The definitions presented here are based on Section 30, "10 Mb/s, 100
Mb/s 1000 Mb/s and 10 Gb/s Management", and Annex 30A, "GDMO Mb/s 1000 Mb/s and 10 Gb/s Management", and Annex 30A, "GDMO
Specification for 802.3 managed object classes" of IEEE Std. 802.3, Specification for 802.3 managed object classes" of IEEE Std. 802.3,
2000 Edition [IEEE802.3], ammended by IEEE Draft P802.3ae/D4.01 2000 Edition [IEEE802.3], amended by IEEE Draft P802.3ae/D4.3
[P802.3a3], as originally interpreted by Frank Kastenholz, then of [P802.3ae], as originally interpreted by Frank Kastenholz, then of
Interlan in [KASTEN]. Implementors of these MIB objects should note Interlan in [KASTEN]. Implementors of these MIB objects should note
that IEEE Std. 802.3 [IEEE802.3] explicitly describes (in the form of that IEEE Std. 802.3 [IEEE802.3] explicitly describes (in the form of
Pascal pseudocode) when, where, and how various MAC attributes are Pascal pseudocode) when, where, and how various MAC attributes are
measured. The IEEE document also describes the effects of MAC actions measured. The IEEE document also describes the effects of MAC actions
that may be invoked by manipulating instances of the MIB objects that may be invoked by manipulating instances of the MIB objects
defined here. defined here.
To the extent that some of the attributes defined in [IEEE802.3] are To the extent that some of the attributes defined in [IEEE802.3] are
represented by previously defined objects in MIB-2 [RFC1213] or in represented by previously defined objects in MIB-2 [RFC1213] or in
the Interfaces MIB [RFC2863], such attributes are not redundantly the Interfaces MIB [RFC2863], such attributes are not redundantly
skipping to change at page 17, line 28 skipping to change at page 17, line 28
oPHYEntity oPHYEntity
.aPhyType Can be derived from .aPhyType Can be derived from
MAU-MIB - ifMauType MAU-MIB - ifMauType
.aPhyTypeList Can be derived from .aPhyTypeList Can be derived from
MAU-MIB - ifMauTypeListBits MAU-MIB - ifMauTypeListBits
.aMIIDetect Not considered useful. .aMIIDetect Not considered useful.
.aPhyAdminState Can already obtain interface .aPhyAdminState Can already obtain interface
state from IF-MIB - ifOperStatus state from IF-MIB - ifAdminStatus
and MAU state from MAU-MIB - and MAU state from MAU-MIB -
ifMauStatus. Providing an ifMauStatus. Providing an
additional state for the PHY additional state for the PHY
was not considered useful. was not considered useful.
.acPhyAdminControl Can already control interface .acPhyAdminControl Can already control interface
state from IF-MIB - ifAdminStatus state from IF-MIB - ifAdminStatus
and MAU state from MAU-MIB - and MAU state from MAU-MIB -
ifMauStatus. Providing separate ifMauStatus. Providing separate
admin control of the PHY was not admin control of the PHY was not
skipping to change at page 18, line 21 skipping to change at page 18, line 21
Counter32, Counter64, mib-2, transmission Counter32, Counter64, mib-2, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex, InterfaceIndex ifIndex, InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
etherMIB MODULE-IDENTITY etherMIB MODULE-IDENTITY
LAST-UPDATED "200202280000Z" -- February 28, 2002 LAST-UPDATED "200205100000Z" -- May 10, 2002
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@ietf.org "WG E-mail: hubmib@ietf.org
To subscribe: hubmib-request@ietf.org To subscribe: hubmib-request@ietf.org
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Avaya Inc. Postal: Avaya Inc.
Atidum Technology Park, Bldg. 3 Atidum Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
skipping to change at page 19, line 11 skipping to change at page 19, line 11
[IEEE 802.3 Std] refers to: [IEEE 802.3 Std] refers to:
IEEE Std 802.3, 2000 Edition: 'IEEE Standard IEEE Std 802.3, 2000 Edition: 'IEEE Standard
for Information technology - for Information technology -
Telecommunications and information exchange Telecommunications and information exchange
between systems - Local and metropolitan between systems - Local and metropolitan
area networks - Specific requirements - area networks - Specific requirements -
Part 3: Carrier sense multiple access with Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method collision detection (CSMA/CD) access method
and physical layer specifications', as and physical layer specifications', as
ammended by IEEE Draft P802.3ae/D4.01: amended by IEEE Draft P802.3ae/D4.3:
'Supplement to Carrier Sense Multiple Access 'Supplement to Carrier Sense Multiple Access
with Collision Detection (CSMA/CD) Access with Collision Detection (CSMA/CD) Access
Method & Physical Layer Specifications - Method & Physical Layer Specifications -
Media Access Control (MAC) Parameters, Media Access Control (MAC) Parameters,
Physical Layer, and Management Parameters Physical Layer, and Management Parameters
for 10 Gb/s Operation', February, 2002. for 10 Gb/s Operation', April, 2002.
Of particular interest is Clause 30, '10 Mb/s, Of particular interest is Clause 30, '10 Mb/s,
100 Mb/s, 1000 Mb/s, and 10 Gb/s Management'." 100 Mb/s, 1000 Mb/s, and 10 Gb/s Management'."
REVISION "200202280000Z" -- February 28, 2002 REVISION "200205100000Z" -- May 10, 2002
DESCRIPTION "Updated to include support for 10 Gb/sec DESCRIPTION "Updated to include support for 10 Gb/sec
interfaces. interfaces.
This version published as RFC XXXX." This version published as RFC XXXX."
REVISION "9908240400Z" -- August 24, 1999 REVISION "9908240400Z" -- August 24, 1999
DESCRIPTION "Updated to include support for 1000 Mb/sec DESCRIPTION "Updated to include support for 1000 Mb/sec
interfaces and full-duplex interfaces. interfaces and full-duplex interfaces.
This version published as RFC 2665." This version published as RFC 2665."
REVISION "9806032150Z" -- June 3, 1998 REVISION "9806032150Z" -- June 3, 1998
skipping to change at page 57, line 7 skipping to change at page 57, line 7
[IEEE802.3] IEEE, IEEE Std 802.3, 2000 Edition: "Information [IEEE802.3] IEEE, IEEE Std 802.3, 2000 Edition: "Information
technology - Telecommunications and information exchange technology - Telecommunications and information exchange
between systems - Local and metropolitan area networks - between systems - Local and metropolitan area networks -
Specific requirements - Part 3: Carrier sense multiple Specific requirements - Part 3: Carrier sense multiple
access with collision detection (CSMA/CD) access method access with collision detection (CSMA/CD) access method
and physical layer specifications", (Adopted by ISO/IEC and physical layer specifications", (Adopted by ISO/IEC
and redesignated as ISO/IEC 8802-3:2000(E), 2000. and redesignated as ISO/IEC 8802-3:2000(E), 2000.
[P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3,
IEEE Draft P802.3ae/D4.01, February 2002, work in IEEE Draft P802.3ae/D4.3, April 2002, work in
progress. progress.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB using SMIv2", RFC 2863, June 2000. MIB using SMIv2", RFC 2863, June 2000.
[MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE
802.3 Medium Attachment Units (MAUs) using SMIv2", work 802.3 Medium Attachment Units (MAUs) using SMIv2", work
in progress, draft-ietf-hubmib-mau-mib-v3-01.txt, in progress, draft-ietf-hubmib-mau-mib-v3-02.txt,
February 2002. May 2002.
Non-Normative References Non-Normative References
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks", Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 1999. RFC 2571, April 1999.
[RFC1155] Rose, M. and K. McCloghrie, "Structure and [RFC1155] Rose, M. and K. McCloghrie, "Structure and
Identification of Management Information for Identification of Management Information for
TCP/IP-based Internets", STD 16, RFC 1155, May 1990. TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
skipping to change at page 59, line 16 skipping to change at page 60, line ?
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2666] Flick, J., "Definitions of Object Identifiers for [RFC2666] Flick, J., "Definitions of Object Identifiers for
Identifying Ethernet Chip Sets", RFC 2666, August 1999. Identifying Ethernet Chip Sets", RFC 2666, August 1999.
[ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald, [ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald,
K., Norseth, K. C., and K. Tesink, "Definitions of K., Norseth, K. C., and K. Tesink, "Definitions of
Managed Objects for the Ethernet WAN Interface Managed Objects for the Ethernet WAN Interface
Sublayer", work in progress, Sublayer", work in progress,
draft-ietf-hubmib-wis-mib-02.txt, February 2002. draft-ietf-hubmib-wis-mib-04.txt, May 2002.
[CASE] Case, J., and C. Partridge, "Case Diagrams: A First Step [CASE] Case, J., and C. Partridge, "Case Diagrams: A First Step
to Diagrammed Management Information Bases", Computer to Diagrammed Management Information Bases", Computer
Communications Review, 19(1):13-16, January 1989. Communications Review, 19(1):13-16, January 1989.
8. Security Considerations 8. Security Considerations
There are two management objects defined in this MIB that have a There are two management objects defined in this MIB that have a
MAX-ACCESS clause of read-write. Such objects may be considered MAX-ACCESS clause of read-write. Such objects may be considered
sensitive or vulnerable in some network environments. The support sensitive or vulnerable in some network environments. The support
skipping to change at page 60, line 4 skipping to change at page 60, line ?
versions of SNMP provide features for such a secure environment. versions of SNMP provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the SNMPv1 by itself is such an insecure environment. Even if the
network itself is secure (for example by using IPSec), even then, network itself is secure (for example by using IPSec), even then,
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET (read) the objects in this MIB. access and GET (read) the objects in this MIB.
It is recommended that the implementors consider the security It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [RFC2574] and the View- of the User-based Security Model RFC 2574 [RFC2574] and the View-
Flick Expires November 2002 [Page 59]e
based Access Control Model RFC 2575 [RFC2575] is recommended. based Access Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to those objects only to those principals configured to give access to those objects only to those principals
(users) that have legitimate rights to access them. (users) that have legitimate rights to access them.
9. Author's Address 9. Author's Address
John Flick John Flick
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/