| RFC 300: ARPA Network mailing lists |
| RFC 301: BBN IMP (#5) and NCC Schedule March 4, 1971 |
| RFC 302: Exercising The ARPANET |
| RFC 303: ARPA Network mailing lists |
| RFC 304: Data management system proposal for the ARPA network |
| RFC 305: Unknown Host Numbers |
| RFC 306: Network host status |
| RFC 307: Using network Remote Job Entry |
| RFC 308: ARPANET host availability data |
| RFC 309: Data and File Transfer Workshop Announcement |
| RFC 310: Another Look at Data and File Transfer Protocols |
| RFC 311: New Console Attachments to the USCB Host |
| RFC 312: Proposed Change in IMP-to-Host Protocol |
| RFC 313: Computer based instruction |
| RFC 314: Network Graphics Working Group Meeting |
| RFC 315: Network Host Status |
| RFC 316: ARPA Network Data Management Working Group |
| RFC 317: Official Host-Host Protocol Modification: Assigned Link Numbers |
| RFC 318: Telnet Protocols |
| RFC 319: Network Host Status |
| RFC 320: Workshop on Hard Copy Line Printers |
| RFC 321: CBI Networking Activity at MITRE |
| RFC 322: Well known socket numbers |
| RFC 323: Formation of Network Measurement Group (NMG) |
| RFC 324: RJE Protocol meeting |
| RFC 325: Network Remote Job Entry program - NETRJS |
| RFC 326: Network Host Status |
| RFC 327: Data and File Transfer workshop notes |
| RFC 328: Suggested Telnet Protocol Changes |
| RFC 329: ARPA Network Mailing Lists |
| RFC 330: Network Host Status |
| RFC 331: IMP System Change Notification |
| RFC 332: Network Host Status |
| RFC 333: Proposed experiment with a Message Switching Protocol |
| RFC 334: Network Use on May 8 |
| RFC 335: New Interface - IMP/360 |
| RFC 336: Level 0 Graphic Input Protocol |
| RFC 338: EBCDIC/ASCII Mapping for Network RJE |
| RFC 339: MLTNET: A "Multi Telnet" Subsystem for Tenex |
| RFC 340: Proposed Telnet Changes |
| RFC 342: Network Host Status |
| RFC 343: IMP System change notification |
| RFC 344: Network Host Status |
| RFC 346: Satellite Considerations |
| RFC 347: Echo process |
| RFC 348: Discard Process |
| RFC 349: Proposed Standard Socket Numbers |
| RFC 350: User Accounts for UCSB On-Line System |
| RFC 352: TIP Site Information Form |
| RFC 353: Network host status |
| RFC 354: File Transfer Protocol |
| RFC 355: Response to NWG/RFC 346 |
| RFC 356: ARPA Network Control Center |
| RFC 357: Echoing strategy for satellite links |
| RFC 359: Status of the Release of the New IMP System (2600) |
| RFC 360: Proposed Remote Job Entry Protocol |
| RFC 361: Deamon Processes on Host 106 |
| RFC 362: Network Host Status |
| RFC 363: ARPA Network mailing lists |
| RFC 364: Serving remote users on the ARPANET |
| RFC 365: Letter to All TIP Users |
| RFC 366: Network Host Status |
| RFC 367: Network host status |
| RFC 368: Comments on "Proposed Remote Job Entry Protocol" |
| RFC 369: Evaluation of ARPANET services January-March, 1972 |
| RFC 370: Network Host Status |
| RFC 372: Notes on a Conversation with Bob Kahn on the ICCC |
| RFC 373: Arbitrary Character Sets |
| RFC 374: IMP System Announcement |
| RFC 376: Network Host Status |
| RFC 377: Using TSO via ARPA Network Virtual Terminal |
| RFC 378: Traffic statistics (July 1972) |
| RFC 379: Using TSO at CCN |
| RFC 381: Three aids to improved network operation |
| RFC 382: Mathematical Software on the ARPA Network |
| RFC 384: Official site idents for organizations in the ARPA Network |
| RFC 385: Comments on the File Transfer Protocol |
| RFC 386: Letter to TIP users-2 |
| RFC 388: NCP statistics |
| RFC 389: UCLA Campus Computing Network Liaison Staff for ARPA Network |
| RFC 390: TSO Scenario |
| RFC 391: Traffic statistics (August 1972) |
| RFC 392: Measurement of host costs for transmitting network data |
| RFC 393: Comments on Telnet Protocol Changes |
| RFC 394: Two Proposed Changes to the IMP-Host Protocol |
| RFC 395: Switch Settings on IMPs and TIPs |
| RFC 396: Network Graphics Working Group Meeting - Second Iteration |
| RFC 398: ICP Sockets |
| RFC 399: SMFS Login and Logout |