Re: [Ibnemo] Clearing up some misconceptions, part 2: Technical Scope Questions

[PEDRO ANDRES ARANDA GUTIERREZ <[e-mail]>]

Hi John,

I’m working with your emails, since they provide a lot of very valuable guidance. Let me try to answer one of the simple questions.

We are still seeing service request times of days (look at the recent talks at TCN’15) and we are expected to make them go drastically down.
Looking at how things are evolving in networking in general, I sincerely think that if we want things to get better, network admins have to start leaving the expect/TCL turf. We all know that maintaining these scripts is a pain and that’s why some of us are looking somewhere else.
And that’s where SDN kicks in.
(OK, yes, some people say scripts are software, but c’on … Script Driven Networking is like using assembler. I did a lot of that in the Z80 and 8088 times.)

I as a network admin would like to get some level of abstraction. For example, I would like to say ‘router’ as a collection of well-known building blocks and with a well-defined behaviour. Whether it ends up being a Cisco, a Juniper or a you name it should not be my concern. The typical network admin sitting in the NOC doesn’t have to be impacted by a deal done somewhere up in the management floors to get routers cheaper.

Same goes for other types of nodes and something similar also holds for links. I don’t want to be bothered by the specifics of programming a link, but I want to be aware of its presence. And here, again, supplier independence,etc.

And since we are already here, why not having design patterns? Who always starts from scratch when designing networks and then proceeds on a node-by-node basis? Doesn’t it make sense to replicate blocks you trust to work for a specific purpose?

This is why I find this IBNEMO stuff valuable. Yes, we need some focusing and shaping here and there, and there is where your valuable comments kick in.


Best, /PA

---
Dr. Pedro A. Aranda Gutiérrez

Technology Exploration -
Network Innovation & Virtualisation
email: pedroa d0t aranda At telefonica d0t com
Telefónica, Investigación y Desarrollo
C/ D. Ramón de la Cruz,84
28006 Madrid, Spain

Fragen sind nicht da, um beantwortet zu werden.
Fragen sind da, um gestellt zu werden.
Georg Kreisler
De: John Strassner <[e-mail]<mailto:[e-mail]>>
Fecha: sábado, 20 de junio de 2015 23:15
Para: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Asunto: [Ibnemo] Clearing up some misconceptions, part 2: Technical Scope Questions

Hi all,
…
  - Why would a network administrator use an intent-based system?
    They live in the world of CLI, YANG, expect and TCL scripts.
…
--
regards,
John





________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição