Proceedings of the Seventh Symposium on Data Communications - SIGCOMM '81 1981
DOI: 10.1145/800081.802680
|View full text |Cite
|
Sign up to set email alerts
|

48-bit absolute internet and Ethernet host numbers

Abstract: Xerox internets and Ethernet local computer networks use 48-bit absolute host numbers. This is a radical departure from practices currently in use in internetwork systems and local networks. This paper describes how the host numbering scheme was designed in the context of an overall internetwork and distributed systems architecture.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

1982
1982
1993
1993

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(2 citation statements)
references
References 6 publications
0
2
0
Order By: Relevance
“…Although the ideas outlined so far seem fairly straightforward, it is surprisingly easy to find real-world examples that pose a challenge in interpretation. In the Xerox/DEC/Intel Ethernet [5,6], for example, the concept of a network attachment point is elusive, because it collapses into the node name. A node can physical attach to an Ethernet anywhere along it; the node brings with it a 48-bit unique identifier that its interfaces watches for in packets passing by.…”
Section: Some Real-world Examplesmentioning
confidence: 99%
See 1 more Smart Citation
“…Although the ideas outlined so far seem fairly straightforward, it is surprisingly easy to find real-world examples that pose a challenge in interpretation. In the Xerox/DEC/Intel Ethernet [5,6], for example, the concept of a network attachment point is elusive, because it collapses into the node name. A node can physical attach to an Ethernet anywhere along it; the node brings with it a 48-bit unique identifier that its interfaces watches for in packets passing by.…”
Section: Some Real-world Examplesmentioning
confidence: 99%
“…For another example, the ARPANET NCP protocol provides character string names that appear, from their mnemonics, to be node names or service names, but in fact they are the names of network attachment points [6]. Thus the character string name RADC-Multics is the name of the network attachment point at ARPANET IMP 18, port 0, so reattaching the node (a Honeywell 68/80 computer) to another network attachment point requires either that the users learn a new name for the service or else a change of tables in all other nodes.…”
Section: Some Real-world Examplesmentioning
confidence: 99%