default search action
John M. McQuillan
Person information
- affiliation: Bolt, Beranek and Newman, Cambridge, MA, USA
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2000 – 2009
- 2009
- [j10]John M. McQuillan:
The Birth of Link-State Routing. IEEE Ann. Hist. Comput. 31(1): 68-71 (2009)
1990 – 1999
- 1995
- [j9]John M. McQuillan, Ira Richer, Eric C. Rosen:
An overview of the new routing algorithm for the ARPANET. Comput. Commun. Rev. 25(1): 54-60 (1995)
1980 – 1989
- 1980
- [j8]John M. McQuillan:
Local Network Technology and the Lessons of History. Comput. Networks 4: 235-238 (1980) - [j7]John M. McQuillan, Ira Richer, Eric C. Rosen:
The New Routing Algorithm for the ARPANET. IEEE Trans. Commun. 28(5): 711-719 (1980)
1970 – 1979
- 1979
- [c6]John M. McQuillan, Ira Richer, Eric C. Rosen:
An overview of the new routing algorithm for the ARPANET. SIGCOMM 1979: 63-68 - 1978
- [j6]Frits C. Schoute, John M. McQuillan:
A Comparison of Information Policies for Minimum Delay Routing Algorithms. IEEE Trans. Commun. 26(8): 1266-1271 (1978) - [j5]John M. McQuillan, Gilbert Falk, Ira Richer:
A Review of the Development and Performance of the ARPANET Routing Algorithm. IEEE Trans. Commun. 26(12): 1802-1811 (1978) - 1977
- [j4]John M. McQuillan:
Graph theory applied to optimal connectivity in computer networks. Comput. Commun. Rev. 7(2): 13-41 (1977) - [j3]John M. McQuillan, David C. Walden:
The ARPA Network Design Decisions. Comput. Networks 1: 243-289 (1977) - [j2]Gilbert Falk, John M. McQuillan:
Alternatives for Data Network Architectures. Computer 10(11): 22-29 (1977) - 1976
- [j1]John M. McQuillan:
Strategies for implementation of multi-host computer networks. Comput. Commun. Rev. 6(4): 19-24 (1976) - 1975
- [c5]William R. Crowther, Frank E. Heart, Alexander A. McKenzie, John M. McQuillan, David C. Walden:
Issues in packet switching network design. AFIPS National Computer Conference 1975: 161-175 - [c4]John M. McQuillan, David C. Walden:
Some considerations for a high performance message-based interprocess communication system. SIGCOMM/SIGOPS Workshop on Interprocess Communications 1975: 77-86 - 1973
- [c3]William R. Crowther, John M. McQuillan, David C. Walden:
Reliability issues in the ARPA network. DATACOMM 1973: 159-160 - [i8]John M. McQuillan:
Software checksumming in the IMP and network reliability. RFC 528: 1-9 (1973) - [i7]John M. McQuillan:
Response to RFC 567 - cross country network bandwidth. RFC 568: 1-3 (1973) - 1972
- [c2]John M. McQuillan, William R. Crowther, Bernard P. Cosell, David C. Walden, Frank E. Heart:
Improvements in the design and performance of the ARPA network. AFIPS Fall Joint Computing Conference (2) 1972: 741-754 - [i6]John M. McQuillan:
IMP System Change Notification. RFC 331: 1 (1972) - [i5]John M. McQuillan:
Three aids to improved network operation. RFC 381: 1-4 (1972) - [i4]John M. McQuillan:
Two Proposed Changes to the IMP-Host Protocol. RFC 394: 1-3 (1972) - [i3]John M. McQuillan:
Switch Settings on IMPs and TIPs. RFC 395: 1 (1972) - [i2]John M. McQuillan:
Scheduled IMP Software Releases. RFC 406: 1-2 (1972) - [i1]John M. McQuillan:
Removal of the 30-Second Delay When Hosts Come Up. RFC 410: 1-2 (1972) - 1971
- [c1]Dan Cohen, John M. McQuillan:
Computer graphics for transportation problems. AFIPS Spring Joint Computing Conference 1971: 77-81
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-24 22:46 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint