Abstract: Providing protection to network traffic includes sending a Pseudowire protection configuration parameter for configuring a standby Pseudowire between a source node and a destination node, receiving a Pseudowire configuration acknowledgement indicating whether the Pseudowire protection configuration parameter has been accepted by the destination node, and in the event that the Pseudowire protection configuration parameter has been accepted by the destination node, using the standby Pseudowire, wherein the standby Pseudowire's configured based at least in part on the Pseudowire protection configuration parameter.

Abstract: A technique for communicating in a network management system is disclosed. The technique includes transferring information from an application server to a gateway that processes the information, transferring the gateway processed information from the gateway to a plurality of adapters associated with the gateway that process the gateway processed information, and transferring the adapter processed information from one of the adapters to a client.

Abstract: Data is transferred. A data packet associated with an application flow is received. A Pseudowire label is determined based at least in part on an application header associated with the data packet. The data packet is encapsulated with the Pseudowire label. The data packet is transferred over a Pseudowire using the Pseudowire label.

Abstract: Communicating is disclosed. A first communication associated with a first mechanism for configuring a pseudo-wire is received. The first communication is transformed into a second communication, where the second communication is associated with a second mechanism for configuring a pseudo-wire. The second communication is transmitted, where a pseudo-wire that is configured using the second communication is associated with (1) a first node that is configured to support the first mechanism and (2) a second node that is configured to support the second mechanism.

Abstract: A system and method are disclosed for processing a packet. Processing the packet comprises receiving the packet; translating the packet from a first protocol-specific format to a canonical packet format; translating the packet from the canonical packet format to a second protocol-specific format; and forwarding the packet.

Abstract: Providing a label is disclosed. A first message is transmitted to an access device where the first message includes a set of available labels. A second message is received from the access device where the second message includes a label from the set of available labels selected to be used by the access device. The set of available labels is updated to account for the label selected by the access device.

Abstract: A technique for communicating in a network management system is disclosed. The technique includes transferring information from an application server to a gateway that processes the information, transferring the gateway processed information from the gateway to a plurality of adapters associated with the gateway that process the gateway processed information, and transferring the adapter processed information from one of the adapters to a client.

Abstract: Transferring data in a network is disclosed. Transferring includes receiving a Provider Backbone Transport (PBT) frame, identifying a plurality of location specific identifiers in the PBT frame, mapping the PBT frame to a service based at least in part on the plurality of location specific identifiers, formatting the PBT frame according to the service to obtain a service frame, and transferring the service frame to a network associated with the service.

Abstract: Transferring data over a network includes identifying an application flow and mapping the application flow to a network bound connection.

Abstract: Data is transferred. A data packet associated with an application flow is received. A Pseudowire label is determined based at least in part on an application header associated with the data packet. The data packet is encapsulated with the Pseudowire label. The data packet is transferred over a Pseudowire using the Pseudowire label.

Abstract: Communicating is disclosed. A first communication associated with a first mechanism for configuring a pseudo-wire is received. The first communication is transformed into a second communication, where the second communication is associated with a second mechanism for configuring a pseudo-wire. The second communication is transmitted, where a pseudo-wire that is configured using the second communication is associated with (1) a first node that is configured to support the first mechanism and (2) a second node that is configured to support the second mechanism.

Abstract: A system and method are disclosed for processing a packet. Processing the packet comprises receiving the packet; translating the packet from a first protocol-specific format to a canonical packet format; translating the packet from the canonical packet format to a second protocol-specific format; and forwarding the packet.

Abstract: A technique for creating a connection is disclosed. The technique includes receiving instructions to set a first endpoint, receiving instructions to set a second endpoint, receiving instructions to set a connection between the first and second endpoints, and transferring the instructions to set the two endpoints and the connection to network elements associated with the two endpoints after receiving the instructions to set the connection. A technique for retrieving a connection endpoint index from a connection table is also disclosed. The technique includes reading a common index column element, wherein the common index column contains indexes corresponding to a plurality of service types, and interpreting the index column element based on an interface index that identifies the service type.

Abstract: A system and method are disclosed for processing a packet. Processing the packet comprises receiving the packet; translating the packet from a first protocol-specific format to a canonical packet format; translating the packet from the canonical packet format to a second protocol-specific format; and forwarding the packet.

Abstract: Data is transferred. A data packet associated with an application flow is received. A Pseudowire label is determined based at least in part on an application header associated with the data packet. The data packet is encapsulated with the Pseudowire label. The data packet is transferred over a Pseudowire using the Pseudowire label.

Abstract: A technique for communicating in a network management system is disclosed. The technique includes transferring information from an application server to a gateway that processes the information, transferring the gateway processed information from the gateway to a plurality of adapters associated with the gateway that process the gateway processed information, and transferring the adapter processed information from one of the adapters to a client.

Abstract: Providing a label is disclosed. A first message is transmitted to an access device where the first message includes a set of available labels. A second message is received from the access device where the second message includes a label from the set of available labels selected to be used by the access device. The set of available labels is updated to account for the label selected by the access device.

Abstract: A technique for communicating in a network management system is disclosed. The technique includes transferring information from an application server to a gateway that processes the information, transferring the gateway processed information from the gateway to a plurality of adapters associated with the gateway that process the gateway processed information, and transferring the adapter processed information from one of the adapters to a client.

Abstract: Providing protection to network traffic includes sending a Pseudowire protection configuration parameter for configuring a standby Pseudowire between a source node and a destination node, receiving a Pseudowire configuration acknowledgement indicating whether the Pseudowire protection configuration parameter has been accepted by the destination node, and in the event that the Pseudowire protection configuration parameter has been accepted by the destination node, using the standby Pseudowire, wherein the standby Pseudowire's configured based at least in part on the Pseudowire protection configuration parameter.

Abstract: Transferring data in a network is disclosed. Transferring includes receiving a Provider Backbone Transport (PBT) frame, identifying a plurality of location specific identifiers in the PBT frame, mapping the PBT frame to a service based at least in part on the plurality of location specific identifiers, formatting the PBT frame according to the service to obtain a service frame, and transferring the service frame to a network associated with the service.