Power Ethernet MIB
RFC 3621

Document Type RFC - Proposed Standard (December 2003; No errata)
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 3621 (Proposed Standard)
Telechat date
Responsible AD Bert Wijnen
IESG note Published as RFC3621
Send notices to <dromasca@avaya.com>
Network Working Group                                          A. Berger
Request for Comments: 3621                               PowerDsine Inc.
Category: Standards Track                                   D. Romascanu
                                                                   Avaya
                                                           December 2003

                           Power Ethernet MIB

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.
   This document proposes an extension to the Ethernet-like Interfaces
   MIB with a set of objects for managing Power Sourcing Equipment
   (PSE).

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  The Internet-Standard Management Framework . . . . . . . . . .  2
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  2
   4.  MIB Structure. . . . . . . . . . . . . . . . . . . . . . . . .  3
   5.  Definitions. . . . . . . . . . . . . . . . . . . . . . . . . .  3
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
       7.1.  Normative References . . . . . . . . . . . . . . . . . . 16
       7.2.  Informative References . . . . . . . . . . . . . . . . . 17
   8.  Intellectual Property Statement. . . . . . . . . . . . . . . . 17
   9.  Security Considerations. . . . . . . . . . . . . . . . . . . . 18
   10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 19
   11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 20

Berger & Romascanu          Standards Track                     [Page 1]
RFC 3621                   Power Ethernet MIB              December 2003

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 a set of MIB objects to manage Power
   Ethernet [IEEE-802.3af] Power Sourcing Equipment (PSE).

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

3.  Overview

   The emergence of IP telephony as an application that allows voice
   applications to be run over the same infrastructure as data
   applications has led to the emergence of Ethernet IP phones, which
   have similar functions and characteristics as traditional phones.
   Powering the phone with the same cable used for signal transfer is
   one of the functions that are being taken as granted.  The IEEE 802.3
   Working Group has initiated standardization on this subject,
   currently known as the IEEE 802.3af work [IEEE-802.3af].

   The IEEE 802.3af WG did not define a full management interface, but
   only the hardware registers that will allow for management interfaces
   to be built for a powered Ethernet device.  The MIB module defined in
   this document extends the Ethernet-like Interfaces MIB [RFC3635] with
   the management objects required for the management of the powered
   Ethernet devices and ports.

Berger & Romascanu          Standards Track                     [Page 2]
RFC 3621                   Power Ethernet MIB              December 2003
Show full document text