From atommib-request@research.telcordia.com Mon Nov 3 21:10:11 2003 Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08813 for ; Mon, 3 Nov 2003 21:10:05 -0500 (EST) Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id hA426kes009175; Mon, 3 Nov 2003 21:06:47 -0500 (EST) Received: (from slmgr@localhost) by donner.research.telcordia.com (8.8.8/8.8.8) id VAA11700; Mon, 3 Nov 2003 21:06:46 -0500 (EST) Resent-Date: Mon, 3 Nov 2003 21:06:46 -0500 (EST) X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to atommib-request@research.telcordia.com using -f Old-Return-Path: X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3A278.1B12D5E0" Subject: Day counters Date: Mon, 3 Nov 2003 18:05:23 -0800 Message-ID: <93401232EABAAB4EA430E13ECC701CCF2B9231@yorktown.pedestalnetworks.com> Thread-Topic: Day counters Thread-Index: AcOieGEZJvmxPtsnTrqYbbcJ2W2i9A== From: "Faye Ly" To: X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi) X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper) Resent-Message-ID: Resent-From: atommib@research.telcordia.com X-Mailing-List: X-Loop: atommib@research.telcordia.com List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: atommib-request@research.telcordia.com This is a multi-part message in MIME format. ------_=_NextPart_001_01C3A278.1B12D5E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 I was going through the Optical MIB and other MIBs trying to find a consistent way of displaying day counters. According to the Optical MIB, current day counter is based on the calendar time of the box and previous day also. This is all very clear but now I go back to the T1, T3, and SONET mib and found various support: =20 T1 and T3 supports Total counter which is really the last 24 hours or last 96 intervals. =20 Sonet MIB doesn't support day counter. =20 I always thought Total is the total since agent is up and day counter should be based on the calendar time. Is it worth the effort to come up with a generic perf MIB for T1, T3 and SONET? =20 Thanks. =20 -faye ------_=_NextPart_001_01C3A278.1B12D5E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

I was going through the Optical MIB and other MIBs = trying to find a consistent way of displaying day counters. According to the Optical MIB, current day counter is based on the calendar time of the = box and previous day also. This is all very clear but now I go back to the = T1, T3, and SONET mib and found various support:

T1 and T3 supports Total counter which is really the = last 24 hours or last 96 intervals.

Sonet MIB doesn’t support day = counter.

I always thought Total is the total since agent is up = and day counter should be based on the calendar time. Is it worth the = effort to come up with a generic perf MIB for T1, T3 and SONET?

Thanks.

-faye

=00 ------_=_NextPart_001_01C3A278.1B12D5E0-- From atommib-request@research.telcordia.com Mon Nov 3 23:42:55 2003 Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14615 for ; Mon, 3 Nov 2003 23:42:54 -0500 (EST) Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id hA44fdes012910; Mon, 3 Nov 2003 23:41:40 -0500 (EST) Received: (from slmgr@localhost) by donner.research.telcordia.com (8.8.8/8.8.8) id XAA14072; Mon, 3 Nov 2003 23:41:39 -0500 (EST) Resent-Date: Mon, 3 Nov 2003 23:41:39 -0500 (EST) Old-Return-Path: X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Mon, 3 Nov 2003 20:41:24 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: AToM MIB Subject: Re: Day counters In-Reply-To: <93401232EABAAB4EA430E13ECC701CCF2B9231@yorktown.pedestalnetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi) X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper) Resent-Message-ID: Resent-From: atommib@research.telcordia.com X-Mailing-List: X-Loop: atommib@research.telcordia.com List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: atommib-request@research.telcordia.com On Mon, 3 Nov 2003, Faye Ly wrote: > I was going through the Optical MIB and other MIBs trying to > find a consistent way of displaying day counters. According to > the Optical MIB, current day counter is based on the calendar > time of the box and previous day also. This is all very clear > but now I go back to the T1, T3, and SONET mib and found various > support: > > T1 and T3 supports Total counter which is really the last 24 > hours or last 96 intervals. > > Sonet MIB doesn't support day counter. > > I always thought Total is the total since agent is up and day > counter should be based on the calendar time. Is it worth the > effort to come up with a generic perf MIB for T1, T3 and SONET? Faye, It is indeed true that we'd need to have supplemental MIBs for DS1, DS3, and SONET in order to support everything in ANSI T1.231. The existing MIB modules don't support 1-day counts nor do they support thresholding and alerting. That said, let me point out that there have been at least two attempts to provide these things in the past (one by Maria Greene and collaborators circa 1996, one by Ken Chapman circa 1998), but these efforts have withered on the vine owing to insufficient interest. Regards, Mike From atommib-request@research.telcordia.com Wed Nov 5 15:54:39 2003 Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23308 for ; Wed, 5 Nov 2003 15:54:39 -0500 (EST) Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id hA5Kques015015; Wed, 5 Nov 2003 15:52:56 -0500 (EST) Received: (from slmgr@localhost) by donner.research.telcordia.com (8.8.8/8.8.8) id PAA25683; Wed, 5 Nov 2003 15:52:55 -0500 (EST) Resent-Date: Wed, 5 Nov 2003 15:52:55 -0500 (EST) X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to atommib-request@research.telcordia.com using -f Old-Return-Path: Message-ID: From: "Lam, Hing-Kam (Kam)" To: "'AToM Working Group'" Cc: "'faye@pedestalnetworks.com'" Subject: FW: ID Tracker State Update Notice: draft-ietf-atommib-atm2 Date: Wed, 5 Nov 2003 15:52:05 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi) X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper) Resent-Message-ID: Resent-From: atommib@research.telcordia.com X-Mailing-List: X-Loop: atommib@research.telcordia.com List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: atommib-request@research.telcordia.com Hi, The state of the ATM2 mib has been changed from "RFC Ed Queue" to "RFC Published". Regards, Kam -----Original Message----- From: The IESG [mailto:iesg-secretary@ietf.org] Sent: Wednesday, November 05, 2003 3:39 PM To: fayely98@hotmail.com; hklam@lucent.com Subject: ID Tracker State Update Notice: draft-ietf-atommib-atm2 'State Changes to RFC Published from RFC Ed Queue by Amy Vezza' ID Tracker URL: https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=1212&rfc_flag=0 From atommib-request@research.telcordia.com Wed Nov 5 18:22:15 2003 Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00492 for ; Wed, 5 Nov 2003 18:22:14 -0500 (EST) Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id hA5NLCes020933; Wed, 5 Nov 2003 18:21:12 -0500 (EST) Received: (from slmgr@localhost) by donner.research.telcordia.com (8.8.8/8.8.8) id SAA27889; Wed, 5 Nov 2003 18:21:11 -0500 (EST) Resent-Date: Wed, 5 Nov 2003 18:21:11 -0500 (EST) Old-Return-Path: X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Wed, 5 Nov 2003 15:21:04 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: "AToM MIB Working Group'" Subject: Re: FW: ID Tracker State Update Notice: draft-ietf-atommib-atm2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi) X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper) Resent-Message-ID: Resent-From: atommib@research.telcordia.com X-Mailing-List: X-Loop: atommib@research.telcordia.com List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: atommib-request@research.telcordia.com On Wed, 5 Nov 2003, Lam, Hing-Kam (Kam) wrote: > The state of the ATM2 mib has been changed from "RFC Ed Queue" > to "RFC Published". > > Regards, > Kam > > -----Original Message----- > From: The IESG [mailto:iesg-secretary@ietf.org] > Sent: Wednesday, November 05, 2003 3:39 PM > To: fayely98@hotmail.com; hklam@lucent.com > Subject: ID Tracker State Update Notice: draft-ietf-atommib-atm2 > > > 'State Changes to RFC Published from RFC Ed Queue by Amy Vezza' > ID Tracker URL: > https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=1212&rfc_flag=0 The published document is RFC 3606 and it is available at these URLs: http://www.rfc-editor.org/rfc/rfc3606.txt ftp://ftp.rfc-editor.org/in-notes/rfc3606.txt //cmh From atommib-request@research.telcordia.com Wed Nov 5 23:04:03 2003 Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08993 for ; Wed, 5 Nov 2003 23:03:53 -0500 (EST) Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id hA642Xes028385; Wed, 5 Nov 2003 23:02:33 -0500 (EST) Received: (from slmgr@localhost) by donner.research.telcordia.com (8.8.8/8.8.8) id XAA02264; Wed, 5 Nov 2003 23:02:33 -0500 (EST) Resent-Date: Wed, 5 Nov 2003 23:02:33 -0500 (EST) Old-Return-Path: X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Wed, 5 Nov 2003 20:02:24 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: AtoM MIB WG Subject: RFC 3606 on Definitions of Supplemental Managed Objects for ATM Interface (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-1893687625-1068091192=:15916" Content-ID: X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi) X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper) Resent-Message-ID: Resent-From: atommib@research.telcordia.com X-Mailing-List: X-Loop: atommib@research.telcordia.com List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: atommib-request@research.telcordia.com This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---2133786286-1893687625-1068091192=:15916 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: The attached message is being forwarded since the list admin has not enabled RFC announcements to be posted to this list by rfc-editor@rfc-editor.org despite repeated requests ... ---2133786286-1893687625-1068091192=:15916 Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII Content-ID: Content-Description: RFC 3606 on Definitions of Supplemental Managed Objects for ATM Interface (fwd) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hA5J2fW12146; Wed, 5 Nov 2003 11:02:41 -0800 (PST) Message-Id: <200311051902.hA5J2fW12146@gamma.isi.edu> To: IETF-Announce: ; Subject: RFC 3606 on Definitions of Supplemental Managed Objects for ATM Interface Cc: rfc-editor@rfc-editor.org, atommib@research.telcordia.com From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 05 Nov 2003 11:02:41 -0800 Sender: owner-ietf-announce@ietf.org Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3606 Title: Definitions of Supplemental Managed Objects for ATM Interface Author(s): F. Ly, M. Noto, A. Smith, E. Spiegel, K. Tesink Status: Standards Track Date: November 2003 Mailbox: faye@pedestalnetworks.com, mnoto@cisco.com, ah_smith@acm.org, mspiegel@cisco.com, kaj@research.telcordia.com Pages: 94 Characters: 183610 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-atommib-atm2-19.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3606.txt This memo defines objects used for managing ATM-based interfaces, devices, and services, in addition to those defined in RFC 2515, the ATM-MIB, to provide additional support for the management of ATM Switched Virtual Connections (SVCs) and ATM Permanent Virtual Connections (PVCs). This document is a product of the AToM MIB Working Group of the IETF. This is now a Proposed Standard Protocol. 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.echo 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <031105110054.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3606 --OtherAccess Content-Type: Message/External-body; name="rfc3606.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <031105110054.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- ---2133786286-1893687625-1068091192=:15916--