Software-Defined Networking (SDN) Definition

What is SDN?

The physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices.

---

Software-Defined Networking (SDN) is an emerging architecture that is dynamic, manageable, cost-effective, and adaptable, making it ideal for the high-bandwidth, dynamic nature of today's applications. This architecture decouples the network control and forwarding functions enabling the network control to become directly programmable and the underlying infrastructure to be abstracted for applications and network services. The OpenFlow™ protocol is a foundational element for building SDN solutions. The SDN architecture is:

• Directly programmable: Network control is directly programmable because it is decoupled from forwarding functions.
• Agile: Abstracting control from forwarding lets administrators dynamically adjust network-wide traffic flow to meet changing needs.
• Centrally managed: Network intelligence is (logically) centralized in software-based SDN controllers that maintain a global view of the network, which appears to applications and policy engines as a single, logical switch.
• Programmatically configured: SDN lets network managers configure, manage, secure, and optimize network resources very quickly via dynamic, automated SDN programs, which they can write themselves because the programs do not depend on proprietary software.
• Open standards-based and vendor-neutral: When implemented through open standards, SDN simplifies network design and operation because instructions are provided by SDN controllers instead of multiple, vendor-specific devices and protocols.

Source:Internet

Read more...

WebTRC-Next big opportunity for Mobile Operators

WebRTC (Web Real-Time Communication) is an API definition being drafted by the World Wide Web Consortium (W3C) to enable browser to browser applications for voice calling, video chat and P2P file sharing without plugins.

A project known as WebRTC, for browser based realtime communication, was open sourced by Google.This has been followed by on going work to standardise the relevant protocols in the IETF and browser APIs in the W3C.
The W3C draft of WebRTC is a work in progress with advanced implementations in the Chrome and Firefox browsers. The API is based on preliminary work done in the WHATWG. It was referred as the ConnectionPeer API, and a pre standards concept implementation was created at Ericsson Labs). The Web Real-Time Communications Working Group expects this specification to evolve significantly based on:

• The outcomes of ongoing exchanges in the companion RTCWEB group at IETF to define the set of protocols that, together with this document, will enable real-time communications in Web browsers.
• Privacy issues that arise when exposing local capabilities and local streams.
• Technical discussions within the group, on implementing data channels in particular.
• Experience gained through early experimentations.
• Feedback received from other groups and individuals.

Read more...