Abstract:
An autonomous system (AS) comprising a topology transparent zone (TTZ) comprising a plurality of TTZ nodes, wherein the plurality of TTZ nodes includes an edge node and an internal node, wherein each of the plurality of TTZ nodes is configured to connect to another TTZ node via an internal link, and a plurality of neighboring external nodes connected to the TTZ edge nodes via a plurality of external links, wherein no link state advertisements (LSAs) describing the internal links are distributed to the neighboring external nodes.
Abstract:
A network node used to construct a topology-transparent zone (TTZ). The network node may obtain a TTZ identifier (ID) that is uniquely associated with a TTZ. Additionally, the network node may obtain a first link that couples the network node to a second network node that is also assigned the TTZ ID and a second link that couples the network node to a third network node that is not assigned the TTZ ID. The network node may generate a router information (RI) link-state advertisement (LSA) that indicates whether the network node is a TTZ edge node or a TTZ internal node and that indicates the TTZ associated with the TTZ. The network node may distribute the RI LSA to the second network node that is also assigned the TTZ ID using the first link.
Abstract:
In a receiver provider edge (PE) router, a method for supporting protocol independent multicast source-specific mode (PIM-SSM) using multicast resource reservation protocol-traffic engineering (mRSVP-TE) comprising the steps of receiving a protocol independent multicast (PIM) join message, in response to receiving the PIM join message sending a path message to a source PE router, wherein the path message is a multicast resource reservation protocol-traffic engineering (mRSVP-TE) message, and sending the PIM join message to the source PE router, wherein the path message and the PIM join message trigger setup of a data multicast data tree (MDT), creating a PIM state, and receiving multicast data traffic via the data MDT using the PIM state.
Abstract:
An apparatus comprising a memory, and a processor coupled to the memory and configured to transmit a backup Label Switched Path (LSP) multicast Resource Reservation Protocol-Traffic Engineering (mRSVP-TE) path request (PATH) message upstream, wherein the backup LSP PATH message requests reservation of a first backup LSP to protect a first primary LSP configured to transmit multicast data, and wherein the backup LSP PATH message is transmitted to support a facility mode one to many (1:N) fast reroute protocol.
Abstract:
A mechanism is disclosed for implementing conditional commands carried by network data packets. A data flow including a data packet is received. The data packet includes a conditional command. A condition and a command are obtained from the conditional command. The mechanism determines that the condition is satisfied. Based on the determination that the condition is satisfied, the command is executed to alter handling of the data flow, alter handling of the data packet, or alter a context for the data flow.
Abstract:
A mechanism is disclosed for implementing conditional commands carried by network data packets. A data flow including a data packet is received. The data packet includes a conditional command. A condition and a command are obtained from the conditional command. The mechanism determines that the condition is satisfied. Based on the determination that the condition is satisfied, the command is executed to alter handling of the data flow, alter handling of the data packet, or alter a context for the data flow.
Abstract:
A method of routing a data packet through a network comprises updating at least one router local forwarding table to include path IDs of network segments defining paths between network nodes and network function bit encoding/decoding information. In response to a data packet arriving at an ingress network node, an encapsulation header including a path ID identifying at least one network segment of an explicit routing path and a bit encoding specifying network functions to be performed on the data packet are encapsulated in unused portions of the source address and/or the destination address in the encapsulation header. A network node in the explicit routing path performs a network function encoded in the source address and/or the destination address of the encapsulation header of the data packet and forwards the data packet based on network function bit encoding/decoding and path ID information in the network node's local updated local forwarding table.
Abstract:
A method implemented by a path computation element centralized controller (PCECC), the method comprises: receiving a service request to provision for a service from a first edge node and a second edge node in a network; computing a path for a label switched path (LSP) from the first edge node to the second edge node in response to the service request; reserving label information for forwarding traffic of the service on the LSP; and sending a label update message to a third node on the path to facilitate forwarding of the traffic of the service on the path, wherein the label update message comprises the label information.
Abstract:
A method implemented in an inter-provider cloud rendezvous point (CRP-IP). The method includes receiving, via a receiver of the CRP-IP, a Register request from a first service provider cloud rendezvous point (CRP-SP) in a first service provider (SP) network domain, the Register request indicating a first portion of a virtual extensible network (VXN) with a global scope is hosted by the first SP network domain; and transmitting, via a transmitter of the CRP-IP, a Report message to a second CRP-SP in a second SP network domain hosting a second portion of the VXN, the Report message indicating the first portion of the VXN is hosted by the first SP network domain.
Abstract:
A method for controlling a data flow in a domain of an OpenFlow protocol controlled software-defined network (SDN) comprising receiving a request from a network element for instructions to route the data flow through the OpenFlow SDN, determining a route for the data flow through the OpenFlow SDN, transmitting a unified header to the network element in the OpenFlow SDN, wherein the unified header facilitates transmission of data flows through the OpenFlow SDN that are encoded according to a plurality of network abstraction types, and transmitting instructions for forwarding the data flow along the route through the OpenFlow SDN, wherein the instructions for forwarding the data flow along the route through the OpenFlow SDN comprise one or more match fields, one or more mask values corresponding to the match fields, and one or more actions for the network element in the OpenFlow SDN to perform on the data flow.