1012: Bibliography of Request For Comments 1 through 999.

References

• RFC28: Time Standards.
• RFC29: Response to RFC 28.
• RFC30: Documentation Conventions.
• RFC31: Binary Message Forms in Computer.
• RFC32: Some Thoughts on SRI's Proposed Real Time Clock.
• RFC33: New Host-Host Protocol.
• RFC34: Some Brief Preliminary Notes on the Augmentation Research Center Clock.
• RFC35: Network Meeting.
• RFC36: Protocol Notes.
• RFC37: Network Meeting Epilogue, etc.
• RFC38: Comments on Network Protocol from NWG/RFC #36.
• RFC39: Comments on Protocol Re: NWG/RFC #36.
• RFC40: More Comments on the Forthcoming Protocol.
• RFC41: IMP-IMP Teletype Communication.
• RFC42: Message Data Types.
• RFC43: Proposed Meeting.
• RFC44: Comments on NWG/RFC 33 and 36.
• RFC45: New Protocol is Coming.
• RFC46: ARPA Network protocol notes.
• RFC47: BBN's Comments on NWG/RFC #33.
• RFC48: Possible protocol plateau.
• RFC49: Conversations with S. Crocker (UCLA).
• RFC50: Comments on the Meyer Proposal.
• RFC51: Proposal for a Network Interchange Language.
• RFC52: Updated distribution list.
• RFC53: Official protocol mechanism.
• RFC54: Official Protocol Proffering.
• RFC55: Prototypical implementation of the
• RFC56: Third Level Protocol: Logger Protocol.
• RFC57: Thoughts and Reflections on NWG/RFC 54.
• RFC58: Logical Message Synchronization.
• RFC59: Flow Control - Fixed Versus Demand Allocation.
• RFC60: Simplified NCP Protocol.
• RFC61: Note on Interprocess Communication in a Resource Sharing Computer Network.
• RFC62: Systems for Interprocess Communication in a Resource Sharing Computer Network.
• RFC63: Belated Network Meeting Report.
• RFC64: Getting rid of marking.
• RFC65: Comments on Host/Host Protocol document #1.
• RFC66: NIC - third level ideas and other noise.
• RFC67: Proposed Change to Host/IMP Spec to Eliminate Marking.
• RFC68: Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and
• RFC69: Distribution List Change for
• RFC70: Note on Padding.
• RFC71: Reallocation in Case of Input Error.
• RFC73: Response to NWG/RFC 67.
• RFC74: Specifications for network use of the UCSB On-Line System.
• RFC75: Network Meeting.
• RFC76: Connection by name: User oriented protocol.
• RFC77: Network meeting report.
• RFC78: NCP Status Report: UCSB/Rand.
• RFC79: Logger Protocol error.
• RFC80: Protocols and Data Formats.
• RFC81: Request for Reference Information.
• RFC82: Network Meeting Notes.
• RFC83: Language-machine for data reconfiguration.
• RFC84: List of NWG/RFC's 1-80.
• RFC85: Network Working Group meeting.
• RFC86: Proposal for a Network Standard Format for a Data Stream to Control Graphics Display.
• RFC87: Topic for Discussion at the Next Network Working Group Meeting.
• RFC88: NETRJS: A third level protocol for Remote Job Entry.
• RFC89: Some historic moments in networking.
• RFC90: CCN as a Network Service Center.
• RFC91: Proposed User-User Protocol.
• RFC93: Initial Connection Protocol.
• RFC94: Some thoughts on Network Graphics.
• RFC95: Distribution of NWG/RFC's through the
• RFC96: An Interactive Network Experiment to Study Modes of Access the Network Information Center.
• RFC97: First Cut at a Proposed Telnet Protocol.
• RFC98: Logger Protocol Proposal.
• RFC99: Network Meeting.
• RFC100: Categorization and guide to NWG/RFCs.
• RFC101: Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971.
• RFC102: Output of the Host-Host Protocol glitch cleaning committee.
• RFC103: Implementation of Interrupt Keys.
• RFC104: Link 191.
• RFC105: Network Specifications for Remote Job Entry and Remote Job Output Retrieval at
• RFC106: User/Server Site Protocol Network Host Questionnaire.
• RFC107: Output of the Host-Host Protocol Glitch Cleaning Committee.
• RFC108: Attendance list at the Urbana NWG meeting, February 17-19, 1971.
• RFC109: Level III Server Protocol for the Lincoln Laboratory NIC 360/67 Host.
• RFC110: Conventions for using an IBM 2741 terminal as a user console for access to network server hosts.
• RFC111: Pressure from the Chairman.
• RFC112: User/Server Site Protocol: Network host questionnaire responses.
• RFC113: Network activity report: UCSB Rand.
• RFC114: File Transfer Protocol.
• RFC115: Some Network Information Center policies on handling documents.
• RFC116: Structure of the May NWG Meeting.
• RFC117: Some comments on the official protocol.
• RFC118: Recommendations for facility documentation.
• RFC119: Network Fortran subprograms.
• RFC120: Network PL1 subprograms.
• RFC121: Network on-line operators.
• RFC122: Network specifications for UCSB's Simple-Minded File System.
• RFC123: Proffered Official
• RFC124: Typographical error in RFC 107.
• RFC125: Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream.
• RFC126: Graphics Facilities at Ames Research Center.
• RFC127: Comments on RFC 123.
• RFC128: Bytes.
• RFC129: Request for comments on socket name structure.
• RFC130: Response to RFC 111: Pressure from the chairman.
• RFC131: Response to RFC 116: May NWG meeting.
• RFC132: Typographical Error in RFC 107.
• RFC133: File Transfer and Error Recovery.
• RFC134: Network Graphics meeting.
• RFC135: Response to NWG/RFC 110.
• RFC136: Host accounting and administrative procedures.
• RFC137: Telnet Protocol - a proposed document.
• RFC138: Status report on proposed Data Reconfiguration Service.
• RFC139: Discussion of Telnet Protocol.
• RFC140: Agenda for the May NWG meeting.
• RFC141: Comments on RFC 114: A File Transfer Protocol.
• RFC142: Time-Out Mechanism in the Host-Host Protocol.
• RFC143: Regarding proffered official
• RFC144: Data sharing on computer networks.
• RFC145: Initial Connection Protocol Control Commands.
• RFC146: Views on issues relevant to data sharing on computer networks.
• RFC147: Definition of a socket.
• RFC148: Comments on RFC 123.
• RFC149: Best Laid Plans.
• RFC150: Use of IPC Facilities: A Working Paper.
• RFC151: Comments on a proffered official ICP: RFCs 123, 127.
• RFC152: SRI Artificial Intelligence status report.
• RFC153: SRI ARC-NIC status.
• RFC154: Exposition Style.
• RFC155: ARPA Network mailing lists.
• RFC156: Status of the Illinois site: Response to RFC 116.
• RFC157: Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems.
• RFC158: Telnet Protocol: A Proposed Document.
• RFC160: RFC brief list. Network Information Center. Stanford Research Institute.
• RFC161: Solution to the race condition in the
• RFC162: NETBUGGER3.
• RFC163: Data transfer protocols.
• RFC165: Proffered official Initial Connection Protocol.
• RFC166: Data Reconfiguration Service: An implementation specification.
• RFC167: Socket conventions reconsidered.
• RFC168: ARPA Network mailing lists.
• RFC169: Computer networks.
• RFC170: RFC List by Number. Network Information Center. Stanford Research Institute.
• RFC171: The Data Transfer Protocol.
• RFC172: The File Transfer Protocol.
• RFC173: Network Data Management Committee Meeting Announcement.
• RFC174: UCLA - Computer Science Graphics Overview.
• RFC175: Comments on "Socket Conventions Reconsidered".
• RFC176: Comments on "Byte size for connections".
• RFC177: Device independent graphical display description.
• RFC178: Network graphic attention handling.
• RFC179: Link Number Assignments.
• RFC180: File system questionnaire.
• RFC181: Modifications to RFC 177.
• RFC182: Compilation of list of relevant site reports.
• RFC183: EBCDIC codes and their mapping to
• RFC184: Proposed graphic display modes.
• RFC185: NIC distribution of manuals and handbooks.
• RFC186: Network graphics loader.
• RFC187: Network/440 Protocol Concept.
• RFC188: Data management meeting announcement.
• RFC189: Interim NETRJS specifications.
• RFC190: DEC PDP-10-IMLAC communications system.
• RFC191: Graphics implementation and conceptualization at Augmentation Research Center.
• RFC192: Some factors which a Network Graphics Protocol must consider.
• RFC193: NETWORK
• RFC194: The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes.
• RFC195: Data computers-data descriptions and access language.
• RFC196: Mail Box Protocol.
• RFC197: Initial Connection Protocol - Reviewed.
• RFC198: Site Certification - Lincoln Labs 360/67.
• RFC199: Suggestions for a network data-tablet graphics protocol.
• RFC200: RFC list by number.
• RFC202: Possible Deadlock in
• RFC203: Achieving reliable communication.
• RFC204: Sockets in use.
• RFC205: NETCRT - a character display protocol.
• RFC206: User Telnet - description of an initial implementation.
• RFC207: September Network Working Group meeting.
• RFC208: Address tables.
• RFC209: Host/IMP interface documentation.
• RFC210: Improvement of Flow Control.
• RFC211: ARPA Network mailing lists.
• RFC212: NWG meeting on network usage. Information Sciences Institute University of Southern California.
• RFC213: IMP System change notification.
• RFC214: Network checkpoint.
• RFC215: NCP, ICP, and Telnet: The Terminal IMP implementation.
• RFC216: Telnet access to UCSB's On-Line System.
• RFC217: Specifications changes for OLS, RJE/RJOR, and
• RFC218: Changing the IMP status reporting facility.
• RFC221: Mail Box Protocol: Version 2.
• RFC222: Subject: System programmer's workshop.
• RFC223: Network Information Center schedule for network users.
• RFC224: Comments on Mailbox Protocol.
• RFC225: Rand/UCSB network graphics experiment.
• RFC226: Standardization of host mnemonics.
• RFC227: Data transfer rates (Rand/UCLA).
• RFC228: Clarification.
• RFC229: Standard host names.
• RFC230: Toward reliable operation of minicomputer-based terminals on a
• RFC231: Service center standards for remote usage: A user's view.
• RFC232: Postponement of network graphics meeting.
• RFC233: Standardization of host call letters.
• RFC234: Network Working Group meeting schedule.
• RFC235: Site status.
• RFC236: Standard host names.
• RFC237: NIC view of standard host names.
• RFC238: Comments on DTP and FTP proposals.
• RFC239: Host mnemonics proposed in RFC 226 (NIC 7625).
• RFC240: Site Status.
• RFC241: Connecting computers to MLC ports.
• RFC242: Data Descriptive Language for Shared Data.
• RFC243: Network and data sharing bibliography.
• RFC245: Reservations for Network Group meeting.
• RFC246: Network Graphics meeting.
• RFC247: Proffered set of standard host names.
• RFC249: Coordination of equipment and supplies purchase.
• RFC250: Some thoughts on file transfer.
• RFC251: Weather data.
• RFC252: Network host status.
• RFC253: Second Network Graphics meeting details.
• RFC254: Scenarios for using ARPANET computers.
• RFC255: Status of network hosts.
• RFC256: IMPSYS change notification.
• RFC263: "Very Distant" Host interface.
• RFC264: The Data Transfer Protocol.
• RFC265: The File Transfer Protocol.
• RFC266: Network host status.
• RFC267: Network Host Status.
• RFC268: Graphics facilities information.
• RFC269: Some Experience with File Transfer.
• RFC270: Correction to BBN Report No. 1822 (NIC NO 7958).
• RFC271: IMP System change notifications.
• RFC273: More on standard host names.
• RFC274: Establishing a local guide for network usage.
• RFC276: NIC course.
• RFC278: Revision of the Mail Box Protocol.
• RFC280: A Draft of Host Names.
• RFC281: Suggested addition to File Transfer Protocol.
• RFC282: Graphics meeting report.
• RFC283: NETRJT: Remote Job Service Protocol for
• RFC285: Network graphics.
• RFC286: Network Library Information System.
• RFC287: Status of Network Hosts.
• RFC288: Network host status.
• RFC289: What we hope is an official list of host names.
• RFC290: Computer networks and data sharing: A bibliography.
• RFC291: Data Management Meeting Announcement.
• RFC292: Graphics Protocol: Level 0 only.
• RFC293: Network Host Status.
• RFC294: The Use of "Set Data Type" Transaction in File Transfer Protocol.
• RFC295: Report of the Protocol Workshop, 12 October 1971.
• RFC296: DS-1 display system.
• RFC297: TIP Message Buffers.
• RFC298: Network host status.
• RFC299: Information Management System.
• RFC300: ARPA Network mailing lists.
• RFC301: BBN IMP (#5) and NCC Schedule March 4, 1971.
• RFC302: Exercising The
• RFC303: ARPA Network mailing lists. Network Information Center. Stanford Research Institute.
• RFC304: Data management system proposal for the ARPA network.
• RFC305: Unknown Host Numbers.
• RFC306: Network host status.
• RFC307: Using network Remote Job Entry.
• RFC308: ARPANET host availability data.
• RFC309: Data and File Transfer Workshop Announcement.
• RFC310: Another Look at Data and File Transfer Protocols.
• RFC311: New Console Attachments to the USCB Host.
• RFC312: Proposed Change in IMP-to-Host Protocol.
• RFC313: Computer based instruction.
• RFC314: Network Graphics Working Group Meeting.
• RFC315: Network Host Status.
• RFC316: ARPA Network Data Management Working Group.
• RFC317: Official Host-Host Protocol Modification: Assigned Link Numbers.
• RFC318: Telnet Protocols.
• RFC319: Network Host Status.
• RFC320: Workshop on Hard Copy Line Printers.
• RFC321: CBI Networking Activity at
• RFC322: Well known socket numbers.
• RFC323: Formation of Network Measurement Group (NMG).
• RFC324: RJE Protocol meeting.
• RFC325: Network Remote Job Entry program -
• RFC326: Network Host Status.
• RFC327: Data and File Transfer workshop notes.
• RFC328: Suggested Telnet Protocol Changes.
• RFC329: ARPA Network Mailing Lists. Network Information Center. Stanford Research Institute.
• RFC330: Network Host Status.
• RFC331: IMP System Change Notification.
• RFC332: Network Host Status.
• RFC333: Proposed experiment with a Message Switching Protocol.
• RFC334: Network Use on May 8.
• RFC335: New Interface - IMP/360.
• RFC336: Level 0 Graphic Input Protocol.
• RFC338: EBCDIC/ASCII Mapping for Network
• RFC339: MLTNET: A "Multi Telnet" Subsystem for Tenex.
• RFC340: Proposed Telnet Changes.
• RFC342: Network Host Status.
• RFC343: IMP System change notification.
• RFC344: Network Host Status.
• RFC345: Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN).
• RFC346: Satellite Considerations.
• RFC347: Echo process.
• RFC348: Discard Process.
• RFC349: Proposed Standard Socket Numbers.
• RFC350: User Accounts for UCSB On-Line System.
• RFC351: Graphics information form for the ARPANET graphics resources notebook.
• RFC352: TIP Site Information Form.
• RFC353: Network host status.
• RFC354: File Transfer Protocol.
• RFC355: Response to NWG/RFC 346.
• RFC356: ARPA Network Control Center.
• RFC357: Echoing strategy for satellite links.
• RFC358: Not Issued.
• RFC360: Proposed Remote Job Entry Protocol.
• RFC361: Deamon Processes on Host 106.
• RFC362: Network Host Status.
• RFC364: Serving remote users on the
• RFC365: Letter to All TIP Users.
• RFC366: Network Host Status.
• RFC367: Network host status.
• RFC368: Comments on "Proposed Remote Job Entry Protocol".
• RFC369: Evaluation of ARPANET services January-March, 1972.
• RFC370: Network Host Status.
• RFC371: Demonstration at International Computer Communications Conference.
• RFC372: Notes on a Conversation with Bob Kahn on the
• RFC373: Arbitrary Character Sets.
• RFC374: IMP System Announcement.
• RFC376: Network Host Status.
• RFC377: Using TSO via ARPA Network Virtual Terminal.
• RFC378: Traffic statistics (July 1972).
• RFC379: Using TSO at CCN. R.. Braden.
• RFC381: Three aids to improved network operation.
• RFC382: Mathematical Software on the ARPA Network.
• RFC384: Official site idents for organizations in the ARPA Network.
• RFC385: Comments on the File Transfer Protocol.
• RFC386: Letter to TIP users-2.
• RFC387: Some experiences in implementing Network Graphics Protocol Level 0.
• RFC388: NCP statistics.
• RFC389: UCLA Campus Computing Network Liaison Staff for ARPA Network.
• RFC390: TSO Scenario.
• RFC391: Traffic statistics (August 1972).
• RFC392: Measurement of host costs for transmitting network data.
• RFC393: Comments on Telnet Protocol Changes.
• RFC394: Two Proposed Changes to the IMP-Host Protocol.
• RFC395: Switch Settings on IMPs and TIPs.
• RFC396: Network Graphics Working Group Meeting - Second Iteration.
• RFC398: ICP Sockets.
• RFC399: SMFS Login and Logout.
• RFC400: Traffic Statistics (September 1972).
• RFC401: Conversion of NGP-0 Coordinates to Device Specific Coordinates.
• RFC402: ARPA Network Mailing Lists.
• RFC403: Desirability of a network 1108 service.
• RFC404: Host Address Changes Involving Rand and
• RFC405: Correction to RFC 404.
• RFC406: Scheduled IMP Software Releases.
• RFC407: Remote Job Entry Protocol.
• RFC408: NETBANK.
• RFC409: Tenex interface to UCSB's Simple-Minded File System.
• RFC410: Removal of the 30-Second Delay When Hosts Come Up.
• RFC411: New MULTICS Network Software Features.
• RFC412: User FTP Documentation.
• RFC413: Traffic statistics (October 1972).
• RFC414: File Transfer Protocol (FTP) status and further comments.
• RFC415: Tenex bandwidth.
• RFC416: ARC System Will Be Unavailable for Use During Thanksgiving Week.
• RFC417: Link usage violation.
• RFC418: Server file transfer under TSS/360 at NASA Ames.
• RFC419: To: Network liaisons and station agents.
• RFC420: CCA ICCC weather demo.
• RFC421: Software Consulting Service for Network Users.
• RFC422: Traffic statistics (November 1972).
• RFC423: UCLA Campus Computing Network Liaison Staff for
• RFC425: "But my NCP costs $500 a day".
• RFC426: Reconnection Protocol.
• RFC429: Character Generator Process.
• RFC430: Comments on File Transfer Protocol.
• RFC431: Update on SMFS Login and Logout.
• RFC432: Network logical map.
• RFC433: Socket number list.
• RFC434: IMP/TIP memory retrofit schedule.
• RFC435: Telnet issues.
• RFC436: Announcement of RJS at
• RFC437: Data Reconfiguration Service at
• RFC438: FTP server-server interaction.
• RFC439: PARRY encounters the
• RFC440: Scheduled network software maintenance.
• RFC441: Inter-Entity Communication - an experiment.
• RFC442: Current flow-control scheme for
• RFC443: Traffic statistics (December 1972).
• RFC445: IMP/TIP preventive maintenance schedule.
• RFC446: Proposal to consider a network program resource notebook.
• RFC447: IMP/TIP memory retrofit schedule.
• RFC448: Print files in
• RFC449: Current flow-control scheme for
• RFC450: MULTICS sampling timeout change.
• RFC451: Tentative proposal for a Unified User Level Protocol.
• RFC452: TELENET Command at Host
• RFC453: Meeting announcement to discuss a network mail system.
• RFC454: File Transfer Protocol - meeting announcement and a new proposed document.
• RFC455: Traffic statistics (January 1973).
• RFC456: Memorandum: Date change of mail meeting.
• RFC457: TIPUG.
• RFC458: Mail retrieval via
• RFC459: Network questionnaires.
• RFC460: NCP survey.
• RFC461: Telnet Protocol meeting announcement.
• RFC462: Responding to user needs.
• RFC463: FTP comments and response to RFC 430.
• RFC464: Resource notebook framework.
• RFC466: Telnet logger/server for host LL-67.
• RFC467: Proposed change to Host-Host Protocol: Resynchronization of connection status.
• RFC468: FTP data compression.
• RFC469: Network mail meeting summary.
• RFC470: Change in socket for TIP news facility.
• RFC471: Workshop on multi-site executive programs.
• RFC472: Illinois' reply to Maxwell's request for graphics information (NIC 14925).
• RFC473: MIX and MIXAL?.
• RFC474: Announcement of NGWG meeting: Call for papers.
• RFC475: FTP and network mail system.
• RFC476: IMP/TIP memory retrofit schedule (rev 2).
• RFC477: Remote Job Service at
• RFC478: FTP server-server interaction -
• RFC479: Use of FTP by the NIC Journal.
• RFC480: Host-dependent FTP parameters.
• RFC482: Traffic statistics (February 1973).
• RFC483: Cancellation of the resource notebook framework meeting.
• RFC485: MIX and MIXAL at
• RFC486: Data transfer revisited.
• RFC487: Free file transfer.
• RFC488: NLS classes at network sites.
• RFC489: Comment on resynchronization of connection status proposal.
• RFC490: Surrogate RJS for UCLA-CCN.
• RFC491: What is "Free"?.
• RFC492: Response to RFC 467.
• RFC493: Graphics Protocol.
• RFC494: Availability of MIX and MIXAL in the Network.
• RFC495: Telnet Protocol specifications.
• RFC496: TNLS quick reference card is available.
• RFC497: Traffic statistics (March 1973).
• RFC498: On mail service to
• RFC499: Harvard's network
• RFC500: Integration of data management systems on a computer network.
• RFC501: Un-muddling "free file transfer".
• RFC503: Socket number list.
• RFC504: Distributed resources workshop announcement.
• RFC505: Two solutions to a file transfer access problem.
• RFC506: FTP command naming problem.
• RFC508: Real-time data transmission on the
• RFC509: Traffic statistics (April 1973).
• RFC510: Request for network mailbox addresses.
• RFC511: Enterprise phone service to NIC from ARPANET sites.
• RFC512: More on lost message detection.
• RFC513: Comments on the new Telnet specifications.
• RFC514: Network make-work.
• RFC515: Specifications for Datalanguage, Version 0/9.
• RFC516: Lost message detection.
• RFC518: ARPANET accounts.
• RFC519: Resource evaluation.
• RFC520: Memo to FTP group: Proposal for File Access Protocol.
• RFC521: Restricted use of IMP
• RFC522: Traffic statistics (May 1973).
• RFC523: SURVEY is in operation again.
• RFC524: Proposed Mail Protocol.
• RFC525: MIT-MATHLAB meets UCSB-OLS -an example of resource sharing.
• RFC526: Technical meeting: Digital image processing software systems.
• RFC527: ARPAWOCKY.
• RFC528: Software checksumming in the IMP and network reliability.
• RFC529: Note on protocol synch sequences.
• RFC530: Report on the Survey project.
• RFC531: Feast or famine? A response to two recent RFC's about network information.
• RFC532: UCSD-CC Server-FTP facility.
• RFC533: Message-ID numbers.
• RFC534: Lost message detection.
• RFC535: Comments on File Access Protocol.
• RFC537: Announcement of NGG meeting July 16-17.
• RFC538: Traffic statistics (June 1973).
• RFC539: Thoughts on the mail protocol proposed in RFC 524.
• RFC542: File Transfer Protocol.
• RFC543: Network journal submission and delivery.
• RFC544: Locating on-line documentation at SRI-ARC.
• RFC545: Of what quality be the UCSB resources evaluators?.
• RFC546: Tenex load averages for July 1973.
• RFC547: Change to the Very Distant Host specification.
• RFC548: Hosts using the IMP Going Down message.
• RFC549: Minutes of Network Graphics Group meeting, 15-17 July 1973.
• RFC550: NIC NCP experiment.
• RFC551: NYU, ANL, and LBL Joining the Net. Feinroth.
• RFC552: Single access to standard protocols.
• RFC553: Draft design for a text/graphics protocol.
• RFC555: Responses to critiques of the proposed mail protocol.
• RFC556: Traffic statistics (July 1973).
• RFC557: Revelations in network host measurements.
• RFC559: Comments on The New Telnet Protocol and its Implementation.
• RFC560: Remote Controlled Transmission and Echoing Telnet option.
• RFC561: Standardizing Network Mail Headers.
• RFC562: Modifications to the Telnet specification.
• RFC563: Comments on the RCTE Telnet option.
• RFC565: Storing network survey data at the datacomputer.
• RFC566: Traffic statistics (August 1973).
• RFC567: Cross Country Network Bandwidth.
• RFC568: Response to RFC 567 - cross country network bandwidth.
• RFC569: NETED: A Common Editor for the ARPA Network.
• RFC570: Experimental input mapping between NVT ASCII and UCSB On Line System.
• RFC571: Tenex FTP problem.
• RFC573: Data and file transfer: Some measurement results.
• RFC574: Announcement of a mail facility at
• RFC576: Proposal for modifying linking.
• RFC577: Mail priority.
• RFC578: Using MIT-Mathlab MACSYMA from MIT-DMS Muddle.
• RFC579: Traffic statistics (September 1973).
• RFC580: Note to Protocol Designers and Implementers.
• RFC581: Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option.
• RFC582: Comments on RFC 580: Machine readable protocols.
• RFC584: Charter for ARPANET Users Interest Working Group.
• RFC585: ARPANET users interest working group meeting.
• RFC586: Traffic statistics (October 1973).
• RFC587: Announcing new Telnet options.
• RFC588: London node is now up.
• RFC589: CCN NETRJS server messages to remote user.
• RFC590: MULTICS address change.
• RFC591: Addition to the Very Distant Host specifications.
• RFC592: Some thoughts on system design to facilitate resource sharing.
• RFC593: Telnet and FTP implementation schedule change.
• RFC594: Speedup of Host-IMP interface.
• RFC595: Second thoughts in defense of the Telnet Go-Ahead.
• RFC596: Second thoughts on Telnet Go-Ahead.
• RFC597: Host status.
• RFC598: RFC index - December 5, 1973. Network Information Center. Stanford Research Institute.
• RFC599: Update on
• RFC600: Interfacing an Illinois plasma terminal to the
• RFC601: Traffic statistics (November 1973).
• RFC602: "The stockings were hung by the chimney with care".
• RFC603: Response to RFC 597: Host status.
• RFC604: Assigned link numbers.
• RFC606: Host names on-line.
• RFC607: Comments on the File Transfer Protocol.
• RFC608: Host names on-line.
• RFC609: Statement of upcoming move of NIC/NLS service.
• RFC610: Further datalanguage design concepts.
• RFC611: Two changes to the IMP/Host Protocol to improve user/network communications.
• RFC612: Traffic statistics (December 1973).
• RFC613: Network connectivity: A response to RFC 603.
• RFC614: Response to RFC 607: "Comments on the File Transfer Protocol".
• RFC615: Proposed Network Standard Data Pathname syntax.
• RFC616: Latest network maps.
• RFC617: Note on socket number assignment.
• RFC618: Few observations on NCP statistics.
• RFC619: Mean round-trip times in the
• RFC620: Request for monitor host table updates.
• RFC621: NIC user directories at SRI
• RFC622: Scheduling IMP/TIP down time.
• RFC623: Comments on on-line host name service.
• RFC624: Comments on the File Transfer Protocol.
• RFC625: On-line hostnames service.
• RFC626: On a possible lockup condition in IMP subnet due to message sequencing.
• RFC627: ASCII text file of hostnames.
• RFC628: Status of RFC numbers and a note on pre-assigned journal numbers.
• RFC630: FTP error code usage for more reliable mail service.
• RFC631: International meeting on minicomputers and data communication: Call for papers.
• RFC632: Throughput degradations for single packet messages.
• RFC633: IMP/TIP preventive maintenance schedule.
• RFC634: Change in network address for Haskins Lab.
• RFC635: Assessment of ARPANET protocols.
• RFC636: TIP/Tenex reliability improvements.
• RFC637: Change of network address for SU-DSL.
• RFC638: IMP/TIP preventive maintenance schedule.
• RFC640: Revised FTP reply codes.
• RFC642: Ready line philosophy and implementation.
• RFC643: Network Debugging Protocol.
• RFC644: On the problem of signature authentication for network mail.
• RFC645: Network Standard Data Specification syntax.
• RFC647: Proposed protocol for connecting host computers to ARPA-like networks via front end processors.
• RFC651: Revised Telnet status option.
• RFC652: Telnet output carriage-return disposition option.
• RFC653: Telnet output horizontal tabstops option.
• RFC654: Telnet output horizontal tab disposition option.
• RFC655: Telnet output formfeed disposition option.
• RFC656: Telnet output vertical tabstops option.
• RFC657: Telnet output vertical tab disposition option.
• RFC658: Telnet output linefeed disposition.
• RFC659: Announcing additional Telnet options.
• RFC660: Some changes to the IMP and the IMP/Host interface.
• RFC661: Protocol information.
• RFC662: Performance improvement in ARPANET file transfers from Multics.
• RFC663: Lost message detection and recovery protocol.
• RFC666: Specification of the Unified User-Level Protocol.
• RFC667: BBN host ports.
• RFC669: November, 1974, survey of New-Protocol Telnet servers.
• RFC671: Note on Reconnection Protocol.
• RFC674: Procedure call documents: Version 2.
• RFC675: Specification of Internet Transmission Control Program.
• RFC677: Maintenance of duplicate databases.
• RFC678: Standard file formats.
• RFC679: February, 1975, survey of New-Protocol Telnet servers.
• RFC680: Message Transmission Protocol.
• RFC681: Network
• RFC684: Commentary on procedure calling as a network protocol.
• RFC685: Response time in cross network debugging.
• RFC686: Leaving well enough alone.
• RFC687: IMP/Host and Host/IMP Protocol changes.
• RFC688: Tentative schedule for the new Telnet implementation for the
• RFC689: Tenex NCP finite state machine for connections.
• RFC690: Comments on the proposed Host/IMP Protocol changes.
• RFC691: One more try on the
• RFC692: Comments on IMP/Host Protocol changes (RFCs 687 and 690).
• RFC694: Protocol information.
• RFC695: Official change in Host-Host Protocol.
• RFC696: Comments on the IMP/Host and Host/IMP Protocol changes.
• RFC697: CWD command of
• RFC698: Telnet extended ASCII option.
• RFC699: Request For Comments summary notes: 600-699.
• RFC700: Protocol experiment.
• RFC701: August, 1974, survey of New-Protocol Telnet servers.
• RFC702: September, 1974, survey of New-Protocol Telnet servers.
• RFC703: July, 1975, survey of New-Protocol Telnet Servers.
• RFC704: IMP/Host and Host/IMP Protocol change.
• RFC705: Front-end Protocol B6700 version.
• RFC706: On the junk mail problem.
• RFC707: High-level framework for network-based resource sharing.
• RFC708: Elements of a Distributed Programming System.
• RFC712: Distributed Capability Computing System (DCCS).
• RFC713: MSDTP-Message Services Data Transmission Protocol.
• RFC714: Host-Host Protocol for an ARPANET-Type Network.
• RFC716: Interim Revision to Appendix F of BBN 1822.
• RFC717: Assigned Network Numbers.
• RFC718: Comments on RCTE from the Tenex Implementation Experience.
• RFC719: Discussion on
• RFC720: Address Specification Syntax for Network Mail.
• RFC721: Out-of-Band Control Signals in a Host-to-Host Protocol.
• RFC722: Thoughts on Interactions in Distributed Services.
• RFC724: Proposed official standard for the format of ARPA Network messages.
• RFC725: RJE protocol for a resource sharing network.
• RFC726: Remote Controlled Transmission and Echoing Telnet option.
• RFC727: Telnet logout option.
• RFC728: Minor pitfall in the Telnet Protocol.
• RFC729: Telnet byte macro option.
• RFC730: Extensible field addressing.
• RFC731: Telnet Data Entry Terminal option.
• RFC732: Telnet Data Entry Terminal option.
• RFC733: Standard for the format of ARPA network text messages.
• RFC734: SUPDUP Protocol.
• RFC735: Revised Telnet byte macro option.
• RFC736: Telnet SUPDUP option.
• RFC737: FTP extension:
• RFC738: Time server.
• RFC739: Assigned numbers.
• RFC740: NETRJS Protocol.
• RFC741: Specifications for the Network Voice Protocol (NVP).
• RFC742: NAME/FINGER Protocol.
• RFC743: FTP extension: XRSQ/XRCP.
• RFC744: MARS - a Message Archiving and Retrieval Service.
• RFC745: JANUS interface specifications.
• RFC746: SUPDUP graphics extension.
• RFC747: Recent extensions to the SUPDUP Protocol.
• RFC748: Telnet randomly-lose option.
• RFC749: Telnet SUPDUP-Output option.
• RFC750: Assigned numbers.
• RFC751: Survey of FTP mail and
• RFC752: Universal host table.
• RFC753: Internet Message Protocol.
• RFC754: Out-of-net host addresses for mail.
• RFC755: Assigned numbers.
• RFC756: NIC name server - a datagram-based information utility.
• RFC758: Assigned numbers.
• RFC759: Internet Message Protocol.
• RFC760: DoD standard Internet Protocol.
• RFC761: DoD standard Transmission Control Protocol.
• RFC762: Assigned numbers.
• RFC763: Role mailboxes.
• RFC764: Telnet Protocol specification.
• RFC765: File Transfer Protocol specification.
• RFC766: Internet Protocol Handbook: Table of contents.
• RFC767: Structured format for transmission of multi-media documents.
• RFC768: User Datagram Protocol.
• RFC769: Rapicom 450 facsimile file format.
• RFC770: Assigned numbers.
• RFC771: Mail transition plan.
• RFC772: Mail Transfer Protocol.
• RFC773: Comments on NCP/TCP mail service transition strategy.
• RFC774: Internet Protocol Handbook: Table of contents.
• RFC776: Assigned numbers.
• RFC777: Internet Control Message Protocol.
• RFC778: DCNET Internet Clock Service.
• RFC779: Telnet send-location option.
• RFC780: Mail Transfer Protocol.
• RFC781: Specification of the Internet Protocol (IP) timestamp option.
• RFC782: Virtual Terminal management model.
• RFC783: TFTP Protocol (revision 2).
• RFC784: Mail Transfer Protocol: ISI TOPS20 implementation.
• RFC785: Mail Transfer Protocol: ISI TOPS20 file definitions.
• RFC786: Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface.
• RFC787: Connectionless data transmission survey/tutorial.
• RFC788: Simple Mail Transfer Protocol.
• RFC789: Vulnerabilities of network control protocols: An example.
• RFC790: Assigned numbers.
• RFC791: Internet Protocol.
• RFC792: Internet Control Message Protocol.
• RFC793: Transmission Control Protocol.
• RFC794: Pre-emption.
• RFC795: Service mappings.
• RFC796: Address mappings.
• RFC797: Format for Bitmap files.
• RFC798: Decoding facsimile data from the Rapicom 450.
• RFC799: Internet name domains.
• RFC800: Request For Comments summary notes: 700-799.
• RFC801: NCP/TCP transition plan.
• RFC802: ARPANET 1822L Host Access Protocol.
• RFC803: Dacom 450/500 facsimile data transcoding.
• RFC804: CCITT draft recommendation T.4. International Telegraph and Telephone Consultative Committee of the International Telecommunication Union.
• RFC805: Computer mail meeting notes.
• RFC807: Multimedia mail meeting notes.
• RFC808: Summary of computer mail services meeting held at BBN on 10 January 1979.
• RFC809: UCL facsimile system.
• RFC810: DoD Internet host table specification.
• RFC811: Hostnames Server.
• RFC812: NICNAME/WHOIS.
• RFC813: Window and Acknowledgement Strategy in
• RFC814: Name, addresses, ports, and routes.
• RFC815: IP datagram reassembly algorithms.
• RFC816: Fault isolation and recovery.
• RFC817: Modularity and efficiency in protocol implementation.
• RFC818: Remote User Telnet service.
• RFC819: Domain naming convention for Internet user applications.
• RFC820: Assigned numbers.
• RFC821: Simple Mail Transfer Protocol.
• RFC822: STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT
• RFC823: DARPA Internet gateway.
• RFC824: CRONUS Virtual Local Network.
• RFC825: Request for comments on Requests For Comments.
• RFC826: Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48.bit Ethernet address for transmission on Ethernet hardware. David
• RFC827: Exterior Gateway Protocol (EGP).
• RFC828: Data communications: IFIP's international "network" of experts.
• RFC829: Packet satellite technology reference sources.
• RFC830: Distributed system for Internet name service.
• RFC831: Backup access to the European side of
• RFC832: Who talks TCP?.
• RFC833: Who talks TCP?.
• RFC834: Who talks TCP?.
• RFC835: Who talks TCP?.
• RFC836: Who talks TCP?.
• RFC837: Who talks TCP?.
• RFC838: Who talks TCP?.
• RFC839: Who talks TCP?.
• RFC840: Official protocols.
• RFC842: Who talks TCP? - survey of 1 February 83.
• RFC843: Who talks TCP? - survey of 8 February 83.
• RFC844: Who talks ICMP, too? - Survey of 18 February 1983.
• RFC845: Who talks TCP? - survey of 15 February 1983.
• RFC846: Who talks TCP? - survey of 22 February 1983.
• RFC847: Summary of Smallberg surveys.
• RFC848: Who provides the "little" TCP services?.
• RFC849: Suggestions for improved host table distribution.
• RFC850: Standard for interchange of USENET messages.
• RFC851: ARPANET 1822L Host Access Protocol.
• RFC852: ARPANET short blocking feature.
• RFC854: Telnet Protocol Specification.
• RFC855: Telnet Option Specifications.
• RFC856: Telnet Binary Transmission.
• RFC857: Telnet Echo Option.
• RFC858: Telnet Suppress Go Ahead Option.
• RFC859: Telnet Status Option.
• RFC860: Telnet Timing Mark Option.
• RFC861: Telnet Extended Options: List Option.
• RFC862: Echo Protocol.
• RFC863: Discard Protocol.
• RFC864: Character Generator Protocol.
• RFC865: Quote of the Day Protocol.
• RFC866: Active users.
• RFC867: Daytime Protocol.
• RFC868: Time Protocol.
• RFC869: Host Monitoring Protocol.
• RFC870: Assigned numbers.
• RFC871: Perspective on the ARPANET reference model.
• RFC872: TCP-on-a-LAN.
• RFC873: Illusion of vendor support.
• RFC874: Critique of X.25.
• RFC875: Gateways, architectures, and heffalumps.
• RFC876: Survey of SMTP implementations.
• RFC877: Standard for the transmission of IP datagrams over public data networks.
• RFC878: ARPANET 1822L Host Access Protocol.
• RFC879: TCP maximum segment size and related topics.
• RFC880: Official protocols.
• RFC881: Domain names plan and schedule.
• RFC882: Domain names: Concepts and facilities.
• RFC883: Domain names: Implementation specification.
• RFC884: Telnet terminal type option.
• RFC885: Telnet end of record option.
• RFC886: Proposed standard for message header munging.
• RFC887: Resource Location Protocol.
• RFC888: "STUB" Exterior Gateway Protocol.
• RFC889: Internet delay experiments.
• RFC890: Exterior Gateway Protocol implementation schedule.
• RFC891: DCN Local-Network Protocols.
• RFC892: ISO Transport Protocol specification. International Organization for Standardization.
• RFC893: Trailer encapsulations.
• RFC894: Standard for the transmission of IP datagrams over Ethernet networks.
• RFC895: Standard for the transmission of IP datagrams over experimental Ethernet networks.
• RFC896: Congestion control in IP/TCP internetworks.
• RFC897: Domain name system implementation schedule.
• RFC898: Gateway special interest group meeting notes.
• RFC899: Request For Comments summary notes: 800-899.
• RFC900: Assigned Numbers.
• RFC901: Official ARPA-Internet protocols.
• RFC902: ARPA Internet Protocol policy.
• RFC903: A Reverse Address Resolution Protocol.
• RFC904: Exterior Gateway Protocol formal specification.
• RFC905: ISO Transport Protocol specification ISO DP 8073. ISO.
• RFC906: Bootstrap loading using
• RFC907: Host Access Protocol specification. Bolt Beranek and Newman Laboratories.
• RFC908: Reliable Data Protocol.
• RFC909: Loader Debugger Protocol.
• RFC910: Multimedia mail meeting notes.
• RFC911: EGP Gateway under Berkeley UNIX 4.2.
• RFC912: Authentication service.
• RFC913: Simple File Transfer Protocol.
• RFC914: Thinwire protocol for connecting personal computers to the Internet.
• RFC915: Network mail path service.
• RFC916: Reliable Asynchronous Transfer Protocol (RATP).
• RFC917: Internet subnets.
• RFC918: Post Office Protocol.
• RFC919: Broadcasting Internet Datagrams.
• RFC920: Domain requirements.
• RFC921: Domain name system implementation schedule - revised.
• RFC922: Broadcasting Internet datagrams in the presence of subnets.
• RFC923: Assigned numbers.
• RFC924: Official ARPA-Internet protocols for connecting personal computers to the Internet.
• RFC925: Multi-LAN address resolution.
• RFC926: Protocol for providing the connectionless mode network services. International Organization for Standardization.
• RFC927: TACACS user identification Telnet option.
• RFC928: Introduction to proposed DoD standard H-FP.
• RFC929: Proposed Host-Front End Protocol.
• RFC930: Telnet terminal type option.
• RFC931: Authentication server.
• RFC932: Subnetwork addressing scheme.
• RFC933: Output marking Telnet option.
• RFC934: Proposed standard for message encapsulation.
• RFC935: Reliable link layer protocols.
• RFC936: Another Internet subnet addressing scheme.
• RFC937: Post Office Protocol: Version 2.
• RFC938: Internet Reliable Transaction Protocol functional and interface specification.
• RFC939: Executive summary of the NRC report on transport protocols for Department of Defense data networks. National Research Council.
• RFC940: Toward an Internet standard scheme for subnetting. Gateway Algorithms and Data Structures Task Force.
• RFC941: Addendum to the network service definition covering network layer addressing. International Organization for Standardization.
• RFC942: Transport protocols for Department of Defense data networks. National Research Council.
• RFC943: Assigned numbers.
• RFC944: Official ARPA-Internet protocols.
• RFC945: DoD statement on the NRC report.
• RFC946: Telnet terminal location number option.
• RFC947: Multi-network broadcasting within the Internet.
• RFC948: Two methods for the transmission of IP datagrams over IEEE 802.3 networks.
• RFC949: FTP unique-named store command.
• RFC950: Internet Standard Subnetting Procedure.
• RFC951: Bootstrap Protocol.
• RFC952: DoD Internet host table specification.
• RFC953: Hostname Server.
• RFC954: NICNAME/WHOIS.
• RFC955: Towards a transport service for transaction processing applications.
• RFC956: Algorithms for synchronizing network clocks.
• RFC957: Experiments in network clock synchronization.
• RFC958: Network Time Protocol (NTP).
• RFC959: File Transfer Protocol.
• RFC960: Assigned numbers.
• RFC961: Official ARPA-Internet protocols.
• RFC962: TCP-4 prime.
• RFC963: Some problems with the specification of the Military Standard Internet Protocol.
• RFC964: Some problems with the specification of the Military Standard Transmission Control Protocol.
• RFC965: Format for a graphical communication protocol.
• RFC966: Host groups: A multicast extension to the Internet Protocol.
• RFC967: All victims together.
• RFC968: Twas the night before start-up.
• RFC969: NETBLT: A bulk data transfer protocol.
• RFC970: On packet switches with infinite storage.
• RFC971: Survey of data representation standards.
• RFC972: Password Generator Protocol.
• RFC973: Domain system changes and observations.
• RFC974: Mail routing and the domain system.
• RFC975: Autonomous confederations.
• RFC976: UUCP mail interchange format standard.
• RFC977: Network News Transfer Protocol.
• RFC978: Voice File Interchange Protocol (VFIP).
• RFC979: PSN End-to-End functional specification.
• RFC980: Protocol document order information.
• RFC981: Experimental multiple-path routing algorithm.
• RFC982: Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address.
• RFC983: ISO transport arrives on top of the
• RFC984: PCMAIL: A distributed mail system for personal computers.
• RFC985: Requirements for Internet gateways - draft. National Science Foundation, Network Technical Advisory Group.
• RFC986: Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol.
• RFC987: Mapping between X.400 and RFC 822.
• RFC988: Host extensions for IP multicasting.
• RFC990: Assigned numbers.
• RFC991: Official ARPA-Internet protocols.
• RFC992: On communication support for fault tolerant process groups.
• RFC993: PCMAIL: A distributed mail system for personal computers.
• RFC994: Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service. International Organization for Standardization.
• RFC995: End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473. International Organization for Standardization.
• RFC996: Statistics server.
• RFC997: Internet numbers.
• RFC998: NETBLT: A bulk data transfer protocol.
• RFC999: Requests For Comments summary notes: 900-999.
• RFC8401: Unknown