[ipcdn] RFC 5428 on Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices

rfc-editor@rfc-editor.org Wed, 01 April 2009 23:39 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ipcdn@core3.amsl.com
Delivered-To: ipcdn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E55593A6AB1; Wed, 1 Apr 2009 16:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.949
X-Spam-Level:
X-Spam-Status: No, score=-16.949 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BikQTBpNYfCl; Wed, 1 Apr 2009 16:39:26 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 440193A6A91; Wed, 1 Apr 2009 16:37:50 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 18A3926CC07; Wed, 1 Apr 2009 16:38:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090401233810.18A3926CC07@bosco.isi.edu>
Date: Wed, 1 Apr 2009 16:38:10 -0700 (PDT)
Cc: ipcdn@ietf.org, rfc-editor@rfc-editor.org
Subject: [ipcdn] RFC 5428 on Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipcdn>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2009 23:39:27 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5428

        Title:      Management Event Management Information Base 
                    (MIB) for PacketCable- and IPCablecom-Compliant
                    Devices 
        Author:     S. Channabasappa, W. De Ketelaere,
                    E. Nechamkin
        Status:     Standards Track
        Date:       April 2009
        Mailbox:    Sumanth@cablelabs.com, 
                    deketelaere@tComLabs.com, 
                    enechamkin@broadcom.com
        Pages:      37
        Characters: 78139
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipcdn-pktc-eventmess-14.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5428.txt

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 basic set of managed objects for Simple
Network Management Protocol (SNMP)-based management of events that
can be generated by PacketCable- and IPCablecom-compliant Multimedia
Terminal Adapter devices.  [STANDARDS TRACK]

This document is a product of the IP over Cable Data Network Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute