MIB draft: ifSpeed & ifPhysAddress
kennethw@vnet.ibm.com Fri, 10 May 1996 03:18 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00658; 9 May 96 23:18 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00652; 9 May 96 23:18 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa00340; 9 May 96 23:18 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id XAA21161; Thu, 9 May 1996 23:05:25 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id WAA17112 for ip-atm-out; Thu, 9 May 1996 22:58:11 -0400 (EDT)
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id WAA17103 for <ip-atm@nexen.com>; Thu, 9 May 1996 22:58:05 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: kennethw@vnet.ibm.com
Received: from VNET.IBM.COM (vnet.ibm.com [199.171.26.4]) by nexen.nexen.com (8.7.3/8.7.3) with SMTP id WAA21982 for <ip-atm@nexen.com>; Thu, 9 May 1996 22:57:42 -0400 (EDT)
Message-Id: <199605100257.WAA21982@nexen.nexen.com>
Received: from RALVM12 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 6856; Thu, 09 May 96 22:57:28 EDT
Date: Thu, 09 May 1996 22:57:00 -0400
To: ip-atm@nexen.com
Subject: MIB draft: ifSpeed & ifPhysAddress
X-Orig-Sender: owner-ip-atm@nexen.com
Precedence: bulk
X-Info: Submissions to ip-atm@nexen.com
X-Info: [Un]Subscribe requests to majordomo@nexen.com
X-Info: Archives via http://cell-relay.indiana.edu/cell-relay/archives/IPATM/IPATM.html
John, The IP over ATM Virtual Interface was suppose to be above the AAL5 layer. I didn't think that RFC 1695 was defining the layers above AAL5. A new draft of the IP-ATM MIB will be going out in a few weeks. We will be dropping the IP over ATM Virtual Interface from the MIB since its not absolutely necessary and limit our interface usage to the AAL5 and ATM layers. Please take a look at the new MIB once we distribute it. Regards, Ken White ------------------------------------------------------------------------= Date: Wed, 8 May 1996 16:48:44 +0100 From: John Rickard <jrr@atml.co.uk> To: ip-atm@nexen.com Subject: MIB draft: ifSpeed & ifPhysAddress Sender: owner-ip-atm@nexen.com Precedence: bulk X-Info: Submissions to ip-atm@nexen.com X-Info: [Un]Subscribe requests to majordomo@nexen.com X-Info: Archives via http://cell-relay.indiana.edu/cell-relay/archives/IPATM/IPATM.html I think there may be a mistake in the description of the interface table in the MIB draft. From draft-ietf-ipatm-mib-01.txt: > 5.2.1.1.1. IP over ATM Virtual Interface > [...] > o ifSpeed - This is the total bandwidth in bits per > second. ifHighSpeed is the speed of the > interface in 1,000,000 bits per second units. > This value will be the same as what is > provided at the AAL5 layer. [...] > o ifPhysAddress - The ATM Port's complete physical address. > This value will be the same as what is > provided at the AAL5 layer. From RFC 1695: > 8.3. Support of AAL5 by ifTable > [...] > Object Use for AAL5 CPCS layer entity > ====== ============================== [...] > ifSpeed Set to 0. [...] > ifPhysAddress An octet string of zero length. Is ifSpeed for an IP over ATM Virtual Interface always going to be 0 and ifPhysAddress always empty, or is the rule in RFC 1695 expected to be changed, or am I misunderstanding something, or is this a mistake in the draft? (According to RFC 1695, non-trivial values of ifSpeed and ifPhysAddress, if available, are supplied at the layer below AAL5: either the ATM cell layer or, in a switch, the proprietary virtual, internal interface.) -- John Rickard
- MIB draft: ifSpeed & ifPhysAddress John Rickard
- MIB draft: ifSpeed & ifPhysAddress kennethw