A Transport Layer and Socket API for (h)ICN: Design, Implementation and Performance Analysis

"Applying IPv6 to LTE Networks" by Deoknyong Ko. A presentation given at the APNIC 40 Internet Mobility Nexus session on Tue 8 Sep 2015.

This document discusses a bandwidth-driven flow allocation policy for RINA that aims to guarantee bandwidth for flows during their lifetime and prevent network congestion. It proposes utilizing existing flow request and routing information to extend the routing graph with capacity details. A logically centralized but fault-tolerant approach is described that uses Raft consensus to intercept flow allocations and reserve bandwidth along viable paths. Congestion prevention is achieved by assuming each flow will use its requested bandwidth and rejecting requests that cannot be satisfied.

This document discusses congestion control in recursive network architectures like the Recursive Inter-Network Architecture (RINA). It describes how RINA uses a layered, recursive stack approach compared to the layered Internet architecture. It also discusses types of network congestion that can be addressed, including through end system adaptation of traffic sources adjusting their send rates. The document outlines ongoing research into developing stable, scalable new types of congestion control for recursive networks, including approaches inspired by logistic growth models in nature.

This document summarizes an SDN and cloud computing presentation given by Affan Basalamah and Dr.-Ing. Eueung Mulyana from Institut Teknologi Bandung. It discusses SDN and cloud computing research activities at ITB, including implementing OpenFlow networks, developing SDN courses, and student projects involving OpenFlow, OpenStack, and IPsec VPNs. It also describes forming an SDN research group at ITB to facilitate collaboration between academia, network operators, and vendors on SDN topics.

This document summarizes an approach called RINA (Recursive InterNetwork Architecture) for simplifying multi-layer network management. RINA proposes a common, repeating structure across layers with only two protocols - one for data transfer and one for layer management. This significantly reduces the complexity of management models compared to the IP protocol suite, which has unique protocols at each layer. A case study shows how RINA could simplify network management in a large-scale data center network by reducing the number of required addresses, forwarding entities, and management protocols. The consistent structure of RINA opens the door to increased network automation by making management models simpler and more standardized.

More details on implementing broadcast/multicast messaging in IoT networking running Haystack + DASH7 networking software. Also implementing CBOR to enable queries over MQTT.

gogo6 IPv6 Video Series. Event, presentation and speaker details below: EVENT gogoNET LIVE! 4: IPv6 & The Internet of Things. http://gogonetlive.com November 12 – 14, 201, Silicon Valley, California Agenda: http://gogonetlive.com/gogonetlive4-agenda.asp PRESENTATION IoT Field Area Network Solutions & Integration of IPv6 Standards Abstract: http://www.gogo6.com/profiles/blogs/my-presentation-at-gogolive-integration-of-ipv4-and-non-ip Presentation video: http://www.gogo6.com/video/iot-field-area-network-solutions-integration-of-ipv6-standards-by Interview video: http://www.gogo6.com/video/interview-with-carsten-bormann-at-gogonet-live-4-ipv6-iot-confere SPEAKER Patrick Grossetete - Technical Marketing Engineer (IoT), Cisco Bio/Profile: http://www.gogo6.com/profile/PatrickGrossetete MORE Learn more about IPv6 on the gogoNET social network and our online training courses http://www.gogo6.com/main Get free IPv6 connectivity with Freenet6 http://www.gogo6.com/Freenet6 Subscribe to the gogo6 IPv6 Channel on YouTube http://www.youtube.com/subscription_center?add_user=gogo6videos Follow gogo6 on Twitter http://twitter.com/gogo6inc Like gogo6 on Facebook http://www.facebook.com/pages/IPv6-products-community-and-services-gogo6/161626696777

Error and Flow Control Protocol (EFCP) Design and Implementation: A Data Transfer Protocol for the Recursive Internet Architecture

This document provides an overview of IRATI, an open source implementation of RINA for Linux/OS. It discusses the goals of being tightly integrated with the OS, supporting existing applications, and experimentation. The high-level design uses a Linux kernel with user-space daemons. Implementation status provides details on various IPCP components and policies. Experimental activities describe designing RINA networks and interoperating with legacy technologies. Open source initiatives discuss the IRATI GitHub organization and planned contributions from projects like PRISTINE and IRINA.

This talk discusses RINA a bit more in-depth, taking the audience through several use cases and discussing results showcasing RINA benefits published in a number of conferences and journals. The talk includes a demo of application discovery and distributed mobility management in RINA networks.

Krzysztof Mazepa (Cisco Systems Poland) – architekt sieci / konsultant pracujący z najwiekszymi polskimi operatorami przewodowymi i kablowymi. Jego misją jest „tłumaczenie” wymogów businessowych klientów na oferowane rozwiązania technologiczne. Jego duże doświadczenie, 16 lat pracy w środowisku operatorskim, pozwala mu dostrzeć specyficzne wymagania tego rynku i zaproponować oczekiwane rozwiązanie. Krzysztof jest częstym prelegentem na konferencjach PLNOG (Polish Network Operator Group), Cisco Forum, EURONOG (European Network Operator’s Group) oraz Cisco Live. Posiada certyfikaty CCIE (Cisco Certified Internetwork Expert) #18 662, JNCIE (Juniper Networks Certified Internet Expert) #137, VMware Certified Professional 4 #99432 i wiele innych. Krzysztof jest mieszkańcem Warszawy, w wolnym czasie ćwiczy biegi długodystansowe oraz gra w tenisa. Temat prezentacji: BGP FlowSpec Język prezentacji: Polski Abstrakt: Celem sesji jest pokazanie podstaw działania BGP FlowSpec. Przedstawione zostaną podstawy teoretyczne oraz sposób wykorzystania przez operatorów SP do eliminowania ataków DDoS. Działanie rozwiązania zostanie zaprezentowane w wirtualnym środowisku korzystając z oprogramowania IOS XRv.

This document summarizes a research paper that evaluates the impact of transitioning from IPv4 to IPv6 using tunneling with MPLS on voice over IP (VOIP) performance. It first provides background on the need to transition from IPv4 to IPv6 due to limited IPv4 address space. It then discusses different transition mechanisms like tunneling and their benefits. The paper reviews previous studies that found 6-to-4 tunneling provides VOIP performance similar to IPv6. It also discusses how MPLS can ensure quality of service for real-time applications like VOIP. The goal of the research was to analyze how tunneling from IPv4 to IPv6 with MPLS impacts VOIP performance metrics.

1) The ARCFIRE project is experimentally validating the benefits of RINA technology through large-scale experiments on the FIRE+ testbed involving over 100 nodes across multiple distributed information fields (DIFs). 2) In RINA, application names uniquely identify applications, addresses are location-dependent synonyms used for locating applications within a DIF, and other identifiers like port-ids and connection endpoint IDs are used to identify communication endpoints. 3) RINA's naming and addressing model simplifies multi-homing and mobility by assigning addresses to nodes instead of interfaces, avoiding the need for special protocols and allowing mobility to be treated as dynamic multi-homing with expected failures.

Migration from IPv4 to IPv6 is still visibly slow, mainly because of the inherent cost involved in the implementation, hardware and software acquisition. However, there are many values IPv6 can bring to the IP enabled environment as compared to IPv4, particularly for Voice Over Internet Protocol (VoIP) solutions. Many companies are drifting away from circuit based switching such as PSTN to packet based switching (VoIP) for collaboration. There are several factors determining the effective utilization and quality of VoIP solutions. These include the choice of codec, echo control, packet loss, delay, delay variation (jitter), and the network topology. The network is basically the environment in which VoIP is deployed. State of art network design for VoIP technologies requires impeccable Interior Gateway routing protocols that will reduce the convergence time of the network, in the event of a link failure. Choice of CODEC is also a main factor. Since most research work in this area did not consider a particular CODEC as a factor in determining performance, this paper will compare the behaviour of RIP and OSPF in IPv4 and IPv6 using G.711 CODEC with riverbed modeller17.5.

PRISTINE slides presented at the Network Virtualization pre-FIA workshop in Athens, during the Future Internet Assembly conference 2014.