appn-mib-with-mltg-and-bx.txt
Robert Moore <remoore@us.ibm.com> Wed, 06 August 1997 13:51 UTC
Received: from cnri by ietf.org id aa03106; 6 Aug 97 9:51 EDT
Received: from akita.cisco.com (akita.cisco.com [171.69.223.72]) by cnri.reston.va.us (8.8.5/8.7.3) with SMTPid JAA15947 for <ietf-archive@cnri.reston.va.us>; Wed, 6 Aug 1997 09:49:38 -0400 (EDT)
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by akita.cisco.com (8.6.12/8.6.5) with ESMTP id GAA29096 for <extdom.snanaumib@aliashost.cisco.com>; Wed, 6 Aug 1997 06:33:29 -0700
Received: from lms02.us1.ibm.com (lms02.ny.us.ibm.com [198.133.22.25]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with SMTP id GAA17837 for <snanaumib@external.cisco.com>; Wed, 6 Aug 1997 06:33:28 -0700 (PDT)
Received: from d04lms02.raleigh.ibm.com by lms02.us1.ibm.com (AIX 4.1/UCB 5.64/4.03) id AA220842; Wed, 6 Aug 1997 13:37:10 GMT
Received: by US.IBM.COM (Soft-Switch LMS 2.0) with snapi via D04AU006 id 5040200003930819; Wed, 6 Aug 1997 09:40:37 -0400
From: Robert Moore <remoore@us.ibm.com>
To: "aiw-appn-reference@raleigh.ibm.com"@lms02.us1.ibm.com, snanaumib@external.cisco.com, "aiw-appn-mibs@raleigh.ibm.com"@lms02.us1.ibm.com
MMDF-Warning: Parse error in original version of preceding line at ietf.org
Subject: appn-mib-with-mltg-and-bx.txt
Message-Id: <5040200003930819000002L092*@MHS>
Date: Wed, 06 Aug 1997 09:40:37 -0400
Mime-Version: 1.0
Content-Type: text/plain
I've added the objects from the Branch Extender MIB into the APPN MIB module, and put them out on the AIW FTP site under the filename I've used here as the subject line. (It strikes me that this file-naming strategy scales *very* poorly, but we'll worry about that later:-).) The objects themselves are very straightforward. What took a little more thought was the conformance section. The way I've got it now, a Branch Extender supports some, but not all, of the groups that an ordinary network node supports - for example, since a Branch Extender doesn't participate in topology exchanges, it doesn't support the network topology tables. Take a look at this whole MIB module, and append any comments or questions to these mailing lists. As we move towards AP for the Branch Extender document itself, you should mentally substitute this updated APPN MIB for the Branch Extender MIB that's still in the document. When we re-issue the Branch Extender document for CP, I'll remove that MIB and substitute a pointer to this one. Assuming we get AIW CP approval for these updates to the APPN MIB, I'm still planning to write them up as part of our IBM implementation experience for the APPN MIB, as we try to move it forward to IETF Draft Standard status. This isn't *quite* correct, since our implementation experience so far has involved the objects in their original "home," the Branch Extender MIB. But I don't think we should allow a narrow interpretation of the IETF's procedural rules to keep us from placing these objects where they plainly belong technically. Regards, Bob Network Studies +1-919-254-4436
- appn-mib-with-mltg-and-bx.txt Robert Moore