{"id":211851,"date":"2024-10-19T13:42:29","date_gmt":"2024-10-19T13:42:29","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/ieee-802-1xck-2018\/"},"modified":"2024-10-25T06:31:09","modified_gmt":"2024-10-25T06:31:09","slug":"ieee-802-1xck-2018","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/ieee\/ieee-802-1xck-2018\/","title":{"rendered":"IEEE 802.1Xck 2018"},"content":{"rendered":"
Amendment Standard – Active. The YANG data model specified in this amendment to IEEE Std 802.1X\u2122-2010 allows configuration and status reporting for port-based network access control, in the scenarios described in Clause 7 of this standard and Clause 11 of IEEE Std 802.1AE\u2122-2018, using the information model previously specified in this standard. (The PDF of this standard is available at no cost to you compliments of the IEEE GET program https:\/\/ieeexplore.ieee.org\/browse\/standards\/get-program\/page)<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
1<\/td>\n | IEEE Std 802.1Xck\u2122-2018 front cover <\/td>\n<\/tr>\n | ||||||
2<\/td>\n | Title page <\/td>\n<\/tr>\n | ||||||
4<\/td>\n | Important Notices and Disclaimers Concerning IEEE Standards Documents <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | Participants <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | Contents <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | Figures <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | Tables <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 1. Overview 1.3 Introduction <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 1.4 Provisions of this standard <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 2. Normative references <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 3. Definitions <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 5. Conformance 5.3 Conformant systems and system components 5.4 PAE requirements <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5.10 MKA requirements 5.12 Virtual port requirements <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.23 Requirement for YANG data model of a PAE 5.24 Options for YANG data model of a PAE <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 6. Principles of port-based network access control operation 6.1 Port-based network access control architecture 6.2 Key hierarchy 6.2.2 Using EAP for CAK key derivation <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 6.3 Port Access Entity (PAE) 6.3.6 Multi-access LANs 6.4 Port Access Controller (PAC) 6.4.2 Controlled Port transmission and reception 6.4.3 PAC management <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 7. Port-based network access control applications 7.5 Host access with MACsec and a multi-access LAN <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 8. Authentication using EAP 8.11 EAP methods <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 9. MACsec Key Agreement protocol (MKA) 9.2 Protocol support requirements 9.2.2 SC identification 9.4 MKA transport 9.4.5 Addressing 9.8 SAK generation, distribution, and selection <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 9.10 SAK installation and use <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 9.10.1 MKPDU application data 9.11 Connectivity change detection <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 11. EAPOL PDUs 11.1 EAPOL PDU transmission, addressing, and protocol identification 11.1.1 Destination MAC address <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 11.11 EAPOL-MKA <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 11.11.1 MKA parameter encoding <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 11.11.3 Encoding MKPDUs <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 12. PAE operation 12.9 PAE management 12.9.2 Identifying PAEs and their capabilities <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 13. PAE MIB 13.2 Structure of the MIB 13.4 Security considerations 13.5 Definitions for PAE MIB <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 14. YANG data model 14.1 PAE management using YANG <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 14.2 Security considerations <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 14.3 802.1X YANG model structure <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 14.4 Relationship to other YANG data models 14.4.1 General <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 14.4.2 Relationship to the IETF System Management YANG data model (IETF RFC 7317) <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | 14.4.3 Relationship to the IETF Interface Management YANG data model (IETF RFC 8343) <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | 14.4.4 The Interface Stack Models <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 14.5 Definition of the IEEE 802.1X YANG data model 14.5.1 YANG tree schema <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | 14.5.2 YANG module definition <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | 14.6 YANG data model use in network access control applications 14.6.1 General 14.6.2 Host accessing network access point using physically secure point-to-point LAN (7.1) <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | 14.6.3 Network access point supporting host access using physically secure point-to-point LAN (7.1) 14.6.4 Network access point supporting host access using MACsec and point-to-point LAN (7.3) <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | 14.6.5 Network access point supporting host access using MACsec and multi-access LAN (7.5) 14.6.6 Network access point supporting host access using MACsec and point-to-point LAN over LAG (IEEE Std 802.1AE-2018, 11.5) <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Annex A (normative) PICS proforma A.5 Major capabilities and options <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | A.6 PAE requirements and options <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | A.9 MKA requirements and options <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | A.15 YANG requirements and options <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Annex B (informative) Bibliography <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Annex D <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Annex E (informative) IEEE 802.1X EAP and RADIUS usage guidelines E.1 EAP Session-Id E.2 RADIUS Attributes for IEEE 802 Networks <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | Back cover <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" IEEE Standard for Local and metropolitan area networks – Port-Based Network Access Control Amendment 2: YANG Data Model<\/b><\/p>\n |