|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
Just took a look at your docs.
I have some suggested changes.
Currently: Standard for YANG data model definitions for Ethernet
Should be: Standard for YANG data model definitions for Ethernet station management
Your PAR date items 4.2 and 4.3 appear to be pretty aggressive for a new work.
There is no downside to giving yourself more time.
PAR 5.5 (Slide 8)
Currently: YANG is specified in Request For Comment (RFC) 6020 and amendments / corrigenda
Should be: YANG is specified in IETF Request For Comment (RFC) 6020 and amendments / corrigenda
Managed Objects slide
Currently: This project will develop YANG models from Clause 30 objects...
Should be: This project will develop YANG models of the definitions from Clause 30 objects...
Broad Market Potential
Currently: The proposed amendment will enable the use of YANG model for a wide variety...
Should be: The proposed standard will enable the use of YANG model of 802.3 managed objects for a wide variety...
Add a bullet: This work is fully aligned to and coordinated with equivalent work taking place in 802.1.
Add a bullet: This work will not be compatible with SNMP. This is an obsolete requirement.
Currently: Other SDOs (e.g., MEF and IETF) have already defined YANG data models and there is...
Should be: Other SDOs (e.g., MEF and IETF) have already defined YANG data models for managing and operating Ethernets and there is...
Currently: Define a YANG module for Ethernet passive optical networks (EPON).
Should be: Define YANG modules for Ethernet passive optical networks (EPON) Optical Network Units (ONU) and Optical Network Terminals (ONT).
On Apr 27, 2016, at 7:57 PMPDT, Zhuangyan (Yan) <zhuangyan.zhuang@xxxxxxxxxx> wrote: