Which two technologies can encapsulate an IPv6 payload in an IPv4 packet for transmission across a network?

Which two technologies can encapsulate an IPv6 payload in an IPv4 packet for transmission across a network? (Choose two)
A. L2TPv3
B. trunking
C. AToM
D. ISATAP
E. NAT-PT

cisco-exams

4 thoughts on “Which two technologies can encapsulate an IPv6 payload in an IPv4 packet for transmission across a network?

  1. Guess it’s AD

    Unlike the above discussed tunneling methods, a translation method provides a way to translate IPv6 to IPv4 traffic and vice versa. When using translation, the traffic is not encapsulated but is converted to the destination type (be that IPv4 or IPv6). There are two methods that are typically used with translated IPv6 networks; these include:

    Network Address Translation—Protocol Translation (NAT-PT) – The NAT-PT method enables the ability to either statically or dynamically configure a translation of a IPv4 network address into an IPv6 network address and vice versa. For those familiar with more typically NAT implementations, the operation is very similar but includes a protocol translation function. NAT-PT also ties in an Application Layer Gateway (ALG) functionality that converts Domain Name System (DNS) mappings between protocols.

  2. DE

    https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/interface/configuration/xe-3s/ir-xe-3s-book/ip6-isatap-xe.html

    Overlay Tunnels for IPv6
    Overlay tunneling encapsulates IPv6 packets in IPv4 packets for delivery across an IPv4 infrastructure (a core network or the figure below).

    https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_nat/configuration/15-mt/nat-15-mt-book/ip6-natpt.html

    Network Address Translation (NAT)-Port Translation (PT) for Cisco software based on RFC 2766 and RFC 2765 is a migration tool that helps customers transition their IPv4 networks to IPv6 networks.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.