[OPSAWG] comments to draft-taylor-opsawg-mibs-to-ieee80231-00

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 15 July 2014 23:39 UTC

X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 15 Jul 2014 19:38:47 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Wed, 16 Jul 2014 01:38:46 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: comments to draft-taylor-opsawg-mibs-to-ieee80231-00
Thread-Index: Ac+ghehnflY99iVhRXegtSZW3I8wug==
Date: Tue, 15 Jul 2014 23:38:46 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C842F1D@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C842F1DAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/opsawg/4IiJJ9ZUeoqYykb_3tzTYnJuWy4
Subject: [OPSAWG] comments to draft-taylor-opsawg-mibs-to-ieee80231-00
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2014 23:39:07 -0000

Here are my comments from a first reading of draft-taylor-opsawg-mibs-to-ieee80231-00.

Thanks to Tom Taylor for taking the burden of editing this document.

The comments are in the order of reading - I apologize if they are not too well structured, writing them during the IEEE 802 Plenary

1. I believe that the scope should be similar to the one of RFC 4663, and this should start from the title. I suggest Transferring MIB Work from IETF Ethernet Interfaces and Hub MIB WG to IEEE 802.3 WG'

2. Capitalize 'Ethernet' at all occurrence

3. s/MIBs/MIB modules/

4. In Section 1:

OLD:

Some years later, another transfer of ownership took

place, this time related to ethernet and directed to IEEE 802.3.

NEW:

Some years later, another transfer of ownership took

place, this time related to Ethernet-related MIB modules developed

in the IETF Ethernet Interfaces and Hub MIB (hubmib) WG which were

transferred to the IEEE 802.3 WG.

5. Section 3.1 - replace text with: 'The content of Section 2.2 of [RFC4663] is accurate also for this document'

6. Section 3.2 - replace text with: 'The IEEE 802.3 WG adopted the approach recommended in [RFC4663], Section 2.3 of developing an IEEE MIB module and defining new compliance clauses under the IEEE OID branch. Information about the IEEE 802.3 Management Registration Arcs can be found at http://www.ieee802.org/3/arcs/index.html'

7. Section 3.3 - I suggest the following content:

The Ethernet Interfaces and Hub MIB WG has completed its documents,

and the WG was closed in September 2007.

The mailing list staid open for a while, and was closed a few years

later.

The appropriate mailing list for IEEE 802.3 MIB modules discussion

is STDS-802-3-MIB@LISTSERV.IEEE.ORG.

To see the general information about 802,1, including how they

work and how to participate, go to http://www.ieee802.org/3/

8. Section 3.1 - replace text with: 'The content of Section 5 of [RFC4663] is accurate also for this document, with the mention that 802.3 should replace 802.1 wherever it occurs in text.'

Regards,

Dan

[OPSAWG] comments to draft-taylor-opsawg-mibs-to-… Romascanu, Dan (Dan)