Active Network papers (2002)

Dmitri Kondratiev d_kondr@yahoo.com

CAOS ANET - CAOS Active Network Architecture.
anet.pdf
Abstract: This paper describes ANET - active network architecture for active network router, that includes both traditional router OS components such as routing and packet management subsystems as well as active network platform - ANET.

CVM Channel. Software Design Specification.
cvm-channel.pdf
Abstract: Packet flow is the set of the packets incoming to or outgoing from the network node selected in accordance to some condition. Channel abstraction defines the processing function performed on the packet flow. This document describes the channel architecture and channel API.

ARM - Active Reliable Multicast
arm.pdf
Abstract: Design overview of the ARM - Active Reliable Multicast family of transport protocols that use IP Multicast to provide reliable one-to-many or many-to-many data delivery. ARM goal is to provide reliable data delivery in terms of the variety of application service requirements. Paper describes some of the mechanisms that existing reliable multicast transports use, with a focus on their strengths and weaknesses. ARM protocol requirements emphasise the need for a family of reliable multicast transport protocols instead of a single one suitable for all applications.

ARM Transport - Active Reliable Multicast Transport Protocol
armtp.pdf
Abstract: Design overview of the ARM - Active Reliable Multicast Transport protocol. ARM uses IP Multicast to reliably deliver bulk data to a group of recivers engaged in one-to-many or many-to-many session. ARM design to some extent follows the one of NACK-Oriented Reliable Multicast Protocol (NORM) and also borrows some ideas from StarBurst Multicast File Transfer Protocol (MFTP). In essence ARM Transport is a simplified version of NORM protocol enchansed with similar to MFTP mechanism used for session anouncement and data transfer in separate multicast groups.

ARM Session
arm-session.pdf
Abstract:This document describes ARM Session protocol, its implementation with ARM Session Manager, its role in CVM (Cambira Virtual Machine) as well as inter operation with other components. ARM Session is a session management protocol that provides extension facilities for AA to fine-tune session parameters.

ARM Session Recovery and Load Balancing
arm-recover.pdf
Abstract: This document describes different cases of multicast session recovery and load balancing in Active Network (AN) running Active Reliable Multicast family of protocols (ARM).

Pilot ARM Session Recovery Design
arm-recover-pilot.pdf
Abstract: Pilot design of ARM Session Recovery in Active Network (AN) running Active Reliable Multicast family of protocols (ARM). The design is 'pilot' as it provides limited, partial solution to ARM session recovery. Design is limited because of several important requirements and interdependencies are remaining unclear or not fully specified at the time of writing this document.

ARM File - Active Reliable Multicast File Protocol
armfile.pdf
Abstract: Design overview of the ARM File - Active Reliable Multicast File transfer protocol. ARM File uses IP Multicast to reliably deliver a set of files to a group of recivers engaged in one-to-many or many-to-many session.

RTP-AA Functional Specification
rtpaa.pdf
Abstract: Functional requirements for RTP-AA subsystem. RTP-AA is a set of active applications that ensure video / audio streaming by multi-casting RTP packets on Internet.

Smart Messages
sm.pdf
Abstract: Smart Messages (SM) - messaging framework built with standard QNX Neutrino messages with the goal to provide optimized for efficiency data transfer both for local and distributed communications. Other goals that SM framework address are attribute-based messaging, blackboard and asynchronous communication, message 'store and forward' mechanisms. SM uses powerful QNX messaging to argument traditional shared memory and other IPC and provide user with efficient and flexible synchronization and data communication mechanism to be used in uniform way no matter where communicating end-points exist: in separate threads of a single process, in different processes running on the same node, or in different threads running on different nodes on the net.