Chad,
Your message of 4/8 ended with a list of changes needed to IPv6
implementations to implement RNET. Changes to processing logic are
just as serious as change to the format.
Steve
-------
The following changes need be made to the IP Version 6 Protocol Logic, in
routers, in order to impliment this technology:
1) encryption routines
2) recognization of RNET Route Requests
3) generation and recognization of RNET errors
4) routing table modifications
NB: the RNET Host address may be stored in the host address
of the route
entry. The Target Host address may be stored in the Netmask of
the
route entry. The Gateway address may be stored in the gateway of
route entry. The Route Decay may be stored in the Metric or be
implimented through some system timer.
5) routines to acquire keys from the RNET Centralized Server
6) storage of the IP address of the RNET Centralized Server
7) storage of the router's unique key
8) storage of the RNET Global Key
9) an additional flag for route entries marking them as RNET Route entries
The following changes need be made to the IP Version 6 Protocol Logic, in
hosts, in order to impliment this technology:
1) encryption routines
2) generation of RNET Route requests
3) recognization of RNET errors
4) routines to acquire keys from the RNET Centralized Server
5) storage of the IP address of the RNET Centralized Server
6) storage of the host's unique key
7) storage of the RNET Global Key
8) an additional flag in the IP Stack to identify the assigned host address
as being an RNET Host address so that the IP Stack is aware of the
protocol to follow in initiating connections. This allows
differentiation from
RNET Host addressess and regular IPs_______________________________________________
IETF mailing list
IETF(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf