Print-Ready Version

MPLS Conformance Test Suites

Part Number 801111 - MPLS/RSVP-TE Conformance Test Suite

The Telcordia® Multi-protocol Label Switching (MPLS) Conformance Test Suite for Resource Reservation Protocol Traffic Engineering (RSVPTE) Test Suite provides a fully automated conformance testing of MPLS network equipment, such as Label Edge Routers (LERs) or intermediate Label Switch Routers (LSRs) system equipment, that implement RSVP signaling requirement.

The Telcordia® MPLS RSVPTE Conformance Test Suite assesses a system's ability to conform to the following standards from the Internet Engineering Task Force (IETF):

  • RFC 2205 Resource ReSerVation Protocol (RSVP)
  • RFC 3209 RSVP-TE: Extensions tot RSVP for LSP Tunnels

The Telcordia® MPLS RSVPTE Conformance Test Suite implements the following tests:

  • MPLS Forum RSVPTE test cases as specified in the MPLS Forum MPLS Forum RSVP-TE Conformance Test Coverage Document, October 2002
  • Telcordia supplemental RSVPTE test cases

The test suite consists of the following conformance test groups:

  • MPLS Forum Test Cases
    • IngressLER - these test cases verify the Implementation Under Test (IUT) IUT's functionality for sending a Path message with correct format in the optional and mandatory object field and responding correctly when it receives other PDUs (Protocol Date Unit).
    • EgressLER - these test cases verify the IUT's functionality for sending a Resv message with correct format and responding correctly when it receives other PDUs.
    • IntermediateLSR - these test group covers the IUT's capabilities to correctly forwarding the Path and Resv messages.
      • Session Attribute - these test cases verify the IUT's functionality for correctly forwarding the Session attribute object in the Path messages.
      • Label and Label Request - these test cases verify the IUT's functionality for correctly forwarding the Label and Label request object in the Resv messages.
      • Record Route - these test cases verify the IUT's functionality for correctly forwarding the Record route object in the Path and Resv messages.
      • Explicit Route - these test cases verify the IUT's functionality for correctly forwarding the Explicit route object in the Path messages.
      • Message Forwarding - these test cases verify the IUT's functionality for correctly forwarding PathTear and ReseTear messages.
      • Additional Object Class and class Type - these test cases verify the IUT's functionality for correctly forwarding the Path message when it receives a Path message containing object class and class type.
    • Error Condition - these test cases verify the IUT's functionality for correctly responding error message with PathError or ResvError message with correct error code and value.
    • Optional Hello Extension - these test cases verify the IUT's functionality to correctly handle the Hello message when the IUT supports the Hello extension.
  • Telcordia Technologies Supplemental Test Cases
    • IngressLER - these additional test cases from Telcordia verify the IUT's functionality for sending a Path message with correct format in the optional and mandatory object field and responding correctly when it receives other PDUs.
    • EgressLER - these additional test cases verify the IUT's functionality for sending a Resv message with correct format and responding correctly when it receives other PDUs.
    • IntermediateLSR - these test group covers the IUT's capabilities to correctly forwarding the Path and Resv messages.
      • Session Attribute - these additional test cases verify the IUT's functionality for correctly forwarding the Session attribute object in the Path messages.
      • Label and Label Request - these additional test cases verify the IUT's functionality for correctly forwarding the Label and Label request object in the Resv messages.
      • Record Route - these additional test cases verify the IUT's functionality for correctly forwarding the Record route object in the Path and Resv messages.
      • Explicit Route - these additional test cases verify the IUT's functionality for correctly forwarding the Explicit route object in the Path messages.
      • Message Forwarding - these additional test cases verify the IUT's functionality for correctly forwarding PathTear and ReseTear messages.
      • Additional Object Class and class Type - these additional test cases verify the IUT's functionality for correctly forwarding the Path message when it receives a Path message for correctly forwarding the Path message when it receives a Path message containing object class and class type.
    • Error Condition - these additional test cases verify the IUT's functionality for correctly responding error message with PathError or ResvError message with correct error code and value.
    • Optional Hello Extension - these additional test cases verify the IUT's functionality to correctly handle the Hello message when the IUT supports the Hello extension.

Part Number 801112 - MPLS/RSVP-TE Refresh Overhead Reduction Conformance Test Suite

The Telcordia® Multi-protocol Label Switching (MPLS) Conformance Test Suite for Resource Reservation Protocol Refresh Overhead Reduction Extensions (RSVPROR) Test Suite provides for fully automated conformance testing of MPLS network equipment, such as Label Edge Routers (LERs) and Label Switch Routers (LSRs) that implement RSVP signaling and RSVP refresh overhead reduction requirements.

The Telcordia® MPLS RSVPROR Conformance Test Suite assesses a system's ability to conform to the following standards from the Internet Engineering Task Force (IETF):

  • RFC 2961 - RSVP Refresh Overhead Reduction Extensions

The test suite consists of the following conformance test groups:

  • Trigger_Refresh_Message - tests in this group verify an Implementation Under Test's (IUT's) ability to correctly send refresh Path and Resv message.
  • Refresh_Reduction_Capable_Bit - tests in this group verify an IUT's ability to correctly send and receive Protocol Data Units (PDUs) when it supports or does not support the refresh overhead reduction extensions.
  • RSVP_Bundle_Message - tests in this group verify an IUT's ability to correctly send and receive the Bundle message.
    • Bundle_Header - tests in this group verify an IUT's ability to correctly set the Refresh-Reduction-Capable bit in the header of the Bundle message.
    • Message_Formats - tests in this group verify an IUT's ability to send a properly formatted Bundle message.
    • Sending_RSVP_Bundle_Message - tests in this group verify an IUT's ability to correctly send a Bundle message.
    • Receiving_RSVP_Bundle_Message - tests in this group verify an IUT's ability to correctly receive a Bundle message.
  • MESSAGE_ID_Extension - tests in this group verify an IUT's ability to support the MESSAGE_ID extensions.
    • Modification_Standard_Message_Formats - tests in this group verify an IUT's ability to include the MESSAGE_ID, MESSAGE_ID_ACK, and MESSAGE_ID_ACK object fields in the standard RSVP message.
    • MESSAGE_ID_Objects - tests in this group verify an IUT's ability to acknowledge a received message according to the contents of the MESSAGE_ID object field.
    • MESSAGE_ID_ACK_NACK_Object - tests in this group verify an IUT's ability to correctly acknowledge a received message according to the contents of the MESSAGE_ID_ACK object.
    • ACK_Message_Format - tests in this group verify an IUT's ability to send a properly formatted ACK message.
    • MESSAGE_ID_Object_Usage - tests in this group verify an IUT's ability to send and receive RSVP messages according to the contents of the MESSAGE_ID_Object.
    • MESSAGE_ID_ACK_NACK_Object_Usage - tests in this group verify an IUT's ability to send and receive RSVP messages according to the contents of the MESSAGE_ID_ACK Object.
    • Compatibility - tests in this group verify an IUT's ability to correctly acknowledge a system that does not support the MESSAGE_ID class.
  • Summary_Refresh_Extension - tests in this group verify an IUT's ability to support the Summary_Refresh_Extension extensions.
    • MESSAGE_ID_SRC_MCAST_LIST - tests in this group verify an IUT's ability to send Srefresh messages with a properly formatted MESSAGE_ID LIST object.
    • Srefresh_Message_Format - tests in this group verify an IUT's ability to send properly formatted Srefresh messages.
    • Srefresh_NACK - tests in this group verify an IUT's ability to correctly send Srefresh Nack messages.
    • Compatibility - tests in this group verify an IUT's ability to indicate support for Summary Refresh Extensions in Path and Resv messages.
  • Exponential_Back_Off_Procedures - tests in this group verify an IUT's implementation of a mechanism for exponential back-off for retransmission.
    • Time_Parameters - tests in this group verify an IUT's ability to correctly retransmit an unacknowledged message within the rapid retransmission interval.
  • Non_Mandatory - tests in this group verify an IUT's ability to correctly react to non-mandatory situations.
    • Srefresh_Message_Format - tests in this group verify an IUT's ability to correctly send the Srefresh message.

Part Number 801114 - MPLS/CR-LDP Conformance Test Suite

The Telcordia® MPLS/CR-LDP Conformance Test Suite provides for fully automated conformance testing of MPLS network equipment, such as Label Switching Routers (LSRs), that implement LDP/CR-LDP signaling requirements for label distribution in support of MPLS forwarding along normally routed paths. CR-LDP (constraint-based routed label distribution protocol) and LDP are two closely related MPLS signaling protocols that establish tunnels for forwarding data. LDP provides while CR-LDP expands LDP by adding constraint-based routing capabilities for traffic engineering.

The Telcordia® MPLS LDP/CR-LDP Conformance Test Suite assesses a system's ability to conform to the following standards from the Internet Engineering Task Force (IETF):

  • RFC 3036 LDP Specification
  • RFC 3212 Constraint-Based LSP Setup using LDP

The Telcordia® MPLS LDP/CR-LDP Conformance Test Suite implements the following tests:

  • MPLS Forum LDP test cases as specified in the MPLS Forum 3.0 MPLS Forum LDP Conformance Implementation Agreement, December 2002
  • Telcordia supplemental LDP test cases
  • Telcordia CR-LDP test cases

The test suite consists of the following conformance test groups:

  • MPLS Forum: Basic And Extended LDP Discovery - tests in this group verify basic and extended LDP discovery procedures which enable an LSR to discover potential LDP peers using link Hello messages and targeted Hello messages.
  • MPLS Forum: Transport Connection Establishment - tests in this group verify TCP transport connection establishment and address scenarios where the System Under Test (SUT) plays the active and passive roles. The correct use of the Transport Address TLV is also tested.
  • MPLS Forum: Session Initialization - tests in this group verify establishment of sessions between LSRs and verify the SUT's implementation of the Initialization state machine.
  • MPLS Forum: Session Finite State Machine - tests in this group verify the SUT's implementation of the Initialization finite state machine, exercising all state transitions and output due to various input.
  • MPLS Forum: Loop Detection - this group of tests verifies the SUT's implementation of the optional Loop Detection Procedure based on Hop Count and Path Vector TLVs.
  • MPLS Forum: Notification Procedures - this group of tests verifies that the SUT sends a Notification for most or all of the Status Codes defined.
  • MPLS Forum: Message Procedures - this group of tests verifies that the SUT implements the proper procedures for the generation and reception of all types of LDP messages.
  • Telcordia Technologies: Supplemental Test Cases - this group provides additional tests in many of the areas listed above, which are not specified by the MPLS Forum. These additional tests enhance the test coverage by expanding its scope.
  • Telcordia Technologies: CR-LSP Test Cases - this group verifies the constraint-based LSP Setup using LDP procedures. It exercises the optional TLVs such as ER TLV, Traffic TLV, Pinning TLV, Resource Class TLV and Preemption TLV.