Definitions of Managed Objects for the Ethernet-like Interface Types
RFC 3635

 
Document Type RFC - Proposed Standard (October 2003; No errata)
Obsoletes RFC 2665
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3635 (Proposed Standard)
Telechat date
Responsible AD Bert Wijnen
IESG note Requested to go on IESG agenda on June 12th
Responsible: bwijnen/iesg
Send notices to <dromasca@avaya.com>

Email authors IPR References Referenced by Nits Search lists

Network Working Group                                           J. Flick
Request for Comments: 3635                       Hewlett-Packard Company
Obsoletes: 2665                                           September 2003
Category: Standards Track

                   Definitions of Managed Objects for
                   the Ethernet-like Interface Types

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it defines objects for managing Ethernet-like
   interfaces.  This memo obsoletes RFC 2665.  It updates that
   specification by including management information useful for the
   management of 10 Gigabit per second (Gb/s) Ethernet interfaces.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  The Internet-Standard Management Framework . . . . . . . . . .  3
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
       3.1.  Relation to MIB-2. . . . . . . . . . . . . . . . . . . .  4
       3.2.  Relation to the Interfaces MIB . . . . . . . . . . . . .  4
             3.2.1.  Layering Model . . . . . . . . . . . . . . . . .  4
             3.2.2.  Virtual Circuits . . . . . . . . . . . . . . . .  4
             3.2.3.  ifRcvAddressTable. . . . . . . . . . . . . . . .  5
             3.2.4.  ifType . . . . . . . . . . . . . . . . . . . . .  5
             3.2.5.  ifXxxOctets. . . . . . . . . . . . . . . . . . .  5
             3.2.6.  ifXxxXcastPkts . . . . . . . . . . . . . . . . .  6
             3.2.7.  ifMtu. . . . . . . . . . . . . . . . . . . . . .  8
             3.2.8.  ifSpeed and ifHighSpeed. . . . . . . . . . . . .  8
             3.2.9.  ifPhysAddress. . . . . . . . . . . . . . . . . .  9
             3.2.10.  Specific Interface MIB Objects. . . . . . . . . 10
       3.3.  Relation to the 802.3 MAU MIB. . . . . . . . . . . . . . 13

Flick                       Standards Track                     [Page 1]
RFC 3635                   Ethernet-Like MIB              September 2003

       3.4.  dot3StatsEtherChipSet. . . . . . . . . . . . . . . . . . 13
       3.5.  Mapping of IEEE 802.3 Managed Objects. . . . . . . . . . 14
   4.  Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 17
   5.  Intellectual Property Statement. . . . . . . . . . . . . . . . 55
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 56
   7.  Normative References . . . . . . . . . . . . . . . . . . . . . 57
   8.  Informative References . . . . . . . . . . . . . . . . . . . . 58
   9.  Security Considerations. . . . . . . . . . . . . . . . . . . . 59
   10. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 60
   A.  Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 61
       A.1.  Changes since RFC 2665 . . . . . . . . . . . . . . . . . 61
       A.2.  Changes between RFC 2358 and RFC 2665  . . . . . . . . . 62
       A.3.  Changes between RFC 1650 and RFC 2358. . . . . . . . . . 62
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 63
   Full Copyright Statement  . . . . . . . . . . . . . . . . . . . . .64

1. Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it defines objects for managing Ethernet-like
   interfaces.

   This memo also includes a MIB module.  This MIB module updates the
   list of managed objects specified in the earlier version of this MIB,
   module, RFC 2665 [RFC2665].

   Ethernet technology, as defined by the 802.3 Working Group of the
   IEEE, continues to evolve, with scalable increases in speed, new
   types of cabling and interfaces, and new features.  This evolution
   may require changes in the managed objects in order to reflect this
   new functionality.  This document, as with other documents issued by
   this working group, reflects a certain stage in the evolution of
   Ethernet technology.  In the future, this document might be revised,
   or new documents might be issued by the Ethernet Interfaces and Hub
   MIB Working Group, in order to reflect the evolution of Ethernet
   technology.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text