aa10962;
          25 May 95 22:04 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id
aa10958;
          25 May 95 22:04 EDT
Received: from relay.hp.com by CNRI.Reston.VA.US id aa25301; 25 May
95 22:04 EDT
Received: from hprnd.rose.hp.com by relay.hp.com with ESMTP
     (1.37.109.15/15.5+ECS 3.3) id AA076943869; Thu, 25 May 1995
19:04:29 -0700
Received: from hprnljf.rose.hp.com by hprnd.rose.hp.com with SMTP
     (1.37.109.14/15.5+ECS 3.3) id AA094363859; Thu, 25 May 1995
19:04:19 -0700
Message-Id: <199505260204.AA094363859@hprnd.rose.hp.com>
Received: from localhost by hprnljf.rose.hp.com with SMTP
     (1.38.193.4/16.2) id AA20477; Thu, 25 May 1995 19:08:46 -0700
To: vgmib@hprnd.rose.hp.com
Subject: Getting started
Date: Thu, 25 May 1995 19:08:46 -0700
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John Flick <johnf@hprnljf.rose.hp.com>

Well, now that we are an official working group, I guess its time
to
get to work.

Just a quick reminder that I posted two internet-drafts back in
January
which were meant to serve as initial proposals for this working
group.
They are:

    draft-flick-interfaces-mib-00.txt
    draft-flick-repeater-dev-mib-00.txt

Of course, others still have until the end of the month to present
additional proposals.

I am currently assembling lists of issues/suggestions that I have
already received regarding the drafts listed above, and will post
these issues to this list next week.

In the meantime, two administrative issues to be resolved:

    - We should probably apply to IANA for experimental branches
for
      these MIB modules to be used when we publish our first
      "official" I-Ds (due next month).

    - IANA has currently assigned a single ifType for VG
interfaces.
      Is this sufficient, or should we have different ifTypes for
      ethernet and token ring framing modes?

John