Cisco Cisco IOS Software Release 12.0(13)S7

OC-48 PoS SPA—Frame Relay 

OC-192 PoS SPA—Frame Relay 

For ingress 1c/1D and nC/nD policies, primary-level hierarchical policing is not supported for IPv6 
traffic.

Frame Relay is used as a way to offer multiple service levels for a customer link. The IPv6 over Frame 
Relay feature allows users to configure IPv6 addresses over Frame Relay physical interfaces and 
subinterfaces on Engine 3 and Engine 5 line cards in Cisco 12000 series Internet routers and to send IPv6 
traffic over the Frame Relay interfaces. The supported Frame Relay encapsulations are Cisco Frame 
Relay and Internet Engineering Task Force (IETF) Frame Relay. 

IPv6 is tunneled over dual-stack MPLS networks (that is, 6PE) on Frame Relay encapsulated links with 
QoS and access lists (ACLs) enabled. IPv6 ACLs are supported on Frame Relay encapsulated links in 
the same way they are supported in IPv4.

The IETF Frame Relay encapsulation with network layer protocol ID (NLPID) format uses fast path with 
the Engine 3 and Engine 5 line cards.

IPv6 over Frame Relay encapsulation support on Cisco 12000 series Internet routers line cards is 
required for service providers (SPs) who offer 6PE service. Frame Relay encapsulation is configured on 
the main interface of the supported line cards. Users can configure either Cisco or IETF Frame Relay 
encapsulation on the main interface.

The Frame Relay encapsulation type set on an interface affects the NLPID in the 4-byte encapsulation 
that is added to any packets that egress out of the interface. However, in the ingress direction both 
NLPIDs corresponding to the two Frame Relay encapsulations are recognized. Only 10-bit data-link 
connection identifier (DLCI) address field packets are recognized. 

Frame Relay subinterfaces are supported on the line-card main interfaces configured with Frame Relay 
encapsulation. A user can configure a subinterface with a given DLCI.