…lic key with an IPv6 address in the Secure Neighbor Discovery (SEND) protocol [ RFC3971 ]. The basic idea is to generate the interface identifier (i.e., the rightmost 64 bits) of the IPv6 address by computing a cryptographic hash of the public key. The resulting IPv6 address is c…
…ption was obtained has been authenticated (e.g., via Secure Neighbor Discovery [RFC3971]). If the Router Advertisement was authenticated, the valid lifetime of the corresponding address should be set to the Valid Lifetime in the received option. 3. Otherwise, reset the valid life…
…tion was obtained has been authenticated (e.g., via Secure Neighbor Discovery [ RFC3971 ]). If the Router Advertisement was authenticated, the valid lifetime of the corresponding address should be set to the Valid Lifetime in the received option. 3. Otherwise, reset the valid lif…
…tion was obtained has been authenticated (e.g., via Secure Neighbor Discovery [ RFC3971 ]). If the Router Advertisement was authenticated, the valid lifetime of the corresponding address should be set to the Valid Lifetime in the received option. 3. Otherwise, reset the valid lif…
…tion was obtained has been authenticated (e.g., via Secure Neighbor Discovery [ RFC3971 ]). If the Router Advertisement was authenticated, the valid lifetime of the corresponding address should be set to the Valid Lifetime in the received option. 3. Otherwise, reset the valid lif…
…blic signature key to an IPv6 address in the SEcure Neighbor Discovery (SEND) [ RFC3971 ] protocol. Generally, the traditional SLAAC addresses are thought to simplify network management, since they simplify Access Control Lists (ACLs) and logging. However, they have a number of d…
…blic signature key to an IPv6 address in the SEcure Neighbor Discovery (SEND) [ RFC3971 ] protocol. Generally, the traditional SLAAC addresses are thought to simplify network management, since they simplify Access Control Lists (ACLs) and logging. However, they have a number of d…
…In particular, it doesn't impact the application of Secure Neighbor Discovery [ RFC3971 ]. 7 . References 7.1 . Normative References [ RFC2119 ] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14 , RFC 2119 , March 1997. [ RFC3971 ] Arkko, J., Kempf, …