SDN and NFV is the next phase of technology change which will help service provider to launch the services in single click. This is all about the programmability of the networks by using open source software defined network controller.
Thursday, April 5, 2018
BlockChain For Telecommuniations
OpenCT is disrupting the telecommunications industry via its twofold go-to-market approach. The company is positioned to be an innovative and transparent telecommunications provider within the blockchain ecosystem. OpenCT is also building a scalable, high-performance platform that provides the stability and reliability from which transformative blockchain-based applications can be designed to solve industry-specific challenges. The OpenCT platform is based on a hybrid blockchain model, meaning it is both public and private, allowing for a diverse range of adoption, users, and clients. OpenCT's custom-developed mining algorithm is called Proof of Duration (PoD). When used in combination with Proof of Stake (PoS), it grants miners the benefit of a far faster, more democratic, and energy efficient approach. The OpenCT Token (OCT) fuels the interactions of the telecommunications-specific blockchain. OCT acts as a service enabler which clients of the platform can use to unlock and enjoy any service offered over the platform. Most importantly, with the smart technology being used to power the OpenCT platform, the block production rate works at an exceptionally fast rate of 100,000 Transactions Per Second (TPS). In addition to launching the OpenCT platform, the company is also introducing two inaugural applications that work to address significant telco service pain points: Blockchain as a Transport (BaaT): BaaT is a leading network technology that is well-positioned to become the transport service of choice for all businesses because of its highly secure and cost-effective ability to leverage the Internet by breaking down barriers that have limited popular services to a single data center, a single autonomous system, or a single carrier. Blockchain-Defined Wide Area Networks (BD-WAN): BD-WAN will have the unique ability to establish and tear-down logical and physical circuits of any capacity, seamlessly and transparently, thereby enabling real-time billing based solely on bandwidth usage. "Throughout the world, data transmission, digital communication and the transferring of data from point A to point B are key functions and the lifeline that gives most, if not all, businesses and industries the ability to prosper and exist," comments Mayande Walker, Chief Operating Officer of OpenCT. "OpenCT will provide a new process, innovate conveyance and offer an effective solution to those who have challenges with costly connectivity giving the entire telco community an option for secure, peer-to-peer financial transactions without the use of any third party or financial institutions." OpenCT (https://www.openct.io/) is taking blockchain to new heights, ensuring the adoption of this industry disrupting solution is fully supportive of service providers, enterprises and carriers alike.
Click Here To Read Rest Of The Post...
Saturday, February 10, 2018
Routing In Fat Trees Protocol
Data Centers have been steadily growing to commonly host tens of thousands of end points, or more, in a single network. Because of their topologies (traditional and emerging), traffic patterns, need for fast restoration, and for low human intervention, data center networks have a unique set of requirements that is resulting in the design of routing solutions specific to them. Clos and Fat-Tree topologies have gained popularity in data center networks as a result of a trend towards centralized data center network architectures that may deliver computation and storage services. The Routing in Fat Trees (RIFT) protocol addresses the demands of routing in Clos and Fat-Tree networks via a mixture of both link-state and distance-vector techniques colloquially described as 'link-state towards the spine and distance vector towards the leafs'. RIFT uses this hybrid approach to focus on networks with regular topologies with a high degree of connectivity, a defined directionality, and large scale. The RIFT Working Group will work on a standards track specification of a specialized, dynamic routing protocol for Clos and fat-tree network topologies. The protocol will: - deal with automatic construction of fat-tree topologies based on detection of links - minimize the amount of routing state held at each topology level - automatically prune topology distribution exchanges to a sufficient subset of links - support automatic disaggregation of prefixes on link and node failures to prevent black-holing and suboptimal routing - allow traffic steering and re-routing policies - and provide mechanisms to synchronize a limited key-value data-store that can be used after protocol convergence It is important that nodes participating in the protocol should need only very light configuration and should be able to join a network as leaf nodes simply by connecting to the network using default configuration. The protocol must support IPv6 and should also support IPv4. Working Group Details can be found here.
Click Here To Read Rest Of The Post...
Sunday, January 28, 2018
Different IGP Designs To Connect SDN Controller
In the previous post, we have discussed, how does PCEP can be used as south bound protocol to discover the active RSVP LSP in the network. In this post, I will be discussing how we can use any IGP protocol to discovery the existing network topology in the SDN controller. This mechanism is also known as inband. topology discovery by using existing IGP. We have the various types of SDN Controller connectivity design available and need to understand which one is the best of the existing network. Design 1: Single area or Small IGP If you have single area or small IGP design, in that case controller can directly participate in the same domain and discover the existing network topology. The controller connects to the network only to obtain information from it, no data traffic should ever be sent to the controller. Within single area, the TED is the same in all nodes, that’s why we need single connection to the controller. Design 2: IGP Domain With Multiple Areas If you have large IGP domain with multiple areas configured, in that case traffic engineering or TED information is only propagated within single area. However the routing among the areas is taken care by border routers. In this case, we might require multiple links to the controller. In large IGP domain, TED information is only available within area. So if we need to get the entire TED information, we may need to connect the controller with different ABRs. If the controller is connected to multiple paths in the network, special care has to be taken so that controller should not come in the forwarding plane. The main disadvantage of this approach is that, you might require hierarchical PCEP controller because it has to correlate the TED information from different areas. Second disadvantage of this design is that you might require multiple connectivity from different areas or place different controllers near to different areas. Design 3: SDN Controller With GRE Tunnel With the known limitations as per design 2, we can use the GRE tunnels to get rid multiple physical connectivity and extract the TED information. The main advantage of this design is that you need single physical connectivity by creating logical interfaces on the top of it.
Click Here To Read Rest Of The Post...
Subscribe to:
Posts (Atom)