Skip to main content

Managed Objects of Ethernet Passive Optical Networks (EPON)
draft-ietf-hubmib-efm-epon-mib-06

Yes

(Dan Romascanu)

No Objection

(Bill Fenner)
(Brian Carpenter)
(Cullen Jennings)
(David Kessens)
(Jari Arkko)
(Jon Peterson)
(Lisa Dusseault)
(Magnus Westerlund)
(Mark Townsley)
(Ross Callon)
(Russ Housley)
(Sam Hartman)

Note: This ballot was opened for revision 06 and is now closed.

Dan Romascanu Former IESG member
Yes
Yes () Unknown

                            
Bill Fenner Former IESG member
No Objection
No Objection () Unknown

                            
Brian Carpenter Former IESG member
No Objection
No Objection () Unknown

                            
Cullen Jennings Former IESG member
No Objection
No Objection () Unknown

                            
David Kessens Former IESG member
No Objection
No Objection () Unknown

                            
Jari Arkko Former IESG member
No Objection
No Objection () Unknown

                            
Jon Peterson Former IESG member
No Objection
No Objection () Unknown

                            
Lars Eggert Former IESG member
No Objection
No Objection (2006-11-28) Unknown
  Word-wrapping makes some of the tables difficult to read. The editors
  might want to think about a different way to present this information.


Section 5., paragraph 23:
>    dot3MpcpSyncTime OBJECT-TYPE
>        SYNTAX  Unsigned32
>        UNITS       "TQ (16nsec)"
>        MAX-ACCESS  read-only
>        STATUS  current
>        DESCRIPTION
>                "An object that reports the 'sync lock time' of the
>                 OLT receiver in increments of Time Quanta (TQ)-16ns
>                 as defined in [802.3ah] 60,64,65. The value returned
>                 shall be (sync lock time ns)/16. If this value exceeds
>                 (2^32-1) the value (2^32-1) shall be returned.
>                 This object is applicable for an OLT, with the same
>                 value for all virtual interfaces, and for an ONU."
>        REFERENCE   "[802.3ah], 64.3.3.2."
>       ::= { dot3MpcpControlEntry 4 }

  If the value can exceed what can be represented in 32 bits, wouldn't a
  64-bit value make sense, both here and for objects below that are
  similarly capped? (I'm no expert in this technology, so there may well
  be a good reason for why this choice was made.)


Section 8., paragraph 17:
>    SNMP versions prior to SNMPv3 did not include adequate security.
>    Even if the network itself is secure (for example by using IPSec),

  Nit: s/IPSec),/IPsec),/
Lisa Dusseault Former IESG member
No Objection
No Objection () Unknown

                            
Magnus Westerlund Former IESG member
No Objection
No Objection () Unknown

                            
Mark Townsley Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection () Unknown

                            
Sam Hartman Former IESG member
No Objection
No Objection () Unknown

                            
Ted Hardie Former IESG member
No Objection
No Objection (2006-11-27) Unknown
Nit:

The document says:


   The Optical Line Terminal (OLT) is the server unit of the network,
   located at the Central Office (CO).

   The Optical Network Unit (ONU) is the client unit of the network,
   located at the Customer Premises Equipment (CPE).

This is a non-blocking comment, but I do wish to note that I find the
"located in" clauses above somewhat strange.  If the services which
make a CO are required by the OLT in some way, the document doesn't
note it in a way that was findable by me; similarly, that operation
of this doesn't seem to require that ONU be in CPE--presumably it
can be anywhere the ONU functaionality is needed.  The other
diagrams and descriptions of functionality seem fairly general.