Abstract: A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) enabled data plane for fifth generation (5G) transport. The method includes setting an indicator in a flags field of a SRV6 header of a data packet that an MTNC-ID type-length-value (TLV) is included in a TLV field of the SRV6 header. The MTNC-ID TLV for the MTNC-ID is inserted in the TLV field of the SRV6 header of the data packet. The data packet with the SRV6 header containing the MTNC-ID is transmitted over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID.

Abstract: A method used by a domain name system (DNS) server is disclosed. The DNS server receives a DNS request containing a host name and a resource record specifying data. The DNS server resolves an internet protocol (IP) address based on the host name. The DNS server resolves a server address of a resource server containing the data specified in the resource record. The DNS server transmits a DNS response including the IP address and the server address.

Abstract: A method performed by a Next Generation Node B (gNB) in a communications system implementing User Datagram Protocol (UDP) comprises indicating that a data packet comprises a multi-transport network context-identifier (MTNC-ID) corresponding to a forwarding path and being associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for traffic forwarding on the forwarding path, inserting the MTNC-ID into a Generic UDP Encapsulation (GUE) header of the data packet, and transmitting the data packet to a network element (NE) in the communications system based on the forwarding path corresponding to the MTNC-ID.

Abstract: A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) enabled data plane for fifth generation (5G) transport. The method includes setting an indicator in a flags field of a SRV6 header of a data packet that an MTNC-ID type-length-value (TLV) is included in a TLV field of the SRV6 header. The MTNC-ID TLV for the MTNC-ID is inserted in the TLV field of the SRV6 header of the data packet. The data packet with the SRV6 header containing the MTNC-ID is transmitted over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID.

Abstract: A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) header for fifth generation (5G) transport. The method receives a data packet that includes an MTNC-ID in a data plane header of the data packet. The MTNC-ID is extracted from the data plane header of the data packet, and is encapsulated in an argument field in a last segment of a segment list (SL[0]) of the SRV6 header of the data packet. An instruction for forwarding the MTNC-ID is encapsulated within a function field in the SL[0] of the SRH of the data packet. The data packet is transmitted over a SRV6 enabled data plane domain along a forwarding path corresponding to the MTNC-ID.

Abstract: A service classifier network device receives a subflow and identifies that the subflow is one of at least two subflows in a multipath data flow. Related data packets are sent from a source node to a destination node in the multipath data flow. The service classifier generates a multipath flow identifier and encapsulates the subflow with a header to produce an encapsulated first subflow. The header identifies a service function path and includes metadata with the multipath flow identifier.

Abstract: A service classifier network device receives a subflow and identifies that the subflow is one of at least two subflows in a multipath data flow. Related data packets are sent from a source node to a destination node in the multipath data flow. The service classifier generates a multipath flow identifier and encapsulates the subflow with a header to produce an encapsulated first subflow. The header identifies a service function path and includes metadata with the multipath flow identifier.

Abstract: In one example embodiment, a system and method is illustrated that includes receiving connectivity data for at least one network device, the connectivity data describing a connection to the at least one network device within an area. The system and method further includes processing the connectivity data to obtain a routing update for distribution to another network device outside the area. Additionally, the system and method includes a routing summary in the routing update, the routing summary including an address prefix. Further, the system and method includes reachability information in the routing update, the reachability information including an address for the at least one network device.

Abstract: In an embodiment, a method is provided for regulating network traffic and virtual private networks. In this method, network traffic transmitted along multiple communication paths is received, and these communication paths are associated with forwarding identifiers. A portion of the forwarding identifiers is identified to match a particular forwarding identifier associated with a particular virtual private network. At the same time, the policy associated with the particular virtual private network is identified. A portion of the network traffic that is associated with the portion of the identified forwarding identifiers can then be regulated based on the policy.

Abstract: Systems and/or methods of secure communication of information between multi-domain virtual private networks (VPNs) are presented. A dynamic group VPN (DGVPN) can reside in one domain and a disparate DGVPN can reside in a disparate domain. An administrative security authority (ASA) can be employed in each domain. Each ASA can generate and exchange respective keying material and crypto-policy information to be used for inter-domain communications when routing data from a member in one DGVPN to a member(s) in the disparate DGVPN, such that an ASA in one domain can facilitate encryption of data in accordance with the policy of the other domain before the data is sent to the other domain. Each ASA can establish a key server to generate the keying material and crypto-policy information associated with its local DGVPN, and such material and information can be propagated to intra-domain members.

Abstract: In one embodiment, label distribution sessions are established between a Modular Cable Modem Termination System (M-CMTS) core and one or more remote PHYs. The label distribution sessions facilitate association of labels with either Radio Frequency (RF) channels or groups of the RF channels that extend from the remote PHYs to one or more cable modems. The labels are then used to facilitate communications between the M-CMTS core and the remote PHYs over a MultiProtocol Label Switching (MPLS) network.

Abstract: In one example embodiment, a system and method is illustrated that includes receiving connectivity data for at least one network device, the connectivity data describing a connection to the at least one network device within an area. The system and method further includes processing the connectivity data to obtain a routing update for distribution to another network device outside the area. Additionally, the system and method includes a routing summary in the routing update, the routing summary including an address prefix. Further, the system and method includes reachability information in the routing update, the reachability information including an address for the at least one network device.

Abstract: In one example embodiment, a system and method are shown that includes receiving information defining a route to a network device. Further, a routing summary summarizing the route to the network device is generated. Additionally, an aggregate label is selected that corresponds to a defined class and to the routing summary. Moreover, the aggregate label and the defined class are advertised into a domain.

Abstract: A method is provided for generating a backup route. Here, a route and a route distinguisher type associated with the route are received and a backup route is generated based on attributes of the route. A particular backup route distinguisher type that is associated with the route distinguisher type is assigned to the backup route. The backup route with the backup route distinguisher type are then advertised. Another method is provided that identifies the backup route. When the route and its route distinguisher type are received from the advertisement, an identification is made as to whether the route distinguisher type is assigned to a backup route. The route may then be designated as a backup route based on the identification.

Abstract: A virtual private network (VPN) is formed with a pair of autonomous systems (ASes) connected by each having at least two autonomous system border routers (ASBRs) connected to the corresponding ASBRs at the other AS, referred to as an Option B VPN-IPv4 network. Route reflectors (RRs) only reflect the best Border Gateway Protocol (BGP) paths, providing no backup BGP paths for fast convergence. Advantageously, an automatic route distinguisher (RD) rewrite component at the ASBRs creates unique prefixes and advertises the original RD as transitive attribute in an update message to external AS peers. Each RD gets mapped to another unique prefix at the ASBR and also that two ASBRs will create different unique prefixes. Thus, the route reflector sees different prefixes and reflects all of them. The ingress provider edge (PE) router can import the prefixes and correctly obtain the alternate paths for fast convergence.

Abstract: In an embodiment, a method is provided for regulating network traffic and virtual private networks. In this method, network traffic transmitted along multiple communication paths is received, and these communication paths are associated with forwarding identifiers. A portion of the forwarding identifiers is identified to match a particular forwarding identifier associated with a particular virtual private network. At the same time, the policy associated with the particular virtual private network is identified. A portion of the network traffic that is associated with the portion of the identified forwarding identifiers can then be regulated based on the policy.

Abstract: In one embodiment, label distribution sessions are established between a Modular Cable Modem Termination System (M-CMTS) core and one or more remote PHYs. The label distribution sessions facilitate association of labels with either Radio Frequency (RF) channels or groups of the RF channels that extend from the remote PHYs to one or more cable modems. The labels are then used to facilitate communications between the M-CMTS core and the remote PHYs over a MultiProtocol Label Switching (MPLS) network.

Abstract: A method is provided for generating a backup route. Here, a route and a route distinguisher type associated with the route are received and a backup route is generated based on attributes of the route. A particular backup route distinguisher type that is associated with the route distinguisher type is assigned to the backup route. The backup route with the backup route distinguisher type are then advertised. Another method is provided that identifies the backup route. When the route and its route distinguisher type are received from the advertisement, an identification is made as to whether the route distinguisher type is assigned to a backup route. The route may then be designated as a backup route based on the identification.

Abstract: A virtual private network (VPN) is formed with a pair of autonomous systems (ASes) connected by each having at least two autonomous system border routers (ASBRs) connected to the corresponding ASBRs at the other AS, referred to as an Option B VPN-IPv4 network. Route reflectors (RRs) only reflect the best Border Gateway Protocol (BGP) paths, providing no backup BGP paths for fast convergence. Advantageously, an automatic route distinguisher (RD) rewrite component at the ASBRs creates unique prefixes and advertises the original RD as transitive attribute in an update message to external AS peers. Each RD gets mapped to another unique prefix at the ASBR and also that two ASBRs will create different unique prefixes. Thus, the route reflector sees different prefixes and reflects all of them. The ingress provider edge (PE) router can import the prefixes and correctly obtain the alternate paths for fast convergence.

Abstract: In one embodiment, label distribution sessions are established between a Modular Cable Modem Termination System (M-CMTS) core and one or more remote PHYs. The label distribution sessions facilitate association of labels with either Radio Frequency (RF) channels or groups of the RF channels that extend from the remote PHYs to one or more cable modems. The labels are then used to facilitate communications between the M-CMTS core and the remote PHYs over a MultiProtocol Label Switching (MPLS) network.