Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

This section compares the networking standards defined in Frame Relay Forum document number FRF.5, Frame Relay/ATM PVC Network Interworking Implementation Agreement, with those defined for the Cisco FRF.5 Frame Relay-to-ATM Network Interworking feature.

The following sections and subsections in this implementation agreement are supported as follows:

• 4.1 Frame Formatting and Delimiting: Only the default (2 octet) address field is supported.
• 4.3 Connection Multiplexing: Mapping one-to-one connections between a Frame Relay data-link connection identifier (DLCI) and Frame Relay service specific convergence sublayer (SSCS) DLCI is done using the default DLCI value of 1022. Mapping many-to-one connections from Frame Relay DLCI to Frame Relay-SSCS DLCI and vice versa is user-configured (and it must be agreed upon between the two ATM end systems).
• 4.5.2.2 Frame Relay to B-ISDN Direction: Backward congestion indication is not supported.
• 5.1 Traffic Management: There is no direct mapping between Frame Relay and ATM traffic parameters; these parameters are configured independently.
• 5.2 PVC Management: PVC management is not supported.
• 5.3 Description of Upper Layer User Protocol Encapsulation Methods: This section applies only to terminal equipment and is not supported.
• 5.4.1 Operations for the Common Part of the AAL Type 5: The error counters mentioned in this section are reset at startup, and are counted until they are reset.

For information about how to configure FRF.5 Frame Relay-ATM Network Interworking, see Configuring Frame Relay-ATM Interworking .

This section compares the networking standards defined in Frame Relay Forum Document Number FRF.8, Frame Relay/ATM PVC Service Interworking Implementation Agreement, with those defined for the Cisco FRF.8 Frame Relay-to-ATM Service Interworking feature.

The following sections and subsections in the FRF.8 agreement are supported as follows:

• 5.1 Traffic Management: There is no direct mapping between the Frame Relay and ATM traffic parameters; these parameters are configured independently.
• 5.2 Frame Relay PVC Management Procedures: Procedures for the asynchronous status message defined in Q.933 annex A are not supported.
• 5.3.1.4 Fragmentation and Reassembly: Fragmentation and reassembly are not supported.
• 5.4 Address Resolution: The IP and IPX protocols are supported.
• 6.0 Operations for the Common Part of the AAL Type 5: The error counters mentioned in this section are reset at startup, and are counted until they are reset.

For information about how to configure FRF.8 Frame Relay-ATM Service Interworking, see Configuring Frame Relay-ATM Interworking .