
solution: The nodes of an active network have the
features of flexibility and abstraction regarding their
behavior as elements of a communication network.
This necessity from adaptability to its environment
turns active nodes in a highly programmable element
since its behavior is susceptible to be modified
voluntarily; and abstraction, since the processes or
services are not known a priori will render to the
network to which it belongs.
On the other hand the forms to conceive the business
planes are directly related to the semantics of the
application in particular, which makes difficult to
elaborate a common technology for all casuistry.
The adaptation of the solution to the particular
semantics in each case, although viable, is not
optimal. Thanks to it the active networks can support
the implantation of solutions that have into account
not only the syntax of the logic of businesses, but
also their semantics on the own network, providing
different strategies and new and powerful designs.
1.3 Routing in active nodes
Active nodes are network devices that are able to
process packets of data crossing them. This capacity
of processing is dynamic, in such a form that the
incoming traffic can contain the code that the node
has to execute for a certain subgroup of packets that
it handles.
A very important stage of the routing in the
traditional devices is the selection of the following
jump which is done taking into account the
characteristics of the packet and the state of the same
device, which usually changes little between packet
and packet. We will talk in this document about this
selection as the distribution of the incoming traffic
in information flows, formed by individual packets
that fulfil a same criterion.
Basically, the proposed solutions until now presents
the feature of distributing the guest code data by
means of its inclusion in the processed traffic
(capsules, active packets) or by means of a dynamic
programming of the node (programmable nodes).
The execution of guest code (the semantic) in
execution environments makes the services. The
design of the node allows selecting what packet
must go towards a specific service.
One of the initial objectives of the active networks
research group (Tennenhouse,1996) has been to
design networks with capacity of fine re-
programming so that they can allow new protocols
in a transparent way. Therefore, a good design of an
active node does not have to circumscribe to a
specific protocol. In fact, it will allow the node to
manage new protocols.
Until now the proposed solutions have a basic
problem: how to segment the incoming traffic and to
distribute it towards its active services. It is
necessary a criterion in each individual packet to
allow selecting a specific target execution
environment. A first approach to solve this question
could be to use the origin and target address as a
selection criteria, with the main disadvantage of not
allowing to distinct more than a flow for each pair
(sender, receptor). Other way to solve this question,
which is the most used solution, is to use the field
"port" of the transport protocols to distribute the
traffic, nevertheless these causes that this traffic has
necessary a TCP or UDP layer (in the case of IP
networks) and therefore it is committed to use these
protocols., besides loosing the necessary flexibility.
Our approach is oriented to guarantee flexibility,
creating a design of active nodes that does not fit its
traffic to a particular protocol and thus allowing
using anyone, even without knowing it a priori, but
preserving the capacity to segment the traffic in a
powerful and individual way.
VAIN architecture has been thought to be used over
IP protocol, nevertheless this is not a limitation,
since it is possible to extend its operation to other
existing protocols or designs. VAIN does not force
at any moment to use a specific network protocol,
although it recognizes the traditional ones by means
of his declaration in the "network scheme". This
scheme can be completed in-band or out-band with
new designs without the need of re-programming the
node entirely or affecting other flows of information.
The following sections will show the VAIN
architecture describing its fundamental components:
The description of the model as three layer
architecture, the internal architecture of the node, its
implantation and the deployment stages for using it.
2 VAIN - VIRTUAL ACTIVE IP
NODE
As we have already said, VAIN has been designed
for marketplaces and collaborative commerce. This
goal is reached through an abstraction layer that
enables complex designs that look for the
collaboration between final entities. These entities
only need to agree in the operations of their business
since the architecture hides the peculiarities of the
network. At the same time this abstraction allows
independence between the virtual design and the
infrastructures of the communication supplier.
VIRTUAL ACTIVE IP NODE FOR COLLABORATIVE ENVIRONMENTS
51