Managed Objects of Ethernet Passive Optical Networks (EPON)
RFC 4837

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

Lars Eggert No Objection

Comment (2006-11-28)
No email
send info
  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),/

(Dan Romascanu; former steering group member) Yes

Yes ()
No email
send info

(Bill Fenner; former steering group member) No Objection

No Objection ()
No email
send info

(Brian Carpenter; former steering group member) No Objection

No Objection ()
No email
send info

(Cullen Jennings; former steering group member) No Objection

No Objection ()
No email
send info

(David Kessens; former steering group member) No Objection

No Objection ()
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection ()
No email
send info

(Jon Peterson; former steering group member) No Objection

No Objection ()
No email
send info

(Lisa Dusseault; former steering group member) No Objection

No Objection ()
No email
send info

(Magnus Westerlund; former steering group member) No Objection

No Objection ()
No email
send info

(Mark Townsley; former steering group member) No Objection

No Objection ()
No email
send info

(Ross Callon; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ()
No email
send info

(Sam Hartman; former steering group member) No Objection

No Objection ()
No email
send info

(Ted Hardie; former steering group member) No Objection

No Objection (2006-11-27)
No email
send info
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.