void __4_4_17__802_1X_ACCESS_CONTROL() {
    /**
     * @group:       	4.4.17 802.1X ACCESS CONTROL
     *
     * @description:	IEEE 802.1X is a Port-based authentication protocol. EAPOL is the protocol normally used by the authentication pro-
     * 					cess as uncontrolled Port. By receiving and extracting special EAPOL frames, the host processor can control whether
     * 					the ingress and egress ports should forward packets or not. If a user port wants service from another port (authentica-
     * 					tor), it must get approved by the authenticator. The device detects EAPOL frames by checking the destination address
     * 					of the frame. The destination addresses should be either a multicast address as defined in IEEE 802.1x (01-80-C2-00-
     * 					00-03) or an address used in the programmable reserved multicast address domain with offset -00-03. Once EAPOL
     * 					frames are detected, the frames are forwarded to the host port so it can send the frames to the authenticator server.
     * 					Eventually, the CPU determines whether the requester is qualified or not based on its source MAC address, and frames
     * 					are either accepted or dropped.
     * 					When the device is configured as an authenticator, the ports of the switch must then be configured for authorization. In
     * 					an authenticator-initiated port authorization, a client is powered up or plugs into the port, and the authenticator port
     * 					sends an Extensible Authentication Protocol (EAP) PDU to the supplicant requesting the identification of the supplicant.
     * 					At this point in the process, the port on the switch is connected from a physical standpoint; however, the 802.1X process
     * 					has not authorized the port and no frames are passed from the port on the supplicant into the switching fabric. If the
     * 					supplicant attached to the switch (KSZ9477S) did not understand the EAP PDU that it was receiving from the switch, it
     * 					would not be able to send an ID and the port would remain unauthorized. In this state, the port would be blocked from
     * 					passing any user traffic. If the supplicant is running the 802.1X EAP, it would respond to the request with its configured
     * 					ID. (This could be a user name/password combination or a certificate.)
     * 					After the device receives the ID from the supplicant, it passes the ID information to an authentication server (RADIUS
     * 					server) that can verify the identification information. The RADIUS server responds to the switch with either a success
     * 					or failure message. If the response is a success, the port will be authorized and user traffic will be allowed to pass
     * 					through the port like any switch port connected to an access device. If the response is a failure, the port will remain
     * 					unauthorized and, therefore, unused. If there is no response from the server, the port will also remain unauthorized and
     * 					will not pass any traffic.
     * 					Port control can be performed via the Access Control List (ACL) Filtering feature.
     *
     */
}