From hubmib-bounces@ietf.org Tue May 01 04:56:12 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hio9Z-0000pC-H7; Tue, 01 May 2007 04:56:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hio9Y-0000j3-EE
	for hubmib@ietf.org; Tue, 01 May 2007 04:56:08 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hio9W-0003Pz-Uc
	for hubmib@ietf.org; Tue, 01 May 2007 04:56:08 -0400
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l418u6tP003120
	for <hubmib@ietf.org>; Tue, 1 May 2007 03:56:06 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 May 2007 03:56:06 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.26]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 May 2007 10:56:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: FW: [Hubmib] RFC 4836 on Definitions of Managed Objects for IEEE
	802.3Medium Attachment Units (MAUs)
Date: Tue, 1 May 2007 10:56:04 +0200
Message-ID: <D4D321F6118846429CD792F0B5AF471F2EAD6E@DEEXC1U02.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Hubmib] RFC 4836 on Definitions of Managed Objects for IEEE
	802.3Medium Attachment Units (MAUs)
Thread-Index: AceJMIRSZgLA/h9DSkCfVtJFkZFFbgCnO2EQ
From: "Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com>
To: "Hub Mib" <hubmib@ietf.org>
X-OriginalArrivalTime: 01 May 2007 08:56:04.0474 (UTC)
	FILETIME=[8CC73DA0:01C78BCE]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Congrats and many thanks (specifically to the editor and reviewers).=20

Bert Wijnen
Chair of the IETF HUBMIB WG=20
-----Original Message-----
From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]=20
Sent: Saturday, April 28, 2007 2:59 AM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: hubmib@ietf.org; rfc-editor@rfc-editor.org
Subject: [Hubmib] RFC 4836 on Definitions of Managed Objects for IEEE
802.3Medium Attachment Units (MAUs)


A new Request for Comments is now available in online RFC libraries.

       =20
        RFC 4836

        Title:      Definitions of Managed Objects for=20
                    IEEE 802.3 Medium Attachment Units (MAUs)=20
        Author:     E. Beili
        Status:     Standards Track
        Date:       April 2007
        Mailbox:    edward.beili@actelis.com
        Pages:      67
        Characters: 151012
        Obsoletes:  RFC3636
        See-Also:  =20

        I-D Tag:    draft-ietf-hubmib-rfc3636bis-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4836.txt

This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community.  In particular, it defines objects for managing IEEE 802.3
Medium Attachment Units (MAUs).  This document obsoletes RFC 3636.
It amends that specification by moving MAU type OBJECT-IDENTITY
definitions and relevant textual conventions into a separate Internet
Assigned Number Authority (IANA) maintained MIB module.  In addition,
management information is added to enable support for Ethernet in the
First Mile (EFM) and 10GBASE-CX4 MAUs.  [STANDARDS TRACK]

This document is a product of the Ethernet Interfaces and Hub MIB
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol.  Distribution of this memo is
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be added to or
deleted from the RFC-DIST distribution list should be sent to
RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an
EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body=20

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Tue May 01 10:04:53 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HisyL-0002vm-5U; Tue, 01 May 2007 10:04:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HisyJ-0002vh-RO
	for hubmib@ietf.org; Tue, 01 May 2007 10:04:51 -0400
Received: from il-mail.actelis.net ([62.90.13.193])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HisyJ-0001aS-Ch
	for hubmib@ietf.org; Tue, 01 May 2007 10:04:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] RFC 4836 on Definitions of Managed Objects for
	IEEE802.3Medium Attachment Units (MAUs)
Date: Tue, 1 May 2007 17:04:59 +0300
Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3EF95A29@il-mail.actelis.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Hubmib] RFC 4836 on Definitions of Managed Objects for
	IEEE802.3Medium Attachment Units (MAUs)
Thread-Index: AceJMIRSZgLA/h9DSkCfVtJFkZFFbgCnO2EQAAqoIUA=
From: "Edward Beili" <EdwardB@actelis.com>
To: "Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: "C. M. Heard" <heard@pobox.com>, dromasca@avaya.com,
	Hub Mib <hubmib@ietf.org>, John Flick <john.flick@hp.com>
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Thank you Bert. I would also like to express my gratitude to Mike Heard, =
John Flick and Dan Romascanu for their help.

Regards,
-E.

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@alcatel-lucent.com]=20
> Sent: Tuesday, May 01, 2007 11:56
> To: Hub Mib
> Subject: FW: [Hubmib] RFC 4836 on Definitions of Managed=20
> Objects for IEEE802.3Medium Attachment Units (MAUs)
>=20
> Congrats and many thanks (specifically to the editor and reviewers).=20
>=20
> Bert Wijnen
> Chair of the IETF HUBMIB WG
> -----Original Message-----
> From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> Sent: Saturday, April 28, 2007 2:59 AM
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: hubmib@ietf.org; rfc-editor@rfc-editor.org
> Subject: [Hubmib] RFC 4836 on Definitions of Managed Objects=20
> for IEEE 802.3Medium Attachment Units (MAUs)
>=20
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>        =20
>         RFC 4836
>=20
>         Title:      Definitions of Managed Objects for=20
>                     IEEE 802.3 Medium Attachment Units (MAUs)=20
>         Author:     E. Beili
>         Status:     Standards Track
>         Date:       April 2007
>         Mailbox:    edward.beili@actelis.com
>         Pages:      67
>         Characters: 151012
>         Obsoletes:  RFC3636
>         See-Also:  =20
>=20
>         I-D Tag:    draft-ietf-hubmib-rfc3636bis-05.txt
>=20
>         URL:        http://www.rfc-editor.org/rfc/rfc4836.txt
>=20
> This document defines a portion of the Management Information Base
> (MIB) for use with network management protocols in the=20
> Internet community.  In particular, it defines objects for=20
> managing IEEE 802.3 Medium Attachment Units (MAUs).  This=20
> document obsoletes RFC 3636.
> It amends that specification by moving MAU type=20
> OBJECT-IDENTITY definitions and relevant textual conventions=20
> into a separate Internet Assigned Number Authority (IANA)=20
> maintained MIB module.  In addition, management information=20
> is added to enable support for Ethernet in the First Mile=20
> (EFM) and 10GBASE-CX4 MAUs.  [STANDARDS TRACK]
>=20
> This document is a product of the Ethernet Interfaces and Hub=20
> MIB Working Group of the IETF.
>=20
> This is now a Proposed Standard Protocol.
>=20
> STANDARDS TRACK: This document specifies an Internet=20
> standards track protocol for the Internet community,and=20
> requests discussion and suggestions for improvements.Please=20
> refer to the current edition of the Internet Official=20
> Protocol Standards (STD 1) for the standardization state and=20
> status of this protocol.  Distribution of this memo is unlimited.
>=20
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution=20
> list should be sent to IETF-REQUEST@IETF.ORG.  Requests to be=20
> added to or deleted from the RFC-DIST distribution list=20
> should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>=20
> Details on obtaining RFCs via FTP or EMAIL may be obtained by=20
> sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the=20
> message body=20
>=20
> help: ways_to_get_rfcs. For example:
>=20
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
>=20
>         help: ways_to_get_rfcs
>=20
> Requests for special distribution should be addressed to=20
> either the author of the RFC in question, or to=20
> RFC-Manager@RFC-EDITOR.ORG.  Unless specifically noted=20
> otherwise on the RFC itself, all RFCs are for unlimited distribution.
>=20
> Submissions for Requests for Comments should be sent to=20
> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223,=20
> Instructions to RFC Authors, for further information.
>=20
>=20
> The RFC Editor Team
> USC/Information Sciences Institute
>=20
> ...
>=20
>=20
>=20
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Tue May 01 10:11:21 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hit4b-0002Dl-RB; Tue, 01 May 2007 10:11:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hit4b-0002CT-5u
	for hubmib@ietf.org; Tue, 01 May 2007 10:11:21 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hit4Z-0002Nl-S5
	for hubmib@ietf.org; Tue, 01 May 2007 10:11:21 -0400
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l41EB3Hv005546;
	Tue, 1 May 2007 09:11:11 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 May 2007 09:11:05 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.26]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 May 2007 16:11:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] RFC 4836 on Definitions of Managed Objects for
	IEEE802.3Medium Attachment Units (MAUs)
Date: Tue, 1 May 2007 16:09:51 +0200
Message-ID: <D4D321F6118846429CD792F0B5AF471F2EAD76@DEEXC1U02.de.lucent.com>
In-Reply-To: <9C1CAB2B65E62D49A10E49DFCD68EF3EF95A29@il-mail.actelis.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Hubmib] RFC 4836 on Definitions of Managed Objects for
	IEEE802.3Medium Attachment Units (MAUs)
Thread-Index: AceJMIRSZgLA/h9DSkCfVtJFkZFFbgCnO2EQAAqoIUAAAI7KkA==
References: <9C1CAB2B65E62D49A10E49DFCD68EF3EF95A29@il-mail.actelis.net>
From: "Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com>
To: "Edward Beili" <EdwardB@actelis.com>
X-OriginalArrivalTime: 01 May 2007 14:11:03.0115 (UTC)
	FILETIME=[8D3F01B0:01C78BFA]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: "C. M. Heard" <heard@pobox.com>, dromasca@avaya.com,
	Hub Mib <hubmib@ietf.org>, John Flick <john.flick@hp.com>
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

> From: Edward Beili [mailto:EdwardB@actelis.com]  wrote:
> Sent: Tuesday, May 01, 2007 4:05 PM
> To: Wijnen, Bert (Bert)
> Cc: C. M. Heard; dromasca@avaya.com; John Flick; Hub Mib
> Subject: RE: [Hubmib] RFC 4836 on Definitions of Managed=20
> Objects for IEEE802.3Medium Attachment Units (MAUs)
>=20
> Thank you Bert. I would also like to express my gratitude to=20
> Mike Heard, John Flick and Dan Romascanu for their help.
>=20

Exactly. And good to mention their names as well!

Good work,
Bert
> Regards,
> -E.

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From ttgn@ramdis.co.uk Tue May 01 10:36:08 2007
Return-path: <ttgn@ramdis.co.uk>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HitSZ-0001Wq-U6
	for hubmib-archive@lists.ietf.org; Tue, 01 May 2007 10:36:08 -0400
Received: from gtnet.tgnet.cz ([82.100.0.70])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HitSZ-0007q4-2K
	for hubmib-archive@lists.ietf.org; Tue, 01 May 2007 10:36:07 -0400
Received: from [151.142.97.193] (helo=zspyp)
	by gtnet.tgnet.cz with smtp (Exim 4.62 (FreeBSD))
	id 1ItUK-0006Qp-JB; Tue, 1 May 2007 16:37:56 +0200
Message-ID: <001401c78bfe$2c01ad90$c1618e97@zspyp>
From: "Vinson" <ttgn@ramdis.co.uk>
To: <hubmib-archive@lists.ietf.org>
Subject: At the time of this writing, version 5.
Date: Tue, 1 May 2007 16:36:57 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1250";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Antivirus: avast! (VPS 000737-2, 30.04.2007), Outbound message
X-Antivirus-Status: Clean
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

CDPN Really Warming Up!

China Datacom Corp.
Sym: CDPN
Close: $0.0675 UP 4%

Investors are taking notice of CDPN, with hot news, volume rising, and
price on a steady climb. This is is on the hot list. Get on CDPN first
thing Tuesday!

I click the Suggest button to have Java Studio Creator fill in the
driver class name and the URL template.
Figure 2: Java Studio Creator 2 IDE and NetBeans 4. And because Sun
opens Solaris source code via the OpenSolaris Project, everyone can
benefit from the work and insight of creative, committed Solaris
developers.
Ajax-Enabled JavaServer Faces Components Create web applications with
Ajax-enabled JavaServer Faces components.
If you don't find components or widgets that provide the Ajax
functionality you need, you must do a lot more JavaScript coding
yourself. With its simplified installation experience coupled with
additional support for common laptops and desktops, developers can more
easily create and deploy applications for Solaris 10.
You can build your applications visually, with minimal code creation,
using its drag-and-drop components (EJBs and web services, too),
automatic page navigation, and other convenient features. However, since
Java Studio Creator was developed over a forked NetBeans source base, a 
disparity has always existed between the two IDEs.
These applications are representative of a new generation of highly
responsive, highly interactive web applications, referred to as Web 2.
For example, enterprise application developers need to add logic in
server-side components to handle Ajax-related requests directed to the
server. Also a Filter that allows you to add headers to Servlet output
(caching application). Check back next week as SDNtv offers a look
Solaris Express, Developer Edition with Don Kretsch.
Download the latest build here, or register for the free NetBeans Day.
NetBeans is the free, open source Integrated Development Environment
(IDE). 0 and get the nice features of the NetBeans 5. Migrate your Sun
Java Studio Creator 2 applications to NetBeans Visual Web Pack.
Also a Filter that allows you to add headers to Servlet output (caching
application). At the other end of the spectrum, you take advantage of
techniques that allow you to build Ajax into a web page with little or
no JavaScript coding. Component developers find the technology
particularly powerful because it contains a set of application
programming interfaces (APIs) for representing UI components and for
managing their state.
A new dialog box then opens that lets me add a new data source, as shown
in Figure 1. com: mysql-connector-java-5.
For article, tutorials, forums, tech tips, and other developer
resources, please see the official page on the Sun Developer Network.
However, since Java Studio Creator was developed over a forked NetBeans
source base, a  disparity has always existed between the two IDEs.
0 Expo Toyko and the just-announced Web 2.
These components run on a server and are rendered to the page.
0 as soon as it was released. For example, a user can continue to move
the mouse over a Google map and see a smooth, uninterrupted change in
the display because extended parts of the map have been loaded
asynchronously. Right now, we're not sure if we are going to work on a
Java Studio Creator 3 IDE.
1 IDE   In addition to a different look, the Java Studio Creator IDE
introduced some important  functionality that was missing in the
NetBeans 3.




From hubmib-bounces@ietf.org Tue May 01 13:16:31 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hivxn-0002p2-Sk; Tue, 01 May 2007 13:16:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hivxn-0002mG-9a
	for hubmib@ietf.org; Tue, 01 May 2007 13:16:31 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hivxl-0007W6-Tm
	for hubmib@ietf.org; Tue, 01 May 2007 13:16:31 -0400
Received: from 51.105.64.135.in-addr.arpa (HELO IS0004AVEXU1.global.avaya.com)
	([135.64.105.51])
	by nj300815-nj-outbound.avaya.com with ESMTP; 01 May 2007 13:16:29 -0400
X-IronPort-AV: i="4.14,475,1170651600"; d="scan'208"; a="10306724:sNHT8009532"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] RFC 4836 on Definitions of Managed Objects for
	IEEE802.3Medium Attachment Units (MAUs)
Date: Tue, 1 May 2007 20:16:25 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0CC0556D@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Hubmib] RFC 4836 on Definitions of Managed Objects for
	IEEE802.3Medium Attachment Units (MAUs)
Thread-Index: AceJMIRSZgLA/h9DSkCfVtJFkZFFbgCnO2EQAAqoIUAABwqHUA==
References: <9C1CAB2B65E62D49A10E49DFCD68EF3EF95A29@il-mail.actelis.net>
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Edward Beili" <EdwardB@actelis.com>,
	"Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: "C. M. Heard" <heard@pobox.com>, Hub Mib <hubmib@ietf.org>,
	John Flick <john.flick@hp.com>, STDS-802-3@listserv.ieee.org
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Congratulations to the whole Working Group and to everybody involved
(including the IEEE 802.3 colleagues).=20

Dan


=20
=20

> -----Original Message-----
> From: Edward Beili [mailto:EdwardB@actelis.com]=20
> Sent: Tuesday, May 01, 2007 5:05 PM
> To: Wijnen, Bert (Bert)
> Cc: C. M. Heard; Romascanu, Dan (Dan); John Flick; Hub Mib
> Subject: RE: [Hubmib] RFC 4836 on Definitions of Managed=20
> Objects for IEEE802.3Medium Attachment Units (MAUs)
>=20
> Thank you Bert. I would also like to express my gratitude to=20
> Mike Heard, John Flick and Dan Romascanu for their help.
>=20
> Regards,
> -E.
>=20
> > -----Original Message-----
> > From: Wijnen, Bert (Bert) [mailto:bwijnen@alcatel-lucent.com]
> > Sent: Tuesday, May 01, 2007 11:56
> > To: Hub Mib
> > Subject: FW: [Hubmib] RFC 4836 on Definitions of Managed=20
> Objects for=20
> > IEEE802.3Medium Attachment Units (MAUs)
> >=20
> > Congrats and many thanks (specifically to the editor and=20
> reviewers).=20
> >=20
> > Bert Wijnen
> > Chair of the IETF HUBMIB WG
> > -----Original Message-----
> > From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> > Sent: Saturday, April 28, 2007 2:59 AM
> > To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> > Cc: hubmib@ietf.org; rfc-editor@rfc-editor.org
> > Subject: [Hubmib] RFC 4836 on Definitions of Managed=20
> Objects for IEEE=20
> > 802.3Medium Attachment Units (MAUs)
> >=20
> >=20
> > A new Request for Comments is now available in online RFC libraries.
> >=20
> >        =20
> >         RFC 4836
> >=20
> >         Title:      Definitions of Managed Objects for=20
> >                     IEEE 802.3 Medium Attachment Units (MAUs)=20
> >         Author:     E. Beili
> >         Status:     Standards Track
> >         Date:       April 2007
> >         Mailbox:    edward.beili@actelis.com
> >         Pages:      67
> >         Characters: 151012
> >         Obsoletes:  RFC3636
> >         See-Also:  =20
> >=20
> >         I-D Tag:    draft-ietf-hubmib-rfc3636bis-05.txt
> >=20
> >         URL:        http://www.rfc-editor.org/rfc/rfc4836.txt
> >=20
> > This document defines a portion of the Management Information Base
> > (MIB) for use with network management protocols in the Internet=20
> > community.  In particular, it defines objects for managing=20
> IEEE 802.3=20
> > Medium Attachment Units (MAUs).  This document obsoletes RFC 3636.
> > It amends that specification by moving MAU type OBJECT-IDENTITY=20
> > definitions and relevant textual conventions into a=20
> separate Internet=20
> > Assigned Number Authority (IANA) maintained MIB module.  In=20
> addition,=20
> > management information is added to enable support for=20
> Ethernet in the=20
> > First Mile
> > (EFM) and 10GBASE-CX4 MAUs.  [STANDARDS TRACK]
> >=20
> > This document is a product of the Ethernet Interfaces and Hub MIB=20
> > Working Group of the IETF.
> >=20
> > This is now a Proposed Standard Protocol.
> >=20
> > STANDARDS TRACK: This document specifies an Internet=20
> standards track=20
> > protocol for the Internet community,and requests discussion and=20
> > suggestions for improvements.Please refer to the current edition of=20
> > the Internet Official Protocol Standards (STD 1) for the=20
> > standardization state and status of this protocol.  Distribution of=20
> > this memo is unlimited.
> >=20
> > This announcement is sent to the IETF list and the RFC-DIST list.
> > Requests to be added to or deleted from the IETF distribution list=20
> > should be sent to IETF-REQUEST@IETF.ORG.  Requests to be=20
> added to or=20
> > deleted from the RFC-DIST distribution list should be sent to=20
> > RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> >=20
> > Details on obtaining RFCs via FTP or EMAIL may be obtained=20
> by sending=20
> > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> >=20
> > help: ways_to_get_rfcs. For example:
> >=20
> >         To: rfc-info@RFC-EDITOR.ORG
> >         Subject: getting rfcs
> >=20
> >         help: ways_to_get_rfcs
> >=20
> > Requests for special distribution should be addressed to either the=20
> > author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. =20
> > Unless specifically noted otherwise on the RFC itself, all RFCs are=20
> > for unlimited distribution.
> >=20
> > Submissions for Requests for Comments should be sent to=20
> > RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223,=20
> Instructions to=20
> > RFC Authors, for further information.
> >=20
> >=20
> > The RFC Editor Team
> > USC/Information Sciences Institute
> >=20
> > ...
> >=20
> >=20
> >=20
> > _______________________________________________
> > Hubmib mailing list
> > Hubmib@ietf.org
> > https://www1.ietf.org/mailman/listinfo/hubmib
> >=20
> > _______________________________________________
> > Hubmib mailing list
> > Hubmib@ietf.org
> > https://www1.ietf.org/mailman/listinfo/hubmib
> >=20
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Thu May 03 11:41:14 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HjdQg-0007CK-RJ; Thu, 03 May 2007 11:41:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HjdQf-0007CC-Q7
	for hubmib@ietf.org; Thu, 03 May 2007 11:41:13 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjdQe-0001Dh-JY
	for hubmib@ietf.org; Thu, 03 May 2007 11:41:13 -0400
Received: from 51.105.64.135.in-addr.arpa (HELO IS0004AVEXU1.global.avaya.com)
	([135.64.105.51])
	by nj300815-nj-outbound.avaya.com with ESMTP; 03 May 2007 11:41:11 -0400
X-IronPort-AV: i="4.14,486,1170651600"; 
	d="scan'208,217"; a="11227787:sNHT15111096"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 3 May 2007 18:40:35 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B886C3D@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [WARNING: VIRUS REMOVED] Fw: Funny :)
Thread-Index: AceNmWRwYA4us9XKR4yFVeziT9STUQAAAACH
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "hubmib" <hubmib@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Hubmib] Out of Office AutoReply: [WARNING: VIRUS REMOVED] Fw:
	Funny :)
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0714025428=="
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0714025428==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78D99.6472DC1F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78D99.6472DC1F
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I am travelling for business purposes until May 4th. Although I expect =
to check email daily there may be delays in answering your mail. For =
urgent matters please leave a message at my office number voice mail.

Regards,

Dan


------_=_NextPart_001_01C78D99.6472DC1F
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6619.9">
<TITLE>Out of Office AutoReply: [WARNING: VIRUS REMOVED] Fw: Funny =
:)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I am travelling for business purposes until May 4th. =
Although I expect to check email daily there may be delays in answering =
your mail. For urgent matters please leave a message at my office number =
voice mail.<BR>
<BR>
Regards,<BR>
<BR>
Dan<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C78D99.6472DC1F--


--===============0714025428==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

--===============0714025428==--




From zpe@theriver.com Sun May 06 05:11:03 2007
Return-path: <zpe@theriver.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hkclj-0003hP-5M
	for hubmib-archive@lists.ietf.org; Sun, 06 May 2007 05:11:03 -0400
Received: from [88.226.98.110] (helo=dsl88-226-25198.ttnet.net.tr)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1Hkclg-0003mw-D5
	for hubmib-archive@lists.ietf.org; Sun, 06 May 2007 05:11:03 -0400
Received: from crx ([131.87.88.126])
	by dsl88-226-25198.ttnet.net.tr (8.13.2/8.13.2) with SMTP id l469CReC076394;
	Sun, 6 May 2007 12:12:27 +0300
Message-ID: <001d01c78fbe$7801a380$7e585783@crx>
From: "harm" <zpe@theriver.com>
To: <hubmib-archive@lists.ietf.org>
Subject: Forest fires have made it one of the world's worst polluters.
Date: Sun, 6 May 2007 12:11:02 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 3.6 (+++)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

The cream of the crop for 2007 - GET IN EARLY! DSDI IS SET TO ROCK YOUR
PORTFOLIO!

DSI Direct Sales, Inc.
Symbol: DSDI
Price: $0.04

There is a MASSIVE PROMOTION underway this weekend! This is hot, read
the news and get on DSDI first thing Monday!

There are far too many variables to make a meaningful call on regime
survival.
Donovan said, September 13, 2005 at 6:13 pm  Cool. Supporters of the
compulsory licences, like Paul Cawthorne from Medicins Sans Frontiers,
believe Thailand's bold step is the right one. Next you will learn the
differences between a nice guy and a cool guy. You will learn how to
talk to girls at a party and if it matters what you say. The by-election
became as much about the possible return to prominence of Mr Anwar -
seen as the opposition's "leader in waiting" - as it had to do with the
people of Ijok. Who was standing next to him at that reception at the
Chinese embassy?
WANG HONGYANG, 14, BEIJING I've been learning about Japanese history for
three years.
They think we're just nagging them about the history.
Few were under any illusions that V1 Immunitor would help them, but then
what did they have to lose? Carrying a can of pesticide, he swings the
spray backwards and forwards over the crop.
If they do not like what they recorded, they can re-record. Indonesia
straddles both ends of the global warming debate.
Permalink Comments are closed. 05  Advice from Meghan.




From xwfd@yellowhatmarketing.com Sun May 06 08:57:00 2007
Return-path: <xwfd@yellowhatmarketing.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HkgIO-0002NW-Jv
	for hubmib-archive@lists.ietf.org; Sun, 06 May 2007 08:57:00 -0400
Received: from dsl-240-26-47.telkomadsl.co.za ([41.240.26.47])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HkgIB-0000uf-TO
	for hubmib-archive@lists.ietf.org; Sun, 06 May 2007 08:57:00 -0400
Received: from [57.208.117.44] (helo=qvcp)
	by dsl-240-26-47.telkomadsl.co.za with smtp (Exim 4.66 (FreeBSD))
	id 1INpAn-0007dw-9S; Sun, 6 May 2007 14:59:55 -0700
Message-ID: <001001c79029$6c658580$2c75d039@qvcp>
From: "Oliver Y. Witt" <xwfd@yellowhatmarketing.com>
To: <hubmib-archive@lists.ietf.org>
Subject: fairy defiance
Date: Sun, 6 May 2007 14:56:38 -0700
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_000C_01C78FEE.BFF94000"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: c2e58d9873012c90703822e287241385

------=_NextPart_000_000C_01C78FEE.BFF94000
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_000D_01C78FEE.BFFC9B60"

------=_NextPart_001_000D_01C78FEE.BFFC9B60
Content-Type: text/plain;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable


The only warm-weather dress that will take you to these events and many =
more is the sundress.
And companies certainly want to keep all those communications.
Especially if you're a consultant on the lookout for customers or on the =
lookout for a new job, for instance.
And companies certainly want to keep all those communications. AACS =
isn't claiming that the code is copyrightable, only that it's a =
component of a DRM scheme. How to parse this story? Network Operating =
Platform handles ZigBee applications. At this time, more than two-thirds =
of all archiving solutions are sold as on-premises products, Radicati =
told eWEEK.
"Malware continues to be released through IM networks, and is on the =
rise again for the first time since January," said Don Montgomery, vice =
president of marketing at Akonix. It reads the RSS xml file directly and =
lets you edit it.
So it makes sort of the comparison set a little bit difficult. in order =
to prevent possible misuse of MMS, immoral actions and social problems, =
the Telecommunications Ministry will filter immoral MMS," the television =
said.
------=_NextPart_001_000D_01C78FEE.BFFC9B60
Content-Type: text/html;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1250">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><IMG alt=3D"reptile" hspace=3D0=20
src=3D"cid:000b01c79029$6c54bca0$2c75d039@qvcp" align=3Dbaseline=20
border=3D0></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The only warm-weather dress that will =
take you to=20
these events and many more is the sundress.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>And companies certainly want to keep =
all those=20
communications.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Especially if you're a consultant on =
the lookout=20
for customers or on the lookout for a new job, for =
instance.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>And companies certainly want to keep =
all those=20
communications. AACS isn't claiming that the code is copyrightable, only =
that it's a=20
component of a DRM scheme. How to parse this story? Network Operating =
Platform=20
handles ZigBee applications. At this time, more than two-thirds of all =
archiving=20
solutions are sold as on-premises products, Radicati told =
eWEEK.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>"Malware continues to be released =
through IM=20
networks, and is on the rise again for the first time since January," =
said Don=20
Montgomery, vice president of marketing at Akonix. It reads the RSS xml =
file=20
directly and lets you edit it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>So it makes sort of the comparison set =
a little bit=20
difficult. in order to prevent possible misuse of MMS, immoral actions =
and social=20
problems, the Telecommunications Ministry will filter immoral MMS," the =
television=20
said.</FONT></DIV></BODY></HTML>

------=_NextPart_001_000D_01C78FEE.BFFC9B60--

------=_NextPart_000_000C_01C78FEE.BFF94000
Content-Type: image/gif;
	name="suspiciously.gif"
Content-Transfer-Encoding: base64
Content-ID: <000b01c79029$6c54bca0$2c75d039@qvcp>

R0lGODdhFwLuAPUZAPPZ53WV5XU9QWNsh1uYQ2jBeTBzsl2EzVmAGkyxoHouLIiQq0a2VDnKRIST
Gamsf1BLmRwfZGp4Yz9aPmlhaEAbN4uRtsicBhGTjJxhiUhcNVufr4paFjb4ScmyM5/wH+yCm4mg
RI7sbqKFJ85mCo1aN1TRqYPONYU+2owLDSg0EoICWIcpmOaK4S5S8uLrIzNMaAlEiwDaJmXYDaSY
SEX5EyAlzsV6dMRHYRKRQbdt4OF4P2oIpeGysuXHba8UQCwAAAAAFwLuAAAG/0CAcEgsGo/IpHLJ
bDqf0Kh0Sq1ar9isdsvter/gsHhMLpvP6LR6zW673/C4fE6v2+/4vH7P7/v/gIGCg4SFhoeIiYqL
jI2Oj5CRkpOUlZaXmJmam5ydnp+goaKjpKWmp6ipqqusra6vsLGQAgoVlyAtAVobBAxEFQoKDkQB
BywCZcXHQg0FFgUnGEMIDRoCKSQKS8DCNAC5ugACHARXBrQVtkI0uEXkDQDPJ0QITee1Rbi6B0Lv
BUYCqFmThQrdrVy7ev0KNmyIMmRkHjJzBk2aEIHXsm1j6A2ckHHlrNxLN4RdC3cE4MmjZ88gEX0A
+AHwBxAjwSYcFAigsOAZAP8MAx4xAJqCCgYDgDg4aIeF5zNfAFIoiFAhBQch4AJkYMGsg4kFCSxm
yZrhYgOvYIdQKNGgAS0SS6ZWvQoTwNagRwysbQsRgE4iQwdIjdBvaREWA+qhJUKhSWCpQ5TqC4eY
WocietnCAxMWaWMAbhWQyDnkKVFtSe5aNnEHGwQBIQZYAKCwEIKMQ2TzYkCYCdIiJhJcUWAVAAgh
AVAAMDAgJIDgR4c0qIdtWwTiHLwhR2HgN4ACujon6btBSG8hqLULUQ6gebMArLNkd5gbNIBwyy9+
bKJuHVP2Rxz1GjVDkABBEc4VJYSCmCGVEmZOhEQcekMwlR9tmxFxIBO9XKf/IHbGJQEedL9Rc1t1
QujWIWpIJNede0OIBwdEGz4gxD8T9OcXByPcQAYwPH6jC3veHaEBXzzYIMQIDzzwjHNJJMddkcJF
J50AScZFlQJB3idld8gFkICMR7qVZRKDAYlVAF8yw+aYYiXRpBBQ9nYVfRcipwWLDU6ARF9NMDgT
AD7ep4Q0MACgwRBJbijEbEL0pyMRyhUpRJxKQAqAOlt2ud4QfkLIxJM5+tXpCElkGNYQi8LDwxCo
xiNEqC1+CkCoYsroBo1C2PjdrTpy2eOPwgoJAJFKlImlkgAw6WQBULaIwpREVFmkmcwmIVexXk4L
ppdw/qbsmUikyeWabYL2/+aqS8xJGxF2EiNEkfgNh0R3tBYBKBOCXlVovUYgqiijNjgqa6RDTDpE
pQE7oSmnQMZq661GWIoEqbZs66kRqorVKgCvLvnorEqEwx6u4c6R7aMLMFDqptcpgIB6ScA58Hdl
2WBASB5Y0PIQKVQQ88wgLMAmCi5YzCq8RLzwhNHJuUAEAQTY7BcCBWQQwcpGsBjMEEYXgZcQwqFX
DwDnoVkEzQAOoPQRBHgANhEfErGAEW4robXOcStxHjt3H5s0EvkyESwAMwMQOBJWD5EzET23TKvC
20ldRNlMyE1ypEPjmWeMTw/hNZ9iu001ERrIjITmTtSbN9mYtpE2AC/4Cv9VCVNRtWiyBBQQFl4K
ZHBABDEo6cAFtQfwDwAS4B4BVYhLEM+QSYwdExENOWH9EAbsXvYEtAg/exGFDyG9qDeCOoRMSpy/
tOdvG1E8Eb4KcX7a7nO/hPjFZ3gEixpAwPmoFyAoQMU8QlhU/ozQO8wJoSxpQ94D6lWChBUBYHRy
wgWGsLwi9GdsAOLgE+o3geZNZQkGSJoGnDMA8CFhg0/Q1OcA4EA3LE4IMDxYAiQggAk8bwljG9MQ
BACoBswAeR7wle946MNN2U9PjCNCEaFwNvSFBAMTsIYAbmiEDlJMP0WQGOKGIJZ9HcGLaLMbrJqw
gN9sxmkiFAdLKCXGK/D/0IJCWFwdaQgFGUKEKlU8QgWjRcQbzkAISQQdAtVYhUMCIJHfwdx5zmYB
DAZyCXC80Q576IQKku2LRnCkE/JXx2i1oSzYG4Kv2NcEVhKhcDHIwfGQJ4Ty5JErvaGkiMKCxd0d
AAKxPF4Tdncwu0Tmkw7bwAE2kIDA6U6AQzjBCIT3mhhhoJdKcJIymWmeZw5QmsLT2wJ+GQMcStAC
tmwmC543KQxeQZ0/jJ5sAjAPIpADjS+sHToBwExnUm4IjlpeLzMQuGAKoXb8XKY66SGB7QHAYEkI
5gVyuM2FbiqADS3CL0HShBwWgYvEqOdD4wjKIeSAikQQaT/kgMohZG+V/1BwpfqIIFFa8hNsuASj
DIvgu2tmUQjklKVHk0BMTbX0TjXMVEX9idFoTnOj1sSmnNCp0G5WoKn3AadMiUBQcppTn+lcwDqh
Jy8uwDOXDa2kSmfSu46ClZ/NNM8/hRDQS2WRoEIwKO1stFSuTCOjRYAoEmo6hL5GCqPb2yg5OooE
kDpEpHXdHBFO+oRArvVOb8ii+2IwAbgg8T4uOIAJLKCDJYixipja6gRDO1odQIAwFajHZ5BAAOiA
rRichQsTAImAz3TAAah6zVVqG5afZjMAoQUoOwP52xEUibixK8ILkohc9r2WrACgQA2amywJGI19
E50uEVor2NluobUJQ/9Ab7WrLw5c8oVItBFr6To+WBlAuPWwrQa8GxPODsFpqxWtDGP73vgR4QC5
pR8A5mvV9zpXuE3Q7SPrF58jaLe5v3EvdDXq3yYAcgjbBagZ1+DT9TEHACSY6KOQu4EK03YAbqtm
JEt8nwMwZwQSdpIuWmwBXNqifF+gSn9k0IFyxPgiPY3uFsbxXkCQDhIEgPF9kYG1KpWQEjYeAI4B
cIEP6Nhy/wMAkZ2DX99d0MZOYCcRxgxjSTDndYirGru8dIAEmLIUA6DAiG/C59YVw85cBsAHRFC/
OciAAQZOxJu9gwA5i4VNdb4zKfK85z5bOkp/LscGB11oORw60ZcOtaj/R03qUpv61KhOtapXzepW
u/rVsI61rGdN61rb+tY38cAH5iEACDSZNrd5KATcZwEPsC671QzAAjIggRDoeq1wu02vuVpsrlLg
Nax09q4d0GsETAADCQgOPYgoxQzsNAPXFkC2dY3rdt8kAwHwGfMC+MgSZE+jC6hHr3+zAhzs4AKs
A4Ge7RLvBQxAAgGENr4RwIFpZ7ff/x5CCwROxJYePOEesLcDNDCAsAE13w1XS7+LMHE998XgCH+v
Q93NclHAW94pr/e9D5xvcUCA3/4GeIUG/nKUJ3wJBwC5wykA8RyWvOK5SfkJMu6AjXccP0FneF+I
jgOSU/zkF1d5y7cu/wkCIEAnliKBeFklABwcIBx4IcAHlHCA2XydrrMVu8SHUHVDJZAJ7NPGfYEm
4ePsB4qfWfva6+H3BDCaReYlwknWhx8KEBOMXI88IxYgdEcJ4AckIIGCJu44PTmeCf9YHET7/r7G
MwFz+i7CD+je+Y+ueQb3RmMV3+b3v6ulCDOXvO4N0UHUQCDuRSnUBYvRBBGIoPf6AlqFPgJv4i+h
AMYvwN0u2ZcUpOAGFvIcADpQgxoQoY6L27OgEu9K7+/+/LwXHdwLFPwjQLr4x1e/FJUvBL8LoPlb
5Wn0p5/8BV0/+1AkBNxnfiLDSHJ0BOOnUUVAgOjXgIAgAu8DUTsQFf9H0Hzu1EWoUwRxt3y3ggPw
1gQjUADQl0diMwQ7oHl1d0GpdBnvMwQQaHvWI2EhUlZDwIIOeIN9AH0fAB62V38odgR+xSZMQDMB
MDY3NwTCV3d+54FM8HjfgR8ON4PWZwQpCAAhYAQOUEUjmCIARQTCZxyLBwBMSARrh4NmqAcjQAMP
UIbZVYIgMIE+2AI6wB4HUGmIszGU53iAAgJvqHnGwRQs0FJH0HSXJAJ5SEww5nd+OARz6FdElHgA
QIieYogLoIcpMgB8CId/KIchdIaeqAd30nRAZYQbAgI3QAKJhAv2l39CkIWYdSMH4FAZYIq98gC1
14kLCHtGsIOsBAH/EDA2MjhxpRUTyxBKWYg9vDgA2uGLAzCL9AOAPfiJ0vgGodgQsQhQpXiKqch5
4sCKkchwPHWNRTCLhdIkt6gENaCLRcCLGvKLBaJ4IDCMxjBisBdIDpCMy/iLzqhK0HiA0/iPbNB0
u+Ne82IAD+ABfJKJrrYCANmQaoAAoigEEsYd+OSQFnmRGJmRGrmRHNmRHvmRIBmSIjmSJFmSJnmS
KJmSKrmSLNmSLvmSMBmTMjmTNFmTNnmTOJmTOrmTPNmTPvmTQBmUQjmURFmURnmUSJmUSrmUTNmU
TvmUUBmVUjmVVFmVVnmVWJmVWrmVXNmVXvmVYBmWV9BZGwRH1TVa/1WgZFVgg0yAWz8olixZZal1
YynWK5XkAraEBGx2BDVEfFomg0egZn7SAHvZPgNQDCe2W/X1BWNFEnDpagEhZzRIAGLUaUdAmIhm
PZH5UZAGaELAafixAShwXbaQEp+2BLTifEswmmYgmtelBJT2Lo/ZZ5EpRJ5DmQq2BJiZmB/RaJyZ
aUMAmoU1mmpmmoiGmg7hjQsjWGDgmvGEBLEpabP5CudjZinCJgGQl5/ZBGfji0PAABKgcgAjAR7Q
ZRMEVEMQTwuUBEAxAYdZBOTZZUawU4jTABNgMOCpXhXpMMQgPfaZIgTQAfk5nX2WIVAyAWcnhEMw
VI3VhVODNxXTbP9dVoZbpZxEsAFFiKAxYgASyobItD4L4HUOJwEM0AAEEJ5V4EAGEHQimicmSqB8
5hyeZAT1sp5HwD774j8kWATMdHDlOTKlwYVCMKNN6BA9Sp5FAGYpcgAHUAAlABHMkRLgWQVK2h4y
UUEMiQQF4GIwqgoyWivm00pDVAQ6qjhGcKQ/WkwHMzZEugTElJ0J4KNJKjZM6qRQ6h5TSgVVOgBX
CgBZekZc2qWo4CjO8QDCx0orZwTsEy0L1CQ3kAEt5U47eG2iRTY2FnTtc4UP5BDFsAF5poGXc6kh
yj3DVqJVkHiYczdEmj8hYJmCagob8iAH5QOq+BkuoGzotgRlYwD/UHhzzaFKL0CrYZhCuDpbH5Bx
5jUmiVYAB/AAwVp7s7VsRXBsP3EEgAIlwfoE1CoWSFEA0naE6+OqrzoK32ows+EBfChiZ+dYoAJu
4jYNROSdS4BtypYF0mNux4Zu9Bo42nYC2fNt4WZ4dFKuRFBtTNCvDeFt0hAcSGEBLTquryB0XOB0
7GoHFEdwKaJ0qPN0ZRN1ITcEI9cEWVdPAqk4YgKxNyGxW0CxfnCxH9geGssqHPtxUkcEIcsEI9uK
G2eySYWyWzlwPhu0KCS0RFu0Rnu0SJu0Sru0F5muZsCHcsi0Rum0ZQC1wyi1LslwV5F72SSuSXCM
U2CO3CgEx4AM/3uEtR4JkRvnAHABkfNgkAh5IHjhdzbCh/VyACuwE0UAkViocEbgKyAQDjHApHn7
GSfAfZfkXg5wAqCGtuiXIaJIAqJIkR4wAvvWjMdhbOYouCvKAnm7t1jItUYQcHdHtlk6AiPQFoGU
eU0niI7riSdgonwrkQvTK3LjnUHxhkPQAxk0BH4lHUZAAmdrBLXnK1QDA4NLBJ70okQAmK8Lu7Kb
PRNpu8LWHsahibwrm2RLpsE7vPmgSnRCAMjLSssbLc77vGeYutXQEBpQQQ7gSZYTK0ghiPHhRQDj
vUzQUqwDfQQQAZYHvBmIvg5JK42BWTLhK0HhjogkBCpVOE+Wq/9MsCEt8IVhur20y1UCLI0r0B9i
gW6f0WjCYQB38wAZsKISkAHQgkgeIIIiEC0Kc8L5a8ItBQKs84JmSiFEYKMZ3IAbTEaOQwEfXDXL
McIlfAAnnMKPtML860FGAMP7I8MVUsNzg8MVvMNmGAIh4AAEME5EYIQwoALZdTcawAFXAQGYOgQy
0AAOQDMagMVaTAQioKlKQMYKYDC9kMZrfHtWOHM2bMU36CdYXEUdYHxdsABZhMVacCAlKgM1+BXG
hRwFMMh97MeeuAGRTAgf0AHShyAbYMlsScmgHMqiPMqkXMqmfMqonMqqvMqsHJPZyQAH1Mr/6Lpj
4Lq98wCi61L/W/wUHiQostyAtCwGtlwAuLwEWtwTBRDLm+LLvwxrRKQbrTM1zfArXfB+dNIMK6Et
F0oEtTBXzbxqObETPZEbRUEVClIXAFAZZ+FimVGmessEk1EfU4wEMrg4QOEX30xrEjY2vEEcQtMP
7FC712xNU3ZJMrYEdzKsRLCfPSjHEpLPsxYyzTI1QCYxFxguMLAvBdME3DIx9pEqRKCpz0IALwPR
rybRYkTSR2DRjNMZGV0EG80EHX0sRFCmNR3SdgktJW3SrbY3O2OARcAiN+QdVAMnQOYEwVBFrqME
gfQb0+UzLsPTr8Y/RSCu55FWUqI/STA8HI0wQioEYLZC+hI8/8NTTioo1ZB5BPGlKUwUTwI0ztwz
ACUAwvpSsTncQ5PkXZXUNm2qKIVkBNPltWhNaiO21uaD12gF1/Mi13QtRXZ92E10EXqdHLnR11oE
UoE92KsmVdgTXvXTT+sEdMIVLRoQzGcaVwwlGwfGnEkQXpqtasWVB4H62kRZpbR927id27q927zd
277928Ad3MI93MRd3MZ93Mid3Mq93Mzd3M793NAd3dI93dRd3dZ93did3dq93dzd3d793eD9CpDY
BSXmwShkxNQcCgdwTQ8ExBchxJiA3pKAxOnDBFh0wkB81Fug33023lxQ3u6tBCac3qCw3hZh3nHW
s5Ig35FA3/8Ezp4l5MH8nQUTLghZvMU2xtBikKhbkOFWOACY88XukBNmfEN4/OCDYHAUcMcZIn2O
p6kYbgD/EBtlAwEiHglPVsdJQDNp0MZaYHA37RvQR+PlYeNJwNpOoOGD0MYhgDXKAwCETAWL7LdF
IMlF8MU68dhP8ORRPi+JEuSb4igGMOU5ZMhM/oTLIwJgEgEGgOV2eHOL3MhmzlODnDBsDgAq8Beg
0QCxAgHKBucZMgNoAchyfMlq/huNKwVPjgR5rjgLsBkcUAEHsgDgCgAncAGCPis+7uRJ4OY3VMYY
ROVkYMhHIMne0eZ+ASgjEOl2xwxNEA4viBR3jgSvCAXggUb/QtPmYCwIeOEr5XHJTKDGfqGhMADL
xs4EnvwLN4flS2DsysxAnQzskVLpAPAAM6DGMvjlAADLHGRwYq3FtjTIOCLpuq4EFVDsxy5omuzt
Q0AA0c6CLWQL5Z4B1i7sqKEOymyDTlgel7E83jwrMsHt3J7JcBPuxzc2uh48vsK22nAA5y4Exn4C
BM/uuCydy97oLpUNGgrx3C42K1TMAi7i9C5KTiDGBFDM7x5/YZ7wQnDtDJ8vz64EuL4c2g4ALk8F
4L7Q8U7tf9DrtfQdn4wE9k7szh7zPCrtK8/sSuDsS+DuyZ4w1F7vbEsE2t7x3+Ht5ZDz2xd/OXLx
5o7uHZ/J/9I3AMTk9MAe7zQPxiNv716d7y348/3u1Uqw8QLvCwQP7QJ48NyD5fTeihrh8F8e8RNP
9tX+xkhw8Xzy8uyT7l388bns5Wpv7VFg8ijvySpP7krv8hoPGLbOxKg+BDc/BVp/Izuf6HjghP9w
AirF8oJWA3zOAX4SDL2TzEk+NQ1V7tqiALNv9EJwhdLjRUY2rR/g+hIj+yJoBC4mx+kd/DUfZvUd
iVOMyDeyPCdgZEiB8QDg+kOw61g4z0+U+vMgnZERKrr/HbBMAA4gSocM/ZYMDaq/9xwzKNwvguff
EBWm/EewctoPSrPPU47s40AAEA6JAwMMoOB4hI0RZ0IsFP8YjGEBsJhoQgCHZDM9DSUDoUrIFD6J
BOIbDti8CeXj0POpEVUKBQEr7s2B6MSwzkxQcZGx0RGO4m1hQ0BApInB4AgN4OWDTyFFwCKwceGt
oyHTYLFPlHTRjfB06LJBUYYodLRUqKONRmiyNtWRE8BiyEoo8FhoDkBEJNWKlehTaEVwGaDXK0tI
INqRZCiFeVmtIIBChSCYYLLyUoj7+ls7nLRquQOrndEtOC+GlCOS7Jo/ds62AWDFyZMMByTyvaKy
7IPCITQcxKM05JcQawqIEDL3SIgbItNEviEohKIrcY2CEbE0TSBKnTt5phwkIZuvDgyMIEnyJt9O
k0K6DEn/JGhFBRUpUjxYpGHIUgAhWA6BcewlHKslBwnRyjUko6hTz9XDQMDBGAAZ3gAFoO3Sr6dp
hsyEw+1EWgddTGZY0TTgEE5jAWAQIheABkIhvhwwDDIOkxkA/LbtBhiAykVprR1t8sZz1sAE6DLS
C8CoAg8vZjSYyfYBrNBxycahByAR2M09t75BbM80ANtrUyvSeoBIWuLTqRMZPoQx9G44GahkSEHA
CiVqFg1+8EAlCwEFcC6KJGSJogIESmw9L+SAevZDCJxA0Kc+IcDD4w3kAmQMABa6cQQ88YjYgJ8r
3hgLOnFseYMkn+KARogPZpivvhDuAyA/R7AJj696mCIi/8Q42KNGlxLyEG28ByZZJgQPG3lRFSH+
I2lGIjgoUIpGLvROARk/UEm8JWxUMcchSjAPPSH0AwBG/wDMY4ikGjGPCAV9ecMZAhrMUD76Bksp
gPzWqw7O6q4TIjtmuPPujTPjY4TK9NZrT5H3ANjTRfrso1C/3/r7MUAABkxRmTcODHPBRs58MEJm
JsSPs3FyEgJN0d7gEAAPQTwUPzEZOTEf8nBksTg4eLQnySBBdfJGpnRkZFYf+wDAVviIlJCRI8+o
dclsaqTFiiiFmFLEKhN8M0tGuQzqETCHUFU6AMq8dBEQ1wytzSvjPHcnuCADYIQhAggHjhMc6ANN
CcJzkP8RJUYAoQchAshAAK4CsncF8bQqpAMEBt0XgAAc5kxgAKyQ15kGCMY3UiIQ0JeId4X4TZBP
sXPrsbQYbniILjoQjJMRGhA5LhtLiSskDk5+uBGXLb5XAUJkbgwkhW3mF+eAp+mWpHaJMBiAJzVs
BK0hKE7C5XAK7vkKBt7ijRG0hjIrDr+GWCAQdW/dt9+GAY5m5cfmpbovlDj299+tuupv3qSXZiSw
jYcEoAeH60aX8Ee0RkwJQlpo4V03H2CJghz/KxwlGcwEgAQ0HVm8cfUYUdhMsR8IAEJ7ItCc8XLF
hqMEBHJh8YOxqhDiggZO/5tzEj2fhoHIh0hS4Rhj9xj/3dZDAy/zUkeX+PDaIxjUgQcWR7f0wkNP
3t/SHXPEwpQ/YDQl5JNs2uPDKe8p9Wllj/z7JFq3XNDz5Z8/ggrOcQCEFvwF2Pj5/T+/IwvQjRAq
8Lwh5E9wrRGEASjQKPhwYCmlKEEBs5K/hg0OAS/7X5wuAoAJzk+A3tggdQrwAAdooDQWwwEJ/jbC
+aGwgSJz4Qx5Ur/7WVBtAugfDXmokwAOEAAUPGDqBrfABr6BAxAklgeF6AULOqw1GZRhD3c0uw/K
L4RUJE4JT5hCCaywhVqMEwxLMEUxnhGNaVTjGtnYRje+EY5xlOMc6VhHO94Rj3nU4x752Ec//hGQ
gRTk/yAJWUhDHhKRiVTkIhnZSEc+EpKRlOQkKVlJQQYABTyxgRkJeYGw4LEACcDAXgAQgRjY4BuJ
dMAFLNnKRlQCJaujogAbEQUixCAHjJwBK+Mkqv8hgAAJEGVfFmAAXN7Ckx5AUCAbMCc42BKOwXSl
/2D5CFn2kJaMgKYQcKlLXsLJl/4DpjC3x5liHhMAyVwmIJu5iG26UZrTlN8W4nABTzJmAwlYAAsM
OL8D5JMWQdSAwkgJB1FigJ5CgAAAcqAVC2zgn4wIwBgyoB1mHJQIB4BADLxgTyE89J8JQJdGOXqw
N/DzeQP96ESVxhkOAEKkPdlnKSvQiL8NMzJD2GhH7/8pCZTW1BGhLCeniFNQQbyToen8JhECeq6G
svIFuZnOS6cTU3kqIgoSCOgESGDPF6jBBQcwgQV0kC4TNCahJIoBV4kwurCOFQAQiED9EBA8RRDA
BKKEZpvWapCvutWicaBADTrggBFYgwPAzGs5F9AmAHAVqsoMQFh7AkwA4FSrfEXqEMaqA7nWDwAI
oMBgC6tQASQ2nPX8K2fJ+llG+OWsj9VAZgsihK8SobNydQRqYzs2InS1E8pkrWcNWNfR7kERep3t
EPrq0SG8dQhzDa1dedLXdN52J4dd6N8Wu1lBBPaqcMAAQsvQkiF8k3g7SaxQtzeANhlgAC2NnQUm
Owf/hAQRqIugrhDcy1/aXWC+6Y1DA16XCAicFgGhLAKJgPPfADdCBh0gwFMQLNTHDuEApYGDC7Zl
wApMQAEEJg1KRtBVAOMztv1c4BDsSt7+Nph2cOjtIoxw4MQOgbxFKLE9sVHfsYqpAh8OcbgOCs0M
w+Qgk+1w/T7chgGY4cCMgC/meJkbJVvpeUGOzoRrPKgEY9RfR95xx8KriPFOoLwOIQJ6ibNeMLs3
w/EdQoBdYN8haPlzcHhxInhs5YAU2LRuXjB0+Hxi+kJYwhR2s2OMrOE3cBjLBASxiIfg6EXs+MRD
2ECKpcxiHKN5z+eVsSNqjOBP24W/mO5xnX9MQCFz/7IbRcawNQyyUkgnaK5B3iaX43pNIkwZuE2j
7635id8tP9kA2/3yeN0l5mD7q8yCEKaAoC1qOk1HAPulQGPbZFUAi8CtlyWCigUhS0FpZwQ8Bjcj
RGMN+ILHskOIROPO++110oHAmXjKo0Q6VAGTeQiZpOkfCOwUlFi1VM8NOCMoHAdaWHSpRGW4EQbw
qMsi9A0J8CVgE8Ahct8VDsQLZ3pRsNAgDkEG+qa4RA+g8XbZ+8obKHmuUe4UVsA7mFbl9mUJ0NKm
RTsOdk1EemuScCHcupQfH1YRJuBenAEA1cu7NQqUvvRAPMVjCG8E8WxpVP+aIev3WEQAJJDBCZgc
S/+etuqL45AdTscB7cgJORHIQ7wZw90Xy0jwEGxJvKK7CyVeHyrKxOIwygqh6nDYL4zlIBbcRtfT
CvU6md8lUlQTHgBwLWXk/TuUsu/d4M94AzaATgRUQ2MCBxCctz/wgXUQoeSMkDupfi2BEADY9W1y
QcdjvwgGNKAOCuv4u1L/rgAkwAC2j/gbImAA6BAAAeJItgR+L6oNBGAAqfcX8pUv5QMsAPp+QTVQ
gnn97IN3zrk/AKRn7vyAQmD6cn9Deu3SeiysX+s2gT8Exj/O6xP1+GQFJSxNCLTu35bKogSOwUCu
ABsm+y5IwEgPAG4N7ZqKAN8gCoxPzeZM4RTKtxT/ihX6j+ku6A2WL9pUASgSLLY0YABU7w08AMAy
ivbgAL4IoEeYwQQWIANYkAgSYACAIgYtYP3k4L7u6gZVcC54sGHy6QcXAQUowAwOoAACBP4GwAbf
4KwUyGGY0FKugAqnDAVDqwCyECsEIdMsygKesAWXBv4aoQW3MKZg8BOEEOkkJTzQTmI8CPR28A3j
QALVQhCoiwVVj3gkQA6l6hnSEAoXAQWNJwfpog/5yxCDcAg3IA0lDkUYQQsbz9oWEBkwTApL4A5r
sBGJABJLLyAYIAXHUAgGUcDkUAalzApvsBseUQkLsAkpkcMssRFsUO9YkQ+zxwcvDw7UkESmEARn
/xEL58JdSMcHu5AZvtAMwhAJd1ARznAIFHENu6QNGY4Q8ykNdFERRHEF8NAKWicQ+NAF4eAPF8FL
NIYIXLEQD/G+LNEYFaERFeYRgWMdgWMS57ASL9ETM3ERNpFUvgkNQXEKR3EWVdGBThEVFYH6bsH2
7o0RIAD93mD/qK+tHuAGMkCB5EkCEiDDvs8NyjEEf08nbs/+CIcCCNF/PjID4kdAWLIdJYE+UHII
gK8ihQAkX5J4Ko4lsXADiDEOqq8RNkAoWcn1IkGsoKEkwc+B2u4jHYUQ/0koO6QAnNIEOMT9PEgb
pk85REUm9Swii+cspwMDps0A/o0nRgsGDWkmKf8gLhehLQsg+vzCBgvgACxyjpCPFUTIJXwABAAA
BEZrAgNAB8/rA5iAApxvOgoTDpoqLSvTMi+zcBIgryCTjSzAA8gDM0NTNEeTOjQT+TJSjDwTNEmT
NVvTNd9gABor/9AIB3bABF8TN3NTN3eTN3vTN38TOINTOIeTOIvTOI8TOZNTOZeTOZvTOZ8TOqNT
OqeTOqvTOq8TO7NTO7eTO7vTO78TPMNTPMeTPMvTPM8TPdNTPdeTPdvTPd8TPuNTPueTPuvTPu8T
P/NTP/eTP/vTP/8TQANUQAeUQAvUQA8UQRNUQReUQRvUQR8UQiNUQieUQivUQi8UQzNUQzeUQzsn
1EM/FERDVERHlERL1ERPFEVTVEVXlEVb1EVfFEZjVEZnlEZRNAgAADs=

------=_NextPart_000_000C_01C78FEE.BFF94000--




From hubmib-bounces@ietf.org Mon May 07 09:33:52 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hl3La-0000Or-IH; Mon, 07 May 2007 09:33:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hl3LY-0000Iw-B5; Mon, 07 May 2007 09:33:48 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hl3G8-0000Bj-0U; Mon, 07 May 2007 09:28:12 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id DF8A326E9D;
	Mon,  7 May 2007 13:28:11 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hl3G7-0001wt-QV; Mon, 07 May 2007 09:28:11 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1Hl3G7-0001wt-QV@stiedprstage1.ietf.org>
Date: Mon, 07 May 2007 09:28:11 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: hubmib@ietf.org
Subject: [Hubmib] Last Call: draft-ietf-hubmib-efm-cu-mib (Ethernet in the
 First Mile Copper (EFMCu) Interfaces MIB) to Proposed Standard 
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

The IESG has received a request from the Ethernet Interfaces and Hub MIB
WG (hubmib) to consider the following document:

- 'Ethernet in the First Mile Copper (EFMCu) Interfaces MIB '
   <draft-ietf-hubmib-efm-cu-mib-07.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-05-21. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-hubmib-efm-cu-mib-07.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11297&rfc_flag=0


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Mon May 07 11:16:09 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hl4wb-00064k-C4; Mon, 07 May 2007 11:16:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hl4wa-00064b-4z
	for hubmib@ietf.org; Mon, 07 May 2007 11:16:08 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hl4wY-0005kk-Mo
	for hubmib@ietf.org; Mon, 07 May 2007 11:16:08 -0400
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id l47FFqTC001841;
	Mon, 7 May 2007 10:16:03 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 May 2007 10:16:02 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.26]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 May 2007 17:15:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: FW: [Hubmib] Last Call: draft-ietf-hubmib-efm-cu-mib (Ethernet in the
	First Mile Copper (EFMCu) Interfaces MIB) to Proposed Standard 
Date: Mon, 7 May 2007 17:15:49 +0200
Message-ID: <D4D321F6118846429CD792F0B5AF471F2EADAF@DEEXC1U02.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Hubmib] Last Call: draft-ietf-hubmib-efm-cu-mib (Ethernet in
	the First Mile Copper (EFMCu) Interfaces MIB) to Proposed
	Standard 
Thread-Index: AceQrHzjTq31IX1BShuNE/U5vu+5UgADKiWg
From: "Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com>
To: <STDS-802-3@listserv.ieee.org>
X-OriginalArrivalTime: 07 May 2007 15:15:58.0468 (UTC)
	FILETIME=[9D893440:01C790BA]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: dromasca@avaya.com, Hub Mib <hubmib@ietf.org>
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Dear colleagues at IEEE 802.3,

below is the IETF Last Call (similar to Sponsor Ballot if you like)
for a document that I bet is of interest to you:
=20
   'Ethernet in the First Mile Copper (EFMCu) Interfaces MIB '
   <draft-ietf-hubmib-efm-cu-mib-07.txt> as a Proposed Standard

If at all possible, please review and send any comments you may have to
ietf@ietf.org mailing list by 2007-05-21. If you DO INTEND TO REVIEW
but need more time, pls let Dan and myself know and we will try to=20
accommodate by asking the IESG for an extension.

Reports of the type "I have read this document and support it"
or "we have implemented" or |we are implementing" are also very welcome.

Thanks,

Bert Wijnen
Chair of the IETF HUBMIB WG=20

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]=20
Sent: Monday, May 07, 2007 3:28 PM
To: IETF-Announce
Cc: hubmib@ietf.org
Subject: [Hubmib] Last Call: draft-ietf-hubmib-efm-cu-mib (Ethernet in
the First Mile Copper (EFMCu) Interfaces MIB) to Proposed Standard=20

The IESG has received a request from the Ethernet Interfaces and Hub MIB
WG (hubmib) to consider the following document:

- 'Ethernet in the First Mile Copper (EFMCu) Interfaces MIB '
   <draft-ietf-hubmib-efm-cu-mib-07.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-05-21. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-hubmib-efm-cu-mib-07.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag=
=3D
11297&rfc_flag=3D0


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun May 13 06:15:07 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HnB6U-0004SV-A0; Sun, 13 May 2007 06:15:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HnB6R-0004Rs-TY; Sun, 13 May 2007 06:14:59 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HnB6R-0004Ja-GJ; Sun, 13 May 2007 06:14:59 -0400
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l4DAEwcJ007995;
	Sun, 13 May 2007 05:14:58 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 13 May 2007 05:14:58 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.26]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 13 May 2007 12:14:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 13 May 2007 12:14:49 +0200
Message-ID: <D4D321F6118846429CD792F0B5AF471F2EADD7@DEEXC1U02.de.lucent.com>
In-Reply-To: <457D36D9D89B5B47BC06DA869B1C815D03F59FAB@exrad3.ad.rad.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-ietf-hubmib-efm-cu-mib (Ethernet in the First
	MileCopper (EFMCu) Interfaces MIB) to Proposed Standard
Thread-Index: AceSPo4Bu47WtPQrQ2S/s9YJ2K/U0QDBoNkQ
References: <457D36D9D89B5B47BC06DA869B1C815D03F59FAB@exrad3.ad.rad.co.il>
From: "Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com>
To: "Yaakov Stein" <yaakov_s@rad.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 13 May 2007 10:14:54.0514 (UTC)
	FILETIME=[8D0F1120:01C79547]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: hubmib@ietf.org, iesg@ietf.org, STDS-802-3@listserv.ieee.org
Subject: [Hubmib] RE: Last Call: draft-ietf-hubmib-efm-cu-mib (Ethernet in
	the First MileCopper (EFMCu) Interfaces MIB) to Proposed Standard
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org


Yaakov, myself (as HUBMIB WG chair and proto-document-shepherd),
the editor and our AD have had some private email exchanges to=20
discuss how to best address the comment from Yaakov below.=20

We have agreed to the following solution:

- we do not change the 802.3ah terminology in the text.
  the main reason for this is to keep consistency with the other
  EFM related MIB RFCs we have published recently.
- We have already explained (1st para on page 3) that IEEE Std
  802.3ah-2004 has been integrated into IEEE Std 802.3-2005.
- We understand that an abstract plays an important role for
  people who search for documents/specifications. So the proposal
  is to add a note to the abstract.

Specific change proposed:

OLD:
   Abstract

   This document defines Management Information Base (MIB) modules for
   use with network management protocols in TCP/IP based internets.
   This document describes extensions to the Ethernet-like Interfaces
   MIB and MAU MIB modules with a set of objects for managing Ethernet
   in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL,
   defined in IEEE Std 802.3ah-2004.  In addition a set of objects is
   defined, describing cross-connect capability of a managed device with
   multi-layer (stacked) interfaces, extending the stack management

NEW:
   Abstract

   This document defines Management Information Base (MIB) modules for
   use with network management protocols in TCP/IP based internets.
   This document describes extensions to the Ethernet-like Interfaces
   MIB and MAU MIB modules with a set of objects for managing Ethernet
   in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL,
   defined in IEEE Std 802.3ah-2004 (note: IEEE Std 802.3ah-2004 has
been
   integrated into IEEE Std 802.3-2005).  In addition a set of objects
   is defined, describing cross-connect capability of a managed device=20
   with multi-layer (stacked) interfaces, extending the stack management
  =20
Our AD (Dan Romascanu) will include a note-to-RFC-editor to request
that this change be made during the RFC-Editor Editing phase.

I assume that everyone is OK with that. However, if anyone does see an
issue with it, pls let us (and the IESG) know asap.

Bert Wijnen
Chair of the IETF HUBMIB WG

> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
> Sent: Wednesday, May 09, 2007 3:33 PM
> To: ietf@ietf.org
> Subject: Last Call: draft-ietf-hubmib-efm-cu-mib (Ethernet in=20
> the First MileCopper (EFMCu) Interfaces MIB) to Proposed Standard
>=20
> Sorry for the nonsubstantive content, but ...
> =20
> The Abstract of this draft refers to IEEE Std 802.3ah-2004.
> This was the output of the EFM task force, which completed=20
> its work several years ago.
> All content has been absorbed into the 2005 version of 802.3.
> =20
> In particular, generic issues on copper are in clause 61,=20
> 10PASS-TS is covered in clause 62 and 2BASE-TL is addressed=20
> in clause 63.
>=20
> Although the inclusion into the base standard is mentioned=20
> later on in the document, the precise clauses are not, and=20
> the 802.3ah nomenclature persists throughout the document.
>=20
> This behavior is similar to another forum insisting on=20
> referencing an Internet Draft, even after an RFC has been issued.
>=20
> Y(J)S
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From jzg@triwire.net Sat May 19 14:00:19 2007
Return-path: <jzg@triwire.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HpTE3-0000la-Fz
	for hubmib-archive@lists.ietf.org; Sat, 19 May 2007 14:00:19 -0400
Received: from adsl-145-75-42.asm.bellsouth.net ([72.145.75.42])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HpTE3-00043M-1d
	for hubmib-archive@lists.ietf.org; Sat, 19 May 2007 14:00:19 -0400
Received: (qmail 20301 invoked from network); Sat, 19 May 2007 11:00:08 -0700
Received: from unknown (HELO laa) (127.149.203.158)
	by adsl-145-75-42.asm.bellsouth.net with SMTP; Sat, 19 May 2007 11:00:08 -0700
Message-ID: <000801c79a3f$89959fd0$9ecb957f@laa>
From: "Lawrence Madden" <jzg@triwire.net>
To: <hubmib-archive@lists.ietf.org>
Subject: Educational feeds can be submitted to the educational feed directory free of charge.
Date: Sat, 19 May 2007 11:00:08 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

GPSI Announces Market Attack Into $1 Trillion Market!

Global Payment Solutions
Symbol: GPSI
Price: $0.03

GPSI announced its plans to address the huge influx of immigrant workers
into the US that need banking solutions that they otherwise would not
qualify for. This market is expected to represent over $1 Trillion
dollars to be managed by 2008. GPSI provides viable solutions to this
market. This is hot, read the news and watch for more Monday! Get on
GPSI first thing Monday!

November Free Autodiscovery Tool - Automatically generate autodiscovery
code for RSS feeds that can be inserted into your website.
If you want to do a podcast, this is the program you need.
The room should also have a door, so that you will not have unexpected
interruptions. Create sound effects, record music or interviews, edit
and layer clips to provide commercial quality recordings. A little due
diligence will go a long way.
Search newsgroups and Google for the interviewees name, product, or
company, and build a background.
I'm also awarding it the Tucows Editors Choice Award for excellence.
RSS Scripts Directory - Subscription based directory containing numerous
PHP scripts for managing RSS feeds. Some podcasts are password
restricted to students who are enrolled in that specific class.
Obviously, the larger files might intimidate listeners with a slow
connection. RSSFilter can be used in conjunction with RSSmesh to filter
and merge multiple RSS feeds as well.
Not surprisingly, podcasters, just like radio stations, have looked for
ways to profit from their on-air dialogue.
Not surprisingly, ideas for blog posts or RSS feed items originate or
are influenced by other web content.
Supports iTunes extensions. While other institution's publicly post
their podcasts and offer non-enrolled students insight into the class
material. Some podcasts are password restricted to students who are
enrolled in that specific class.
Easily record and edit audio files to create professional sounding
podcasts.
Now, this is software that you actually buy.
Social Bookmarking Icons - Create bookmarklets to insert into your
webpages to increase popularity.
The iPod however comes with very little documentation.
This also means you can easily create iTunes compatible podcasts.
Files can be imported or recorded. This also means you can easily create
iTunes compatible podcasts.
htm Podcasting Quiz  How much do you know about podcasting? htm Looking
for Innovative RSS Ideas?
Enter the coupon code ffanews .
PodSafe Music  Podsafe music refers to music specifically for
podcasters. Educational feeds can be submitted to the educational feed
directory free of charge.




From belh@orange.net Sat May 19 14:07:08 2007
Return-path: <belh@orange.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HpTKe-0005Au-Au
	for hubmib-archive@lists.ietf.org; Sat, 19 May 2007 14:07:08 -0400
Received: from 242.159.broadband4.iol.cz ([85.71.159.242])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HpTKc-0007K7-Lj
	for hubmib-archive@lists.ietf.org; Sat, 19 May 2007 14:07:08 -0400
Received: from wexq ([136.212.188.112])
	by 242.159.broadband4.iol.cz (8.13.5/8.13.5) with SMTP id l4JI9UZl007140;
	Sat, 19 May 2007 20:09:30 +0200
Message-ID: <000e01c79a40$7fc1a4d0$70bcd488@wexq>
From: "Huffman Freda" <belh@orange.net>
To: <hubmib-archive@lists.ietf.org>
Subject: emphatic heel
Date: Sat, 19 May 2007 20:07:01 +0200
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_000A_01C79A51.4340B0D0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 3.8 (+++)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e

------=_NextPart_000_000A_01C79A51.4340B0D0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_000B_01C79A51.434321D0"

------=_NextPart_001_000B_01C79A51.434321D0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable


Email open rates have plummeted, filtering systems have become =
increasingly complex and with the complexity and volume even "approved" =
messages have been unable to get through.
RecordForAll is so impressive that it's truly a "Must Have Application".
In this game, that constitutes a highlight.
" hurrahs BC, taunting us by reminding us that football can be =
entertaining. 'Britain's almost undeviating support for the ill-advised =
policies of President Bush in Iraq have been a major tragedy for the =
world,' he added. What started as a hobby for many, has turned into a =
lucrative profession for some. "Before logging on to this website and =
reading your comments, I was wondering why there are no sounds coming =
out of the Irish pub next door," reveals Jan Krcmar in Prague.
The iPod tutorial is even designed to help advanced iPod users to take =
advantage of the iPods more advanced and complex features. The script =
also creates an index of feed items as a separate web page. July New RSS =
Knowledgebase - Questions and answers related to, web feeds, data feeds, =
XML, podcasting, itunes, mediaRSS, namespace extensions and =
videocasting.
, sorry, Prince William tottered out on to the hallowed turf to deliver =
a few words that were barely audible above the highly commendable =
efforts of both sets of fans to drown him out.
and against the outside of the post!
, sorry, Prince William tottered out on to the hallowed turf to deliver =
a few words that were barely audible above the highly commendable =
efforts of both sets of fans to drown him out. The Welshman was sent =
through by a smart Rooney ball, but he spent so long sizing up his =
options that Essien was able to get back and boot the ball out for a =
corner. As such, NotePage, Inc.
------=_NextPart_001_000B_01C79A51.434321D0
Content-Type: text/html;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-2">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><IMG alt=3D"hyphen" hspace=3D0=20
src=3D"http://zzcrane.com/incapable.gif" align=3Dbaseline=20
border=3D0></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Email open rates have plummeted, =
filtering systems=20
have become increasingly complex and with the complexity and volume even =
"approved"=20
messages have been unable to get through.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>RecordForAll is so impressive that it's =
truly a=20
"Must Have Application".</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In this game, that constitutes a=20
highlight.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>" hurrahs BC, taunting us by reminding =
us that=20
football can be entertaining. 'Britain's almost undeviating support for =
the=20
ill-advised policies of President Bush in Iraq have been a major tragedy =
for the=20
world,' he added. What started as a hobby for many, has turned into a =
lucrative=20
profession for some. "Before logging on to this website and reading your =
comments, I=20
was wondering why there are no sounds coming out of the Irish pub next =
door,"=20
reveals Jan Krcmar in Prague.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The iPod tutorial is even designed to =
help advanced=20
iPod users to take advantage of the iPods more advanced and complex =
features. The=20
script also creates an index of feed items as a separate web page. July =
New RSS=20
Knowledgebase - Questions and answers related to, web feeds, data feeds, =
XML,=20
podcasting, itunes, mediaRSS, namespace extensions and =
videocasting.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>, sorry, Prince William tottered out on =
to the=20
hallowed turf to deliver a few words that were barely audible above the =
highly=20
commendable efforts of both sets of fans to drown him out.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and against the outside of the =
post!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>, sorry, Prince William tottered out on =
to the=20
hallowed turf to deliver a few words that were barely audible above the =
highly=20
commendable efforts of both sets of fans to drown him out. The Welshman =
was sent=20
through by a smart Rooney ball, but he spent so long sizing up his =
options that=20
Essien was able to get back and boot the ball out for a corner. As such, =
NotePage,=20
Inc.</FONT></DIV></BODY></HTML>

------=_NextPart_001_000B_01C79A51.434321D0--

------=_NextPart_000_000A_01C79A51.4340B0D0--




From hubmib-bounces@ietf.org Tue May 22 02:29:39 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqNsI-000762-Td; Tue, 22 May 2007 02:29:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqNsI-00075w-2w
	for hubmib@ietf.org; Tue, 22 May 2007 02:29:38 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqNsG-0007WC-RJ
	for hubmib@ietf.org; Tue, 22 May 2007 02:29:38 -0400
Received: from 12.140.64.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com)
	([135.64.140.12])
	by nj300815-nj-outbound.avaya.com with ESMTP; 22 May 2007 02:29:36 -0400
X-IronPort-AV: i="4.14,564,1170651600"; 
	d="scan'208,217"; a="19110093:sNHT11428776"
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 22 May 2007 08:29:20 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0403DD99@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [WARNING: VIRUS REMOVED.] Fwd: image.jpg
Thread-Index: AcecOoerMosfEPidRXyNcyhfAPGfSwAAAAFx
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "hubmib" <hubmib@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Hubmib] Out of Office AutoReply: [WARNING: VIRUS REMOVED.] Fwd:
	image.jpg
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0099333523=="
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0099333523==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C79C3A.87B01C9C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C79C3A.87B01C9C
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I am out-of-office and will be back in office after June 2nd. Although I =
expect to check email daily there may be delays in answering your mail. =
For urgent matters please leave a message at my office number voice =
mail.

Regards,

Dan

------_=_NextPart_001_01C79C3A.87B01C9C
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>Out of Office AutoReply: [WARNING: VIRUS REMOVED.] Fwd: =
image.jpg</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I am out-of-office and will be back in office after =
June 2nd. Although I expect to check email daily there may be delays in =
answering your mail. For urgent matters please leave a message at my =
office number voice mail.<BR>
<BR>
Regards,<BR>
<BR>
Dan<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C79C3A.87B01C9C--


--===============0099333523==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

--===============0099333523==--




From hubmib-bounces@ietf.org Tue May 22 03:11:56 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqOXB-0004W8-Bw; Tue, 22 May 2007 03:11:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqOXA-0004SW-54
	for hubmib@ietf.org; Tue, 22 May 2007 03:11:52 -0400
Received: from il-mail.actelis.net ([62.90.13.193])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqOX7-0001bW-0K
	for hubmib@ietf.org; Tue, 22 May 2007 03:11:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="WINDOWS-1255"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 May 2007 10:11:59 +0300
Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E0102764A@il-mail.actelis.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RFC 4836 - (minor) textual flaws
Thread-Index: AceXszWo/6MD/JSdSvWybgeVRcZ1pwEdav2g
From: "Edward Beili" <EdwardB@actelis.com>
To: =?WINDOWS-1255?Q?Alfred_H=CEnes?= <ah@tr-sys.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 847361531d5cb2b89126844012e81b58
Cc: dromasca@avaya.com, hubmib@ietf.org, bwijnen@alcatel-lucent.com,
	rfc-editor@rfc-editor.org
Subject: [Hubmib] RE: RFC 4836 - (minor) textual flaws
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

=20
Alfred,

Thank you for the comments. I agree with all of them, however I don't =
feel they warrant an RFC errata.
I'm forwarding your email to the HUBMIB mailing list for archiving =
purposes, so if RFC 4836 is updated your comments would be implemented.

A note on the table formatting - I used xml2rfc tool =
(http://xml.resource.org/) to convert the XML source into TXT and HTML =
formats. Unfortunately current XML format (defined in RFC 2629 and its =
unofficial successor) provides only very basic attributes controlling =
tables appearance - there's no way to specify COLSPAN or ROWSPAN, border =
thickness or text alignment within a cell. That is why the tables look =
like that - I wanted the final draft to be produced directly from the =
XML file, without additional post-processing. My repeated requests to =
the xml2rfc team for the support of table formatting attributes have so =
far been unanswered (I urge the other authors on the list using xml2rfc =
to submit a feature request to the xml2rfc mailing list).

Regards,
-E.


> -----Original Message-----
> From: Alfred H=CEnes [mailto:ah@tr-sys.de]=20
> Sent: Wednesday, May 16, 2007 15:10
> To: Edward Beili; rfc-editor@rfc-editor.org
> Subject: RFC 4836 - (minor) textual flaws
>=20
> Hello,
> after studying the recently published RFC 4836 (revised MAU=20
> MIB) authored/edited by you, I would like to submit a few=20
> comments, pointing out some minor textual flaws I found in=20
> the RFC text.
>=20
> Some of these are legacy flaws (I had decided not to report
> previously) or instances of recurring editorial issues, but=20
> some have been newly introduced.
>=20
> The intent of this note is to make you aware of the issues,=20
> and to possibly address these in future related / derived work.
> Although published policy would perhaps admit the publication=20
> of an RFC Errata Note, IMHO that is not necessary in this case.
>=20
> The items below are presented in (almost) RFC textual order.
> I use change bars ('|' in column 1) and occasionally up/down=20
> pointing marker lines ('^^^'/'vvv') to emphasize the location=20
> of textual issues and/or proposed corrections.
> Modified text has been re-adjusted to match RFC formatting=20
> rules, where necessary.
>=20
>=20
> (1)  Section 3 -- 'rational' quotation -- [legacy]
>=20
> At the end of the first paragraph of Section 3, on page 4 of RFC 4836,
>=20
> |  "interface MAUs."
>                   ^^
> should be written as:
>=20
> |  "interface MAUs".
>                   ^^
>=20
> Rationale: AFAICS, This is the only place left in the RFC violating
>   RFC-Ed policy on 'rational' quotation.
>=20
>=20
> (2)  Section 3.1 -- typos -- [new]
>=20
> The third paragraph of Section 3.1 says:
>=20
> |  In addition, the new definitions are added to the=20
> IANA-maintained MIB =20
> | module, to support Ethernet in the First Mile (EFM) and 10GBASE-CX4
>    interfaces, defined in [...]
>=20
> It should say:
>=20
> |  In addition, new definitions are added to the IANA-maintained MIB =20
> | module to support Ethernet in the First Mile (EFM) and 10GBASE-CX4
>    interfaces, defined in [...]
>=20
> Rationale:
> a) '*the* new definitions' seems to be inappropriate because these
>    new definitions have not been introduced so far in the text;
> b) the comma separates the subject and the verb in the sentence,
>    which better should be avoided.
>=20
>=20
> (3)  Section 3.2.1 -- typo / text formatting -- [new]
>=20
> In the second paragraph of Section 3.2.1, in the 5th line=20
> from the bottom of page 5,  "non- 10GBASE-W type"  should be=20
> spelled "non-10GBASE-W type".
>=20
> Note to the RFC-Ed:
>   Aparently, this is a recurring text-reformatting problem
>   which I have observed multiple times in various recent RFCs.
>   According to my experience, matches to the regular expression
>     /[a-z0-9]- [a-z0-9]/  (in case-ignoring mode)
>   will help find similar problems -- unfortunately, there are
>   perfectly feasible matches as well, but finding the candidate
>   flaws as always is the first step required.  Maybe, something
>   like that search can be added to your nits-checking toolkit.
>=20
> (4)  Section 3.4 -- table formatting -- [new]
>=20
> In the tables on pages 7 / 8, the structure of the IEEE=20
> Managed Object names has been hidden even more by the added=20
> separator lines.  E.g., in Table 1, on top of page 7, the=20
> table formatting IMHO hides the fact that  "oMAU"  is the=20
> prefix to all subsequent
> (partial) object names, and neaer the bottom of page 7, the=20
> 'group change' to the next prefix "oAutoNegotiation" is not=20
> obvious any more.
> Perhaps this is an artifact of new tools used.
> The most simple suggestion for improving the visible grouping=20
> in such tables that comes to my mind is to use modified=20
> separator lines for grouping, and omit the column separator=20
> in group headlines, e.g.,
>=20
> - on top of page 7, modify:
>=20
>   =20
> +----------------------------------+--------------------------------+
>    | IEEE 802.3 Managed Object        | Corresponding SNMP=20
> Object      |
>   =20
> +----------------------------------+--------------------------------+
>    | oMAU                             |                      =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | .aMAUID                          | rpMauIndex or=20
> ifMauIndex or    |
>    |                                  | broadMauIndex        =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | ....                             | ...                  =20
>          |
>=20
> to:
>=20
>   =20
> +----------------------------------+--------------------------------+
>    | IEEE 802.3 Managed Object        | Corresponding SNMP=20
> Object      |
>   =20
> =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
>    | oMAU                                                    =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | .aMAUID                          | rpMauIndex or=20
> ifMauIndex or    |
>    |                                  | broadMauIndex        =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | ....                             | ...                  =20
>          |
>=20
> - and near the bottom of page 7, change:
>=20
>    | ...                              | ...                  =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | .nJabber                         | rpMauJabberTrap or   =20
>          |
>    |                                  | ifMauJabberTrap      =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | oAutoNegotiation                 |                      =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | .aAutoNegID                      | ifMauIndex           =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | ...                              | ...                  =20
>          |
>=20
> to:
>=20
>    | ...                              | ...                  =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | .nJabber                         | rpMauJabberTrap or   =20
>          |
>    |                                  | ifMauJabberTrap      =20
>          |
>   =20
> =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
>    | oAutoNegotiation                                        =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | .aAutoNegID                      | ifMauIndex           =20
>          |
>   =20
> +----------------------------------+--------------------------------+
>    | ...                              | ...                  =20
>          |
>=20
>=20
> An additional artifact has subtly changed the apparent=20
> semantics in table 2, on page 8.  The 'Reason for exclusion'=20
> given for oAutoNegotiation.aAutoNegLocalSelectorAbility in=20
> fact applies to all three objetcs in the oAutoNegotiation=20
> group.  The published form of the table does not properly=20
> represent this fact.  In HTML, the corresponding cell could=20
> be given a vertical span of three rows.
> Incorporating the modification for better grouping support=20
> proposed above, the Table 2,
>=20
>   =20
> +------------------------------------+------------------------------+
>    | IEEE 802.3 Managed Object          | Reason for=20
> exclusion         |
>   =20
> +------------------------------------+------------------------------+
>    | oMAU                               |                    =20
>          |
>   =20
> +------------------------------------+------------------------------+
>    | .aIdleErrorCount                   | Only useful for=20
> 100BaseT2,   |
>    |                                    | which is not widely=20
>          |
>    |                                    | implemented.       =20
>          |
>   =20
> +------------------------------------+------------------------------+
>    | oAutoNegotiation                   |                    =20
>          |
>   =20
> +------------------------------------+------------------------------+
>    | .aAutoNegLocalSelectorAbility      | Only needed for=20
> support of   |
>    |                                    | isoethernet=20
> (802.9a), which  |
>    |                                    | is not supported by=20
> MAU-MIB. |
>   =20
> +------------------------------------+------------------------------+
>    | .aAutoNegAdvertisedSelectorAbility |                    =20
>          |
>   =20
> +------------------------------------+------------------------------+
>    | .aAutoNegReceivedSelectorAbility   |                    =20
>          |
>   =20
> +------------------------------------+------------------------------+
>=20
> should perhaps better be presented as:
>=20
>   =20
> +------------------------------------+------------------------------+
>    | IEEE 802.3 Managed Object          | Reason for=20
> exclusion         |
>   =20
> =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
>    | oMAU                                                    =20
>          |
>   =20
> +------------------------------------+------------------------------+
>    | .aIdleErrorCount                   | Only useful for=20
> 100BaseT2,   |
>    |                                    | which is not widely=20
>          |
>    |                                    | implemented.       =20
>          |
>   =20
> =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
>    | oAutoNegotiation                                        =20
>          |
>   =20
> +------------------------------------+------------------------------+
>    | .aAutoNegLocalSelectorAbility      | Only needed for=20
> support of   |
>    +------------------------------------+ isoethernet=20
> (802.9a), which  |
>    | .aAutoNegAdvertisedSelectorAbility | is not supported by=20
> the MAU- |
>    +------------------------------------+ MIB.               =20
>          |
>    | .aAutoNegReceivedSelectorAbility   |                    =20
>          |
>   =20
> +------------------------------------+------------------------------+
>=20
> Note: I have also added the missing article in front of "MAU-MIB".
>=20
>=20
> (5)  Section 4 (MAU-MIB Module)
>=20
> (5a)  rpMauMediaAvailable -- missing article -- [new]
>=20
> The DESCRIPTION clause in the rpMauMediaAvailable OBJECT-TYPE=20
> macro invocation, at the bottom of page 16, says:
>                                              v
> |         DESCRIPTION "This object identifies Media Available state of
>                       the MAU, complementary to the=20
> rpMauStatus.  [...]
>=20
> It should say:
>                                              vvvvv
> |         DESCRIPTION "This object identifies the Media=20
> Available state
>                       of the MAU, complementary to the rpMauStatus.
>                       [...]
>=20
> (5b)  ifMauMediaAvailable -- missing article -- [new]
>=20
> Similarly to the preceding item, the DESCRIPTION clause in=20
> the ifMauMediaAvailable OBJECT-TYPE declaration, on top of=20
> page 23, says:
>                                              v
> |         DESCRIPTION "This object identifies Media Available state of
>                       the MAU, complementary to the=20
> ifMauStatus.  [...]
>=20
> It should say:
>                                              vvvvv
> |         DESCRIPTION "This object identifies the Media=20
> Available state
>                       of the MAU, complementary to the ifMauStatus.
>                       [...]
>=20
> (5c)  ifMauTypeListBits              (page 27
> (5d)  ifMauAutoNegCapabilityBits     (page 33)
> (5e)  ifMauAutoNegCapAdvertisedBits  (page 34)
> (5f)  ifMauAutoNegCapReceivedBits    (page 34)
>=20
> For completeness and uniformity, it would be useful to amend=20
> the textual references to the bOther bit value in the=20
> DESCRIPTION clauses of these OBJECT-TYPE declarations by=20
> adding the numerical value in parentheses, as it has been=20
> done in all similar places in the text:
>=20
> Change   "bOther"   -->   "bOther(0)" .
>=20
> (5g)  ifMauAutoNegCapability -- tabular formatting -- [legacy]
>=20
> The latest additions to the table in the DESCRIPTION clause=20
> of the deprecated ifMauAutoNegCapability OBJECT-TYPE=20
> declaration have not been aligned properly.
> Near the top of page 32, the RFC says:
>=20
>                        [...]
>                        17       (reserved)
>                        18       (reserved)
> |                      19      100BASE-T2 half duplex mode
> |                      20      100BASE-T2 full duplex mode
>                                ^^
> It should say:
>=20
>                        [...]
>                        17       (reserved)
>                        18       (reserved)
> |                      19       100BASE-T2 half duplex mode
> |                      20       100BASE-T2 full duplex mode
>                                ^^
>=20
> (5h)  mauIfGrp100Mbs -- spurious blank line -- [legacy/repagination]
>=20
> Perhaps as an artifact of the text reformatting (new=20
> pagination), there now is a spurious blank line in the=20
> mauIfGrp100Mbs OBJECT-GROUP macro invocation, on top of page 40.
> The RFC says:
>=20
>                       }
> |
>           STATUS      deprecated
>=20
> It should say:
>=20
>                       }
>           STATUS      deprecated
>=20
> Note to the RFC-Ed:
>   This is a recurring artifact observed repeatedly in MIB modules,
>   but also in other places; where older editions of the text
>   (previous RFC or I-D) had a page break and this is removed
>   in the RFC, sometimes such spurious blank line(s) remain.
>=20
> (5i)  mauModRpCompl2 -- spurious blank line -- [legacy/repagination]
>=20
> Similarly as above, the mauModRpCompl2 MODULE-COMPLIANCE=20
> macro invocation contains a spurious blank line, after the=20
> 8th non-blank text line on page 45.
> The RFC says:
>=20
>               GROUP       rpMauNotifications
> |
>               DESCRIPTION "Implementation of this group is recommended
>                           for MAUs attached to repeater ports."
>=20
> It should say:
>=20
>               GROUP       rpMauNotifications
>               DESCRIPTION "Implementation of this group is recommended
>                           for MAUs attached to repeater ports."
>=20
> (5j)  mauModIfCompl3 -- lost blank line -- [legacy/repagination]
>=20
> In contrast to the two preceding items, in the mauModIfCompl3=20
> MODULE-COMPLIANCE macro invocation, a separating blank line=20
> has been lost.
> At the top of page 46, the RFC says:
>=20
>               GROUP       mauIfGrpAutoNeg2
>               DESCRIPTION "Implementation of this group is mandatory
>                           for MAUs that support managed
>                           auto-negotiation."
>               GROUP       mauIfGrpAutoNeg1000Mbps
>               DESCRIPTION "Implementation of this group is mandatory
>                           [...]
>=20
> It should say:
>=20
>               GROUP       mauIfGrpAutoNeg2
>               DESCRIPTION "Implementation of this group is mandatory
>                           for MAUs that support managed
>                           auto-negotiation."
> |
>               GROUP       mauIfGrpAutoNeg1000Mbps
>               DESCRIPTION "Implementation of this group is mandatory
>                           [...]
>=20
>=20
> (6)  Section 5 (IANA-MAU-MIB Module)
>=20
> (6a)  IANAifMauTypeListBits TC -- formatting -- [legacy++]
>=20
> The SYNTAX clause of the IANAifMauTypeListBits=20
> TEXTUAL-CONVENTION, on page 48 of RFC 4836, contains three=20
> blank lines.
> I suspect that these initially were intended to visually=20
> group the lines according to the speed classes; but this was=20
> never handled correctly; e.g., in :
>=20
>        SYNTAX       BITS {
>               bOther(0),          -- other or unknown
>               bAUI(1),            -- AUI
>               b10base5(2),        -- 10BASE-5
>               bFoirl(3),          -- FOIRL
> |
>               b10base2(4),        -- 10BASE-2
>=20
> a break would perhaps have been appropiate below bOther(0),=20
> not below bFoirl(3), thus not disrupting the group of 10 Mbps=20
> MAU types,
> i.e.:
>=20
>        SYNTAX       BITS {
>               bOther(0),          -- other or unknown
> |
>               bAUI(1),            -- AUI
>               b10base5(2),        -- 10BASE-5
>               bFoirl(3),          -- FOIRL
>               b10base2(4),        -- 10BASE-2
>=20
> In RFC 3636, there was a page break between the 10 Mbps MAU=20
> types and the 100 Mbps MAU types; in RFC 4836, there's no=20
> separating blank line there.
> The addition of the new MAU types (on page 49) finally has=20
> made this grouping scheme impossible/obsolete.
>=20
> I therefore recommend to remove these embedded separating=20
> blank lines from the IANA-MAU-MIB module at the next update,=20
> under the control of the designated expert.
>=20
> (6b)  IANAifMauMediaAvailable -- typo -- [new]
>=20
> Within the DESCRIPTION clause of the IANAifMauMediaAvailable=20
> TC, in the first line of the last paragraph on page 51, a=20
> comma has been dropped.
> For consistency of style and grammar, I recommend to change=20
> back in the IANA-MAU-MIB module (at the next update) the line,
>=20
>          For 10 Gb/s the enumerations map to value of the link_fault
>=20
> to say:
>=20
>          For 10 Gb/s, the enumerations map to value of the link_fault
>=20
> (6c)  OBJECT IDENTITIES for MAU types -- visual enhancement
>=20
> For enhanced readability, I also recommend to insert=20
> additional blank lines below the ASN.1 comments, "-----  new=20
> since ..." in the section listing the OBJECT IDENTITIES for MAU types.
>=20
> This could be done at the next regular update of the=20
> IANA-MAU-MIB module, at the places corresponding to page 56,=20
> 57, 59, and 60 in RFC 4836, respectively; e.g. (on page 56), change
>=20
>      ------ new since RFC 1515:
>      dot3MauType10BaseTHD OBJECT-IDENTITY
>         STATUS     current
>         [...]
> to:
>=20
>      ------ new since RFC 1515:
> |
>      dot3MauType10BaseTHD OBJECT-IDENTITY
>         STATUS     current
>         [...]
>=20
>=20
> (7)  Section 7 -- missing article -- [new]
>=20
> The first paragraph of Section 7, on page 63, says:
>=20
>                         v
> |  This document defines first version of the IANA-maintained=20
> IANA-MAU-
>    MIB module.  [...]
>=20
> It should say:
>                         vvvvv
> |  This document defines the first version of the=20
> IANA-maintained IANA-
>    MAU-MIB module.  [...]
>=20
>=20
>=20
> If you anyway consider adressing some of the above issues by=20
> an RFC Errata Note, please make freely use of the material=20
> supplied above.
>=20
> Best regards,
>   Alfred H=CEnes.
>=20
> --=20
>=20
> +------------------------+------------------------------------
> --------+
> | TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math.,=20
> Dipl.-Phys.  |
> | Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18=20
>         |
> | D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de            =20
>         |
> +------------------------+------------------------------------
> --------+
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Tue May 22 06:14:18 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqRNg-0002bc-8a; Tue, 22 May 2007 06:14:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqRNe-0002bT-Po
	for hubmib@ietf.org; Tue, 22 May 2007 06:14:15 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqRNb-0005gn-Vb
	for hubmib@ietf.org; Tue, 22 May 2007 06:14:14 -0400
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l4MADQBd019286;
	Tue, 22 May 2007 05:13:48 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 05:13:33 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.26]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 12:13:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] RE: RFC 4836 - (minor) textual flaws
Date: Tue, 22 May 2007 12:13:26 +0200
Message-ID: <D4D321F6118846429CD792F0B5AF471F2EAE30@DEEXC1U02.de.lucent.com>
In-Reply-To: <9C1CAB2B65E62D49A10E49DFCD68EF3E0102764A@il-mail.actelis.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Hubmib] RE: RFC 4836 - (minor) textual flaws
Thread-Index: AceXszWo/6MD/JSdSvWybgeVRcZ1pwEdav2gAAwuzNA=
References: <9C1CAB2B65E62D49A10E49DFCD68EF3E0102764A@il-mail.actelis.net>
From: "Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com>
To: "Edward Beili" <EdwardB@actelis.com>,
	=?windows-1255?Q?Alfred_H=CEnes?= <ah@tr-sys.de>
X-OriginalArrivalTime: 22 May 2007 10:13:30.0315 (UTC)
	FILETIME=[D89711B0:01C79C59]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6852087d2a39b5d20c975154ae1cd415
Cc: dromasca@avaya.com, hubmib@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Alfred, thanks for reporting your findings.
As Edward already suggested, I think it is best to
just file these comments so we can pick them up if
we ever do another revision in the future.

Bert Wijnen
Chair of the IETF HUBMIB WG

> -----Original Message-----
> From: Edward Beili [mailto:EdwardB@actelis.com]=20
> Sent: Tuesday, May 22, 2007 9:12 AM
> To: Alfred H?nes
> Cc: dromasca@avaya.com; hubmib@ietf.org; Wijnen, Bert (Bert);=20
> rfc-editor@rfc-editor.org
> Subject: [Hubmib] RE: RFC 4836 - (minor) textual flaws
>=20
> =20
> Alfred,
>=20
> Thank you for the comments. I agree with all of them, however=20
> I don't feel they warrant an RFC errata.
> I'm forwarding your email to the HUBMIB mailing list for=20
> archiving purposes, so if RFC 4836 is updated your comments=20
> would be implemented.
>=20
> A note on the table formatting - I used xml2rfc tool=20
> (http://xml.resource.org/) to convert the XML source into TXT=20
> and HTML formats. Unfortunately current XML format (defined=20
> in RFC 2629 and its unofficial successor) provides only very=20
> basic attributes controlling tables appearance - there's no=20
> way to specify COLSPAN or ROWSPAN, border thickness or text=20
> alignment within a cell. That is why the tables look like=20
> that - I wanted the final draft to be produced directly from=20
> the XML file, without additional post-processing. My repeated=20
> requests to the xml2rfc team for the support of table=20
> formatting attributes have so far been unanswered (I urge the=20
> other authors on the list using xml2rfc to submit a feature=20
> request to the xml2rfc mailing list).
>=20
> Regards,
> -E.
>=20
>=20
> > -----Original Message-----
> > From: Alfred H=CEnes [mailto:ah@tr-sys.de]
> > Sent: Wednesday, May 16, 2007 15:10
> > To: Edward Beili; rfc-editor@rfc-editor.org
> > Subject: RFC 4836 - (minor) textual flaws
> >=20
> > Hello,
> > after studying the recently published RFC 4836 (revised MAU
> > MIB) authored/edited by you, I would like to submit a few comments,=20
> > pointing out some minor textual flaws I found in the RFC text.
> >=20
> > Some of these are legacy flaws (I had decided not to report
> > previously) or instances of recurring editorial issues, but=20
> some have=20
> > been newly introduced.
> >=20
> > The intent of this note is to make you aware of the issues, and to=20
> > possibly address these in future related / derived work.
> > Although published policy would perhaps admit the publication of an=20
> > RFC Errata Note, IMHO that is not necessary in this case.
> >=20
> > The items below are presented in (almost) RFC textual order.
> > I use change bars ('|' in column 1) and occasionally=20
> up/down pointing=20
> > marker lines ('^^^'/'vvv') to emphasize the location of=20
> textual issues=20
> > and/or proposed corrections.
> > Modified text has been re-adjusted to match RFC formatting rules,=20
> > where necessary.
> >=20
> >=20
> > (1)  Section 3 -- 'rational' quotation -- [legacy]
> >=20
> > At the end of the first paragraph of Section 3, on page 4=20
> of RFC 4836,
> >=20
> > |  "interface MAUs."
> >                   ^^
> > should be written as:
> >=20
> > |  "interface MAUs".
> >                   ^^
> >=20
> > Rationale: AFAICS, This is the only place left in the RFC violating
> >   RFC-Ed policy on 'rational' quotation.
> >=20
> >=20
> > (2)  Section 3.1 -- typos -- [new]
> >=20
> > The third paragraph of Section 3.1 says:
> >=20
> > |  In addition, the new definitions are added to the
> > IANA-maintained MIB
> > | module, to support Ethernet in the First Mile (EFM) and=20
> 10GBASE-CX4
> >    interfaces, defined in [...]
> >=20
> > It should say:
> >=20
> > |  In addition, new definitions are added to the=20
> IANA-maintained MIB=20
> > | module to support Ethernet in the First Mile (EFM) and 10GBASE-CX4
> >    interfaces, defined in [...]
> >=20
> > Rationale:
> > a) '*the* new definitions' seems to be inappropriate because these
> >    new definitions have not been introduced so far in the text;
> > b) the comma separates the subject and the verb in the sentence,
> >    which better should be avoided.
> >=20
> >=20
> > (3)  Section 3.2.1 -- typo / text formatting -- [new]
> >=20
> > In the second paragraph of Section 3.2.1, in the 5th line from the=20
> > bottom of page 5,  "non- 10GBASE-W type"  should be spelled=20
> > "non-10GBASE-W type".
> >=20
> > Note to the RFC-Ed:
> >   Aparently, this is a recurring text-reformatting problem
> >   which I have observed multiple times in various recent RFCs.
> >   According to my experience, matches to the regular expression
> >     /[a-z0-9]- [a-z0-9]/  (in case-ignoring mode)
> >   will help find similar problems -- unfortunately, there are
> >   perfectly feasible matches as well, but finding the candidate
> >   flaws as always is the first step required.  Maybe, something
> >   like that search can be added to your nits-checking toolkit.
> >=20
> > (4)  Section 3.4 -- table formatting -- [new]
> >=20
> > In the tables on pages 7 / 8, the structure of the IEEE=20
> Managed Object=20
> > names has been hidden even more by the added separator=20
> lines.  E.g.,=20
> > in Table 1, on top of page 7, the table formatting IMHO=20
> hides the fact=20
> > that  "oMAU"  is the prefix to all subsequent
> > (partial) object names, and neaer the bottom of page 7, the 'group=20
> > change' to the next prefix "oAutoNegotiation" is not=20
> obvious any more.
> > Perhaps this is an artifact of new tools used.
> > The most simple suggestion for improving the visible=20
> grouping in such=20
> > tables that comes to my mind is to use modified separator lines for=20
> > grouping, and omit the column separator in group headlines, e.g.,
> >=20
> > - on top of page 7, modify:
> >=20
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | IEEE 802.3 Managed Object        | Corresponding SNMP=20
> > Object      |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | oMAU                             |                      =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | .aMAUID                          | rpMauIndex or=20
> > ifMauIndex or    |
> >    |                                  | broadMauIndex        =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | ....                             | ...                  =20
> >          |
> >=20
> > to:
> >=20
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | IEEE 802.3 Managed Object        | Corresponding SNMP=20
> > Object      |
> >   =20
> >=20
> =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
> >    | oMAU                                                    =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | .aMAUID                          | rpMauIndex or=20
> > ifMauIndex or    |
> >    |                                  | broadMauIndex        =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | ....                             | ...                  =20
> >          |
> >=20
> > - and near the bottom of page 7, change:
> >=20
> >    | ...                              | ...                  =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | .nJabber                         | rpMauJabberTrap or   =20
> >          |
> >    |                                  | ifMauJabberTrap      =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | oAutoNegotiation                 |                      =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | .aAutoNegID                      | ifMauIndex           =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | ...                              | ...                  =20
> >          |
> >=20
> > to:
> >=20
> >    | ...                              | ...                  =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | .nJabber                         | rpMauJabberTrap or   =20
> >          |
> >    |                                  | ifMauJabberTrap      =20
> >          |
> >   =20
> >=20
> =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
> >    | oAutoNegotiation                                        =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | .aAutoNegID                      | ifMauIndex           =20
> >          |
> >   =20
> >=20
> +----------------------------------+--------------------------------+
> >    | ...                              | ...                  =20
> >          |
> >=20
> >=20
> > An additional artifact has subtly changed the apparent semantics in=20
> > table 2, on page 8.  The 'Reason for exclusion'
> > given for oAutoNegotiation.aAutoNegLocalSelectorAbility in fact=20
> > applies to all three objetcs in the oAutoNegotiation group.  The=20
> > published form of the table does not properly represent=20
> this fact.  In=20
> > HTML, the corresponding cell could be given a vertical span=20
> of three=20
> > rows.
> > Incorporating the modification for better grouping support proposed=20
> > above, the Table 2,
> >=20
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | IEEE 802.3 Managed Object          | Reason for=20
> > exclusion         |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | oMAU                               |                    =20
> >          |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | .aIdleErrorCount                   | Only useful for=20
> > 100BaseT2,   |
> >    |                                    | which is not widely=20
> >          |
> >    |                                    | implemented.       =20
> >          |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | oAutoNegotiation                   |                    =20
> >          |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | .aAutoNegLocalSelectorAbility      | Only needed for=20
> > support of   |
> >    |                                    | isoethernet=20
> > (802.9a), which  |
> >    |                                    | is not supported by=20
> > MAU-MIB. |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | .aAutoNegAdvertisedSelectorAbility |                    =20
> >          |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | .aAutoNegReceivedSelectorAbility   |                    =20
> >          |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >=20
> > should perhaps better be presented as:
> >=20
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | IEEE 802.3 Managed Object          | Reason for=20
> > exclusion         |
> >   =20
> >=20
> =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
> >    | oMAU                                                    =20
> >          |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | .aIdleErrorCount                   | Only useful for=20
> > 100BaseT2,   |
> >    |                                    | which is not widely=20
> >          |
> >    |                                    | implemented.       =20
> >          |
> >   =20
> >=20
> =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
> >    | oAutoNegotiation                                        =20
> >          |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >    | .aAutoNegLocalSelectorAbility      | Only needed for=20
> > support of   |
> >    +------------------------------------+ isoethernet=20
> (802.9a), which =20
> > |
> >    | .aAutoNegAdvertisedSelectorAbility | is not supported=20
> by the MAU-=20
> > |
> >    +------------------------------------+ MIB.               =20
> >          |
> >    | .aAutoNegReceivedSelectorAbility   |                    =20
> >          |
> >   =20
> >=20
> +------------------------------------+------------------------------+
> >=20
> > Note: I have also added the missing article in front of "MAU-MIB".
> >=20
> >=20
> > (5)  Section 4 (MAU-MIB Module)
> >=20
> > (5a)  rpMauMediaAvailable -- missing article -- [new]
> >=20
> > The DESCRIPTION clause in the rpMauMediaAvailable OBJECT-TYPE macro=20
> > invocation, at the bottom of page 16, says:
> >                                              v
> > |         DESCRIPTION "This object identifies Media=20
> Available state of
> >                       the MAU, complementary to the rpMauStatus. =20
> > [...]
> >=20
> > It should say:
> >                                              vvvvv
> > |         DESCRIPTION "This object identifies the Media
> > Available state
> >                       of the MAU, complementary to the rpMauStatus.
> >                       [...]
> >=20
> > (5b)  ifMauMediaAvailable -- missing article -- [new]
> >=20
> > Similarly to the preceding item, the DESCRIPTION clause in the=20
> > ifMauMediaAvailable OBJECT-TYPE declaration, on top of page=20
> 23, says:
> >                                              v
> > |         DESCRIPTION "This object identifies Media=20
> Available state of
> >                       the MAU, complementary to the ifMauStatus. =20
> > [...]
> >=20
> > It should say:
> >                                              vvvvv
> > |         DESCRIPTION "This object identifies the Media
> > Available state
> >                       of the MAU, complementary to the ifMauStatus.
> >                       [...]
> >=20
> > (5c)  ifMauTypeListBits              (page 27
> > (5d)  ifMauAutoNegCapabilityBits     (page 33)
> > (5e)  ifMauAutoNegCapAdvertisedBits  (page 34)
> > (5f)  ifMauAutoNegCapReceivedBits    (page 34)
> >=20
> > For completeness and uniformity, it would be useful to amend the=20
> > textual references to the bOther bit value in the=20
> DESCRIPTION clauses=20
> > of these OBJECT-TYPE declarations by adding the numerical value in=20
> > parentheses, as it has been done in all similar places in the text:
> >=20
> > Change   "bOther"   -->   "bOther(0)" .
> >=20
> > (5g)  ifMauAutoNegCapability -- tabular formatting -- [legacy]
> >=20
> > The latest additions to the table in the DESCRIPTION clause of the=20
> > deprecated ifMauAutoNegCapability OBJECT-TYPE declaration have not=20
> > been aligned properly.
> > Near the top of page 32, the RFC says:
> >=20
> >                        [...]
> >                        17       (reserved)
> >                        18       (reserved)
> > |                      19      100BASE-T2 half duplex mode
> > |                      20      100BASE-T2 full duplex mode
> >                                ^^
> > It should say:
> >=20
> >                        [...]
> >                        17       (reserved)
> >                        18       (reserved)
> > |                      19       100BASE-T2 half duplex mode
> > |                      20       100BASE-T2 full duplex mode
> >                                ^^
> >=20
> > (5h)  mauIfGrp100Mbs -- spurious blank line -- [legacy/repagination]
> >=20
> > Perhaps as an artifact of the text reformatting (new pagination),=20
> > there now is a spurious blank line in the mauIfGrp100Mbs=20
> OBJECT-GROUP=20
> > macro invocation, on top of page 40.
> > The RFC says:
> >=20
> >                       }
> > |
> >           STATUS      deprecated
> >=20
> > It should say:
> >=20
> >                       }
> >           STATUS      deprecated
> >=20
> > Note to the RFC-Ed:
> >   This is a recurring artifact observed repeatedly in MIB modules,
> >   but also in other places; where older editions of the text
> >   (previous RFC or I-D) had a page break and this is removed
> >   in the RFC, sometimes such spurious blank line(s) remain.
> >=20
> > (5i)  mauModRpCompl2 -- spurious blank line -- [legacy/repagination]
> >=20
> > Similarly as above, the mauModRpCompl2 MODULE-COMPLIANCE macro=20
> > invocation contains a spurious blank line, after the 8th non-blank=20
> > text line on page 45.
> > The RFC says:
> >=20
> >               GROUP       rpMauNotifications
> > |
> >               DESCRIPTION "Implementation of this group is=20
> recommended
> >                           for MAUs attached to repeater ports."
> >=20
> > It should say:
> >=20
> >               GROUP       rpMauNotifications
> >               DESCRIPTION "Implementation of this group is=20
> recommended
> >                           for MAUs attached to repeater ports."
> >=20
> > (5j)  mauModIfCompl3 -- lost blank line -- [legacy/repagination]
> >=20
> > In contrast to the two preceding items, in the mauModIfCompl3=20
> > MODULE-COMPLIANCE macro invocation, a separating blank line=20
> has been=20
> > lost.
> > At the top of page 46, the RFC says:
> >=20
> >               GROUP       mauIfGrpAutoNeg2
> >               DESCRIPTION "Implementation of this group is mandatory
> >                           for MAUs that support managed
> >                           auto-negotiation."
> >               GROUP       mauIfGrpAutoNeg1000Mbps
> >               DESCRIPTION "Implementation of this group is mandatory
> >                           [...]
> >=20
> > It should say:
> >=20
> >               GROUP       mauIfGrpAutoNeg2
> >               DESCRIPTION "Implementation of this group is mandatory
> >                           for MAUs that support managed
> >                           auto-negotiation."
> > |
> >               GROUP       mauIfGrpAutoNeg1000Mbps
> >               DESCRIPTION "Implementation of this group is mandatory
> >                           [...]
> >=20
> >=20
> > (6)  Section 5 (IANA-MAU-MIB Module)
> >=20
> > (6a)  IANAifMauTypeListBits TC -- formatting -- [legacy++]
> >=20
> > The SYNTAX clause of the IANAifMauTypeListBits=20
> TEXTUAL-CONVENTION, on=20
> > page 48 of RFC 4836, contains three blank lines.
> > I suspect that these initially were intended to visually group the=20
> > lines according to the speed classes; but this was never handled=20
> > correctly; e.g., in :
> >=20
> >        SYNTAX       BITS {
> >               bOther(0),          -- other or unknown
> >               bAUI(1),            -- AUI
> >               b10base5(2),        -- 10BASE-5
> >               bFoirl(3),          -- FOIRL
> > |
> >               b10base2(4),        -- 10BASE-2
> >=20
> > a break would perhaps have been appropiate below bOther(0),=20
> not below=20
> > bFoirl(3), thus not disrupting the group of 10 Mbps MAU types,
> > i.e.:
> >=20
> >        SYNTAX       BITS {
> >               bOther(0),          -- other or unknown
> > |
> >               bAUI(1),            -- AUI
> >               b10base5(2),        -- 10BASE-5
> >               bFoirl(3),          -- FOIRL
> >               b10base2(4),        -- 10BASE-2
> >=20
> > In RFC 3636, there was a page break between the 10 Mbps MAU=20
> types and=20
> > the 100 Mbps MAU types; in RFC 4836, there's no separating=20
> blank line=20
> > there.
> > The addition of the new MAU types (on page 49) finally has=20
> made this=20
> > grouping scheme impossible/obsolete.
> >=20
> > I therefore recommend to remove these embedded separating=20
> blank lines=20
> > from the IANA-MAU-MIB module at the next update, under the=20
> control of=20
> > the designated expert.
> >=20
> > (6b)  IANAifMauMediaAvailable -- typo -- [new]
> >=20
> > Within the DESCRIPTION clause of the IANAifMauMediaAvailable TC, in=20
> > the first line of the last paragraph on page 51, a comma has been=20
> > dropped.
> > For consistency of style and grammar, I recommend to change back in=20
> > the IANA-MAU-MIB module (at the next update) the line,
> >=20
> >          For 10 Gb/s the enumerations map to value of the link_fault
> >=20
> > to say:
> >=20
> >          For 10 Gb/s, the enumerations map to value of the=20
> link_fault
> >=20
> > (6c)  OBJECT IDENTITIES for MAU types -- visual enhancement
> >=20
> > For enhanced readability, I also recommend to insert=20
> additional blank=20
> > lines below the ASN.1 comments, "-----  new since ..." in=20
> the section=20
> > listing the OBJECT IDENTITIES for MAU types.
> >=20
> > This could be done at the next regular update of the IANA-MAU-MIB=20
> > module, at the places corresponding to page 56, 57, 59, and=20
> 60 in RFC=20
> > 4836, respectively; e.g. (on page 56), change
> >=20
> >      ------ new since RFC 1515:
> >      dot3MauType10BaseTHD OBJECT-IDENTITY
> >         STATUS     current
> >         [...]
> > to:
> >=20
> >      ------ new since RFC 1515:
> > |
> >      dot3MauType10BaseTHD OBJECT-IDENTITY
> >         STATUS     current
> >         [...]
> >=20
> >=20
> > (7)  Section 7 -- missing article -- [new]
> >=20
> > The first paragraph of Section 7, on page 63, says:
> >=20
> >                         v
> > |  This document defines first version of the IANA-maintained
> > IANA-MAU-
> >    MIB module.  [...]
> >=20
> > It should say:
> >                         vvvvv
> > |  This document defines the first version of the
> > IANA-maintained IANA-
> >    MAU-MIB module.  [...]
> >=20
> >=20
> >=20
> > If you anyway consider adressing some of the above issues by an RFC=20
> > Errata Note, please make freely use of the material supplied above.
> >=20
> > Best regards,
> >   Alfred H=CEnes.
> >=20
> > --
> >=20
> > +------------------------+------------------------------------
> > --------+
> > | TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math.,=20
> > Dipl.-Phys.  |
> > | Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18=20
> >         |
> > | D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de            =20
> >         |
> > +------------------------+------------------------------------
> > --------+
> >=20
>=20
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From lulx@mcio.org Tue May 22 11:37:52 2007
Return-path: <lulx@mcio.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqWQq-0007G5-9s
	for hubmib-archive@lists.ietf.org; Tue, 22 May 2007 11:37:52 -0400
Received: from adsl-223-93-215.aep.bellsouth.net ([68.223.93.215])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HqWQo-0006jk-Ol
	for hubmib-archive@lists.ietf.org; Tue, 22 May 2007 11:37:52 -0400
Received: from [177.227.219.136] (helo=wqafo)
	by adsl-223-93-215.aep.bellsouth.net with smtp (Exim 4.62 (FreeBSD))
	id 1ITWTP-0004H1-TM; Tue, 22 May 2007 11:40:31 -0400
Message-ID: <002901c79c87$2db89ce0$88dbe3b1@wqafo>
From: "ably" <lulx@mcio.org>
To: <hubmib-archive@lists.ietf.org>
Subject: htm Looking for Innovative RSS Ideas?
Date: Tue, 22 May 2007 11:38:00 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1250";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

GPSI Closes Deal To Increase Revenue By $2.9 Million Annually!

Global Pay Solutions Inc.
Sym: GPSI
Monday Close: $0.031

The news is out and the deal is done. GPSI will provide 70,000 payroll
cards in the Dominican Republic. Initial revenues of $400,000 will be
followed by services fees over the year estimated at $2.5 Million. This
is huge and only sets the beginning of their move into Latin America.
Get on GPSI Today!

Professors are using podcasts to instruct students and get their
messages out.
It also deciphers the technical jargon used on websites to explain the
iPods various features and functions. Just as the second generation of
search engines and directories evolved into niche topic specific portals
we are seeing the same occur in the area of RSS feed directories and
search engines. If you want to do a podcast, this is the program you
need.
The new version of FeedForAll has full support for extensions and
includes unified publishing that allows publishers to easily upload
files along with their feed. In FeedforAll, the first step in the RSS
creation wizard is to give your feed a title.
RecordForAll, by NotePage, Inc. Reduce extraneous noise by turning off
fans or any equipment.
Now the hard part: how to retain the subscribers to your RSS feed. RSS
Namespace Directory - Collection of popular RSS extensions along with
the details of each. This is a short summary that aptly describes the
contents of the feed. RSS Scripts Directory - Subscription based
directory containing numerous PHP scripts for managing RSS feeds. Easily
remove sound distortions and imperfections with drag and drop editing.
Easily record and edit audio files to create professional sounding
podcasts. Podcasting is not restricted to one educational sector,
professors at prestigest colleges from Bentley to Purdue have flocked to
this medium. Why should a musician podcast? File Finder reviewed
RecordForAll on Tucows.
It is easiest if you use the same location each time, that way the
equipment can remain in place and will not require moving or setup each
time you produce a show. Now, this is software that you actually buy.
has created a downloadable pdf that explains the ins and outs of iPods.
Allowing web publishers to prepublish content weeks or even month's in
advance, knowing that the content will automatically be displayed at the
appropriate time. Contact us and we will provide a free registration key
that can be entered into the trial version. htm Looking for Innovative
RSS Ideas? Listen to previous interviews in which the interviewee
participated, read their blog and articles to get a feel for the
interviewees position on issues. Celebrate valentines day in style with
your feeds conveying the spirit!
The templates allow publishers to display their RSS feeds as HTML web
pages.
Namespace Explanation Please also keep in mind that details for specific
extensions are listed in the Namespace Directory. Today nearly all
software companies use the "shareware" marketing model whether they use
the term or not. How much do you know about podcasting?
A growing number of professors are recording their lectures, the term
coursecasting has been adopted in academia.
Podcasting is not restricted to one educational sector, professors at
prestigest colleges from Bentley to Purdue have flocked to this medium.
May FeedForAll Mac Released - Software to create, edit and publish RSS
feeds on a Mac. Listen to previous interviews in which the interviewee
participated, read their blog and articles to get a feel for the
interviewees position on issues. The iPod tutorial includes screenshots
to assist users in setting up the basics, from the date and time to
their contacts.
The new educational feed search engine groups related feeds by category.
In the music world, these music segments are referred to as intros and
extros. htm  How to Get Ideas for RSS Feed and Blog Posts  Not
surprisingly, ideas for blog posts or RSS feed items originate or are
influenced by other web content. Professors are using podcasts to
instruct students and get their messages out.
Users opt to subscribe the information in an RSS feed.
The details on the new RSS script versions can be viewed in the release
notes of each script. Question: Are there any size limitations to
podcasts?
I give it my highest recommendation. In order to use traditional music
that is heard on the radio in a podcast, podcasters may have to pay
royalties for each time the song is played.
com  NEW iPod Tutorial  NotePage has sponsored a free iPod tutorial that
explains the differences between the iPod models.
Export your work to several popular audio formats. Now, this is software
that you actually buy.
RecordForAll also includes integrated support for FeedForAll podcast
feed creation software, making it the perfect choice for podcasters
interested in high quality audio recordings.
Email newsletters have had an increasing problem with spam. Not
surprisingly, podcasters, just like radio stations, have looked for ways
to profit from their on-air dialogue. Follow these tips and be on your
way to a popular podcast.
Now the hard part: how to retain the subscribers to your RSS feed.
Some podcasts are password restricted to students who are enrolled in
that specific class. Users opt to subscribe the information in an RSS
feed. htm Podcasting Quiz  How much do you know about podcasting?
, is a complete solution for creating podcasts.
Now the hard part: how to retain the subscribers to your RSS feed.
Recording Away from Home  When taking your podcast on the road it is
equally important that the quality of the podcast is not compromised for
the sake of portability. The Shareware Industry Awards are dedicated to
excellence in software. As such, NotePage, Inc. Stay current on the
latest news and tips related to RSS.




From cfjy@keithstern.com Tue May 22 11:42:57 2007
Return-path: <cfjy@keithstern.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqWVl-0001PQ-6C
	for hubmib-archive@lists.ietf.org; Tue, 22 May 2007 11:42:57 -0400
Received: from adsl-223-93-215.aep.bellsouth.net ([68.223.93.215])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HqWVj-0000E1-NA
	for hubmib-archive@lists.ietf.org; Tue, 22 May 2007 11:42:57 -0400
Received: from jwx ([183.179.67.109])
	by adsl-223-93-215.aep.bellsouth.net (8.13.3/8.13.3) with SMTP id l4MFhj3M041431;
	Tue, 22 May 2007 11:43:45 -0400
Message-ID: <000f01c79c87$e3c958d0$6d43b3b7@jwx>
From: "Cecilia" <cfjy@keithstern.com>
To: <hubmib-archive@lists.ietf.org>
Subject: Actually, TWO hot tips!
Date: Tue, 22 May 2007 11:43:05 -0400
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_000B_01C79C66.5CACBC50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

------=_NextPart_000_000B_01C79C66.5CACBC50
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_000C_01C79C66.5CAF7B70"

------=_NextPart_001_000C_01C79C66.5CAF7B70
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: quoted-printable


Joel is the co-creator of ClassicGames.
The problem is that I receive SO many questions about making money =
online there is simply not enough time in the day to answer them.
There are many people searching and just need to get another little =
piece of the puzzle to connect.
If it is as good as I hope, I will share it with you tomorrow.
Two hot tips, as promised.
They're interested in those off-topic pieces too.
I'm talking about outgoing links. and now it's your turn!
------=_NextPart_001_000C_01C79C66.5CAF7B70
Content-Type: text/html;
	charset="windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><IMG alt=3D"commemorate" hspace=3D0=20
src=3D"http://ysurine.com/climatic.gif" align=3Dbaseline=20
border=3D0></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Joel is the co-creator of=20
ClassicGames.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The problem is that I receive SO many =
questions=20
about making money online there is simply not enough time in the day to =
answer=20
them.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>There are many people searching and =
just need to=20
get another little piece of the puzzle to connect.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If it is as good as I hope, I will =
share it with=20
you tomorrow.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Two hot tips, as promised.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>They're interested in those off-topic =
pieces=20
too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm talking about outgoing links. and =
now it's your=20
turn!</FONT></DIV></BODY></HTML>

------=_NextPart_001_000C_01C79C66.5CAF7B70--

------=_NextPart_000_000B_01C79C66.5CACBC50--




From 866jervis@linkbg.com Thu May 24 13:19:55 2007
Return-path: <866jervis@linkbg.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrGyh-00029S-9J; Thu, 24 May 2007 13:19:55 -0400
Received: from [189.173.81.223] (helo=zqxk7.fqc67njx.comcast.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HrGye-0007Wb-7Y; Thu, 24 May 2007 13:19:55 -0400
Message-ID: <91981777747621.6763F0C92A@3B9ID>
From: "(270) 818-7244 Maricela " <755ashish@ku.edu.tr>
To: <grow-archive@lists.ietf.org>
Subject: Re: Geta  Diploma without the hassle!
Date: Thu, 24 May 2007 10:24:22 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: LechKncG6KrUGvmiXgMyO51H37TgS0HpMTEu
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 8bit
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d

Hello Grow-archive!!!

Want the degere but cant find the time?



WHAT A GREAT IDEA!
We provide a concept that will allow anyone with sufficinet work experience to obtain a fully verifiable University Degree.
Bachelors, Masters or even a Doctorate.
Think of it, within four to six weeks, you too could be a college graduat.e
Many people share the same frustration, they are all doing the work of the person that has the degree and the person that has the degree is getting all the money.
Don?t you think that it is time you were paid fair compensation for the level of work you are already doing?


This is your chancet o finally make the right move and receive your due benefits.
If you are like most people, you are more than qualified with your experience, but are lacking that prestigious piece of paper known as a diploma that is often the passport to success.
CALL US TODAY AND GIVE YOUR WORK
EXPERIENEC THE CHANCE TO EARN YOU
THE HIGHER COMPENSATION YOU DESERVE!

Begin Tonight +1     (270) 818-7244
Operators Waiting 

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*













of  the  others. Eagles of Rome's Legions had fallen into enemy hands.of their leaders. And messengers are coming-bringing terms and, for usby  all  the  hardheaded  Roman  gods  that he did not care about suchfor  the way his twenty surviving men-out of four cohorts-had tried tomouth.  They were all treacherous here, all the easterners. "No loss,"command,   the   drums   and  bronze  bells  throbbed,  all  over  theFirst  mass  market  edition:  May 1995 Primed in the United States of




From hubmib-bounces@ietf.org Fri May 25 06:53:16 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrXQ4-0001mU-Jd; Fri, 25 May 2007 06:53:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrXQ3-0001mD-9N; Fri, 25 May 2007 06:53:15 -0400
Received: from il-mail.actelis.net ([62.90.13.193])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HrXQ2-0000uW-7k; Fri, 25 May 2007 06:53:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="WINDOWS-1255"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 May 2007 13:53:36 +0300
Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E0102776F@il-mail.actelis.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-hubmib-efm-cu-mib-07 LC comments
Thread-Index: AcedcixqKzinB449SdaobFBnq7f6hQABCcBQAFDOgYA=
From: "Edward Beili" <EdwardB@actelis.com>
To: <hubmib@ietf.org>,
	<iesg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 748ed3980abc7d4bd6a14905626ff64e
Cc: dromasca@avaya.com, =?WINDOWS-1255?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	bwijnen@alcatel-lucent.com
Subject: [Hubmib] FW: draft-ietf-hubmib-efm-cu-mib-07 LC comments
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Dear members of the HUBMIB WG and IESG,
I have received some important LC comments w.r.t. =
draft-ietf-hubmib-efm-cu-mib-07 from Alfred Hoenes, which I'm forwarding =
together with my replies to the mailing lists.

Regards,
-E.

-----Original Message-----
From: Edward Beili=20
Sent: Thursday, May 24, 2007 2:20
To: 'Alfred H=CEnes'
Cc: bwijnen@alcatel-lucent.com; dromasca@avaya.com
Subject: RE: draft-ietf-hubmib-efm-cu-mib-07 LC comments

Alfred,
Thank you very much for your comments, I fully appreciate the time and =
effort you put into checking the draft. I agree with almost all of your =
comments. See my rebuttal inline below.

Bert,
How do you want me to proceed - should I issue a new version of the =
draft?

Regards,
-E.=20

> -----Original Message-----
> From: Alfred H=CEnes [mailto:ah@tr-sys.de]
> Sent: Wednesday, May 23, 2007 22:39
> To: Edward Beili
> Cc: bwijnen@alcatel-lucent.com; dromasca@avaya.com
> Subject: draft-ietf-hubmib-efm-cu-mib-07 LC comments
>=20
> Hello,
> as recommended by Bert Wijnen yesterday, I've hurried up, and hereby I =

> submit my notes on the more-than-just-editorial issues I found in=20
> draft-ietf-hubmib-efm-cu-mib-07, plus the issues in Section 7 & up.
>=20
> A subsequent message will address the remaining textual flaws in=20
> Sections 1..6  I have observed.
>=20
> All but the last two items below deal with the MIB modules in the=20
> draft.  For brevity, I use the following shorthand notation to locate=20
> the affected part of the text there:
>=20
>       <object_name> D <n>
>                    /    \
>                   /      paragraph number; positive values count
>     DESCRIPTION clause   top-down, negative values count from the end
> or:
>       <object_name> <X>
>=20
> where the following single capital letters <X> are used:
>      S ... SYNTAX clause
>      O ... OBJECTS clause
>      R ... REFERENCES clause
>=20
> The items are listed in textual order.
> Issues spanning more than one object (etc.) will be noted for either=20
> place in the text via cross-references.
>=20
>=20
> (A)  =3D=3D=3D=3D  IF-CAP-STACK-MIB  =3D=3D=3D=3D
>=20
>=20
> (1)  ifCapStackTable D -2
>=20
> Please reconsider the trailing phrase,
>=20
>   "... for any existing value of x or y." .
>            ^^^^^^^^^^^^^^^^^^
>=20
> This might be misleading, since in the preceding text, the scenario of =

> EFM-Cu interfaces is only referred to by "e.g.".
>=20
> The IF-CAP-STACK-MIB obviously has been specified separately with=20
> other areas of applicability in mind, i.e., the ifCapStackTable (and=20
> its inverse) might be applicable for other scenarios of stacked=20
> interfaces too (although not specified yet).
> Currently these tables should only be applied to EFMCu interfaces; in=20
> all other cases where it would be conceptionally valid,=20
> ifCapStackTable rows should not be instantiated unless and until=20
> specified otherwise.
>
> Therefore, I recommend to replace the above phrase by:
>=20
>   "... for any ifIndex values x or y representing an EFMCu PME
>    or PCS, respectively."
>=20
> (or similar).

EFMCu interfaces with flexible cross-connect are just one example where =
IF-CAP-STACK-MIB can be used.
In fact ifCapStackTable (and its inverse) can be implemented for _any_ =
stacked interface. Of course in some cases it would not add any value, =
for example for interfaces without flexible cross-connect, the =
ifCapStackTable would be semantically identical to the ifStackTable - =
meaning that the sublayers which MAY be connected, as indicated by if =
CapStackTable, ARE connected, as indicated by ifStackTable.

The DESCRIPTION text clearly states that ifStackTable describes =
cross-connect capability of the devices with stacked interfaces. Apart =
from EFMCu there are G.Bond interfaces (their MIB modules are being =
drafted) which use this table, so specifying EFMCu here is incorrect. =
While there is no point in implementing this table for devices without =
cross-connect capability, it won't do any harm if implemented.

Therefore, I suggest leaving this text as it is. =20
=20
> (B)  =3D=3D=3D=3D  EFM-CU-MIB  =3D=3D=3D=3D
>=20
>=20
> (2)  efmCuLowRateCrossing O
>=20
> The ASN.1 comment,
>=20
>   -- ifIndex is not needed here since we are under specific PCS
>                                      =20
> ^^^^^^^^^^^^^^^^^^^^^^^^^ is unclear, and in fact not needed at all:
> the ifIndex value occurs in the index part of all the OIDs of the=20
> objects included in this NOTIFICATION, anyway!
>=20
> I recomment to remove that ASN.1 comment entirely, or else to replace=20
> it by:
>=20
>   -- The ifIndex of the specific PCS is delivered in the index part
>      of the OIDs of the following objects' instances.
>=20
> (or similar).

You are right, I wrote this comment for myself, it should be removed.

> (3)  efmCuNumPMEs S
>=20
> The semantics of that object apparently perfectly fit the=20
> specification of the Gauge32 SYNTAX in SMIv2.
>=20
> Are there specific reasons to *not* specify a subrange of
> Gauge32 for this object, but using Unsigned32 instead ?

My understanding of Gauge32 is it should be used for "latched" objects, =
that is, whose information being modeled can be greater than the maximum =
or smaller than the minimum.
Since the number of PMEs can never be negative or more than 32, I =
concluded that Gauge32 is inappropriate here. Please correct me if I'm =
wrong here.

> (4)  efmCuPmeThreshSnrMgn D 2
>=20
> The draft says:
>=20
>           This object is writable for the CO subtype PMEs
> |         (2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype
>           (2BaseTL-R/10PassTS-R).
>=20
> It should say:
>=20
>           This object is writable for the CO subtype PMEs
> |         (2BaseTL-O/10PassTS-O). It is read-only for the CPE subtype
>           (2BaseTL-R/10PassTS-R).

You are right, it should be corrected.

> (5)  efmCuPmeOperSubType D 2
>=20
> The draft says:
>=20
>           The operational sub type of the PME can be configured via
>           efmCuPmeAdminSubType variable.
>=20
> This might be confusing.  It should perhaps better say:
>=20
>              vvvvvvvvv
> |         The desired operational sub type of the PME can be
> configured
> |         via the efmCuPmeAdminSubType variable.
>              ^^^^^

Ok.

> (6)  efmCuPme2BsModeRowStatus D 2
>=20
> The draft says:
>=20
>           If an 'active' entry is referenced via efmCuPme2BsMode, the
>           entry MUST remain 'active' until all references are removed.
>=20
> This is illogical and confusing.
> It should perhaps better (and even simpler) say:
>=20
>           If an 'active' entry is referenced via efmCuPme2BsMode, the
>           entry MUST remain 'active'.

I don't see a big difference between the two, but willing to go with =
your wording. I think though that it is important to remind the =
implementer that there can be multiple references to the same entry =
(from multiple PMEs). So I would suggest to say:

          If an 'active' entry is referenced via efmCuPme2BsMode, the
          entry MUST remain 'active'. Note that there can be multiple
	    references to the same entry.

> (7)  efmCuPme10PProfileTable D 3
>=20
> There are a couple of issues with the table of predefined=20
> efmCuPme10PProfileTable entries presented there.
>=20
> a)  The order of the columns does not exactly match the (OID)
>     order of the columnar objects specified subsequently.
>     This might raise some confusion.
>=20
>     I recommend to exchange the last two columns to achieve
>     a matching order.  (Changing the columnar object sequence
>     and the OIDs for efmCuPme10PPayloadURateProfile and
>     efmCuPme10PPayloadDRateProfile will perhaps not be feasible!)

I agree. Suggest to swap the order of the efmCuPme10PPayloadURateProfile =
and efmCuPme10PPayloadDRateProfile, since the IEEE standard defines =
Downstream rate before the Upstream.

> b)  In the first table row, the "(default)" is attached to the
>     value in the last column without any intervening white space.
>=20
>     I strongly suspect that this tag conceptually is affixed to
>     the entire row, not to the last columnar valu there.
>     I that's right, to avoid confusion, I recommend to insert
>     at least one space character before the "(default)"

Agree, to further avoid confusion I suggest to add the word 'profile' =
after the 'default', i.e.
          1      1      3    2,6,10,11    20    20 (default profile)

> c)  From the 4th row down to the last row, in the third column
>     the value '0' (for UPBO p#) is specified.
>=20
>     But the efmCuPme10PUPBOReferenceProfile SYNTAX does not
>     admit the enumerated value 0, it only allows (1..9).
>=20
>     What's wrong there ???

Right, I added the value of profile(0) to =
efmCuPme10PUPBOReferenceProfile, with a description - no profile.

> d)  The last row (profile index 22) in its second row gives a
>     Bandplan PSDMask# value of '30'.
>=20
>     But the efmCuPme10PBandplanPSDMskProfile SYNTAX does not
>     admit the enumerated value 30, it only allows (1..29).
>=20
>     What's wrong there ???

Missed that one, I added the value 30 with description.

> (7')  efmCuPme10PProfileTable D -3 and D -2
>=20
> Because of item (7) above, I include the following remarks on textual=20
> flaws in the subsequent paragraphs as well:
>                            vvvv
> a) Change:  "... be created by during agent initialization ..."
>=20
>    to say:  "... be created during agent initialization ..."

Agree.

> b) Delete the two commas from D -2.
>=20
>=20
> (8)  efmCuPme10PBandplanPSDMskProfile S
>=20
> See item (7) d)  above!

Agree.

> (9)  efmCuPme10PBandplanPSDMskProfile D 2  and  R
>=20
> a)
> The profile table uses short references for the "PSD Mask":
>    'T1.424/T-U P1', 'TS1 101 270-1', and 'G.993.1 F.1.2.*' .
>=20
> These should be detailed in the REFERENCE clause of the object.

Agree.

> b)
> The ref. label "TS1 101 270-1" is used here, whereas in the=20
> efmCuPme10PUPBOReferenceProfile D, "ETSI TS 101 270-1", and in the=20
> efmCuPme10PBandNotchProfiles D, "TS101 270-1"
> is used for what perhaps denotes the same document.
>=20
> Using a unified notation in all three tables would be appreciated!

Agree.

> (10)  efmCuPme10PUPBOReferenceProfile S
>=20
> See item (7) c)  above!

Agree.
=20
> (11)  efmCuPme10PUPBOReferenceProfile D 2  and  R
>=20
> a)
> As in item (9) a)  above:
>=20
> The profile table uses short references for the "PSD Mask":
>    'T1.424/T-U', and 'ETSI TS 101 270-1' .
>=20
> These should be detailed in the REFERENCE clause of the object.
>=20
> b)
> See item  (9) b)  above !
>=20
>=20
> (12)  efmCuPme10PBandNotchProfiles D 2  and  R
>=20
> a)
> The profile table uses short references for the table heading
>    'G.991.3',  'T1.424/T-U', and 'TS101 270-1' .
>=20
> These should be detailed in the REFERENCE clause of the object.
>=20
> b)
> See item  (9) b)  above !
>=20
>=20
> (13)  efmCuPme10PBandNotchProfiles D -2

Agree

> The draft says:
>=20
>           Any combination of profiles can be specified by ORing
>           individual profiles, for example value of 0x0622 selects
>           profiles 2,6,10 and 11.
>=20
> The hex value given does not match the set of profiles listed.
> [See RFC 3416, Section 2.5, paragraph #2 for the mapping of BITS.]
>=20
> 0x0622 corresponds to 5,6,10,14 !
> (The 1st nibble is for BITS 0,1,2,3, the 2nd for BIT 4,5,6,7, ...)
>=20
> Assuming the set of profiles to be left unchanged, the hex value must=20
> be corrected to 0x2230 .
>=20
> Hence, the draft should say:
>=20
>           Any combination of profiles can be specified by ORing
>           individual profiles, for example value of 0x2230 selects
>           profiles 2,6,10 and 11.

You are right. Must be corrected.

> (14)  efmCuPme10PStatusEntry D + other
>=20
> The draft is not clear about the instantiation rules for rows in the=20
> efmCuPme10PStatusTable.
>=20
> From the D's of the columnar objects it can be concluded that such=20
> rows only make sense for 10PASS-TS PMEs, and that therefore the=20
> instantiation of efmCuPme10PStatusTable rows is not intended for=20
> 2-BASE-TL PMEs, and cannot be assumed to be mandatory in that case.
>=20
> The efmCuCompliance MODULE-COMPLIANCE statement contains the lines:
>=20
>           GROUP       efmCuPme10PStatusGroup
>           DESCRIPTION
>             "Support for this group is OPTIONAL for implementations
>             supporting 10PASS-TS Phy."
>=20
> Hence, even for 10PASS-TS PMEs, the instantiation of=20
> efmCuPme10PStatusTable rows is *not* mandatory.
>=20
> Contrary to that, the efmCuPme10PStatusEntry OBJECT-TYPE declaration=20
> contains the structural specification:
>=20
>         AUGMENTS { efmCuPmeStatusEntry }
>=20
> According to the SMIv2 (STD 58, RFC 2578, Section 7.8), this clause=20
> means that the efmCuPme10PStatusTable is a *dense* augmentation of the =

> efmCuPmeStatusTable, i.e. that the instantiation of any row
> (efmCuPmeStatusEntry) there immediately enforces the instantiation of=20
> the corresponging efmCuPme10PStatusEntry.
>=20
> That makes no sense!
>=20
> IMHO, the above AUGMENTS clause has to be substituted by:
>=20
>         INDEX { ifIndex }

Agree.

> Also, the instantiation rules should be made explicit in the=20
> efmCuPme10PStatusTable D or the efmCuPme10PStatusEntry D .

Agree.
=20
> (15)  efmCuNotificationGroup NOTIFICATION-GROUP
>=20
> The draft says:
>=20
>         NOTIFICATIONS {
>           efmCuLowRateCrossing,
>           efmCuPmeLineAtnCrossing,
>           efmCuPmeSnrMgnCrossing,
>           efmCuPmeDeviceFault,
>           efmCuPmeConfigInitFailure,
>           efmCuPmeProtocolInitFailure
> |  --       efmCuPmeDeviceFault,
> |  --       efmCuPmeLocalPowerLoss
>         }
>=20
> It remains unclear what has been intended with the two lines tagged=20
> above, written as ASN.1 comments.
>=20
> a)
> 'efmCuPmeDeviceFault' is well defined in the MIB module.
>=20
> I cannot see any immediate reason why it is getting excluded from the=20
> conformance groups.
>=20
> Perhaps this line should be re-activated !
>
> b)
> 'efmCuPmeLocalPowerLoss' does not appear anywhere else in the draft.
>=20
> Perhaps this line should be dropped !
=20
Both comments should be removed. efmCuPmeDeviceFault already appears in =
the confirmance group.
=20
> (16)  Section 7
>=20
> In the second paragraph below the bulleted list,
> change   "evasdrop"  -->  "eavesdrop" .

Right.

> (17)  Sections 8, 10, and 11
>=20
> Hint:  To alleviate the job of the RFC-Editor and the IANA,
>        - RFC 4836 and RFC 4837 should be substituted for the
>          respective I-Ds;
>        - the first paragraph of Section 8 apparently is void
>          in the meantime (and hence should be deleted), by
>          publication of RFC 4836 and IANA action for that RFC;
>        - the text in Section 10 can be simplified;
>        - one Normative and one Informative Ref. can be updated
>          immediately from I-D to RFC.

Agree.

> I apologize for any errors introduced into this memo due to its=20
> hastily preparation.
>=20
> If you like, please forward (parts of) this note to the hubmib  list=20
> if you think the issues above should be discussed there.
>=20
> Kind regards,
>   Alfred H=CEnes.
>=20
> --
>=20
> +------------------------+------------------------------------
> --------+
> | TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math.,=20
> Dipl.-Phys.  |
> | Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18=20
>         |
> | D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de            =20
>         |
> +------------------------+------------------------------------
> --------+
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Fri May 25 06:55:21 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrXS5-0001sP-DG; Fri, 25 May 2007 06:55:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrXS3-0001s6-Rb; Fri, 25 May 2007 06:55:19 -0400
Received: from il-mail.actelis.net ([62.90.13.193])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HrXS3-0001cR-1V; Fri, 25 May 2007 06:55:19 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="WINDOWS-1255"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 May 2007 13:55:42 +0300
Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E01027770@il-mail.actelis.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: FW: draft-ietf-hubmib-efm-cu-mib-07 LC comments
Thread-Index: Aced1/QIVBhhTSgeQc+qudlPSy7CcQAATOKwADh3BaA=
From: "Edward Beili" <EdwardB@actelis.com>
To: <hubmib@ietf.org>,
	<iesg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32a65c0bf5eb4ec26489239c7cdd0636
Cc: dromasca@avaya.com, =?WINDOWS-1255?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	bwijnen@alcatel-lucent.com
Subject: [Hubmib] FW: draft-ietf-hubmib-efm-cu-mib-07 LC comments
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Continuation of the previous mail on the subject, below my second reply.
Regards,
-E.=20

> -----Original Message-----
> From: Edward Beili=20
> Sent: Thursday, May 24, 2007 11:58
> To: 'Alfred H=CEnes'
> Cc: bwijnen@alcatel-lucent.com; Dan Romascanu (dromasca@avaya.com)
> Subject: RE: draft-ietf-hubmib-efm-cu-mib-07 LC comments
>=20
> Alfred,
> Thanks again. See my reply inline below.
>=20
> Regards,
> -E.
>=20
> > -----Original Message-----
> > From: Alfred H=CEnes [mailto:ah@tr-sys.de]
> > Sent: Thursday, May 24, 2007 10:48
> > To: Edward Beili
> > Cc: bwijnen@alcatel-lucent.com
> > Subject: Re: draft-ietf-hubmib-efm-cu-mib-07 LC comments
> >=20
> > Edward,
> > thanks for your very quick and detailed response.
> > Please find inline below a few comments on selected open topics.
> >=20
> > > Alfred,
> > > Thank you very much for your comments, I fully appreciate
> > the time and
> > > effort you put into checking the draft. I agree with=20
> almost all of=20
> > > your comments. See my rebuttal inline below.
> > >=20
> > > Bert,
> > > How do you want me to proceed - should I issue a new=20
> version of the=20
> > > draft?
> > >
> > > ...
> > >
> > >> A subsequent message will address the remaining textual flaws in=20
> > >> Sections 1..6  I have observed.
> >=20
> > 'Strategic' consideration for the next steps:
> >=20
> > I have myriads of textual issues, in particular=20
> missing/wrong articles=20
> > etc. to report.
>=20
> BTW, last night when I was looking at the draft I realized=20
> that some of the references, in particular various 10P=20
> related profiles in Clause 30 are wrong, I was using an old=20
> version of the draft at the time of writing and since then=20
> didn't check it. My bad:(
>=20
> > Taking altogether, that IMHO will deserve a new draft, for=20
> clarity and=20
> > for the ease of all parties involved.
> >=20
> > From previous messages I conclude that you start from an XML source.
> > Perhaps it would be much more efficient if you could provide me the=20
> > source, and I could make the proposed changes in a copy thereof
> > (-- this will not happen before Friday evening).  This=20
> would save me a=20
> > lot of time and decrease the amount of text to be produced,=20
> and with=20
> > that version at hand you could certainly derive an accepted version=20
> > more efficiently -- thus speeding up the entire process.
> >=20
> > If you agree, I propose to start from the version after the edits=20
> > already discussed, and perhaps further changes as a result=20
> from other=20
> > comments.  For best timing, your then current intermediate source=20
> > version on Friday evening (in your time zone) would be the best=20
> > starting point.
> >=20
> > Otherwise, if I do not obtain an updated version, I will start from=20
> > the published -07.txt version, for my additional comments.
>=20
> I agree, I'll try to implement all the changes and send you=20
> the final xml file by Saturday night, I'm China now, flying=20
> back home tonight, not sure I'll be able to do this by Friday=20
> night. Since I'm going to check all the references again, I=20
> might as well do it against 802.3-2005 instead of=20
> 802.3ah-2004. That was a comment some time ago from Yakov=20
> Stein, which we decided to decline.=20
>=20
> > >> (A)  =3D=3D=3D=3D  IF-CAP-STACK-MIB  =3D=3D=3D=3D
> > >>
> > >>
> > >> (1)  ifCapStackTable D -2
> > >>
> > >> Please reconsider the trailing phrase,
> > >>
> > >>   "... for any existing value of x or y." .
> > >>            ^^^^^^^^^^^^^^^^^^
> > >>
> > >> This might be misleading, since in the preceding text, the
> > scenario
> > >> of EFM-Cu interfaces is only referred to by "e.g.".
> > >>
> > >> The IF-CAP-STACK-MIB obviously has been specified=20
> separately with=20
> > >> other areas of applicability in mind, i.e., the
> > ifCapStackTable (and
> > >> its inverse) might be applicable for other scenarios of stacked=20
> > >> interfaces too (although not specified yet).
> > >> Currently these tables should only be applied to EFMCu
> > interfaces; in
> > >> all other cases where it would be conceptionally valid,=20
> > >> ifCapStackTable rows should not be instantiated unless and until=20
> > >> specified otherwise.
> > >>
> > >> Therefore, I recommend to replace the above phrase by:
> > >>
> > >>   "... for any ifIndex values x or y representing an EFMCu PME
> > >>    or PCS, respectively."
> > >>
> > >> (or similar).
> > >=20
> > > EFMCu interfaces with flexible cross-connect are just one example=20
> > > where IF-CAP-STACK-MIB can be used.
> > > In fact ifCapStackTable (and its inverse) can be
> > implemented for _any_
> > > stacked interface. Of course in some cases it would not add
> > any value,
> > > for example for interfaces without flexible cross-connect, the=20
> > > ifCapStackTable would be semantically identical to the
> > ifStackTable -
> > > meaning that the sublayers which MAY be connected, as
> > indicated by if
> > > CapStackTable, ARE connected, as indicated by ifStackTable.
> > >=20
> > > The DESCRIPTION text clearly states that ifStackTable describes=20
> > > cross-connect capability of the devices with stacked
> > interfaces. Apart
> > > from EFMCu there are G.Bond interfaces (their MIB modules=20
> are being
> > > drafted) which use this table, so specifying EFMCu here is
> > incorrect.
> > > While there is no point in implementing this table for
> > devices without
> > > cross-connect capability, it won't do any harm if implemented.
> > >=20
> > > Therefore, I suggest leaving this text as it is.
> >=20
> > I fully agree with almost all of your explanation.
> > That's what I reasonably had expected, and what the major=20
> part of the=20
> > DESCRIPTION clause says.
> >=20
> > The ultimate reason for my note was that "any existing"=20
> might well be=20
> > misunderstood to extending the scope of the last sentence=20
> there beyond=20
> > whay is specified in this MIB module.
> >=20
> > To propose a 'least impact' change:
> > What about  "... any such existing value ..."   ?
> >                     ^^^^^^
>=20
> Agree.
>=20
> > >> (3)  efmCuNumPMEs S
> > >>
> > >> The semantics of that object apparently perfectly fit the=20
> > >> specification of the Gauge32 SYNTAX in SMIv2.
> > >>
> > >> Are there specific reasons to *not* specify a subrange of
> > >> Gauge32 for this object, but using Unsigned32 instead ?
> > >=20
> > > My understanding of Gauge32 is it should be used for "latched"
> > > objects, that is, whose information being modeled can be
> > greater than
> > > the maximum or smaller than the minimum.
> > > Since the number of PMEs can never be negative or more than 32, I=20
> > > concluded that Gauge32 is inappropriate here.
> > > Please correct me if I'm wrong here.
> >=20
> > The statement,
> >   "the number of PMEs can never be negative or more than 32"
> > IMHO perfectly represent the expected behavior of an object of
> > Gauge32 (0..32) type.  On page 23, RFC 2578 says:
> >=20
> >  7.1.7.  Gauge32
> >=20
> >    The Gauge32 type represents a non-negative integer, which may
> >    increase or decrease, but shall never exceed a maximum value, nor
> >    fall below a minimum value.  The maximum value can not be greater
> >    than 2^32-1 (4294967295 decimal), and the minimum value=20
> can not be
> >    smaller than 0.
> >=20
> > IMHO, this is a perfect match to the semantics intended for=20
> > efmCuNumPMEs.
>=20
> I'm still not convinced (I've read the Gague32 description,=20
> it just sounds wrong to me to represent a number of apples as=20
> a gauge; speed/throughput/attenuation/acceleration would be=20
> perfect candidates for a gauge), but willing to go with your=20
> suggestion. (Bert/Dan, your advice would be appreciated?)=20
>=20
> > >> (6)  efmCuPme2BsModeRowStatus D 2
> > >>
> > >> The draft says:
> > >>
> > >>           If an 'active' entry is referenced via
> > efmCuPme2BsMode, the
> > >>           entry MUST remain 'active' until all references
> > are removed.
> > >>
> > >> This is illogical and confusing.
> > >> It should perhaps better (and even simpler) say:
> > >>
> > >>           If an 'active' entry is referenced via
> > efmCuPme2BsMode, the
> > >>           entry MUST remain 'active'.
> > >=20
> > > I don't see a big difference between the two, but willing
> > to go with
> > > your wording. I think though that it is important to remind the=20
> > > implementer that there can be multiple references to the
> > same entry (from multiple PMEs).
> > > So I would suggest to say:
> > >=20
> > >           If an 'active' entry is referenced via
> > efmCuPme2BsMode, the
> > >           entry MUST remain 'active'. Note that there can
> > be multiple
> > >           references to the same entry.
> >=20
> > A shorter variant might be:
> >=20
> >             If an 'active' entry is referenced via some=20
> > efmCuPme2BsMode
> >             instance(s), the entry MUST remain 'active'.
>=20
> Agree.
> =20
> > >> (7)  efmCuPme10PProfileTable D 3
> > >>
> > >> There are a couple of issues with the table of predefined=20
> > >> efmCuPme10PProfileTable entries presented there.
> > >>
> > >> a)  The order of the columns does not exactly match the (OID)
> > >>     order of the columnar objects specified subsequently.
> > >>     This might raise some confusion.
> > >>
> > >>     I recommend to exchange the last two columns to achieve
> > >>     a matching order.  (Changing the columnar object sequence
> > >>     and the OIDs for efmCuPme10PPayloadURateProfile and
> > >>     efmCuPme10PPayloadDRateProfile will perhaps not be feasible!)
> > >=20
> > > I agree.
> > > Suggest to swap the order of the=20
> efmCuPme10PPayloadURateProfile and=20
> > > efmCuPme10PPayloadDRateProfile, since the IEEE standard defines=20
> > > Downstream rate before the Upstream.
> >=20
> > I do not know the state of initial implementation(s) and=20
> whether such=20
> > change would already negatively effect these; therefore I=20
> had proposed=20
> > the other way.
> > But if you do not see any obstacles, swapping the entries in the=20
> > efmCuPme10PProfileEntry syntax (SEQUENCE statement), the order of=20
> > description and the assigned OIDs, is clearly the better choice!
>=20
> Yes, initial draft implementations do exist and I had a=20
> similar concern a while ago on another change, but Bert=20
> assured me that the existence of such implementations is not=20
> a good excuse at all.
> =20
> > >> b)  In the first table row, the "(default)" is attached to the
> > >>     value in the last column without any intervening white space.
> > >>
> > >>     I strongly suspect that this tag conceptually is affixed to
> > >>     the entire row, not to the last columnar valu there.
> > >>     I that's right, to avoid confusion, I recommend to insert
> > >>     at least one space character before the "(default)"
> > >=20
> > > Agree, to further avoid confusion I suggest to add the word
> > 'profile'
> > > after the 'default', i.e.
> > >=20
> > >           1      1      3    2,6,10,11    20    20=20
> (default profile)
> >=20
> > Even better!  I fully agree.
> > (But please verify that the 72 colunm margin really does=20
> admit this!)
>=20
> I verified, it's ok.
>=20
> > >> (15)  efmCuNotificationGroup NOTIFICATION-GROUP
> > >>
> > >> The draft says:
> > >>
> > >>         NOTIFICATIONS {
> > >>           efmCuLowRateCrossing,
> > >>           efmCuPmeLineAtnCrossing,
> > >>           efmCuPmeSnrMgnCrossing,
> > >>           efmCuPmeDeviceFault,
> > >>           efmCuPmeConfigInitFailure,
> > >>           efmCuPmeProtocolInitFailure
> > >> |  --       efmCuPmeDeviceFault,
> > >> |  --       efmCuPmeLocalPowerLoss
> > >>         }
> > >>
> > >> ...
> > >=20
> > > Both comments should be removed.
> >=20
> > O.k.
> >=20
> > > efmCuPmeDeviceFault already appears in the conformance group.
> >=20
> > Oooops, now that you say that ...  I really have overlooked that!
> > =20
> > =20
> > Kind regards, again,
> >    Alfred.
> >=20
> > --
> >=20
> > +------------------------+------------------------------------
> > --------+
> > | TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math.,=20
> > Dipl.-Phys.  |
> > | Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18=20
> >         |
> > | D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de            =20
> >         |
> > +------------------------+------------------------------------
> > --------+
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun May 27 12:39:52 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HsLmW-0003h8-5g; Sun, 27 May 2007 12:39:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HsLmU-0003h3-Jc
	for hubmib@ietf.org; Sun, 27 May 2007 12:39:46 -0400
Received: from il-mail.actelis.net ([62.90.13.193])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HsLmT-0005tu-Ev
	for hubmib@ietf.org; Sun, 27 May 2007 12:39:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 27 May 2007 19:40:00 +0300
Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E01027818@il-mail.actelis.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-hubmib-efm-cu-mib-07 LC comments
Thread-Index: AcedcixqKzinB449SdaobFBnq7f6hQABCcBQAMBh4uA=
From: "Edward Beili" <EdwardB@actelis.com>
To: =?windows-1255?Q?Alfred_H=CEnes?= <ah@tr-sys.de>,
	<bwijnen@alcatel-lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3da7e5d5ca82d58872786934e4963616
Cc: dromasca@avaya.com, hubmib@ietf.org
Subject: [Hubmib] RE: draft-ietf-hubmib-efm-cu-mib-07 LC comments
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Alfred/Bret,

On the references to G.991.3, T1.424, and TS101 270-1 in EFM-CU-MIB, in =
efmCuPme10PBandplanPSDMskProfile, efmCuPme10PUPBOReferenceProfile and =
efmCuPme10PBandNotchProfiles:

1st of all I do agree that the standards in question should be written =
the same way in all places (already fixed that in the new version of the =
draft).

What I'm contemplating now is whether to list these standards in the =
REFERENCE clauses of the relevant objects. I don't think it is necessary =
and here is my reasoning:

The tables listing these standards in the DESCRIPTION clauses are the =
exact copies of the relevant IEEE 802.3ah tables. From the EFM-CU-MIB =
point of view, the only important part of these tables is the profile =
number, which is an index of a relevant entry in a relevant table. In =
other words when describing profile(1) the only important thing to say =
about it is that it is the index of the 1st entry in the relevant =
802.3ah table. The meaning of this entry (value of each columnar =
parameter) is described in the relevant 802.3ah section, already =
referenced in the REFERENCE clauses of the management objects. The =
10Pass-TS PHY/equipment manufacturers would implement these tables, and =
a management station would use the efmCuPme10P*Profile objects to =
activate these entries as a single profile.

Regards,
-E.

> -----Original Message-----
> From: Edward Beili=20
> Sent: Thursday, May 24, 2007 2:20
> To: 'Alfred H=CEnes'
> Cc: bwijnen@alcatel-lucent.com; dromasca@avaya.com
> Subject: RE: draft-ietf-hubmib-efm-cu-mib-07 LC comments
>=20
> Alfred,
> Thank you very much for your comments, I fully appreciate the=20
> time and effort you put into checking the draft. I agree with=20
> almost all of your comments. See my rebuttal inline below.
>=20
> Bert,
> How do you want me to proceed - should I issue a new version=20
> of the draft?
>=20
> Regards,
> -E.=20
>=20
> > -----Original Message-----
> > From: Alfred H=CEnes [mailto:ah@tr-sys.de]
> > Sent: Wednesday, May 23, 2007 22:39
> > To: Edward Beili
> > Cc: bwijnen@alcatel-lucent.com; dromasca@avaya.com
> > Subject: draft-ietf-hubmib-efm-cu-mib-07 LC comments
> >=20
> > Hello,
> > as recommended by Bert Wijnen yesterday, I've hurried up,=20
> and hereby I=20
> > submit my notes on the more-than-just-editorial issues I found in=20
> > draft-ietf-hubmib-efm-cu-mib-07, plus the issues in Section 7 & up.
> >=20
> > A subsequent message will address the remaining textual flaws in=20
> > Sections 1..6  I have observed.
> >=20
> > All but the last two items below deal with the MIB modules in the=20
> > draft.  For brevity, I use the following shorthand notation=20
> to locate=20
> > the affected part of the text there:
> >=20
> >       <object_name> D <n>
> >                    /    \
> >                   /      paragraph number; positive values count
> >     DESCRIPTION clause   top-down, negative values count=20
> from the end
> > or:
> >       <object_name> <X>
> >=20
> > where the following single capital letters <X> are used:
> >      S ... SYNTAX clause
> >      O ... OBJECTS clause
> >      R ... REFERENCES clause
> >=20
> > The items are listed in textual order.
> > Issues spanning more than one object (etc.) will be noted=20
> for either=20
> > place in the text via cross-references.
> >=20
> >=20
> > (A)  =3D=3D=3D=3D  IF-CAP-STACK-MIB  =3D=3D=3D=3D
> >=20
> >=20
> > (1)  ifCapStackTable D -2
> >=20
> > Please reconsider the trailing phrase,
> >=20
> >   "... for any existing value of x or y." .
> >            ^^^^^^^^^^^^^^^^^^
> >=20
> > This might be misleading, since in the preceding text, the=20
> scenario of=20
> > EFM-Cu interfaces is only referred to by "e.g.".
> >=20
> > The IF-CAP-STACK-MIB obviously has been specified separately with=20
> > other areas of applicability in mind, i.e., the=20
> ifCapStackTable (and=20
> > its inverse) might be applicable for other scenarios of stacked=20
> > interfaces too (although not specified yet).
> > Currently these tables should only be applied to EFMCu=20
> interfaces; in=20
> > all other cases where it would be conceptionally valid,=20
> > ifCapStackTable rows should not be instantiated unless and until=20
> > specified otherwise.
> >
> > Therefore, I recommend to replace the above phrase by:
> >=20
> >   "... for any ifIndex values x or y representing an EFMCu PME
> >    or PCS, respectively."
> >=20
> > (or similar).
>=20
> EFMCu interfaces with flexible cross-connect are just one=20
> example where IF-CAP-STACK-MIB can be used.
> In fact ifCapStackTable (and its inverse) can be implemented=20
> for _any_ stacked interface. Of course in some cases it would=20
> not add any value, for example for interfaces without=20
> flexible cross-connect, the ifCapStackTable would be=20
> semantically identical to the ifStackTable - meaning that the=20
> sublayers which MAY be connected, as indicated by if=20
> CapStackTable, ARE connected, as indicated by ifStackTable.
>=20
> The DESCRIPTION text clearly states that ifStackTable=20
> describes cross-connect capability of the devices with=20
> stacked interfaces. Apart from EFMCu there are G.Bond=20
> interfaces (their MIB modules are being drafted) which use=20
> this table, so specifying EFMCu here is incorrect. While=20
> there is no point in implementing this table for devices=20
> without cross-connect capability, it won't do any harm if implemented.
>=20
> Therefore, I suggest leaving this text as it is. =20
> =20
> > (B)  =3D=3D=3D=3D  EFM-CU-MIB  =3D=3D=3D=3D
> >=20
> >=20
> > (2)  efmCuLowRateCrossing O
> >=20
> > The ASN.1 comment,
> >=20
> >   -- ifIndex is not needed here since we are under specific PCS
> >                                      =20
> > ^^^^^^^^^^^^^^^^^^^^^^^^^ is unclear, and in fact not needed at all:
> > the ifIndex value occurs in the index part of all the OIDs of the=20
> > objects included in this NOTIFICATION, anyway!
> >=20
> > I recomment to remove that ASN.1 comment entirely, or else=20
> to replace=20
> > it by:
> >=20
> >   -- The ifIndex of the specific PCS is delivered in the index part
> >      of the OIDs of the following objects' instances.
> >=20
> > (or similar).
>=20
> You are right, I wrote this comment for myself, it should be removed.
>=20
> > (3)  efmCuNumPMEs S
> >=20
> > The semantics of that object apparently perfectly fit the=20
> > specification of the Gauge32 SYNTAX in SMIv2.
> >=20
> > Are there specific reasons to *not* specify a subrange of
> > Gauge32 for this object, but using Unsigned32 instead ?
>=20
> My understanding of Gauge32 is it should be used for=20
> "latched" objects, that is, whose information being modeled=20
> can be greater than the maximum or smaller than the minimum.
> Since the number of PMEs can never be negative or more than=20
> 32, I concluded that Gauge32 is inappropriate here. Please=20
> correct me if I'm wrong here.
>=20
> > (4)  efmCuPmeThreshSnrMgn D 2
> >=20
> > The draft says:
> >=20
> >           This object is writable for the CO subtype PMEs
> > |         (2BaseTL-O/10PassTS-R). It is read-only for the=20
> CPE subtype
> >           (2BaseTL-R/10PassTS-R).
> >=20
> > It should say:
> >=20
> >           This object is writable for the CO subtype PMEs
> > |         (2BaseTL-O/10PassTS-O). It is read-only for the=20
> CPE subtype
> >           (2BaseTL-R/10PassTS-R).
>=20
> You are right, it should be corrected.
>=20
> > (5)  efmCuPmeOperSubType D 2
> >=20
> > The draft says:
> >=20
> >           The operational sub type of the PME can be configured via
> >           efmCuPmeAdminSubType variable.
> >=20
> > This might be confusing.  It should perhaps better say:
> >=20
> >              vvvvvvvvv
> > |         The desired operational sub type of the PME can be
> > configured
> > |         via the efmCuPmeAdminSubType variable.
> >              ^^^^^
>=20
> Ok.
>=20
> > (6)  efmCuPme2BsModeRowStatus D 2
> >=20
> > The draft says:
> >=20
> >           If an 'active' entry is referenced via=20
> efmCuPme2BsMode, the
> >           entry MUST remain 'active' until all references=20
> are removed.
> >=20
> > This is illogical and confusing.
> > It should perhaps better (and even simpler) say:
> >=20
> >           If an 'active' entry is referenced via=20
> efmCuPme2BsMode, the
> >           entry MUST remain 'active'.
>=20
> I don't see a big difference between the two, but willing to=20
> go with your wording. I think though that it is important to=20
> remind the implementer that there can be multiple references=20
> to the same entry (from multiple PMEs). So I would suggest to say:
>=20
>           If an 'active' entry is referenced via efmCuPme2BsMode, the
>           entry MUST remain 'active'. Note that there can be multiple
> 	    references to the same entry.
>=20
> > (7)  efmCuPme10PProfileTable D 3
> >=20
> > There are a couple of issues with the table of predefined=20
> > efmCuPme10PProfileTable entries presented there.
> >=20
> > a)  The order of the columns does not exactly match the (OID)
> >     order of the columnar objects specified subsequently.
> >     This might raise some confusion.
> >=20
> >     I recommend to exchange the last two columns to achieve
> >     a matching order.  (Changing the columnar object sequence
> >     and the OIDs for efmCuPme10PPayloadURateProfile and
> >     efmCuPme10PPayloadDRateProfile will perhaps not be feasible!)
>=20
> I agree. Suggest to swap the order of the=20
> efmCuPme10PPayloadURateProfile and=20
> efmCuPme10PPayloadDRateProfile, since the IEEE standard=20
> defines Downstream rate before the Upstream.
>=20
> > b)  In the first table row, the "(default)" is attached to the
> >     value in the last column without any intervening white space.
> >=20
> >     I strongly suspect that this tag conceptually is affixed to
> >     the entire row, not to the last columnar valu there.
> >     I that's right, to avoid confusion, I recommend to insert
> >     at least one space character before the "(default)"
>=20
> Agree, to further avoid confusion I suggest to add the word=20
> 'profile' after the 'default', i.e.
>           1      1      3    2,6,10,11    20    20 (default profile)
>=20
> > c)  From the 4th row down to the last row, in the third column
> >     the value '0' (for UPBO p#) is specified.
> >=20
> >     But the efmCuPme10PUPBOReferenceProfile SYNTAX does not
> >     admit the enumerated value 0, it only allows (1..9).
> >=20
> >     What's wrong there ???
>=20
> Right, I added the value of profile(0) to=20
> efmCuPme10PUPBOReferenceProfile, with a description - no profile.
>=20
> > d)  The last row (profile index 22) in its second row gives a
> >     Bandplan PSDMask# value of '30'.
> >=20
> >     But the efmCuPme10PBandplanPSDMskProfile SYNTAX does not
> >     admit the enumerated value 30, it only allows (1..29).
> >=20
> >     What's wrong there ???
>=20
> Missed that one, I added the value 30 with description.
>=20
> > (7')  efmCuPme10PProfileTable D -3 and D -2
> >=20
> > Because of item (7) above, I include the following remarks=20
> on textual=20
> > flaws in the subsequent paragraphs as well:
> >                            vvvv
> > a) Change:  "... be created by during agent initialization ..."
> >=20
> >    to say:  "... be created during agent initialization ..."
>=20
> Agree.
>=20
> > b) Delete the two commas from D -2.
> >=20
> >=20
> > (8)  efmCuPme10PBandplanPSDMskProfile S
> >=20
> > See item (7) d)  above!
>=20
> Agree.
>=20
> > (9)  efmCuPme10PBandplanPSDMskProfile D 2  and  R
> >=20
> > a)
> > The profile table uses short references for the "PSD Mask":
> >    'T1.424/T-U P1', 'TS1 101 270-1', and 'G.993.1 F.1.2.*' .
> >=20
> > These should be detailed in the REFERENCE clause of the object.
>=20
> Agree.
>=20
> > b)
> > The ref. label "TS1 101 270-1" is used here, whereas in the=20
> > efmCuPme10PUPBOReferenceProfile D, "ETSI TS 101 270-1", and in the=20
> > efmCuPme10PBandNotchProfiles D, "TS101 270-1"
> > is used for what perhaps denotes the same document.
> >=20
> > Using a unified notation in all three tables would be appreciated!
>=20
> Agree.
>=20
> > (10)  efmCuPme10PUPBOReferenceProfile S
> >=20
> > See item (7) c)  above!
>=20
> Agree.
> =20
> > (11)  efmCuPme10PUPBOReferenceProfile D 2  and  R
> >=20
> > a)
> > As in item (9) a)  above:
> >=20
> > The profile table uses short references for the "PSD Mask":
> >    'T1.424/T-U', and 'ETSI TS 101 270-1' .
> >=20
> > These should be detailed in the REFERENCE clause of the object.
> >=20
> > b)
> > See item  (9) b)  above !
> >=20
> >=20
> > (12)  efmCuPme10PBandNotchProfiles D 2  and  R
> >=20
> > a)
> > The profile table uses short references for the table heading
> >    'G.991.3',  'T1.424/T-U', and 'TS101 270-1' .
> >=20
> > These should be detailed in the REFERENCE clause of the object.
> >=20
> > b)
> > See item  (9) b)  above !
> >=20
> >=20
> > (13)  efmCuPme10PBandNotchProfiles D -2
>=20
> Agree
>=20
> > The draft says:
> >=20
> >           Any combination of profiles can be specified by ORing
> >           individual profiles, for example value of 0x0622 selects
> >           profiles 2,6,10 and 11.
> >=20
> > The hex value given does not match the set of profiles listed.
> > [See RFC 3416, Section 2.5, paragraph #2 for the mapping of BITS.]
> >=20
> > 0x0622 corresponds to 5,6,10,14 !
> > (The 1st nibble is for BITS 0,1,2,3, the 2nd for BIT 4,5,6,7, ...)
> >=20
> > Assuming the set of profiles to be left unchanged, the hex=20
> value must=20
> > be corrected to 0x2230 .
> >=20
> > Hence, the draft should say:
> >=20
> >           Any combination of profiles can be specified by ORing
> >           individual profiles, for example value of 0x2230 selects
> >           profiles 2,6,10 and 11.
>=20
> You are right. Must be corrected.
>=20
> > (14)  efmCuPme10PStatusEntry D + other
> >=20
> > The draft is not clear about the instantiation rules for=20
> rows in the=20
> > efmCuPme10PStatusTable.
> >=20
> > From the D's of the columnar objects it can be concluded that such=20
> > rows only make sense for 10PASS-TS PMEs, and that therefore the=20
> > instantiation of efmCuPme10PStatusTable rows is not intended for=20
> > 2-BASE-TL PMEs, and cannot be assumed to be mandatory in that case.
> >=20
> > The efmCuCompliance MODULE-COMPLIANCE statement contains the lines:
> >=20
> >           GROUP       efmCuPme10PStatusGroup
> >           DESCRIPTION
> >             "Support for this group is OPTIONAL for implementations
> >             supporting 10PASS-TS Phy."
> >=20
> > Hence, even for 10PASS-TS PMEs, the instantiation of=20
> > efmCuPme10PStatusTable rows is *not* mandatory.
> >=20
> > Contrary to that, the efmCuPme10PStatusEntry OBJECT-TYPE=20
> declaration=20
> > contains the structural specification:
> >=20
> >         AUGMENTS { efmCuPmeStatusEntry }
> >=20
> > According to the SMIv2 (STD 58, RFC 2578, Section 7.8), this clause=20
> > means that the efmCuPme10PStatusTable is a *dense*=20
> augmentation of the=20
> > efmCuPmeStatusTable, i.e. that the instantiation of any row
> > (efmCuPmeStatusEntry) there immediately enforces the=20
> instantiation of=20
> > the corresponging efmCuPme10PStatusEntry.
> >=20
> > That makes no sense!
> >=20
> > IMHO, the above AUGMENTS clause has to be substituted by:
> >=20
> >         INDEX { ifIndex }
>=20
> Agree.
>=20
> > Also, the instantiation rules should be made explicit in the=20
> > efmCuPme10PStatusTable D or the efmCuPme10PStatusEntry D .
>=20
> Agree.
> =20
> > (15)  efmCuNotificationGroup NOTIFICATION-GROUP
> >=20
> > The draft says:
> >=20
> >         NOTIFICATIONS {
> >           efmCuLowRateCrossing,
> >           efmCuPmeLineAtnCrossing,
> >           efmCuPmeSnrMgnCrossing,
> >           efmCuPmeDeviceFault,
> >           efmCuPmeConfigInitFailure,
> >           efmCuPmeProtocolInitFailure
> > |  --       efmCuPmeDeviceFault,
> > |  --       efmCuPmeLocalPowerLoss
> >         }
> >=20
> > It remains unclear what has been intended with the two lines tagged=20
> > above, written as ASN.1 comments.
> >=20
> > a)
> > 'efmCuPmeDeviceFault' is well defined in the MIB module.
> >=20
> > I cannot see any immediate reason why it is getting=20
> excluded from the=20
> > conformance groups.
> >=20
> > Perhaps this line should be re-activated !
> >
> > b)
> > 'efmCuPmeLocalPowerLoss' does not appear anywhere else in the draft.
> >=20
> > Perhaps this line should be dropped !
> =20
> Both comments should be removed. efmCuPmeDeviceFault already=20
> appears in the confirmance group.
> =20
> > (16)  Section 7
> >=20
> > In the second paragraph below the bulleted list,
> > change   "evasdrop"  -->  "eavesdrop" .
>=20
> Right.
>=20
> > (17)  Sections 8, 10, and 11
> >=20
> > Hint:  To alleviate the job of the RFC-Editor and the IANA,
> >        - RFC 4836 and RFC 4837 should be substituted for the
> >          respective I-Ds;
> >        - the first paragraph of Section 8 apparently is void
> >          in the meantime (and hence should be deleted), by
> >          publication of RFC 4836 and IANA action for that RFC;
> >        - the text in Section 10 can be simplified;
> >        - one Normative and one Informative Ref. can be updated
> >          immediately from I-D to RFC.
>=20
> Agree.
>=20
> > I apologize for any errors introduced into this memo due to its=20
> > hastily preparation.
> >=20
> > If you like, please forward (parts of) this note to the=20
> hubmib  list=20
> > if you think the issues above should be discussed there.
> >=20
> > Kind regards,
> >   Alfred H=CEnes.
> >=20
> > --
> >=20
> > +------------------------+------------------------------------
> > --------+
> > | TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math.,=20
> > Dipl.-Phys.  |
> > | Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18=20
> >         |
> > | D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de            =20
> >         |
> > +------------------------+------------------------------------
> > --------+
> >=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Tue May 29 17:38:04 2007
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ht9OF-0002iy-Sf; Tue, 29 May 2007 17:38:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HsOwJ-0004CY-83
	for hubmib@ietf.org; Sun, 27 May 2007 16:02:07 -0400
Received: from dsl.tr-sys.de ([213.178.172.147] helo=WOTAN.TR-Sys.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HsOwH-00021e-DS
	for hubmib@ietf.org; Sun, 27 May 2007 16:02:07 -0400
Received: from ZEUS.TR-Sys.de by w. with ESMTP
	($Revision: 1.37.109.26 $/16.3) id AA138086115;
	Sun, 27 May 2007 22:01:55 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id
	WAA29612; Sun, 27 May 2007 22:01:53 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@tr-sys.de>
Message-Id: <200705272001.WAA29612@TR-Sys.de>
To: EdwardB@actelis.com
Date: Sun, 27 May 2007 22:01:53 +0200 (MESZ)
In-Reply-To: <9C1CAB2B65E62D49A10E49DFCD68EF3E01027818@il-mail.actelis.net>
	from Edward Beili at May "27, " 2007 "07:40:00" pm
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
X-Mailman-Approved-At: Tue, 29 May 2007 17:38:03 -0400
Cc: dromasca@avaya.com, hubmib@ietf.org, bwijnen@alcatel-lucent.com
Subject: [Hubmib] Re: draft-ietf-hubmib-efm-cu-mib-07 LC comments
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org

Edward,
thanks for your note:
> 
> On the references to G.991.3, T1.424, and TS101 270-1 in EFM-CU-MIB,
> in efmCuPme10PBandplanPSDMskProfile, efmCuPme10PUPBOReferenceProfile
> and efmCuPme10PBandNotchProfiles:
> 
> 1st of all I do agree that the standards in question should be
> written the same way in all places (already fixed that in the new
> version of the draft).
> 
> What I'm contemplating now is whether to list these standards in
> the REFERENCE clauses of the relevant objects. I don't think it is
> necessary and here is my reasoning:
> 
> The tables listing these standards in the DESCRIPTION clauses are the
> exact copies of the relevant IEEE 802.3ah tables. From the EFM-CU-MIB
> point of view, the only important part of these tables is the profile
> number, which is an index of a relevant entry in a relevant table.
> In other words when describing profile(1) the only important thing to
> say about it is that it is the index of the 1st entry in the relevant
> 802.3ah table. The meaning of this entry (value of each columnar
> parameter) is described in the relevant 802.3ah section, already
> referenced in the REFERENCE clauses of the management objects. The
> 10Pass-TS PHY/equipment manufacturers would implement these tables,
> and a management station would use the efmCuPme10P*Profile objects
> to activate these entries as a single profile.

Well; that's an argument.

On the other hand, due to the columnar space restrictions enforcing
abbreviated references, it might anyway be a service for the reader
and the user of a management station to somewhere give the full
references.

If you dislike expanding the REFERENCE clauses of these objects,
an alternative might be to update the DESCRIPTION clause of the
efmCuMIB MODULE-IDENTITY, where [802.3ah] is expanded.
One possibility I envision would be to amend the IEEE 802.3ah
expansion there, without introducing new [...] style reference
tags, by a note like this:

      This document makes normative references to
      -  G.991.3,
      -  T1.424, and
      -  TS101 270-1,
      indirectly quoted as well by DESCRIPTION causes in this
      MIB module.  The full references for these standards are:

      ...
      ...
      ...

Kind regards,
  Alfred.


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



