Re: RFC 5098 on Signaling MIB for PacketCable and IPCablecom MultimediaTerminal Adapters (MTAs)

Folks,

I would like to congratulate Gordon Beacham, Satish Kumar, and Sumanth
Channabasappa on the publishing of RFC 5098 aka the NCS Signaling MIB,
and to thank my co-chair Jean-Francois Mule for the shepherding of this
document.

Only one more to go! (PacketCable/IPCableCom Management Event MIB)

-- Rich

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, February 29, 2008 9:39 PM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]
Subject: RFC 5098 on Signaling MIB for PacketCable and IPCablecom
MultimediaTerminal Adapters (MTAs)


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

        
        RFC 5098

        Title:      Signaling MIB for PacketCable and 
                    IPCablecom Multimedia Terminal Adapters (MTAs) 
        Author:     G. Beacham, S. Kumar,
                    S. Channabasappa
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    [email protected], 
                    [email protected], 
                    [email protected]
        Pages:      79
        Characters: 159415
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipcdn-pktc-signaling-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5098.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 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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email protected]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-announce