1. Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AS 18 March 2014 Authors: NameCompanyPhoneemail

2. This presentation provides responses to comments on IEEE 802.1AS during FDIS ballot The FDIS voting results on IEEE 802.1AS in N15831 –It passed 16/1/16 (China NB voted negative) –Comments were received from China NB and Switzerland NB The FDIS comments have been processed in a timely manner using the mechanisms defined and agreed in 6N15606 This presentation provides the proposed responses from IEEE 802 to all comments by China NB and the Switzerland NB in the FDIS ballot Slide 2

3. China NB comment CN1 on IEEE 802.1AS Since the procedural and technical concerns China NB proposed in 6N15626 still haven’t been reasonably disposed in this FDIS text, and referencing issues mentioned below exist in this text, so China NB has to vote against on this FDIS ballot. If these issues could not be disposed reasonably and this proposal would have been passing the FDIS ballot, it is regretful for China to be obliged to lose the responsibility and obligation of complying with and adopting the standard. Furthermore, China NB wishes to state for the record. Slide 3

4. China NB comment CN1 on IEEE 802.1AS (continued) Proposed IEEE 802 response to CN1 on IEEE 802.1AS IEEE 802 thanks the China NB for its carefully considered comments on the 802.1AS FDIS ballot We note that IEEE 802 responded in 6N15659 to all comments submitted by the China NB. Per the agreement in 6N15606, China NB representatives are invited to participate in the IEEE 802 comment resolution process. IEEE 802 is unable to respond to the China NB comment that they are “obliged to lose the responsibility and obligation of complying with and adopting the standard” because IEEE 802 is not party to any treaty or other obligations of China. Slide 4

5. China NB comment CN2 on IEEE 802.1AS The referenced RFC 3410 are informational standards, it is unqualified for normative references in ISO standards. China NB proposed change CN2 on IEEE 802.1AS Delete the referenced RFC and related technology from the document. Slide 5

6. China NB comment CN2 on IEEE 802.1AS (continued) Proposed IEEE 802 response to CN2 on IEEE 802.1AS As part of the normal maintenance process for IEEE 802.1AS, the IEEE 802.1 WG will review the references to ensure that only required references are included, RFC references are up to date, and normative RFC references have an appropriate status. According to IETF RFC 2026, “Specifications that have been prepared outside of the Internet community and are not incorporated into the Internet Standards Process by any of the provisions of section 10 may be published as Informational RFCs, with the permission of the owner and the concurrence of the RFC Editor. An "Informational" specification is published for the general information of the Internet community.” It is appropriate to reference these published specifications in IEEE Standards. Additionally, the IETF has defined a DownRef Registry, RFC 3967 (BCP 97), "Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level". Documents added to the Registry are considered Normative by the IETF, and thus are considered as standards by the IETF.RFC 3967 (BCP 97) Slide 6

7. Switzerland comment CH1 on IEEE 802.1AS In a conventional DIS or DIS fast-track ballot, the subsequent comments would be issued with a DISAPPROVE vote, which would be turned into APPROVAL if the comments were satisfactorily resolved. The FDIS fast-track however postpones, by 2.7 of the ISO/IEC Directives, Part 1, such resolution to the next review of the standard. Furthermore, affirmative votes to an FDIS cannot be made conditional on the resolution of any comments. However, we wish ISO/IEC to endorse this standard and to subjugate it under its maintenance procedures as set forth in F.2.4 of the ISO/IEC Directives, Part 1, and Sc6 Graz Resolution 6.1.10. Therefore our vote is APPROVE, unconditionally. Our comments are submitted under the late option of 6N15606 to be processed by the IEEE 802.1 WG as soon as possible, i.e. either during comment resolution on any subsequent draft or during normal maintenance. Slide 7

8. Switzerland comment CH1 on IEEE 802.1AS (continued) Proposed IEEE 802 response to CH1 on IEEE 802.1AS IEEE 802 thanks the Switzerland NB for its carefully considered comments on the IEEE 802.AB FDIS ballot, and assures the Switzerland NB that its comments will be processed in a timely manner by the IEEE 802.1 WG using the mechanisms defined and agreed in 6N15606. Swiss NB representatives are invited to participate in the comment resolution process. The mechanisms defined and agreed in 6N15606 apply. Editing and maintenance will continue to be the responsibility of IEEE 802 and will conform to the IEEE policies and procedures. Slide 8

9. Switzerland comment CH2 on IEEE 802.1AS When the ISO/IEC/IEEE 8802-1AB standard has been endorsed by ISO/IEC, then the ISO Directives, Part 2, “Rules for the structure and drafting of International Standards” as well as the JTC 1 Supplement and the relevant JTC 1 Standing Documents must be considered. It is desirable that the next revision of the specification be in line with the applicable requirements. This is a major aim of our comments. We will be pleased to find resolutions in fruitful collaboration with the IEEE 802.1 WG. Slide 9

10. Switzerland comment CH2 on IEEE 802.1AS (continued) Proposed IEEE 802 response to CH.2 on IEEE 802.1AS IEEE 802.1AS has been developed according to the IEEE Standards Association standards development process and IEEE-SA Standards Style Manual. Editing and maintenance will continue to be the responsibility of IEEE 802 and will conform to the IEEE policies and procedures. The mechanisms defined and agreed in 6N15606 will apply. We look forward to collaboration with the Swiss NB in the future. Slide 10

11. Switzerland comment CH3 on IEEE 802.1AS ANSI and NIST are AROs, therefore he references to the cryptography standards do not comply with JTC1 Standing Document N5. Switzerland NB proposed change CH3 on IEEE 802.1AS For each of the cryptography standards, chose one of the following alternative actions: Produce an RER according to JTC1 Standing Document N5. Reference published standards, preferably ISO/IEC standards (ISO/IEC 15946- 2, ISO/IEC 10118-3 and ISO/IEC 14888-3) Incorporate technical requirements into the standard text. Proposed IEEE 802 response to CH3 on IEEE 802.1AS IEEE 802.1 would respectfully observe that, as the IEEE 802.1AS standard contains no references to cryptography standards of any kind, this comment is not relevant. Slide 11

12. Switzerland comment CH4 on IEEE 802.1AS The reference to FIPS 140 does not comply with JTC1 Standing Document N5. Switzerland proposed change CH4 on IEEE 802.1AS Choose one of the following alternative actions: - Produce an RER according to JTC1 Standing Document N5. - Reference ISO/IEC 15408 and incorporate a generic PP (Protection Profile) into the standard text. Proposed IEEE 802 response to CH4 on IEEE 802.1AS IEEE 802.1 would respectfully observe that, as the IEEE 802.1AS standard contains no references to FIPS 140, this comment is not relevant. Slide 12

13. Switzerland comment CH5 on IEEE 802.1AS RFC 1588 and 3410 have only INFORMATIONAL status. According to RFC 2026 a specification of INFORMATIONAL status is a non-standard-track document which is (cit.) “”not subject to the rules of Internet standardization” and (cit.) “published for the general information of the Internet community and does not represent an Internet community consensus or recommendation. … Standards track specifications normally must not depend on other standards track specifications which are at a lower maturity level or on non standards track specifications other than referenced specifications from other standards bodies.” (citation end) Therefore these documents do not qualify for normative referencing. Switzerland proposed change CH5 on IEEE 802.1AS Resolve the issue by any of the following: - Placing the reference into the Informative References section. - Referencing of published standards, preferably ISO/IEC standards, Incorporation of technical requirements into the standard text.. Proposed IEEE 802 response to CH5 on IEEE 802.1AS There is no reference to RFC 1588 in this standard, so this part of the comment is not relevant. See Proposed IEEE 802 response to CN2 on IEEE 802.1AS in slide 6. Slide 13

14. Switzerland comment CH6 on IEEE 802.1AS IEEE Std 802.11 has been submitted for publication as ISO/IEC/IEEE 8802-11. Switzerland proposed change CH6 on IEEE 802.1AS Reference the international standard. Proposed IEEE 802 response to CH6 on IEEE 802.1AS This comment will be submitted to the IEEE 802.1 maintenance process and considered by the IEEE 802.1 Maintenance Task Group for potential inclusion in a future revision or corrigendum to the standard. Slide 14

15. Submission February 2014 Switzerland comment CH7 on IEEE 802.1AS The phrasing of some of the definitions does not conform to the ISO/IEC Directives, Part 2 Switzerland proposed change CH7 on IEEE 802.1AS Discard articles (“a”, “the”) at the beginning of the definition. Avoid two or more sentences. Discard Notes. Proposed IEEE 802 response to CH7 on IEEE 802.1AS IEEE 802.1AS has been developed according to the IEEE Standards Association standards development process and IEEE-SA Standards Style Manual. Editing and maintenance will continue to be the responsibility of IEEE 802 and will conform to the IEEE policies and procedures. The mechanisms defined and agreed in 6N15606 will apply. Slide 15