[ipcdn] RFC 5098 on Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)
rfc-editor@rfc-editor.org Sat, 01 March 2008 02:38 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 712E228C97E; Fri, 29 Feb 2008 18:38:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.182
X-Spam-Level:
X-Spam-Status: No, score=-0.182 tagged_above=-999 required=5 tests=[AWL=-0.345, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6, RDNS_NONE=0.1]
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 w8jhlpbGQWKn; Fri, 29 Feb 2008 18:38:49 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5153A28C89B; Fri, 29 Feb 2008 18:38:48 -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 2FB863A6C43; Fri, 29 Feb 2008 18:38:45 -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 WCpI2-RXwPXK; Fri, 29 Feb 2008 18:38:44 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 5C97A28C0D8; Fri, 29 Feb 2008 18:38:44 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 8BC16117840; Fri, 29 Feb 2008 18:38:33 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080301023833.8BC16117840@bosco.isi.edu>
Date: Fri, 29 Feb 2008 18:38:33 -0800
Cc: ipcdn@ietf.org, rfc-editor@rfc-editor.org
Subject: [ipcdn] RFC 5098 on Signaling MIB for PacketCable and IPCablecom Multimedia Terminal 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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org
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 ... _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www.ietf.org/mailman/listinfo/ipcdn
- [ipcdn] RFC 5098 on Signaling MIB for PacketCable… rfc-editor
- Re: [ipcdn] RFC 5098 on Signaling MIB for PacketC… Woundy, Richard