Abstract: Services with policy control may be provided. A computing device may receive registration information associated with a border device. The registration information may comprise information identifying a service provided by a server associated with the border device, information identifying the border device, and policies associated with the service. Then an address for the server may be determined. Next a request may be received comprising the information identifying the service provided by the server. In response to receiving the request comprising the information identifying the service provided by the server, the address for the server, the information identifying the border device, and the policies associated with the service may be provided.

Abstract: A system and method for onboarding a virtual machine in a bridge host extension mode are provided. The method includes: creating a virtual machine on a host computing device, wherein the host computing device is associated with a first MAC address and a first IP address; assigning the virtual machine a second MAC address by the host computing device; receiving a first DHCP packet from the virtual machine by the host computing device, wherein the first DHCP packet comprises a first field that includes the second MAC address; replacing the second MAC address in the first field with the first MAC address by the host computing device; adding the second MAC address to a second field of the first DHCP packet by the host computing device; and providing the first DHCP packet to a DHCP server through a network by the host computing device.

Abstract: Services with policy control may be provided. A computing device may receive registration information associated with a border device. The registration information may comprise information identifying a service provided by a server associated with the border device, information identifying the border device, and policies associated with the service. Then an address for the server may be determined. Next a request may be received comprising the information identifying the service provided by the server. In response to receiving the request comprising the information identifying the service provided by the server, the address for the server, the information identifying the border device, and the policies associated with the service may be provided.

Abstract: A system and method for onboarding a virtual machine in a bridge host extension mode are provided. The method includes: creating a virtual machine on a host computing device, wherein the host computing device is associated with a first MAC address and a first IP address; assigning the virtual machine a second MAC address by the host computing device; receiving a first DHCP packet from the virtual machine by the host computing device, wherein the first DHCP packet comprises a first field that includes the second MAC address; replacing the second MAC address in the first field with the first MAC address by the host computing device; adding the second MAC address to a second field of the first DHCP packet by the host computing device; and providing the first DHCP packet to a DHCP server through a network by the host computing device.

Abstract: Differentiated sidecars in a service mesh may be provided. A first routing rule includes a first plurality of weights to be associated with a first plurality of data paths of a first microservice instance may be received. Next, first mapping between a first set of features associated with the first microservice instance and the first plurality of weights may be determined. Then a second microservice instance may be detected and a second set of features associated with the second microservice instance may be detected. A second routing rule comprising a second plurality of weights to be associated with a second plurality of data paths of the second microservice instance may be determined. The second plurality of weights may be determined such that a second mapping between the second set of features and the second plurality of weights imitates the first mapping.

Abstract: Services with policy control may be provided. A computing device may receive registration information associated with a border device. The registration information may comprise information identifying a service provided by a server associated with the border device, information identifying the border device, and policies associated with the service. Then an address for the server may be determined. Next a request may be received comprising the information identifying the service provided by the server. In response to receiving the request comprising the information identifying the service provided by the server, the address for the server, the information identifying the border device, and the policies associated with the service may be provided.

Abstract: A map server/map resolver (MS/MR) of a Locator ID Separation Protocol (LISP) control plane for an enterprise private network for group-based service insertion is described. The MS/MR may facilitate communications from a first host having a first endpoint ID (EID) and located at a first tunnel router having a first routing locator (RLOC), to a second host having a second EID and located at a second tunnel router having a second RLOC. The MS/MR receives, from the first tunnel router, a map request for requesting an EID-to-RLOC mapping associated with the second EID and including a group identifier. The MS/MR selects a service insertion policy including an address of a service border router for a service that is registered with the MS/MR, and responds with a map reply including the address for populating an overlay route for forwarding communications via the service border router for insertion of the registered service.

Abstract: Services with policy control may be provided. A computing device may receive registration information associated with a border device. The registration information may comprise information identifying a service provided by a server associated with the border device, information identifying the border device, and policies associated with the service. Then an address for the server may be determined. Next a request may be received comprising the information identifying the service provided by the server. In response to receiving the request comprising the information identifying the service provided by the server, the address for the server, the information identifying the border device, and the policies associated with the service may be provided.

Abstract: Differentiated sidecars in a service mesh may be provided. A first routing rule includes a first plurality of weights to be associated with a first plurality of data paths of a first microservice instance may be received. Next, first mapping between a first set of features associated with the first microservice instance and the first plurality of weights may be determined. Then a second microservice instance may be detected and a second set of features associated with the second microservice instance may be detected. A second routing rule comprising a second plurality of weights to be associated with a second plurality of data paths of the second microservice instance may be determined. The second plurality of weights may be determined such that a second mapping between the second set of features and the second plurality of weights imitates the first mapping.

Abstract: Systems and methods are disclosed for processing framed routes initiated by user equipment (UE) at customer-premises equipment (CPE) and gateways using protocol configuration options (PCO). The PCO can include encoding and decoding framed route information using a PCO information element (IE). The framed route information can include a framed route and a virtual private networking routing and forwarding (VRF) name. The framed route information can also include a tunnel identifier and a packet data protocol (PDP) address. The gateway can include a packet data network gateway (PGW) and a gateway general packet radio service support node (GGSN). When the gateway receives an attach request message from the UE with the encoded PCO, the gateway decodes the PCO to extract the framed route and VRF name, associates a tunnel identifier and PDP address with the extracted framed route and VRF name, and installs the framed route in a corresponding VRF.

Abstract: Systems and methods are disclosed for processing framed routes initiated by user equipment (UE) at customer-premises equipment (CPE) and gateways using protocol configuration options (PCO). The PCO can include encoding and decoding framed route information using a PCO information element (IE). The framed route information can include a framed route and a virtual private networking routing and forwarding (VRF) name. The framed route information can also include a tunnel identifier and a packet data protocol (PDP) address. The gateway can include a packet data network gateway (PGW) and a gateway general packet radio service support node (GGSN). When the gateway receives an attach request message from the UE with the encoded PCO, the gateway decodes the PCO to extract the framed route and VRF name, associates a tunnel identifier and PDP address with the extracted framed route and VRF name, and installs the framed route in a corresponding VRF.

Abstract: Systems and methods are disclosed for processing framed routes initiated by user equipment (UE) at customer-premises equipment (CPE) and gateways using protocol configuration options (PCO). The PCO can include encoding and decoding framed route information using a PCO information element (IE). The framed route information can include a framed route and a virtual private networking routing and forwarding (VRF) name. The framed route information can also include a tunnel identifier and a packet data protocol (PDP) address. The gateway can include a packet data network gateway (PGW) and a gateway general packet radio service support node (GGSN). When the gateway receives an attach request message from the UE with the encoded PCO, the gateway decodes the PCO to extract the framed route and VRF name, associates a tunnel identifier and PDP address with the extracted framed route and VRF name, and installs the framed route in a corresponding VRF.

Abstract: Systems and methods are disclosed for processing framed routes initiated by user equipment (UE) at customer-premises equipment (CPE) and gateways using protocol configuration options (PCO). The PCO can include encoding and decoding framed route information using a PCO information element (IE). The framed route information can include a framed route and a virtual private networking routing and forwarding (VRF) name. The framed route information can also include a tunnel identifier and a packet data protocol (PDP) address. The gateway can include a packet data network gateway (PGW) and a gateway general packet radio service support node (GGSN). When the gateway receives an attach request message from the UE with the encoded PCO, the gateway decodes the PCO to extract the framed route and VRF name, associates a tunnel identifier and PDP address with the extracted framed route and VRF name, and installs the framed route in a corresponding VRF.