SDLC Objects, Reprise

Bob Stewart <rlstewart@xap.xyplex.com> Fri, 04 March 1994 14:38 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04179; 4 Mar 94 9:38 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04173; 4 Mar 94 9:38 EST
Received: from hubbub.cisco.com by CNRI.Reston.VA.US id aa07144; 4 Mar 94 9:38 EST
Received: from xap.xyplex.com by hubbub.cisco.com with SMTP id AA25549 (8.6.4/IDA-1.5 for <snadlcmib@cisco.com>); Fri, 4 Mar 1994 06:23:40 -0800
Received: by xap.xyplex.com id <AA24393@xap.xyplex.com>; Fri, 4 Mar 94 09:27:55 -0500
Date: Fri, 04 Mar 1994 09:27:55 -0500
Message-Id: <9403041427.AA24393@xap.xyplex.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bob Stewart <rlstewart@xap.xyplex.com>
To: char-mib@pa.dec.com, snadlcmib@cisco.com
Subject: SDLC Objects, Reprise

I love it when something works.

Clearly I was wrong in leaving out the SDLC objects.  They indeed have a
constituancy.  I'll add them.

****** Consensus Check  ******

Are there strong objections to adding the SDLC objects as an SDLC compliance
group? 

	Bob