% need to be able to attach (perhaps multiple) credentials to packets,
% that stay with those packets end-to-end rather than having to do
% tunneling. those credentials (sadly) may need to be based on both
% user identity and current network location. it should follow that
% (c) IP addresses have nothing to do with authentication in such a
% world - there will be too many cases where trust boundaries and IP
% topology don't coincide, and trying to do VPN-like things for all
% of the different things you want to authenticate to from the
% same host will be too hairy.
%
% Keith
Erp,
"current network location" == IP address
your model needs to be extended a bit. I see
three types of "things", where the node is,
where applications are being housed, & who is
running them. Credentials apply to all three.
--bill
(thinking that renumbering the Internet every
20minutes is a desireable goal... again :)
More work on supporting untethered nodes & nets
is a good thing. DynamicDNS & DHCP are a good
first start. "fixing" the transport protocols
... another kettle of fish ...
