It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Some features of ATS will be disabled while you continue to use an ad-blocker.
Originally posted by kwakakev
reply to post by verschickter
The .NET structure has become a rally point for the Microsoft branch, so how does this fit with SDN Exploder? HTML 5 is a clear future rally point, so how does SDN relate to this?
So how is IP addressing handled? I would expect it is IP4 and IP6 compliant. Are there white, grey and black lists supported from certain IP domains or is this all in the box? No developer concerns or awareness about IP traffic?
Sounds like some programmer overheads / abstractions that need to be performed, any specifics?
This is one of the hard edges at the divide. The ability to restrict permissions is a huge plus. The structured function also provides a clear separation of powers. Ok, a hacker may be able to implement what can be done through the website, but they cannot do a table delete or basic reformat if database permissions where exposed.
My flash video player is busted at the moment, bandwidth issues prevent me for implementing a fix. I have heard of REST before, can you describe it?
The controller exposes open northbound APIs which are used by applications. OpenDaylight supports the OSGi framework and bidirectional REST for the northbound API. The OSGi framework is used for applications that will run in the same address space as the controller while the REST (web based) API is used for applications that do not run in the same address space (or even necessarily on the same machine) as the controller. The business logic and algorithms reside in the applications. These applications use the controller to gather network intelligence, run algorithms to perform analytics, and then use the controller to orchestrate the new rules, if any, throughout the network.
The controller platform itself contains a collection of dynamically pluggable modules to perform needed network tasks. There are a series of base network services for such tasks as understanding what devices are contained within the network and the capabilities of each, statistics gathering, etc. In addition, platform oriented services and other extensions can also be inserted into the controller platform for enhanced SDN functionality.
Open SDN Architectures represent a fundamental change in networking architectures. An Open SDN introduces centralized software controllers that implement a common data plane abstraction that unifies the entire network fabric southbound, and publishes open APIs for software applications northbound. With this open architecture, a fabric of multi-vendor devices can be aggregated into a single policy domain that can be programmed and automated using standard software (not CLI). Open SDN Architectures leverage an industry standard data plane abstraction protocol, like OpenFlow, which provide direct access to the data plane hardware and forwarding flow tables – not just a CLI proxy mechanism. And, OpenFlow can operate across a variety of physical and virtual switches, as well as vendor architectures. As a result, for the first time in history, an Open SDN controller can program and automate a multi-vendor network using standard software protocols, like OpenFlow and RESTful APIs.
Nah not 100% correct. It does not speed up the delivery it just makes sure that all the bits, that frame the packet, are delivered or can be reconstructed so you don´t need to resend the whole chunk.
If you think about it, chopping data into packets is already doing a job, because corrupted packets can be resend, not the whole file or whatever you try to send. In truth, loss avoidance algorithms will make the data you have to send more bulky, thus you get longer transfer rates per chunk itself. While short transfer rates are critical to high FPS games, you may get lag free (as in smooth) playing experience but will add an offset to everything.
I opted out from telecoms loss avoidance system. years ago when I was customer to telekom (germany) it cost me a few euros a month to have this technology shut off on my line. Made me a stable 15ms latency on most servers in Germany, where as I had 45ms or more before. This was/is called fastpath.
Funny, you have to pay to make sure you don´t get a service.
You only gain end-to-end speed increase if the time needed to compute, add, send, receive and decipher the validation bits is shorter then to send the whole packet again. Of course, there is always some kind of correction system working in the back.
I would know a nice example about GSM protocols that would clearly show how this affects bandwidth (or packet window size) but increases quality but my post is already lengthy and a little bit OT.
The Googles of the world (i.e Google, universities, and a tiny set of other companies) will use this technology to improve service and lower prices.
Everybody else (the Comcasts, Time-Warners, ad networks, Verizons, etc) will use this technology to enable fine-grained anti competitive behavior (slowing down Netflix because it competes with their own more expensive cable---this is the "dynamic allocation of bandwidth" at work), intrusive advertisement (add/replace ads on websites) and espionage.
The Chinese will take the software without paying and build it into Huawei routers (and use it for international corporate and government espionage, and improving internal censorship capabilities).
It democratizes the previously expensive technology necessary to make the internet anti-democratic.
The .NET structure has become a rally point for the Microsoft branch, so how does this fit with SDN Exploder?
At the moment is it sounding like IP v6.5 with the network layer focus while those on the server development branch are left to twiddle their thumbs.
I know the actual system and integration is not this simple. HTML 5 is a clear future rally point, so how does SDN relate to this?
When it comes to database integration with PHP I choose the abstract layer of PDO. I know mySql plus does have some efficiencies and optimizations, but as a programmer I do not want to be hindered by the storage level and want to remain agile enough through a constantly evolving and dynamic situation. The .NET framework does have quite a massive branch of functions and programming translations. The No Sql branch also looks to be making some ground with the distributed information arena.
I know this stuff ain't simple exploder, just putting up a few flags to watch on your journey. Any information will be considered.
I think the issue we are having is a generic complexity of the software development landscape and in particular the online capabilities
Originally posted by Aleister
Bumping so more people can see and comment on this tech. Thanks for the thread and the continuing data.
Originally posted by Taupin Desciple
reply to post by XPLodER
Do you anticipate a spike in new .coms..... .nets...... etc. because of this streamlining?
Seems like this change makes things more user friendly on all levels. From the random user, to site owners, to hosts......... And because of the lower costs that SHOULD trickle down from the top, people should have an easier time financially getting a site going?
Make sense? Or is that wishful thinking on my part?
Originally posted by Taupin Desciple
reply to post by XPLodER
Sounds good. Thank you.
This thread has been a wealth of information.
Originally posted by TiM3LoRd
faster porn and no lag in games is what 90% of the people on here will read this news as meaning.
I have absolutely NO idea about networking. It blows my mind that there is an actual language to speak to computers. Wish I was smart enough to learn it but alas I am terrible at new languages.
Thanks for the heads up new tech is always something I smile about.
Originally posted by XPLodER
in a very unexpected announcement, Google has announced it moved the worlds largest network onto open flow,
this news was missed by many because of the tragedy of Boston.
in an announcement that went largely missed by the general population Google has announced that it altered its WAN network to work on Open Flow, a new Software Defined Networking standard (SDN)
In April 2012, Google's Urs Hölzle described how the company's Internal Network had been completely re-designed over the previous two years to run under OpenFlow with substantial efficiency improvement