Juniper Networks, Inc.

Magic Leap, Inc.

Arista Networks, Inc.

Nitin Singh

Manoj Sharma

Adrian Kaehler

Kapil Arora

Ryan Bickhart

Hassan C Hosseini

Poorna Pushkala Balasubramanian

Wen Lin

Vikram Nagarajan

Amit Dattatray Ranpise

Sunil Kumar Malali

Xiaomin Wu

John E Drake

Alton Lo

Rajesh Kumar Semwal

Kaliraj Vairavakkalai

Santosh Pallagatti Kotrabasappa

Madhu Sudan

Ramesh Kandula

Anshu Verma

Prasantha Kumar Gudipati

Sudha Madhavi Yeevani

This disclosure describes techniques for device authentication and/or pairing. A display system can comprise a head mountable display, computer memory, and processor(s). In response to receiving a request to authenticate a connection between the display system and a companion device (e.g., controller or other computer device), first data may be determined, the first data based at least partly on audio data spoken by a user. The first data may be sent to an authentication device configured to compare the first data to second data received from the companion device, the second data based at least partly on the audio data. Based at least partly on a correspondence between the first and second data, the authentication device can send a confirmation to the display system to permit communication between the display system and companion device.

Pairing with companion device

Disclosed herein are systems and methods for device authentication or pairing. In an aspect, a wearable display system comprises a display, an image capture device configured to capture images of a companion device, a computer-readable storage medium configured to store the images of the companion device, and a processor in communication with the image capture device and the storage medium. The processor can be programmed with executable instructions to receive a first image of a first optical pattern displayed by the companion device captured by the image capture device, wherein the first optical pattern is generated by the companion device based on first shared data, extract first data from the first optical pattern in the received first image, authenticate the companion device based on the first data extracted from the first optical pattern, and notify a user of the wearable display system that the companion device is authenticated.

Network identifiers are extracted from route advertisements. A table associates virtual network identifiers with provider edge devices. When a virtual network identifier extracted from a route advertisement matches a virtual network identifier in the table, the route advertisement is propagated to the provider edge devices associated with that virtual network identifier in the table. The route advertisement is not propagated to provider edge devices not associated with that virtual network identifier in the table.

Filtering advertising of route advertisements based on virtual network identifiers

Techniques for implementing neighbor equivalence groups on a network device are provided, where a neighbor equivalence group is a group of peers of the network device that communicate identical control plane state information for a given network protocol to the network device. In the context of Border Gateway Protocol (BGP), these techniques can include (1) creating, by the network device, a neighbor equivalence group for a set of BGP peers that advertise the same BGP paths to the device, (2) maintaining, by the network device, a single path database for the neighbor equivalence group (rather than one path database for each BGP peer in the group), and (3) immediately processing by the network device, BGP path update/withdrawal messages received from any of the BGP peers in the group against the single path database, without waiting for the same message to be received from every peer.

Neighbor equivalence groups

A provider edge device, capable of accessing a first type of memory and a second type of memory, may determine a network address associated with a customer edge device. The provider edge device may determine whether the customer edge device is categorized as a leaf device in an Ethernet Tree service provided by the provider edge device. The provider edge device may selectively store the network address in the first type of memory or the second type of memory based on determining whether the customer edge device is categorized as a leaf device in the Ethernet Tree service.

Conserving memory resources of a provider edge device in an ethernet tree

A first device may receive network traffic including a first label. The first label may be an inclusive multicast label associated with a second device. The second device may be a designated forwarder for an Ethernet segment. The first device may determine a second label based on receiving the network traffic including the first label. The second label may be used to route the network traffic to a customer edge device, via a third device, rather than the second device. The third device may be a non-designated forwarder for the Ethernet segment. The first device may provide the network traffic, including the second label, to the third device to permit the third device to provide, via the Ethernet segment, the network traffic to the customer edge device based on the second label when a failure occurs in association with the second device.

Egress node protection for broadcast, unknown unicast, or multicast traffic in EVPN topologies

A device may receive, from a first device associated with a first LAN, network traffic destined for a second LAN. The device may provide the first LAN with access to a core network. The device may not provide the second LAN with access to the core network. The device may identify, based on the network traffic, a Layer 3 address associated with a second device. The second device may be associated with the second LAN. The device may determine that the first device is categorized as a leaf device within an Ethernet Tree provided by the device. The device may determine, based on the Layer 3 address, that the second device is categorized as a leaf device within the Ethernet Tree. The device may drop the network traffic based on determining that the first device and the second device are categorized as leaf devices within the Ethernet Tree.

Processing inter-VLAN traffic in an ethernet tree

The disclosed method may include (1) identifying a customer edge router that is multi-homed to a provider edge router and another provider edge router, (2) determining, by the provider edge router, that the other provider edge router has identified an Internet Protocol address of the customer edge router by way of an Address Resolution Protocol, (3) learning, by the provider edge router, the Internet Protocol address of the customer edge router from the other provider edge router, and then (4) advertising, by the provider edge router to at least one gateway of at least one other customer edge router, a route that facilitates communication with the customer edge router via the provider edge router based at least in part on the Internet Protocol address of the customer edge router. Various other methods, systems, and apparatuses are also disclosed.

Apparatus, system, and method for achieving redundancy and load-balancing across communication layers within networks

A network device is configured to provide, via an Ethernet segment with a customer network, active-active multi-homing L2 virtual bridge connectivity to the customer network using an EVPN instance (EVI) and L3 routing using an IRB interface that is a L3 routing interface assigned to the EVI; to receive, from a peer PE device of the EVPN instance, an EVPN route comprising an L2-L3 binding for a customer device of the customer network and associating the L2-L3 binding with the Ethernet segment, the L2-L3 binding comprising an L2 and an L3 address assigned to the customer device, wherein the peer PE device provides, with the network device and via the Ethernet segment, active-active multi-homing L2 virtual bridge connectivity to the customer network; and to forward, via the Ethernet segment and based at least on the L2-L3 binding received from the peer PE device, an L3 packet to the customer device.

Layer 3 convergence for EVPN link failure

The disclosed apparatus may include (1) a database that maintains a pruned multicast distribution tree and (2) a processing unit having access to the database, wherein the processing unit (A) receives at least one type 3 Ethernet Segment Identifier (ESI) message from at least one other bridge domain on at least one other computing device, (B) determines, based at least in part on the type 3 ESI message, whether the other bridge domain on the other computing device has a root access concentrator, and then (C) populates, in response to determining whether the other bridge domain has a root access concentrator, the pruned multicast distribution tree to account for the other bridge domain such that the bridge domain on the computing device is able to determine whether to send multicast traffic to the other bridge domain. Various other apparatuses, systems, and methods are also disclosed.

Apparatus, system, and method for preventing multicast traffic drops at egress routers in E-Tree topologies

In general, techniques are provided for described herein that extend existing Ethernet Virtual Private Network (EVPN) protocol signaling mechanisms so that local, multi-homing PEs couple to an Ethernet segment can definitively convey their primary/backup designated forwarder (DF) status to any remote PE of the EVPN. In one example, this is accomplished by utilizing a new extended community attribute to each Ethernet A-D per EVI route advertised by each of the multi-homing PEs to specifically carry the advertising PE's primary or backup status. As such, any receiving remote PE need not rely on the arrival of individual MAC routes from a new primary PE and withdrawal of MAC routes from a former primary PE to update its forwarding information.

Update of MAC routes in EVPN single-active topology

In general, techniques of this disclosure may enable a remote provider edge (PE) router to improve convergence time in response to a link failure in an Ethernet Virtual Private Network (EVPN) by establishing per-Ethernet Segment Identifier (ESI) Bidirectional Forwarding Detection (BFD) sessions with other PE routers that are coupled to the PE router in an EVPN. The remote PE may determine that at least two PE routers with the remote PE are locally connected to a multi-homed customer network by a particular Ethernet Segment. The remote PE may send, based on determining that the at least two PE routers are connected to the multi-homed customer network by the particular Ethernet Segment, an ESI Ping request packet through the intermediate network to one of the at least two PE routers, wherein the ESI Ping request packet includes at least a BFD discriminator and an ESI for the particular Ethernet Segment.

Growing community of inventors

Fremont, CA, United States of America

Nitin Singh