Re: FW: EPON MIB comments (eponDeviceObjectPowerDown)

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 [email protected]

----- Original Message ----- 
From: "Glen Kramer" <[email protected]>
To: "'Lior khermosh'" <[email protected]>; "'Romascanu, Dan (Dan)'" 
<[email protected]>; <[email protected]>
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
> [email protected]
> https://www1.ietf.org/mailman/listinfo/hubmib
>