Pages

Showing posts with label innovation. Show all posts
Showing posts with label innovation. Show all posts

Saturday, August 18, 2012

A new era with ... OpenFlow?

I wanted to write a post about OpenFlow, but it's holidays, and you know... :)

So the OpenFlow protocol is related to the the "Software-Defined Networking" (or SDN). The SDN is the new paradigm where the control plane and the data plane are distinct. The hardware is used to transmit packets and the processing tasks is done on more powerful equipments.

And here comes the OpenFlow protocol. The OpenFlow protocol is the protocol used between the network equipment and the processing equipment (the OpenFlow controller).
http://www.openflow.org/documents/openflow-wp-latest.pdf
So how all of this is supposed to work?
In fact, the network equipment will send all the frames / packets received to the controller for processing through a secure channel. The controller will reply to the network equipment with the output interface on which the packet should be transmit. The equipments will only accomplish switching operation.

What are the advantages?
  • Test of new protocols on the network: the OpenFlow protocol has been designed by academics for research purposes. [1]
  • Manufacturer independent: if the equipment support OpenFlow, it can be used in the network with others OpenFlow enabled equipments
  • Centralized management : all the equipments are connected to the OpenFlow controller.
OpenFlow and the SDN are opening a new era: manufacturers will deliver equipments with high line card and the packet processing will be done at the controller. 

OpenFlow is still under development, but Google has already deployed OpenFlow on its production network [2] [3].
A little video where Urs Hoezle is talking at the Open Networking Summit 2012.


And Cisco is releasing equipments which can support OpenFlow, it's the "Cisco Open Network Environnement".

In this hypothetical Cisco Open Network Environnement, the OpenFlow controller could become a centralized station for all the different services, the Cisco Prime Unified Security Open Orchestrator (or Cisco PUSOO), from this controller: centralization of energy management (we'll suppose that manufacturers will release EMAN WG MIBs), centralization of security policy, centralization of network management and monitoring, all in one. Of course, there is currently no Cisco Prime Unified Secure Open Orchestrator or maybe there is one at the beta version.

Let's imagine a bit further ... in a future, where all network equipments will request to a global controller, and this global controller is running with a AI, it will be Skynet (the famous AI from Terminator).

With OpenFlow, SDN and the cloud, maybe the beginning of the RaaS (Routing as a Service)? 

References
[1] McKeown N., Anderson T. et al. OpenFlow : Enabling Innovation in Campus Networks, March 2008
[3] Merritt R., Google describes its OpenFlow network, EE Times, April 17th 2012

Monday, March 5, 2012

Ecrire un I-D ... qui deviendra peut-être un jour un standard

A l'occasion de l'IETF 83 se déroulant à Paris du 25 au 30 mars, un petit post pour parler des Internet-Drafts. 

Qu'est ce qu'un Internet-Draft (I-D)?
C'est tout simplement un document écrit par une ou plusieurs personnes pour essayer d'améliorer l'Internet. Toute personne peut contribuer à ce travail d'amélioration. Un draft a une durée de vie de 6 mois à partir de sa publication pendant laquelle toute personne peut y apporter une modification (cela peut être une faute de frappe ou une erreur un peu plus technique). Les drafts les plus pertinents ont la chance de finir par devenir une RFC voir même un standard.

Alors comment cela se passe-t-il?
Cela commence par avoir un sujet de discussion en relation avec l'Internet, avec un groupe de travail de l'IETF ou un groupe de recherche de l'IRTF. Chaque I-D doit être formaté suivant un template. Lorsque le draft est prêt, il est soumis à l'IETF. Le draft peut ensuite ... tombé dans l'oubli, devenir une RFC ou donner naissance à un autre draft (changement du numéro de version).

Monday, December 12, 2011