RFC 3456:Dynamic Host Configuration Protocol (DHCP...
RFC-Ref

authentication


Click on the red underlined text to get to the source

... security and simplicity in the IKE implementation. f. authentication where required ...
... to support configuration. Authentication Where DHCPv4 authentication ...
... Authentication Where DHCPv4 authentication [5] is required, this can be supported on an IPsec tunnel mode ...


... remote host and the security gateway are authenticated and integrity protected. ...
... between the security gateway and the DHCP server, unless DHCP authentication is used. Note that authenticated ...
... DHCP authentication is used. Note that authenticated DHCP cannot be used as an access control mechanism. This is because a remote host ...
... remote host can always set its own IP address and thus evade any security measures based on DHCP authentication. As a result, the assigned address ...


... Droms, R. and W. Arbaugh, "Authentication for DHCP Messages", RFC 3118prop, June 2001. ...
... Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402(-> 4305(-> 4835prop) | 4302prop), November 1998. ...


... duplication of effort to address assignment. Instead, it will be tempting to also duplicate the configuration, authentication and fail-over facilities of DHCPv4 ...
... IKE. Authentication While IKECFG can support mutual authentication of the IPsec ...
... Authentication While IKECFG can support mutual authentication of the IPsec tunnel endpoints ...
... tunnel endpoints, it is difficult to integrate IKECFG with DHCPv4 authentication [5]. This is because the security gateway will not typically have access to the client ...
... credentials necessary to issue an DHCPv4 authentication option on the client's behalf. ...



Google
Web
RFC-Ref