bridge mib (source routing)

Fred Baker <fred@cisco.com> Mon, 03 April 1995 21:30 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01587; 3 Apr 95 17:30 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id ac01575; 3 Apr 95 17:30 EDT
Received: from inet-gw-2.pa.dec.com by CNRI.Reston.VA.US id aa13439; 3 Apr 95 15:49 EDT
Received: from nsl.pa.dec.com by inet-gw-2.pa.dec.com (5.65/24Feb95) id AA14679; Mon, 3 Apr 95 12:36:34 -0700
Received: by nsl.pa.dec.com; id AA04576; Mon, 3 Apr 95 12:27:42 -0700
Received: by nsl.pa.dec.com; id AA04572; Mon, 3 Apr 95 12:27:41 -0700
Received: by pobox1.pa.dec.com; id AA04233; Mon, 3 Apr 95 12:27:39 -0700
Received: from stilton.cisco.com by inet-gw-1.pa.dec.com (5.65/24Feb95) id AA23617; Mon, 3 Apr 95 12:23:24 -0700
Received: from [171.69.126.172] (sl-chattel-02.cisco.com [171.69.126.172]) by stilton.cisco.com (8.6.8+c/8.6.5) with SMTP id MAA18523; Mon, 3 Apr 1995 12:20:45 -0700
X-Sender: fred@stilton.cisco.com
Message-Id: <v02110100aba5c89d0701@[171.69.126.145]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 3 Apr 1995 12:20:48 -0700
To: bridge-mib@pa.dec.com
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Fred Baker <fred@cisco.com>
Subject: bridge mib (source routing)
Cc: dck2-iesg@mail.bellcore.com

We are ready, timewise, to advance the Source Routing MIB from Proposed to
Draft Standard. Do we need any changes? What implementations exist?

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
computers run on smoke, it if leaks out they won't run