From daemon Tue Nov 11 09:00:08 1997 Delivery-Date: Tue, 11 Nov 1997 09:07:45 -0500 Return-Path: daemon Received: (from daemon@localhost) by ietf.org (8.8.7/8.8.7a) id IAA00608 for ietf-123-outbound.10@ietf.org; Tue, 11 Nov 1997 08:59:55 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.7/8.8.7a) with ESMTP id IAA00586; Tue, 11 Nov 1997 08:59:46 -0500 (EST) Message-Id: <199711111359.IAA00586@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce Cc: frs-mib@newbridge.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-frnetmib-frs-mib-02.txt Date: Tue, 11 Nov 1997 08:59:45 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Frame Relay Service MIB Working Group of the IETF. Title : Definitions of Managed Objects for Frame Relay Service Author(s) : D. Fowler Filename : draft-ietf-frnetmib-frs-mib-02.txt Pages : 69 Date : 10-Nov-97 This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. This memo does not specify a standard for the Internet community. This document entirely replaces RFC 1604. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-frnetmib-frs-mib-02.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-frnetmib-frs-mib-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-frnetmib-frs-mib-02.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971110140206.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-frnetmib-frs-mib-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-frnetmib-frs-mib-02.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971110140206.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-frs-mib@ca.newbridge.com Wed Feb 18 09:08:24 1998 Delivery-Date: Wed, 18 Feb 1998 09:08:25 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id JAA29414 for ; Wed, 18 Feb 1998 09:08:23 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id JAA03015; Wed, 18 Feb 1998 09:06:36 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma002821; Wed Feb 18 09:04:38 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 18 Feb 1998 14:04:38 UT Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id JAA18965; Wed, 18 Feb 1998 09:04:37 -0500 (EST) Received: from distmaster.ca.newbridge.com(138.120.49.20) by kanmaster.ca.newbridge.com via smap (V1.3) id sma018855; Wed Feb 18 09:04:23 1998 Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id JAA27787; Wed, 18 Feb 1998 09:02:29 -0500 Received: from thor.ca.newbridge.com by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id JAA27779; Wed, 18 Feb 1998 09:02:24 -0500 Received: from newbridge.com (macdavef [138.120.55.103]) by thor.ca.newbridge.com (8.6.12/8.6.12) with ESMTP id JAA23224; Wed, 18 Feb 1998 09:01:28 -0500 Message-ID: <34EADC51.5A290D06@newbridge.com> Date: Wed, 18 Feb 1998 09:04:30 -0400 From: David Fowler X-Mailer: Mozilla 4.04 (Macintosh; I; PPC) MIME-Version: 1.0 To: amalis@casc.com, rspitzer@telogy.com, james@ca.newbridge.com CC: frs-mib@ca.newbridge.com Subject: ifLinkUpDownTrapEnable for Phys Layer Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM Hi, I'm just going through the final comments before submitting the final draft when I noticed a comment from Roy about changing the recommendation for ifLinkUpDownTrapEnable. draft 2 says that the trap enable is to be defaulted to enabled for frameRelayService interfaces. It also says that is it recommended that physical interfaces below FRS interfaces be defaulted to disabled (this would include ds0Bundles, ds0s, ds1s, data ports) since both are not required. This is the opposite recomendation from ifMIB. The reasoning for FRS interface traps is that PVC traps are required to be squahed when they result from an underlying FRS port failure. The reason for no DSx traps is that they are redundant. (i.e. phys layer failures always result in FRS layer failures) Roy's suggestion, from the FRF, is that the recommendation be changed to enabled for physical interfaces. I am just looking for a little reasoning behind this (it sounds fine for DS1s). I guess I don't think it is useful to generate traps on ds0Bundles and ds0s by default. Also, a manager can always enable any interface traps required. Comments? David -- ------------------------------- "One should always be in love. That is why one should never marry." - Oscar Wilde David Fowler Newbridge Networks 613-591-3600 From owner-frs-mib@ca.newbridge.com Fri Feb 20 10:38:20 1998 Delivery-Date: Fri, 20 Feb 1998 10:38:21 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id KAA11446 for ; Fri, 20 Feb 1998 10:38:20 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id KAA29014; Fri, 20 Feb 1998 10:35:26 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma028538; Fri Feb 20 10:31:24 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 20 Feb 1998 15:31:23 UT Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id KAA14647; Fri, 20 Feb 1998 10:31:21 -0500 (EST) Received: from distmaster.ca.newbridge.com(138.120.49.20) by kanmaster.ca.newbridge.com via smap (V1.3) id sma014539; Fri Feb 20 10:30:52 1998 Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id KAA24699; Fri, 20 Feb 1998 10:29:40 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id KAA24691; Fri, 20 Feb 1998 10:29:35 -0500 Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id KAA13913; Fri, 20 Feb 1998 10:28:40 -0500 (EST) Received: from kanata-gw.ca.newbridge.com(138.120.49.2) by kanmaster.ca.newbridge.com via smap (V1.3) id sma013534; Fri Feb 20 10:27:21 1998 Received: from ns.newbridge.com ([192.75.23.67]) by kanata-gw.ca.newbridge.com via smtpd (for kanmaster.ca.newbridge.com [138.120.124.4]) with SMTP; 20 Feb 1998 15:27:21 UT Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id KAA27973; Fri, 20 Feb 1998 10:27:20 -0500 (EST) Received: from webserver.casc.com(152.148.41.200) by ns.newbridge.com via smap (V1.3) id sma027554; Fri Feb 20 10:23:54 1998 Received: from casc.com (alpo [152.148.10.6]) by webserver.casc.com (8.6.12/8.6.12) with ESMTP id KAA10238; Fri, 20 Feb 1998 10:23:54 -0500 Received: from spice.cascade by casc.com (SMI-8.6/SMI-SVR4-bob.2) id KAA17078; Fri, 20 Feb 1998 10:13:49 -0500 Received: from localhost by spice.cascade (SMI-8.6/SMI-SVR4) id KAA00887; Fri, 20 Feb 1998 10:13:49 -0500 Date: Fri, 20 Feb 1998 10:13:49 -0500 (EST) From: "Andrew G. Malis" X-Sender: amalis@spice To: David Fowler cc: rspitzer@telogy.com, james@ca.newbridge.com, frs-mib@ca.newbridge.com Subject: Re: ifLinkUpDownTrapEnable for Phys Layer In-Reply-To: <34EADC51.5A290D06@newbridge.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM Dave, > Roy's suggestion, from the FRF, is that the recommendation be changed to > enabled for physical interfaces. I am just looking for a little > reasoning behind this (it sounds fine for DS1s). I guess I don't think > it is useful to generate traps on ds0Bundles and ds0s by default. Also, > a manager can always enable any interface traps required. That's consistent with RFC 2233 - the "lowest" layer gets the trap enabled by default, and the layers above that have it turned off. Actually, having thought about this for all of a minute of so after reading your message and checking out the recommendation in 2233, there are instances when the FR service can go down even though the physical interface is up (LMI failure, etc.). So, my own druthers would be to have it on for the lowest physical layer (the DS1 of a DS0 or DS0 bundle, for example), plus the FR service layer, but off otherwise. However, abiding by 2233 is probably for the best. Cheers, Andy ________________________________________________________________________ Andrew G. Malis malis@ascend.com phone:978 952-7414 fax:978 392-1484 Ascend Communications, Inc. 1 Robbins Road Westford, MA 01886 From owner-frs-mib@ca.newbridge.com Mon Feb 23 08:49:50 1998 Delivery-Date: Mon, 23 Feb 1998 08:49:50 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id IAA16486 for ; Mon, 23 Feb 1998 08:49:49 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id IAA29791; Mon, 23 Feb 1998 08:40:10 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma029774; Mon Feb 23 08:39:40 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 23 Feb 1998 13:39:40 UT Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id IAA28520; Mon, 23 Feb 1998 08:39:39 -0500 (EST) Received: from distmaster.ca.newbridge.com(138.120.49.20) by kanmaster.ca.newbridge.com via smap (V1.3) id sma027964; Mon Feb 23 08:35:14 1998 Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id IAA12717; Mon, 23 Feb 1998 08:33:54 -0500 Received: from thor.ca.newbridge.com by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id IAA12709; Mon, 23 Feb 1998 08:33:49 -0500 Received: from newbridge.com (macdavef [138.120.55.103]) by thor.ca.newbridge.com (8.6.12/8.6.12) with ESMTP id IAA08928; Mon, 23 Feb 1998 08:33:02 -0500 Message-ID: <34F16D3C.267CF067@newbridge.com> Date: Mon, 23 Feb 1998 08:36:21 -0400 From: David Fowler X-Mailer: Mozilla 4.04 (Macintosh; I; PPC) MIME-Version: 1.0 To: "Andrew G. Malis" CC: rspitzer@telogy.com, james@ca.newbridge.com, frs-mib@ca.newbridge.com Subject: Re: ifLinkUpDownTrapEnable for Phys Layer References: Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM Andy, After I sent my note, I thought of the LMI case where FR can be down where DS1 is not. I am leaning towards recommending that DS1s get enabled. I think we do need to keep FRS enabled by default as well. I've been trying to recreate in my mind why we made this decision X months ago, andthe only thing I can come up with was that the PVC traps are describes as "This trap indicates that the indicated PVC has changed state. This trap is not sent if an FR_UNI changes state, a linkDown or linkUp trap should be sent instead." This text tells me to send a trap for the FRS entry, so we really should have it on be default. My implementation experience tells me this is useful as well. So, I will change the word disabled to enabled for DS1 traps and clarify that ds0 and ds0 bundle traps should remain disabled. Regards, David Andrew G. Malis wrote: > Dave, > > > Roy's suggestion, from the FRF, is that the recommendation be changed to > > enabled for physical interfaces. I am just looking for a little > > reasoning behind this (it sounds fine for DS1s). I guess I don't think > > it is useful to generate traps on ds0Bundles and ds0s by default. Also, > > a manager can always enable any interface traps required. > > That's consistent with RFC 2233 - the "lowest" layer gets the trap > enabled by default, and the layers above that have it turned off. > > Actually, having thought about this for all of a minute of so after > reading your message and checking out the recommendation in 2233, there > are instances when the FR service can go down even though the physical > interface is up (LMI failure, etc.). So, my own druthers would be to > have it on for the lowest physical layer (the DS1 of a DS0 or DS0 > bundle, for example), plus the FR service layer, but off otherwise. > However, abiding by 2233 is probably for the best. > > Cheers, > Andy > ________________________________________________________________________ > Andrew G. Malis malis@ascend.com phone:978 952-7414 fax:978 392-1484 > Ascend Communications, Inc. 1 Robbins Road Westford, MA 01886 -- David Fowler Newbridge Networks 613-591-3600 From owner-frs-mib@ca.newbridge.com Tue Feb 24 17:09:33 1998 Delivery-Date: Tue, 24 Feb 1998 17:09:33 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id RAA05986 for ; Tue, 24 Feb 1998 17:09:32 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id RAA16554; Tue, 24 Feb 1998 17:06:31 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma016506; Tue Feb 24 17:06:16 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 24 Feb 1998 22:06:16 UT Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id RAA14695; Tue, 24 Feb 1998 17:06:15 -0500 (EST) Received: from distmaster.ca.newbridge.com(138.120.49.20) by kanmaster.ca.newbridge.com via smap (V1.3) id sma014635; Tue Feb 24 17:05:51 1998 Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id RAA23255; Tue, 24 Feb 1998 17:01:37 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id RAA23247; Tue, 24 Feb 1998 17:01:32 -0500 Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id RAA13447; Tue, 24 Feb 1998 17:00:47 -0500 (EST) Received: from kanata-gw.ca.newbridge.com(138.120.49.2) by kanmaster.ca.newbridge.com via smap (V1.3) id sma013125; Tue Feb 24 16:59:36 1998 Received: from ns.newbridge.com ([192.75.23.67]) by kanata-gw.ca.newbridge.com via smtpd (for kanmaster.ca.newbridge.com [138.120.124.4]) with SMTP; 24 Feb 1998 21:59:35 UT Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id QAA15460; Tue, 24 Feb 1998 16:59:33 -0500 (EST) Received: from webserver.casc.com(152.148.41.200) by ns.newbridge.com via smap (V1.3) id sma015308; Tue Feb 24 16:59:17 1998 Received: from casc.com (alpo [152.148.10.6]) by webserver.casc.com (8.6.12/8.6.12) with ESMTP id QAA18665; Tue, 24 Feb 1998 16:59:09 -0500 Received: from malisa by casc.com (SMI-8.6/SMI-SVR4-bob.2) id QAA08781; Tue, 24 Feb 1998 16:49:03 -0500 Message-Id: <3.0.5.32.19980224143417.00a52d80@alpo.casc.com> X-Sender: amalis@alpo.casc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 24 Feb 1998 14:34:17 -0500 To: David Fowler From: "Andrew G. Malis" Subject: Re: ifLinkUpDownTrapEnable for Phys Layer Cc: "Andrew G. Malis" , rspitzer@telogy.com, james@ca.newbridge.com, frs-mib@ca.newbridge.com In-Reply-To: <34F16D3C.267CF067@newbridge.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM Dave, >So, I will change the word disabled to enabled for DS1 traps and clarify that >ds0 and ds0 bundle traps should remain disabled. Sounds good! Cheers, Andy ________________________________________________________________________ Andrew G. Malis malis@ascend.com phone:978 952-7414 fax:978 392-1484 Ascend Communications, Inc. 1 Robbins Road Westford, MA 01886 From owner-frs-mib@ca.newbridge.com Thu Mar 5 22:48:26 1998 Delivery-Date: Thu, 05 Mar 1998 22:49:46 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id WAA22410 for ; Thu, 5 Mar 1998 22:48:26 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id WAA28689; Thu, 5 Mar 1998 22:45:37 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma028549; Thu Mar 5 22:44:19 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 6 Mar 1998 03:44:19 UT Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id WAA23371; Thu, 5 Mar 1998 22:44:18 -0500 (EST) Received: from distmaster.ca.newbridge.com(138.120.118.27) by kanmaster.ca.newbridge.com via smap (V1.3) id sma023354; Thu Mar 5 22:44:16 1998 Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id WAA17745; Thu, 5 Mar 1998 22:43:57 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id WAA17737; Thu, 5 Mar 1998 22:43:53 -0500 Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id WAA23178 for ; Thu, 5 Mar 1998 22:42:11 -0500 (EST) From: b112@light-avenue.com Received: from kanata-gw.ca.newbridge.com(138.120.49.2) by kanmaster.ca.newbridge.com via smap (V1.3) id sma023160; Thu Mar 5 22:41:58 1998 Received: from ns.newbridge.com ([192.75.23.67]) by kanata-gw.ca.newbridge.com via smtpd (for kanmaster.ca.newbridge.com [138.120.124.4]) with SMTP; 6 Mar 1998 03:41:58 UT Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id WAA28383 for ; Thu, 5 Mar 1998 22:40:37 -0500 (EST) Date: Thu, 5 Mar 1998 22:40:37 -0500 (EST) Message-Id: <199803060340.WAA28383@ns.newbridge.com> Received: from 1cust75.tnt4.redmond.wa.da.uu.net(153.37.202.75) by ns.newbridge.com via smap (V1.3) id sma028373; Thu Mar 5 22:40:17 1998 To: Subject: My Secret Weapon Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM Hi, Just wanted to pass along some info about a new piece of software I call my "secret weapon" . It's amazing! Listen to this............................. Hundreds of others and myself can now reach "millions of potential customers"- Absolutely FREE! A lot of us are creating immediate "cash flow explosions"- literally overnight! And blowing our competition right out of the water! You have to check out these fantastic products for yourself! at http://209.20.199.100 Take care. I'll talk with you later. B.J. http://209.20.199.100 ********************************************** This Is An Email Advertisement. If Such Mail Is Unwelcome Please Accept My Apologies. To be removed from this list type remove in the subject line and hit return. ********************************************** From owner-frs-mib@ca.newbridge.com Fri Mar 13 08:16:42 1998 Delivery-Date: Fri, 13 Mar 1998 08:16:42 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id IAA24521 for ; Fri, 13 Mar 1998 08:16:41 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id IAA19785; Fri, 13 Mar 1998 08:15:23 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma019611; Fri Mar 13 08:14:16 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 13 Mar 1998 13:14:16 UT Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id IAA09611; Fri, 13 Mar 1998 08:14:15 -0500 (EST) Received: from distmaster.ca.newbridge.com(138.120.118.27) by kanmaster.ca.newbridge.com via smap (V1.3) id sma009602; Fri Mar 13 08:14:13 1998 Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id IAA10248; Fri, 13 Mar 1998 08:12:59 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id IAA10240; Fri, 13 Mar 1998 08:12:54 -0500 Received: (from smap@localhost) by ca.newbridge.com. (8.8.6/8.8.6) id IAA09028 for ; Fri, 13 Mar 1998 08:12:08 -0500 (EST) Received: from kanata-gw.ca.newbridge.com(138.120.49.2) by kanmaster.ca.newbridge.com via smap (V1.3) id sma008996; Fri Mar 13 08:11:53 1998 Received: from ns.newbridge.com ([192.75.23.67]) by kanata-gw.ca.newbridge.com via smtpd (for kanmaster.ca.newbridge.com [138.120.124.4]) with SMTP; 13 Mar 1998 13:11:53 UT Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id IAA19376 for ; Fri, 13 Mar 1998 08:11:53 -0500 (EST) Received: from ietf.org(132.151.1.19) by ns.newbridge.com via smap (V1.3) id sma019311; Fri Mar 13 08:10:52 1998 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id IAA24264; Fri, 13 Mar 1998 08:10:46 -0500 (EST) Message-Id: <199803131310.IAA24264@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: frs-mib@ca.newbridge.com From: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-frnetmib-spvc-01.txt Date: Fri, 13 Mar 1998 08:10:46 -0500 Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Frame Relay Service MIB Working Group of the IETF. Title : Frame Relay Switched PVC MIB Author(s) : B. Coutts Filename : draft-ietf-frnetmib-spvc-01.txt Pages : 19 Date : 12-Mar-98 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP- based internets. In particular, it defines objects for managing Frame Relay Switched Permanent Virtual Circuits (SPVCs). Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-frnetmib-spvc-01.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-frnetmib-spvc-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-frnetmib-spvc-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980312181039.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-frnetmib-spvc-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-frnetmib-spvc-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980312181039.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Fri Mar 13 10:06:33 1998 Delivery-Date: Fri, 13 Mar 1998 10:09:31 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id KAA01832 for ietf-123-outbound.10@ietf.org; Fri, 13 Mar 1998 10:05:05 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id IAA24264; Fri, 13 Mar 1998 08:10:46 -0500 (EST) Message-Id: <199803131310.IAA24264@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: frs-mib@newbridge.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-frnetmib-spvc-01.txt Date: Fri, 13 Mar 1998 08:10:46 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Frame Relay Service MIB Working Group of the IETF. Title : Frame Relay Switched PVC MIB Author(s) : B. Coutts Filename : draft-ietf-frnetmib-spvc-01.txt Pages : 19 Date : 12-Mar-98 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP- based internets. In particular, it defines objects for managing Frame Relay Switched Permanent Virtual Circuits (SPVCs). Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-frnetmib-spvc-01.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-frnetmib-spvc-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-frnetmib-spvc-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980312181039.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-frnetmib-spvc-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-frnetmib-spvc-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980312181039.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-frs-mib@ca.newbridge.com Fri Apr 3 14:43:04 1998 Delivery-Date: Fri, 03 Apr 1998 14:43:05 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id OAA03071 for ; Fri, 3 Apr 1998 14:43:03 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id OAA04175; Fri, 3 Apr 1998 14:41:42 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma004096; Fri Apr 3 14:41:20 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 3 Apr 1998 19:41:20 UT Received: from distmaster.ca.newbridge.com (distmaster.ca.newbridge.com [138.120.118.27]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id OAA07583; Fri, 3 Apr 1998 14:41:19 -0500 (EST) Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id OAA09605; Fri, 3 Apr 1998 14:39:39 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id OAA09597; Fri, 3 Apr 1998 14:39:34 -0500 Received: from kanata-gw.ca.newbridge.com (kanata-gw.ca.newbridge.com [138.120.49.2]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id OAA07244 for ; Fri, 3 Apr 1998 14:38:53 -0500 (EST) Received: from ns.newbridge.com ([192.75.23.67]) by kanata-gw.ca.newbridge.com via smtpd (for kanmaster.ca.newbridge.com [138.120.124.4]) with SMTP; 3 Apr 1998 19:38:53 UT Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id OAA03863 for ; Fri, 3 Apr 1998 14:38:52 -0500 (EST) Received: from services2.paradyne.com(135.90.253.91) by ns.newbridge.com via smap (V1.3) id sma003759; Fri Apr 3 14:38:29 1998 Received: from hermes.eng.paradyne.com ([135.26.1.14]) by services2.paradyne.com (Netscape Messaging Server 3.5) with ESMTP id AAA1E9F; Fri, 3 Apr 1998 14:38:14 -0500 Received: from eng.paradyne.com (moray.eng.paradyne.com [135.26.4.21]) by hermes.eng.paradyne.com (8.7.5/8.7.3) with ESMTP id OAA03334; Fri, 3 Apr 1998 14:38:11 -0500 (EST) Message-ID: <35253AA2.7BAB602F@eng.paradyne.com> Date: Fri, 03 Apr 1998 14:38:10 -0500 From: Rob Steinberger Organization: Paradyne Corporation X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@ca.newbridge.com Subject: ifSpeed on T1 and Frame Relay Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM All, Sorry if this has been discussed in the IETF before, but it has become a hot topic locally. Should the ifSpeed for a T1 interface be 1.54Mb or should it be 3.08Mb in that it can sustain 1.54Mb in both the transmit and receive directions. The same question holds for frame relay. We are currently reporting the number of DS0s times the rate of each DS0. Should this be twice this number to account for its full duplex nature? Thanks for any responses. Rob Steinberger Paradyne Corporation From ras@eng.paradyne.com Fri Apr 3 14:52:18 1998 Delivery-Date: Fri, 03 Apr 1998 14:52:18 -0500 Return-Path: ras@eng.paradyne.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id OAA03119 for ; Fri, 3 Apr 1998 14:52:17 -0500 (EST) Received: from pleco.cisco.com (pleco.cisco.com [171.69.30.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id OAA10118 for ; Fri, 3 Apr 1998 14:54:34 -0500 (EST) Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by pleco.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id LAA28500 for ; Fri, 3 Apr 1998 11:47:59 -0800 (PST) Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id LAA25068 for ; Fri, 3 Apr 1998 11:47:58 -0800 (PST) Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id LAA11082 for ; Fri, 3 Apr 1998 11:47:58 -0800 (PST) Received: from services2.paradyne.com(135.90.253.91) by proxy3.cisco.com via smap (V2.0) id xma011077; Fri, 3 Apr 98 19:47:54 GMT Received: from hermes.eng.paradyne.com ([135.26.1.14]) by services2.paradyne.com (Netscape Messaging Server 3.5) with ESMTP id AAA1E9F; Fri, 3 Apr 1998 14:38:14 -0500 Received: from eng.paradyne.com (moray.eng.paradyne.com [135.26.4.21]) by hermes.eng.paradyne.com (8.7.5/8.7.3) with ESMTP id OAA03334; Fri, 3 Apr 1998 14:38:11 -0500 (EST) Sender: ras@eng.paradyne.com Message-ID: <35253AA2.7BAB602F@eng.paradyne.com> Date: Fri, 03 Apr 1998 14:38:10 -0500 From: Rob Steinberger Organization: Paradyne Corporation X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@newbridge.com Subject: ifSpeed on T1 and Frame Relay Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit All, Sorry if this has been discussed in the IETF before, but it has become a hot topic locally. Should the ifSpeed for a T1 interface be 1.54Mb or should it be 3.08Mb in that it can sustain 1.54Mb in both the transmit and receive directions. The same question holds for frame relay. We are currently reporting the number of DS0s times the rate of each DS0. Should this be twice this number to account for its full duplex nature? Thanks for any responses. Rob Steinberger Paradyne Corporation From owner-if-mib@padauk.vnd.tek.com Fri Apr 3 15:04:05 1998 Delivery-Date: Fri, 03 Apr 1998 15:04:05 -0500 Return-Path: owner-if-mib@padauk.vnd.tek.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id PAA03233 for ; Fri, 3 Apr 1998 15:04:04 -0500 (EST) Received: from fw1.tek.com (fw1.tek.com [192.65.17.16]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA20471 for ; Fri, 3 Apr 1998 15:06:35 -0500 (EST) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id MAA08646 for ; Fri, 3 Apr 1998 12:04:05 -0800 (PST) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.189.46]) by fw1.tek.com with ESMTP id MAA08642 for ; Fri, 3 Apr 1998 12:04:05 -0800 (PST) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id MAA20525 for if-mib-outgoing; Fri, 3 Apr 1998 12:02:15 -0800 (PST) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Message-ID: <35253AA2.7BAB602F@eng.paradyne.com> Date: Fri, 03 Apr 1998 14:38:10 -0500 From: Rob Steinberger Organization: Paradyne Corporation X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@newbridge.com Subject: ifSpeed on T1 and Frame Relay Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-if-mib@vnd.tek.com Precedence: bulk All, Sorry if this has been discussed in the IETF before, but it has become a hot topic locally. Should the ifSpeed for a T1 interface be 1.54Mb or should it be 3.08Mb in that it can sustain 1.54Mb in both the transmit and receive directions. The same question holds for frame relay. We are currently reporting the number of DS0s times the rate of each DS0. Should this be twice this number to account for its full duplex nature? Thanks for any responses. Rob Steinberger Paradyne Corporation From owner-frs-mib@ca.newbridge.com Fri Apr 3 15:30:05 1998 Delivery-Date: Fri, 03 Apr 1998 15:30:05 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id PAA03519 for ; Fri, 3 Apr 1998 15:30:04 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id PAA09797; Fri, 3 Apr 1998 15:28:23 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma009728; Fri Apr 3 15:27:44 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 3 Apr 1998 20:27:44 UT Received: from distmaster.ca.newbridge.com (distmaster.ca.newbridge.com [138.120.118.27]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id PAA14792; Fri, 3 Apr 1998 15:27:44 -0500 (EST) Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id PAA09918; Fri, 3 Apr 1998 15:27:28 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id PAA09910; Fri, 3 Apr 1998 15:27:23 -0500 Received: from kanata-gw.ca.newbridge.com (kanata-gw.ca.newbridge.com [138.120.49.2]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id PAA14538 for ; Fri, 3 Apr 1998 15:26:30 -0500 (EST) Received: from ns.newbridge.com ([192.75.23.67]) by kanata-gw.ca.newbridge.com via smtpd (for kanmaster.ca.newbridge.com [138.120.124.4]) with SMTP; 3 Apr 1998 20:25:21 UT Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id PAA09459 for ; Fri, 3 Apr 1998 15:25:21 -0500 (EST) Received: from kentrox.kentrox.com(192.228.59.2) by ns.newbridge.com via smap (V1.3) id sma009392; Fri Apr 3 15:24:50 1998 Received: from kentrox.com by kentrox.com (Smail-3.2.0.91 1997-Jan-14 #1) id ; Fri, 3 Apr 1998 12:20:52 -0800 (PST) Received: from localhost by kentrox.com (4.1/SMI-4.1_KTX1.1) id AA03476; Fri, 3 Apr 98 12:20:49 PST Date: Fri, 3 Apr 1998 12:20:49 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Rob Steinberger Cc: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@ca.newbridge.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: <35253AA2.7BAB602F@eng.paradyne.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM Rob, On Fri, 3 Apr 1998, Rob Steinberger wrote: > All, > > Sorry if this has been discussed in the IETF before, but it has become > a hot topic locally. > > Should the ifSpeed for a T1 interface be 1.54Mb or should it be 3.08Mb > in that it can sustain 1.54Mb in both the transmit and receive The latest for the DS1-MIB is unambiguous on this point. In section 3.1 it says to use 1544000 for the ifSpeed for DS1 lines. > directions. The same question holds for frame relay. We are If a ds1(18) interface is used for Frame Relay, its ifSpeed will still always be 1544000. RFC 2115 says that the frameRelay(32) interface's ifSpeed is the "access rate for the frame relay interface" and then goes on to say that this "could be different from the speed of the underlying physical interface, e.g. in a fractional T1 case the access rate could be 384 kbits/s". For a bundle of N DS0s, this would thus be N x 64000. Although the latest for the DS0-MIB and DS0BUNDLE-MIB does not clarify what ifSpeed should be for the ds0Bundle(82) interface, I would assume in a bundled-DS0 case, the ifSpeed of the ds0Bundle interface would be the same as the frameRelay interface. And, of course, the ifSpeed of each ds0 would be 64000, again per the latest draft. > currently reporting the number of DS0s times the rate of each DS0. > Should this be twice this number to account for its full duplex > nature? No. > Thanks for any responses. > > Rob Steinberger > Paradyne Corporation I hope this helps. Regards, Gary From gary@kentrox.com Fri Apr 3 15:30:36 1998 Delivery-Date: Fri, 03 Apr 1998 15:30:36 -0500 Return-Path: gary@kentrox.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id PAA03529 for ; Fri, 3 Apr 1998 15:30:36 -0500 (EST) Received: from beasley.cisco.com (mailgate-sj-2.cisco.com [171.69.2.135]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA14025 for ; Fri, 3 Apr 1998 15:33:07 -0500 (EST) Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89]) by beasley.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id MAA09895 for ; Fri, 3 Apr 1998 12:24:47 -0800 (PST) Received: (from smap@localhost) by proxy2.cisco.com (8.8.7/8.8.5) id MAA04822 for ; Fri, 3 Apr 1998 12:24:45 -0800 (PST) Received: from kentrox.kentrox.com(192.228.59.2) by proxy2.cisco.com via smap (V2.0) id xma004811; Fri, 3 Apr 98 20:24:41 GMT Received: from kentrox.com by kentrox.com (Smail-3.2.0.91 1997-Jan-14 #1) id ; Fri, 3 Apr 1998 12:20:52 -0800 (PST) Received: from localhost by kentrox.com (4.1/SMI-4.1_KTX1.1) id AA03476; Fri, 3 Apr 98 12:20:49 PST Date: Fri, 3 Apr 1998 12:20:49 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Rob Steinberger Cc: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@newbridge.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: <35253AA2.7BAB602F@eng.paradyne.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Rob, On Fri, 3 Apr 1998, Rob Steinberger wrote: > All, > > Sorry if this has been discussed in the IETF before, but it has become > a hot topic locally. > > Should the ifSpeed for a T1 interface be 1.54Mb or should it be 3.08Mb > in that it can sustain 1.54Mb in both the transmit and receive The latest for the DS1-MIB is unambiguous on this point. In section 3.1 it says to use 1544000 for the ifSpeed for DS1 lines. > directions. The same question holds for frame relay. We are If a ds1(18) interface is used for Frame Relay, its ifSpeed will still always be 1544000. RFC 2115 says that the frameRelay(32) interface's ifSpeed is the "access rate for the frame relay interface" and then goes on to say that this "could be different from the speed of the underlying physical interface, e.g. in a fractional T1 case the access rate could be 384 kbits/s". For a bundle of N DS0s, this would thus be N x 64000. Although the latest for the DS0-MIB and DS0BUNDLE-MIB does not clarify what ifSpeed should be for the ds0Bundle(82) interface, I would assume in a bundled-DS0 case, the ifSpeed of the ds0Bundle interface would be the same as the frameRelay interface. And, of course, the ifSpeed of each ds0 would be 64000, again per the latest draft. > currently reporting the number of DS0s times the rate of each DS0. > Should this be twice this number to account for its full duplex > nature? No. > Thanks for any responses. > > Rob Steinberger > Paradyne Corporation I hope this helps. Regards, Gary From owner-frs-mib@ca.newbridge.com Fri Apr 3 15:31:30 1998 Delivery-Date: Fri, 03 Apr 1998 15:31:30 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id PAA03545 for ; Fri, 3 Apr 1998 15:31:29 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id PAA10017; Fri, 3 Apr 1998 15:29:39 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma009898; Fri Apr 3 15:29:12 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 3 Apr 1998 20:29:12 UT Received: from distmaster.ca.newbridge.com (distmaster.ca.newbridge.com [138.120.118.27]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id PAA15081; Fri, 3 Apr 1998 15:29:11 -0500 (EST) Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id PAA09937; Fri, 3 Apr 1998 15:29:29 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id PAA09929; Fri, 3 Apr 1998 15:29:25 -0500 Received: from kanata-gw.ca.newbridge.com (kanata-gw.ca.newbridge.com [138.120.49.2]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id PAA15022 for ; Fri, 3 Apr 1998 15:28:43 -0500 (EST) Received: from ns.newbridge.com ([192.75.23.67]) by kanata-gw.ca.newbridge.com via smtpd (for kanmaster.ca.newbridge.com [138.120.124.4]) with SMTP; 3 Apr 1998 20:28:43 UT Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id PAA09878 for ; Fri, 3 Apr 1998 15:28:42 -0500 (EST) Received: from kentrox.kentrox.com(192.228.59.2) by ns.newbridge.com via smap (V1.3) id sma009784; Fri Apr 3 15:28:20 1998 Received: from kentrox.com by kentrox.com (Smail-3.2.0.91 1997-Jan-14 #1) id ; Fri, 3 Apr 1998 12:28:12 -0800 (PST) Received: from localhost by kentrox.com (4.1/SMI-4.1_KTX1.1) id AA03479; Fri, 3 Apr 98 12:28:10 PST Date: Fri, 3 Apr 1998 12:28:10 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Rob Steinberger Cc: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@ca.newbridge.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM Oops, I just mistakenly wrote the following: > [...] > Although the latest for the > DS0-MIB and DS0BUNDLE-MIB does not clarify what ifSpeed should be > for the ds0Bundle(82) interface, I would assume in a bundled-DS0 > case, the ifSpeed of the ds0Bundle interface would be the same as > the frameRelay interface. Section 3.2 says it clear as day: "n * 64000 for ds0Bundle". I had looked but must have blinked at the wrong moment.... Regards, Gary From owner-if-mib@padauk.vnd.tek.com Fri Apr 3 15:32:47 1998 Delivery-Date: Fri, 03 Apr 1998 15:32:47 -0500 Return-Path: owner-if-mib@padauk.vnd.tek.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id PAA03558 for ; Fri, 3 Apr 1998 15:32:45 -0500 (EST) Received: from fw1.tek.com (fw1.tek.com [192.65.17.16]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA16037 for ; Fri, 3 Apr 1998 15:35:17 -0500 (EST) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id MAA12048 for ; Fri, 3 Apr 1998 12:32:40 -0800 (PST) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.189.46]) by fw1.tek.com with ESMTP id MAA12044 for ; Fri, 3 Apr 1998 12:32:39 -0800 (PST) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id MAA20944 for if-mib-outgoing; Fri, 3 Apr 1998 12:32:25 -0800 (PST) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Date: Fri, 3 Apr 1998 12:20:49 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Rob Steinberger Cc: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@newbridge.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: <35253AA2.7BAB602F@eng.paradyne.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-if-mib@vnd.tek.com Precedence: bulk Rob, On Fri, 3 Apr 1998, Rob Steinberger wrote: > All, > > Sorry if this has been discussed in the IETF before, but it has become > a hot topic locally. > > Should the ifSpeed for a T1 interface be 1.54Mb or should it be 3.08Mb > in that it can sustain 1.54Mb in both the transmit and receive The latest for the DS1-MIB is unambiguous on this point. In section 3.1 it says to use 1544000 for the ifSpeed for DS1 lines. > directions. The same question holds for frame relay. We are If a ds1(18) interface is used for Frame Relay, its ifSpeed will still always be 1544000. RFC 2115 says that the frameRelay(32) interface's ifSpeed is the "access rate for the frame relay interface" and then goes on to say that this "could be different from the speed of the underlying physical interface, e.g. in a fractional T1 case the access rate could be 384 kbits/s". For a bundle of N DS0s, this would thus be N x 64000. Although the latest for the DS0-MIB and DS0BUNDLE-MIB does not clarify what ifSpeed should be for the ds0Bundle(82) interface, I would assume in a bundled-DS0 case, the ifSpeed of the ds0Bundle interface would be the same as the frameRelay interface. And, of course, the ifSpeed of each ds0 would be 64000, again per the latest draft. > currently reporting the number of DS0s times the rate of each DS0. > Should this be twice this number to account for its full duplex > nature? No. > Thanks for any responses. > > Rob Steinberger > Paradyne Corporation I hope this helps. Regards, Gary From gary@kentrox.com Fri Apr 3 15:33:59 1998 Delivery-Date: Fri, 03 Apr 1998 15:34:00 -0500 Return-Path: gary@kentrox.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id PAA03567 for ; Fri, 3 Apr 1998 15:33:59 -0500 (EST) Received: from rhine.cisco.com (rhine.cisco.com [171.69.43.21]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA17159 for ; Fri, 3 Apr 1998 15:36:29 -0500 (EST) Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by rhine.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id MAA02042 for ; Fri, 3 Apr 1998 12:28:43 -0800 (PST) Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id MAA01184 for ; Fri, 3 Apr 1998 12:28:27 -0800 (PST) Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id MAA17055 for ; Fri, 3 Apr 1998 12:28:18 -0800 (PST) Received: from kentrox.kentrox.com(192.228.59.2) by proxy3.cisco.com via smap (V2.0) id xma017050; Fri, 3 Apr 98 20:28:14 GMT Received: from kentrox.com by kentrox.com (Smail-3.2.0.91 1997-Jan-14 #1) id ; Fri, 3 Apr 1998 12:28:12 -0800 (PST) Received: from localhost by kentrox.com (4.1/SMI-4.1_KTX1.1) id AA03479; Fri, 3 Apr 98 12:28:10 PST Date: Fri, 3 Apr 1998 12:28:10 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Rob Steinberger Cc: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@newbridge.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Oops, I just mistakenly wrote the following: > [...] > Although the latest for the > DS0-MIB and DS0BUNDLE-MIB does not clarify what ifSpeed should be > for the ds0Bundle(82) interface, I would assume in a bundled-DS0 > case, the ifSpeed of the ds0Bundle interface would be the same as > the frameRelay interface. Section 3.2 says it clear as day: "n * 64000 for ds0Bundle". I had looked but must have blinked at the wrong moment.... Regards, Gary From owner-if-mib@padauk.vnd.tek.com Fri Apr 3 15:42:22 1998 Delivery-Date: Fri, 03 Apr 1998 15:42:22 -0500 Return-Path: owner-if-mib@padauk.vnd.tek.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id PAA03663 for ; Fri, 3 Apr 1998 15:42:21 -0500 (EST) Received: from fw1.tek.com (fw1.tek.com [192.65.17.16]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA24616 for ; Fri, 3 Apr 1998 15:44:53 -0500 (EST) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id MAA13739 for ; Fri, 3 Apr 1998 12:42:24 -0800 (PST) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.189.46]) by fw1.tek.com with ESMTP id MAA13735 for ; Fri, 3 Apr 1998 12:42:24 -0800 (PST) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id MAA21224 for if-mib-outgoing; Fri, 3 Apr 1998 12:41:52 -0800 (PST) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Date: Fri, 3 Apr 1998 12:28:10 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Rob Steinberger Cc: if-mib@vnd.tek.com, trunk-mib@external.cisco.com, frs-mib@newbridge.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-if-mib@vnd.tek.com Precedence: bulk Oops, I just mistakenly wrote the following: > [...] > Although the latest for the > DS0-MIB and DS0BUNDLE-MIB does not clarify what ifSpeed should be > for the ds0Bundle(82) interface, I would assume in a bundled-DS0 > case, the ifSpeed of the ds0Bundle interface would be the same as > the frameRelay interface. Section 3.2 says it clear as day: "n * 64000 for ds0Bundle". I had looked but must have blinked at the wrong moment.... Regards, Gary From owner-frs-mib@ca.newbridge.com Fri Apr 3 17:21:17 1998 Delivery-Date: Fri, 03 Apr 1998 17:21:17 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id RAA04440 for ; Fri, 3 Apr 1998 17:21:15 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id RAA21565; Fri, 3 Apr 1998 17:17:40 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma021540; Fri Apr 3 17:17:05 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 3 Apr 1998 22:17:04 UT Received: from distmaster.ca.newbridge.com (distmaster.ca.newbridge.com [138.120.118.27]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id RAA27946; Fri, 3 Apr 1998 17:17:04 -0500 (EST) Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id RAA10449; Fri, 3 Apr 1998 17:16:36 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id RAA10441; Fri, 3 Apr 1998 17:16:28 -0500 Received: from fennel.acc.com (fennel.acc.com [129.192.64.25]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id RAA27830 for ; Fri, 3 Apr 1998 17:15:43 -0500 (EST) Received: from opal.acc.com.acc by fennel.acc.com (4.1/SMI-4.1) id AA08780; Fri, 3 Apr 98 14:14:50 PST Date: Fri, 3 Apr 98 14:14:50 PST From: art@acc.com (Art Berggreen) Message-Id: <9804032214.AA08780@fennel.acc.com> To: gary@kentrox.com, ras@eng.paradyne.com Subject: Re: ifSpeed on T1 and Frame Relay Cc: frs-mib@ca.newbridge.com, if-mib@vnd.tek.com, trunk-mib@external.cisco.com Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM > >The latest for the DS1-MIB is >unambiguous on this point. In section 3.1 it says to use 1544000 >for the ifSpeed for DS1 lines. > >> directions. The same question holds for frame relay. We are > >If a ds1(18) interface is used for Frame Relay, its ifSpeed will >still always be 1544000. > >RFC 2115 says that the frameRelay(32) interface's ifSpeed is the >"access rate for the frame relay interface" and then goes on to >say that this "could be different from the speed of the underlying >physical interface, e.g. in a fractional T1 case the access rate >could be 384 kbits/s". For a bundle of N DS0s, this would thus be > N x 64000. Interestingly, most T1s run channelized with a maximum user information rate of 24X64000=1536000. Signalling and ones density often reduce this to 24X56000=1344000. The mib definition specifies the interface "bandwidth", which sure sounds like user useable bandwidth to me. But 1.544mb/s is probably too entrenched with the concept of T1s to ever change this detail. Art From art@acc.com Fri Apr 3 17:24:28 1998 Delivery-Date: Fri, 03 Apr 1998 17:24:28 -0500 Return-Path: art@acc.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id RAA04459 for ; Fri, 3 Apr 1998 17:24:22 -0500 (EST) Received: from beasley.cisco.com (mailgate-sj-2.cisco.com [171.69.2.135]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA24743 for ; Fri, 3 Apr 1998 17:26:54 -0500 (EST) Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by beasley.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id OAA27075 for ; Fri, 3 Apr 1998 14:20:09 -0800 (PST) Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id OAA04106 for ; Fri, 3 Apr 1998 14:20:08 -0800 (PST) Received: from fennel.acc.com(129.192.64.25) by proxy3.cisco.com via smap (V2.0) id xma004076; Fri, 3 Apr 98 22:20:03 GMT Received: from opal.acc.com.acc by fennel.acc.com (4.1/SMI-4.1) id AA08780; Fri, 3 Apr 98 14:14:50 PST Date: Fri, 3 Apr 98 14:14:50 PST From: art@acc.com (Art Berggreen) Message-Id: <9804032214.AA08780@fennel.acc.com> To: gary@kentrox.com, ras@eng.paradyne.com Subject: Re: ifSpeed on T1 and Frame Relay Cc: frs-mib@newbridge.com, if-mib@vnd.tek.com, trunk-mib@external.cisco.com > >The latest for the DS1-MIB is >unambiguous on this point. In section 3.1 it says to use 1544000 >for the ifSpeed for DS1 lines. > >> directions. The same question holds for frame relay. We are > >If a ds1(18) interface is used for Frame Relay, its ifSpeed will >still always be 1544000. > >RFC 2115 says that the frameRelay(32) interface's ifSpeed is the >"access rate for the frame relay interface" and then goes on to >say that this "could be different from the speed of the underlying >physical interface, e.g. in a fractional T1 case the access rate >could be 384 kbits/s". For a bundle of N DS0s, this would thus be > N x 64000. Interestingly, most T1s run channelized with a maximum user information rate of 24X64000=1536000. Signalling and ones density often reduce this to 24X56000=1344000. The mib definition specifies the interface "bandwidth", which sure sounds like user useable bandwidth to me. But 1.544mb/s is probably too entrenched with the concept of T1s to ever change this detail. Art From owner-if-mib@padauk.vnd.tek.com Fri Apr 3 17:33:29 1998 Delivery-Date: Fri, 03 Apr 1998 17:33:29 -0500 Return-Path: owner-if-mib@padauk.vnd.tek.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id RAA04537 for ; Fri, 3 Apr 1998 17:33:28 -0500 (EST) Received: from fw1.tek.com (fw1.tek.com [192.65.17.16]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA03161 for ; Fri, 3 Apr 1998 17:36:00 -0500 (EST) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id OAA27364 for ; Fri, 3 Apr 1998 14:33:29 -0800 (PST) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.189.46]) by fw1.tek.com with ESMTP id OAA27264 for ; Fri, 3 Apr 1998 14:33:24 -0800 (PST) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id OAA27185 for if-mib-outgoing; Fri, 3 Apr 1998 14:32:35 -0800 (PST) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Date: Fri, 3 Apr 98 14:14:50 PST From: art@acc.com (Art Berggreen) Message-Id: <9804032214.AA08780@fennel.acc.com> To: gary@kentrox.com, ras@eng.paradyne.com Subject: Re: ifSpeed on T1 and Frame Relay Cc: frs-mib@newbridge.com, if-mib@vnd.tek.com, trunk-mib@external.cisco.com Sender: owner-if-mib@vnd.tek.com Precedence: bulk > >The latest for the DS1-MIB is >unambiguous on this point. In section 3.1 it says to use 1544000 >for the ifSpeed for DS1 lines. > >> directions. The same question holds for frame relay. We are > >If a ds1(18) interface is used for Frame Relay, its ifSpeed will >still always be 1544000. > >RFC 2115 says that the frameRelay(32) interface's ifSpeed is the >"access rate for the frame relay interface" and then goes on to >say that this "could be different from the speed of the underlying >physical interface, e.g. in a fractional T1 case the access rate >could be 384 kbits/s". For a bundle of N DS0s, this would thus be > N x 64000. Interestingly, most T1s run channelized with a maximum user information rate of 24X64000=1536000. Signalling and ones density often reduce this to 24X56000=1344000. The mib definition specifies the interface "bandwidth", which sure sounds like user useable bandwidth to me. But 1.544mb/s is probably too entrenched with the concept of T1s to ever change this detail. Art From owner-frs-mib@ca.newbridge.com Fri Apr 3 19:04:19 1998 Delivery-Date: Fri, 03 Apr 1998 19:04:19 -0500 Return-Path: owner-frs-mib@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id TAA05045 for ; Fri, 3 Apr 1998 19:04:18 -0500 (EST) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id TAA29683; Fri, 3 Apr 1998 19:02:47 -0500 (EST) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma029673; Fri Apr 3 19:02:27 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 4 Apr 1998 00:02:27 UT Received: from distmaster.ca.newbridge.com (distmaster.ca.newbridge.com [138.120.118.27]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id TAA05882; Fri, 3 Apr 1998 19:02:26 -0500 (EST) Received: by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id TAA10928; Fri, 3 Apr 1998 19:02:19 -0500 Received: from ca.newbridge.com. by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id TAA10920; Fri, 3 Apr 1998 19:02:15 -0500 Received: from kanata-gw.ca.newbridge.com (kanata-gw.ca.newbridge.com [138.120.49.2]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id TAA05835 for ; Fri, 3 Apr 1998 19:01:34 -0500 (EST) Received: from ns.newbridge.com ([192.75.23.67]) by kanata-gw.ca.newbridge.com via smtpd (for kanmaster.ca.newbridge.com [138.120.124.4]) with SMTP; 4 Apr 1998 00:01:34 UT Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id TAA29623 for ; Fri, 3 Apr 1998 19:01:34 -0500 (EST) Received: from kentrox.kentrox.com(192.228.59.2) by ns.newbridge.com via smap (V1.3) id sma029608; Fri Apr 3 19:01:15 1998 Received: from kentrox.com by kentrox.com (Smail-3.2.0.91 1997-Jan-14 #1) id ; Fri, 3 Apr 1998 15:57:17 -0800 (PST) Received: from localhost by kentrox.com (4.1/SMI-4.1_KTX1.1) id AA03563; Fri, 3 Apr 98 15:57:15 PST Date: Fri, 3 Apr 1998 15:57:15 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Art Berggreen Cc: ras@eng.paradyne.com, frs-mib@ca.newbridge.com, if-mib@vnd.tek.com, trunk-mib@external.cisco.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: <9804032214.AA08780@fennel.acc.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-frs-mib@Newbridge.COM Precedence: bulk Reply-To: frs-mib@Newbridge.COM Hi Art, On Fri, 3 Apr 1998, Art Berggreen wrote: > [...] > Interestingly, most T1s run channelized with a maximum user information > rate of 24X64000=1536000. Signalling and ones density often reduce this > to 24X56000=1344000. This is certainly true. > The mib definition specifies the interface "bandwidth", which sure sounds > like user useable bandwidth to me. I agree. However, the bandwidth usable here is that usable by the DS1 signal itself, which is 1544000. The higher layers, of course, cannot use all of this bandwidth, and thus they have a lower ifSpeed value to report for themselves. > But 1.544mb/s is probably too entrenched with the concept of T1s to > ever change this detail. It certainly is an entrenched value, but that would not be a detail that I would change. Keeping it the way it is allows the various levels of the stack to report the bandwidth that they see "below" them (the bandwidth available to them, if you will). I would expect my DS1 physical links to report its ds1 interface ifSpeed with the full DS1 bit rate. > Art Regards, Gary From gary@kentrox.com Fri Apr 3 19:05:05 1998 Delivery-Date: Fri, 03 Apr 1998 19:05:05 -0500 Return-Path: gary@kentrox.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id TAA05064 for ; Fri, 3 Apr 1998 19:05:04 -0500 (EST) Received: from rhine.cisco.com (rhine.cisco.com [171.69.43.21]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id TAA24599 for ; Fri, 3 Apr 1998 19:07:34 -0500 (EST) Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by rhine.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id QAA05351 for ; Fri, 3 Apr 1998 16:01:16 -0800 (PST) Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id QAA05658 for ; Fri, 3 Apr 1998 16:01:16 -0800 (PST) Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id QAA18674 for ; Fri, 3 Apr 1998 16:01:15 -0800 (PST) Received: from kentrox.kentrox.com(192.228.59.2) by proxy3.cisco.com via smap (V2.0) id xma018646; Sat, 4 Apr 98 00:01:12 GMT Received: from kentrox.com by kentrox.com (Smail-3.2.0.91 1997-Jan-14 #1) id ; Fri, 3 Apr 1998 15:57:17 -0800 (PST) Received: from localhost by kentrox.com (4.1/SMI-4.1_KTX1.1) id AA03563; Fri, 3 Apr 98 15:57:15 PST Date: Fri, 3 Apr 1998 15:57:15 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Art Berggreen Cc: ras@eng.paradyne.com, frs-mib@newbridge.com, if-mib@vnd.tek.com, trunk-mib@external.cisco.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: <9804032214.AA08780@fennel.acc.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi Art, On Fri, 3 Apr 1998, Art Berggreen wrote: > [...] > Interestingly, most T1s run channelized with a maximum user information > rate of 24X64000=1536000. Signalling and ones density often reduce this > to 24X56000=1344000. This is certainly true. > The mib definition specifies the interface "bandwidth", which sure sounds > like user useable bandwidth to me. I agree. However, the bandwidth usable here is that usable by the DS1 signal itself, which is 1544000. The higher layers, of course, cannot use all of this bandwidth, and thus they have a lower ifSpeed value to report for themselves. > But 1.544mb/s is probably too entrenched with the concept of T1s to > ever change this detail. It certainly is an entrenched value, but that would not be a detail that I would change. Keeping it the way it is allows the various levels of the stack to report the bandwidth that they see "below" them (the bandwidth available to them, if you will). I would expect my DS1 physical links to report its ds1 interface ifSpeed with the full DS1 bit rate. > Art Regards, Gary From owner-if-mib@padauk.vnd.tek.com Fri Apr 3 19:18:48 1998 Delivery-Date: Fri, 03 Apr 1998 19:18:49 -0500 Return-Path: owner-if-mib@padauk.vnd.tek.com Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id TAA05164 for ; Fri, 3 Apr 1998 19:18:48 -0500 (EST) Received: from fw1.tek.com (fw1.tek.com [192.65.17.16]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id TAA07073 for ; Fri, 3 Apr 1998 19:21:18 -0500 (EST) Received: from fw1.tek.com (root@localhost) by fw1.tek.com with ESMTP id QAA09879 for ; Fri, 3 Apr 1998 16:18:49 -0800 (PST) Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.189.46]) by fw1.tek.com with ESMTP id QAA09875 for ; Fri, 3 Apr 1998 16:18:49 -0800 (PST) Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id QAA23819 for if-mib-outgoing; Fri, 3 Apr 1998 16:17:11 -0800 (PST) X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f Date: Fri, 3 Apr 1998 15:57:15 -0800 (PST) From: Gary Hanson X-Sender: gary@skeeter To: Art Berggreen Cc: ras@eng.paradyne.com, frs-mib@newbridge.com, if-mib@vnd.tek.com, trunk-mib@external.cisco.com Subject: Re: ifSpeed on T1 and Frame Relay In-Reply-To: <9804032214.AA08780@fennel.acc.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-if-mib@vnd.tek.com Precedence: bulk Hi Art, On Fri, 3 Apr 1998, Art Berggreen wrote: > [...] > Interestingly, most T1s run channelized with a maximum user information > rate of 24X64000=1536000. Signalling and ones density often reduce this > to 24X56000=1344000. This is certainly true. > The mib definition specifies the interface "bandwidth", which sure sounds > like user useable bandwidth to me. I agree. However, the bandwidth usable here is that usable by the DS1 signal itself, which is 1544000. The higher layers, of course, cannot use all of this bandwidth, and thus they have a lower ifSpeed value to report for themselves. > But 1.544mb/s is probably too entrenched with the concept of T1s to > ever change this detail. It certainly is an entrenched value, but that would not be a detail that I would change. Keeping it the way it is allows the various levels of the stack to report the bandwidth that they see "below" them (the bandwidth available to them, if you will). I would expect my DS1 physical links to report its ds1 interface ifSpeed with the full DS1 bit rate. > Art Regards, Gary