From mailman-bounces@ietf.org  Sat Jan  1 06:01:40 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09186
	for <hubmib-archive@lists.ietf.org>; Sat, 1 Jan 2005 06:01:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkgFp-0007h5-H8
	for hubmib-archive@lists.ietf.org; Sat, 01 Jan 2005 05:13:01 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: hubmib-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.9353.1104573809.4100.mailman@lists.ietf.org>
Date: Sat, 01 Jan 2005 05:03:29 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for hubmib-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
hubmib@ietf.org                          XUKx      
https://www1.ietf.org/mailman/options/hubmib/hubmib-archive%40lists.ietf.org


From hubmib-bounces@ietf.org  Sat Jan  1 15:40:06 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20617
	for <hubmib-archive@lists.ietf.org>; Sat, 1 Jan 2005 15:40:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ckq1Z-0003VJ-2p; Sat, 01 Jan 2005 15:38:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ckpwa-0008JS-Oz
	for hubmib@megatron.ietf.org; Sat, 01 Jan 2005 15:33:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20429
	for <hubmib@ietf.org>; Sat, 1 Jan 2005 15:33:46 -0500 (EST)
Received: from mail14b.g14.rapidsite.net ([128.121.64.164])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Ckq8N-0007mr-EV
	for hubmib@ietf.org; Sat, 01 Jan 2005 15:46:00 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14b.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	4-0877051609; Sat,  1 Jan 2005 15:33:31 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Sat, 1 Jan 2005 22:32:51 +0200
Message-ID: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F06E3071E@is0004avexu1.global.avaya.com>
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 83867a50fd8f547996ccdaf89af24437
Content-Transfer-Encoding: 7bit
Cc: "'Glen Kramer'" <glen.kramer@teknovus.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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Glen,
Thank you very much for the comments and for the time you invested in
reviewing the document. I appreciate it very much.


1. Thanks

2. I believe it is useful to have also a configuration possibility for
this parameter. As a guideline I believe management should have access
to define main modes of the system. Can you please specify why do you
think writing such a parameter is not useful? If we want to be strictly
following clause 30 I can add change the attribute in the device MIBs
objects to read-write but I would rather have it following the
configuration from the EFM MIB objects. 

3. Agreed

4. My believe is that the management entity as a general requires the
knowledge of the PON switching time and does not need to find parameters
in the spec to complete the picture as it is may be probably part of a
more general access system. I think the MIB objects should supply a
visibility of the system major parameters although some are fixed. I can
add the description of 32TQs value to align with the MPCP. 
 
5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode frames
which are not of PAUSE or used by the MPCP protocol. I will clear the
description.

6. Agreed

7+8. If we can see the forwarding rules of the ONU in clause 65 then 
7+there is a behavior for frames with bit broadcast in the LLID where 
7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is 
7+not the ONU's LLID (frame is accepted) as part of the point to point 
7+emulation peer to peer capabilities. This counter counts the first 
7+frame. I have sent in the past comments regarding that to clause 30. 
7+The result was  OnuPonCastLLID and OltPonCastLLID which I think their 
7+definition is too vague and refers to a long list of forwarding rules.

7+A solution for alignment is to make a request to change in the 
7+definition of these attributes in the spec and then unify these 
7+counters in them.

9. As a general logical deductive comment you have here a very good
comment. The problem comes when in devices a reset process can be a very
long process where many different sub-systems are reset. In such a
scenario there is a meaning for being in a reset process. Therefore I
believe that this is an attribute which is needed for a device. I am
open here for suggestions.

10. Thanks.

11. Changing this variable might indeed cause very major changes in the
system. Yet in my opinion it is needed for management. Unfortunately in
true life engineered systems there is a possibility that a system is not
operating well and it is needed to make it inactive immediately. The
purpose of such an attribute is like this. 

12. I guess the question is what is the meaning of power down. I thought
of a condition where the device is in minimal power mode where it is not
transmitting and it is in listening mode so it can be enabled by
activation according to MAC address. Keeping it registered can be done
easily by reducing its SLA to minimal BW but I don't think it  is a
power down mode. Keeping it in listening mode will really make it
possible for the system to reduce power (notice I do not define what is
exactly this mode as it can be implemented as the vendor wishes) yet
have the minimal capability to wake up.  

13. O.K. Would you consider such an object definition instead: I think
it covers multiple thresholds. eponDeviceObjectReportNumThreshold
OBJECT-TYPE
    SYNTAX  Integer32
    MAX-ACCESS  read-write
    STATUS  current
    DESCRIPTION
            "A set of 8 integers, for each LLID, that defines the
             number of thresholds for each Queue in the REPORT
             message, as defined in [802.3ah] 64. Each Queue set
             reporting will provide information on the queue 
             occupancy of frames below the matching Threshold. 
             Writing can be done all the time.
             This attribute is relevant for an OLT and an ONU."
    DEFVAL { 0 }
    ::= { eponDeviceControlEntry 7 }

    eponDeviceObjectReportThreshold OBJECT-TYPE
    SYNTAX  Integer32
    UNITS       "TQ (16nsec)"
    MAX-ACCESS  read-write
    STATUS  current
    DESCRIPTION
            "A multiple set of 8 integers, for each LLID, that 
             defines the thresholds reporting for each Queue in the 
             REPORT message, as defined in [802.3ah] 64. The number 
             of sets is eponDeviceObjectReportNumThreshold. Each 
             Queue set reporting will provide information on the  
             queue occupancy of frames below the matching Threshold.
             The value returned shall be in Time quanta (TQ) which 
             is 16nsec or 2 octets increments.
             Writing can be done all the time.
             This attribute is relevant for an OLT and an ONU."
    DEFVAL { 0 }
    ::= { eponDeviceControlEntry 8 }

14. The OLT and ONUs of an EPON device serves as a distributed virtual
switch where the LLIDs represent bridge ports. This model is behind the
point to point emulation mechanism of clause 65 and of the whole LLID
concept. A bridge have a MAC address to port address table and this
table here serves for exactly the same purpose. It is not a proprietary
implementation. The eponDeviceRemoteMACAddressLLIDControl is a control
attribute for resetting this Table. As a table is a manageable entity I
think such an object is needed. The useDefaultReporting(3) category is a
common option for such attributes as a default setting for tables -
Implementation is according to Vendors preference. I have no special
suggestion for the default value. If people will feel more comfortable I
can remove useDefaultReporting(3) and return in the reading none(1).

15. The report message in the MPCP refers to such entities. Please see
section 64.3.6.2 for report message format. These counters refer to
that.

16. As a general concept we tried to create in the EFM MIB objects a
reflection of the IEEE802.3ah management object keeping as much as we
can aligned to clause 30. There is here an additional section which
refers to device MIB objects. In there I tried to put all things which
are necessary for the management of an EPON device (in an access
network) and was not truly covered by the IEEE802.3ah spec as being a
spec for L2 MAC mainly. So although they are OAM they are in device
level.


Best regards,
Lior



-----Original Message-----
From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
Of Romascanu, Dan (Dan)
Sent: Sunday, December 19, 2004 4:22 PM
To: hubmib@ietf.org
Cc: Glen Kramer
Subject: [Hubmib] FW: EPON MIB comments


Although these comments from one of the 802.3ae contributors came in
after the WG Last Call deadline, I suggest that we enter them as Last
Call comments and address them accordingly. 

Regards,

Dan



-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com]
Sent: 16 December, 2004 9:49 PM
To: Romascanu, Dan (Dan)
Subject: EPON MIB comments


Dan,

I finally read the EPON MIB document. Below are my comments. I am not
sure if it is too late to make use of these, or not. Plsease, feel free
to post these on the reflector.

Regards,
Glen

 
1. In tables in section 7, object names that are split across lines lost
a letter.

2. dot3MpcpMode object should be read-only as is its counterpart in
802.3ah (aMPCPMode attribute).

3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly
to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The ONUs
are not aware of the round-trip times to the OLT.

4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the
description that these objects refer to laser_on and laser_off times.
Also, according to the 802.3ah, these times are constant and fixed at 32
TQ. These objects are not necessary.  Correspondingly, 802.3ah did not
find it necessary to specify such attributes in clause 30.
 
5. dot3MpcpRxNotSupportedMpcp.  The description of this object does not
make sense. If a frame is not supported, it is not an MPCP frame.
Conversely, there exist no unsupported MPCP frames. There is no matching
attribute in clause 30 in 802.3ah and this object should be removed from
this draft as well.

6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but
optional at the ONU. It is not optional per 802.3ah and is relevant for
both devices. (For comparison, the dot3OmpEmulationCRC8Errors is
mandatory in the OLT and ONUs).

7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the
phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. Should
it simply say "broadcast or unicast LLID"?  Also, there is no relevant
attribute in clause 30 in 802.3ah.

8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,
as the dot3OmpEmulationBadLLID will count the same frames. I recommend
removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.

9. The access to eponDeviceObjectReset object should be write-only. If
device is being reset, it cannot generate "reset" response. When the
device can generate the response, it will be running already. Thus, the
only possible response is "running".

10. The object eponDeviceObjectOamMode is not necessary. To get the OAM
mode, the management agent would access OAM MIB. No need to duplicate
objects in different MIBs.

11. eponDeviceObjectDeviceReadyMode object should be read-only.
Modifying device mode through the management may have unpredictable
results (like taking down entire EPON).

12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will
cause Device to be entered into Power down mode where no registration is
allowed and only receiving data from the link.". This object does not
make sense. Setting it to True will cause the device lose the link
(because no transmission is allowed leading to MPCP timeout) and never
register again (because registration is not allowed).

13. eponDeviceObjectReportThreshold. The 802.3ah standard does not limit
number of thresholds to be used.  This object will only return the first
threshold for each queue. What about the rest of thresholds? How to
read/set them?

14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls the
resetting of the LLID MAC address log. Setting this object to none(1)
has no action resetLog(2) empties the LLID MAC address log. All data is
deleted. Setting it to useDefaultReporting(3) returns all entries
priorities to their factory-default reporting. Reading this object
always returns useDefaultReporting(3)." The description of this object
seems to match some proprietary EPON device. In the 802.3ah standard,
there is no provision of whether to keep LLID MAC address log. It is not
clear, what does it mean "returns all entries priorities to their
factory-default reporting", since there is no specification for either
"entries" or "factory-default reporting". This object should be removed.

15. Objects eponDeviceStatTxFramesQueue[0-7],
eponDeviceStatRxFramesQueue[0-7], and
eponDeviceStatDroppedFramesQueue[0-7]
are not specific to EPON. These objects exist for other devices, such as
bridge ports. There is no need to duplicate these objects here. Besides,
neither 802.3ah nor 802.1D standards require exactly 8 queues to be
implemented. I recommend removing these objects.

16. The following objects represent non-EPON-specific events and should
be
moved to OAM MIB.   
   eponDeviceSampleMinimum 
   eponDeviceDyingGaspAlarmState
   eponDeviceDyingGaspAlarmEnabled
   eponDeviceCriticalEventState
   eponDeviceCriticalEventEnabled
   eponDeviceLocalLinkFaultAlarmState
   eponDeviceLocalLinkFaultAlarmEnabled
   eponDeviceTemperatureEventIndicationState
   eponDeviceTemperatureEventIndicationEnabled
   eponDevicePowerVoltageEventIndicationState
   eponDevicePowerVoltageEventIndicationEnabled
   eponDeviceGlobalEventState
   eponDeviceGlobalEventEnabled
   eponDeviceErroredSymbolPeriodEventState
   eponDeviceErroredSymbolPeriodEventEnabled
   eponDeviceErroredFrameEventState
   eponDeviceErroredFrameEventEnabled
   eponDeviceErroredFramePeriodEventState
   eponDeviceErroredFramePeriodEventEnabled
   eponDeviceErroredFrameSecondsSummaryEventState
   eponDeviceErroredFrameSecondsSummaryEventEnabled
   eponDeviceOrganizationSpecificEventState
   eponDeviceOrganizationSpecificEventEnabled
   eponDeviceEventControl




_______________________________________________
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 Jan  4 14:13:14 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09231
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 14:13:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clu3h-00016p-BY; Tue, 04 Jan 2005 14:09:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cltz5-0006zm-AR
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 14:04:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08596
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 14:04:45 -0500 (EST)
Message-Id: <200501041904.OAA08596@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CluBH-0004cn-5O
	for hubmib@ietf.org; Tue, 04 Jan 2005 14:17:37 -0500
Received: (qmail 6671 invoked by alias); 4 Jan 2005 19:04:28 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 4 Jan 2005 19:04:28 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpMode)
Date: Tue, 4 Jan 2005 11:04:21 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCS8A6Q
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bc102ac530ba955ef81f1f75b8bebe44
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Lior,

I am going to break this large e-mail into separate threads, so it is easier
to follow the discussion per comment. This one is about dot3MpcpMode.


[GK] dot3MpcpMode object should be read-only as is its counterpart in
802.3ah (aMPCPMode attribute).

[LK] I believe it is useful to have also a configuration possibility for
this parameter. As a guideline I believe management should have access to
define main modes of the system. Can you please specify why do you think
writing such a parameter is not useful? If we want to be strictly following
clause 30 I can add change the attribute in the device MIBs objects to
read-write but I would rather have it following the configuration from the
EFM MIB objects.

[GK] dot3MpcpMode specifies whether the device is an OLT or an ONU. *ALL*
MPCP state machines defined by IEEE 802.3ah are specified either for the OLT
or ONUs. There are no common state machines. It is not possible to change a
configuration parameter and force the OLT to behave as the ONU or the ONU to
behave as the OLT. If in a network, the management somehow forces the mode
change for an EPON device, this will result in EPON malfunction.
In addition, physical layer parameters are different for these devices: OLT
has burst-mode receiver and normal transmitter and ONUs have normal receiver
and burst-mode transmitter. 


Regards,
Glen



> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Lior khermosh
> Sent: Saturday, January 01, 2005 12:33 PM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Cc: 'Glen Kramer'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> Thank you very much for the comments and for the time you invested in
> reviewing the document. I appreciate it very much.
> 
> 
> 1. Thanks
> 
> 2. I believe it is useful to have also a configuration possibility for
> this parameter. As a guideline I believe management should have access
> to define main modes of the system. Can you please specify why do you
> think writing such a parameter is not useful? If we want to be strictly
> following clause 30 I can add change the attribute in the device MIBs
> objects to read-write but I would rather have it following the
> configuration from the EFM MIB objects.
> 
> 3. Agreed
> 
> 4. My believe is that the management entity as a general requires the
> knowledge of the PON switching time and does not need to find parameters
> in the spec to complete the picture as it is may be probably part of a
> more general access system. I think the MIB objects should supply a
> visibility of the system major parameters although some are fixed. I can
> add the description of 32TQs value to align with the MPCP.
> 
> 5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode frames
> which are not of PAUSE or used by the MPCP protocol. I will clear the
> description.
> 
> 6. Agreed
> 
> 7+8. If we can see the forwarding rules of the ONU in clause 65 then
> 7+there is a behavior for frames with bit broadcast in the LLID where
> 7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is
> 7+not the ONU's LLID (frame is accepted) as part of the point to point
> 7+emulation peer to peer capabilities. This counter counts the first
> 7+frame. I have sent in the past comments regarding that to clause 30.
> 7+The result was  OnuPonCastLLID and OltPonCastLLID which I think their
> 7+definition is too vague and refers to a long list of forwarding rules.
> 
> 7+A solution for alignment is to make a request to change in the
> 7+definition of these attributes in the spec and then unify these
> 7+counters in them.
> 
> 9. As a general logical deductive comment you have here a very good
> comment. The problem comes when in devices a reset process can be a very
> long process where many different sub-systems are reset. In such a
> scenario there is a meaning for being in a reset process. Therefore I
> believe that this is an attribute which is needed for a device. I am
> open here for suggestions.
> 
> 10. Thanks.
> 
> 11. Changing this variable might indeed cause very major changes in the
> system. Yet in my opinion it is needed for management. Unfortunately in
> true life engineered systems there is a possibility that a system is not
> operating well and it is needed to make it inactive immediately. The
> purpose of such an attribute is like this.
> 
> 12. I guess the question is what is the meaning of power down. I thought
> of a condition where the device is in minimal power mode where it is not
> transmitting and it is in listening mode so it can be enabled by
> activation according to MAC address. Keeping it registered can be done
> easily by reducing its SLA to minimal BW but I don't think it  is a
> power down mode. Keeping it in listening mode will really make it
> possible for the system to reduce power (notice I do not define what is
> exactly this mode as it can be implemented as the vendor wishes) yet
> have the minimal capability to wake up.
> 
> 13. O.K. Would you consider such an object definition instead: I think
> it covers multiple thresholds. eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }
> 
> 14. The OLT and ONUs of an EPON device serves as a distributed virtual
> switch where the LLIDs represent bridge ports. This model is behind the
> point to point emulation mechanism of clause 65 and of the whole LLID
> concept. A bridge have a MAC address to port address table and this
> table here serves for exactly the same purpose. It is not a proprietary
> implementation. The eponDeviceRemoteMACAddressLLIDControl is a control
> attribute for resetting this Table. As a table is a manageable entity I
> think such an object is needed. The useDefaultReporting(3) category is a
> common option for such attributes as a default setting for tables -
> Implementation is according to Vendors preference. I have no special
> suggestion for the default value. If people will feel more comfortable I
> can remove useDefaultReporting(3) and return in the reading none(1).
> 
> 15. The report message in the MPCP refers to such entities. Please see
> section 64.3.6.2 for report message format. These counters refer to
> that.
> 
> 16. As a general concept we tried to create in the EFM MIB objects a
> reflection of the IEEE802.3ah management object keeping as much as we
> can aligned to clause 30. There is here an additional section which
> refers to device MIB objects. In there I tried to put all things which
> are necessary for the management of an EPON device (in an access
> network) and was not truly covered by the IEEE802.3ah spec as being a
> spec for L2 MAC mainly. So although they are OAM they are in device
> level.
> 
> 
> Best regards,
> Lior
> 
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Romascanu, Dan (Dan)
> Sent: Sunday, December 19, 2004 4:22 PM
> To: hubmib@ietf.org
> Cc: Glen Kramer
> Subject: [Hubmib] FW: EPON MIB comments
> 
> 
> Although these comments from one of the 802.3ae contributors came in
> after the WG Last Call deadline, I suggest that we enter them as Last
> Call comments and address them accordingly.
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 16 December, 2004 9:49 PM
> To: Romascanu, Dan (Dan)
> Subject: EPON MIB comments
> 
> 
> Dan,
> 
> I finally read the EPON MIB document. Below are my comments. I am not
> sure if it is too late to make use of these, or not. Plsease, feel free
> to post these on the reflector.
> 
> Regards,
> Glen
> 
> 
> 1. In tables in section 7, object names that are split across lines lost
> a letter.
> 
> 2. dot3MpcpMode object should be read-only as is its counterpart in
> 802.3ah (aMPCPMode attribute).
> 
> 3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly
> to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The ONUs
> are not aware of the round-trip times to the OLT.
> 
> 4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the
> description that these objects refer to laser_on and laser_off times.
> Also, according to the 802.3ah, these times are constant and fixed at 32
> TQ. These objects are not necessary.  Correspondingly, 802.3ah did not
> find it necessary to specify such attributes in clause 30.
> 
> 5. dot3MpcpRxNotSupportedMpcp.  The description of this object does not
> make sense. If a frame is not supported, it is not an MPCP frame.
> Conversely, there exist no unsupported MPCP frames. There is no matching
> attribute in clause 30 in 802.3ah and this object should be removed from
> this draft as well.
> 
> 6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but
> optional at the ONU. It is not optional per 802.3ah and is relevant for
> both devices. (For comparison, the dot3OmpEmulationCRC8Errors is
> mandatory in the OLT and ONUs).
> 
> 7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the
> phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. Should
> it simply say "broadcast or unicast LLID"?  Also, there is no relevant
> attribute in clause 30 in 802.3ah.
> 
> 8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,
> as the dot3OmpEmulationBadLLID will count the same frames. I recommend
> removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.
> 
> 9. The access to eponDeviceObjectReset object should be write-only. If
> device is being reset, it cannot generate "reset" response. When the
> device can generate the response, it will be running already. Thus, the
> only possible response is "running".
> 
> 10. The object eponDeviceObjectOamMode is not necessary. To get the OAM
> mode, the management agent would access OAM MIB. No need to duplicate
> objects in different MIBs.
> 
> 11. eponDeviceObjectDeviceReadyMode object should be read-only.
> Modifying device mode through the management may have unpredictable
> results (like taking down entire EPON).
> 
> 12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will
> cause Device to be entered into Power down mode where no registration is
> allowed and only receiving data from the link.". This object does not
> make sense. Setting it to True will cause the device lose the link
> (because no transmission is allowed leading to MPCP timeout) and never
> register again (because registration is not allowed).
> 
> 13. eponDeviceObjectReportThreshold. The 802.3ah standard does not limit
> number of thresholds to be used.  This object will only return the first
> threshold for each queue. What about the rest of thresholds? How to
> read/set them?
> 
> 14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls the
> resetting of the LLID MAC address log. Setting this object to none(1)
> has no action resetLog(2) empties the LLID MAC address log. All data is
> deleted. Setting it to useDefaultReporting(3) returns all entries
> priorities to their factory-default reporting. Reading this object
> always returns useDefaultReporting(3)." The description of this object
> seems to match some proprietary EPON device. In the 802.3ah standard,
> there is no provision of whether to keep LLID MAC address log. It is not
> clear, what does it mean "returns all entries priorities to their
> factory-default reporting", since there is no specification for either
> "entries" or "factory-default reporting". This object should be removed.
> 
> 15. Objects eponDeviceStatTxFramesQueue[0-7],
> eponDeviceStatRxFramesQueue[0-7], and
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such as
> bridge ports. There is no need to duplicate these objects here. Besides,
> neither 802.3ah nor 802.1D standards require exactly 8 queues to be
> implemented. I recommend removing these objects.
> 
> 16. The following objects represent non-EPON-specific events and should
> be
> moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl
> 
> 
> 
> 
> _______________________________________________
> 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



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


From hubmib-bounces@ietf.org  Tue Jan  4 14:35:02 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10738
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 14:35:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CluKR-00080i-1C; Tue, 04 Jan 2005 14:26:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CluHI-0006tw-Vz
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 14:23:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09998
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 14:23:33 -0500 (EST)
Message-Id: <200501041923.OAA09998@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CluTf-0004zh-KV
	for hubmib@ietf.org; Tue, 04 Jan 2005 14:36:25 -0500
Received: (qmail 24778 invoked by alias); 4 Jan 2005 19:23:28 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 4 Jan 2005 19:23:28 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpOnTime and
	dot3MpcpOffTime)
Date: Tue, 4 Jan 2005 11:23:20 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCTimUg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1c0c3d540ad9f95212b1c2a9a2cc2595
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[GK] dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the
description that these objects refer to laser_on and laser_off times. Also,
according to the 802.3ah, these times are constant and fixed at 32 TQ. These
objects are not necessary.  Correspondingly, 802.3ah did not find it
necessary to specify such attributes in clause 30.

[LK] My believe is that the management entity as a general requires the
knowledge of the PON switching time and does not need to find parameters in
the spec to complete the picture as it is may be probably part of a more
general access system. I think the MIB objects should supply a visibility of
the system major parameters although some are fixed. I can add the
description of 32TQs value to align with the MPCP.

[GK] There is a large number of constants specified in MPCP spec. Laser-on
and laser-off constants are not more important that other parameters. Why
would you choose to define MIB objects for some constants and not other? 
If the management entity does not know what "PON switching time" is, it
cannot query dot3MpcpOnTime and dot3MpcpOffTime objects. If the management
is EPON-specific enough to understand that there exists "PON switching
time", it already knows that this is a constant equal 32 TQ. 

Regards,
Glen


> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Lior khermosh
> Sent: Saturday, January 01, 2005 12:33 PM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Cc: 'Glen Kramer'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> Thank you very much for the comments and for the time you invested in
> reviewing the document. I appreciate it very much.
> 
> 
> 1. Thanks
> 
> 2. I believe it is useful to have also a configuration possibility for
> this parameter. As a guideline I believe management should have access
> to define main modes of the system. Can you please specify why do you
> think writing such a parameter is not useful? If we want to be strictly
> following clause 30 I can add change the attribute in the device MIBs
> objects to read-write but I would rather have it following the
> configuration from the EFM MIB objects.
> 
> 3. Agreed
> 
> 4. My believe is that the management entity as a general requires the
> knowledge of the PON switching time and does not need to find parameters
> in the spec to complete the picture as it is may be probably part of a
> more general access system. I think the MIB objects should supply a
> visibility of the system major parameters although some are fixed. I can
> add the description of 32TQs value to align with the MPCP.
> 
> 5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode frames
> which are not of PAUSE or used by the MPCP protocol. I will clear the
> description.
> 
> 6. Agreed
> 
> 7+8. If we can see the forwarding rules of the ONU in clause 65 then
> 7+there is a behavior for frames with bit broadcast in the LLID where
> 7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is
> 7+not the ONU's LLID (frame is accepted) as part of the point to point
> 7+emulation peer to peer capabilities. This counter counts the first
> 7+frame. I have sent in the past comments regarding that to clause 30.
> 7+The result was  OnuPonCastLLID and OltPonCastLLID which I think their
> 7+definition is too vague and refers to a long list of forwarding rules.
> 
> 7+A solution for alignment is to make a request to change in the
> 7+definition of these attributes in the spec and then unify these
> 7+counters in them.
> 
> 9. As a general logical deductive comment you have here a very good
> comment. The problem comes when in devices a reset process can be a very
> long process where many different sub-systems are reset. In such a
> scenario there is a meaning for being in a reset process. Therefore I
> believe that this is an attribute which is needed for a device. I am
> open here for suggestions.
> 
> 10. Thanks.
> 
> 11. Changing this variable might indeed cause very major changes in the
> system. Yet in my opinion it is needed for management. Unfortunately in
> true life engineered systems there is a possibility that a system is not
> operating well and it is needed to make it inactive immediately. The
> purpose of such an attribute is like this.
> 
> 12. I guess the question is what is the meaning of power down. I thought
> of a condition where the device is in minimal power mode where it is not
> transmitting and it is in listening mode so it can be enabled by
> activation according to MAC address. Keeping it registered can be done
> easily by reducing its SLA to minimal BW but I don't think it  is a
> power down mode. Keeping it in listening mode will really make it
> possible for the system to reduce power (notice I do not define what is
> exactly this mode as it can be implemented as the vendor wishes) yet
> have the minimal capability to wake up.
> 
> 13. O.K. Would you consider such an object definition instead: I think
> it covers multiple thresholds. eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }
> 
> 14. The OLT and ONUs of an EPON device serves as a distributed virtual
> switch where the LLIDs represent bridge ports. This model is behind the
> point to point emulation mechanism of clause 65 and of the whole LLID
> concept. A bridge have a MAC address to port address table and this
> table here serves for exactly the same purpose. It is not a proprietary
> implementation. The eponDeviceRemoteMACAddressLLIDControl is a control
> attribute for resetting this Table. As a table is a manageable entity I
> think such an object is needed. The useDefaultReporting(3) category is a
> common option for such attributes as a default setting for tables -
> Implementation is according to Vendors preference. I have no special
> suggestion for the default value. If people will feel more comfortable I
> can remove useDefaultReporting(3) and return in the reading none(1).
> 
> 15. The report message in the MPCP refers to such entities. Please see
> section 64.3.6.2 for report message format. These counters refer to
> that.
> 
> 16. As a general concept we tried to create in the EFM MIB objects a
> reflection of the IEEE802.3ah management object keeping as much as we
> can aligned to clause 30. There is here an additional section which
> refers to device MIB objects. In there I tried to put all things which
> are necessary for the management of an EPON device (in an access
> network) and was not truly covered by the IEEE802.3ah spec as being a
> spec for L2 MAC mainly. So although they are OAM they are in device
> level.
> 
> 
> Best regards,
> Lior
> 
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Romascanu, Dan (Dan)
> Sent: Sunday, December 19, 2004 4:22 PM
> To: hubmib@ietf.org
> Cc: Glen Kramer
> Subject: [Hubmib] FW: EPON MIB comments
> 
> 
> Although these comments from one of the 802.3ae contributors came in
> after the WG Last Call deadline, I suggest that we enter them as Last
> Call comments and address them accordingly.
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 16 December, 2004 9:49 PM
> To: Romascanu, Dan (Dan)
> Subject: EPON MIB comments
> 
> 
> Dan,
> 
> I finally read the EPON MIB document. Below are my comments. I am not
> sure if it is too late to make use of these, or not. Plsease, feel free
> to post these on the reflector.
> 
> Regards,
> Glen
> 
> 
> 1. In tables in section 7, object names that are split across lines lost
> a letter.
> 
> 2. dot3MpcpMode object should be read-only as is its counterpart in
> 802.3ah (aMPCPMode attribute).
> 
> 3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly
> to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The ONUs
> are not aware of the round-trip times to the OLT.
> 
> 4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the
> description that these objects refer to laser_on and laser_off times.
> Also, according to the 802.3ah, these times are constant and fixed at 32
> TQ. These objects are not necessary.  Correspondingly, 802.3ah did not
> find it necessary to specify such attributes in clause 30.
> 
> 5. dot3MpcpRxNotSupportedMpcp.  The description of this object does not
> make sense. If a frame is not supported, it is not an MPCP frame.
> Conversely, there exist no unsupported MPCP frames. There is no matching
> attribute in clause 30 in 802.3ah and this object should be removed from
> this draft as well.
> 
> 6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but
> optional at the ONU. It is not optional per 802.3ah and is relevant for
> both devices. (For comparison, the dot3OmpEmulationCRC8Errors is
> mandatory in the OLT and ONUs).
> 
> 7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the
> phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. Should
> it simply say "broadcast or unicast LLID"?  Also, there is no relevant
> attribute in clause 30 in 802.3ah.
> 
> 8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,
> as the dot3OmpEmulationBadLLID will count the same frames. I recommend
> removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.
> 
> 9. The access to eponDeviceObjectReset object should be write-only. If
> device is being reset, it cannot generate "reset" response. When the
> device can generate the response, it will be running already. Thus, the
> only possible response is "running".
> 
> 10. The object eponDeviceObjectOamMode is not necessary. To get the OAM
> mode, the management agent would access OAM MIB. No need to duplicate
> objects in different MIBs.
> 
> 11. eponDeviceObjectDeviceReadyMode object should be read-only.
> Modifying device mode through the management may have unpredictable
> results (like taking down entire EPON).
> 
> 12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will
> cause Device to be entered into Power down mode where no registration is
> allowed and only receiving data from the link.". This object does not
> make sense. Setting it to True will cause the device lose the link
> (because no transmission is allowed leading to MPCP timeout) and never
> register again (because registration is not allowed).
> 
> 13. eponDeviceObjectReportThreshold. The 802.3ah standard does not limit
> number of thresholds to be used.  This object will only return the first
> threshold for each queue. What about the rest of thresholds? How to
> read/set them?
> 
> 14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls the
> resetting of the LLID MAC address log. Setting this object to none(1)
> has no action resetLog(2) empties the LLID MAC address log. All data is
> deleted. Setting it to useDefaultReporting(3) returns all entries
> priorities to their factory-default reporting. Reading this object
> always returns useDefaultReporting(3)." The description of this object
> seems to match some proprietary EPON device. In the 802.3ah standard,
> there is no provision of whether to keep LLID MAC address log. It is not
> clear, what does it mean "returns all entries priorities to their
> factory-default reporting", since there is no specification for either
> "entries" or "factory-default reporting". This object should be removed.
> 
> 15. Objects eponDeviceStatTxFramesQueue[0-7],
> eponDeviceStatRxFramesQueue[0-7], and
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such as
> bridge ports. There is no need to duplicate these objects here. Besides,
> neither 802.3ah nor 802.1D standards require exactly 8 queues to be
> implemented. I recommend removing these objects.
> 
> 16. The following objects represent non-EPON-specific events and should
> be
> moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl
> 
> 
> 
> 
> _______________________________________________
> 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



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


From hubmib-bounces@ietf.org  Tue Jan  4 15:04:02 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13078
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 15:04:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clumm-0001Rk-1c; Tue, 04 Jan 2005 14:56:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Clugg-0007PB-27
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 14:49:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11885
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 14:49:48 -0500 (EST)
Message-Id: <200501041949.OAA11885@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Clut5-0005XU-Nb
	for hubmib@ietf.org; Tue, 04 Jan 2005 15:02:40 -0500
Received: (qmail 20924 invoked by alias); 4 Jan 2005 19:49:46 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 4 Jan 2005 19:49:46 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpRxNotSupportedMpcp)
Date: Tue, 4 Jan 2005 11:49:38 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCURoVA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 142a000676f5977e1797396caab8b611
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[GK] dot3MpcpRxNotSupportedMpcp.  The description of this object does not
make sense. If a frame is not supported, it is not an MPCP frame.
Conversely, there exist no unsupported MPCP frames. There is no matching
attribute in clause 30 in 802.3ah and this object should be removed from
this draft as well.

[LK] dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode frames
which are not of PAUSE or used by the MPCP protocol. I will clear the
description.

[GK] Aha! So it is simply a counter of "not supported MAC Control opcodes".
In this case, this object is not EPON specific, but general for all Ethernet
MIBs. Furthermore, this object already exists (dot3ControlInUnknownOpcodes) 

Regards,
Glen

> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Lior khermosh
> Sent: Saturday, January 01, 2005 12:33 PM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Cc: 'Glen Kramer'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> Thank you very much for the comments and for the time you invested in
> reviewing the document. I appreciate it very much.
> 
> 
> 1. Thanks
> 
> 2. I believe it is useful to have also a configuration possibility for
> this parameter. As a guideline I believe management should have access
> to define main modes of the system. Can you please specify why do you
> think writing such a parameter is not useful? If we want to be strictly
> following clause 30 I can add change the attribute in the device MIBs
> objects to read-write but I would rather have it following the
> configuration from the EFM MIB objects.
> 
> 3. Agreed
> 
> 4. My believe is that the management entity as a general requires the
> knowledge of the PON switching time and does not need to find parameters
> in the spec to complete the picture as it is may be probably part of a
> more general access system. I think the MIB objects should supply a
> visibility of the system major parameters although some are fixed. I can
> add the description of 32TQs value to align with the MPCP.
> 
> 5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode frames
> which are not of PAUSE or used by the MPCP protocol. I will clear the
> description.
> 
> 6. Agreed
> 
> 7+8. If we can see the forwarding rules of the ONU in clause 65 then
> 7+there is a behavior for frames with bit broadcast in the LLID where
> 7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is
> 7+not the ONU's LLID (frame is accepted) as part of the point to point
> 7+emulation peer to peer capabilities. This counter counts the first
> 7+frame. I have sent in the past comments regarding that to clause 30.
> 7+The result was  OnuPonCastLLID and OltPonCastLLID which I think their
> 7+definition is too vague and refers to a long list of forwarding rules.
> 
> 7+A solution for alignment is to make a request to change in the
> 7+definition of these attributes in the spec and then unify these
> 7+counters in them.
> 
> 9. As a general logical deductive comment you have here a very good
> comment. The problem comes when in devices a reset process can be a very
> long process where many different sub-systems are reset. In such a
> scenario there is a meaning for being in a reset process. Therefore I
> believe that this is an attribute which is needed for a device. I am
> open here for suggestions.
> 
> 10. Thanks.
> 
> 11. Changing this variable might indeed cause very major changes in the
> system. Yet in my opinion it is needed for management. Unfortunately in
> true life engineered systems there is a possibility that a system is not
> operating well and it is needed to make it inactive immediately. The
> purpose of such an attribute is like this.
> 
> 12. I guess the question is what is the meaning of power down. I thought
> of a condition where the device is in minimal power mode where it is not
> transmitting and it is in listening mode so it can be enabled by
> activation according to MAC address. Keeping it registered can be done
> easily by reducing its SLA to minimal BW but I don't think it  is a
> power down mode. Keeping it in listening mode will really make it
> possible for the system to reduce power (notice I do not define what is
> exactly this mode as it can be implemented as the vendor wishes) yet
> have the minimal capability to wake up.
> 
> 13. O.K. Would you consider such an object definition instead: I think
> it covers multiple thresholds. eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }
> 
> 14. The OLT and ONUs of an EPON device serves as a distributed virtual
> switch where the LLIDs represent bridge ports. This model is behind the
> point to point emulation mechanism of clause 65 and of the whole LLID
> concept. A bridge have a MAC address to port address table and this
> table here serves for exactly the same purpose. It is not a proprietary
> implementation. The eponDeviceRemoteMACAddressLLIDControl is a control
> attribute for resetting this Table. As a table is a manageable entity I
> think such an object is needed. The useDefaultReporting(3) category is a
> common option for such attributes as a default setting for tables -
> Implementation is according to Vendors preference. I have no special
> suggestion for the default value. If people will feel more comfortable I
> can remove useDefaultReporting(3) and return in the reading none(1).
> 
> 15. The report message in the MPCP refers to such entities. Please see
> section 64.3.6.2 for report message format. These counters refer to
> that.
> 
> 16. As a general concept we tried to create in the EFM MIB objects a
> reflection of the IEEE802.3ah management object keeping as much as we
> can aligned to clause 30. There is here an additional section which
> refers to device MIB objects. In there I tried to put all things which
> are necessary for the management of an EPON device (in an access
> network) and was not truly covered by the IEEE802.3ah spec as being a
> spec for L2 MAC mainly. So although they are OAM they are in device
> level.
> 
> 
> Best regards,
> Lior
> 
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Romascanu, Dan (Dan)
> Sent: Sunday, December 19, 2004 4:22 PM
> To: hubmib@ietf.org
> Cc: Glen Kramer
> Subject: [Hubmib] FW: EPON MIB comments
> 
> 
> Although these comments from one of the 802.3ae contributors came in
> after the WG Last Call deadline, I suggest that we enter them as Last
> Call comments and address them accordingly.
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 16 December, 2004 9:49 PM
> To: Romascanu, Dan (Dan)
> Subject: EPON MIB comments
> 
> 
> Dan,
> 
> I finally read the EPON MIB document. Below are my comments. I am not
> sure if it is too late to make use of these, or not. Plsease, feel free
> to post these on the reflector.
> 
> Regards,
> Glen
> 
> 
> 1. In tables in section 7, object names that are split across lines lost
> a letter.
> 
> 2. dot3MpcpMode object should be read-only as is its counterpart in
> 802.3ah (aMPCPMode attribute).
> 
> 3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly
> to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The ONUs
> are not aware of the round-trip times to the OLT.
> 
> 4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the
> description that these objects refer to laser_on and laser_off times.
> Also, according to the 802.3ah, these times are constant and fixed at 32
> TQ. These objects are not necessary.  Correspondingly, 802.3ah did not
> find it necessary to specify such attributes in clause 30.
> 
> 5. dot3MpcpRxNotSupportedMpcp.  The description of this object does not
> make sense. If a frame is not supported, it is not an MPCP frame.
> Conversely, there exist no unsupported MPCP frames. There is no matching
> attribute in clause 30 in 802.3ah and this object should be removed from
> this draft as well.
> 
> 6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but
> optional at the ONU. It is not optional per 802.3ah and is relevant for
> both devices. (For comparison, the dot3OmpEmulationCRC8Errors is
> mandatory in the OLT and ONUs).
> 
> 7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the
> phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. Should
> it simply say "broadcast or unicast LLID"?  Also, there is no relevant
> attribute in clause 30 in 802.3ah.
> 
> 8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,
> as the dot3OmpEmulationBadLLID will count the same frames. I recommend
> removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.
> 
> 9. The access to eponDeviceObjectReset object should be write-only. If
> device is being reset, it cannot generate "reset" response. When the
> device can generate the response, it will be running already. Thus, the
> only possible response is "running".
> 
> 10. The object eponDeviceObjectOamMode is not necessary. To get the OAM
> mode, the management agent would access OAM MIB. No need to duplicate
> objects in different MIBs.
> 
> 11. eponDeviceObjectDeviceReadyMode object should be read-only.
> Modifying device mode through the management may have unpredictable
> results (like taking down entire EPON).
> 
> 12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will
> cause Device to be entered into Power down mode where no registration is
> allowed and only receiving data from the link.". This object does not
> make sense. Setting it to True will cause the device lose the link
> (because no transmission is allowed leading to MPCP timeout) and never
> register again (because registration is not allowed).
> 
> 13. eponDeviceObjectReportThreshold. The 802.3ah standard does not limit
> number of thresholds to be used.  This object will only return the first
> threshold for each queue. What about the rest of thresholds? How to
> read/set them?
> 
> 14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls the
> resetting of the LLID MAC address log. Setting this object to none(1)
> has no action resetLog(2) empties the LLID MAC address log. All data is
> deleted. Setting it to useDefaultReporting(3) returns all entries
> priorities to their factory-default reporting. Reading this object
> always returns useDefaultReporting(3)." The description of this object
> seems to match some proprietary EPON device. In the 802.3ah standard,
> there is no provision of whether to keep LLID MAC address log. It is not
> clear, what does it mean "returns all entries priorities to their
> factory-default reporting", since there is no specification for either
> "entries" or "factory-default reporting". This object should be removed.
> 
> 15. Objects eponDeviceStatTxFramesQueue[0-7],
> eponDeviceStatRxFramesQueue[0-7], and
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such as
> bridge ports. There is no need to duplicate these objects here. Besides,
> neither 802.3ah nor 802.1D standards require exactly 8 queues to be
> implemented. I recommend removing these objects.
> 
> 16. The following objects represent non-EPON-specific events and should
> be
> moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl
> 
> 
> 
> 
> _______________________________________________
> 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



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


From hubmib-bounces@ietf.org  Tue Jan  4 15:10:19 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13898
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 15:10:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cluz6-0003rx-FC; Tue, 04 Jan 2005 15:08:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CluwZ-0001Ww-Rq
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 15:06:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13403
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 15:06:13 -0500 (EST)
Message-Id: <200501042006.PAA13403@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Clv8z-0005v2-6p
	for hubmib@ietf.org; Tue, 04 Jan 2005 15:19:06 -0500
Received: (qmail 22874 invoked by alias); 4 Jan 2005 20:06:02 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 4 Jan 2005 20:06:02 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 4 Jan 2005 12:05:55 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCVIK0w
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 90e8b0e368115979782f8b3d811b226b
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[GK] Comment #7: dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear
what the phrase "broadcast LLID plus ONU's LLID (frame reflected)" means.
Should it simply say "broadcast or unicast LLID"?  Also, there is no
relevant attribute in clause 30 in 802.3ah. 
Comment #8: dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is
redundant, as the dot3OmpEmulationBadLLID will count the same frames. I
recommend removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.

[LK] If we can see the forwarding rules of the ONU in clause 65 then there
is a behavior for frames with bit broadcast in the LLID where the LLID is
the OLU's LLID (frames is rejected) and when the LLID is not the ONU's LLID
(frame is accepted) as part of the point to point emulation peer to peer
capabilities. This counter counts the first frame. I have sent in the past
comments regarding that to clause 30.
The result was OnuPonCastLLID and OltPonCastLLID which I think their
definition is too vague and refers to a long list of forwarding rules. A
solution for alignment is to make a request to change in the definition of
these attributes in the spec and then unify these counters in them.

[GK] I understand now the intentions of this object. I must add that its
description needs some work. Also, more appropriate name would be
"dot3OmpEmulationMode1PlusOnuId", because "Broadcast LLID" refers to a very
specific 15-bit value.
Also note that this mode would be used for shared medium emulation, not P2P.


Regards,
Glen


> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Lior khermosh
> Sent: Saturday, January 01, 2005 12:33 PM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Cc: 'Glen Kramer'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> Thank you very much for the comments and for the time you invested in
> reviewing the document. I appreciate it very much.
> 
> 
> 1. Thanks
> 
> 2. I believe it is useful to have also a configuration possibility for
> this parameter. As a guideline I believe management should have access
> to define main modes of the system. Can you please specify why do you
> think writing such a parameter is not useful? If we want to be strictly
> following clause 30 I can add change the attribute in the device MIBs
> objects to read-write but I would rather have it following the
> configuration from the EFM MIB objects.
> 
> 3. Agreed
> 
> 4. My believe is that the management entity as a general requires the
> knowledge of the PON switching time and does not need to find parameters
> in the spec to complete the picture as it is may be probably part of a
> more general access system. I think the MIB objects should supply a
> visibility of the system major parameters although some are fixed. I can
> add the description of 32TQs value to align with the MPCP.
> 
> 5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode frames
> which are not of PAUSE or used by the MPCP protocol. I will clear the
> description.
> 
> 6. Agreed
> 
> 7+8. If we can see the forwarding rules of the ONU in clause 65 then
> 7+there is a behavior for frames with bit broadcast in the LLID where
> 7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is
> 7+not the ONU's LLID (frame is accepted) as part of the point to point
> 7+emulation peer to peer capabilities. This counter counts the first
> 7+frame. I have sent in the past comments regarding that to clause 30.
> 7+The result was  OnuPonCastLLID and OltPonCastLLID which I think their
> 7+definition is too vague and refers to a long list of forwarding rules.
> 
> 7+A solution for alignment is to make a request to change in the
> 7+definition of these attributes in the spec and then unify these
> 7+counters in them.
> 
> 9. As a general logical deductive comment you have here a very good
> comment. The problem comes when in devices a reset process can be a very
> long process where many different sub-systems are reset. In such a
> scenario there is a meaning for being in a reset process. Therefore I
> believe that this is an attribute which is needed for a device. I am
> open here for suggestions.
> 
> 10. Thanks.
> 
> 11. Changing this variable might indeed cause very major changes in the
> system. Yet in my opinion it is needed for management. Unfortunately in
> true life engineered systems there is a possibility that a system is not
> operating well and it is needed to make it inactive immediately. The
> purpose of such an attribute is like this.
> 
> 12. I guess the question is what is the meaning of power down. I thought
> of a condition where the device is in minimal power mode where it is not
> transmitting and it is in listening mode so it can be enabled by
> activation according to MAC address. Keeping it registered can be done
> easily by reducing its SLA to minimal BW but I don't think it  is a
> power down mode. Keeping it in listening mode will really make it
> possible for the system to reduce power (notice I do not define what is
> exactly this mode as it can be implemented as the vendor wishes) yet
> have the minimal capability to wake up.
> 
> 13. O.K. Would you consider such an object definition instead: I think
> it covers multiple thresholds. eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }
> 
> 14. The OLT and ONUs of an EPON device serves as a distributed virtual
> switch where the LLIDs represent bridge ports. This model is behind the
> point to point emulation mechanism of clause 65 and of the whole LLID
> concept. A bridge have a MAC address to port address table and this
> table here serves for exactly the same purpose. It is not a proprietary
> implementation. The eponDeviceRemoteMACAddressLLIDControl is a control
> attribute for resetting this Table. As a table is a manageable entity I
> think such an object is needed. The useDefaultReporting(3) category is a
> common option for such attributes as a default setting for tables -
> Implementation is according to Vendors preference. I have no special
> suggestion for the default value. If people will feel more comfortable I
> can remove useDefaultReporting(3) and return in the reading none(1).
> 
> 15. The report message in the MPCP refers to such entities. Please see
> section 64.3.6.2 for report message format. These counters refer to
> that.
> 
> 16. As a general concept we tried to create in the EFM MIB objects a
> reflection of the IEEE802.3ah management object keeping as much as we
> can aligned to clause 30. There is here an additional section which
> refers to device MIB objects. In there I tried to put all things which
> are necessary for the management of an EPON device (in an access
> network) and was not truly covered by the IEEE802.3ah spec as being a
> spec for L2 MAC mainly. So although they are OAM they are in device
> level.
> 
> 
> Best regards,
> Lior
> 
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Romascanu, Dan (Dan)
> Sent: Sunday, December 19, 2004 4:22 PM
> To: hubmib@ietf.org
> Cc: Glen Kramer
> Subject: [Hubmib] FW: EPON MIB comments
> 
> 
> Although these comments from one of the 802.3ae contributors came in
> after the WG Last Call deadline, I suggest that we enter them as Last
> Call comments and address them accordingly.
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 16 December, 2004 9:49 PM
> To: Romascanu, Dan (Dan)
> Subject: EPON MIB comments
> 
> 
> Dan,
> 
> I finally read the EPON MIB document. Below are my comments. I am not
> sure if it is too late to make use of these, or not. Plsease, feel free
> to post these on the reflector.
> 
> Regards,
> Glen
> 
> 
> 1. In tables in section 7, object names that are split across lines lost
> a letter.
> 
> 2. dot3MpcpMode object should be read-only as is its counterpart in
> 802.3ah (aMPCPMode attribute).
> 
> 3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly
> to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The ONUs
> are not aware of the round-trip times to the OLT.
> 
> 4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the
> description that these objects refer to laser_on and laser_off times.
> Also, according to the 802.3ah, these times are constant and fixed at 32
> TQ. These objects are not necessary.  Correspondingly, 802.3ah did not
> find it necessary to specify such attributes in clause 30.
> 
> 5. dot3MpcpRxNotSupportedMpcp.  The description of this object does not
> make sense. If a frame is not supported, it is not an MPCP frame.
> Conversely, there exist no unsupported MPCP frames. There is no matching
> attribute in clause 30 in 802.3ah and this object should be removed from
> this draft as well.
> 
> 6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but
> optional at the ONU. It is not optional per 802.3ah and is relevant for
> both devices. (For comparison, the dot3OmpEmulationCRC8Errors is
> mandatory in the OLT and ONUs).
> 
> 7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the
> phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. Should
> it simply say "broadcast or unicast LLID"?  Also, there is no relevant
> attribute in clause 30 in 802.3ah.
> 
> 8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,
> as the dot3OmpEmulationBadLLID will count the same frames. I recommend
> removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.
> 
> 9. The access to eponDeviceObjectReset object should be write-only. If
> device is being reset, it cannot generate "reset" response. When the
> device can generate the response, it will be running already. Thus, the
> only possible response is "running".
> 
> 10. The object eponDeviceObjectOamMode is not necessary. To get the OAM
> mode, the management agent would access OAM MIB. No need to duplicate
> objects in different MIBs.
> 
> 11. eponDeviceObjectDeviceReadyMode object should be read-only.
> Modifying device mode through the management may have unpredictable
> results (like taking down entire EPON).
> 
> 12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will
> cause Device to be entered into Power down mode where no registration is
> allowed and only receiving data from the link.". This object does not
> make sense. Setting it to True will cause the device lose the link
> (because no transmission is allowed leading to MPCP timeout) and never
> register again (because registration is not allowed).
> 
> 13. eponDeviceObjectReportThreshold. The 802.3ah standard does not limit
> number of thresholds to be used.  This object will only return the first
> threshold for each queue. What about the rest of thresholds? How to
> read/set them?
> 
> 14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls the
> resetting of the LLID MAC address log. Setting this object to none(1)
> has no action resetLog(2) empties the LLID MAC address log. All data is
> deleted. Setting it to useDefaultReporting(3) returns all entries
> priorities to their factory-default reporting. Reading this object
> always returns useDefaultReporting(3)." The description of this object
> seems to match some proprietary EPON device. In the 802.3ah standard,
> there is no provision of whether to keep LLID MAC address log. It is not
> clear, what does it mean "returns all entries priorities to their
> factory-default reporting", since there is no specification for either
> "entries" or "factory-default reporting". This object should be removed.
> 
> 15. Objects eponDeviceStatTxFramesQueue[0-7],
> eponDeviceStatRxFramesQueue[0-7], and
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such as
> bridge ports. There is no need to duplicate these objects here. Besides,
> neither 802.3ah nor 802.1D standards require exactly 8 queues to be
> implemented. I recommend removing these objects.
> 
> 16. The following objects represent non-EPON-specific events and should
> be
> moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl
> 
> 
> 
> 
> _______________________________________________
> 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



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


From hubmib-bounces@ietf.org  Tue Jan  4 19:21:49 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07161
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 19:21:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clytp-00013F-8N; Tue, 04 Jan 2005 19:19:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Clysh-0000R0-Ii
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 19:18:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07028
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 19:18:26 -0500 (EST)
Message-Id: <200501050018.TAA07028@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Clz4t-0004NC-9n
	for hubmib@ietf.org; Tue, 04 Jan 2005 19:31:22 -0500
Received: (qmail 11358 invoked by alias); 5 Jan 2005 00:18:01 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 5 Jan 2005 00:18:01 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 4 Jan 2005 16:17:52 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCcHRDw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[GK] eponDeviceObjectDeviceReadyMode object should be read-only. Modifying
device mode through the management may have unpredictable results (like
taking down entire EPON).

[LK] Changing this variable might indeed cause very major changes in the
system. Yet in my opinion it is needed for management. Unfortunately in true
life engineered systems there is a possibility that a system is not
operating well and it is needed to make it inactive immediately. The purpose
of such an attribute is like this.

[GK] We should not confuse MIB with debug functions. I would agree to have
an object that would allow disabling a device. I am against allowing
management changing device mode from notReady to ready or from inProcess to
ready. This would take down the device and very likely would take down the
entire EPON. Device mode should only change according to state machines
defined in IEEE 802.3ah.

Regards,
Glen

 



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


From hubmib-bounces@ietf.org  Tue Jan  4 19:41:50 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08216
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 19:41:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClzC1-00077r-K8; Tue, 04 Jan 2005 19:38:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Clz85-0005yR-8U
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 19:34:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07869
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 19:34:21 -0500 (EST)
Message-Id: <200501050034.TAA07869@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1ClzKU-0004eU-MV
	for hubmib@ietf.org; Tue, 04 Jan 2005 19:47:18 -0500
Received: (qmail 9387 invoked by alias); 5 Jan 2005 00:34:18 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 5 Jan 2005 00:34:18 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (eponDeviceObjectPowerDown)
Date: Tue, 4 Jan 2005 16:34:10 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCekAYQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[GK] eponDeviceObjectPowerDown - "Setting this variable to True(1) will
cause Device to be entered into Power down mode where no registration is
allowed and only receiving data from the link.". This object does not make
sense. Setting it to True will cause the device lose the link (because no
transmission is allowed leading to MPCP timeout) and never register again
(because registration is not allowed).

[LK] I guess the question is what is the meaning of power down. I thought of
a condition where the device is in minimal power mode where it is not
transmitting and it is in listening mode so it can be enabled by activation
according to MAC address. Keeping it registered can be done easily by
reducing its SLA to minimal BW but I don't think it is a power down mode.
Keeping it in listening mode will really make it possible for the system to
reduce power (notice I do not define what is exactly this mode as it can be
implemented as the vendor wishes) yet have the minimal capability to wake
up.

[GK] This is very suspiciously seems like fitting of MIB spec to a specific
proprietary implementation. Even if device is not transmitting any user
data, it should periodically transmit MPCP and OAM messages. 
You are trying to define some kind of standby mode without clear explanation
what this mode is or how it can be implemented. I argue that because MPCP
relies on periodic messages, this mode is not possible without breaking IEEE
802.3ah standard.
"Keeping it registered can be done easily by reducing its SLA to minimal
BW..." This is a particular implementation. Device registration has nothing
to do with the provisioned SLA. There is a very formal state machine that
explains steps of EPON device registration. 



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


From hubmib-bounces@ietf.org  Tue Jan  4 19:55:23 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09075
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 19:55:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClzNs-00032u-T8; Tue, 04 Jan 2005 19:50:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClzJm-0001H9-GH
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 19:46:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08505
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 19:46:26 -0500 (EST)
Message-Id: <200501050046.TAA08505@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1ClzWC-0004rP-4s
	for hubmib@ietf.org; Tue, 04 Jan 2005 19:59:23 -0500
Received: (qmail 28951 invoked by alias); 5 Jan 2005 00:46:22 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 5 Jan 2005 00:46:22 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (eponDeviceObjectReportThreshold)
Date: Tue, 4 Jan 2005 16:46:15 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCfDJLg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[GK] eponDeviceObjectReportThreshold. The 802.3ah standard does not limit
number of thresholds to be used.  This object will only return the first
threshold for each queue. What about the rest of thresholds? How to read/set
them?

[LK] O.K. Would you consider such an object definition instead: I think it
covers multiple thresholds. 

> eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }

[GK] This is better. For the eponDeviceObjectReportNumThreshold, we need to
describe what happens if this parameter is set to a value greater than the
device can support.  Or maybe we should define a read-only object
eponDeviceObjectReportMaximumNumThreshold that would inform management
entity of the maximum supported number of thresholds.

I would also add read-only object for maximum supported number of queues:
802.1D says that a device can have from 1 to 8 queues.




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


From hubmib-bounces@ietf.org  Tue Jan  4 20:10:14 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09898
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 20:10:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClzeR-0008CI-NY; Tue, 04 Jan 2005 20:07:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClzZI-0006VY-5t
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 20:02:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09497
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 20:02:30 -0500 (EST)
Message-Id: <200501050102.UAA09497@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Clzlh-0005Ax-P4
	for hubmib@ietf.org; Tue, 04 Jan 2005 20:15:25 -0500
Received: (qmail 23621 invoked by alias); 5 Jan 2005 01:02:26 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 5 Jan 2005 01:02:26 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>,
        "'Lior khermosh'" <lior.khermosh@passave.com>
Subject: RE: [Hubmib] FW: EPON MIB comments
	(eponDeviceRemoteMACAddressLLIDControl)
Date: Tue, 4 Jan 2005 17:02:17 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCfgvIQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[GK] eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls the
resetting of the LLID MAC address log. Setting this object to none(1) has no
action resetLog(2) empties the LLID MAC address log. All data is deleted.
Setting it to useDefaultReporting(3) returns all entries priorities to their
factory-default reporting. Reading this object always returns
useDefaultReporting(3)." The description of this object seems to match some
proprietary EPON device. In the 802.3ah standard, there is no provision of
whether to keep LLID MAC address log. It is not clear, what does it mean
"returns all entries priorities to their factory-default reporting", since
there is no specification for either "entries" or "factory-default
reporting". This object should be removed.

[LK] The OLT and ONUs of an EPON device serves as a distributed virtual
switch where the LLIDs represent bridge ports. This model is behind the
point to point emulation mechanism of clause 65 and of the whole LLID
concept. A bridge have a MAC address to port address table and this table
here serves for exactly the same purpose. It is not a proprietary
implementation. The eponDeviceRemoteMACAddressLLIDControl is a control
attribute for resetting this Table. As a table is a manageable entity I
think such an object is needed. The useDefaultReporting(3) category is a
common option for such attributes as a default setting for tables -
Implementation is according to Vendors preference. I have no special
suggestion for the default value. If people will feel more comfortable I can
remove useDefaultReporting(3) and return in the reading none(1).

[GK] There is no document defining what is "LLID MAC address log". The
phrase "The OLT and ONUs of an EPON device serves as a distributed virtual
switch where the LLIDs represent bridge ports" assumes a particular
implementation.
LLIDs do not represent bridge ports. LLID represent virtual links.  These
links may or may not be connected to a bridge at the OLT. The
eponDeviceRemoteMACAddressLLIDControl attribute refers to an address table
in the bridge and has nothing to do with EPON. Therefore, it should be moved
to the bridge MIB.

Regards,
Glen

 




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


From hubmib-bounces@ietf.org  Tue Jan  4 20:34:33 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11564
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 20:34:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clzyg-00066m-FB; Tue, 04 Jan 2005 20:28:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClzvF-0004mA-69
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 20:25:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10641
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 20:25:11 -0500 (EST)
Message-Id: <200501050125.UAA10641@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cm07g-0005ZF-CC
	for hubmib@ietf.org; Tue, 04 Jan 2005 20:38:06 -0500
Received: (qmail 29081 invoked by alias); 5 Jan 2005 01:25:00 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 5 Jan 2005 01:25:00 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 4 Jan 2005 17:24:51 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0088_01C4F282.4C7D0AF0"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCgCDcw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdfdd9dd835c9bb499f7c92933fef080
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0088_01C4F282.4C7D0AF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

[GK] Objects eponDeviceStatTxFramesQueue[0-7],
eponDeviceStatRxFramesQueue[0-7], and
eponDeviceStatDroppedFramesQueue[0-7]
are not specific to EPON. These objects exist for other devices, such as
bridge ports. There is no need to duplicate these objects here. Besides,
neither 802.3ah nor 802.1D standards require exactly 8 queues to be
implemented. I recommend removing these objects.

[LK] The report message in the MPCP refers to such entities. Please see
section 64.3.6.2 for report message format. These counters refer to that.

[GK] The REPORT message does not refer directly of indirectly to any such
entities. I attached the clause 64.3.6.2. Would appreciate if you could
point where and how this clause refers to count of transmitted, received,
and dropped frames. 
I agree that these are useful parameters. But my point is that they are
already defined and are not EPON-specific. There is no need to duplicate
them in this MIB.
 
Regards,
Glen

------=_NextPart_000_0088_01C4F282.4C7D0AF0
Content-Type: application/pdf;
	name="Clause64.3.6.2.pdf"
Content-Disposition: attachment;
	filename="Clause64.3.6.2.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjQNJeLjz9MNCjEzIDAgb2JqIDw8L0xpbmVhcml6ZWQgMS9MIDE5MTUyL08gMTYvRSA5
NzA0L04gMi9UIDE4ODQ1L0ggWyA3MzYgMTkzXT4+DWVuZG9iag0gICAgICAgICAgICAgICAgICAg
DQp4cmVmDQoxMyAyMg0KMDAwMDAwMDAxNiAwMDAwMCBuDQowMDAwMDAwOTI5IDAwMDAwIG4NCjAw
MDAwMDA3MzYgMDAwMDAgbg0KMDAwMDAwMTAwOCAwMDAwMCBuDQowMDAwMDAxMTg3IDAwMDAwIG4N
CjAwMDAwMDEzMDAgMDAwMDAgbg0KMDAwMDAwMTkxNyAwMDAwMCBuDQowMDAwMDAyNDI3IDAwMDAw
IG4NCjAwMDAwMDMwNTggMDAwMDAgbg0KMDAwMDAwMzIzNyAwMDAwMCBuDQowMDAwMDAzNDE4IDAw
MDAwIG4NCjAwMDAwMDM2MDggMDAwMDAgbg0KMDAwMDAwMzY4NCAwMDAwMCBuDQowMDAwMDA0NTQw
IDAwMDAwIG4NCjAwMDAwMDUzMDcgMDAwMDAgbg0KMDAwMDAwNjE1NyAwMDAwMCBuDQowMDAwMDA3
MDAxIDAwMDAwIG4NCjAwMDAwMDc3ODUgMDAwMDAgbg0KMDAwMDAwODI3NiAwMDAwMCBuDQowMDAw
MDA4OTIyIDAwMDAwIG4NCjAwMDAwMDkyNjYgMDAwMDAgbg0KMDAwMDAwOTUxOCAwMDAwMCBuDQp0
cmFpbGVyDQo8PC9TaXplIDM1L1ByZXYgMTg4MzQvUm9vdCAxNCAwIFIvSW5mbyAxMiAwIFIvSURb
PDNlYTFiZTg4OWZmOGVkMmY1M2UxZTg3ZjBkMjMyNmI3PjwzZjM1NTVhODRkZjYxMjQ2Yjk3ZGNl
ZGViMGY0NmY3Yz5dPj4NCnN0YXJ0eHJlZg0KMA0KJSVFT0YNCiAgICAgICAgICAgICANCjE1IDAg
b2JqPDwvTGVuZ3RoIDExMy9GaWx0ZXIvRmxhdGVEZWNvZGUvTCAxMjAvUyA2Nj4+c3RyZWFtDQp4
2mJgYGBlYGDWZ2BhYBC0ZOBlQABeoBgrEHM8aP3BwNAJFtPoMZ4ovIABrImBLQEkAWIwMJglAGlh
IBYFi/gwcEkeiijd1HWscEkRg8Gp82wHdNzqrJy5GXcuznCAmM/BwGBlA6SZgNgCIMAAfmsUvQ0K
ZW5kc3RyZWFtDWVuZG9iag0xNCAwIG9iajw8L1BhZ2VzIDEwIDAgUi9UeXBlL0NhdGFsb2cvUGFn
ZUxhYmVscyA4IDAgUi9NZXRhZGF0YSAxMSAwIFI+Pg1lbmRvYmoNMTYgMCBvYmo8PC9Db250ZW50
c1syNSAwIFIgMjYgMCBSIDI3IDAgUiAyOCAwIFIgMjkgMCBSIDMxIDAgUiAzMiAwIFIgMzMgMCBS
XS9UeXBlL1BhZ2UvUGFyZW50IDEwIDAgUi9Sb3RhdGUgMC9NZWRpYUJveFswIDAgNjEyIDc5Ml0v
Q3JvcEJveFswIDAgNjEyIDc5Ml0vUmVzb3VyY2VzIDE3IDAgUj4+DWVuZG9iag0xNyAwIG9iajw8
L0ZvbnQ8PC9GMSAxOCAwIFIvRjIgMTkgMCBSL0YzIDIwIDAgUi9GNCAzMCAwIFI+Pi9Qcm9jU2V0
Wy9QREYvVGV4dF0vRXh0R1N0YXRlPDwvR1MxIDI0IDAgUj4+Pj4NZW5kb2JqDTE4IDAgb2JqPDwv
VHlwZS9Gb250L0VuY29kaW5nL1dpbkFuc2lFbmNvZGluZy9CYXNlRm9udC9IZWx2ZXRpY2EvRmly
c3RDaGFyIDMyL0xhc3RDaGFyIDE2OS9TdWJ0eXBlL1R5cGUxL0ZvbnREZXNjcmlwdG9yIDIxIDAg
Ui9XaWR0aHNbMjc4IDI3OCAzNTUgNTU2IDU1NiA4ODkgNjY3IDE5MSAzMzMgMzMzIDM4OSA1ODQg
Mjc4IDMzMyAyNzggMjc4IDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiAy
NzggMjc4IDU4NCA1ODQgNTg0IDU1NiAxMDE1IDY2NyA2NjcgNzIyIDcyMiA2NjcgNjExIDc3OCA3
MjIgMjc4IDUwMCA2NjcgNTU2IDgzMyA3MjIgNzc4IDY2NyA3NzggNzIyIDY2NyA2MTEgNzIyIDY2
NyA5NDQgNjY3IDY2NyA2MTEgMjc4IDI3OCAyNzggNDY5IDU1NiAzMzMgNTU2IDU1NiA1MDAgNTU2
IDU1NiAyNzggNTU2IDU1NiAyMjIgMjIyIDUwMCAyMjIgODMzIDU1NiA1NTYgNTU2IDU1NiAzMzMg
NTAwIDI3OCA1NTYgNTAwIDcyMiA1MDAgNTAwIDUwMCAzMzQgMjYwIDMzNCA1ODQgMCAwIDAgMCAw
IDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAg
MCAwIDU1NiA1NTYgMCAwIDAgMCAwIDczN10+Pg1lbmRvYmoNMTkgMCBvYmo8PC9UeXBlL0ZvbnQv
RW5jb2RpbmcvV2luQW5zaUVuY29kaW5nL0Jhc2VGb250L1RpbWVzLVJvbWFuL0ZpcnN0Q2hhciAz
Mi9MYXN0Q2hhciAxMjIvU3VidHlwZS9UeXBlMS9Gb250RGVzY3JpcHRvciAyMiAwIFIvV2lkdGhz
WzI1MCAzMzMgNDA4IDUwMCA1MDAgODMzIDc3OCAxODAgMzMzIDMzMyA1MDAgNTY0IDI1MCAzMzMg
MjUwIDI3OCA1MDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgMjc4IDI3OCA1
NjQgNTY0IDU2NCA0NDQgOTIxIDcyMiA2NjcgNjY3IDcyMiA2MTEgNTU2IDcyMiA3MjIgMzMzIDM4
OSA3MjIgNjExIDg4OSA3MjIgNzIyIDU1NiA3MjIgNjY3IDU1NiA2MTEgNzIyIDcyMiA5NDQgNzIy
IDcyMiA2MTEgMzMzIDI3OCAzMzMgNDY5IDUwMCAzMzMgNDQ0IDUwMCA0NDQgNTAwIDQ0NCAzMzMg
NTAwIDUwMCAyNzggMjc4IDUwMCAyNzggNzc4IDUwMCA1MDAgNTAwIDUwMCAzMzMgMzg5IDI3OCA1
MDAgNTAwIDcyMiA1MDAgNTAwIDQ0NF0+Pg1lbmRvYmoNMjAgMCBvYmo8PC9UeXBlL0ZvbnQvRW5j
b2RpbmcvV2luQW5zaUVuY29kaW5nL0Jhc2VGb250L0hlbHZldGljYS1Cb2xkL0ZpcnN0Q2hhciAz
Mi9MYXN0Q2hhciAxNTEvU3VidHlwZS9UeXBlMS9Gb250RGVzY3JpcHRvciAyMyAwIFIvV2lkdGhz
WzI3OCAzMzMgNDc0IDU1NiA1NTYgODg5IDcyMiAyMzggMzMzIDMzMyAzODkgNTg0IDI3OCAzMzMg
Mjc4IDI3OCA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiA1NTYgMzMzIDMzMyA1
ODQgNTg0IDU4NCA2MTEgOTc1IDcyMiA3MjIgNzIyIDcyMiA2NjcgNjExIDc3OCA3MjIgMjc4IDU1
NiA3MjIgNjExIDgzMyA3MjIgNzc4IDY2NyA3NzggNzIyIDY2NyA2MTEgNzIyIDY2NyA5NDQgNjY3
IDY2NyA2MTEgMzMzIDI3OCAzMzMgNTg0IDU1NiAzMzMgNTU2IDYxMSA1NTYgNjExIDU1NiAzMzMg
NjExIDYxMSAyNzggMjc4IDU1NiAyNzggODg5IDYxMSA2MTEgNjExIDYxMSAzODkgNTU2IDMzMyA2
MTEgNTU2IDc3OCA1NTYgNTU2IDUwMCAzODkgMjgwIDM4OSA1ODQgMzUwIDAgMzUwIDI3OCA1NTYg
NTAwIDEwMDAgNTU2IDU1NiAzMzMgMTAwMCA2NjcgMzMzIDEwMDAgMzUwIDYxMSAzNTAgMzUwIDI3
OCAyNzggNTAwIDUwMCAzNTAgNTU2IDEwMDBdPj4NZW5kb2JqDTIxIDAgb2JqPDwvVHlwZS9Gb250
RGVzY3JpcHRvci9Gb250QkJveFstMTY2IC0yMjUgMTAwMCA5MzFdL0ZvbnROYW1lL0hlbHZldGlj
YS9GbGFncyAzMi9TdGVtViA4OC9TdGVtSCA4OC9DYXBIZWlnaHQgNzE4L1hIZWlnaHQgNTIzL0Fz
Y2VudCA3MTgvRGVzY2VudCAtMjA3L0l0YWxpY0FuZ2xlIDA+Pg1lbmRvYmoNMjIgMCBvYmo8PC9U
eXBlL0ZvbnREZXNjcmlwdG9yL0ZvbnRCQm94Wy0xNjggLTIxOCAxMDAwIDg5OF0vRm9udE5hbWUv
VGltZXMtUm9tYW4vRmxhZ3MgMzQvU3RlbVYgODQvU3RlbUggODQvQ2FwSGVpZ2h0IDY2Mi9YSGVp
Z2h0IDQ1MC9Bc2NlbnQgNjk5L0Rlc2NlbnQgLTIxNy9JdGFsaWNBbmdsZSAwPj4NZW5kb2JqDTIz
IDAgb2JqPDwvVHlwZS9Gb250RGVzY3JpcHRvci9Gb250QkJveFstMTcwIC0yMjggMTAwMyA5NjJd
L0ZvbnROYW1lL0hlbHZldGljYS1Cb2xkL0ZsYWdzIDI2MjE3Ni9TdGVtViAxNDAvU3RlbUggMTQw
L0NhcEhlaWdodCA3MTgvWEhlaWdodCA1MzIvQXNjZW50IDcxOC9EZXNjZW50IC0yMDcvSXRhbGlj
QW5nbGUgMD4+DWVuZG9iag0yNCAwIG9iajw8L1R5cGUvRXh0R1N0YXRlL1NBIGZhbHNlL09QIGZh
bHNlL1NNIDAuMDIvb3AgZmFsc2UvT1BNIDE+Pg1lbmRvYmoNMjUgMCBvYmo8PC9MZW5ndGggNzg3
L0ZpbHRlci9GbGF0ZURlY29kZT4+c3RyZWFtDQpIiZRUyVLbQBC96yv6OHPQMJu1HAmYFKliKaOc
AgdiCVtVIBtZhuKT8pfp6Wlhi8olpcOo99fvjfSanCya58ehfWvONs+bvn1phr5dQt9CcvL9zsBq
l3yrkpMLAwaqpyRXpQWND70UhdIF5DOtMq9zqF4SDask1Upr7aBaolm9J7/EpUztTDkxn89BPlQ/
0J8aZWZmBtV5gummDNmh0HoXa+6kL1UmBmk9VtbSlmomQKZOo1lEU0ssKYSNloqp7nEd7VSaQuUY
pSQ9KfHYyOAsZcWpNCWWXc3jeS2Nw6rzeFxJh0XTUCXTTHkBlbROleJGujKYDO0youCSzyM1RsDn
TjOPRw0FgcqEHaETOScXNpJdqsIT2fRSlEp7cIHyyHWgy1h7xLPPkGiPYDJu9E/VXJarrDjuRArY
gwSz2O4s7FuKTQCZi+1HHwgtRRtsI1ZSi3UMkUgHdf5IG/LAah3jHi5jBtExIzqCCmwqLj9l93Mc
wMfY9cv06eid9CGVc5oY2zVsv0kXWGkQcR1Digly/2K6RKJwc4Q/sqMzTzTjW8H3M/NKpkUQTUmT
4fDAvRNsWFjgkmG5W2k83ZLUajQXlUT2BdR0NFSzW/Zt7LUl74A42bEhRze9F/j1WOX84euxDC4v
WTkcHhbA4TlOxmSxkFmJjipcxMDUiwzgcH6OxOwk8c7HY3SuGmny0Qdr9r6RF9jdHDt7TkHdDFIM
T/tuGfxDGx2bbpqAK9qo4JHFQ1OEnwUyiwC2ki7QwCkT6CMS7sITYsoW2g6oIbsJzjr8AayAA0ep
CcEvPFEMaUpJvgmsT57Qt4rdRjS86sgafY5O7MMltZ/11KxmGE+bHvpNTNh39eH3aE1JAtNnXpgo
LK/Z02+p3cL9F8CjvvcSlkeLM+PLaDGc50gnp4wybLoYVeEv5wRcdsCh9bhquACLOU+6vfmvqxUo
m4bg5vrn+Np2dTuBSgVDHDms47nfjpr3x+LGsfCbSrr6va3jIsMaOsrjsUz8OPLrcpTzweL00uak
Pnlf98efxCAf4K8AAwC9ZZFODQplbmRzdHJlYW0NZW5kb2JqDTI2IDAgb2JqPDwvTGVuZ3RoIDY5
OC9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0KSIlsVMlu2zAQvecreCSLiBApmpLOSVG0aOo0
kE9FD4LlhYgjO4rcwn/f2WggQU8WZ3tv5s24+3bTfbopbencQnVr/Cpjo7q/N7/0aWNctAs9qab0
1rjaRu1+qtOUjHfW62P+mC/q9SzB+deaItpGq6fPxnlb60eD1qVxYHwyIdigO/aoF1O4Bbwl8824
0lb5pzdFbVu9e+9UpvBYoheGpsrZShIOpqiAmsQfTVEi1FneEjyIWXJy8Wdxb9h84qjC+JogpT61
nhjmz5Ve4YJ1Wm0njj7m5tTyx0rNR+MrBFwCfw/j/G4cQXYmOhoaDRljPzQqk77OhmHOXG5jfndX
HT3pWOBnE1lI1KAiDWrSwJMGsQVTB5VKhHyhkiRCzXN2AlQBUM/WneHhgbRtDlEnSZkSdBeg5pDW
bOk5EEblgfvhotKojtPAUVJlMqWmuaAtd/sCbebsxNkjQc9CBApJVRCA3M9qv/kf6rxXYpjZoOYc
mNGWqIIjFWQY/fsOB0nYplG+BmwlBtCrgfhKfuFdLHDpv45KiA5DEtx0HLnJ26xWQcfm5Ox8CKzW
vAcaDc/ZL4gn06RNamBnIno7lAxRgawDiS6Spd5wQSvcWq6yljJpSxJHGlkJhdac2Iv/YCpwHsR5
Lcfgk+RuOOdVvOcPVAV7plKqx+svfAvdP0IgJuYmnswCn524BQU6qqqMIbXgp3Iwtn6XsSwNsFQo
vGth3e958QNP0tVR9r7DtY96D6vj6ZgzDtJypVxEoIuo+SKiLME19AGZ1/rOwFRaib8H1khpRXkS
mGhbPP+ZaNIaRpBGMdMW0LDBKY9ESxL0zJcTNZzHVokzs6YI9YXoj/Kc+MLA/sCM7oTY6hY3sM2c
GG34yHB7njJILig7Hq47HmDHz5KQOHjcwe0w0U2WAITyHhVQ/wQYAASwYS0NCmVuZHN0cmVhbQ1l
bmRvYmoNMjcgMCBvYmo8PC9MZW5ndGggNzgxL0ZpbHRlci9GbGF0ZURlY29kZT4+c3RyZWFtDQpI
iXxUyW7bMBC9+ysG6EUsIEKk9t6KJpcCzVb31OaQWJItwJUUWULQv+9sdOMcepLI2d68ecM4sYmr
cti+bn5G3Wh8ZovoeNSfVxN7Z8uoN95bFw17aFrjSptFXT/o5aLfcTgZ56yPPpnH7deNs4nPMoid
dd7VsL3aUCVXwHa3iem3LKXok4lLW0W/jIldhgny6HbaGVdg+RGrsdFS0TKCLfqQx8FgiiJqxQ0Q
ZYaYEHSKzpMYdxI6yqkRm+aDbpxhObyLfzA+wUautcidIeOtcbZGU1FhXKgP38T4RT5XP0IK5MLZ
NDpRLxEkSZxI3dQyKQnxgXTkgQ8iYYd/znudwbPJsQCzkeaU/MZU0cqXv43LkV/xaGdT4wGw6RoB
dnK6Pzu3qxha+G6cR/KwdRrlYjzN70St55FFSl2FbgcO6vUaJF0vvu1Rvg37gPpMUmZH00eFdCZN
EW3fhhRaSBK3MAic0ElccycC8dwK2TQRyKWifmFTaElLLKGU4hwE36IlBRg8XEuHdzy7Egda4TjL
DK+0d1A4GqFZTySVGuXJl/u3Oa1oCj7zUL1M9N1kfSGTTdLEyWQJCGnhzpSsK1qtnJRVs7LYBt38
RFoviCKXoZRaOSJGR+LEbSnQ7w/tJ7ofxiNBSqMmOKwmQSqOi1z3k9pbiQPDMuVNzcLlokc1jh08
kIxdsE/jbHxFhMNzL+mWSziTwtHjIMcG7leFv17W/zDojwYEAPqduAcN3YmLFu5MhmV7tTWg1wNH
gHZ90Pi3JW/WwOizoFPzzDPcfpR1rMLz5NNapkaiLHi9Ul4vppiucMHSJKxXJUItVJOFbBDyb1Lm
0ZPLkQ8NF4z/rxqXeymv3evrmJBgtHeciraLU9G/0KJqaLIkcH03E343iZg+0N1fDv48Peay0pme
k6tXp4pS7714i21WUvc6Fs2/oNaZBkY18whxTRXlosH90GiYNh3sGhfAvh76ndwc4GW9GOb6VjjB
/ykMOvuHAebA4nz2xgc3mIflYmsaQ1o/w7yUGZL4CH8FGADUzZn8DQplbmRzdHJlYW0NZW5kb2Jq
DTI4IDAgb2JqPDwvTGVuZ3RoIDc3NS9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0KSIlsVctu
2zAQvPsrCORCFpUgUpZknZP2EKBoYqinNgcn8kOFQjmKnCB/313u0ImCXsTX7sxwH1RzvXCps3Wh
Eitjc7XI0swWtWoeeJa5pWpeF7/1+puxVWr1jbFZWuufJrGr1Om1qXLabeRQ/cDxJcYrU5LRr/BN
jXNambvmepFEVlentsqqSOsKoXVZVgtt+8cQU17adKVvT1umKTSNSUno6sKrNeZH45ZppQeTpbke
p9SQvJLoEtpesr6cTg/htCMhpOeZgVn0y0Zg+4gfvUasj3HybKwlAFD66RPQdBARUV4PN7+PJxF5
2KmnD7cJ40U89AqCJsOBItzukcJ5hiVnzgZf6Iaoy5AORwFam7KmTVw2wn30xQUwbGRzH1Vzav5f
D86hHqo6l8Tsg2qnPSHzOG5kPVF0LYEOPqQg16ohjVwLIQRLDXs1GreioGF5HLCesNGKNWLoOIYC
fFCsnlPJ+vmol4Ne3c8ZoKgly79icqKpZGupAfeJbhqUzID9IBgPsqLqIgxJ0qR2g0xHJP6d2W+j
WxiwHXSHD8DHN5B1fq4GsUh2mMD+0dRSXYEkIB1DGD5qRPw9HexDRpsvksISKcwzKykM6V+RJWlY
6TbWy3dTUeeEAlvpS3WE2RjaJtfTm2oDY6knjOeqfhGoLTzMkrQftmIEmFZMvpqk4BrtdirycZUU
+pLl2zMkSEPStAIU3U0yxID3YdGLHZjbUHtVrL0iND6nR+TeErjlzpvJPc1swH8hJsIYN9eiEX4o
XWpXtevg3reqC0225DJEmAPEyWMfN9v77SwwkcOW8/V9DP8spzY+06WTnKKSVlIlufR2HlcjFQVK
bsTWUQxGk5Ns7D3L472VR92bJOPG7ATY7xUoxGcjPl5wpLuKUKql7oCEAQiDD80f2fAQ2mgVXr1S
n1sDk5OH+wQ7egcZJarpxE2IAQ3Xp9NcJBg2Qpty/F205Yrh1yXcGYyRcNfNYtvLilI9N8Pvwr7H
UcghVA2Q0cf2fz1sZ/rwnnDa7tQ/AQYALkevFw0KZW5kc3RyZWFtDWVuZG9iag0yOSAwIG9iajw8
L0xlbmd0aCA3MTUvRmlsdGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0NCkiJdFXBbtswDL3nK3iUhtmz
ZMdxjkO6S4GuXeGeth7SOE0NuLahKi3Srx8pUkk8ZCdJJvn4SL4w9fWs/jLL0szYHOrNLKFrVUD9
MfutNjpZpEYN2hbpXDm35febNgaPUWcnY9+0/Y6voBM8C/XcaWvVmmN2wRnafurjyeUl2AQc7rfa
LNJcjYML1uj61NLLv+plWkXUUVCFEcgpUCE81Y/19SyxqTXLOSSGz/oKazZZXnKhEvBH68QUJsME
d5o4SJrmGyFFYm/olOMpT/culybVSYl0A9sanQiHawvUI8kj2zXH9VyEoHB9oz8I0HMrhq6RL/5F
Aj1McL2LgPLllapJS87uQzek0AZT5pHqejJV+GQQ8XQy31j0V20qjDlyb5jDrh9cbANESXBd8buI
KU7Xh7ihh4+XbewDTerSoFCc1Umcy6M4SywOk82l4lJ5t98QWKUCPJHYMdVKgVgGpFVKb1hBperY
+RAep8gbUkGlVnzA6LSt0oUa/BCxOulh+6oNtXTstmyJ+PLsPYOumbS82qFPqZ9LBbU2RRBLSZ0n
H0GmxltEEFafbBRYGJ6PohAH6QSIbqqTbhoBHqljcu+b6M8+OA/hdonLPpIR6CZM7P/749deRru/
9OOG7bn+vWvPBCpijGqTFXASnWh2M5HWEIBcw/LDfRQW0AHexftSBtxI0EUiO15HxwVG47bK6ZxG
HX9NkIEfIF/KYslTW+RLwAVDB8s1z+bcAJxqnoa5clrcZvc/+Nvd7b0u5shAfEhsiSGXlbYZqoxE
Z9UVcjEokAdNQwkLLsCFVljVdfC05WtkveNZSb5erG7Nb6yQ4MTawNMB1tP4m+8rWA0M0ns3dBwR
zS0/cWihhQiYsLADCH3e8DUWzH1bRI9xFEbN2X8AIeL0FAjLnu/BbzMh3nK693+Kvv35ELSST7Vi
j1qhNfkIfwUYAIsnja8NCmVuZHN0cmVhbQ1lbmRvYmoNMzAgMCBvYmo8PC9UeXBlL0ZvbnQvRW5j
b2RpbmcvV2luQW5zaUVuY29kaW5nL0Jhc2VGb250L1RpbWVzLUJvbGQvRmlyc3RDaGFyIDMyL0xh
c3RDaGFyIDExNy9TdWJ0eXBlL1R5cGUxL0ZvbnREZXNjcmlwdG9yIDM0IDAgUi9XaWR0aHNbMjUw
IDMzMyA1NTUgNTAwIDUwMCAxMDAwIDgzMyAyNzggMzMzIDMzMyA1MDAgNTcwIDI1MCAzMzMgMjUw
IDI3OCA1MDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgMzMzIDMzMyA1NzAg
NTcwIDU3MCA1MDAgOTMwIDcyMiA2NjcgNzIyIDcyMiA2NjcgNjExIDc3OCA3NzggMzg5IDUwMCA3
NzggNjY3IDk0NCA3MjIgNzc4IDYxMSA3NzggNzIyIDU1NiA2NjcgNzIyIDcyMiAxMDAwIDcyMiA3
MjIgNjY3IDMzMyAyNzggMzMzIDU4MSA1MDAgMzMzIDUwMCA1NTYgNDQ0IDU1NiA0NDQgMzMzIDUw
MCA1NTYgMjc4IDMzMyA1NTYgMjc4IDgzMyA1NTYgNTAwIDU1NiA1NTYgNDQ0IDM4OSAzMzMgNTU2
XT4+DWVuZG9iag0zMSAwIG9iajw8L0xlbmd0aCA1NzcvRmlsdGVyL0ZsYXRlRGVjb2RlPj5zdHJl
YW0NCkiJzJPNjhMxDMfv8xQ+JocJifMxkyuUSqwWAdXABXHodqcwotuWtqMVLwKvi5N4FnrYSghp
hSrVcRLbP/+d6a4qDbVRaKKHblbVWmntLXSrilZoA3T31UdxlHVQXoyyNg3Z1RdeAB9M/nIja9Ri
AzcyqCh68pxqBEgyTtzJ2qJCsZRUxooDBVnViq8c3N9OWe9p4cUgU9ApZ3woWDItzxNPXFu2JXLF
l7gco5Z8HFic7xy2n0BKAOxyE2vGhOvrV7ycZT4lP3VX1bO5BQPduorKBh/BknUmi5m0bAxrqRvW
spO+UYaokP5vZEuVSLVGBdEzVSAqpG33A39mJCsWL2XdUuW30ni6+Ya2I7mLLsfDa2l0Ps2XXrCd
vYdFv883dhQQxOEEpeBQCp4k2jwVnWQqN2E9SBMoumeq27x95GZdaZbSt6DplxeotQoOXCS9gm6g
u0sdG3QPvcfS+/MhDSEm3T02gd7CXGJC3ZR9GpUhVT5L9OTBfJCoySeUbOmBNAFTpx9k6xMzH4z9
xIeFr0bVYGyArLHe8DSMC4koPXI0riBpyumjpbG/y+Me+zEhUVGgI9doQxpombCghm9jLzFxj3QM
B9KPtMnvJYr9jn2SNY0PaIxp0kNxj6k3ekbb3XS+P3CyI9vtKXdB8qMJmL7LM3j3Gx4LvJmQfCZn
pAREnzQDZZwzmISSHh8B5NtHTsDl6z/qR9PGC+KZx8Uzl8UzTyGebv9GPPPE4uHj4uFl8fD/e3n4
z+LBLwEGAGe+cAQNCmVuZHN0cmVhbQ1lbmRvYmoNMzIgMCBvYmo8PC9MZW5ndGggMjc1L0ZpbHRl
ci9GbGF0ZURlY29kZT4+c3RyZWFtDQpIicySuWrEMBCGez3FlJpCQqPT6hMC7gLqQqrgIin28pp9
/YzX2hyFDQuLcSGk0fHr04dKKxRFbSlaUKQzNRnKkzDakI9QPoTioSUP5SLepEOVQnY6yFeMOsuh
G9A2mmQHvOSTIR2lQeIZUHAcOrSczdvAwQmt0052yIlZHva1PqO13AEqm/jY51T2yDCNhN3+tn44
1bC+9rszvpdW/IEn09APvP+FtxM83ZDClbwijUDEcRPQFecfzIhix/ccpt19DajX3yHPz8vzy/L8
GvJcuEeeX1lemJcXluWF7ckLj5bXZFqSF+flxWV5cXvy4so/L83LS8vy0vbkpUfIey7CwAu3Fgx8
ASfBBeBbgAEAgOhn0A0KZW5kc3RyZWFtDWVuZG9iag0zMyAwIG9iajw8L0xlbmd0aCAxODMvRmls
dGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0NCkiJXJA7DgMhDAV7TuETWLYxv0OkiLaM0qWJlNS5fkDg
BbbD84ZnBBPc4PEkeDmGNzhOhEFAkmCIDF8DgTKKMnzc4aie4AdOVFBrUlC1qX2WxOhjMz3rlvd5
5odjlFZUY0zr0gHmUo4FSwdZuyFI+QSnoTnVm4thYH24uZGwxNUdYLZ5v+8zMA2Kl44BTsOnsncY
mEaQvcPANCRcOgY4DSl57zCwfLOpifcvMtDUu4O/AAMAUV5nPQ0KZW5kc3RyZWFtDWVuZG9iag0z
NCAwIG9iajw8L1R5cGUvRm9udERlc2NyaXB0b3IvRm9udEJCb3hbLTE2OCAtMjE4IDEwMDAgOTM1
XS9Gb250TmFtZS9UaW1lcy1Cb2xkL0ZsYWdzIDI2MjE3OC9TdGVtViAxMzkvU3RlbUggMTM5L0Nh
cEhlaWdodCA2NzYvWEhlaWdodCA0NjEvQXNjZW50IDY5OS9EZXNjZW50IC0yMDUvSXRhbGljQW5n
bGUgMD4+DWVuZG9iag0xIDAgb2JqPDwvQ29udGVudHMgMyAwIFIvVHlwZS9QYWdlL1BhcmVudCAx
MCAwIFIvUm90YXRlIDAvTWVkaWFCb3hbMCAwIDYxMiA3OTJdL0Nyb3BCb3hbMCAwIDYxMiA3OTJd
L1Jlc291cmNlcyAyIDAgUj4+DWVuZG9iag0yIDAgb2JqPDwvRm9udDw8L0YxIDE4IDAgUi9GMiAx
OSAwIFIvRjMgMjAgMCBSL0Y1IDYgMCBSL0Y2IDcgMCBSPj4vUHJvY1NldFsvUERGL1RleHRdL0V4
dEdTdGF0ZTw8L0dTMSAyNCAwIFI+Pj4+DWVuZG9iag0zIDAgb2JqPDwvTGVuZ3RoIDM3MjIvRmls
dGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0NCkiJfFfNbhw5Dr73UwjYS9Viq6x/VS0wB8duJx7EceLu
wR6yg4Fjt50e2G5Pu51gXmT3GfYtl6QoldSxB0HcJYoiP/6IpP6YHVys7i5362+ro83dZru+X+22
6yuxXYvZwduFErdPszfL2cGJEkosb2ahH7WQ8I8+nNT9IIKTvbcyiOX9TIrbWSd7KZUXyytYLr/P
Pjen8/m87YzqfSPaX5c/zzqne221FZ3qlVNOLI9neMoZPPW5OVq0DpjP2k7JXjeHtDpoYeGbo1Y2
xyTF+t4FNwAaOI5alXSkFSXpqBoEyd42u7ZzIOgaUMjeNGLgDwnCNH/3kcdc8vpr13YW8DVaJm4b
0SfF3TD0wQWf4MsB1ZP9XkX9R5tWKTj6CKaMzZ+t8s12jd9gyW3c+kpbu9aDKvE/2hsaoYkqI4uk
hY0LwWhO6QS5Vo8AvI8SDu9Y/B36KzTir/Q9IaAkcLuKDE/AYMFpvNx+y2s8eB2pPbni4ETHxADM
lhKDPpx0mB9m6J3nxIDoaJ1zorE+tMvf4byJ5zsLGeEHWEFKORNyRuSIjhxRbyFQaK/pW4UB82C/
6ceGl0bwxwXQBzB7Tllkm7ewVvB7GrcXTF6CI0JmuvhtOqZs84nPiFajByB/VIC91dMVehVRPNLx
HeQREzZEeKjdI0Wne2tGNkupwGYZzpNlC4aPGBvZO/R0wNBdzCP57emCpC5BP8JhMoLVeEHmTP8k
zj4S41H8Of4F8GvEv27JDgwt+kpcQuAJJumDDCD7mIupT5hADu+OaWr+HTNeRpy7uFpvHsTmRvBq
z5S3/PHQUrB4tWVBV8y1D/8fbeexalxWh6/38DLQRL15jmzb3ddVhL0V16zwJpnIO1kUn0kOqj1x
S9GUVK4wizmI+bqrMMYwku0u2m6jkYD+ZnMX6Xeb7+v49XDLkDxDAtKaT4MfId0YytD8k5SrXmob
C6ZWlEefo/tt8+8WL6jCUnX+eNWq0GyibIt3YsCiEBNHRWAab3bI7tpgbmMi09ZVPLiJq+u4x9LA
kK0gp06nKQMdZ6CiTMU8BeQ6Ey9+i2IuEoHylMKMQa6iGdhucJuUXauh0UDd7acAgPWpX6SKUtTb
L+QM4zVoOWkDKIVyqAEgJDCubuGiRgXonI4qZrzbS6oAeAUjGEgqxfcG0wIXLOMBZEAHITbxhTl2
LObmLmliwpacB+tS1C6CWkXWbWsw+XeR4SuIv4xnmJJQPFzzx1XcZk07FpPsYsWk6BGE8TYfWvOp
uwkfrf94Xm9bjdnCgO/bEVDxAm3elb6AVIjcJWxm3recPRptLu3fJgvYrk0sm/MlhPot/P8ZGsrv
Aq7SIL4LJcWZ+PyrFNczJWA+0TJgr/HB9kYrcT8zATJhyIS7mfHUjbwde+OJgwmZA2V4YvCyZGDC
XVaSOQqtziPHohqQ6j6osVsAIjeACbkRShdyU0tTShx0Ni127GdqaFC10Cke4+YpV6ibHzLr9fV2
9RR3nmKBgJbrlBY2TUNyDMUMdg5V3EdpMV9X1NWheMfjMrbfzvYymFji8DR0V2jTEJAfHJG8nV2V
fAfB9vZVZ3piGIaSgQmTtzNHoXWwL3IkGFkGC3XjCCPIq1oAhpS9qrKCCZOSzJG1Oqy+Kegvx9rY
OtYmNwkXI/Geyh1cs4fbHY4M0CphtHVQgAzWnz/xSrjmccVs4if4oPY2DJ0cUiGE6zO1ImlTRqkc
bej7XNRNvPoO24L4CcuqNDFlfKymGq6HG3PM44SmMfCVokiacsFAcXblzUuEHAQDDwRX+njiiEFA
hqG8eYmQgzBxFFqDf5EjwcgyWKgOgdLnFS0eGAY4WDAkQlYycWStppf2r3PBwJSWX0bYrnx83ny8
bLHx4zTpocEftBAr01ysiPoUf7YtBv9bG+eIyI4xW/4dRWmcG1HUyVFLNX+xF9Bp1pQYWbjIsjPj
FFLj/XTHbR1XHXSyFSq8ngh3SBDaBroF93E17UVXwm4stonXlMEqtidlXIsLabBtYQivVAPBlsrj
uoCGeVEqyAcYQYFnws66K2Gw64e+ss3jU6bUzoQKnqrUT0dYf4WnNIAx1CKBYYD3RKkCnptjBYIJ
FUwo3oWO6QiDqFFVhjCMWihcCYnts9CCBKULHIlQIQ0ljuII46iBVbZw866Fggx45bpSCxKqfEyE
AimEsYx6cSTi2ANW2cI4aqHAYbGzlFqwwVU4mFAhlWXsiyOMowZW2cI4aqG52hVauHZNOFIxK5Ha
Csd0hHHUwCpbzGutz0B9RawOyk9R7gZqfc3Z4g3Wl07BODlIJ7AXphEDy1MsZO8XWMhc84YKme4D
8GClgnKm4mvni8T5FjoVlMwvgdhMLHf1q4BrI6oxgIr64Rt6Cpy2Aw360FcNVEwaVf/VdnABYMtA
S2iW72I5paVtPuB7pREnF5F6GKlnLf6dEwJA6OU4IITSKOVTPzbckZc0dzl4L3U4NR/ik1WhAlwt
aBYzIBm9pEA9PJNMPrOc8/5xZBfvE+Fk2TqcETucBEc0DYw45xWrOqVnATzN3sX1Ms3YZpBUssAd
nFGJAI89am1IwPsDBB0b6iiJP46+ZlSUGywgbZs0EKbTMNb4RCD5MMnqiqAKhVj1cURljpGqeqGz
VsHbpU4SgKn4sgmDogsOHAkEE5IVNzMEDC+OEo61yUNESLyLfdJ9CSHs28BuqsWCRmzq0GhRpR/J
nDyv0DmT3YX3bNpOBJsvJz+W6GYXVt3vRxtKsDJ092Hq5AErERRPNokA+rjh1Eeivogbt7DkZ2yZ
kN9auFUy8PpH7Flvwk7xHSq3Wx1Lj6LrBjzWQDXI6ztYa4wi1nM9RILE5mjymM8i9Iivs0QwvuLA
GJYygGCHUgvm1d4aJz858pxbaLXyFSWZYBPySsAPdmjCIEcOU3JFJtzMcO5ET1oY4JzOW/eZkAEv
yuNxmi8UMITEMdlAVmcGyt8YO+a1zoEfosZMGPUe3OD3ODx7mdq2HyW/JAvCUHI4mOP1Pod/bSq3
OG0Pwg4QQ8ltKpVpfEDRw+mo7QxO3lRzHdbUBX9gq4hdBIBTbYaEa97hEy5QkbXw+yF2BYUNQVlv
uCEoCAf3JKlY1QlW6QBVGv8eQlPBhjAXS3z/+UT+QD+Ls9MWMg9rN51hnvlxnPpJ2fQYlCG/4qDv
nH8k/Bp7RMAWh5IMvRD9RH3DTOfL5fkZST04MQJ61w01bqMCaMHcdkPqszKE/LQNNtsEYmyzRoC2
ueXlMzTeEZ40HVBHeM5Ae2+Et9TeQvMfo/9LTyFwxhx7lG4+tviUQZCgXDcXSxIg4IClBgzt0QIT
8R7x7/EvqbHx08LzFcujks93juceFyy1pjwITRzxNeOCo7ZxP51w3EdYycRRaLUyp+DBiYpufPGF
6AasfjEX0ZEwQpWxW7cdDGKuuSdPoec6KCfwRoRfjNqOU/OS6cBnMbiP1WuwHLheeu85J6kAZj8l
wuQn7bg2JELmYD8BQygdmQiTnzJHoTW8NlEm9xgHpTFPlDLeIvzC2RJddLHCe9g8brY7TBmYjb6s
KVd2mBQGPUKD0uUPLsm3Mzu8UbVfLI5WsvBLImS/YDvwtjB74oh+QYZhKBmYkP0ycRRah9dKGPvF
GuxLk19cGjflyOPmJ8oY0zyvnlfib0ZcrMhFr/kgzeH/Z71adtsGYuA9X+GjXCDNSqtdSccCRY8F
inxBUjtAAdtp4uTQvy+55PKhKI4D+KgRtVwNX0NOvHBDXa2bVVQ/5DKslREGdpYAt1qoBTOipC5R
5mg3Xkn8nWAko5Y6n5HuQoyk0JaxrLXDwM4SEGwKqAUzoqQuUeZoN17TB7WDY67N5zPSXooRSOhg
q6YCO0tA6F2zqBbcTZTUJcoc7cZr90HVpBblw/mMhEtVDagUN4cqIIzEYfBjRi2IETToLWUVEEbU
wng1c2iRkTiC308wkt5jZMAzPsGItkVmRNqiEEAb4DuNM1tSlyhztIvXoewxJ6um7VhBncdIfyFG
YqpKlhmpgOYIam5bFGrBOQIGbkhXQHNELIzXfvwgR0BpxE/0keFSjGhNMCMM7OYE7OdlJIzw7znK
ettH1GJWRicZyZ2ItnMYyRdiJE+TnzUVEEYy6Fk3a9SCGEEDN2sqIIyohfH60azJY3TTV7cdLMDy
U99JqB3X7QhCldUZSbXDGtX8XXnPKo5ePBbosPqGfKRms3negvJNIHyPJwUuqbnMai5AkuBm2vaw
JaxSX9dcfk6BZw9sUMCVNWBALG5ly8VXfTElTYtnhVEAMrVuI+ynlKv6TOqXvRgDBao+9m7xDSUt
u63AYojagOIBVNXok1ak9CRS+u/27gWpjs12szqsIBapxAKXtn1ZNeDNGi6DCwi042Z1d+RdMfGu
yJG4hgrJaZLszpIPib39fKUT2+Z++1wXu8cHdA8i/um1pAu4gAIqznLxjJlTrlH98nLFbtuvkA6t
ryn8w4F84p+k5rD5U7bNqfmNW2oHmReaFyo5+O/7f+trRFe1+tpYCExRAhQ72BoFgBDG+JUMpkzP
qWiSEh0C6AhJDwRGZzBBAbkjJlqA1Mc4d4pBLwAnUvU68P7w1gk96/seBqQ7Yf4fkS4xcVsVKirw
cNXBAlRSE8ZE7h1LDFTbW8vkQBVWHegNmCi9o/w2WTx80Wog4z6PLCYEmHjOL4ROgN5Gpn6yn39i
rh37UMuOglMBCV+MPr4xhrIeihssVJci1gK5tyeUJLM+4txpCR8CIXin4/iODwGqRckhe8SbHyn8
I5AspQrYFEiC7+lJLutYpPWgHu3uX47W68kvk8VC8DvKFA1+Nys6/LrzFjW56u4wJK80KqAbSwpe
aagFbywpeKVRAXUiFsarURo3PzK1suXVJePFtHsPrTbUzA0VmlqAFva6BjiWfo1t7J4et2tosG3z
DCiEq1lhpx2xgz8VjcL997gt7TXP2+vS8qODtuVB++vqvwADAA9mdBcKDQplbmRzdHJlYW0NZW5k
b2JqDTQgMCBvYmo8PC9UeXBlL0ZvbnREZXNjcmlwdG9yL0ZvbnRCQm94Wy0xNzAgLTIyNSAxMTE2
IDkzMV0vRm9udE5hbWUvSGVsdmV0aWNhLU9ibGlxdWUvRmxhZ3MgOTYvU3RlbVYgODgvU3RlbUgg
ODgvQ2FwSGVpZ2h0IDcxOC9YSGVpZ2h0IDUyMy9Bc2NlbnQgNzE4L0Rlc2NlbnQgLTIwNy9JdGFs
aWNBbmdsZSAtMTI+Pg1lbmRvYmoNNSAwIG9iajw8L1R5cGUvRm9udERlc2NyaXB0b3IvRm9udEJC
b3hbLTEzNiAtMjI1IDgyMCA5MzFdL0ZvbnROYW1lL0hlbHZldGljYS1OYXJyb3cvRmxhZ3MgMzIv
U3RlbVYgODgvU3RlbUggODgvQ2FwSGVpZ2h0IDcxOC9YSGVpZ2h0IDUyMy9Bc2NlbnQgNzE4L0Rl
c2NlbnQgLTIwNy9JdGFsaWNBbmdsZSAwPj4NZW5kb2JqDTYgMCBvYmo8PC9UeXBlL0ZvbnQvRW5j
b2RpbmcvV2luQW5zaUVuY29kaW5nL0Jhc2VGb250L0hlbHZldGljYS1PYmxpcXVlL0ZpcnN0Q2hh
ciAzMi9MYXN0Q2hhciAxMTcvU3VidHlwZS9UeXBlMS9Gb250RGVzY3JpcHRvciA0IDAgUi9XaWR0
aHNbMjc4IDI3OCAzNTUgNTU2IDU1NiA4ODkgNjY3IDE5MSAzMzMgMzMzIDM4OSA1ODQgMjc4IDMz
MyAyNzggMjc4IDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiAyNzggMjc4
IDU4NCA1ODQgNTg0IDU1NiAxMDE1IDY2NyA2NjcgNzIyIDcyMiA2NjcgNjExIDc3OCA3MjIgMjc4
IDUwMCA2NjcgNTU2IDgzMyA3MjIgNzc4IDY2NyA3NzggNzIyIDY2NyA2MTEgNzIyIDY2NyA5NDQg
NjY3IDY2NyA2MTEgMjc4IDI3OCAyNzggNDY5IDU1NiAzMzMgNTU2IDU1NiA1MDAgNTU2IDU1NiAy
NzggNTU2IDU1NiAyMjIgMjIyIDUwMCAyMjIgODMzIDU1NiA1NTYgNTU2IDU1NiAzMzMgNTAwIDI3
OCA1NTZdPj4NZW5kb2JqDTcgMCBvYmo8PC9UeXBlL0ZvbnQvRW5jb2RpbmcvV2luQW5zaUVuY29k
aW5nL0Jhc2VGb250L0hlbHZldGljYS1OYXJyb3cvRmlyc3RDaGFyIDMyL0xhc3RDaGFyIDExNy9T
dWJ0eXBlL1R5cGUxL0ZvbnREZXNjcmlwdG9yIDUgMCBSL1dpZHRoc1syMjggMjI4IDI5MSA0NTYg
NDU2IDcyOSA1NDcgMTU3IDI3MyAyNzMgMzE5IDQ3OSAyMjggMjczIDIyOCAyMjggNDU2IDQ1NiA0
NTYgNDU2IDQ1NiA0NTYgNDU2IDQ1NiA0NTYgNDU2IDIyOCAyMjggNDc5IDQ3OSA0NzkgNDU2IDgz
MiA1NDcgNTQ3IDU5MiA1OTIgNTQ3IDUwMSA2MzggNTkyIDIyOCA0MTAgNTQ3IDQ1NiA2ODMgNTky
IDYzOCA1NDcgNjM4IDU5MiA1NDcgNTAxIDU5MiA1NDcgNzc0IDU0NyA1NDcgNTAxIDIyOCAyMjgg
MjI4IDM4NSA0NTYgMjczIDQ1NiA0NTYgNDEwIDQ1NiA0NTYgMjI4IDQ1NiA0NTYgMTgyIDE4MiA0
MTAgMTgyIDY4MyA0NTYgNDU2IDQ1NiA0NTYgMjczIDQxMCAyMjggNDU2XT4+DWVuZG9iag04IDAg
b2JqPDwvTnVtc1swIDkgMCBSXT4+DWVuZG9iag05IDAgb2JqPDwvUy9EPj4NZW5kb2JqDTEwIDAg
b2JqPDwvQ291bnQgMi9LaWRzWzE2IDAgUiAxIDAgUl0vVHlwZS9QYWdlcz4+DWVuZG9iag0xMSAw
IG9iajw8L0xlbmd0aCAzMzI1L1R5cGUvTWV0YWRhdGEvU3VidHlwZS9YTUw+PnN0cmVhbQ0KPD94
cGFja2V0IGJlZ2luPSfvu78nIGlkPSdXNU0wTXBDZWhpSHpyZVN6TlRjemtjOWQnPz4KPD9hZG9i
ZS14YXAtZmlsdGVycyBlc2M9IkNSTEYiPz4NCjx4OnhtcG1ldGEgeG1sbnM6eD0nYWRvYmU6bnM6
bWV0YS8nIHg6eG1wdGs9J1hNUCB0b29sa2l0IDIuOS4xLTEzLCBmcmFtZXdvcmsgMS42Jz4NCjxy
ZGY6UkRGIHhtbG5zOnJkZj0naHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4
LW5zIycgeG1sbnM6aVg9J2h0dHA6Ly9ucy5hZG9iZS5jb20vaVgvMS4wLyc+DQo8cmRmOkRlc2Ny
aXB0aW9uIHJkZjphYm91dD0ndXVpZDpkODM1ZWM0YS0zZTdlLTRhZjUtYTRjNy0wODA1YTgzZmNi
NjEnIHhtbG5zOnBkZj0naHR0cDovL25zLmFkb2JlLmNvbS9wZGYvMS4zLycgcGRmOlByb2R1Y2Vy
PSdBY3JvYmF0IERpc3RpbGxlciA2LjAuMSAoV2luZG93cyknPjwvcmRmOkRlc2NyaXB0aW9uPg0K
PHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9J3V1aWQ6ZDgzNWVjNGEtM2U3ZS00YWY1LWE0Yzct
MDgwNWE4M2ZjYjYxJyB4bWxuczp4YXA9J2h0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8nIHhh
cDpDcmVhdGVEYXRlPScyMDA1LTAxLTA0VDE3OjA4OjM5LTA4OjAwJyB4YXA6Q3JlYXRvclRvb2w9
J1BTY3JpcHQ1LmRsbCBWZXJzaW9uIDUuMi4yJyB4YXA6TW9kaWZ5RGF0ZT0nMjAwNS0wMS0wNFQx
NzowODozOS0wODowMCc+PC9yZGY6RGVzY3JpcHRpb24+DQo8cmRmOkRlc2NyaXB0aW9uIHJkZjph
Ym91dD0ndXVpZDpkODM1ZWM0YS0zZTdlLTRhZjUtYTRjNy0wODA1YTgzZmNiNjEnIHhtbG5zOnhh
cE1NPSdodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvbW0vJyB4YXBNTTpEb2N1bWVudElEPSd1
dWlkOmI0NWI2NDQ0LWQ1NDUtNDcwYi1iNWUxLWE3NDNiMWJiMTI5MicvPg0KPHJkZjpEZXNjcmlw
dGlvbiByZGY6YWJvdXQ9J3V1aWQ6ZDgzNWVjNGEtM2U3ZS00YWY1LWE0YzctMDgwNWE4M2ZjYjYx
JyB4bWxuczpkYz0naHR0cDovL3B1cmwub3JnL2RjL2VsZW1lbnRzLzEuMS8nIGRjOmZvcm1hdD0n
YXBwbGljYXRpb24vcGRmJz48ZGM6Y3JlYXRvcj48cmRmOlNlcT48cmRmOmxpPmdsZW5rPC9yZGY6
bGk+PC9yZGY6U2VxPjwvZGM6Y3JlYXRvcj48ZGM6dGl0bGU+PHJkZjpBbHQ+PHJkZjpsaSB4bWw6
bGFuZz0neC1kZWZhdWx0Jz44MDIuM2FoLTIwMDR1cGRhdGUucGRmPC9yZGY6bGk+PC9yZGY6QWx0
PjwvZGM6dGl0bGU+PC9yZGY6RGVzY3JpcHRpb24+DQo8L3JkZjpSREY+DQo8L3g6eG1wbWV0YT4N
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAKPD94
cGFja2V0IGVuZD0ndyc/Pg0KZW5kc3RyZWFtDWVuZG9iag0xMiAwIG9iajw8L01vZERhdGUoRDoy
MDA1MDEwNDE3MDgzOS0wOCcwMCcpL0NyZWF0aW9uRGF0ZShEOjIwMDUwMTA0MTcwODM5LTA4JzAw
JykvVGl0bGUoODAyLjNhaC0yMDA0dXBkYXRlLnBkZikvQ3JlYXRvcihQU2NyaXB0NS5kbGwgVmVy
c2lvbiA1LjIuMikvUHJvZHVjZXIoQWNyb2JhdCBEaXN0aWxsZXIgNi4wLjEgXChXaW5kb3dzXCkp
L0F1dGhvcihnbGVuayk+Pg1lbmRvYmoNeHJlZg0KMCAxMw0KMDAwMDAwMDAwMCA2NTUzNSBmDQow
MDAwMDA5NzA0IDAwMDAwIG4NCjAwMDAwMDk4MzAgMDAwMDAgbg0KMDAwMDAwOTk1MCAwMDAwMCBu
DQowMDAwMDEzNzQxIDAwMDAwIG4NCjAwMDAwMTM5MjkgMDAwMDAgbg0KMDAwMDAxNDExMyAwMDAw
MCBuDQowMDAwMDE0NjA4IDAwMDAwIG4NCjAwMDAwMTUxMDEgMDAwMDAgbg0KMDAwMDAxNTEzNCAw
MDAwMCBuDQowMDAwMDE1MTU3IDAwMDAwIG4NCjAwMDAwMTUyMTUgMDAwMDAgbg0KMDAwMDAxODYx
NyAwMDAwMCBuDQp0cmFpbGVyDQo8PC9TaXplIDEzPj4NCnN0YXJ0eHJlZg0KMTE2DQolJUVPRg0K

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

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

------=_NextPart_000_0088_01C4F282.4C7D0AF0--





From hubmib-bounces@ietf.org  Tue Jan  4 20:44:08 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11977
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 20:44:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm0BX-0001aN-RJ; Tue, 04 Jan 2005 20:42:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm07Q-0000IS-NA
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 20:37:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11725
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 20:37:46 -0500 (EST)
Message-Id: <200501050137.UAA11725@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cm0Jt-0005ne-GI
	for hubmib@ietf.org; Tue, 04 Jan 2005 20:50:42 -0500
Received: (qmail 26813 invoked by alias); 5 Jan 2005 01:37:37 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 5 Jan 2005 01:37:37 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 4 Jan 2005 17:37:28 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <02c701c4f041$12ab1940$2b0b0b0b@passave.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTwQhmGIkD84Vy/QIuQf8QXhBYpAgCg1PBQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[GK] The following objects represent non-EPON-specific events and should be
moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl

[LK] As a general concept we tried to create in the EFM MIB objects a
reflection of the IEEE802.3ah management object keeping as much as we can
aligned to clause 30. There is here an additional section which refers to
device MIB objects. In there I tried to put all things which are necessary
for the management of an EPON device (in an access network) and was not
truly covered by the IEEE802.3ah spec as being a spec for L2 MAC mainly. So
although they are OAM they are in device level.

[GK] Lior, any network device is a combination of multiple specs. And
correspondingly, management of a network device comprises many MIBs. EPON
MIB should only cover EPON-specific objects. There exist many other MIBs
that are not EPON-specific, but that must be implemented in EPON devices.
Such objects as eponDeviceDyingGaspAlarmEnabled and
eponDeviceTemperatureEventIndicationState (and all other objects listed
above) are not EPON-specific. They exist in other MIBs.
What I am trying to say is that EPON MIB will not be used as substitution
for other MIBs. It is to be used in EPON devices in addition to other MIBs. 

Regards,
Glen




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


From hubmib-bounces@ietf.org  Tue Jan  4 21:50:20 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16385
	for <hubmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 21:50:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm15m-0002s3-9M; Tue, 04 Jan 2005 21:40:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm12K-0001mw-3P
	for hubmib@megatron.ietf.org; Tue, 04 Jan 2005 21:36:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15346
	for <hubmib@ietf.org>; Tue, 4 Jan 2005 21:36:34 -0500 (EST)
Received: from mta9.srv.hcvlny.cv.net ([167.206.5.42])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cm1Em-0006uG-9d
	for hubmib@ietf.org; Tue, 04 Jan 2005 21:49:30 -0500
Received: from Nadia (ool-44c6903d.dyn.optonline.net [68.198.144.61])
	by mta9.srv.hcvlny.cv.net
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with SMTP id <0I9T006N3OJ6RT@mta9.srv.hcvlny.cv.net> for
	hubmib@ietf.org; Tue, 04 Jan 2005 21:35:31 -0500 (EST)
Date: Tue, 04 Jan 2005 21:35:31 -0500
From: prarch <prarch@optonline.net>
Subject: Re: [Hubmib] FW: EPON MIB comments (eponDeviceObjectPowerDown)
To: glen.kramer@teknovus.com, "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, hubmib@ietf.org
Message-id: <054d01c4f2cf$39d4b590$3d90c644@Nadia>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <200501050034.TAA07869@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7BIT
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

A new start up company located in New York, NY in VoIP/Telephony software 
space is looking for software architects and developers.



  1.. Network Management Software product architects
  2.. SNMP/MIB architects and developers
  3.. Voice application product architects
  4.. Voice protocol architects and developers
  5.. Application GUI architects and developers
  6.. Technical marketing and product engineering
  7.. Sales engineers




Please send your resume to prarch@optonline.net

----- Original Message ----- 
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>; "'Romascanu, Dan (Dan)'" 
<dromasca@avaya.com>; <hubmib@ietf.org>
Sent: Tuesday, January 04, 2005 7:34 PM
Subject: RE: [Hubmib] FW: EPON MIB comments (eponDeviceObjectPowerDown)


> [GK] eponDeviceObjectPowerDown - "Setting this variable to True(1) will
> cause Device to be entered into Power down mode where no registration is
> allowed and only receiving data from the link.". This object does not make
> sense. Setting it to True will cause the device lose the link (because no
> transmission is allowed leading to MPCP timeout) and never register again
> (because registration is not allowed).
>
> [LK] I guess the question is what is the meaning of power down. I thought 
> of
> a condition where the device is in minimal power mode where it is not
> transmitting and it is in listening mode so it can be enabled by 
> activation
> according to MAC address. Keeping it registered can be done easily by
> reducing its SLA to minimal BW but I don't think it is a power down mode.
> Keeping it in listening mode will really make it possible for the system 
> to
> reduce power (notice I do not define what is exactly this mode as it can 
> be
> implemented as the vendor wishes) yet have the minimal capability to wake
> up.
>
> [GK] This is very suspiciously seems like fitting of MIB spec to a 
> specific
> proprietary implementation. Even if device is not transmitting any user
> data, it should periodically transmit MPCP and OAM messages.
> You are trying to define some kind of standby mode without clear 
> explanation
> what this mode is or how it can be implemented. I argue that because MPCP
> relies on periodic messages, this mode is not possible without breaking 
> IEEE
> 802.3ah standard.
> "Keeping it registered can be done easily by reducing its SLA to minimal
> BW..." This is a particular implementation. Device registration has 
> nothing
> to do with the provisioned SLA. There is a very formal state machine that
> explains steps of EPON device registration.
>
>
>
> _______________________________________________
> 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  Wed Jan  5 01:27:25 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00677
	for <hubmib-archive@lists.ietf.org>; Wed, 5 Jan 2005 01:27:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm4cA-0008SE-VN; Wed, 05 Jan 2005 01:25:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm4ZD-0007cS-Mw
	for hubmib@megatron.ietf.org; Wed, 05 Jan 2005 01:22:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00487
	for <hubmib@ietf.org>; Wed, 5 Jan 2005 01:22:46 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cm4lf-0003EL-J3
	for hubmib@ietf.org; Wed, 05 Jan 2005 01:35:43 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	0-1607845815; Wed,  5 Jan 2005 01:17:05 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpOnTime and
	dot3MpcpOffTime)
Date: Wed, 5 Jan 2005 08:16:26 +0200
Message-ID: <04e101c4f2ee$1d4536b0$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d49da3f50144c227c0d2fac65d3953e6
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] As opposed to other constants in the MPCP the switching time
parameter has a meaning in management perspective as to BW management.
It defines the efficiency of the link and therefore is in interest to
the entire network. That is the reason why I considered that there is a
sense in defining these attributes.


-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Tuesday, January 04, 2005 9:23 PM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpOnTime and
dot3MpcpOffTime)


[GK] dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the
description that these objects refer to laser_on and laser_off times.
Also, according to the 802.3ah, these times are constant and fixed at 32
TQ. These objects are not necessary.  Correspondingly, 802.3ah did not
find it necessary to specify such attributes in clause 30.

[LK] My believe is that the management entity as a general requires the
knowledge of the PON switching time and does not need to find parameters
in the spec to complete the picture as it is may be probably part of a
more general access system. I think the MIB objects should supply a
visibility of the system major parameters although some are fixed. I can
add the description of 32TQs value to align with the MPCP.

[GK] There is a large number of constants specified in MPCP spec.
Laser-on and laser-off constants are not more important that other
parameters. Why would you choose to define MIB objects for some
constants and not other? 
If the management entity does not know what "PON switching time" is, it
cannot query dot3MpcpOnTime and dot3MpcpOffTime objects. If the
management is EPON-specific enough to understand that there exists "PON
switching time", it already knows that this is a constant equal 32 TQ. 

Regards,
Glen


> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Lior khermosh
> Sent: Saturday, January 01, 2005 12:33 PM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Cc: 'Glen Kramer'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> Thank you very much for the comments and for the time you invested in 
> reviewing the document. I appreciate it very much.
> 
> 
> 1. Thanks
> 
> 2. I believe it is useful to have also a configuration possibility for

> this parameter. As a guideline I believe management should have access

> to define main modes of the system. Can you please specify why do you 
> think writing such a parameter is not useful? If we want to be 
> strictly following clause 30 I can add change the attribute in the 
> device MIBs objects to read-write but I would rather have it following

> the configuration from the EFM MIB objects.
> 
> 3. Agreed
> 
> 4. My believe is that the management entity as a general requires the 
> knowledge of the PON switching time and does not need to find 
> parameters in the spec to complete the picture as it is may be 
> probably part of a more general access system. I think the MIB objects

> should supply a visibility of the system major parameters although 
> some are fixed. I can add the description of 32TQs value to align with

> the MPCP.
> 
> 5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode 
> frames which are not of PAUSE or used by the MPCP protocol. I will 
> clear the description.
> 
> 6. Agreed
> 
> 7+8. If we can see the forwarding rules of the ONU in clause 65 then 
> 7+there is a behavior for frames with bit broadcast in the LLID where 
> 7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is

> 7+not the ONU's LLID (frame is accepted) as part of the point to point

> 7+emulation peer to peer capabilities. This counter counts the first 
> 7+frame. I have sent in the past comments regarding that to clause 30.

> 7+The result was  OnuPonCastLLID and OltPonCastLLID which I think 
> 7+their definition is too vague and refers to a long list of 
> 7+forwarding rules.
> 
> 7+A solution for alignment is to make a request to change in the 
> 7+definition of these attributes in the spec and then unify these 
> 7+counters in them.
> 
> 9. As a general logical deductive comment you have here a very good 
> comment. The problem comes when in devices a reset process can be a 
> very long process where many different sub-systems are reset. In such 
> a scenario there is a meaning for being in a reset process. Therefore 
> I believe that this is an attribute which is needed for a device. I am

> open here for suggestions.
> 
> 10. Thanks.
> 
> 11. Changing this variable might indeed cause very major changes in 
> the system. Yet in my opinion it is needed for management. 
> Unfortunately in true life engineered systems there is a possibility 
> that a system is not operating well and it is needed to make it 
> inactive immediately. The purpose of such an attribute is like this.
> 
> 12. I guess the question is what is the meaning of power down. I 
> thought of a condition where the device is in minimal power mode where

> it is not transmitting and it is in listening mode so it can be 
> enabled by activation according to MAC address. Keeping it registered 
> can be done easily by reducing its SLA to minimal BW but I don't think

> it  is a power down mode. Keeping it in listening mode will really 
> make it possible for the system to reduce power (notice I do not 
> define what is exactly this mode as it can be implemented as the 
> vendor wishes) yet have the minimal capability to wake up.
> 
> 13. O.K. Would you consider such an object definition instead: I think

> it covers multiple thresholds. eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }
> 
> 14. The OLT and ONUs of an EPON device serves as a distributed virtual

> switch where the LLIDs represent bridge ports. This model is behind 
> the point to point emulation mechanism of clause 65 and of the whole 
> LLID concept. A bridge have a MAC address to port address table and 
> this table here serves for exactly the same purpose. It is not a 
> proprietary implementation. The eponDeviceRemoteMACAddressLLIDControl 
> is a control attribute for resetting this Table. As a table is a 
> manageable entity I think such an object is needed. The 
> useDefaultReporting(3) category is a common option for such attributes

> as a default setting for tables - Implementation is according to 
> Vendors preference. I have no special suggestion for the default 
> value. If people will feel more comfortable I can remove 
> useDefaultReporting(3) and return in the reading none(1).
> 
> 15. The report message in the MPCP refers to such entities. Please see

> section 64.3.6.2 for report message format. These counters refer to 
> that.
> 
> 16. As a general concept we tried to create in the EFM MIB objects a 
> reflection of the IEEE802.3ah management object keeping as much as we 
> can aligned to clause 30. There is here an additional section which 
> refers to device MIB objects. In there I tried to put all things which

> are necessary for the management of an EPON device (in an access
> network) and was not truly covered by the IEEE802.3ah spec as being a 
> spec for L2 MAC mainly. So although they are OAM they are in device 
> level.
> 
> 
> Best regards,
> Lior
> 
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Romascanu, Dan (Dan)
> Sent: Sunday, December 19, 2004 4:22 PM
> To: hubmib@ietf.org
> Cc: Glen Kramer
> Subject: [Hubmib] FW: EPON MIB comments
> 
> 
> Although these comments from one of the 802.3ae contributors came in 
> after the WG Last Call deadline, I suggest that we enter them as Last 
> Call comments and address them accordingly.
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 16 December, 2004 9:49 PM
> To: Romascanu, Dan (Dan)
> Subject: EPON MIB comments
> 
> 
> Dan,
> 
> I finally read the EPON MIB document. Below are my comments. I am not 
> sure if it is too late to make use of these, or not. Plsease, feel 
> free to post these on the reflector.
> 
> Regards,
> Glen
> 
> 
> 1. In tables in section 7, object names that are split across lines 
> lost a letter.
> 
> 2. dot3MpcpMode object should be read-only as is its counterpart in 
> 802.3ah (aMPCPMode attribute).
> 
> 3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly

> to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The 
> ONUs are not aware of the round-trip times to the OLT.
> 
> 4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the 
> description that these objects refer to laser_on and laser_off times. 
> Also, according to the 802.3ah, these times are constant and fixed at 
> 32 TQ. These objects are not necessary.  Correspondingly, 802.3ah did 
> not find it necessary to specify such attributes in clause 30.
> 
> 5. dot3MpcpRxNotSupportedMpcp.  The description of this object does 
> not make sense. If a frame is not supported, it is not an MPCP frame. 
> Conversely, there exist no unsupported MPCP frames. There is no 
> matching attribute in clause 30 in 802.3ah and this object should be 
> removed from this draft as well.
> 
> 6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but

> optional at the ONU. It is not optional per 802.3ah and is relevant 
> for both devices. (For comparison, the dot3OmpEmulationCRC8Errors is 
> mandatory in the OLT and ONUs).
> 
> 7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the 
> phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. 
> Should it simply say "broadcast or unicast LLID"?  Also, there is no 
> relevant attribute in clause 30 in 802.3ah.
> 
> 8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,

> as the dot3OmpEmulationBadLLID will count the same frames. I recommend

> removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.
> 
> 9. The access to eponDeviceObjectReset object should be write-only. If

> device is being reset, it cannot generate "reset" response. When the 
> device can generate the response, it will be running already. Thus, 
> the only possible response is "running".
> 
> 10. The object eponDeviceObjectOamMode is not necessary. To get the 
> OAM mode, the management agent would access OAM MIB. No need to 
> duplicate objects in different MIBs.
> 
> 11. eponDeviceObjectDeviceReadyMode object should be read-only. 
> Modifying device mode through the management may have unpredictable 
> results (like taking down entire EPON).
> 
> 12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will

> cause Device to be entered into Power down mode where no registration 
> is allowed and only receiving data from the link.". This object does 
> not make sense. Setting it to True will cause the device lose the link

> (because no transmission is allowed leading to MPCP timeout) and never

> register again (because registration is not allowed).
> 
> 13. eponDeviceObjectReportThreshold. The 802.3ah standard does not 
> limit number of thresholds to be used.  This object will only return 
> the first threshold for each queue. What about the rest of thresholds?

> How to read/set them?
> 
> 14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls 
> the resetting of the LLID MAC address log. Setting this object to 
> none(1) has no action resetLog(2) empties the LLID MAC address log. 
> All data is deleted. Setting it to useDefaultReporting(3) returns all 
> entries priorities to their factory-default reporting. Reading this 
> object always returns useDefaultReporting(3)." The description of this

> object seems to match some proprietary EPON device. In the 802.3ah 
> standard, there is no provision of whether to keep LLID MAC address 
> log. It is not clear, what does it mean "returns all entries 
> priorities to their factory-default reporting", since there is no 
> specification for either "entries" or "factory-default reporting". 
> This object should be removed.
> 
> 15. Objects eponDeviceStatTxFramesQueue[0-7], 
> eponDeviceStatRxFramesQueue[0-7], and 
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such 
> as bridge ports. There is no need to duplicate these objects here. 
> Besides, neither 802.3ah nor 802.1D standards require exactly 8 queues

> to be implemented. I recommend removing these objects.
> 
> 16. The following objects represent non-EPON-specific events and 
> should be moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl
> 
> 
> 
> 
> _______________________________________________
> 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


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


From hubmib-bounces@ietf.org  Wed Jan  5 01:28:54 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00777
	for <hubmib-archive@lists.ietf.org>; Wed, 5 Jan 2005 01:28:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm4cD-0008SO-13; Wed, 05 Jan 2005 01:25:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm4ZD-0007cT-OJ
	for hubmib@megatron.ietf.org; Wed, 05 Jan 2005 01:22:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00484
	for <hubmib@ietf.org>; Wed, 5 Jan 2005 01:22:46 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cm4lf-0003EN-KS
	for hubmib@ietf.org; Wed, 05 Jan 2005 01:35:43 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	0-2607845815; Wed,  5 Jan 2005 01:17:11 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpMode)
Date: Wed, 5 Jan 2005 08:16:26 +0200
Message-ID: <04e401c4f2ee$214b0780$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4166dd0e0c668adc975c3d3e0f1bce3b
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] Although I am generally in favor of extending management
flexibilities I am willing to accept this observation regarding the
great difference between an OLT and an ONU and as result the pointless
in a configuration option.
So unless anyone IS planning to make a device which can be an OLT or an
ONU (please shout - objection) I will make it a read only attribute.

-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Tuesday, January 04, 2005 9:04 PM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpMode)


Lior,

I am going to break this large e-mail into separate threads, so it is
easier to follow the discussion per comment. This one is about
dot3MpcpMode.


[GK] dot3MpcpMode object should be read-only as is its counterpart in
802.3ah (aMPCPMode attribute).

[LK] I believe it is useful to have also a configuration possibility for
this parameter. As a guideline I believe management should have access
to define main modes of the system. Can you please specify why do you
think writing such a parameter is not useful? If we want to be strictly
following clause 30 I can add change the attribute in the device MIBs
objects to read-write but I would rather have it following the
configuration from the EFM MIB objects.

[GK] dot3MpcpMode specifies whether the device is an OLT or an ONU.
*ALL* MPCP state machines defined by IEEE 802.3ah are specified either
for the OLT or ONUs. There are no common state machines. It is not
possible to change a configuration parameter and force the OLT to behave
as the ONU or the ONU to behave as the OLT. If in a network, the
management somehow forces the mode change for an EPON device, this will
result in EPON malfunction. In addition, physical layer parameters are
different for these devices: OLT has burst-mode receiver and normal
transmitter and ONUs have normal receiver and burst-mode transmitter. 


Regards,
Glen



> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Lior khermosh
> Sent: Saturday, January 01, 2005 12:33 PM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Cc: 'Glen Kramer'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> Thank you very much for the comments and for the time you invested in 
> reviewing the document. I appreciate it very much.
> 
> 
> 1. Thanks
> 
> 2. I believe it is useful to have also a configuration possibility for

> this parameter. As a guideline I believe management should have access

> to define main modes of the system. Can you please specify why do you 
> think writing such a parameter is not useful? If we want to be 
> strictly following clause 30 I can add change the attribute in the 
> device MIBs objects to read-write but I would rather have it following

> the configuration from the EFM MIB objects.
> 
> 3. Agreed
> 
> 4. My believe is that the management entity as a general requires the 
> knowledge of the PON switching time and does not need to find 
> parameters in the spec to complete the picture as it is may be 
> probably part of a more general access system. I think the MIB objects

> should supply a visibility of the system major parameters although 
> some are fixed. I can add the description of 32TQs value to align with

> the MPCP.
> 
> 5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode 
> frames which are not of PAUSE or used by the MPCP protocol. I will 
> clear the description.
> 
> 6. Agreed
> 
> 7+8. If we can see the forwarding rules of the ONU in clause 65 then 
> 7+there is a behavior for frames with bit broadcast in the LLID where 
> 7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is

> 7+not the ONU's LLID (frame is accepted) as part of the point to point

> 7+emulation peer to peer capabilities. This counter counts the first 
> 7+frame. I have sent in the past comments regarding that to clause 30.

> 7+The result was  OnuPonCastLLID and OltPonCastLLID which I think 
> 7+their definition is too vague and refers to a long list of 
> 7+forwarding rules.
> 
> 7+A solution for alignment is to make a request to change in the 
> 7+definition of these attributes in the spec and then unify these 
> 7+counters in them.
> 
> 9. As a general logical deductive comment you have here a very good 
> comment. The problem comes when in devices a reset process can be a 
> very long process where many different sub-systems are reset. In such 
> a scenario there is a meaning for being in a reset process. Therefore 
> I believe that this is an attribute which is needed for a device. I am

> open here for suggestions.
> 
> 10. Thanks.
> 
> 11. Changing this variable might indeed cause very major changes in 
> the system. Yet in my opinion it is needed for management. 
> Unfortunately in true life engineered systems there is a possibility 
> that a system is not operating well and it is needed to make it 
> inactive immediately. The purpose of such an attribute is like this.
> 
> 12. I guess the question is what is the meaning of power down. I 
> thought of a condition where the device is in minimal power mode where

> it is not transmitting and it is in listening mode so it can be 
> enabled by activation according to MAC address. Keeping it registered 
> can be done easily by reducing its SLA to minimal BW but I don't think

> it  is a power down mode. Keeping it in listening mode will really 
> make it possible for the system to reduce power (notice I do not 
> define what is exactly this mode as it can be implemented as the 
> vendor wishes) yet have the minimal capability to wake up.
> 
> 13. O.K. Would you consider such an object definition instead: I think

> it covers multiple thresholds. eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }
> 
> 14. The OLT and ONUs of an EPON device serves as a distributed virtual

> switch where the LLIDs represent bridge ports. This model is behind 
> the point to point emulation mechanism of clause 65 and of the whole 
> LLID concept. A bridge have a MAC address to port address table and 
> this table here serves for exactly the same purpose. It is not a 
> proprietary implementation. The eponDeviceRemoteMACAddressLLIDControl 
> is a control attribute for resetting this Table. As a table is a 
> manageable entity I think such an object is needed. The 
> useDefaultReporting(3) category is a common option for such attributes

> as a default setting for tables - Implementation is according to 
> Vendors preference. I have no special suggestion for the default 
> value. If people will feel more comfortable I can remove 
> useDefaultReporting(3) and return in the reading none(1).
> 
> 15. The report message in the MPCP refers to such entities. Please see

> section 64.3.6.2 for report message format. These counters refer to 
> that.
> 
> 16. As a general concept we tried to create in the EFM MIB objects a 
> reflection of the IEEE802.3ah management object keeping as much as we 
> can aligned to clause 30. There is here an additional section which 
> refers to device MIB objects. In there I tried to put all things which

> are necessary for the management of an EPON device (in an access
> network) and was not truly covered by the IEEE802.3ah spec as being a 
> spec for L2 MAC mainly. So although they are OAM they are in device 
> level.
> 
> 
> Best regards,
> Lior
> 
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Romascanu, Dan (Dan)
> Sent: Sunday, December 19, 2004 4:22 PM
> To: hubmib@ietf.org
> Cc: Glen Kramer
> Subject: [Hubmib] FW: EPON MIB comments
> 
> 
> Although these comments from one of the 802.3ae contributors came in 
> after the WG Last Call deadline, I suggest that we enter them as Last 
> Call comments and address them accordingly.
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 16 December, 2004 9:49 PM
> To: Romascanu, Dan (Dan)
> Subject: EPON MIB comments
> 
> 
> Dan,
> 
> I finally read the EPON MIB document. Below are my comments. I am not 
> sure if it is too late to make use of these, or not. Plsease, feel 
> free to post these on the reflector.
> 
> Regards,
> Glen
> 
> 
> 1. In tables in section 7, object names that are split across lines 
> lost a letter.
> 
> 2. dot3MpcpMode object should be read-only as is its counterpart in 
> 802.3ah (aMPCPMode attribute).
> 
> 3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly

> to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The 
> ONUs are not aware of the round-trip times to the OLT.
> 
> 4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the 
> description that these objects refer to laser_on and laser_off times. 
> Also, according to the 802.3ah, these times are constant and fixed at 
> 32 TQ. These objects are not necessary.  Correspondingly, 802.3ah did 
> not find it necessary to specify such attributes in clause 30.
> 
> 5. dot3MpcpRxNotSupportedMpcp.  The description of this object does 
> not make sense. If a frame is not supported, it is not an MPCP frame. 
> Conversely, there exist no unsupported MPCP frames. There is no 
> matching attribute in clause 30 in 802.3ah and this object should be 
> removed from this draft as well.
> 
> 6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but

> optional at the ONU. It is not optional per 802.3ah and is relevant 
> for both devices. (For comparison, the dot3OmpEmulationCRC8Errors is 
> mandatory in the OLT and ONUs).
> 
> 7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the 
> phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. 
> Should it simply say "broadcast or unicast LLID"?  Also, there is no 
> relevant attribute in clause 30 in 802.3ah.
> 
> 8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,

> as the dot3OmpEmulationBadLLID will count the same frames. I recommend

> removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.
> 
> 9. The access to eponDeviceObjectReset object should be write-only. If

> device is being reset, it cannot generate "reset" response. When the 
> device can generate the response, it will be running already. Thus, 
> the only possible response is "running".
> 
> 10. The object eponDeviceObjectOamMode is not necessary. To get the 
> OAM mode, the management agent would access OAM MIB. No need to 
> duplicate objects in different MIBs.
> 
> 11. eponDeviceObjectDeviceReadyMode object should be read-only. 
> Modifying device mode through the management may have unpredictable 
> results (like taking down entire EPON).
> 
> 12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will

> cause Device to be entered into Power down mode where no registration 
> is allowed and only receiving data from the link.". This object does 
> not make sense. Setting it to True will cause the device lose the link

> (because no transmission is allowed leading to MPCP timeout) and never

> register again (because registration is not allowed).
> 
> 13. eponDeviceObjectReportThreshold. The 802.3ah standard does not 
> limit number of thresholds to be used.  This object will only return 
> the first threshold for each queue. What about the rest of thresholds?

> How to read/set them?
> 
> 14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls 
> the resetting of the LLID MAC address log. Setting this object to 
> none(1) has no action resetLog(2) empties the LLID MAC address log. 
> All data is deleted. Setting it to useDefaultReporting(3) returns all 
> entries priorities to their factory-default reporting. Reading this 
> object always returns useDefaultReporting(3)." The description of this

> object seems to match some proprietary EPON device. In the 802.3ah 
> standard, there is no provision of whether to keep LLID MAC address 
> log. It is not clear, what does it mean "returns all entries 
> priorities to their factory-default reporting", since there is no 
> specification for either "entries" or "factory-default reporting". 
> This object should be removed.
> 
> 15. Objects eponDeviceStatTxFramesQueue[0-7], 
> eponDeviceStatRxFramesQueue[0-7], and 
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such 
> as bridge ports. There is no need to duplicate these objects here. 
> Besides, neither 802.3ah nor 802.1D standards require exactly 8 queues

> to be implemented. I recommend removing these objects.
> 
> 16. The following objects represent non-EPON-specific events and 
> should be moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl
> 
> 
> 
> 
> _______________________________________________
> 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


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


From hubmib-bounces@ietf.org  Wed Jan  5 01:29:43 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00816
	for <hubmib-archive@lists.ietf.org>; Wed, 5 Jan 2005 01:29:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm4cD-0008ST-Fw; Wed, 05 Jan 2005 01:25:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm4ZD-0007cU-QO
	for hubmib@megatron.ietf.org; Wed, 05 Jan 2005 01:22:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00488
	for <hubmib@ietf.org>; Wed, 5 Jan 2005 01:22:46 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cm4lf-0003EK-Kq
	for hubmib@ietf.org; Wed, 05 Jan 2005 01:35:43 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	0-0607845815; Wed,  5 Jan 2005 01:16:57 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpRxNotSupportedMpcp)
Date: Wed, 5 Jan 2005 08:16:26 +0200
Message-ID: <04e001c4f2ee$1ac1e730$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9c7d7a899dc8f3389bf7ace6f0ad8e29
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] Thanks. The dot3ControlInUnknownOpcodes is the necessary counter.


-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Tuesday, January 04, 2005 9:50 PM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments (dot3MpcpRxNotSupportedMpcp)


[GK] dot3MpcpRxNotSupportedMpcp.  The description of this object does
not make sense. If a frame is not supported, it is not an MPCP frame.
Conversely, there exist no unsupported MPCP frames. There is no matching
attribute in clause 30 in 802.3ah and this object should be removed from
this draft as well.

[LK] dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode
frames which are not of PAUSE or used by the MPCP protocol. I will clear
the description.

[GK] Aha! So it is simply a counter of "not supported MAC Control
opcodes". In this case, this object is not EPON specific, but general
for all Ethernet MIBs. Furthermore, this object already exists
(dot3ControlInUnknownOpcodes) 

Regards,
Glen

> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Lior khermosh
> Sent: Saturday, January 01, 2005 12:33 PM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Cc: 'Glen Kramer'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> Thank you very much for the comments and for the time you invested in 
> reviewing the document. I appreciate it very much.
> 
> 
> 1. Thanks
> 
> 2. I believe it is useful to have also a configuration possibility for

> this parameter. As a guideline I believe management should have access

> to define main modes of the system. Can you please specify why do you 
> think writing such a parameter is not useful? If we want to be 
> strictly following clause 30 I can add change the attribute in the 
> device MIBs objects to read-write but I would rather have it following

> the configuration from the EFM MIB objects.
> 
> 3. Agreed
> 
> 4. My believe is that the management entity as a general requires the 
> knowledge of the PON switching time and does not need to find 
> parameters in the spec to complete the picture as it is may be 
> probably part of a more general access system. I think the MIB objects

> should supply a visibility of the system major parameters although 
> some are fixed. I can add the description of 32TQs value to align with

> the MPCP.
> 
> 5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode 
> frames which are not of PAUSE or used by the MPCP protocol. I will 
> clear the description.
> 
> 6. Agreed
> 
> 7+8. If we can see the forwarding rules of the ONU in clause 65 then 
> 7+there is a behavior for frames with bit broadcast in the LLID where 
> 7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is

> 7+not the ONU's LLID (frame is accepted) as part of the point to point

> 7+emulation peer to peer capabilities. This counter counts the first 
> 7+frame. I have sent in the past comments regarding that to clause 30.

> 7+The result was  OnuPonCastLLID and OltPonCastLLID which I think 
> 7+their definition is too vague and refers to a long list of 
> 7+forwarding rules.
> 
> 7+A solution for alignment is to make a request to change in the 
> 7+definition of these attributes in the spec and then unify these 
> 7+counters in them.
> 
> 9. As a general logical deductive comment you have here a very good 
> comment. The problem comes when in devices a reset process can be a 
> very long process where many different sub-systems are reset. In such 
> a scenario there is a meaning for being in a reset process. Therefore 
> I believe that this is an attribute which is needed for a device. I am

> open here for suggestions.
> 
> 10. Thanks.
> 
> 11. Changing this variable might indeed cause very major changes in 
> the system. Yet in my opinion it is needed for management. 
> Unfortunately in true life engineered systems there is a possibility 
> that a system is not operating well and it is needed to make it 
> inactive immediately. The purpose of such an attribute is like this.
> 
> 12. I guess the question is what is the meaning of power down. I 
> thought of a condition where the device is in minimal power mode where

> it is not transmitting and it is in listening mode so it can be 
> enabled by activation according to MAC address. Keeping it registered 
> can be done easily by reducing its SLA to minimal BW but I don't think

> it  is a power down mode. Keeping it in listening mode will really 
> make it possible for the system to reduce power (notice I do not 
> define what is exactly this mode as it can be implemented as the 
> vendor wishes) yet have the minimal capability to wake up.
> 
> 13. O.K. Would you consider such an object definition instead: I think

> it covers multiple thresholds. eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }
> 
> 14. The OLT and ONUs of an EPON device serves as a distributed virtual

> switch where the LLIDs represent bridge ports. This model is behind 
> the point to point emulation mechanism of clause 65 and of the whole 
> LLID concept. A bridge have a MAC address to port address table and 
> this table here serves for exactly the same purpose. It is not a 
> proprietary implementation. The eponDeviceRemoteMACAddressLLIDControl 
> is a control attribute for resetting this Table. As a table is a 
> manageable entity I think such an object is needed. The 
> useDefaultReporting(3) category is a common option for such attributes

> as a default setting for tables - Implementation is according to 
> Vendors preference. I have no special suggestion for the default 
> value. If people will feel more comfortable I can remove 
> useDefaultReporting(3) and return in the reading none(1).
> 
> 15. The report message in the MPCP refers to such entities. Please see

> section 64.3.6.2 for report message format. These counters refer to 
> that.
> 
> 16. As a general concept we tried to create in the EFM MIB objects a 
> reflection of the IEEE802.3ah management object keeping as much as we 
> can aligned to clause 30. There is here an additional section which 
> refers to device MIB objects. In there I tried to put all things which

> are necessary for the management of an EPON device (in an access
> network) and was not truly covered by the IEEE802.3ah spec as being a 
> spec for L2 MAC mainly. So although they are OAM they are in device 
> level.
> 
> 
> Best regards,
> Lior
> 
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Romascanu, Dan (Dan)
> Sent: Sunday, December 19, 2004 4:22 PM
> To: hubmib@ietf.org
> Cc: Glen Kramer
> Subject: [Hubmib] FW: EPON MIB comments
> 
> 
> Although these comments from one of the 802.3ae contributors came in 
> after the WG Last Call deadline, I suggest that we enter them as Last 
> Call comments and address them accordingly.
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 16 December, 2004 9:49 PM
> To: Romascanu, Dan (Dan)
> Subject: EPON MIB comments
> 
> 
> Dan,
> 
> I finally read the EPON MIB document. Below are my comments. I am not 
> sure if it is too late to make use of these, or not. Plsease, feel 
> free to post these on the reflector.
> 
> Regards,
> Glen
> 
> 
> 1. In tables in section 7, object names that are split across lines 
> lost a letter.
> 
> 2. dot3MpcpMode object should be read-only as is its counterpart in 
> 802.3ah (aMPCPMode attribute).
> 
> 3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly

> to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The 
> ONUs are not aware of the round-trip times to the OLT.
> 
> 4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the 
> description that these objects refer to laser_on and laser_off times. 
> Also, according to the 802.3ah, these times are constant and fixed at 
> 32 TQ. These objects are not necessary.  Correspondingly, 802.3ah did 
> not find it necessary to specify such attributes in clause 30.
> 
> 5. dot3MpcpRxNotSupportedMpcp.  The description of this object does 
> not make sense. If a frame is not supported, it is not an MPCP frame. 
> Conversely, there exist no unsupported MPCP frames. There is no 
> matching attribute in clause 30 in 802.3ah and this object should be 
> removed from this draft as well.
> 
> 6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but

> optional at the ONU. It is not optional per 802.3ah and is relevant 
> for both devices. (For comparison, the dot3OmpEmulationCRC8Errors is 
> mandatory in the OLT and ONUs).
> 
> 7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the 
> phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. 
> Should it simply say "broadcast or unicast LLID"?  Also, there is no 
> relevant attribute in clause 30 in 802.3ah.
> 
> 8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,

> as the dot3OmpEmulationBadLLID will count the same frames. I recommend

> removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.
> 
> 9. The access to eponDeviceObjectReset object should be write-only. If

> device is being reset, it cannot generate "reset" response. When the 
> device can generate the response, it will be running already. Thus, 
> the only possible response is "running".
> 
> 10. The object eponDeviceObjectOamMode is not necessary. To get the 
> OAM mode, the management agent would access OAM MIB. No need to 
> duplicate objects in different MIBs.
> 
> 11. eponDeviceObjectDeviceReadyMode object should be read-only. 
> Modifying device mode through the management may have unpredictable 
> results (like taking down entire EPON).
> 
> 12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will

> cause Device to be entered into Power down mode where no registration 
> is allowed and only receiving data from the link.". This object does 
> not make sense. Setting it to True will cause the device lose the link

> (because no transmission is allowed leading to MPCP timeout) and never

> register again (because registration is not allowed).
> 
> 13. eponDeviceObjectReportThreshold. The 802.3ah standard does not 
> limit number of thresholds to be used.  This object will only return 
> the first threshold for each queue. What about the rest of thresholds?

> How to read/set them?
> 
> 14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls 
> the resetting of the LLID MAC address log. Setting this object to 
> none(1) has no action resetLog(2) empties the LLID MAC address log. 
> All data is deleted. Setting it to useDefaultReporting(3) returns all 
> entries priorities to their factory-default reporting. Reading this 
> object always returns useDefaultReporting(3)." The description of this

> object seems to match some proprietary EPON device. In the 802.3ah 
> standard, there is no provision of whether to keep LLID MAC address 
> log. It is not clear, what does it mean "returns all entries 
> priorities to their factory-default reporting", since there is no 
> specification for either "entries" or "factory-default reporting". 
> This object should be removed.
> 
> 15. Objects eponDeviceStatTxFramesQueue[0-7], 
> eponDeviceStatRxFramesQueue[0-7], and 
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such 
> as bridge ports. There is no need to duplicate these objects here. 
> Besides, neither 802.3ah nor 802.1D standards require exactly 8 queues

> to be implemented. I recommend removing these objects.
> 
> 16. The following objects represent non-EPON-specific events and 
> should be moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl
> 
> 
> 
> 
> _______________________________________________
> 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


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


From hubmib-bounces@ietf.org  Wed Jan  5 01:38:25 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01517
	for <hubmib-archive@lists.ietf.org>; Wed, 5 Jan 2005 01:38:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm4mt-00035g-Bp; Wed, 05 Jan 2005 01:36:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm4j8-00024F-B3
	for hubmib@megatron.ietf.org; Wed, 05 Jan 2005 01:33:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00984
	for <hubmib@ietf.org>; Wed, 5 Jan 2005 01:33:00 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cm4ve-0003Ph-0h
	for hubmib@ietf.org; Wed, 05 Jan 2005 01:45:58 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	4-0839416774; Wed,  5 Jan 2005 01:32:55 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Wed, 5 Jan 2005 08:32:25 +0200
Message-ID: <050d01c4f2f0$53b80c20$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4cbeb0f20efb229aa93fae1468d20275
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] I will change broadcastLLID to broadcastBit I think that is the
attribute used in the spec. So I will clear the definition as follow:
dot3OmpEmulationBroadcastBitPlusOnuLlid OBJECT-TYPE
    SYNTAX  Counter32
    UNITS      "frames"
    MAX-ACCESS  read-only
    STATUS  current
    DESCRIPTION
            "A count of frames received that contain a valid SLD
             field in a OLT, as defined in [802.3ah] clause
             65.1.3.3.1, and pass the CRC-8 check, as defined in
             [802.3ah] clause 65.1.3.3.3, and contain the broadcast
             bit in LLID and the ONU's LLID (frame reflected) as 
             defined in [802.3ah] clause 65. This attribute is 
             mandatory for an ONU and mandatory for an OLT (a
             counter per LLID)."
    ::= { dot3OmpEmulationStatEntry 9}



-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Tuesday, January 04, 2005 10:06 PM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments


[GK] Comment #7: dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear
what the phrase "broadcast LLID plus ONU's LLID (frame reflected)"
means. Should it simply say "broadcast or unicast LLID"?  Also, there is
no relevant attribute in clause 30 in 802.3ah. 
Comment #8: dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is
redundant, as the dot3OmpEmulationBadLLID will count the same frames. I
recommend removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this
draft.

[LK] If we can see the forwarding rules of the ONU in clause 65 then
there is a behavior for frames with bit broadcast in the LLID where the
LLID is the OLU's LLID (frames is rejected) and when the LLID is not the
ONU's LLID (frame is accepted) as part of the point to point emulation
peer to peer capabilities. This counter counts the first frame. I have
sent in the past comments regarding that to clause 30. The result was
OnuPonCastLLID and OltPonCastLLID which I think their definition is too
vague and refers to a long list of forwarding rules. A solution for
alignment is to make a request to change in the definition of these
attributes in the spec and then unify these counters in them.

[GK] I understand now the intentions of this object. I must add that its
description needs some work. Also, more appropriate name would be
"dot3OmpEmulationMode1PlusOnuId", because "Broadcast LLID" refers to a
very specific 15-bit value. Also note that this mode would be used for
shared medium emulation, not P2P.


Regards,
Glen


> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Lior khermosh
> Sent: Saturday, January 01, 2005 12:33 PM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Cc: 'Glen Kramer'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> Thank you very much for the comments and for the time you invested in 
> reviewing the document. I appreciate it very much.
> 
> 
> 1. Thanks
> 
> 2. I believe it is useful to have also a configuration possibility for

> this parameter. As a guideline I believe management should have access

> to define main modes of the system. Can you please specify why do you 
> think writing such a parameter is not useful? If we want to be 
> strictly following clause 30 I can add change the attribute in the 
> device MIBs objects to read-write but I would rather have it following

> the configuration from the EFM MIB objects.
> 
> 3. Agreed
> 
> 4. My believe is that the management entity as a general requires the 
> knowledge of the PON switching time and does not need to find 
> parameters in the spec to complete the picture as it is may be 
> probably part of a more general access system. I think the MIB objects

> should supply a visibility of the system major parameters although 
> some are fixed. I can add the description of 32TQs value to align with

> the MPCP.
> 
> 5. dot3MpcpRxNotSupportedMpcp. The meaning here is to 8808 opcode 
> frames which are not of PAUSE or used by the MPCP protocol. I will 
> clear the description.
> 
> 6. Agreed
> 
> 7+8. If we can see the forwarding rules of the ONU in clause 65 then 
> 7+there is a behavior for frames with bit broadcast in the LLID where 
> 7+the LLID is the OLU's LLID (frames is rejected) and when the LLID is

> 7+not the ONU's LLID (frame is accepted) as part of the point to point

> 7+emulation peer to peer capabilities. This counter counts the first 
> 7+frame. I have sent in the past comments regarding that to clause 30.

> 7+The result was  OnuPonCastLLID and OltPonCastLLID which I think 
> 7+their definition is too vague and refers to a long list of 
> 7+forwarding rules.
> 
> 7+A solution for alignment is to make a request to change in the 
> 7+definition of these attributes in the spec and then unify these 
> 7+counters in them.
> 
> 9. As a general logical deductive comment you have here a very good 
> comment. The problem comes when in devices a reset process can be a 
> very long process where many different sub-systems are reset. In such 
> a scenario there is a meaning for being in a reset process. Therefore 
> I believe that this is an attribute which is needed for a device. I am

> open here for suggestions.
> 
> 10. Thanks.
> 
> 11. Changing this variable might indeed cause very major changes in 
> the system. Yet in my opinion it is needed for management. 
> Unfortunately in true life engineered systems there is a possibility 
> that a system is not operating well and it is needed to make it 
> inactive immediately. The purpose of such an attribute is like this.
> 
> 12. I guess the question is what is the meaning of power down. I 
> thought of a condition where the device is in minimal power mode where

> it is not transmitting and it is in listening mode so it can be 
> enabled by activation according to MAC address. Keeping it registered 
> can be done easily by reducing its SLA to minimal BW but I don't think

> it  is a power down mode. Keeping it in listening mode will really 
> make it possible for the system to reduce power (notice I do not 
> define what is exactly this mode as it can be implemented as the 
> vendor wishes) yet have the minimal capability to wake up.
> 
> 13. O.K. Would you consider such an object definition instead: I think

> it covers multiple thresholds. eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }
> 
> 14. The OLT and ONUs of an EPON device serves as a distributed virtual

> switch where the LLIDs represent bridge ports. This model is behind 
> the point to point emulation mechanism of clause 65 and of the whole 
> LLID concept. A bridge have a MAC address to port address table and 
> this table here serves for exactly the same purpose. It is not a 
> proprietary implementation. The eponDeviceRemoteMACAddressLLIDControl 
> is a control attribute for resetting this Table. As a table is a 
> manageable entity I think such an object is needed. The 
> useDefaultReporting(3) category is a common option for such attributes

> as a default setting for tables - Implementation is according to 
> Vendors preference. I have no special suggestion for the default 
> value. If people will feel more comfortable I can remove 
> useDefaultReporting(3) and return in the reading none(1).
> 
> 15. The report message in the MPCP refers to such entities. Please see

> section 64.3.6.2 for report message format. These counters refer to 
> that.
> 
> 16. As a general concept we tried to create in the EFM MIB objects a 
> reflection of the IEEE802.3ah management object keeping as much as we 
> can aligned to clause 30. There is here an additional section which 
> refers to device MIB objects. In there I tried to put all things which

> are necessary for the management of an EPON device (in an access
> network) and was not truly covered by the IEEE802.3ah spec as being a 
> spec for L2 MAC mainly. So although they are OAM they are in device 
> level.
> 
> 
> Best regards,
> Lior
> 
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Romascanu, Dan (Dan)
> Sent: Sunday, December 19, 2004 4:22 PM
> To: hubmib@ietf.org
> Cc: Glen Kramer
> Subject: [Hubmib] FW: EPON MIB comments
> 
> 
> Although these comments from one of the 802.3ae contributors came in 
> after the WG Last Call deadline, I suggest that we enter them as Last 
> Call comments and address them accordingly.
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 16 December, 2004 9:49 PM
> To: Romascanu, Dan (Dan)
> Subject: EPON MIB comments
> 
> 
> Dan,
> 
> I finally read the EPON MIB document. Below are my comments. I am not 
> sure if it is too late to make use of these, or not. Plsease, feel 
> free to post these on the reflector.
> 
> Regards,
> Glen
> 
> 
> 1. In tables in section 7, object names that are split across lines 
> lost a letter.
> 
> 2. dot3MpcpMode object should be read-only as is its counterpart in 
> 802.3ah (aMPCPMode attribute).
> 
> 3. dot3MpcpRoundTripTime should be defined for the OLT only, similarly

> to its counterpart in 802.3ah (aMPCPRoundTripTime attribute).  The 
> ONUs are not aware of the round-trip times to the OLT.
> 
> 4. dot3MpcpOnTime and dot3MpcpOffTime. It is not clear from the 
> description that these objects refer to laser_on and laser_off times. 
> Also, according to the 802.3ah, these times are constant and fixed at 
> 32 TQ. These objects are not necessary.  Correspondingly, 802.3ah did 
> not find it necessary to specify such attributes in clause 30.
> 
> 5. dot3MpcpRxNotSupportedMpcp.  The description of this object does 
> not make sense. If a frame is not supported, it is not an MPCP frame. 
> Conversely, there exist no unsupported MPCP frames. There is no 
> matching attribute in clause 30 in 802.3ah and this object should be 
> removed from this draft as well.
> 
> 6. Not clear why dot3OmpEmulationSLDErrors is mandatory at the OLT but

> optional at the ONU. It is not optional per 802.3ah and is relevant 
> for both devices. (For comparison, the dot3OmpEmulationCRC8Errors is 
> mandatory in the OLT and ONUs).
> 
> 7. dot3OmpEmulationBroadcastLLIDPlusOnuId. It is not clear what the 
> phrase "broadcast LLID plus ONU's LLID (frame reflected)" means. 
> Should it simply say "broadcast or unicast LLID"?  Also, there is no 
> relevant attribute in clause 30 in 802.3ah.
> 
> 8. dot3OmpEmulationNotBroadcastLLIDNotOnuId. This object is redundant,

> as the dot3OmpEmulationBadLLID will count the same frames. I recommend

> removing dot3OmpEmulationNotBroadcastLLIDNotOnuId from this draft.
> 
> 9. The access to eponDeviceObjectReset object should be write-only. If

> device is being reset, it cannot generate "reset" response. When the 
> device can generate the response, it will be running already. Thus, 
> the only possible response is "running".
> 
> 10. The object eponDeviceObjectOamMode is not necessary. To get the 
> OAM mode, the management agent would access OAM MIB. No need to 
> duplicate objects in different MIBs.
> 
> 11. eponDeviceObjectDeviceReadyMode object should be read-only. 
> Modifying device mode through the management may have unpredictable 
> results (like taking down entire EPON).
> 
> 12. eponDeviceObjectPowerDown - "Setting this variable to True(1) will

> cause Device to be entered into Power down mode where no registration 
> is allowed and only receiving data from the link.". This object does 
> not make sense. Setting it to True will cause the device lose the link

> (because no transmission is allowed leading to MPCP timeout) and never

> register again (because registration is not allowed).
> 
> 13. eponDeviceObjectReportThreshold. The 802.3ah standard does not 
> limit number of thresholds to be used.  This object will only return 
> the first threshold for each queue. What about the rest of thresholds?

> How to read/set them?
> 
> 14. eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls 
> the resetting of the LLID MAC address log. Setting this object to 
> none(1) has no action resetLog(2) empties the LLID MAC address log. 
> All data is deleted. Setting it to useDefaultReporting(3) returns all 
> entries priorities to their factory-default reporting. Reading this 
> object always returns useDefaultReporting(3)." The description of this

> object seems to match some proprietary EPON device. In the 802.3ah 
> standard, there is no provision of whether to keep LLID MAC address 
> log. It is not clear, what does it mean "returns all entries 
> priorities to their factory-default reporting", since there is no 
> specification for either "entries" or "factory-default reporting". 
> This object should be removed.
> 
> 15. Objects eponDeviceStatTxFramesQueue[0-7], 
> eponDeviceStatRxFramesQueue[0-7], and 
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such 
> as bridge ports. There is no need to duplicate these objects here. 
> Besides, neither 802.3ah nor 802.1D standards require exactly 8 queues

> to be implemented. I recommend removing these objects.
> 
> 16. The following objects represent non-EPON-specific events and 
> should be moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl
> 
> 
> 
> 
> _______________________________________________
> 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


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


From hubmib-bounces@ietf.org  Wed Jan  5 06:53:22 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25876
	for <hubmib-archive@lists.ietf.org>; Wed, 5 Jan 2005 06:53:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm9c5-0004BE-GR; Wed, 05 Jan 2005 06:46:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm9Xq-0002UX-N3
	for hubmib@megatron.ietf.org; Wed, 05 Jan 2005 06:41:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24908
	for <hubmib@ietf.org>; Wed, 5 Jan 2005 06:41:39 -0500 (EST)
Received: from mail14b.g14.rapidsite.net ([128.121.64.164])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cm9kL-0001qE-G1
	for hubmib@ietf.org; Wed, 05 Jan 2005 06:54:41 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14b.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	4-0381915274; Wed,  5 Jan 2005 06:41:16 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Wed, 5 Jan 2005 13:40:47 +0200
Message-ID: <053001c4f31b$67d5fc00$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] Why is it referred only to debug mode? It can be needed during
operation also. Anyway management can affect device condition and
malfunctioning can be a result of any write operation even if it is
resetting of some database log/or table. I think that the security
section in the document should point to the proper place and point out
the hazards.
Why is it different in a concept from resetting an alarm table action or
from changing an operational mode? 
 

-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Wednesday, January 05, 2005 2:18 AM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments


[GK] eponDeviceObjectDeviceReadyMode object should be read-only.
Modifying device mode through the management may have unpredictable
results (like taking down entire EPON).

[LK] Changing this variable might indeed cause very major changes in the
system. Yet in my opinion it is needed for management. Unfortunately in
true life engineered systems there is a possibility that a system is not
operating well and it is needed to make it inactive immediately. The
purpose of such an attribute is like this.

[GK] We should not confuse MIB with debug functions. I would agree to
have an object that would allow disabling a device. I am against
allowing management changing device mode from notReady to ready or from
inProcess to ready. This would take down the device and very likely
would take down the entire EPON. Device mode should only change
according to state machines defined in IEEE 802.3ah.

Regards,
Glen

 


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


From hubmib-bounces@ietf.org  Wed Jan  5 06:59:34 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26414
	for <hubmib-archive@lists.ietf.org>; Wed, 5 Jan 2005 06:59:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm9jM-00066S-SK; Wed, 05 Jan 2005 06:53:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm9eE-0004Wu-EX
	for hubmib@megatron.ietf.org; Wed, 05 Jan 2005 06:48:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25379
	for <hubmib@ietf.org>; Wed, 5 Jan 2005 06:48:15 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cm9qk-00020G-E1
	for hubmib@ietf.org; Wed, 05 Jan 2005 07:01:17 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	3-0114995688; Wed,  5 Jan 2005 06:48:09 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (eponDeviceObjectReportThreshold)
Date: Wed, 5 Jan 2005 13:47:40 +0200
Message-ID: <053101c4f31c$5dca9d50$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] OK.


-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Wednesday, January 05, 2005 2:46 AM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments
(eponDeviceObjectReportThreshold)


[GK] eponDeviceObjectReportThreshold. The 802.3ah standard does not
limit number of thresholds to be used.  This object will only return the
first threshold for each queue. What about the rest of thresholds? How
to read/set them?

[LK] O.K. Would you consider such an object definition instead: I think
it covers multiple thresholds. 

> eponDeviceObjectReportNumThreshold
> OBJECT-TYPE
>     SYNTAX  Integer32
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A set of 8 integers, for each LLID, that defines the
>              number of thresholds for each Queue in the REPORT
>              message, as defined in [802.3ah] 64. Each Queue set
>              reporting will provide information on the queue
>              occupancy of frames below the matching Threshold.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 7 }
> 
>     eponDeviceObjectReportThreshold OBJECT-TYPE
>     SYNTAX  Integer32
>     UNITS       "TQ (16nsec)"
>     MAX-ACCESS  read-write
>     STATUS  current
>     DESCRIPTION
>             "A multiple set of 8 integers, for each LLID, that
>              defines the thresholds reporting for each Queue in the
>              REPORT message, as defined in [802.3ah] 64. The number
>              of sets is eponDeviceObjectReportNumThreshold. Each
>              Queue set reporting will provide information on the
>              queue occupancy of frames below the matching Threshold.
>              The value returned shall be in Time quanta (TQ) which
>              is 16nsec or 2 octets increments.
>              Writing can be done all the time.
>              This attribute is relevant for an OLT and an ONU."
>     DEFVAL { 0 }
>     ::= { eponDeviceControlEntry 8 }

[GK] This is better. For the eponDeviceObjectReportNumThreshold, we need
to describe what happens if this parameter is set to a value greater
than the device can support.  Or maybe we should define a read-only
object eponDeviceObjectReportMaximumNumThreshold that would inform
management entity of the maximum supported number of thresholds.

I would also add read-only object for maximum supported number of
queues: 802.1D says that a device can have from 1 to 8 queues.



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


From hubmib-bounces@ietf.org  Thu Jan  6 01:40:22 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29622
	for <hubmib-archive@lists.ietf.org>; Thu, 6 Jan 2005 01:40:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmRGS-000434-O6; Thu, 06 Jan 2005 01:36:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmRCj-00039O-1y
	for hubmib@megatron.ietf.org; Thu, 06 Jan 2005 01:33:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29118
	for <hubmib@ietf.org>; Thu, 6 Jan 2005 01:33:03 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CmRPO-0005Ze-DU
	for hubmib@ietf.org; Thu, 06 Jan 2005 01:46:14 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	1-0913691661; Thu,  6 Jan 2005 01:07:44 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments (eponDeviceObjectPowerDown)
Date: Thu, 6 Jan 2005 08:07:15 +0200
Message-ID: <05c801c4f3b5$fa0d43e0$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] O.K. I see what you mean and that is not my intention. I want to
refer to a general power down mode without referring to a specific
implementation. So I will remove the reference for receiving data from
link.
eponDeviceObjectPowerDown OBJECT-TYPE
    SYNTAX  TruthValue
    MAX-ACCESS  read-write
    STATUS  current
    DESCRIPTION
            "Setting this variable to True(1) will cause Device to be
             entered into Power down mode. Setting this variable to
             False(0) will cause the device to go out of power down
             mode. When getting True(1) the device is in power down.
             when getting False(0) the device is not in power down.
             Writing can be done all the time. 
             This attribute is relevant for an OLT and an ONU."
    DEFVAL { false }
    ::= { eponDeviceControlEntry 5 }



-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Wednesday, January 05, 2005 2:34 AM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments (eponDeviceObjectPowerDown)


[GK] eponDeviceObjectPowerDown - "Setting this variable to True(1) will
cause Device to be entered into Power down mode where no registration is
allowed and only receiving data from the link.". This object does not
make sense. Setting it to True will cause the device lose the link
(because no transmission is allowed leading to MPCP timeout) and never
register again (because registration is not allowed).

[LK] I guess the question is what is the meaning of power down. I
thought of a condition where the device is in minimal power mode where
it is not transmitting and it is in listening mode so it can be enabled
by activation according to MAC address. Keeping it registered can be
done easily by reducing its SLA to minimal BW but I don't think it is a
power down mode. Keeping it in listening mode will really make it
possible for the system to reduce power (notice I do not define what is
exactly this mode as it can be implemented as the vendor wishes) yet
have the minimal capability to wake up.

[GK] This is very suspiciously seems like fitting of MIB spec to a
specific proprietary implementation. Even if device is not transmitting
any user data, it should periodically transmit MPCP and OAM messages. 
You are trying to define some kind of standby mode without clear
explanation what this mode is or how it can be implemented. I argue that
because MPCP relies on periodic messages, this mode is not possible
without breaking IEEE 802.3ah standard. "Keeping it registered can be
done easily by reducing its SLA to minimal BW..." This is a particular
implementation. Device registration has nothing to do with the
provisioned SLA. There is a very formal state machine that explains
steps of EPON device registration. 


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


From hubmib-bounces@ietf.org  Thu Jan  6 02:15:37 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16069
	for <hubmib-archive@lists.ietf.org>; Thu, 6 Jan 2005 02:15:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmRmk-00051P-Qs; Thu, 06 Jan 2005 02:10:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmRkx-0004FF-9T
	for hubmib@megatron.ietf.org; Thu, 06 Jan 2005 02:08:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09088
	for <hubmib@ietf.org>; Thu, 6 Jan 2005 02:08:26 -0500 (EST)
Received: from mail14b.g14.rapidsite.net ([128.121.64.164])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CmRxf-00024G-9u
	for hubmib@ietf.org; Thu, 06 Jan 2005 02:21:36 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14b.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id 4-09215289; 
	Thu,  6 Jan 2005 02:08:14 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Thu, 6 Jan 2005 09:07:43 +0200
Message-ID: <05ee01c4f3be$6deb00b0$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <200501050125.UAA10641@ietf.org>
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] of course it does not refer to the counters. It refers to the
queues. The counters are an outcome of these entities. 
As indeed you say they are useful parameters. As it is not defined in
the EFM MIB objects I added them to the device MIB objects.


-----Original Message-----
From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
Of Glen Kramer
Sent: Wednesday, January 05, 2005 3:25 AM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments


[GK] Objects eponDeviceStatTxFramesQueue[0-7],
eponDeviceStatRxFramesQueue[0-7], and
eponDeviceStatDroppedFramesQueue[0-7]
are not specific to EPON. These objects exist for other devices, such as
bridge ports. There is no need to duplicate these objects here. Besides,
neither 802.3ah nor 802.1D standards require exactly 8 queues to be
implemented. I recommend removing these objects.

[LK] The report message in the MPCP refers to such entities. Please see
section 64.3.6.2 for report message format. These counters refer to
that.

[GK] The REPORT message does not refer directly of indirectly to any
such entities. I attached the clause 64.3.6.2. Would appreciate if you
could point where and how this clause refers to count of transmitted,
received, and dropped frames. 
I agree that these are useful parameters. But my point is that they are
already defined and are not EPON-specific. There is no need to duplicate
them in this MIB.
 
Regards,
Glen


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


From hubmib-bounces@ietf.org  Thu Jan  6 02:17:14 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16376
	for <hubmib-archive@lists.ietf.org>; Thu, 6 Jan 2005 02:17:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmRrM-0006mk-AO; Thu, 06 Jan 2005 02:15:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmRmL-0004uU-TW
	for hubmib@megatron.ietf.org; Thu, 06 Jan 2005 02:09:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10545
	for <hubmib@ietf.org>; Thu, 6 Jan 2005 02:09:52 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CmRz3-00025q-4T
	for hubmib@ietf.org; Thu, 06 Jan 2005 02:23:03 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	3-0836495388; Thu,  6 Jan 2005 02:09:49 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Thu, 6 Jan 2005 09:09:22 +0200
Message-ID: <05ef01c4f3be$a70a6a70$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <200501050137.UAA11725@ietf.org>
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] Can you kindly please refer to the MIBs where all these entities
exist in.


-----Original Message-----
From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
Of Glen Kramer
Sent: Wednesday, January 05, 2005 3:37 AM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments


[GK] The following objects represent non-EPON-specific events and should
be moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl

[LK] As a general concept we tried to create in the EFM MIB objects a
reflection of the IEEE802.3ah management object keeping as much as we
can aligned to clause 30. There is here an additional section which
refers to device MIB objects. In there I tried to put all things which
are necessary for the management of an EPON device (in an access
network) and was not truly covered by the IEEE802.3ah spec as being a
spec for L2 MAC mainly. So although they are OAM they are in device
level.

[GK] Lior, any network device is a combination of multiple specs. And
correspondingly, management of a network device comprises many MIBs.
EPON MIB should only cover EPON-specific objects. There exist many other
MIBs that are not EPON-specific, but that must be implemented in EPON
devices. Such objects as eponDeviceDyingGaspAlarmEnabled and
eponDeviceTemperatureEventIndicationState (and all other objects listed
above) are not EPON-specific. They exist in other MIBs.
What I am trying to say is that EPON MIB will not be used as
substitution for other MIBs. It is to be used in EPON devices in
addition to other MIBs. 

Regards,
Glen




_______________________________________________
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  Sat Jan  8 01:30:16 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00531
	for <hubmib-archive@lists.ietf.org>; Sat, 8 Jan 2005 01:30:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CnA4r-0005L5-DD; Sat, 08 Jan 2005 01:27:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CnA40-00058U-BQ
	for hubmib@megatron.ietf.org; Sat, 08 Jan 2005 01:27:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00403
	for <hubmib@ietf.org>; Sat, 8 Jan 2005 01:27:03 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CnAH6-0002ta-Ii
	for hubmib@ietf.org; Sat, 08 Jan 2005 01:40:39 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id 3-079314443;
	Sat,  8 Jan 2005 01:07:28 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
	(eponDeviceRemoteMACAddressLLIDControl)
Date: Sat, 8 Jan 2005 08:06:59 +0200
Message-ID: <06eb01c4f548$46f3cdd0$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

[LK] You are right. It seems like the definition of the table mixes 2
things which were not my intention. My intention was not to hold a MAC
address table as in a bridge (which is well covered in the bridge MIB
objects and I had no intention to replica) but to hold a log of ONUs and
their status. The description of the table is indeed confusing and I
will clear it. I think that the MIBs in the table are O.K. I added the
last 3 sentences for clarification in the last draft and they should be
removed as confusing.

Should be:
eponDeviceRemoteMACAddressLLIDTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF EponDeviceRemoteMACAddressLLIDEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION 
            "A table of read-only value that identifies the
             source_address and LLIDs parameter of the remote devices
             in the network. This MacAddress value, as defined in 
             [802.3ah], 30.3.5.1.5, is updated on reception of a
             valid frame with a unicast destination Field or 
             (1) a destination Field equal to the reserved multicast
             address for MAC Control specified in [802.3ah] Annex
             31A, (2) lengthOrType field value equal to the reserved
             Type for MAC Control as specified in [802.3ah] Annex
             31A. (3)an MPCP subtype value equal to the subtype
             reserved for MPCP as specified in [802.3ah] Annex 31A,
             and an LLID as allocated by the OLT. The table is
             defined as Remote MAC address - LLID (RMadL)
             The table is relevant only for an OLT device"
    ::= { eponDeviceControlObjects 2 }




-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Wednesday, January 05, 2005 3:02 AM
To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org; 'Lior khermosh'
Subject: RE: [Hubmib] FW: EPON MIB comments
(eponDeviceRemoteMACAddressLLIDControl)


[GK] eponDeviceRemoteMACAddressLLIDControl - "Indicates and controls the
resetting of the LLID MAC address log. Setting this object to none(1)
has no action resetLog(2) empties the LLID MAC address log. All data is
deleted. Setting it to useDefaultReporting(3) returns all entries
priorities to their factory-default reporting. Reading this object
always returns useDefaultReporting(3)." The description of this object
seems to match some proprietary EPON device. In the 802.3ah standard,
there is no provision of whether to keep LLID MAC address log. It is not
clear, what does it mean "returns all entries priorities to their
factory-default reporting", since there is no specification for either
"entries" or "factory-default reporting". This object should be removed.

[LK] The OLT and ONUs of an EPON device serves as a distributed virtual
switch where the LLIDs represent bridge ports. This model is behind the
point to point emulation mechanism of clause 65 and of the whole LLID
concept. A bridge have a MAC address to port address table and this
table here serves for exactly the same purpose. It is not a proprietary
implementation. The eponDeviceRemoteMACAddressLLIDControl is a control
attribute for resetting this Table. As a table is a manageable entity I
think such an object is needed. The useDefaultReporting(3) category is a
common option for such attributes as a default setting for tables -
Implementation is according to Vendors preference. I have no special
suggestion for the default value. If people will feel more comfortable I
can remove useDefaultReporting(3) and return in the reading none(1).

[GK] There is no document defining what is "LLID MAC address log". The
phrase "The OLT and ONUs of an EPON device serves as a distributed
virtual switch where the LLIDs represent bridge ports" assumes a
particular implementation. LLIDs do not represent bridge ports. LLID
represent virtual links.  These links may or may not be connected to a
bridge at the OLT. The eponDeviceRemoteMACAddressLLIDControl attribute
refers to an address table in the bridge and has nothing to do with
EPON. Therefore, it should be moved to the bridge MIB.

Regards,
Glen

 



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


From hubmib-bounces@ietf.org  Sun Jan  9 21:06:44 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24313
	for <hubmib-archive@lists.ietf.org>; Sun, 9 Jan 2005 21:06:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CnovL-0001sg-9v; Sun, 09 Jan 2005 21:04:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CnosR-0001YX-6y
	for hubmib@megatron.ietf.org; Sun, 09 Jan 2005 21:01:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24110
	for <hubmib@ietf.org>; Sun, 9 Jan 2005 21:01:49 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cnp5w-0001Bf-UX
	for hubmib@ietf.org; Sun, 09 Jan 2005 21:15:49 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0A1qZqm029896
	for <hubmib@ietf.org>; Sun, 9 Jan 2005 20:52:35 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0A1qXqm029858
	for <hubmib@ietf.org>; Sun, 9 Jan 2005 20:52:33 -0500 (EST)
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] FW: EPON MIB comments
	(eponDeviceRemoteMACAddressLLIDControl)
Date: Mon, 10 Jan 2005 04:01:46 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F079C4CF7@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] FW: EPON MIB comments
	(eponDeviceRemoteMACAddressLLIDControl)
Thread-Index: AcT1SwromK/Z1WTjTNap1S48Z1JSeQBbAiMQ
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Lior khermosh" <lior.khermosh@passave.com>, <glen.kramer@teknovus.com>,
        <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Content-Transfer-Encoding: quoted-printable
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Lior,

Please clean up the grammar of this DESCRIPTION clause, otherwise it is =
hard to understand. Expressions like 'a table of read-only value that =
identifies...' or 'the table is defined as Remote MAC Address...' do not =
make too much sense to me. I can guess that you are referring to the =
objects (columns) in the table, but I will leave to you clarifying this =
text.=20

Regards,

Dan



> -----Original Message-----
> From: Lior khermosh [mailto:lior.khermosh@passave.com]
> Sent: 08 January, 2005 8:07 AM
> To: glen.kramer@teknovus.com; Romascanu, Dan (Dan); hubmib@ietf.org
> Subject: RE: [Hubmib] FW: EPON MIB comments=20
> (eponDeviceRemoteMACAddressLLIDControl)
>=20
>=20
> [LK] You are right. It seems like the definition of the table mixes 2
> things which were not my intention. My intention was not to hold a MAC
> address table as in a bridge (which is well covered in the bridge MIB
> objects and I had no intention to replica) but to hold a log=20
> of ONUs and
> their status. The description of the table is indeed confusing and I
> will clear it. I think that the MIBs in the table are O.K. I added the
> last 3 sentences for clarification in the last draft and they=20
> should be
> removed as confusing.
>=20
> Should be:
> eponDeviceRemoteMACAddressLLIDTable OBJECT-TYPE
>     SYNTAX      SEQUENCE OF EponDeviceRemoteMACAddressLLIDEntry
>     MAX-ACCESS  not-accessible
>     STATUS      current
>     DESCRIPTION=20
>             "A table of read-only value that identifies the
>              source_address and LLIDs parameter of the remote devices
>              in the network. This MacAddress value, as defined in=20
>              [802.3ah], 30.3.5.1.5, is updated on reception of a
>              valid frame with a unicast destination Field or=20
>              (1) a destination Field equal to the reserved multicast
>              address for MAC Control specified in [802.3ah] Annex
>              31A, (2) lengthOrType field value equal to the reserved
>              Type for MAC Control as specified in [802.3ah] Annex
>              31A. (3)an MPCP subtype value equal to the subtype
>              reserved for MPCP as specified in [802.3ah] Annex 31A,
>              and an LLID as allocated by the OLT. The table is
>              defined as Remote MAC address - LLID (RMadL)
>              The table is relevant only for an OLT device"
>     ::=3D { eponDeviceControlObjects 2 }
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]=20
> Sent: Wednesday, January 05, 2005 3:02 AM
> To: 'Romascanu, Dan (Dan)'; hubmib@ietf.org; 'Lior khermosh'
> Subject: RE: [Hubmib] FW: EPON MIB comments
> (eponDeviceRemoteMACAddressLLIDControl)
>=20
>=20
> [GK] eponDeviceRemoteMACAddressLLIDControl - "Indicates and=20
> controls the
> resetting of the LLID MAC address log. Setting this object to none(1)
> has no action resetLog(2) empties the LLID MAC address log.=20
> All data is
> deleted. Setting it to useDefaultReporting(3) returns all entries
> priorities to their factory-default reporting. Reading this object
> always returns useDefaultReporting(3)." The description of this object
> seems to match some proprietary EPON device. In the 802.3ah standard,
> there is no provision of whether to keep LLID MAC address=20
> log. It is not
> clear, what does it mean "returns all entries priorities to their
> factory-default reporting", since there is no specification for either
> "entries" or "factory-default reporting". This object should=20
> be removed.
>=20
> [LK] The OLT and ONUs of an EPON device serves as a=20
> distributed virtual
> switch where the LLIDs represent bridge ports. This model is=20
> behind the
> point to point emulation mechanism of clause 65 and of the whole LLID
> concept. A bridge have a MAC address to port address table and this
> table here serves for exactly the same purpose. It is not a=20
> proprietary
> implementation. The eponDeviceRemoteMACAddressLLIDControl is a control
> attribute for resetting this Table. As a table is a=20
> manageable entity I
> think such an object is needed. The useDefaultReporting(3)=20
> category is a
> common option for such attributes as a default setting for tables -
> Implementation is according to Vendors preference. I have no special
> suggestion for the default value. If people will feel more=20
> comfortable I
> can remove useDefaultReporting(3) and return in the reading none(1).
>=20
> [GK] There is no document defining what is "LLID MAC address log". The
> phrase "The OLT and ONUs of an EPON device serves as a distributed
> virtual switch where the LLIDs represent bridge ports" assumes a
> particular implementation. LLIDs do not represent bridge ports. LLID
> represent virtual links.  These links may or may not be connected to a
> bridge at the OLT. The eponDeviceRemoteMACAddressLLIDControl attribute
> refers to an address table in the bridge and has nothing to do with
> EPON. Therefore, it should be moved to the bridge MIB.
>=20
> Regards,
> Glen
>=20
> =20
>=20
>=20
>=20

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


From hubmib-bounces@ietf.org  Mon Jan 10 18:41:39 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15006
	for <hubmib-archive@lists.ietf.org>; Mon, 10 Jan 2005 18:41:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co920-00051W-6B; Mon, 10 Jan 2005 18:33:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Co90A-0004gF-0Y
	for hubmib@megatron.ietf.org; Mon, 10 Jan 2005 18:31:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14037
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 18:31:06 -0500 (EST)
Message-Id: <200501102331.SAA14037@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Co9DV-0005tn-9r
	for hubmib@ietf.org; Mon, 10 Jan 2005 18:45:19 -0500
Received: (qmail 2078 invoked by alias); 10 Jan 2005 23:30:43 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 10 Jan 2005 23:30:43 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Lior khermosh'" <lior.khermosh@passave.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Mon, 10 Jan 2005 15:30:35 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTzvnxr5/hRWDL4QiWluekD8Ui5fADrEnQQ
In-Reply-To: <05ee01c4f3be$6deb00b0$2b0b0b0b@passave.co.il>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Lior,

I think we have a fundamental disagreement on the scope of this document. I
argue that this MIB should only include EPON-specific objects, i.e., objects
that you would not find in any other MIB. This would include statistics for
MPCP messages, LLIDs, and so on. I believe that EPON devices should
implement multiple MIBs: OAM MIB, Bridging MIB, and EPON-specific MIB.
It seems to me that your approach is to define a single MIB that would
include (or duplicate) all objects that *MAY BE* used in EPON, even though
these objects may already have been defined elsewhere. 

For example, counters of transmitted, received, and dropped frames per queue
are not EPON-specific. Any port (according to 802.1D) may have up to 8
queues behind it and would count these statistics. I don't think these
objects belong to EPON-specific MIB.

Before further discussing specific comments, I'd like to ask for a
clarification from the task force on the scope of this document.

Regards,
Glen

> -----Original Message-----
> From: Lior khermosh [mailto:lior.khermosh@passave.com]
> Sent: Wednesday, January 05, 2005 11:08 PM
> To: glen.kramer@teknovus.com; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> [LK] of course it does not refer to the counters. It refers to the
> queues. The counters are an outcome of these entities.
> As indeed you say they are useful parameters. As it is not defined in
> the EFM MIB objects I added them to the device MIB objects.
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf
> Of Glen Kramer
> Sent: Wednesday, January 05, 2005 3:25 AM
> To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> 
> [GK] Objects eponDeviceStatTxFramesQueue[0-7],
> eponDeviceStatRxFramesQueue[0-7], and
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such as
> bridge ports. There is no need to duplicate these objects here. Besides,
> neither 802.3ah nor 802.1D standards require exactly 8 queues to be
> implemented. I recommend removing these objects.
> 
> [LK] The report message in the MPCP refers to such entities. Please see
> section 64.3.6.2 for report message format. These counters refer to
> that.
> 
> [GK] The REPORT message does not refer directly of indirectly to any
> such entities. I attached the clause 64.3.6.2. Would appreciate if you
> could point where and how this clause refers to count of transmitted,
> received, and dropped frames.
> I agree that these are useful parameters. But my point is that they are
> already defined and are not EPON-specific. There is no need to duplicate
> them in this MIB.
> 
> Regards,
> Glen
> 




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


From hubmib-bounces@ietf.org  Mon Jan 10 19:08:24 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16377
	for <hubmib-archive@lists.ietf.org>; Mon, 10 Jan 2005 19:08:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co9GY-0007q0-5M; Mon, 10 Jan 2005 18:48:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Co9Ew-0007Rs-0a
	for hubmib@megatron.ietf.org; Mon, 10 Jan 2005 18:46:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15239
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 18:46:22 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Co9Sa-0006Em-0O
	for hubmib@ietf.org; Mon, 10 Jan 2005 19:00:35 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0ANb5qm028820
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 18:37:05 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0ANb3qm028779
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 18:37:04 -0500 (EST)
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 11 Jan 2005 01:46:15 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9FE3@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] FW: EPON MIB comments
Thread-Index: AcTzvnxr5/hRWDL4QiWluekD8Ui5fADrEnQQAACppOA=
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <glen.kramer@teknovus.com>, "Lior khermosh" <lior.khermosh@passave.com>,
        <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: quoted-printable
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Glen,

The focus of the EPON MIB  work is on defining management objects for =
EPON networks. This does not mean however providing a one-to-one mapping =
to the management attributes defined by the IEEE spec. According to the =
case we may define less, the same or more objects than the ones defined =
by the IEEE spec. We can even in some cases define objects that are not =
EPON specific, if they are helpful and the common management practice is =
to use them in the management of EPONs. This should however be rather =
the exception, and if the non-EPON objects become a consistent part of =
the overall work I would recommend defining a separate MIB module. =
Duplication is generally considered a bad practice but please be more =
specific about what objects you consider being already covered in other =
standard MIBs.
=20
Regards,

Dan
(Speaking as chair)




> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 11 January, 2005 1:31 AM
> To: 'Lior khermosh'; Romascanu, Dan (Dan); hubmib@ietf.org
> Subject: RE: [Hubmib] FW: EPON MIB comments
>=20
>=20
> Lior,
>=20
> I think we have a fundamental disagreement on the scope of=20
> this document. I
> argue that this MIB should only include EPON-specific=20
> objects, i.e., objects
> that you would not find in any other MIB. This would include=20
> statistics for
> MPCP messages, LLIDs, and so on. I believe that EPON devices should
> implement multiple MIBs: OAM MIB, Bridging MIB, and EPON-specific MIB.
> It seems to me that your approach is to define a single MIB that would
> include (or duplicate) all objects that *MAY BE* used in=20
> EPON, even though
> these objects may already have been defined elsewhere.=20
>=20
> For example, counters of transmitted, received, and dropped=20
> frames per queue
> are not EPON-specific. Any port (according to 802.1D) may have up to 8
> queues behind it and would count these statistics. I don't think these
> objects belong to EPON-specific MIB.
>=20
> Before further discussing specific comments, I'd like to ask for a
> clarification from the task force on the scope of this document.
>=20
> Regards,
> Glen
>=20
> > -----Original Message-----
> > From: Lior khermosh [mailto:lior.khermosh@passave.com]
> > Sent: Wednesday, January 05, 2005 11:08 PM
> > To: glen.kramer@teknovus.com; 'Romascanu, Dan (Dan)';=20
> hubmib@ietf.org
> > Subject: RE: [Hubmib] FW: EPON MIB comments
> >=20
> > [LK] of course it does not refer to the counters. It refers to the
> > queues. The counters are an outcome of these entities.
> > As indeed you say they are useful parameters. As it is not=20
> defined in
> > the EFM MIB objects I added them to the device MIB objects.
> >=20
> >=20
> > -----Original Message-----
> > From: hubmib-bounces@ietf.org=20
> [mailto:hubmib-bounces@ietf.org] On Behalf
> > Of Glen Kramer
> > Sent: Wednesday, January 05, 2005 3:25 AM
> > To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> > Subject: RE: [Hubmib] FW: EPON MIB comments
> >=20
> >=20
> > [GK] Objects eponDeviceStatTxFramesQueue[0-7],
> > eponDeviceStatRxFramesQueue[0-7], and
> > eponDeviceStatDroppedFramesQueue[0-7]
> > are not specific to EPON. These objects exist for other=20
> devices, such as
> > bridge ports. There is no need to duplicate these objects=20
> here. Besides,
> > neither 802.3ah nor 802.1D standards require exactly 8 queues to be
> > implemented. I recommend removing these objects.
> >=20
> > [LK] The report message in the MPCP refers to such=20
> entities. Please see
> > section 64.3.6.2 for report message format. These counters refer to
> > that.
> >=20
> > [GK] The REPORT message does not refer directly of indirectly to any
> > such entities. I attached the clause 64.3.6.2. Would=20
> appreciate if you
> > could point where and how this clause refers to count of=20
> transmitted,
> > received, and dropped frames.
> > I agree that these are useful parameters. But my point is=20
> that they are
> > already defined and are not EPON-specific. There is no need=20
> to duplicate
> > them in this MIB.
> >=20
> > Regards,
> > Glen
> >=20
>=20
>=20
>=20
>=20

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


From hubmib-bounces@ietf.org  Mon Jan 10 19:33:27 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18125
	for <hubmib-archive@lists.ietf.org>; Mon, 10 Jan 2005 19:33:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co9wQ-0000pV-Ms; Mon, 10 Jan 2005 19:31:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Co9uA-00009j-9r
	for hubmib@megatron.ietf.org; Mon, 10 Jan 2005 19:29:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17804
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 19:28:58 -0500 (EST)
Message-Id: <200501110028.TAA17804@ietf.org>
Received: from m1008.hostcentric.net ([216.65.102.204])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CoA7q-00071t-L8
	for hubmib@ietf.org; Mon, 10 Jan 2005 19:43:12 -0500
Received: (qmail 32026 invoked by alias); 11 Jan 2005 00:28:48 -0000
Received: from unknown (HELO glen) (69.28.99.210)
	by 0 with SMTP; 11 Jan 2005 00:28:48 -0000
From: "Glen Kramer" <glen.kramer@teknovus.com>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
        "'Lior khermosh'" <lior.khermosh@passave.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Mon, 10 Jan 2005 16:28:39 -0800
Organization: Teknovus
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTzvnxr5/hRWDL4QiWluekD8Ui5fADrEnQQAACppOAAAP3TEA==
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9FE3@is0004avexu1.global.avaya.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Content-Transfer-Encoding: 7bit
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: glen.kramer@teknovus.com
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Dan,

Thanks for your response. I didn't try to enforce one-to-one correspondence
with IEEE spec. But there are attributes defined in EPON MIB now that are
applicable to non-EPON devices. For example, TxFrames, RxFrames, and
DropFrames counters (see end of this e-mail) are attributes of any 802.1D
port. 
Another example is alarm related attributes:
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl

These objects are equally applicable to point-to-point fiber links or copper
links. I believe they should be moved to OAM MIB. 

Regards,
Glen

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Monday, January 10, 2005 3:46 PM
> To: glen.kramer@teknovus.com; Lior khermosh; hubmib@ietf.org
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> Glen,
> 
> The focus of the EPON MIB  work is on defining management objects for EPON
> networks. This does not mean however providing a one-to-one mapping to the
> management attributes defined by the IEEE spec. According to the case we
> may define less, the same or more objects than the ones defined by the
> IEEE spec. We can even in some cases define objects that are not EPON
> specific, if they are helpful and the common management practice is to use
> them in the management of EPONs. This should however be rather the
> exception, and if the non-EPON objects become a consistent part of the
> overall work I would recommend defining a separate MIB module. Duplication
> is generally considered a bad practice but please be more specific about
> what objects you consider being already covered in other standard MIBs.
> 
> Regards,
> 
> Dan
> (Speaking as chair)
> 
> 
> 
> 
> > -----Original Message-----
> > From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> > Sent: 11 January, 2005 1:31 AM
> > To: 'Lior khermosh'; Romascanu, Dan (Dan); hubmib@ietf.org
> > Subject: RE: [Hubmib] FW: EPON MIB comments
> >
> >
> > Lior,
> >
> > I think we have a fundamental disagreement on the scope of
> > this document. I
> > argue that this MIB should only include EPON-specific
> > objects, i.e., objects
> > that you would not find in any other MIB. This would include
> > statistics for
> > MPCP messages, LLIDs, and so on. I believe that EPON devices should
> > implement multiple MIBs: OAM MIB, Bridging MIB, and EPON-specific MIB.
> > It seems to me that your approach is to define a single MIB that would
> > include (or duplicate) all objects that *MAY BE* used in
> > EPON, even though
> > these objects may already have been defined elsewhere.
> >
> > For example, counters of transmitted, received, and dropped
> > frames per queue
> > are not EPON-specific. Any port (according to 802.1D) may have up to 8
> > queues behind it and would count these statistics. I don't think these
> > objects belong to EPON-specific MIB.
> >
> > Before further discussing specific comments, I'd like to ask for a
> > clarification from the task force on the scope of this document.
> >
> > Regards,
> > Glen
> >
> > > -----Original Message-----
> > > From: Lior khermosh [mailto:lior.khermosh@passave.com]
> > > Sent: Wednesday, January 05, 2005 11:08 PM
> > > To: glen.kramer@teknovus.com; 'Romascanu, Dan (Dan)';
> > hubmib@ietf.org
> > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > >
> > > [LK] of course it does not refer to the counters. It refers to the
> > > queues. The counters are an outcome of these entities.
> > > As indeed you say they are useful parameters. As it is not
> > defined in
> > > the EFM MIB objects I added them to the device MIB objects.
> > >
> > >
> > > -----Original Message-----
> > > From: hubmib-bounces@ietf.org
> > [mailto:hubmib-bounces@ietf.org] On Behalf
> > > Of Glen Kramer
> > > Sent: Wednesday, January 05, 2005 3:25 AM
> > > To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > >
> > >
> > > [GK] Objects eponDeviceStatTxFramesQueue[0-7],
> > > eponDeviceStatRxFramesQueue[0-7], and
> > > eponDeviceStatDroppedFramesQueue[0-7]
> > > are not specific to EPON. These objects exist for other
> > devices, such as
> > > bridge ports. There is no need to duplicate these objects
> > here. Besides,
> > > neither 802.3ah nor 802.1D standards require exactly 8 queues to be
> > > implemented. I recommend removing these objects.
> > >
> > > [LK] The report message in the MPCP refers to such
> > entities. Please see
> > > section 64.3.6.2 for report message format. These counters refer to
> > > that.
> > >
> > > [GK] The REPORT message does not refer directly of indirectly to any
> > > such entities. I attached the clause 64.3.6.2. Would
> > appreciate if you
> > > could point where and how this clause refers to count of
> > transmitted,
> > > received, and dropped frames.
> > > I agree that these are useful parameters. But my point is
> > that they are
> > > already defined and are not EPON-specific. There is no need
> > to duplicate
> > > them in this MIB.
> > >
> > > Regards,
> > > Glen
> > >
> >
> >
> >
> >



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


From hubmib-bounces@ietf.org  Mon Jan 10 19:40:26 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18573
	for <hubmib-archive@lists.ietf.org>; Mon, 10 Jan 2005 19:40:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoA2q-0001nb-9U; Mon, 10 Jan 2005 19:38:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoA05-0001Pb-7s
	for hubmib@megatron.ietf.org; Mon, 10 Jan 2005 19:35:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18248
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 19:35:06 -0500 (EST)
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoADj-000797-2F
	for hubmib@ietf.org; Mon, 10 Jan 2005 19:49:19 -0500
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0B0WvFe025898
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 19:32:57 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0B0WtFe025861
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 19:32:56 -0500 (EST)
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 11 Jan 2005 02:34:57 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E30817@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] FW: EPON MIB comments
Thread-Index: AcTzvnxr5/hRWDL4QiWluekD8Ui5fADrEnQQAACppOAAAP3TEAAA8fHA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <glen.kramer@teknovus.com>, "Lior khermosh" <lior.khermosh@passave.com>,
        <hubmib@ietf.org>, "Matt Squire" <MSquire@HatterasNetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Content-Transfer-Encoding: quoted-printable
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Lior, Matt, other,=20

Please comment.=20

Regards,

Dan



> -----Original Message-----
> From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> Sent: 11 January, 2005 2:29 AM
> To: Romascanu, Dan (Dan); 'Lior khermosh'; hubmib@ietf.org
> Subject: RE: [Hubmib] FW: EPON MIB comments
>=20
>=20
> Dan,
>=20
> Thanks for your response. I didn't try to enforce one-to-one=20
> correspondence
> with IEEE spec. But there are attributes defined in EPON MIB=20
> now that are
> applicable to non-EPON devices. For example, TxFrames, RxFrames, and
> DropFrames counters (see end of this e-mail) are attributes=20
> of any 802.1D
> port.=20
> Another example is alarm related attributes:
> >    eponDeviceDyingGaspAlarmState
> >    eponDeviceDyingGaspAlarmEnabled
> >    eponDeviceCriticalEventState
> >    eponDeviceCriticalEventEnabled
> >    eponDeviceLocalLinkFaultAlarmState
> >    eponDeviceLocalLinkFaultAlarmEnabled
> >    eponDeviceTemperatureEventIndicationState
> >    eponDeviceTemperatureEventIndicationEnabled
> >    eponDevicePowerVoltageEventIndicationState
> >    eponDevicePowerVoltageEventIndicationEnabled
> >    eponDeviceGlobalEventState
> >    eponDeviceGlobalEventEnabled
> >    eponDeviceErroredSymbolPeriodEventState
> >    eponDeviceErroredSymbolPeriodEventEnabled
> >    eponDeviceErroredFrameEventState
> >    eponDeviceErroredFrameEventEnabled
> >    eponDeviceErroredFramePeriodEventState
> >    eponDeviceErroredFramePeriodEventEnabled
> >    eponDeviceErroredFrameSecondsSummaryEventState
> >    eponDeviceErroredFrameSecondsSummaryEventEnabled
> >    eponDeviceOrganizationSpecificEventState
> >    eponDeviceOrganizationSpecificEventEnabled
> >    eponDeviceEventControl
>=20
> These objects are equally applicable to point-to-point fiber=20
> links or copper
> links. I believe they should be moved to OAM MIB.=20
>=20
> Regards,
> Glen
>=20
> > -----Original Message-----
> > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > Sent: Monday, January 10, 2005 3:46 PM
> > To: glen.kramer@teknovus.com; Lior khermosh; hubmib@ietf.org
> > Subject: RE: [Hubmib] FW: EPON MIB comments
> >=20
> > Glen,
> >=20
> > The focus of the EPON MIB  work is on defining management=20
> objects for EPON
> > networks. This does not mean however providing a one-to-one=20
> mapping to the
> > management attributes defined by the IEEE spec. According=20
> to the case we
> > may define less, the same or more objects than the ones=20
> defined by the
> > IEEE spec. We can even in some cases define objects that=20
> are not EPON
> > specific, if they are helpful and the common management=20
> practice is to use
> > them in the management of EPONs. This should however be rather the
> > exception, and if the non-EPON objects become a consistent=20
> part of the
> > overall work I would recommend defining a separate MIB=20
> module. Duplication
> > is generally considered a bad practice but please be more=20
> specific about
> > what objects you consider being already covered in other=20
> standard MIBs.
> >=20
> > Regards,
> >=20
> > Dan
> > (Speaking as chair)
> >=20
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> > > Sent: 11 January, 2005 1:31 AM
> > > To: 'Lior khermosh'; Romascanu, Dan (Dan); hubmib@ietf.org
> > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > >
> > >
> > > Lior,
> > >
> > > I think we have a fundamental disagreement on the scope of
> > > this document. I
> > > argue that this MIB should only include EPON-specific
> > > objects, i.e., objects
> > > that you would not find in any other MIB. This would include
> > > statistics for
> > > MPCP messages, LLIDs, and so on. I believe that EPON=20
> devices should
> > > implement multiple MIBs: OAM MIB, Bridging MIB, and=20
> EPON-specific MIB.
> > > It seems to me that your approach is to define a single=20
> MIB that would
> > > include (or duplicate) all objects that *MAY BE* used in
> > > EPON, even though
> > > these objects may already have been defined elsewhere.
> > >
> > > For example, counters of transmitted, received, and dropped
> > > frames per queue
> > > are not EPON-specific. Any port (according to 802.1D) may=20
> have up to 8
> > > queues behind it and would count these statistics. I=20
> don't think these
> > > objects belong to EPON-specific MIB.
> > >
> > > Before further discussing specific comments, I'd like to ask for a
> > > clarification from the task force on the scope of this document.
> > >
> > > Regards,
> > > Glen
> > >
> > > > -----Original Message-----
> > > > From: Lior khermosh [mailto:lior.khermosh@passave.com]
> > > > Sent: Wednesday, January 05, 2005 11:08 PM
> > > > To: glen.kramer@teknovus.com; 'Romascanu, Dan (Dan)';
> > > hubmib@ietf.org
> > > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > >
> > > > [LK] of course it does not refer to the counters. It=20
> refers to the
> > > > queues. The counters are an outcome of these entities.
> > > > As indeed you say they are useful parameters. As it is not
> > > defined in
> > > > the EFM MIB objects I added them to the device MIB objects.
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: hubmib-bounces@ietf.org
> > > [mailto:hubmib-bounces@ietf.org] On Behalf
> > > > Of Glen Kramer
> > > > Sent: Wednesday, January 05, 2005 3:25 AM
> > > > To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> > > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > >
> > > >
> > > > [GK] Objects eponDeviceStatTxFramesQueue[0-7],
> > > > eponDeviceStatRxFramesQueue[0-7], and
> > > > eponDeviceStatDroppedFramesQueue[0-7]
> > > > are not specific to EPON. These objects exist for other
> > > devices, such as
> > > > bridge ports. There is no need to duplicate these objects
> > > here. Besides,
> > > > neither 802.3ah nor 802.1D standards require exactly 8=20
> queues to be
> > > > implemented. I recommend removing these objects.
> > > >
> > > > [LK] The report message in the MPCP refers to such
> > > entities. Please see
> > > > section 64.3.6.2 for report message format. These=20
> counters refer to
> > > > that.
> > > >
> > > > [GK] The REPORT message does not refer directly of=20
> indirectly to any
> > > > such entities. I attached the clause 64.3.6.2. Would
> > > appreciate if you
> > > > could point where and how this clause refers to count of
> > > transmitted,
> > > > received, and dropped frames.
> > > > I agree that these are useful parameters. But my point is
> > > that they are
> > > > already defined and are not EPON-specific. There is no need
> > > to duplicate
> > > > them in this MIB.
> > > >
> > > > Regards,
> > > > Glen
> > > >
> > >
> > >
> > >
> > >
>=20
>=20
>=20

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


From hubmib-bounces@ietf.org  Mon Jan 10 19:42:40 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18703
	for <hubmib-archive@lists.ietf.org>; Mon, 10 Jan 2005 19:42:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoA5x-0002fX-7A; Mon, 10 Jan 2005 19:41:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoA4y-0002Ts-LV
	for hubmib@megatron.ietf.org; Mon, 10 Jan 2005 19:40:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18565
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 19:40:09 -0500 (EST)
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoAId-0007F5-Uh
	for hubmib@ietf.org; Mon, 10 Jan 2005 19:54:23 -0500
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0B0c6Fe001353
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 19:38:06 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0B0c4Fe001306
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 19:38:05 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 11 Jan 2005 02:40:06 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9FE4@is0004avexu1.global.avaya.com>
Thread-Topic: Meeting in Minneapolis? 
Thread-Index: AcT3dheluMha6uinQTKFbHsnOkUUYQ==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Subject: [Hubmib] Meeting in Minneapolis? 
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="===============1855313188=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1855313188==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F776.18695F8A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4F776.18695F8A
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

It looks like there is still more work to do with the EFM MIB documents. =
The number of comments received during the Last Call indicates that we =
will need another round, and this is even before the traditional chair =
review. My question is whether the participants believe that a meeting =
during the Minneapolis IETF (March 6 to 11). Please answer if you =
believe that we need to meet, and let me know if there are fair chances =
for you to attend. I need your answers in the next week or so, so that =
we have time to ask for a meeting slot.=20

Regards,

Dan



------_=_NextPart_001_01C4F776.18695F8A
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.6603.0">
<TITLE>Meeting in Minneapolis? </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">It looks like there is still =
more work to do with the EFM MIB documents. The number of comments =
received during the Last Call indicates that we will need another round, =
and this is even before the traditional chair review. My question is =
whether the participants believe that a meeting during the Minneapolis =
IETF (March 6 to 11). Please answer if you believe that we need to meet, =
and let me know if there are fair chances for you to attend. I need your =
answers in the next week or so, so that we have time to ask for a =
meeting slot. </FONT></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C4F776.18695F8A--


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

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

--===============1855313188==--



From hubmib-bounces@ietf.org  Mon Jan 10 20:32:39 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21992
	for <hubmib-archive@lists.ietf.org>; Mon, 10 Jan 2005 20:32:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoAry-00033g-A8; Mon, 10 Jan 2005 20:30:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoAq7-0002bF-Sj
	for hubmib@megatron.ietf.org; Mon, 10 Jan 2005 20:28:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21613
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 20:28:54 -0500 (EST)
Received: from mailserv.hatterasnetworks.com ([63.89.58.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoB3l-0008Bo-Dg
	for hubmib@ietf.org; Mon, 10 Jan 2005 20:43:06 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Mon, 10 Jan 2005 20:28:19 -0500
Message-ID: <8052E2EA753D144EB906B7A7AA399714032868B3@mailserv.hatteras.com>
Thread-Topic: [Hubmib] FW: EPON MIB comments
Thread-Index: AcTzvnxr5/hRWDL4QiWluekD8Ui5fADrEnQQAACppOAAAP3TEAAA8fHAAADs9dA=
From: "Matt Squire" <MSquire@HatterasNetworks.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, <glen.kramer@teknovus.com>,
        "Lior khermosh" <lior.khermosh@passave.com>, <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1e467ff145ef391eb7b594ef62b8301f
Content-Transfer-Encoding: quoted-printable
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable


My comments are dispersed throughout.  =20

> Lior, Matt, other,=20
>=20
> Please comment.=20
>=20
> Regards,
>=20
> Dan
>=20
>=20
>=20
> > -----Original Message-----
> > From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> > Sent: 11 January, 2005 2:29 AM
> > To: Romascanu, Dan (Dan); 'Lior khermosh'; hubmib@ietf.org
> > Subject: RE: [Hubmib] FW: EPON MIB comments
> >=20
> >=20
> > Dan,
> >=20
> > Thanks for your response. I didn't try to enforce one-to-one=20
> > correspondence
> > with IEEE spec. But there are attributes defined in EPON MIB=20
> > now that are
> > applicable to non-EPON devices. For example, TxFrames, RxFrames, and
> > DropFrames counters (see end of this e-mail) are attributes=20
> > of any 802.1D
> > port.=20

Counters in .1D are defined to reflect operation at the 802.1 level - =
counters in the .3 MIBs should reflect behavior at the .3 level.  =
Although both may define "DropFrames", the dropping point and therefore =
the actual semantics of the counter would be different.  I'm not arguing =
that EPON needs or does not need a DropFrame counter, only that if it =
does define one, it has nothing to do with the 802.1D DropFrame counter. =
=20

> > Another example is alarm related attributes:
> > >    eponDeviceDyingGaspAlarmState
> > >    eponDeviceDyingGaspAlarmEnabled
> > >    eponDeviceCriticalEventState
> > >    eponDeviceCriticalEventEnabled
> > >    eponDeviceLocalLinkFaultAlarmState
> > >    eponDeviceLocalLinkFaultAlarmEnabled

In the first revision of the OAM MIB, these states were directly =
reflected.  In the -02 revision, all event information was shoved into a =
new "EventLog" table.  So transition in these are flags are reflected =
there.  I can add them back as separate objects, I just don't want to go =
back and forth.  In the transition to the -02 version, the =
enable/disable of the events reflected in flags was <stupidly> removed.  =
Can add that back as removing it was unintentional. =20

> > >    eponDeviceTemperatureEventIndicationState
> > >    eponDeviceTemperatureEventIndicationEnabled
> > >    eponDevicePowerVoltageEventIndicationState
> > >    eponDevicePowerVoltageEventIndicationEnabled

Where are these objects reflected in the management clause of 802.3ah?  =
I'm not a fan of adding new things at this stage of the game.  Temp and =
voltage measurements and events aren't generally within the purview of =
802.3.  =20

> > >    eponDeviceGlobalEventState
> > >    eponDeviceGlobalEventEnabled
> > >    eponDeviceErroredSymbolPeriodEventState
> > >    eponDeviceErroredSymbolPeriodEventEnabled
> > >    eponDeviceErroredFrameEventState
> > >    eponDeviceErroredFrameEventEnabled
> > >    eponDeviceErroredFramePeriodEventState
> > >    eponDeviceErroredFramePeriodEventEnabled
> > >    eponDeviceErroredFrameSecondsSummaryEventState
> > >    eponDeviceErroredFrameSecondsSummaryEventEnabled

The configuration (enable/disable/thresholds/etc.) are covered in the =
dot3OamEventConfigTable, so I don't see any benefit/need for change from =
these - we got 'em. =20

> > >    eponDeviceOrganizationSpecificEventState
> > >    eponDeviceOrganizationSpecificEventEnabled

The thought was controls like these weren't useful.  There can be a =
plethora of organization specific events from a group of different =
organizations.  IMHO, each organization should define their controls as =
one switch doesn't cover all, at least not well. =20

> > >    eponDeviceEventControl
> >=20
> > These objects are equally applicable to point-to-point fiber=20
> > links or copper
> > links. I believe they should be moved to OAM MIB.=20
> >=20
> > Regards,
> > Glen
> >=20
> > > -----Original Message-----
> > > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > > Sent: Monday, January 10, 2005 3:46 PM
> > > To: glen.kramer@teknovus.com; Lior khermosh; hubmib@ietf.org
> > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > >=20
> > > Glen,
> > >=20
> > > The focus of the EPON MIB  work is on defining management=20
> > objects for EPON
> > > networks. This does not mean however providing a one-to-one=20
> > mapping to the
> > > management attributes defined by the IEEE spec. According=20
> > to the case we
> > > may define less, the same or more objects than the ones=20
> > defined by the
> > > IEEE spec. We can even in some cases define objects that=20
> > are not EPON
> > > specific, if they are helpful and the common management=20
> > practice is to use
> > > them in the management of EPONs. This should however be rather the
> > > exception, and if the non-EPON objects become a consistent=20
> > part of the
> > > overall work I would recommend defining a separate MIB=20
> > module. Duplication
> > > is generally considered a bad practice but please be more=20
> > specific about
> > > what objects you consider being already covered in other=20
> > standard MIBs.
> > >=20
> > > Regards,
> > >=20
> > > Dan
> > > (Speaking as chair)
> > >=20
> > >=20
> > >=20
> > >=20
> > > > -----Original Message-----
> > > > From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> > > > Sent: 11 January, 2005 1:31 AM
> > > > To: 'Lior khermosh'; Romascanu, Dan (Dan); hubmib@ietf.org
> > > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > >
> > > >
> > > > Lior,
> > > >
> > > > I think we have a fundamental disagreement on the scope of
> > > > this document. I
> > > > argue that this MIB should only include EPON-specific
> > > > objects, i.e., objects
> > > > that you would not find in any other MIB. This would include
> > > > statistics for
> > > > MPCP messages, LLIDs, and so on. I believe that EPON=20
> > devices should
> > > > implement multiple MIBs: OAM MIB, Bridging MIB, and=20
> > EPON-specific MIB.
> > > > It seems to me that your approach is to define a single=20
> > MIB that would
> > > > include (or duplicate) all objects that *MAY BE* used in
> > > > EPON, even though
> > > > these objects may already have been defined elsewhere.
> > > >
> > > > For example, counters of transmitted, received, and dropped
> > > > frames per queue
> > > > are not EPON-specific. Any port (according to 802.1D) may=20
> > have up to 8
> > > > queues behind it and would count these statistics. I=20
> > don't think these
> > > > objects belong to EPON-specific MIB.
> > > >
> > > > Before further discussing specific comments, I'd like=20
> to ask for a
> > > > clarification from the task force on the scope of this document.
> > > >
> > > > Regards,
> > > > Glen
> > > >
> > > > > -----Original Message-----
> > > > > From: Lior khermosh [mailto:lior.khermosh@passave.com]
> > > > > Sent: Wednesday, January 05, 2005 11:08 PM
> > > > > To: glen.kramer@teknovus.com; 'Romascanu, Dan (Dan)';
> > > > hubmib@ietf.org
> > > > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > > >
> > > > > [LK] of course it does not refer to the counters. It=20
> > refers to the
> > > > > queues. The counters are an outcome of these entities.
> > > > > As indeed you say they are useful parameters. As it is not
> > > > defined in
> > > > > the EFM MIB objects I added them to the device MIB objects.
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: hubmib-bounces@ietf.org
> > > > [mailto:hubmib-bounces@ietf.org] On Behalf
> > > > > Of Glen Kramer
> > > > > Sent: Wednesday, January 05, 2005 3:25 AM
> > > > > To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> > > > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > > >
> > > > >
> > > > > [GK] Objects eponDeviceStatTxFramesQueue[0-7],
> > > > > eponDeviceStatRxFramesQueue[0-7], and
> > > > > eponDeviceStatDroppedFramesQueue[0-7]
> > > > > are not specific to EPON. These objects exist for other
> > > > devices, such as
> > > > > bridge ports. There is no need to duplicate these objects
> > > > here. Besides,
> > > > > neither 802.3ah nor 802.1D standards require exactly 8=20
> > queues to be
> > > > > implemented. I recommend removing these objects.
> > > > >
> > > > > [LK] The report message in the MPCP refers to such
> > > > entities. Please see
> > > > > section 64.3.6.2 for report message format. These=20
> > counters refer to
> > > > > that.
> > > > >
> > > > > [GK] The REPORT message does not refer directly of=20
> > indirectly to any
> > > > > such entities. I attached the clause 64.3.6.2. Would
> > > > appreciate if you
> > > > > could point where and how this clause refers to count of
> > > > transmitted,
> > > > > received, and dropped frames.
> > > > > I agree that these are useful parameters. But my point is
> > > > that they are
> > > > > already defined and are not EPON-specific. There is no need
> > > > to duplicate
> > > > > them in this MIB.
> > > > >
> > > > > Regards,
> > > > > Glen
> > > > >
> > > >
> > > >
> > > >
> > > >
> >=20
> >=20
> >=20
>=20

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


From hubmib-bounces@ietf.org  Mon Jan 10 20:44:34 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23062
	for <hubmib-archive@lists.ietf.org>; Mon, 10 Jan 2005 20:44:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoB3g-0004fY-C0; Mon, 10 Jan 2005 20:42:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoB2o-0004Sd-8r
	for hubmib@megatron.ietf.org; Mon, 10 Jan 2005 20:42:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22794
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 20:42:00 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoBGV-0008TL-S5
	for hubmib@ietf.org; Mon, 10 Jan 2005 20:56:13 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0B1Wgqm026157
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 20:32:42 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0B1Weqm026114
	for <hubmib@ietf.org>; Mon, 10 Jan 2005 20:32:41 -0500 (EST)
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 11 Jan 2005 03:41:54 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9FE6@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] FW: EPON MIB comments
Thread-Index: AcTzvnxr5/hRWDL4QiWluekD8Ui5fADrEnQQAACppOAAAP3TEAAA8fHAAADs9dAAAUQA8A==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Matt Squire" <MSquire@HatterasNetworks.com>, <glen.kramer@teknovus.com>,
        "Lior khermosh" <lior.khermosh@passave.com>, <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

> > > >    eponDeviceTemperatureEventIndicationState
> > > >    eponDeviceTemperatureEventIndicationEnabled
> > > >    eponDevicePowerVoltageEventIndicationState
> > > >    eponDevicePowerVoltageEventIndicationEnabled
>=20
> Where are these objects reflected in the management clause of=20
> 802.3ah?  I'm not a fan of adding new things at this stage of=20
> the game.  Temp and voltage measurements and events aren't=20
> generally within the purview of 802.3.  =20
>=20

I agree with Glen and Matt, although reflecting the objects from the =
management clause of 802.3ah is not a requirement. I made the comment at =
IETF-59 that RFC 3433 (Entity Sensor MIB) would be a better solution for =
temperature and voltage indication.=20

Regards,

Dan
(speaking as contributor)

 =20
>=20

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


From hubmib-bounces@ietf.org  Tue Jan 11 02:05:46 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15441
	for <hubmib-archive@lists.ietf.org>; Tue, 11 Jan 2005 02:05:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoG1I-0000Fb-UH; Tue, 11 Jan 2005 02:00:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoG08-00086j-2m
	for hubmib@megatron.ietf.org; Tue, 11 Jan 2005 01:59:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09100
	for <hubmib@ietf.org>; Tue, 11 Jan 2005 01:59:34 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CoGDp-0005bq-QV
	for hubmib@ietf.org; Tue, 11 Jan 2005 02:13:49 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	4-0688056764; Tue, 11 Jan 2005 01:59:25 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: <glen.kramer@teknovus.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 11 Jan 2005 08:59:06 +0200
Message-ID: <080501c4f7ab$0cbfef30$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Glen,
We do not have any fundamental agreement. The EPON MIB objects document
is not trying to duplicate all objects from other MIBs and it tries to
fill what the author considered as missing from that for an EPON device.
Such an equipment usually uses many many protocols and higher layer
applications and I believe each one is needed to be covered by its own
MIB objects. So that if it is needed for a device to be a bridge then it
should rely on using the bridge MIB objects.
I think that this state of mind is clearly presented at the beginning of
the document. 
Please note however that the EPON has its special properties so if there
is needed a special consideration due to that, then I think it should be
in this MIB document. Obviously we will find it in objects which are on
the boundary of the L2 EPON. That is why considerations and issues so
often come regarding bridge MIB objects.

Please note that some device MIB objects documents of other standards
(not IEEE) used different approach and did try to define much more - for
instance DOCSIS (RFC2669). In such a document you can find for instance
IP addresses for the devices and reference to services. I think I
clearly do not take this approach in this document.

As for your specific point. You are assuming here that the ONU is a
bridge and therefore holding the 802.1D bridge MIB objects. I tried to
avoid the assumption of this specific implementation in the ONU. 
I think that in order to cover the items described in the MPCP spec
which include description of queues for transmission and reporting we
need these counters and can not assume that they are covered by other
MIB objects.

Lior
  
 


-----Original Message-----
From: Glen Kramer [mailto:glen.kramer@teknovus.com] 
Sent: Tuesday, January 11, 2005 1:31 AM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments


Lior,

I think we have a fundamental disagreement on the scope of this
document. I argue that this MIB should only include EPON-specific
objects, i.e., objects that you would not find in any other MIB. This
would include statistics for MPCP messages, LLIDs, and so on. I believe
that EPON devices should implement multiple MIBs: OAM MIB, Bridging MIB,
and EPON-specific MIB. It seems to me that your approach is to define a
single MIB that would include (or duplicate) all objects that *MAY BE*
used in EPON, even though these objects may already have been defined
elsewhere. 

For example, counters of transmitted, received, and dropped frames per
queue are not EPON-specific. Any port (according to 802.1D) may have up
to 8 queues behind it and would count these statistics. I don't think
these objects belong to EPON-specific MIB.

Before further discussing specific comments, I'd like to ask for a
clarification from the task force on the scope of this document.

Regards,
Glen

> -----Original Message-----
> From: Lior khermosh [mailto:lior.khermosh@passave.com]
> Sent: Wednesday, January 05, 2005 11:08 PM
> To: glen.kramer@teknovus.com; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> [LK] of course it does not refer to the counters. It refers to the 
> queues. The counters are an outcome of these entities. As indeed you 
> say they are useful parameters. As it is not defined in the EFM MIB 
> objects I added them to the device MIB objects.
> 
> 
> -----Original Message-----
> From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On 
> Behalf Of Glen Kramer
> Sent: Wednesday, January 05, 2005 3:25 AM
> To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> Subject: RE: [Hubmib] FW: EPON MIB comments
> 
> 
> [GK] Objects eponDeviceStatTxFramesQueue[0-7], 
> eponDeviceStatRxFramesQueue[0-7], and 
> eponDeviceStatDroppedFramesQueue[0-7]
> are not specific to EPON. These objects exist for other devices, such 
> as bridge ports. There is no need to duplicate these objects here. 
> Besides, neither 802.3ah nor 802.1D standards require exactly 8 queues

> to be implemented. I recommend removing these objects.
> 
> [LK] The report message in the MPCP refers to such entities. Please 
> see section 64.3.6.2 for report message format. These counters refer 
> to that.
> 
> [GK] The REPORT message does not refer directly of indirectly to any 
> such entities. I attached the clause 64.3.6.2. Would appreciate if you

> could point where and how this clause refers to count of transmitted, 
> received, and dropped frames. I agree that these are useful 
> parameters. But my point is that they are already defined and are not 
> EPON-specific. There is no need to duplicate them in this MIB.
> 
> Regards,
> Glen
> 



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


From hubmib-bounces@ietf.org  Tue Jan 11 15:21:27 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23380
	for <hubmib-archive@lists.ietf.org>; Tue, 11 Jan 2005 15:21:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoSUK-0007Xq-AH; Tue, 11 Jan 2005 15:19:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoSTC-00079d-CW
	for hubmib@megatron.ietf.org; Tue, 11 Jan 2005 15:18:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23005
	for <hubmib@ietf.org>; Tue, 11 Jan 2005 15:18:24 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CoSh2-0005i4-FL
	for hubmib@ietf.org; Tue, 11 Jan 2005 15:32:47 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	4-0638564684; Tue, 11 Jan 2005 15:18:07 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: "'Matt Squire'" <MSquire@HatterasNetworks.com>,
        "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
        <glen.kramer@teknovus.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 11 Jan 2005 22:17:46 +0200
Message-ID: <082b01c4f81a$9faf9920$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <8052E2EA753D144EB906B7A7AA399714032868B3@mailserv.hatteras.com>
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdeeb24e6b743a852c396a4af0e53c8f
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

My comments are in the text.


-----Original Message-----
From: Matt Squire [mailto:MSquire@HatterasNetworks.com] 
Sent: Tuesday, January 11, 2005 3:28 AM
To: Romascanu, Dan (Dan); glen.kramer@teknovus.com; Lior khermosh;
hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments



My comments are dispersed throughout.   

> Lior, Matt, other,
> 
> Please comment.
> 
> Regards,
> 
> Dan
> 
> 
> 
> > -----Original Message-----
> > From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> > Sent: 11 January, 2005 2:29 AM
> > To: Romascanu, Dan (Dan); 'Lior khermosh'; hubmib@ietf.org
> > Subject: RE: [Hubmib] FW: EPON MIB comments
> > 
> > 
> > Dan,
> > 
> > Thanks for your response. I didn't try to enforce one-to-one
> > correspondence
> > with IEEE spec. But there are attributes defined in EPON MIB 
> > now that are
> > applicable to non-EPON devices. For example, TxFrames, RxFrames, and
> > DropFrames counters (see end of this e-mail) are attributes 
> > of any 802.1D
> > port. 

Counters in .1D are defined to reflect operation at the 802.1 level -
counters in the .3 MIBs should reflect behavior at the .3 level.
Although both may define "DropFrames", the dropping point and therefore
the actual semantics of the counter would be different.  I'm not arguing
that EPON needs or does not need a DropFrame counter, only that if it
does define one, it has nothing to do with the 802.1D DropFrame counter.


[Lior] Please see other mail.

> > Another example is alarm related attributes:
> > >    eponDeviceDyingGaspAlarmState
> > >    eponDeviceDyingGaspAlarmEnabled
> > >    eponDeviceCriticalEventState
> > >    eponDeviceCriticalEventEnabled
> > >    eponDeviceLocalLinkFaultAlarmState
> > >    eponDeviceLocalLinkFaultAlarmEnabled

In the first revision of the OAM MIB, these states were directly
reflected.  In the -02 revision, all event information was shoved into a
new "EventLog" table.  So transition in these are flags are reflected
there.  I can add them back as separate objects, I just don't want to go
back and forth.  In the transition to the -02 version, the
enable/disable of the events reflected in flags was <stupidly> removed.
Can add that back as removing it was unintentional.  

[Lior] Then I will remove from the EPON device MIB objects.

> > >    eponDeviceTemperatureEventIndicationState
> > >    eponDeviceTemperatureEventIndicationEnabled
> > >    eponDevicePowerVoltageEventIndicationState
> > >    eponDevicePowerVoltageEventIndicationEnabled

Where are these objects reflected in the management clause of 802.3ah?
I'm not a fan of adding new things at this stage of the game.  Temp and
voltage measurements and events aren't generally within the purview of
802.3.   

> > >    eponDeviceGlobalEventState
> > >    eponDeviceGlobalEventEnabled
> > >    eponDeviceErroredSymbolPeriodEventState
> > >    eponDeviceErroredSymbolPeriodEventEnabled
> > >    eponDeviceErroredFrameEventState
> > >    eponDeviceErroredFrameEventEnabled
> > >    eponDeviceErroredFramePeriodEventState
> > >    eponDeviceErroredFramePeriodEventEnabled
> > >    eponDeviceErroredFrameSecondsSummaryEventState
> > >    eponDeviceErroredFrameSecondsSummaryEventEnabled

The configuration (enable/disable/thresholds/etc.) are covered in the
dot3OamEventConfigTable, so I don't see any benefit/need for change from
these - we got 'em.  
[Lior] Then I will remove from the EPON device MIB objects.

> > >    eponDeviceOrganizationSpecificEventState
> > >    eponDeviceOrganizationSpecificEventEnabled

The thought was controls like these weren't useful.  There can be a
plethora of organization specific events from a group of different
organizations.  IMHO, each organization should define their controls as
one switch doesn't cover all, at least not well.  

[Lior] I tend to agree with this argument I will remove from the EPON
device MIB objects.

> > >    eponDeviceEventControl
> > 
> > These objects are equally applicable to point-to-point fiber
> > links or copper
> > links. I believe they should be moved to OAM MIB. 
> > 
> > Regards,
> > Glen
> > 
> > > -----Original Message-----
> > > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > > Sent: Monday, January 10, 2005 3:46 PM
> > > To: glen.kramer@teknovus.com; Lior khermosh; hubmib@ietf.org
> > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > 
> > > Glen,
> > > 
> > > The focus of the EPON MIB  work is on defining management
> > objects for EPON
> > > networks. This does not mean however providing a one-to-one
> > mapping to the
> > > management attributes defined by the IEEE spec. According
> > to the case we
> > > may define less, the same or more objects than the ones
> > defined by the
> > > IEEE spec. We can even in some cases define objects that
> > are not EPON
> > > specific, if they are helpful and the common management
> > practice is to use
> > > them in the management of EPONs. This should however be rather the

> > > exception, and if the non-EPON objects become a consistent
> > part of the
> > > overall work I would recommend defining a separate MIB
> > module. Duplication
> > > is generally considered a bad practice but please be more
> > specific about
> > > what objects you consider being already covered in other
> > standard MIBs.
> > > 
> > > Regards,
> > > 
> > > Dan
> > > (Speaking as chair)
> > > 
> > > 
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Glen Kramer [mailto:glen.kramer@teknovus.com]
> > > > Sent: 11 January, 2005 1:31 AM
> > > > To: 'Lior khermosh'; Romascanu, Dan (Dan); hubmib@ietf.org
> > > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > >
> > > >
> > > > Lior,
> > > >
> > > > I think we have a fundamental disagreement on the scope of this 
> > > > document. I argue that this MIB should only include 
> > > > EPON-specific objects, i.e., objects
> > > > that you would not find in any other MIB. This would include
> > > > statistics for
> > > > MPCP messages, LLIDs, and so on. I believe that EPON 
> > devices should
> > > > implement multiple MIBs: OAM MIB, Bridging MIB, and
> > EPON-specific MIB.
> > > > It seems to me that your approach is to define a single
> > MIB that would
> > > > include (or duplicate) all objects that *MAY BE* used in EPON, 
> > > > even though these objects may already have been defined 
> > > > elsewhere.
> > > >
> > > > For example, counters of transmitted, received, and dropped 
> > > > frames per queue are not EPON-specific. Any port (according to 
> > > > 802.1D) may
> > have up to 8
> > > > queues behind it and would count these statistics. I
> > don't think these
> > > > objects belong to EPON-specific MIB.
> > > >
> > > > Before further discussing specific comments, I'd like
> to ask for a
> > > > clarification from the task force on the scope of this document.
> > > >
> > > > Regards,
> > > > Glen
> > > >
> > > > > -----Original Message-----
> > > > > From: Lior khermosh [mailto:lior.khermosh@passave.com]
> > > > > Sent: Wednesday, January 05, 2005 11:08 PM
> > > > > To: glen.kramer@teknovus.com; 'Romascanu, Dan (Dan)';
> > > > hubmib@ietf.org
> > > > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > > >
> > > > > [LK] of course it does not refer to the counters. It
> > refers to the
> > > > > queues. The counters are an outcome of these entities. As 
> > > > > indeed you say they are useful parameters. As it is not
> > > > defined in
> > > > > the EFM MIB objects I added them to the device MIB objects.
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: hubmib-bounces@ietf.org
> > > > [mailto:hubmib-bounces@ietf.org] On Behalf
> > > > > Of Glen Kramer
> > > > > Sent: Wednesday, January 05, 2005 3:25 AM
> > > > > To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; hubmib@ietf.org
> > > > > Subject: RE: [Hubmib] FW: EPON MIB comments
> > > > >
> > > > >
> > > > > [GK] Objects eponDeviceStatTxFramesQueue[0-7], 
> > > > > eponDeviceStatRxFramesQueue[0-7], and 
> > > > > eponDeviceStatDroppedFramesQueue[0-7]
> > > > > are not specific to EPON. These objects exist for other
> > > > devices, such as
> > > > > bridge ports. There is no need to duplicate these objects
> > > > here. Besides,
> > > > > neither 802.3ah nor 802.1D standards require exactly 8
> > queues to be
> > > > > implemented. I recommend removing these objects.
> > > > >
> > > > > [LK] The report message in the MPCP refers to such
> > > > entities. Please see
> > > > > section 64.3.6.2 for report message format. These
> > counters refer to
> > > > > that.
> > > > >
> > > > > [GK] The REPORT message does not refer directly of
> > indirectly to any
> > > > > such entities. I attached the clause 64.3.6.2. Would
> > > > appreciate if you
> > > > > could point where and how this clause refers to count of
> > > > transmitted,
> > > > > received, and dropped frames.
> > > > > I agree that these are useful parameters. But my point is
> > > > that they are
> > > > > already defined and are not EPON-specific. There is no need
> > > > to duplicate
> > > > > them in this MIB.
> > > > >
> > > > > Regards,
> > > > > Glen
> > > > >
> > > >
> > > >
> > > >
> > > >
> > 
> > 
> > 
> 


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


From hubmib-bounces@ietf.org  Tue Jan 11 15:24:52 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23666
	for <hubmib-archive@lists.ietf.org>; Tue, 11 Jan 2005 15:24:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoSWU-0000XG-5l; Tue, 11 Jan 2005 15:21:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoSUh-0007iX-Af
	for hubmib@megatron.ietf.org; Tue, 11 Jan 2005 15:20:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23254
	for <hubmib@ietf.org>; Tue, 11 Jan 2005 15:19:57 -0500 (EST)
Received: from mail14a.g14.rapidsite.net ([128.121.64.70])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CoSiW-0005kH-TD
	for hubmib@ietf.org; Tue, 11 Jan 2005 15:34:20 -0500
Received: from mxw1400.sanjose14-verio.com (128.121.143.19)
	by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id
	2-1655604757; Tue, 11 Jan 2005 15:19:54 -0500 (EST)
From: "Lior khermosh" <lior.khermosh@passave.com>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
        "'Matt Squire'" <MSquire@HatterasNetworks.com>,
        <glen.kramer@teknovus.com>, <hubmib@ietf.org>
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Tue, 11 Jan 2005 22:19:00 +0200
Message-ID: <086101c4f81a$df98aea0$2b0b0b0b@passave.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9FE6@is0004avexu1.global.avaya.com>
Importance: Normal
X-Loop-Detect: 1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: 7bit

My comments are in the text.

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
Sent: Tuesday, January 11, 2005 3:42 AM
To: Matt Squire; glen.kramer@teknovus.com; Lior khermosh;
hubmib@ietf.org
Subject: RE: [Hubmib] FW: EPON MIB comments


> > > >    eponDeviceTemperatureEventIndicationState
> > > >    eponDeviceTemperatureEventIndicationEnabled
> > > >    eponDevicePowerVoltageEventIndicationState
> > > >    eponDevicePowerVoltageEventIndicationEnabled
> 
> Where are these objects reflected in the management clause of
> 802.3ah?  I'm not a fan of adding new things at this stage of 
> the game.  Temp and voltage measurements and events aren't 
> generally within the purview of 802.3.   
> 

I agree with Glen and Matt, although reflecting the objects from the
management clause of 802.3ah is not a requirement. I made the comment at
IETF-59 that RFC 3433 (Entity Sensor MIB) would be a better solution for
temperature and voltage indication. 

[Lior] Dan. Thanks for the detailed comment. I will verify the coverage
and remove the objects from the EPON device MIB and create a reference
instead.


Regards,

Dan
(speaking as contributor)

  
> 


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


From hubmib-bounces@ietf.org  Tue Jan 11 16:41:19 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06754
	for <hubmib-archive@lists.ietf.org>; Tue, 11 Jan 2005 16:41:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoT9W-00083s-5j; Tue, 11 Jan 2005 16:02:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoT2J-0002eD-TA
	for hubmib@megatron.ietf.org; Tue, 11 Jan 2005 15:54:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27060
	for <hubmib@ietf.org>; Tue, 11 Jan 2005 15:54:41 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoTGB-00073L-KH
	for hubmib@ietf.org; Tue, 11 Jan 2005 16:09:05 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0BKjOqm002792
	for <hubmib@ietf.org>; Tue, 11 Jan 2005 15:45:24 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0BKjMqm002696
	for <hubmib@ietf.org>; Tue, 11 Jan 2005 15:45:23 -0500 (EST)
content-class: urn:content-classes:message
Subject: RE: [Hubmib] FW: EPON MIB comments
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 11 Jan 2005 22:54:37 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E3082F@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] FW: EPON MIB comments
Thread-Index: AcTzvnxr5/hRWDL4QiWluekD8Ui5fADrEnQQAACppOAAAP3TEAAA8fHAAADs9dAAKZeOEA==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Matt Squire" <MSquire@HatterasNetworks.com>, <glen.kramer@teknovus.com>,
        "Lior khermosh" <lior.khermosh@passave.com>, <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: quoted-printable
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

> -----Original Message-----
> From: Matt Squire [mailto:MSquire@HatterasNetworks.com]
> > > Another example is alarm related attributes:
> > > >    eponDeviceDyingGaspAlarmState
> > > >    eponDeviceDyingGaspAlarmEnabled
> > > >    eponDeviceCriticalEventState
> > > >    eponDeviceCriticalEventEnabled
> > > >    eponDeviceLocalLinkFaultAlarmState
> > > >    eponDeviceLocalLinkFaultAlarmEnabled
>=20
> In the first revision of the OAM MIB, these states were=20
> directly reflected.  In the -02 revision, all event=20
> information was shoved into a new "EventLog" table.  So=20
> transition in these are flags are reflected there.  I can add=20
> them back as separate objects, I just don't want to go back=20
> and forth.  In the transition to the -02 version, the=20
> enable/disable of the events reflected in flags was=20
> <stupidly> removed.  Can add that back as removing it was=20
> unintentional. =20

unintentional - maybe
stupid - I am not so sure :-)

The Alarm MIB (RFC 3877) can be used to define the alarms, their =
severity status, and also defines a log. We can consider using it, the =
balance being between the overhead of supporting the full Alarm MIB vs. =
the benefit of avoiding duplication.

Regards,

Dan


>=20

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


From hubmib-bounces@ietf.org  Sun Jan 16 21:43:42 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08390
	for <hubmib-archive@lists.ietf.org>; Sun, 16 Jan 2005 21:43:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqMlB-0001Fv-3a; Sun, 16 Jan 2005 21:36:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CqMel-0000jG-AU
	for hubmib@megatron.ietf.org; Sun, 16 Jan 2005 21:30:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07926
	for <hubmib@ietf.org>; Sun, 16 Jan 2005 21:30:13 -0500 (EST)
Received: from mailserv.hatterasnetworks.com ([63.89.58.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqMti-00080x-Tx
	for hubmib@ietf.org; Sun, 16 Jan 2005 21:45:43 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] FW: EPON MIB comments
Date: Sun, 16 Jan 2005 15:37:39 -0500
Message-ID: <8052E2EA753D144EB906B7A7AA39971402A3B8C9@mailserv.hatteras.com>
Thread-Topic: [Hubmib] FW: EPON MIB comments
Thread-Index: AcTzvnxr5/hRWDL4QiWluekD8Ui5fADrEnQQAACppOAAAP3TEAAA8fHAAADs9dAAKZeOEAD6zj+w
From: "Matt Squire" <MSquire@HatterasNetworks.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, <glen.kramer@teknovus.com>,
        "Lior khermosh" <lior.khermosh@passave.com>, <hubmib@ietf.org>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable


> > > > Another example is alarm related attributes:
> > > > >    eponDeviceDyingGaspAlarmState
> > > > >    eponDeviceDyingGaspAlarmEnabled
> > > > >    eponDeviceCriticalEventState
> > > > >    eponDeviceCriticalEventEnabled
> > > > >    eponDeviceLocalLinkFaultAlarmState
> > > > >    eponDeviceLocalLinkFaultAlarmEnabled
> >=20
> > In the first revision of the OAM MIB, these states were=20
> > directly reflected.  In the -02 revision, all event=20
> > information was shoved into a new "EventLog" table.  So=20
> > transition in these are flags are reflected there.  I can add=20
> > them back as separate objects, I just don't want to go back=20
> > and forth.  In the transition to the -02 version, the=20
> > enable/disable of the events reflected in flags was=20
> > <stupidly> removed.  Can add that back as removing it was=20
> > unintentional. =20
>=20
> unintentional - maybe
> stupid - I am not so sure :-)
>=20
> The Alarm MIB (RFC 3877) can be used to define the alarms,=20
> their severity status, and also defines a log. We can=20
> consider using it, the balance being between the overhead of=20
> supporting the full Alarm MIB vs. the benefit of avoiding duplication.

We talked about this a little bit at one of the IETF meetings a while =
back.  I had some simple "event status" objects defined at the time, and =
EPON had defined its own little event log.  The sense of the group was =
that I should EPON and OAM should define their own little event logs =
rather then try to leverage the alarm log. =20

>From my notes (which I think were turned into your minutes): =20
"
6) Event status table.  Currently, event information is stored as a TLV =
(e.g. an octet array).  The individual field are not pulled out and =
exposed.  A question was raised as to whether this is good or bad.  The =
positive aspects are that it results in fewer fields, but on the other =
side, the fields are probably useful and need to be exposed for a =
manager.  There seemed to be consensus that the fields should be pulled =
out of the TLV.  Also that we should be able to create a generic event =
table rather than one row per event type.
"

Hence we are where we are. =20

- Matt =20

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


From hubmib-bounces@ietf.org  Wed Jan 19 11:58:46 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28225
	for <hubmib-archive@lists.ietf.org>; Wed, 19 Jan 2005 11:58:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrJ8x-0004sD-OL; Wed, 19 Jan 2005 11:57:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CrJ0W-00030n-7U
	for hubmib@megatron.ietf.org; Wed, 19 Jan 2005 11:48:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27544
	for <hubmib@ietf.org>; Wed, 19 Jan 2005 11:48:33 -0500 (EST)
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrJG0-0007Ez-Ux
	for hubmib@ietf.org; Wed, 19 Jan 2005 12:04:37 -0500
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0JGkUFe027297
	for <hubmib@ietf.org>; Wed, 19 Jan 2005 11:46:30 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0JGkKFe026992
	for <hubmib@ietf.org>; Wed, 19 Jan 2005 11:46:24 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 19 Jan 2005 18:48:21 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E308F9@is0004avexu1.global.avaya.com>
Thread-Topic: Comments on draft-ietf-hubmib-efm-mib-02.txt
Thread-Index: AcT+Rq7+OgqQIP4uRvWcLyWf1HcPFw==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 54f716cba2c98b25bc07e094cc18394c
Subject: [Hubmib] Comments on draft-ietf-hubmib-efm-mib-02.txt
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="===============1530731044=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1530731044==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4FE46.AF3BC6C3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4FE46.AF3BC6C3
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Here are my comments on draft-ietf-hubmib-efm-mib-02.txt. This document =
being in Last Call, all comments need to be taken into consideration, =
including the minor ones the comments editorial in nature.=20

First running idnits we get the following:

tmp/draft-ietf-hubmib-efm-mib-02.txt:

tmp/draft-ietf-hubmib-efm-mib-02.txt(319): Line has weird spacing: =
'...ficInfo   dot3...'
tmp/draft-ietf-hubmib-efm-mib-02.txt(325): Line has weird spacing: =
'...ationTx  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-02.txt(326): Line has weird spacing: =
'...ationRx  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-02.txt(347): Line has weird spacing: =
'...dConfig    dot...'
tmp/draft-ietf-hubmib-efm-mib-02.txt(355): Line has weird spacing: =
'...dConfig  dot3O...'
tmp/draft-ietf-hubmib-efm-mib-02.txt(1691): Line has weird spacing: =
'...smitted  on th...'

  Checking nits according to http://www.ietf.org/ID-Checklist.html :

    Checking conformance with RFC 3667/3668 boilerplate...
  * The document claims conformance with section 10 of RFC 2026, but =
uses
    some RFC 3667/3668 boilerplate.  As RFC 3667/3668 replaces section =
10 of RFC
    2026, you should not claim conformance with it if you have changed =
to using
    RFC 3667/3668 boilerplate.
  * The document seems to lack an RFC 3667 Section 5.1 IPR Disclosure
    Acknowledgement  -- however, there's a paragraph with a matching =
beginning.
    Boilerplate error?

  (Expected a match on the following text:=20
    "By submitting this Internet-Draft, each author represents that any
    applicable patent or other IPR claims of which he or she is aware
    have been or will be disclosed, and any of which he or she becomes
    aware will be disclosed, in accordance with Section 6 of RFC 3668."

   ... but found this:
    "By submitting this Internet-Draft, I certify that any applicable
    patent or other IPR claims of which I am aware have been disclosed,
    or will be disclosed, and any of which I become aware will be
    disclosed, in accordance with   RFC 3668 [RFC3668].")


  * The document seems to lack an RFC 3668 Section 5, para 3 IPR =
Disclosure
    Invitation -- however, there's a paragraph with a matching =
beginning.
    Boilerplate error?

  (Expected a match on the following text:=20
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at
    ietf-ipr@ietf.org."

   ... but found this:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    EFM OAM MIB                 October 2004")

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt =
:

  * The document seems to lack a 1id_guidelines paragraph about
    Internet-Drafts being working documents -- however, there's a =
paragraph with
    a matching beginning. Boilerplate error?

  (Expected a match on the following text:=20
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as =
Internet-Drafts."

   ... but found this:
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet =
Drafts.")

More:

Technical

T1. I do not agree with the assertion made in the Security Consideration =
section that the read-write objects defined in this MIB module do not =
impact the users traffic, because they are only controls of the OAM =
protocol. For example the dot3OamLoopbackCommand object, puts the link =
on loopback mode. Even if there is another object that allows for the =
remote device to ignore the loopback commands, this does not help if the =
loopback command objects are activated in an improper manner. Also, an =
object like dot3OamAdminState if set to disabled(1) will cut-off the OAM =
functionality of the device, which does have a negative impact on the =
network behavior and can be considered as a possible source of attack. I =
would suggest that the editor makes another pass through the read-write =
objects and explicitly describes all the potential security hazard =
resulting from inadequate write operations on these objects.=20
T2. What is the DEFAULT value of read-write objects like =
dot3OamAdminState and dot3OamMode? You need to describe the desired =
behavior of the agent at initialization before the first SetRequest =
command
T3 In the Security section: 'By default, OAM is disabled on =
Ethernet-likeEthernet like interfaces and is therefore not a risk.' =
First there is an editorial problem (repeated words). Second, there may =
be a technical issue. As far as I remember from my participation in the =
EFM work, there is no interdiction in the standard to apply OAM to a =
non-EFM Ethernet interface. Did this change in the latest part of the =
work, when my attendance became rare? =20




Editorial

E1. The expiration date on the footer of all pages excepting the first =
is longer than the accepted six months period.
E2. Section 3.1 - last phrase '...notifications into within the SNMP =
...' needs to be fixed
E3.  Section 3.2, second paragraph - no need to capitalize DOES NOT
E4. Section 4, second phrase - replace 'affects' by 'effects'
E5. Section 4.1 - 'Ethernet-like' is duplicated
E6. Section 4.2 - correct 'ThisThe' in the first phrase
E7. Titles of Section 4 - replace 'MIBs' with 'MIB modules'
E8. First phrase of 4.2 - replace 'MIBs' by 'MIB modules' and MIB =
document'' by 'MIB module'
E9. Numbering of subsections 4.24.3 and 4.34.4 is broken
E10. Last phrase in 4.34.4 - replace 'MIB' by 'MIB module', decide about =
'waymanner'
E11. I would strongly recommend to add UNITS clauses for all objects =
where these apply, especially for counters
E12. No need for something like  REFERENCE   "N/A". If there is no =
reference, there is no reference clause.
E13 Avoid using Traps, even in object names (dot3OamTraps, =
dot3OamTrapsPrefix, etc.)=20
E14 Some characters seem to have been corrupted when copied to the =
[802.3ah reference] =20



Regards,

Dan



------_=_NextPart_001_01C4FE46.AF3BC6C3
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.6603.0">
<TITLE>Comments on draft-ietf-hubmib-efm-mib-02.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Here are my comments on =
draft-ietf-hubmib-efm-mib-02.txt. This document being in Last Call, all =
comments need to be taken into consideration, including the minor ones =
the comments editorial in nature. </FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">First running idnits we get =
the following:</FONT></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">tmp/draft-ietf-hubmib-efm-mib-02.txt:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">tmp/draft-ietf-hubmib-efm-mib-02.txt(319): Line has weird spacing: =
'...ficInfo&nbsp;&nbsp; dot3...'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">tmp/draft-ietf-hubmib-efm-mib-02.txt(325): Line has weird spacing: =
'...ationTx&nbsp; dot3O...'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">tmp/draft-ietf-hubmib-efm-mib-02.txt(326): Line has weird spacing: =
'...ationRx&nbsp; dot3O...'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">tmp/draft-ietf-hubmib-efm-mib-02.txt(347): Line has weird spacing: =
'...dConfig&nbsp;&nbsp;&nbsp; dot...'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">tmp/draft-ietf-hubmib-efm-mib-02.txt(355): Line has weird spacing: =
'...dConfig&nbsp; dot3O...'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">tmp/draft-ietf-hubmib-efm-mib-02.txt(1691): Line has weird spacing: =
'...smitted&nbsp; on th...'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; Checking nits according to <A =
HREF=3D"http://www.ietf.org/ID-Checklist.html">http://www.ietf.org/ID-Che=
cklist.html</A> :</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; Checking conformance with RFC 3667/3668 =
boilerplate...</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; * The document claims conformance with section 10 of RFC =
2026, but uses</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; some RFC 3667/3668 boilerplate.&nbsp; As RFC =
3667/3668 replaces section 10 of RFC</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; 2026, you should not claim conformance with it if =
you have changed to using</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; RFC 3667/3668 boilerplate.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; * The document seems to lack an RFC 3667 Section 5.1 IPR =
Disclosure</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; Acknowledgement&nbsp; -- however, there's a =
paragraph with a matching beginning.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; Boilerplate error?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; (Expected a match on the following text: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; &quot;By submitting this Internet-Draft, each =
author represents that any</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; applicable patent or other IPR claims of which he =
or she is aware</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; have been or will be disclosed, and any of which =
he or she becomes</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; aware will be disclosed, in accordance with =
Section 6 of RFC 3668.&quot;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp; ... but found this:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; &quot;By submitting this Internet-Draft, I =
certify that any applicable</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; patent or other IPR claims of which I am aware =
have been disclosed,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; or will be disclosed, and any of which I become =
aware will be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; disclosed, in accordance with&nbsp;&nbsp; RFC =
3668 [RFC3668].&quot;)</FONT></SPAN></P>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; * The document seems to lack an RFC 3668 Section 5, para 3 =
IPR Disclosure</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; Invitation -- however, there's a paragraph with a =
matching beginning.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; Boilerplate error?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; (Expected a match on the following text: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; &quot;The IETF invites any interested party to =
bring to its attention any</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; copyrights, patents or patent applications, or =
other proprietary</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; rights that may cover technology that may be =
required to implement</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; this standard.&nbsp; Please address the =
information to the IETF at</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; ietf-ipr@ietf.org.&quot;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp; ... but found this:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; &quot;The IETF invites any interested party to =
bring to its attention any</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; copyrights, patents or patent applications, or =
other proprietary</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; rights that may cover technology that may be =
required to implement</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; EFM OAM =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; October 2004&quot;)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; Checking nits according to <A =
HREF=3D"http://www.ietf.org/ietf/1id-guidelines.txt">http://www.ietf.org/=
ietf/1id-guidelines.txt</A> :</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; * The document seems to lack a 1id_guidelines paragraph =
about</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; Internet-Drafts being working documents -- =
however, there's a paragraph with</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; a matching beginning. Boilerplate =
error?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp; (Expected a match on the following text: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; &quot;Internet-Drafts are working documents of =
the Internet Engineering</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; Task Force (IETF), its areas, and its working =
groups.&nbsp; Note that</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; other groups may also distribute working =
documents as Internet-Drafts.&quot;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp; ... but found this:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; &quot;Internet-Drafts are working documents of =
the Internet Engineering</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; Task Force (IETF), its areas, and its working =
groups.&nbsp; Note that</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">&nbsp;&nbsp;&nbsp; other groups may also distribute working =
documents as Internet Drafts.&quot;)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">More:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Technical</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">T1. I do =
not agree with the assertion made in the Security Consideration section =
that the read-write objects defined in this MIB module do not impact the =
users traffic, because they are only controls of the OAM protocol. For =
example</FONT> <FONT SIZE=3D2 FACE=3D"Arial">the</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">dot3OamLoopbackCommand =
object</FONT></SPAN><SPAN LANG=3D"he"></SPAN><SPAN LANG=3D"he"><FONT =
SIZE=3D2 FACE=3D"Arial">, puts the link on loopback mode. Even if there =
is another object that allows for the remote device to ignore the =
loopback commands, this does not help if the loopback command objects =
are activated in an improper manner. Also, an object like =
dot3OamAdminState if set to disabled(1) will cut-off the OAM =
functionality of the device, which does have a negative impact on the =
network behavior and can be considered as a possible source of attack. I =
would suggest that the editor makes another pass through the read-write =
objects and explicitly describes all the potential security hazard =
resulting from inadequate write operations on these objects. =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">T2. What is =
the DEFAULT value of read-write objects like dot3OamAdminState and =
dot3OamMode? You need to describe the desired behavior of the agent at =
initialization before the first SetRequest command</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">T3 In the =
Security section:</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">'</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">By default, OAM is disabled on Ethernet-likeEthernet like =
interfaces and is therefore not a risk.' First there is an editorial =
problem (repeated words). Second, there may be a technical issue. As far =
as I remember from my participation in the EFM work, there is no =
interdiction in the standard to apply OAM to a non-EFM Ethernet =
interface. Did this change in the latest part of the work, when my =
attendance became rare?</FONT>&nbsp;<FONT SIZE=3D2 FACE=3D"Courier New"> =
</FONT></SPAN></P>
<BR>
<BR>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Editorial</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E1. The =
expiration date on the footer of all pages excepting the first is longer =
than the accepted six months period.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E2. Section =
3.1 - last phrase '...</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">notifications into =
within the SNMP</FONT></SPAN><SPAN LANG=3D"he"></SPAN><SPAN =
LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial"> ...' needs to be =
fixed</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E3.&nbsp; =
Section 3.2, second paragraph - no need to capitalize DOES =
NOT</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E4. Section =
4, second phrase - replace 'affects' by 'effects'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E5. Section =
4.1 - 'Ethernet-like' is duplicated</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E6. Section =
4.2 - correct 'ThisThe' in the first phrase</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E7. Titles =
of Section 4 - replace 'MIBs' with 'MIB modules'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E8. First =
phrase of 4.2 - replace 'MIBs' by 'MIB modules' and MIB document'' by =
'MIB module'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E9. =
Numbering of subsections 4.24.3 and 4.34.4 is broken</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E10. Last =
phrase in 4.34.4 - replace 'MIB' by 'MIB module', decide about =
'waymanner'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E11. I =
would strongly recommend to add UNITS clauses for all objects where =
these apply, especially for counters</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">E12. No =
need for something like</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Courier New"></FONT> <FONT =
SIZE=3D2 FACE=3D"Arial">REFERENCE&nbsp;&nbsp; &quot;N/A&quot;. If there =
is no reference, there is no reference clause.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">E13 =
Avoid using Traps, even in object names (dot3OamTraps, =
dot3OamTrapsPrefix, etc.) </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">E14 Some =
characters seem to have been corrupted when copied to the [802.3ah =
reference]</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp; =
</FONT></SPAN></P>
<BR>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C4FE46.AF3BC6C3--


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

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

--===============1530731044==--



From hubmib-bounces@ietf.org  Thu Jan 20 04:57:09 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11555
	for <hubmib-archive@lists.ietf.org>; Thu, 20 Jan 2005 04:57:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrZ0g-0006TG-S4; Thu, 20 Jan 2005 04:53:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CrYxu-00064H-EO
	for hubmib@megatron.ietf.org; Thu, 20 Jan 2005 04:50:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10961
	for <hubmib@ietf.org>; Thu, 20 Jan 2005 04:50:56 -0500 (EST)
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrZDX-00014h-Uu
	for hubmib@ietf.org; Thu, 20 Jan 2005 05:07:09 -0500
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0K9mqFe029138
	for <hubmib@ietf.org>; Thu, 20 Jan 2005 04:48:52 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0K9mkFe028981
	for <hubmib@ietf.org>; Thu, 20 Jan 2005 04:48:47 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 20 Jan 2005 11:50:47 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E30908@is0004avexu1.global.avaya.com>
Thread-Topic: No hubmib meeting in Minneapolis
Thread-Index: AcT+1YRRFKjXn+D+Qh+g9DpMsOoJCA==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Subject: [Hubmib] No hubmib meeting in Minneapolis
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="===============0113827151=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0113827151==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4FED5.844C4F2E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4FED5.844C4F2E
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I did not receive any answers to the my query about a possible hubmib =
meeting in Minneapolis. My conclusion is that there is no interest to do =
it, and that we will resolve all our pending charter items by work on =
the e-mail list.=20

Regards,

Dan



------_=_NextPart_001_01C4FED5.844C4F2E
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.6603.0">
<TITLE>No hubmib meeting in Minneapolis</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">I did not receive any answers =
to the my query about a possible hubmib meeting in Minneapolis. My =
conclusion is that there is no interest to do it, and that we will =
resolve all our pending charter items by work on the e-mail list. =
</FONT></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C4FED5.844C4F2E--


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

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

--===============0113827151==--



From hubmib-bounces@ietf.org  Thu Jan 20 07:00:04 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19345
	for <hubmib-archive@lists.ietf.org>; Thu, 20 Jan 2005 07:00:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Craru-0001lY-Pg; Thu, 20 Jan 2005 06:52:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Crar7-0001cN-Ju
	for hubmib@megatron.ietf.org; Thu, 20 Jan 2005 06:52:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18993
	for <hubmib@ietf.org>; Thu, 20 Jan 2005 06:52:02 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Crb6l-0003uo-Ik
	for hubmib@ietf.org; Thu, 20 Jan 2005 07:08:17 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0KBgaqm027254
	for <hubmib@ietf.org>; Thu, 20 Jan 2005 06:42:36 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0KBgYqm027212
	for <hubmib@ietf.org>; Thu, 20 Jan 2005 06:42:35 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 20 Jan 2005 13:51:57 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038AA01F@is0004avexu1.global.avaya.com>
Thread-Topic: comments on draft-ietf-hubmib-efm-cu-mib-02.txt
Thread-Index: AcT+5nGIOSO6AV1lTxSZE89JhNI55A==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: f2984bf50fb52a9e56055f779793d783
Subject: [Hubmib] comments on draft-ietf-hubmib-efm-cu-mib-02.txt
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="===============0831470000=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0831470000==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4FEE6.718E613E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4FEE6.718E613E
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find below my comments relative to =
draft-ietf-hubmib-efm-cu-mib-02.txt. All last call comments need to be =
addressed by the document editor.=20

Regards,

Dan

idnits errors:

idnits 1.58=20

tmp/draft-ietf-hubmib-efm-cu-mib-02.txt:

tmp/draft-ietf-hubmib-efm-cu-mib-02.txt(232): Line has weird spacing: =
'...=3D10Mbps  ifSpe...'
tmp/draft-ietf-hubmib-efm-cu-mib-02.txt(235): Line has weird spacing: =
'...100Mbps  ifSpe...'
tmp/draft-ietf-hubmib-efm-cu-mib-02.txt(3181): Line seems to end with a =
hyphenated word.


  Checking nits according to http://www.ietf.org/ID-Checklist.html :

  * The document seems to lack an IANA Considerations section.

Technical

T1. Objects with read-write MAX-ACCESS like efmCuPAFAdminState need to =
have a DEFAULT value defined by using the DEFAULT clause in order to =
define the behavior of the agent at initialization. Also if the values =
of such objects need to be preserved in case of reboots, this also needs =
to be mentioned.
T2. The technical content of the specification does not seem stable. =
There are several editor notes reflecting open questions, or places =
where the editor believes that there is a need to add more information. =
These editor notes need to be replaced by meaningful text and proposals =
for resolution of the open items, before the document is submitted to =
the IESG.
=20

Editorial

E1. Wherever there is mention of a specific MIB the correct terminology =
is 'MIB module' and not 'MIB'. There are many instances of such =
occurrences. For example in the abstract section, instead of 'This =
document proposes an extension to the Ethernet-like Interfaces MIB and =
MAU MIB' should be 'This document proposes an extension to the =
Ethernet-like Interfaces MIB and MAU MIB modules'. The title of section =
3 should be 'Relation to other MIB modules' instead of 'Relation to =
other MIBs', etc., etc.
E2. Several DESCRIPTION clauses of objects in the efmCuPmeConftable end =
with the phrase 'Value of false(0) indicates the it is disabled.' which =
is syntactically incorrect.
E3. Commented text on enumerated values like in the definition of =
efmCuPmeOperStatus is not recommended and not necessary, as the =
DESCRIPTION clause below should specify the meaning of each one of the =
values
E4. No need for commented leftovers like in the definition of =
efmCuAlarmConfGroup.
=20




------_=_NextPart_001_01C4FEE6.718E613E
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.6603.0">
<TITLE>comments on draft-ietf-hubmib-efm-cu-mib-02.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please find below my comments =
relative</FONT> <FONT SIZE=3D2 FACE=3D"Arial">to<SPAN LANG=3D"en-us"> =
draft-ietf-hubmib-efm-cu-mib-02.txt.</SPAN><SPAN =
LANG=3D"he"></SPAN></FONT><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial"> All last call comments need to be addressed by the =
document editor. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">idnits =
errors:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial Unicode =
MS">idnits 1.58 </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">tmp/draft-ietf-hubmib-efm-cu-mib-02.txt:</FONT></SPAN></P>=


<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">tmp/draft-ietf-hubmib-efm-cu-mib-02.txt(232): Line has =
weird spacing: '...=3D10Mbps&nbsp; ifSpe...'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">tmp/draft-ietf-hubmib-efm-cu-mib-02.txt(235): Line has =
weird spacing: '...100Mbps&nbsp; ifSpe...'</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">tmp/draft-ietf-hubmib-efm-cu-mib-02.txt(3181): Line seems =
to end with a hyphenated word.</FONT></SPAN></P>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; =
Checking nits according to <A =
HREF=3D"http://www.ietf.org/ID-Checklist.html">http://www.ietf.org/ID-Che=
cklist.html</A> :</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; * =
The document seems to lack an IANA Considerations =
section.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Technical</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">T1. =
Objects with read-write MAX-ACCESS like efmCuPAFAdminState need to have =
a DEFAULT value defined by using the DEFAULT clause in order to define =
the behavior of the agent at initialization. Also if the values of such =
objects need to be preserved in case of reboots, this also needs to be =
mentioned.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">T2. The =
technical content of the specification does not seem stable. There are =
several editor notes reflecting open questions, or places where the =
editor believes that there is a need to add more information. These =
editor notes need to be replaced by meaningful text and proposals for =
resolution of the open items, before the document is submitted to the =
IESG.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Editorial</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">E1. =
Wherever there is mention of a specific MIB the correct terminology is =
'MIB module' and not 'MIB'. There are many instances of such =
occurrences. For example in the abstract section, instead of 'This =
document proposes an extension to the Ethernet-like Interfaces MIB and =
MAU MIB' should be 'This document proposes an extension to the =
Ethernet-like Interfaces MIB and MAU MIB modules'. The title of section =
3 should be 'Relation to other MIB modules' instead of 'Relation to =
other MIBs', etc., etc.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">E2. =
Several DESCRIPTION clauses of objects in the efmCuPmeConftable end with =
the phrase 'Value of false(0) indicates the it is disabled.' which is =
syntactically incorrect.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">E3. =
Commented text on enumerated values like in the definition of =
efmCuPmeOperStatus is not recommended and not necessary, as the =
DESCRIPTION clause below should specify the meaning of each one of the =
values</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">E4. No =
need for commented leftovers like in the definition of =
efmCuAlarmConfGroup.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4FEE6.718E613E--


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

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

--===============0831470000==--



From hubmib-bounces@ietf.org  Fri Jan 21 13:16:49 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02953
	for <hubmib-archive@lists.ietf.org>; Fri, 21 Jan 2005 13:16:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cs3AC-0006K2-Ur; Fri, 21 Jan 2005 13:05:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cs37K-0005qm-HM
	for hubmib@megatron.ietf.org; Fri, 21 Jan 2005 13:02:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02095
	for <hubmib@ietf.org>; Fri, 21 Jan 2005 13:02:39 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cs3NF-0002zL-Qw
	for hubmib@ietf.org; Fri, 21 Jan 2005 13:19:10 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0LHrDqm002250
	for <hubmib@ietf.org>; Fri, 21 Jan 2005 12:53:13 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0LHqtqm001737
	for <hubmib@ietf.org>; Fri, 21 Jan 2005 12:52:56 -0500 (EST)
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 21 Jan 2005 20:01:52 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E30927@is0004avexu1.global.avaya.com>
Thread-Topic: Approval to Post Version -00 Internet-Drafts for the 62nd
	IETFMeeting in Minneapolis, MN 
Thread-Index: AcT/0RDJdxj9qas1QiaPmrQmVFd71QAEhZdA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
Subject: [Hubmib] FW: Approval to Post Version -00 Internet-Drafts for the
	62nd IETFMeeting in Minneapolis, MN 
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

If there is any intension to submit a draft-00, please take into =
consideration the message below.

Regards,

Dan



-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org]On =
Behalf Of Internet-Drafts Administrator
Sent: 21 January, 2005 5:41 PM
To: Working Group Chairs
Subject: Approval to Post Version -00 Internet-Drafts for the 62nd =
IETFMeeting in Minneapolis, MN=20


Dear IETF Working Group Chairs:

In order to expedite the processing of the many version -00 I-Ds that=20
the Secretariat  receives before an IETF meeting, we ask that you please =

notify the Secretariat prior to the initial submission cutoff date of =
all=20
version -00 I-Ds that you expect to approve for posting as WG documents. =
=20
Please send the filenames of your approved -00 I-Ds to =
internet-drafts@ietf.org=20
by no later than five (5) business days prior to the cutoff date for -00 =
submissions,
or by Monday, February 7th at 9:00 AM ET for the 62nd IETF Meeting. =
Please include=20
the word "Approved I-Ds" in the "Subject" field. This procedure will =
help to ensure=20
that version -00 I-Ds are posted in a timely manner, allowing more time =
for review=20
by the public.

Thank you for your cooperation in this matter.

The Internet-Drafts Administrator=20



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


