Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

Jump to content

Template:Ref RFC/db/5

From Wikipedia, the free encyclopedia
RFC Title Status Reference Notes
505 Two solutions to a file transfer access problem Status Unknown M. A. Padlipsky (25 June 1973). Two solutions to a file transfer access problem. Network Working Group. doi:10.17487/RFC0505. RFC 505. NIC 16156.
506 FTP command naming problem Status Unknown M. A. Padlipsky (26 June 1973). FTP command naming problem. Network Working Group. doi:10.17487/RFC0506. RFC 506. NIC 16157.
527 ARPAWOCKY Status Unknown D.L. Covill (22 June 1973). R. Merryman (ed.). ARPAWOCKY. Network Working Group. doi:10.17487/RFC0527. RFC 527.
531 Feast or famine? A response to two recent RFC's about network information Status Unknown M. A. Padlipsky (June 26, 1973). Feast or famine? A response to two recent RFC's about network information. Network Working Group. doi:10.17487/RFC0531. RFC 531. NIC 17450.
562 Modifications to the TELNET Specification Status Unknown A. McKenzie (28 August 1973). Modifications to the TELNET Specification. Network Working Group. doi:10.17487/RFC0562. RFC 562. NIC 18638.
569 NETED: A Common Editor for the ARPA Network Historic M. A. Padlipsky (October 15, 1973). NETED: A Common Editor for the ARPA Network. Network Working Group. doi:10.17487/RFC0569. RFC 569. NIC 18972.
590 MULTICS address change Status Unknown M. A. Padlipsky (19 November 1973). MULTICS address change. Network Working Group. doi:10.17487/RFC0590. RFC 590. NIC 20326.

← prev | next →