| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Kent / all – below are my comments on the PARs and CSDs. PAR comments for 802.3 review P802.1Qdq extension: The reason for extension cites dependence on the revision project as one reason, yet there is no mention of this dependency in the original PAR. Is the delay in the project a RESULT of the
dependence (it seems not, that something else happened since the standard was supposed to be in SA ballot 3 years ago)? If the dependence is not a factor, then suggest delete the sentence beginning “Furthermore” to avoid confusion with the response to 5.3.
(note that the PAR for 802.1Q states it IS dependent on the roll up revision). If the delay has caused the standard to be dependent on the roll-up revision, than I suggest you say that directly in the reason for the extension (since I believe you cannot modify
the original PAR response to 5.3). PAR 802.1Qee: 5.2b Scope. Suggest “This amendment specifies procedures and YANG to…” should be “This amendment specifies procedures and YANG data models to…” (YANG is a data modelling language as described
in 8.1, YANG data models are what may be specified…) 5.2b Scope. “to extend bridge attributes for traffic engineering for bridged networks with delay variance beyond that supported by the existing specification.” – suggest that SOME boundary
on the delay variance targeted or some additional information would be useful. Simply saying anything outside the existing specification, in conjunction with the ability to make technical corrections to the existing specification (next sentence) makes the
scope the entire world. 6.1.2 Explanation – it is best not to promise future action. While it is FAIRLY SURE that URNs and OUIs will be used, it is better to say “is expected to use”. (the text for CID is fine). CSD 802.1Qee: 1.2.4 Technical Feasibility: The responses to technical feasibility speak ONLY to the capabilities in the base standard, yet the amendment seeks to extend those capabilities to links “with
more uncertain delays” than those in the base standard, something it claims is not in there. Therefore, these responses are not relevant to the amendment being proposed. Please provide some support that the suggested delays can be supported. (note – this
may also be useful in setting some boundary to the scope as suggested above). 1.2.5 Economic Feasibility: (a) to say that it “will not add hardware cost” is to promise future action, and may not be true. For example, management extensions might require additional memory
of monitoring functionality. Suggest “are not expected to add”. Also, “beyond the minimal and firmly bounded resources consumed by additional management modules” doesn’t really have meaning. If I take this to an extreme, such resources are not obviously
“firmly bounded” or even “minimal”. Suggest delete, or replace by “beyond the resources consumed by management modules required for the existing specification”, or, if this phrasing is needed, additional explanation as to what “minimal” is relative to and
what “firm bounds” are meant. (b) (c) (d) replace “will” which promises an outcome or future action where possible, suggest “is not expected to” unless it is bounded by the scope. (potentially “c” is) PAR & CSD 802.3dq: no comments George Zimmerman, Ph.D. President & Principal CME Consulting, Inc. Experts in Advanced PHYsical Communications 310-920-3860 From: Kent Lusted <00003dd2e253c6a1-dmarc-request@xxxxxxxxxxxxxxxxx>
Dear Colleagues, This is an announcement of an IEEE 802.3 PAR review ad hoc teleconference meeting scheduled for 7am Pacific, 7 July 2025. The call information can be found on the IEEE 802.3 Call and Meeting calendar. (see:
https://www.ieee802.org/3/calendar.html) The deadline for a Working Group to submit comments is 18:30 local time on the Tuesday of the Plenary session. In the case of the July 2025 Plenary session, that is 18:30 CEST on Tuesday 29 July 2025. I want to remind all teleconference meeting participants to review the following documents prior to participation in an IEEE 802.3 meeting teleconference:
All of these policies may be found at
http://ieee802.org/3/policies.html -Kent Chair, IEEE 802.3 PAR Review ad hoc To unsubscribe from the STDS-802-3-DIALOG list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-DIALOG&A=1 To unsubscribe from the STDS-802-3-DIALOG list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-DIALOG&A=1 |