[Editor’s Note: A limited number of student grants are available to help pay for travel, accommodations, and NDSS Symposium registration fees for full-time students attending the 24th annual Network and Distributed System Security (NDSS) Symposium. Watch the NDSS website at https://www.internetsociety.org/events/ndss-symposium for information and deadlines as the process opens for NDSS 2018 in February of next year. The following post is a guest contribution from one 2017 grantee.]
Verizon is taking networking tips from Facebook and Google.
When the inevitable 2AM call happens—”our network is under attack”—what do you do? After running through the OODA loop (1, 2, 3, 4), used communities to distribute the attack as much as possible, mitigated the attack where possible, and now you realist there little you can do locally. What now? You need to wander out on the ‘net and try to figure out how to stop this thing. You could try to use flowspec, but many providers do not like to support flowspec, because it directly impacts the forwarding performance of their edge boxes. Further, flowspec, used in this situation, doesn’t really work to walk the attack back to its source; the provider’s network is still impact by the DDoS attack.
This is where DOTS comes in. There are four components of DOTS, as shown below (taken directly from the relevant draft)—
The best place to start is with the attack target—that’s you, at 6AM, after trying to chase this thing down for a few hours, panicked because the office is about to open, and your network is still down. Within your network there would also be a DOTS client; this would be a small piece of software running Continue reading
The managed SD-WAN service will be available at the end of the second quarter.
Pica8 now supports five 100G white box switches.
The post Worth Reading: A Guide to Private VPN Services appeared first on 'net work.
Google lends expertise to mobile operators; Cisco might split up hardware and software businesses.
I'm grateful to Christian de Larrinaga, from the Internet Society's UK Chapter, for pointing me to a recent publication by the World Bank: "Principles on identification for sustainable development: toward the digital age".
The premise of the report is this: full participation in today's societies and achievement of one's desired potential are increasingly likely to depend on the ability to identify oneself; however, some 1.5 billion people are reckoned to lack "legal identification", and action should be taken to remedy this.
While most people are getting excited about ‘cloud’ there are multi-billion dollar businesses working on upgrading their networks to early-2000’s level technology.
This proposed standard complexifies a carrier network to a whole new level. I understand that some carriers are delivering legacy video over their networks with IPv4 Multicast, but wow, keeping this running and finding high quality software apps won’t be a fun place to work.
This document specifies a solution for the delivery of IPv4 multicast services to IPv4 clients over an IPv6 multicast network. The solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme and uses an IPv6 multicast distribution tree to deliver IPv4 multicast traffic. The solution is particularly useful for the delivery of multicast service offerings to customers serviced by Dual-Stack Lite (DS-Lite).
Some people networks are making money out of this stuff. I can’t imagine how much it costs to support the inherent complexity.
RFC 8114 – Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network, MARCH 2017 – Proposed
The post RFC 8114 IPv4 Multicast over IPv6 Multicast. Ouch. appeared first on EtherealMind.