Implementing distribution lists in computer-based message systems
Proc. of the IFIP WG 6.5 working conference on Computer-based message services
A user-friendly naming convention for use in communication networks
Proc. of the IFIP WG 6.5 working conference on Computer-based message services
Proc. of the IFIP WG 6.5 working conference on Computer-based message services
Computer networks
ACM Transactions on Information Systems (TOIS)
48-bit absolute internet and Ethernet host numbers
SIGCOMM '81 Proceedings of the seventh symposium on Data communications
Efficient and robust policy routing using multiple hierarchical addresses
SIGCOMM '91 Proceedings of the conference on Communications architecture & protocols
Naming and registration for IBM distributed systems
IBM Systems Journal
A taxonomy of issues in name systems design and implementation
ACM SIGOPS Operating Systems Review
Dynamic names and private address maps: complete self-configuration for MANETs
CoNEXT '06 Proceedings of the 2006 ACM CoNEXT conference
YANAIL: yet another definition on names, addresses, identifiers, and locators
Proceedings of the 6th International Conference on Future Internet Technologies
tinyLUNAR: one-byte multihop communications through hybrid routing in wireless sensor networks
NEW2AN'07 Proceedings of the 7th international conference on Next Generation Teletraffic and Wired/Wireless Advanced Networking
Hi-index | 0.00 |
Naming and addressing are areas in which there is still a need for clarification. Many definitions for names, addresses, and routes have been proposed, but the exact relations among these concepts are obscure. A taxonomy of names, addresses, and routes is presented. First, we identify names and routes as the essential concepts of communication. Then, addresses are introduced as an intermediate form that eases the process of mapping between names and routes; an original definition of an address is thus proposed. Relations among names, addresses, and routes are explained with the concept of mapping. On this basis, a general model relating names, addresses, and routes is built and then applied recursively throughout a layered architecture, leading to a layered naming and addressing model which may play the same role for naming and addressing features that the OS1 reference model plays for the definition of services and protocols. Finally, the model is particularized to a typical network architecture. The model may also be applied to non-OSI layered systems; naming, addressing, and routing issues in any network architecture could be a particular instance of this layered model.