Routes from different customers with the same IPv4 address prefix are treated as equivalent by MP-BGP.

MP-BGP will advertise routes to other BGP sessions on the same PE without the need of policies.

The multi-protocol nature of MP-BGP allows VPRN routes to be converted into IPv4 routes in the provider core network.

MP-BGP is an enhanced version of BGP that can carry customer route prefixes for multiple VPRNs.

IPCP

LDP

PPP

TLDP

The outer label allows traffic to transit across the MPLS network.

The inner label identifies the VPRN service.

MP-BGP is used to signal VPRN labels.

The VPRN service label contains the customer's IP address.

1520

1540

1548

1556

A VPLS service does not use a MAC FDB.

A single MAC FDB is shared by all VPLS services on a PE.

A separate MAC FDB is used on the PE for each VPLS service.

Each VPLS service uses a separate MAC FDBs for unicast and multicast traffic.

An IES can only have one interface.

An IES interface can have an SDP or a SAP.

An IES can perform fragmentation.

An IES must have an IP address assigned to it.

Multiple MP-BGP sessions are required to carry VPN-IPv4 and VPN-IPv6 routes.

PE routers must support both IPv4 and IPv6 addresses; customer routers can use either one

In 6VPE, MP-BGP is used to advertise IPv6 prefixes and the associated VPRN label.

In 6VPE, the provider core routers are IPv6-unaware.

All of the above statements are true.

All of the above statements are false.