![](https://dblp.org/img/logo.ua.320x120.png)
![](https://dblp.org/img/dropdown.dark.16x16.png)
![](https://dblp.org/img/peace.dark.16x16.png)
Остановите войну!
for scientists:
![search dblp search dblp](https://dblp.org/img/search.dark.16x16.png)
![search dblp](https://dblp.org/img/search.dark.16x16.png)
default search action
John F. Heafner
Person information
Refine list
![note](https://dblp.org/img/note-mark.dark.12x12.png)
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
1980 – 1989
- 1986
- [c8]John F. Heafner, Ronald M. Huhn, Dennis R. Mensh, Richard E. Nance, Herbert Sallin:
Issues in simulation model integration, reusability, and adaptability (panel session). WSC 1986: 511 - 1982
- [c7]Frances H. Nielsen, John F. Heafner:
Description of a Planned Federal Information Processing Standard for the Session Protocol. COMPCON 1982: 272-278 - 1981
- [c6]John F. Heafner, Robert P. Blanc:
Description of a planned federal information processing standard for transport protocol. SIGCOMM 1981: 2-10 - 1980
- [c5]John F. Heafner, Frances H. Nielsen:
A linear programming model for optimal computer network protocol design. AFIPS National Computer Conference 1980: 855-861 - [c4]John F. Heafner, Frances H. Nielsen, M. Wayne Shiveley:
Extracting service features from protocol documents. AFIPS National Computer Conference 1980: 863-870
1970 – 1979
- 1974
- [c3]Donald R. Oestreicher, John F. Heafner, Jeffrey G. Rothenberg:
CONNECT: a user-oriented communications service. ACM Annual Conference (2) 1974: 531-538 - 1972
- [j2]Vinton G. Cerf, Eric Harslem, John F. Heafner, Robert M. Metcalfe, James E. White:
An Experimental Service for Adaptable Data Reconfiguration. IEEE Trans. Commun. 20(3): 557-564 (1972) - [c2]Stephen D. Crocker, John F. Heafner, Robert Metcalfe, Jonathan B. Postel:
Function-oriented protocols for the ARPA computer network. AFIPS Spring Joint Computing Conference 1972: 271-279 - [i26]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, Bob Sundberg, Dick Watson, James E. White:
The Data Transfer Protocol. RFC 264: 1-9 (1972) - 1971
- [c1]Robert H. Anderson, Eric Harslem, John F. Heafner, Vinton G. Cerf, James Madden, Robert Metcalfe, Arie Shoshani, James E. White, David C. M. Wood:
The Data Reconfiguration Service - an experiment in adaptable, process/process communication. Symposium on Problems in the Optimizations of Data Communications Systems 1971: 1-9 - [i25]Eric Harslem, John F. Heafner:
Some thoughts on Network Graphics. RFC 94: 1-6 (1971) - [i24]Eric Harslem, John F. Heafner, James E. White:
Network activity report: UCSB Rand. RFC 113: 1-2 (1971) - [i23]Eric Harslem, John F. Heafner, Edwin W. Meyer Jr.:
Request for comments on socket name structure. RFC 129: 1-6 (1971) - [i22]John F. Heafner:
Response to RFC 111: Pressure from the chairman. RFC 130: 1 (1971) - [i21]Eric Harslem, John F. Heafner:
Response to RFC 116: May NWG meeting. RFC 131: 1-3 (1971) - [i20]Robert H. Anderson, Vinton G. Cerf, Eric Harslem, John F. Heafner, James Madden, Robert M. Metcalfe, Arie Shoshani, James E. White, David C. M. Wood:
Status report on proposed Data Reconfiguration Service. RFC 138: 1-23 (1971) - [i19]Eric Harslem, John F. Heafner:
Comments on RFC 114: A File Transfer Protocol. RFC 141: 1-2 (1971) - [i18]John F. Heafner:
Minutes of Network Working Group meeting, 5/16 through 5/19/71. RFC 164: 1-32 (1971) - [i17]Robert H. Anderson, Vinton G. Cerf, Eric Harslem, John F. Heafner, James Madden, Robert M. Metcalfe, Arie Shoshani, James E. White, David C. M. Wood:
Data Reconfiguration Service: An implementation specification. RFC 166: 1-20 (1971) - [i16]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The Data Transfer Protocol. RFC 171: 1-9 (1971) - [i15]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The File Transfer Protocol. RFC 172: 1-12 (1971) - [i14]Eric Harslem, John F. Heafner:
Comments on "Socket Conventions Reconsidered". RFC 175: 1 (1971) - [i13]Eric Harslem, John F. Heafner:
NETWORK CHECKOUT. RFC 193: 1-2 (1971) - [i12]Vinton G. Cerf, Eric Harslem, John F. Heafner, Bob Metcalfe, James E. White:
The Data Reconfiguration Service - Compiler/Interpreter Implementation Notes. RFC 194: 1-18 (1971) - [i11]John F. Heafner:
Site Certification - Lincoln Labs 360/67. RFC 198: 1 (1971) - [i10]John F. Heafner, Eric Harslem:
Data transfer rates (Rand/UCLA). RFC 227: 1-2 (1971) - [i9]John F. Heafner, Eric Harslem:
Service center standards for remote usage: A user's view. RFC 231: 1-4 (1971) - [i8]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The File Transfer Protocol. RFC 265: 1-12 (1971) - [i7]Abhay K. Bhushan, Robert T. Braden, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Robert L. Sundberg, Richard W. Watson, James E. White:
Revision of the Mail Box Protocol. RFC 278: 1-4 (1971) - 1970
- [i6]Eric Harslem, John F. Heafner:
Comments on Protocol Re: NWG/RFC #36. RFC 39: 1-3 (1970) - [i5]Eric Harslem, John F. Heafner:
More Comments on the Forthcoming Protocol. RFC 40: 1-3 (1970) - [i4]Eric Harslem, John F. Heafner:
Comments on the Meyer Proposal. RFC 50: 1-2 (1970) - [i3]Eric Harslem, John F. Heafner, James E. White:
NCP Status Report: UCSB/Rand. RFC 78: 1 (1970) - [i2]Eric Harslem, John F. Heafner:
Protocols and Data Formats. RFC 80: 1-9 (1970) - [i1]Robert H. Anderson, Eric Harslem, John F. Heafner:
Language-machine for data reconfiguration. RFC 83: 1-13 (1970)
1960 – 1969
- 1967
- [j1]Gabriel F. Groner, John F. Heafner, T. W. Robinson:
On-Line Computer Classification of Handprinted Chinese Characters as a Translation Aid. IEEE Trans. Electron. Comput. 16(6): 856-860 (1967)
Coauthor Index
![](https://dblp.org/img/cog.dark.24x24.png)
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-25 05:55 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint