Protocol Details Client Details This section specifies the DHCP NAP client behavior. Abstract Data Model The common Abstract Data Model is specified in section . DHCP clients implementing this protocol are required to track the following state: NAP-Capable Server: State indicating whether the DHCP server with which the client is communicating has NAP Enforcement enabled on it. This information is used to determine whether to exchange NAP-specific information with that server in message exchanges. Possible values are "Unknown", "Yes", and "No". Timers There are no timers beyond those in section 3.1.2. Initialization See section 3.1.3 for DHCP client initialization. Higher-Layer Triggered Events See section 3.1.4 for the higher-layer triggered events for the DHCP client. If DHCP enforcement is enabled for NAP on a DHCP client, the client MUST also trigger a DHCPDISCOVER or a DHCP transaction, as specified in section 3, whenever the system health state or configuration changes. Due to the vulnerability of DHCP, DHCP clients SHOULD NOT attempt to use NAP on unauthenticated wireless networks. Creating and Transmitting a DHCPDISCOVER Message Whenever a DHCP client a DHCPDISCOVER message, the DHCP client implementing this specification MUST indicate its capability to the DHCP server by sending the SoH vendor-specific option with length equal to zero. It MUST also include a option (section 2.2.1.3) in this message. The (section 2.2.1.1) option and NAP-CoID (section 2.2.1.3) option are appended to the DHCPDISCOVER message packet by calling DhcpAppendVendorSpecificOption ( section 3.1.7.1). In addition, it MUST set its NAP-Capable Server state to "Unknown". Creating and Transmitting a DHCPREQUEST Message During Lease Renewal Whenever a DHCP client sends a DHCPREQUEST message during DHCP lease renewal and its Server state is set to "Unknown" or "Yes", it MUST include the option of length one octet and data equal to zero in the DHCPREQUEST message. It MUST also include a option in this message. If instead the NAP-Capable Server state is set to "No", it MUST send the message without any options defined in this document.
Protocol Details Client Details This section specifies the DHCP NAP client behavior. Abstract Data Model The common Abstract Data Model is specified in section . DHCP clients implementing this protocol are required to track the following state: NAP-Capable Server: State indicating whether the DHCP server with which the client is communicating has NAP Enforcement enabled on it. This information is used to determine whether to exchange NAP-specific information with that server in message exchanges. Possible values are "Unknown", "Yes", and "No". Timers There are no timers beyond those in section 3.1.2. Initialization See section 3.1.3 for DHCP client initialization. Higher-Layer Triggered Events See section 3.1.4 for the higher-layer triggered events for the DHCP client. If DHCP enforcement is enabled for NAP on a DHCP client, the client MUST also trigger a DHCPDISCOVER or a DHCP transaction, as specified in section 3, whenever the system health state or configuration changes. Due to the vulnerability of DHCP, DHCP clients SHOULD NOT attempt to use NAP on unauthenticated wireless networks. Creating and Transmitting a DHCPDISCOVER Message Whenever a DHCP client a DHCPDISCOVER message, the DHCP client implementing this specification MUST indicate its capability to the DHCP server by sending the SoH vendor-specific option with length equal to zero. It MUST also include a option (section 2.2.1.3) in this message. The (section 2.2.1.1) option and NAP-CoID (section 2.2.1.3) option are appended to the DHCPDISCOVER message packet by calling DhcpAppendVendorSpecificOption ( section 3.1.7.1). In addition, it MUST set its NAP-Capable Server state to "Unknown". Creating and Transmitting a DHCPREQUEST Message During Lease Renewal Whenever a DHCP client sends a DHCPREQUEST message during DHCP lease renewal and its Server state is set to "Unknown" or "Yes", it MUST include the option of length one octet and data equal to zero in the DHCPREQUEST message. It MUST also include a option in this message. If instead the NAP-Capable Server state is set to "No", it MUST send the message without any options defined in this document.