Towards developing a Secure Architecture for the Internet of Everything, I plan to kick off a series of blogs around this pivotal topic.
In discussing security and the Internet of Everything, the first question that comes to mind is, “Which segment of “everything” is one referring to?”. A reasonable approach has been to understand the common attributes that crosses vertical segments such as Intelligent Transportation, Smart Utilities, Industrial Automation and so on. The Internet of Things (IoT) and Machine-to-Machine (M2M) are general abstractions for the network infrastructure that links physical and virtual objects. In Cisco, we now refer to these abstractions as the Internet of Everything, IoE. The IoE describes a world where billions of objects have sensors to detect, measure and assess their status; all connected over public or private networks using standard and proprietary protocols.
Until a point in time around 2008/2009, there were more human beings in the world than devices connected to the Internet. That is no longer the case. Read More »
Tags: analytics, architecture, internet, Internet of Everything, internet of things, IoE, IoT, ip, IPv6, M2M, Service Provider, sms
By Andrew Yourtchenko, Technical Leader, Network Operations Systems Technology Group
As any geek, I find it a lot of fun to get some hands with the new technology – be it a new gadget, new product or a solution.
It’s not very often that I have a chance to play with a whole new protocol. EANTC (European Advanced Network Testing Center) interoperability testing gave me such a chance. The bulk of the work happened on EANTC premises in Germany this past February. The overall activity involved many representatives from various vendors making their devices talk to each other. The goal is to test the protocols in several areas, including MPLS, SDN, and IPv6, but the highlight for me was the testing of MAP (Mapping Address and Port) – a new protocol to enable the sharing of IPv4 addresses by several customer premise devices without keeping the state at the service provider end.
This protocol is being developed by IETF, and has two flavours, the standards-track “MAP” which uses encapsulation to transmit the packets, otherwise known also as MAP, and the experimental track “MAP-T” – which uses the address family translation in order to send packets, instead of the encapsulation. Read More »
Tags: asr 9000, asr9k, ipv4, IPv6, Service Provider
By Steve Simlo, IPv6 Product Manager, Cisco Network Operating Systems Technology Group
As IPv6 gains more and more ground within the Internet we are starting to see recognition amongst the wider community that technologies such as Carrier Grade NAT (CGNAT) have some significant drawbacks from a service and scalability standpoint. Some of the issues were recently highlighted by a major carrier which actually issued a public “opt out” option to their customers if needed.
However, there are some applications such as online gaming, VPN access, FTP service, surveillance cameras, etc., that may not work when broadband service is provided via a CGN. For our customers utilizing these types of applications, we provide the ability to “opt out” of CGN Read More »
Tags: cgv6, Cisco, Internet of Everything, internet of things, IoT, IPv6, map, Service Provider, Steve Simlo, World IPv6 Congress
We first talked about the Mapping of Address and Port (MAP) method to handle IPv4 exhaust and the transition to IPv6 last week. MAP is based on two IETF drafts currently in the process of standardization in draft-ietf-softwire-map (MAP-E) and draft-ietf-softwire-map-t (MAP-T). The real advantage with MAP is that it’s stateless and doesn’t require additional hardware as traffic grows. Read More »
Tags: cgv6, Cisco, DSLite, IPv6, map, MAP-E, MAP-T, Mark Townsley, Service Provider, stateful, stateless
Another year, another CiscoLive. This was the last year in the London venue, and since it was the third time we did it, we had a chance to incorporate learning from the previous two years. As a result, I would say the network was quite a success.
The key element of the design, led by Mark McKillop, was the balance between showcasing the latest technology and maintaining the simplicity of the network. This year we had a mixed L2 + L3 core design. This design helped decrease the impact of various parts on each other. The L2 core was in place for the “special-case” requests, which a routing-based infrastructure could not help with. Read More »
Tags: cisco live, Cisco Live NOC, Cisco Live Orlando, IPv6, l2, L3, Network design