Justin Scott Pietsch, Age 42Van Nuys, CA

8331370, Dec 11, 2012

Dec 17, 2009

12/641255

James R. Hamilton - Seattle WA, US
Alan M. Judge - Dublin, IE
David J. McGaugh - Seattle WA, US
Justin O. Pietsch - Bothell WA, US
David J. O'Meara - Dublin, IE

Amazon Technologies, Inc. - Reno NV

H04L 12/28

370392, 370408

A hierarchical distributed routing architecture including at least two levels, or layers, for receiving, processing and forwarding data packets between network components is provided. The core level router components receive an incoming packet from a network component and identify a distribution level router component based on processing a subset of the destination address associated with the received packet. The distribution level router components receive a forwarded packet and forward the packet to a respective network. The mapping, or other assignment, of portions of destination addresses to router components of the distributed routing environment may be managed by a router management component. In some embodiments, mapping of destination address to router components may be based, at least in part, on traffic volumes associated with the mapped destination addresses.

8331371, Dec 11, 2012

Dec 17, 2009

12/641260

Alan M. Judge - Dublin, IE
David J. McGaugh - Seattle WA, US
James R. Hamilton - Seattle WA, US
Justin O. Pietsch - Bothell WA, US
David J. O'Meara - Dublin, IE

Amazon Technologies, Inc. - Reno NV

H04L 12/56
H04L 12/28

370392, 370400, 370408

A hierarchical distributed routing architecture including at least three levels, or layers, for receiving, processing and forwarding data packets between network components is provided. The core level router components receive an incoming packet from a network component and identify a distribution level router component based on processing a subset of the destination address associated with the received packet. The distribution level router components receive a forwarded packet and identify a transit level router component based on at least a subset of the destination address associated with the received packet. The transit level router components receive the forwarded packet and forward the packet to a respective network. The mapping of destination addresses to router components of may be managed by a router management component. In some embodiments, mapping of destination address to router components may be based, at least in part, on traffic volumes associated with the mapped destination addresses.

8406128, Mar 26, 2013

Jun 29, 2010

12/826586

Jagwinder Singh Brar - Bellevue WA, US
Michael David Marr - Monroe WA, US
Tyson J. Lamoreaux - Seattle WA, US
Mark N. Kelly - Dublin, IE
Justin O. Pietsch - Bothell WA, US

Amazon Technologies, Inc. - Reno NV

H04L 1/00

370229, 709235

Efficient and highly-scalable network solutions are provided that each utilize deployment units based on Clos networks, but in an environment such as a data center of Internet Protocol-based network. Each of the deployment units can include multiple stages of devices, where connections between devices are only made between stages and the deployment units are highly connected. In some embodiments, the level of connectivity between two stages can be reduced, providing available connections to add edge switches and additional host connections while keeping the same number of between-tier connections. In some embodiments, where deployment units (or other network groups) can be used at different levels to connect other deployment units, the edges of the deployment units can be fused to reduce the number of devices per host connection.

8495194, Jul 23, 2013

Jun 29, 2010

12/826607

Jagwinder Singh Brar - Bellevue WA, US
Michael David Marr - Monroe WA, US
Tyson J. Lamoreaux - Seattle WA, US
Mark N. Kelly - Dublin, IE
Justin O. Pietsch - Bothell WA, US

Amazon Technologies, Inc. - Reno NV

G06F 15/173
H04L 1/00

709223, 709224, 709225, 709226, 709250, 709251, 709252, 370216, 370396, 370397, 370398, 370399

Efficient and highly-scalable network solutions are provided that each utilize deployment units based on Clos networks, but in an environment such as a data center of Internet Protocol-based network. Each of the deployment units can include multiple stages of devices, where connections between devices are only made between stages and the deployment units are highly connected. In some embodiments, the level of connectivity between two stages can be reduced, providing available connections to add edge switches and additional host connections while keeping the same number of between-tier connections. In some embodiments, where deployment units (or other network groups) can be used at different levels to connect other deployment units, the edges of the deployment units can be fused to reduce the number of devices per host connection.

8554952, Oct 8, 2013

Jun 29, 2010

12/826597

Jagwinder Signh Brar - Bellevue WA, US
Michael David Marr - Monroe WA, US
Tyson J. Lamoreaux - Seattle WA, US
Mark N. Kelly - Dublin, IE
Justin O. Pietsch - Bothell WA, US

Amazon Technologies, Inc. - Reno NV

G06F 15/16
G06F 15/173
H04Q 11/00
H04L 17/00

709250, 709251, 709252, 370250, 370259

Efficient and highly-scalable network solutions are provided that each utilize deployment units based on Clos networks, but in an environment such as a data center of Internet Protocol-based network. Each of the deployment units can include multiple stages of devices, where connections between devices are only made between stages and the deployment units are highly connected. In some embodiments, the level of connectivity between two stages can be reduced, providing available connections to add edge switches and additional host connections while keeping the same number of between-tier connections. In some embodiments, where deployment units (or other network groups) can be used at different levels to connect other deployment units, the edges of the deployment units can be fused to reduce the number of devices per host connection.

2011014, Jun 23, 2011

Dec 17, 2009

12/641280

Alan M. Judge - Dublin, IE
David J. McGaugh - Seattle WA, US
James R. Hamilton - Seattle WA, US
Justin O. Pietsch - Bothell WA, US
David J. O'Meara - Dublin, IE

H04L 12/56

370392

A hierarchical distributed routing architecture including at least three levels, or layers, for receiving, processing and forwarding data packets between network components is provided. The core level router components receive an incoming packet from a network component and identify a distribution level router component based on processing a subset of the destination address associated with the received packet. The distribution level router components that receiving a forwarded packet and identify a transit level router component based a second processing of at least a subset of the destination address associated with the received packet. The distribution level router components maintain address routing information a first and second memory. The transit level router components receive the forwarded packet and forward the packet to a respective network. The mapping, or other assignment, of portions of the FIB associated with the distributed routing environment is managed by a router management component.

2013001, Jan 10, 2013

Sep 14, 2012

13/620281

James R. Hamilton - Seattle WA, US
Alan M. Judge - Dublin, IE
David J. McGaugh - Seattle WA, US
Justin O. Pietsch - Bothell WA, US
David J. O'Meara - Dublin, IE

H04L 12/28

370389

A hierarchical distributed routing architecture including at least two levels, or layers, for receiving, processing and forwarding data packets between network components is provided. The core level router components receive an incoming packet from a network component and identify a distribution level router component based on processing a subset of the destination address associated with the received packet. The distribution level router components receive a forwarded packet and forward the packet to a respective network. The mapping, or other assignment, of portions of the FIB associated with the distributed routing environment is managed by a router management component.

2013001, Jan 10, 2013

Sep 14, 2012

13/620363

Alan M. Judge - Dublin, IE
David J. McGaugh - Seattle WA, US
James R. Hamilton - Seattle WA, US
Justin O. Pietsch - Bothell WA, US
David J. O'Meara - Dublin, IE

H04L 12/56

370392

A hierarchical distributed routing architecture including at least three levels, or layers, for receiving, processing and forwarding data packets between network components is provided. The core level router components receive an incoming packet from a network component and identify a distribution level router component based on processing a subset of the destination address associated with the received packet. The distribution level router components that receiving a forwarded packet and identify a transit level router component based a second processing of at least a subset of the destination address associated with the received packet. The transit level router components receive the forwarded packet and forward the packet to a respective network. The mapping, or other assignment, of portions of the FIB associated with the distributed routing environment is managed by a router management component.