Implications of fragmentation dynamic routing for internet datagram authentication
ACM SIGCOMM Computer Communication Review
Sirpent: a high-performance internetworking approach
SIGCOMM '89 Symposium proceedings on Communications architectures & protocols
SIGCOMM '92 Conference proceedings on Communications architectures & protocols
A new label-based source routing for multi-ring networks
IEEE/ACM Transactions on Networking (TON)
Issues in using DARPA domain names for computer mail
SIGCOMM '85 Proceedings of the ninth symposium on Data communications
Identification in computer networks
SIGCOMM '83 Proceedings of the eighth symposium on Data communications
NIRA: a new Internet routing architecture
FDNA '03 Proceedings of the ACM SIGCOMM workshop on Future directions in network architecture
LIPSIN: line speed publish/subscribe inter-networking
Proceedings of the ACM SIGCOMM 2009 conference on Data communication
A mutualistic resource pooling architecture
Proceedings of the Re-Architecting the Internet Workshop
Hi-index | 0.00 |
As plans for network interconnection develop, the problems of internet routing and addressing become increasingly important. In one popular model of internet addressing, a hierarchical form of network and local (within network) address is used, with the source providing only the destination address while the intermediate network(s) and/or Gateways between networks take care of routing packets to that destination by various paths. This and related techniques requiring some form of routing table and knowledge at intermediate nodes are more fully discussed in [1,2,3]. This paper considers another technique for internet routing in which the source of internet packets specifies the complete internet route. When the entire route accompanies each internet packet, no routing decisions or tables are required at Gateways, but the packet format is complicated and overhead increases. In particular, the packet must carry a varying number of intermediate addresses depending on the path and destination [4]. This overhead may be reduced by setting up a fixed route with connection tables [1] when a connection is established.