----------------------------- 802.1 Responses to Comments received on the 802.1X Revision (maintenance PAR) Responses to comments from 802.11 --------------------------------- The comments formed part of the set https://mentor.ieee.org/802.11/dcn/18/11-18-0293-01-0PAR-par-review-meeting-agenda-and-comment-slides-march-2018-rosemont.pptx PAR 5.3 PAR 5.5 indicates that IEEE P802.1Xck is a dependency, so that would mean that 5.3 should say yes and add the appropriate information. PAR 5.5 - P802.1Xck is missing the IEEE PAR 8.1 Titles should be the full title of each cited standard IEEE 802.1Xck and IEEE Std 802.1Xbx PAR 8.1 - a reference to IEEE Std 802.1AE, IEEE Stds 802 and IEEE Std 802.1AE. PAR 8.1 - correct IEEE Stds 802 and 802.1AE. should be IEEE Stds 802 and IEEE Stds 802.1AE. Responses The answer to 5.3 has been changed to Yes. Explanatory text has been added to the effect that IEEE P802.1Xck passed its 802.1WG ballot on 12/12/2017 with 100% Approval (following recirculation). [There were no outstanding comments (neither "must be satisfied" or other), and the response rate was 77%. Separately we have a motion to send P802.1Xck to Sponsor Ballot after this meeting]. "IEEE" now appears prior to "P802.1Xck" throughout. Full titles of all referenced standards are given in #8.1. All IEEE Standards now have "Std" before the standard number/designation. Responses to comments from 802.3 -------------------------------- The comments formed part of the document 2018_03 PARs ad hoc report-1.pptx received by email: 5.2 – Since you are doing a revision, you may want to update the scope to match IEEE Style (colon on the sentence preceding the list and list items punctuated correctly). 6.1.b – Minor nit, but listing the MIB arc type(s) could be helpful. One can guess URN is included because of the YANG amendment being merged, but will the amendment also include use of OID management arcs? 8.1 – It is strange to have a note for #7.3 which does not appear on the PAR. Did 7.3 get marked No by accident? Responses The punctuation of the Scope has been changed (no other changes were made to the Scope), adding a colon after the phrase introducing the list and a semi-colon after each item in the list, except for the last which retains a period. The punctuation in the original Scope was not a product of any WG or ballot activity, but an IEEE editorial change. Following the introduction a style guide rule that "as follows" or "following" should always precede a colon introducing a list, the editorial response (at that time) was to simply remove colons in cases where "as follows" or "following" was clearly redundant. The semi-colons we have also added back, might be removed once more following IEEE editing. The project editor will consult with IEEE staff as to the best consistent approach when the base and the amendments are rolled up, resolving changing style differences. The MIB arc has been listed in full in 6.1.b explanatory text. Item #7.3 does appear on the PAR. Unfortunately the "save as PDF" provided by myProject did not included it, and a simple copy of the web page loses other information.