Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] Updated P802.1Qcw PAR & CSD with 802.1 comment responses



Disregard this email, as I see you added a reconsidered motion slide.

 

From: John D'Ambrosia [mailto:jdambrosia@gmail.com]
Sent: Friday, July 14, 2017 6:00 AM
To: 'Glenn Parsons' <glenn.parsons@ERICSSON.COM>; STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: RE: [802SEC] Updated P802.1Qcw PAR & CSD with 802.1 comment responses

 

Glenn,

Per your email below the PAR was updated to V3.  THe file you sent out still indicated V2 in the motion.

 

I have modified the agenda item, per email below to V3.

 

John

 

 

From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Glenn Parsons
Sent: Thursday, July 13, 2017 11:27 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Updated P802.1Qcw PAR & CSD with 802.1 comment responses

 

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,
Glenn.

 

 

From: Jon Rosdahl [mailto:jrosdahl@ieee.org]
Sent: Thursday, July 13, 2017 6:48 AM
To: Glenn Parsons <glenn.parsons@ericsson.com>
Cc: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Updated P802.1Qcw PAR & CSD with 802.1 comment responses

 

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


-----------------------------------------------------------------------------
Jon Rosdahl                 Engineer, Senior Staff
office: 801-492-4023      Qualcomm Technologies, Inc.
cell:   801-376-6435      10871 North 5750 West
                                   Highland, UT 84003


A Job is only necessary to eat!
A Family is necessary to be happy!!

 

On Wed, Jul 12, 2017 at 9:04 AM, Glenn Parsons <glenn.parsons@ericsson.com> wrote:

Colleagues,

 

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 and 802.3.

 

The responses to the comment are here:

http://ieee802.org/1/files/public/docs2017/cw-PAR-CSD-comments-0717-v01.pdf

 

The PAR has been updated:

http://ieee802.org/1/files/public/docs2017/cw-draft-PAR-0517-v02.pdf

 

The CSD has been updated:

http://ieee802.org/1/files/public/docs2017/cw-draft-CSD-0517-v02.pdf

 

Cheers,

Glenn.

 

--

Glenn Parsons - Chair, IEEE 802.1

glenn.parsons@ericsson.com

+1-613-963-8141

 

 

 

 

 

---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.

 

---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.

---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.