We’re excited to announce that CloudFlare has just been named a Google Cloud Platform Technology Partner. So what does this mean? Now, Google Cloud Platform customers can experience the best of both worlds—the power and protection of the CloudFlare community along with the flexibility and scalability of Google’s infrastructure.
We share many mutual customers with Google, and this collaboration makes it even easier for Google Cloud Platform customers to get started with CloudFlare.
When CloudFlare is enabled, Google Cloud Platform customers have their infrastructure extended directly to the network edge, giving them faster content delivery as well as heightened optimization and security.
2x Web Performance Speed - CloudFlare uses advanced caching and the SPDY protocol to double web content transfer speeds, making web content transfer times significantly faster.
Datacenters at Your Customer’s Doorstep - CloudFlare’s global edge network caches static files close to their destination, meaning that content always loads fast no matter where customers are located. Also, CloudFlare peers with Google in strategic locations globally, improving response times for Google Cloud Platform services.
Protection Against DDoS and SQL Injection Attacks - Because CloudFlare sits on the edge, customers are protected from malicious traffic Continue reading
Alcatel-Lucent aims to bring NFV benefits to routing with its Virtual Service Router (VSR), a carrier-grade virtualized IP/MPLS edge router.
Normally for these FFF articles I’ve taken to writing about new protocols as a way of introducing others to it and also edumacating myself about it. For this post I get all nostalgic and look at good old Enhanced Interior Gateway Routing Protocol (EIGRP).
Unlike RIP with its simple hop count or OSPF with its simple bandwidth metric, the EIGRP metric is actually derived by plugging a number of values into a formula and solving the formula. The formula looks like this:
Let’s talk about the k values first. The k values are constants that are configured in IOS and fed into the formula. They have the affect of basically turning on and off the variables that are used in the calculation: bandwidth, delay, load, reliability. They also have the affect of giving more or less emphasis to a variable. For example, setting k3 to 50 would give the “delay” variable more emphasis than if k3 is set to 1. The default settings for the k values are:
This has the net result of simplifying the Continue reading
Pardon me if I go a little bit on the philosophical side of life as a network engineer this week, but we need to have a little talk about freedom. This last week, Ethan wrote a post on his new criteria for network design and architecture. While I agree with the points Ethan makes in his post, there was one thing that put me sideways. In fact, this one thing has always put me sideways to our modern world.
Freedom.
Ethan gives what is a pretty standard (Lockian) definition of the idea when he says, “Freedom is the power or right to act, speak or think as one wants without hindrance or restraint.”
But, harking back to the story of Ishmael and Isaac, we need to remember there is a real difference between freedom from and freedom to. Freedom from constraint might feel like real freedom, but it’s the freedom of the wilderness. Freedom to create might feel like slavery with its self-discipline and bounds, but it’s the freedom to build — to create.
Let’s turn to one of Ethan’s examples here — open standards, and vendors sticking to them, to bring the point to the world of network Continue reading
Startup aims to provide an automator of automators.
I was listening to one of the HP SDN Packet Pushers podcasts in which Greg made an interesting comment along the lines of “people say that OpenFlow doesn’t scale, but what HP does with its IMC is it verifies the amount of TCAM in the switches, checks whether it can install new flows, and throws an alert if it runs out of TCAM.”
Read more ...Quite often RFCs in the “earlier days” discussed not only process but also design. Looking back now, considering the complexity of the network engineering world, these RFCs might seem even a little trite. But these “architectural RFCs” often still carry thoughts and records of experience that are important, even if they aren’t so much followed […]
The post RFCs You Should Know: 5218 appeared first on Packet Pushers Podcast and was written by Russ White.