Opening Session Led by:
Agenda as modified was agreed.
Meeting minutes
2016.583, 2016.584, 2016.613, 2016.614,2016.629, 2016.632 and 2016.637 approved.
Liaisons
2016.704 - RPF Managed Objects draft for G.997.2
Latency question is perhaps more Architecture related. Liaison was briefly reviewed.
Commscope to look at the ETSI liaison.
Will be reviewed in detail during the joint session.
2016.705 - Managed objects used by the DPU rather than used by the PMA.
Question around where the state machine would run as the expectation would be that it would be the DPU running the state machine rather than the PMA.
Relating to the software image of the G.fast DPU.
Mauro - question on if the code to that goes to the unit is the full code or separate for the different parts of the DPU. It would be the entire DPU code.
Reviewed in the joint session tomorrow.
2016.867 - SELT in g.fast deployment
Mainly for PhyTX. Expectation to cover in the joint session, but there is a wish to have a teleconference to cover if needed before the next SG15/Q4 meeting.
Update on FTTdp management interop project stream
Now WT-355 & WT-371 have passed final ballot, then we need to start getting contributions to progress OD-374
Update on YANG
YANG Models Advice to not to include specific revision dates. - Removed the revision dates Mike has some concerns especially over when we have test specifications we will need revision dates. If we don't, then we have a moving goalpost. Ken - think it is simpler. Just use the version by the supported The module has a specific revision date. It is about how the modules reference each other. All this is doing is removing from the modules itself the versions of the other modules. Always inside the module, but filename will have revision date on the file. So where are we removing the date from - If we have module A wanting to inport Module B, then rather than importing a date specific version, it will just pick up the latest version.
WT-301 Session Led by:
Attendees:
