A Common API for Transparent Hybrid Multicast

Group communication services exist in a large variety of flavors and technical implementations at different protocol layers. Multicast data distribution is most efficiently performed on the lowest available layer, but a heterogeneous deployment status of multicast technologies throughout the Internet requires an adaptive service binding at runtime. Today, it is difficult to write an application that runs everywhere and at the same time makes use of the most efficient multicast service available in the network. Facing robustness requirements, developers are frequently forced to use a stable upper-layer protocol provided by the application itself. This document describes a common multicast API that is suitable for transparent communication in underlay and overlay and that grants access to the different flavors of multicast. It proposes an abstract naming scheme that uses multicast URIs, and it discusses mapping mechanisms between different namespaces and distribution technologies. Additionally, this document describes the application of this API for building gateways that interconnect current Multicast Domains throughout the Internet. It reports on an implementation of the programming Interface, including service middleware. This document is a product of the Scalable Adaptive Multicast (SAM) Research Group

IDHOCNET-A Novel Protocol Stack and Architecture for Ad hoc Networks

Presently employed Internet Protocol (IP) stack possesses number of architectural problems. The issues like Dual/Overriding role of IP addresses, mobility, multi-homing etc are the limitations for the infrastructure oriented networks which even have support of Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), Network Address Translation (NAT) servers, etc. Such issues are extremely complex to handle in the case of multi-hop wireless ad hoc networks which lack the support of any infrastructure component. The contemporary research direction for the improvement of present Internet architecture mainly focuses on the use of real identifiers instead of IP addresses for host identification in the network. However, the proposed architectures mostly discuss the infrastructure oriented network models and minimal research has been conducted in the direction of proposals for ad hoc networks.  In this paper we provide a thorough discussion on the practical usage issues of IP based ad hoc network implementation. In order to resolve the present limitations of ad hoc networks, we describe an implementation of a novel identifier based ad hoc network protocol stack and architecture known as IDHOCNET (Identifier based ad hoc network). The architecture proposes a novel paradigm of identifier based applications for multi-hop wireless ad hoc environment. The proposed system further provides backward compatibility to support co-existence with IP based applications. As a proof of concept, the architecture has been implemented on Linux platform with WiFi interfaces. Various practical scenarios with architectural insight are presented to demonstrate the practicability of the proposed approach

Internet Engineering Task Force (IETF) S. Nadas, Ed. Request for Comments: 5798

This memo defines the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It is version three (3) of the protocol, and it is based on VRRP (version 2) for IPv4 that is defined in RFC 3768 and in "Virtual Router Redundancy Protocol for IPv6". VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IPv4 or IPv6 address(es) associated with a virtual router is called the Master, and it forwards packets sent to these IPv4 or IPv6 addresses. VRRP Master routers are configured with virtual IPv4 or IPv6 addresses, and VRRP Backup routers infer the address family of the virtual addresses being carried based on the transport protocol. Within a VRRP router, the virtual routers in each of the IPv4 and IPv6 address families are a domain unto themselves and do not overlap. The election process provides dynamic failover in the forwarding responsibility should the Master become unavailable. For IPv4, the advantage gained from using VRRP is a higher-availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. For IPv6, the advantage gained from using VRRP for IPv6 is a quicker switchover to Backup routers than can be obtained with standard IPv6 Neighbor Discovery mechanisms. Status of This Mem

Internet-wide geo-networking problem statement

This document describes the need of specifying Internet-wide location-aware forwarding protocol solutions that provide packet routing using geographical positions for packet transport

On the Use of Stream Control Transmission Protocol (SCTP) with IPsec

This document describes functional requirements for IPsec (RFC 2401) and Internet Key Exchange (IKE) (RFC 2409) to facilitate their use in securing SCTP (RFC 2960) traffic