posted on Apr, 23 2013 @ 04:01 PM
Originally posted by Maxatoria
Most of what google seems to be doing is a 2 level job
i think you are correct, transport layer
1. separate the control of the physical devices from its manufacturers built in control system to the eyes of the people looking after it, so
so you point and you click and the jobs done (should of been do able with SNMP but it never really worked)
it will be much easyer to see the topology of the network and to set policy "on the fly"
2. the physical slinging of data down the pipes is done differently but its no surprise due to the fact that modern links have such low error
rates/latency compared to when most of the protocols were formalized and it being google they can do their own thing since its their network and not
having to spend years arguing with the standards body, but they still have to present it in standard tcp/ip 4/6 format at the gateway
yes it still has to "share" the internet with other users so their protocol must be "compliant" with existing protocols,
and not hog links, the interesting part is the routing instructions can be,
the packet header, or "off the back" of the packet data.
in the interior of the SDN the packets can be routed on content,
on the open internet the packets can be routed by header
having worked on mainframes from the days of 300bps modems theres always been these sort of moments where someone gives the technology a good
kicking into touch and it takes a while but everyone says "hmm...that'll work" and the standards people eventually rubber stamp it
in think you are right, and this is one of those times where the technology is changing in a fundamental way and the changes although not noticable at
the end user level will change the face of IT and Administration and the delivery of services.
internet 2.0, backwards compatible with internet 1.0