Re: [Hubmib] [MIB-DOCTORS] Questions on IEEE published mib modules vs IETF

Michael MacFaden <mrm@macfaden.com> Wed, 17 August 2011 17:15 UTC

Return-Path: <macfaden@gmail.com>
X-Original-To: hubmib@ietfa.amsl.com
Delivered-To: hubmib@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E847A21F8BCB; Wed, 17 Aug 2011 10:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wp1ekCAXvWR4; Wed, 17 Aug 2011 10:15:21 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8B99221F8BC4; Wed, 17 Aug 2011 10:15:15 -0700 (PDT)
Received: by wwf5 with SMTP id 5so823453wwf.13 for <multiple recipients>; Wed, 17 Aug 2011 10:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1DG5POvxlB7CVAOKDB6Jmj8nbRBYW/claZu19agalIo=; b=ZVoCz/89nWE6wpzfFruN2onHd8N7OP6/AA4B/melMaTKhBVBNC7cuHz/U5vpXDJfjS AlUH26EqG5bR+mE9diHowoS+hvrTUYMQE++ik/OcfzwjISk+X2nWU0TmKOl8el1Gmrzy ickLZq6sNrS8zKujccrGNwSnR8ZlxqmKMKv5Q=
MIME-Version: 1.0
Received: by 10.216.172.69 with SMTP id s47mr4219170wel.95.1313601365038; Wed, 17 Aug 2011 10:16:05 -0700 (PDT)
Sender: macfaden@gmail.com
Received: by 10.216.169.82 with HTTP; Wed, 17 Aug 2011 10:16:04 -0700 (PDT)
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040385FCAA@307622ANEX5.global.avaya.com>
References: <CAD3a8TkBxG+ZgzL1DnMo2ziaSChLKWNNmGT=1hhK7AMVUzaUPg@mail.gmail.com> <EDC652A26FB23C4EB6384A4584434A040385FCAA@307622ANEX5.global.avaya.com>
Date: Wed, 17 Aug 2011 10:16:04 -0700
X-Google-Sender-Auth: eYQ_9Cyb3jWnMnXIhfHY1AFfD3M
Message-ID: <CAD3a8T=HEcLKf6HNmY2WxADVypQFfeQc9+mGt2fJHtYFQ5WhwQ@mail.gmail.com>
From: Michael MacFaden <mrm@macfaden.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Thu, 18 Aug 2011 10:49:52 -0700
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, hubmib@ietf.org
Subject: Re: [Hubmib] [MIB-DOCTORS] Questions on IEEE published mib modules vs IETF
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hubmib>, <mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hubmib>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 17:15:22 -0000

On Wed, Aug 17, 2011 at 8:36 AM, Romascanu, Dan (Dan)
<dromasca@avaya.com> wrote:
> There is no equivalent of the IETF maturity levels in the IEEE. There is
> just one level of standards, and there is a re-affirmation process that
> needs to happen every five years, unless the standard was updated
> sooner.

Ok, that's good to know. Unfortunately there is no README.txt file at this URL
  http://www.ieee802.org/1/files/public/MIBs
to describe when files are posted here at what part of the standards
process this is/such as being up for reaffirmation. Am
going to the pdf's just to make sure.

> The MIB modules defined in RFC 3635 and RFC 4836 (and a few more) are in
> the scope of IEEE 802.3.1 which was approved as an IEEE standard a few
> months ago. We entertained a discussion at and around the Quebec meeting
> and decided to mark the RFCs as obsolete by the IEEE standards and point
> to these, but not transit them to Historic (not yet in any case). Bert
> will write when he gets some time a short Informational RFC to document
> this transition.

Makes sense to me, have already started using IEEE8021-BRIDGE-MIB,
IEEE8021-Q-BRIDGE, and others in products so would
prefer new to use correct IEEE versions when they become available.

Thanks again,
Mike MacFaden