Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

James D. Atkins

dblp:271/7479 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1980
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Computer networks · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer networks
1 paper
Internet architecture and protocols · 38% Software-defined and programmable networks · 38% Routing and switching · 12%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Internet architecture and protocols
layered network architecture
0.011980
Path Control: The Transport Network of SNA · IEEE Trans. Commun. 1980
Software-defined and programmable networks
path control
0.011980
Path Control: The Transport Network of SNA · IEEE Trans. Commun. 1980
Transport protocols and congestion control
flow control
0.011980
Path Control: The Transport Network of SNA · IEEE Trans. Commun. 1980
Routing and switching
routing
0.011980
Path Control: The Transport Network of SNA · IEEE Trans. Commun. 1980
YearPublicationVenuePosition
1980 Path Control: The Transport Network of SNA
abstract
A primary virtue of a communications system is transparency of the transport network to the person using the system. The layered structure of SNA provides for the separation of the transport network, called path control, from higher level functions involving the end users of the network. This paper describes the structure of the path control layer of SNA, focusing on connectivity, routing, and flow control. The end user's view of these architectural concepts is presented, as well as a discussion of the underlying formats and protocols.
James D. Atkins
IEEE Trans. Commun.1