1982
DOI: 10.17487/rfc0871
|View full text |Cite
|
Sign up to set email alerts
|

Perspective on the ARPANET reference model

Abstract: The paper, by one of its developers, describes the conceptual framework in which the ARPANET intercomputer networking protocol suite, including the DoD standard Transmission Control Protocol (TCP) and Internet Protocol (IP), were designed. It also compares and contrasts several aspects of the ARPANET Reference Model (ARM) with the more widely publicized International Standards Organization's Reference Model for Open System Interconnection (ISORM).

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

1982
1982
2024
2024

Publication Types

Select...
5
3

Relationship

2
6

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 2 publications
0
6
0
Order By: Relevance
“…For instance, operating in a different country would merely require downloading from a different website or using a new smart card. 5 Avoiding the creation of m n problems has long been a hallmark of good communications design (see [19]). The need for machine-understandable policies leads us to the problem of developing a language for expressing policies.…”
Section: Policy Agilitymentioning
confidence: 99%
“…For instance, operating in a different country would merely require downloading from a different website or using a new smart card. 5 Avoiding the creation of m n problems has long been a hallmark of good communications design (see [19]). The need for machine-understandable policies leads us to the problem of developing a language for expressing policies.…”
Section: Policy Agilitymentioning
confidence: 99%
“…(That is, given an abstract enough interface--in the spirit of the Principle of Layering--a Host could, for example, go from doing TCP as its "Host-Host" protocol to, say, ECMA Class 4 as its "Transport" protocol without taking any particular cognizance of the change, however unattractive such a change would be to advocates of the APRANET Reference Model such as the author. See [3] for more on the implied "Reference Model" issues.) Finally, although a few rather specialized points could also be adduced, it should be noted that for network security architectures which are predicated on the ability to control all means of egress from and ingress to "the net", uniform use of OPEs is clearly desirable.…”
Section: Rfc 928mentioning
confidence: 99%
“…(For a more complete discussion, see Reference [4].) But it should be just about enough to slay the Woozle, especially if just one more protocol's most significant property can be snuck in.…”
Section: Tcpmentioning
confidence: 99%