SNA NAU WG charter, DLUR and HPR MIB progrss

"R.E. (Robert) Moore (254-4436)" <REMOORE@ralvm6.vnet.ibm.com> Fri, 09 May 1997 17:03 UTC

Received: from cnri by ietf.org id aa06682; 9 May 97 13:03 EDT
Received: from brittany.cisco.com by CNRI.Reston.VA.US id aa16007; 9 May 97 13:03 EDT
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by brittany.cisco.com (8.6.12/8.6.5) with ESMTP id JAA14650 for <extdom.snanaumib@aliashost.cisco.com>; Fri, 9 May 1997 09:53:09 -0700
Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with SMTP id JAA17301 for <snanaumib@external.cisco.com>; Fri, 9 May 1997 09:53:07 -0700 (PDT)
Message-Id: <199705091653.JAA17301@hubbub.cisco.com>
Received: from RALVM6 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 6375; Fri, 09 May 97 12:53:04 EDT
Date: Fri, 09 May 1997 12:52:55 -0400
From: "R.E. (Robert) Moore (254-4436)" <REMOORE@ralvm6.vnet.ibm.com>
To: jhalpern@newbridge.com
cc: snanaumib@external.cisco.com, rpresuhn@peer.com
Subject: SNA NAU WG charter, DLUR and HPR MIB progrss

Hi Joel,

I've gotten agreement from the WG on the updates to our charter I
sent our a few weeks ago.  I'm attaching it again at the bottom of
this note, since I believe you said that the next step is yours.

I guess you saw that we got Randy's comments back on our updates
to the DLUR and HPR MIB.  Since the DLUR MIB comments are so minor,
and since they raise no issues that would affect WG consensus, I
think we can move on to the next stage.  We'll have an updated
draft-ietf-snanau-dlurmib-02.txt available on Monday.  Once this
is posted as an Internet-Draft, what happens next?  If we need a
WG last call, let's say that this note is it:  unless we hear
something to the contrary by May 19, we'll assume that there's
WG consensus on draft-ietf-snanau-dlurmib-02.txt.  At that point,
what more will you need from me / us before you can take the
DLUR MIB forward to the IESG?

The HPR MIB's situation is a little more complicated, since it's
caught up in the RFC 190x versus SMICng controversy about how
the BITS construct should be handled.  (I don't think we'll have
any trouble with any of Randy's other comments.)  Now I can
certainly perform the dance of:

   - validating the MIB (with an IMPORT for BITS) with SMICng
   - removing the IMPORT for BITS before the MIB is published.

But this is really pretty silly.  Since IBM is one of Dave Perkins'
customers for SMICng, I'm going to express to him that we're
really not very satisfied with this situation.  (I can't fault
Randy here:  his role is to make sure our MIBs comply with
the SNMPv2 RFCs, and that's exactly what he's doing.)  In the
meantime, I guess I'll *have* to do the dance.

It's a little less firm than the date for the DLUR MIB, but I'll
guess that we'll be ready to post draft-ietf-snanau-hprmib-02.txt
as an Internet-Draft by the end of next week.

Thanks again to Randy for finding the time to review our MIBs
in the midst of his SNMPv3 work.

Bob
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SNA NAU Services MIB (snanau) Charter

Chair(s)

     Robert Moore <remoore@ralvm6.vnet.ibm.com>

Routing Area Director(s):

     Joel Halpern <jhalpern@newbridge.com>

Mailing List Information

     General Discussion:snanaumib@external.cisco.com
     To Subscribe: snanaumib-request@cisco.com
     Archive: ftp://ftp.cisco.com/snanaumib/mail-archive

Description of Working Group

The SNA NAU MIB Working Group is chartered to define a set of managed
objects for SNA Network Accessible Units.  These objects will provide the
ability to monitor and control those devices, providing fault,
configuration, and performance management, and will be consistent with
the SNMP framework and existing SNMP standards.

The working group has completed MIBs for base SNA NAU functions, for LU
Type 6.2 or APPC (Advanced Program-to-Program Communication), and for
APPN (Advanced Peer-to-Peer Networking).  MIBs for Dependent LU Requester
(DLUR) and for HPR (High Performance Routing) are nearing completion.
The working group is currently working on a MIB for APPN Extended Border
Node (EBN).

The working group will make sure that its work is aligned with the SNA
DLC MIB Working Group, due to the close relationship between the devices
being worked on by the two groups.

Goals and Milestones

Done
     Begin discussion of proprietary MIBs and develop a single proposal.
Done
     Post an Internet-Draft of the SNA NAU Services MIB.
Done
     Submit the SNA NAU Services MIB to the IESG for consideration as a Proposed
Standard.
Done
     Post proprietary MIB modules.
Done
     Develop and post a single proposal for structure of the MIB module.
Done
     Meet at IETF to review proposed structure/walk through.
Done
     Post Internet-Draft of the APPC MIB.
Done
     Post second Internet-Draft of APPC MIB.
Done
     Meet at IETF to review MIB (if necessary).
Done
     Achieve consensus on the final Internet-Draft.
Done
     Post Internet-Draft of the APPN MIB.
Done
     Submit APPC MIB to the IESG for consideration as a Proposed Standard.
Done
     Post second Internet-Draft of APPN MIB.
Done
     Post third Internet-Draft of APPN MIB.
Done
     Post Internet-Draft of DLUR MIB.
Done
     Post Internet-Draft of HPR MIB.
Done
     Submit APPN MIB to the IESG for consideration as a Proposed Standard.
Done
     Post second Internet-Draft of DLUR MIB.
Done
     Post second Internet-Draft of HPR MIB.
Jul 97
     Submit DLUR MIB to the IESG for consideration as a Proposed Standard.
Jul 97
     Submit HPR MIB to the IESG for consideration as a Proposed Standard.
Aug 97
     Post Internet-Draft of EBN MIB
Oct 97
     Post second Internet-Draft of EBN MIB
Dec 97
     Submit EBN MIB to the IESG for consideration as a Proposed Standard.
Dec 97
     Submit APPC MIB to the IESG for consideration as a Draft Standard.
Dec 97
     Submit APPN MIB to the IESG for consideration as a Draft Standard.

Current Internet-Drafts

     Definitions of Managed Objects for APPN (214585 bytes)
     Definitions of Managed Objects for HPR (63247 bytes)
     Definitions of Managed Objects for DLUR (36797 bytes)

Request for Comments

     Definitions of Managed Objects for SNA NAUs using SMIv2 (RFC 1665) (133381 bytes)
     Definitions of Managed Objects for SNA NAUs using SMIv2 (RFC 1666) (134385 bytes)
     Definitions of Managed Objects for APPC (RFC 2051) (239359 bytes)