Free im protocols software for linux

Ethics Search Protocol in short ESP is an XML-based protocol for search engines that is designed to allow people to express specific ethical requirements when performing searches.
Consumers seldom get the chance to communicate ethical requirements because the proper communication channel does not exist. This project has the goal to offer an open source specification and implementation for that missing communication channel.
Enhancements:
- Changes were made to Category, OrganizationSearchParameters, SearchProfile, and Community.
- PolicyReference complements PolicyStatement.
- EvaluationScheme complements VotingScheme.
- The Envelope type was removed.
- The documentation was improved.

STUN Protocol Library provides the Simple Traversal of UDP through NATs Library.
STUN Protocol Library, Client and Server implements a simple STUN (Simple Traversal of UDP through NATs) server and client, using the included library.
The STUN protocol is described in the IETF RFC 3489, available from the IETF.
STUN is a lightweight protocol that allows applications to discover the presence and types of Network Address Translators (NATs) and firewalls between them and the public Internet.
It also provides the ability for applications to determine the public IP addresses allocated to them by the NAT.
STUN works with nearly all existing NATs, and does not require any special behavior from them.
As a result, it allows a wide variety of applications to work through existing NAT infrastructure.
The STUN protocol is very simple, being almost identical to echo.
Enhancements:
- Changed to new terminology.

Generic Protocol Framework aims to allow users to rapidly prototype different emerging communications protocols. Implementations can be easily "dropped in" and tested independant of a finished product. Testing on both the end product, and the protocol itself can be easily accomplished. The tool aims to provide the developer and end user with a robust solution which can track the size of messages, how rapidly they will be generated, and how many of each type can be seen.
Why the GPF:
There are many similar tools available. The problem with many of these tools is that they are 1) closed source, 2) not easily adaptable to a specific implementation (they use custom languages), 3) expensive. The advantages of the GPF are its open source nature, the ease of which it can be adapted, and the cost: free!
Basic Flow:
Modification of the GPF is fairly simple. Tool-opts.h contains the basic options that will be applied to the packet while it is being built. To transmit a packet, the system calls the tx_message() function, and passes the message ID as well as the option block. This is then passed to the custom function: tx_message_custom() in tx.c. From the message id, the system selects an appropriate tx_* function (to be implemented by the user) and passes an unsigned char **, where the buffer will be written, and the option block. In turn, that function will make heavy use of the add_buf_tu*() functions, which will allow the user to add a tubyte8, tuint16, or tuint32 number to the buffer.
In daemonize mode, the basic options are set, and the system then listens for incomming packets. When a packet arrives, the system calls basic_parse() on the packet. This function then calls basic_parse_custom(), found in parse.c. In turn, this can call any appropriate parsing helpers, including the get_tu*() functions, which allow the user to retrieve a tubyte8, tuint16, or tuint32 from the buffer. CAVEAT: if the first two bytes of the buffer are zerod, it will be treated as an END message. However, recovery is available. In the basic_parse_custom() message, you can set the end_signal_caught variable of the option_block to 0. In this case, it will not stop the daemon from running.
Enhancements:
- Currently, TCP support is somewhat experimental.
- Testing for that portion will be ongoing.
- No clear examples are provided.
- The examples/ directory contains the precursors to a MIP example.

Host Identity Protocol on Linux is an implemetation of the Host Identity Protocol (HIP) and the related architecture. Host Identity Protocol (HIP) is a proposal to change the TCP/IP stack to securely support mobility and multi-homing.
Additionally, it provides for enhanced security and privacy and advanced network concepts, such as moving networks and mobile ad hoc networks. HIP is "cool", which means that as a mobile VPN solution, when your network interfaces go up or down, there is no need to re-establish a secure tunnel.
Enhancements:
- The implementation was moved from kernel to user space.
- Support for the Nokia 770 Linux PDA (ARM) was added.

A miniature console based AIM client written in pure Java. It implements the TOC protocol and provides a solid framework for understanding and writing your own IM clients or bots. Project SimpleAIM is an open source development project aimed at providing platform independence and interoperability in the realm of instant messaging services.

This document describes the TOC protocol. The protocol is built on TCP. Framing is done by SFLAP, described at the bottom of this document. Inside each
SFLAP frame is a TOC command.

The TOC protocol is ASCII based, and special attention must be placed argument separation. The separator and the rules of separation are different for messages inbound
to TOC and outbound to the client. The rules of separation are described in sections below.

The TOC server is built mainly to service the TIC and TiK clients. Since the TIC client is a Java applet, and downloadable, TOC will NOT support multiple TOC protocol versions at the same time. Therefore, TiK users will be forced to upgrade if the protocol version changes.
TOC sends down the protocol version it expects the client to speak and understand. Note, the protocol version is a string.

TAHI Test Suite provides a mechanism for validating an IPv6 implementation against a standardized test for conformance to the IPv6 specification, extensions and directly related protocols.
Enhancements:
- Ported FreeBSD-4.x
- Dont support FreeBSD 2.x
- pa can decode MIP6 packets
- All interoperability test tools is included.

Multicast Dissemination Protocol project is a protocol framework and software toolkit for reliable multicasting data objects including files and application memory blocks. A primary design goal of MDP is to provide a reliable multicast protocol approach which is suitable for reliable dissemination of data over both wireless and wired networks.

MDP software has been demonstrated across a range of network architecture and heterogeneous conditions including; the worldwide Internet MBone, bandwidth and routing asymmetric network connections, high delay satellite networks, and mobile, radio networks. MDP integrates numerous multicast protocol advances including highly robust, packet-based erasure correction techniques and adaptive group timing mechanisms.

The present MDP software toolkit includes a library with a well-defined API. Several example working applications including a multicast file transfer applications and a very basic multicast chat application are also provided. To learn more and/or download the software see the following sections.