RFC 4891:Using IPsec to Secure IPv6-in-IPv4 Tunnel...
RFC-Ref

prefix


Click on the red underlined text to get to the source

... the tunnel could come from a wide range of IPv6 prefixes, so binding IPv6 addresses ...
... IPv6 source addresses coming from a well-known prefix, whereas the destination addresses could be any nodes on the Internet ...
... In this case, an IPsec tunnel mode SA could be bound to the prefix that was allocated to the router at Site B, and Router ...
... Router A could verify that the source address of the packet matches the prefix. Site B will not be able to do a similar verification for the packets it ...


... of the traffic could come from a wide range of prefixes that are normally learned through routing. As routing ...
... routing. As routing can always learn a new prefix, one cannot assume that all the prefixes are known a priori [RFC3884 ...
... routing can always learn a new prefix, one cannot assume that all the prefixes are known a priori [RFC3884]. This mainly affects scenario (1). ...


... SPD (SSPD) tunnel mode. Such usage is more complicated because IPv6 prefixes need to be known a priori, and multicast and link-local ...


... somehow (e.g., using authentication protocol and obtaining a static v6 prefix), someone might be able to spoof the signaling (control plane security ...


... router/router-to-site scenarios (i.e., when the IPv6 prefixes can be known a priori), and it offers only a limited set of features (e.g., no multicast) compared with a ...



Google
Web
RFC-Ref