Google Ventures re-ups for CoreOS's Series B.
This is the second and final part of the Back to Basics: Cooling – Part 1 article. Here we will cover: Relative Humidity Calculating Cooling Capacity Converting Between Units For handy references and info, download my Power & Cooling Cheat Sheet to the right Approx Reading Time: 10-15 Minutes Relative Humidity The datacenter may seem […]
The post Back to Basics: Cooling – Part 2 appeared first on Packet Pushers.
This is the second and final part of the Back to Basics: Cooling – Part 1 article. Here we will cover: Relative Humidity Calculating Cooling Capacity Converting Between Units For handy references and info, download my Power & Cooling Cheat Sheet to the right Approx Reading Time: 10-15 Minutes Relative Humidity The datacenter may seem […]
The post Back to Basics: Cooling – Part 2 appeared first on Packet Pushers.

The post Worth Reading: On the Quants and the Creatives appeared first on 'net work.

The next proposed (and actually already partially operational) system on our list is the Router Public Key Infrastructure (RPKI) system, which is described in RFC7115 (and a host of additional drafts and RFCs). The RPKI systems is focused on solving a single solution: validating that the originating AS is authorized to originate a particular prefix. An example will be helpful; we’ll use the network below.

(this is a graphic pulled from a presentation, rather than one of my usual line drawings)
Assume, for a moment, that AS65002 and AS65003 both advertise the same route, 2001:db8:0:1::/64, towards AS65000. How can the receiver determine if both of these two advertisers can actually reach the destination, or only one can? And, if only one can, how can AS65000 determine which one is the “real thing?” This is where the RPKI system comes into play. A very simplified version of the process looks something like this (assuming AS650002 is the true owner of 2001:db8:0:1::/64):
Jim Metzler recaps Martin Casado's Interop keynote and reflects on the VC's predictions.
How does a network engineer deal with divestiture--that is, getting rid of some part of your company's business? On today's Weekly Show, Jeremy Filliben shares his lessons learned in separating networking one from another is. Jeremy is a network engineer for a Fortune 500 insurance company.
The post Show 287: Handling Business Divestitures appeared first on Packet Pushers.
How does a network engineer deal with divestiture--that is, getting rid of some part of your company's business? On today's Weekly Show, Jeremy Filliben shares his lessons learned in separating networking one from another is. Jeremy is a network engineer for a Fortune 500 insurance company.
The post Show 287: Handling Business Divestitures appeared first on Packet Pushers.