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

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Thu, 06 March 2008 04:27 UTC

Return-Path: <ipcdn-bounces@ietf.org>
X-Original-To: ietfarch-ipcdn-archive@core3.amsl.com
Delivered-To: ietfarch-ipcdn-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 504AC28C49E; Wed, 5 Mar 2008 20:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.844
X-Spam-Level:
X-Spam-Status: No, score=-99.844 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 kyKNwvE6lP+b; Wed, 5 Mar 2008 20:27:39 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 514DC28C122; Wed, 5 Mar 2008 20:27:39 -0800 (PST)
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 3E9D728C11D for <ipcdn@core3.amsl.com>; Wed, 5 Mar 2008 20:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 1lSWQG6WpVLJ for <ipcdn@core3.amsl.com>; Wed, 5 Mar 2008 20:27:36 -0800 (PST)
Received: from pacdcimo02.cable.comcast.com (PacdcIMO02.cable.comcast.com [24.40.8.146]) by core3.amsl.com (Postfix) with ESMTP id D7B343A6CB7 for <ipcdn@ietf.org>; Wed, 5 Mar 2008 20:27:35 -0800 (PST)
Received: from ([10.52.116.31]) by pacdcimo02.cable.comcast.com with ESMTP id KP-GZL85.17561875; Wed, 05 Mar 2008 23:27:12 -0500
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Mar 2008 23:27:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 5 Mar 2008 23:27:11 -0500
Message-ID: <EF2F0EC839870F43A6637360BC12ABD404AA8FE5@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <20080301023833.8BC16117840@bosco.isi.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RFC 5098 on Signaling MIB for PacketCable and IPCablecom MultimediaTerminal Adapters (MTAs)
Thread-Index: Ach7RXbsHfvkPh9xTJGguVizX2r6kwD7mKfA
References: <20080301023833.8BC16117840@bosco.isi.edu>
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: <ipcdn@ietf.org>
X-OriginalArrivalTime: 06 Mar 2008 04:27:11.0818 (UTC) FILETIME=[5905CAA0:01C87F42]
Cc: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
Subject: Re: [ipcdn] RFC 5098 on Signaling MIB for PacketCable and IPCablecom MultimediaTerminal Adapters (MTAs)
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-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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

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: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of
rfc-editor@rfc-editor.org
Sent: Friday, February 29, 2008 9:39 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: ipcdn@ietf.org; rfc-editor@rfc-editor.org
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:    gordon.beacham@motorola.com, 
                    satish.kumar@ti.com, 
                    Sumanth@cablelabs.com
        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 IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www.ietf.org/mailman/listinfo/ipcdn