| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Colleagues, Rebuttal comments on the PAR for P802.1Qcw - Amendment: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing were received from 802.11. While we are not aware of a rule describing the process for rebuttal comments, 802.1 has prepared additional responses to the comments in this document: http://www.ieee802.org/1/files/public/docs2017/admin-farkas-11-rebuttal-responses-0717-v2.pdf
The PAR has been updated: http://ieee802.org/1/files/public/docs2017/cw-draft-PAR-0517-v03.pdf
The CSD is unchanged: http://ieee802.org/1/files/public/docs2017/cw-draft-CSD-0517-v02.pdf
Cheers, From: Jon Rosdahl [mailto:jrosdahl@ieee.org] 802.11 PAR Review SC has the following rebuttal to the comments/changes to the PAR: 1.PAR 5.2.b (project scope)
– the addition of the “Additionally, this amendment will address errors or omissions to existing features related to the aforementioned clauses as approved by the 802.1 maintenance
process.”
The “IEEE 802.1 maintenance process” does not have a PAR, so it is not an authorized Activity. The purpose each of the 802.1 maintenance PARs should authorize the specific activity
that is proposed.
Delete the “as approved by the 802.1 maintenance process”.
2. PAR 5.3
– “If yes, please explain” – listing the title of another amendment does not seem to “explain”.
•How is the proposed standard dependent on IEEE
P802.1Q-Rev and IEEE P802.1Qcp? •What is the schedule impact
due to the dependency on IEEE P802.1Q-Rev and IEEE P802.1Qcp?
3 PAR – 6.1b – “The YANG Data Model will be assigned a URN based on the RA URN tutorial
and IEEE Std 802d.” a)The acronyms need to be expanded “URN”, “RA” b)The RA URN tutorial should include a reference. c)IEEE Std 802d should be fully cited in 8.1 Respectfully submitted, Jon -----------------------------------------------------------------------------
On Wed, Jul 12, 2017 at 9:04 AM, Glenn Parsons <glenn.parsons@ericsson.com> wrote:
|