Internet RFC/STD/FYI/BCP Archives

# Active RFC Index

[ Index | Search | What's New | Comments | Help ]

Search the Archives
|  | Display RFC by number

- RFC 2913 - MIME Content Types in Media Feature Expressions
- RFC 2912 - Indicating Media Features for MIME Content
- RFC 2906 - AAA Authorization Requirements
- RFC 2905 - AAA Authorization Application Examples
- RFC 2904 - AAA Authorization Framework
- RFC 2903 - Generic AAA Architecture
- RFC 2901 - Guide to Administrative Procedures of the Internet Infrastructure
- RFC 2897 - Proposal for an MGCP Advanced Audio Package
- RFC 2896 - Remote Network Monitoring MIB Protocol Identifier Macros
- RFC 2895 - Remote Network Monitoring MIB Protocol Identifier Reference
- RFC 2894 - Router Renumbering for IPv6
- RFC 2893 - Transition Mechanisms for IPv6 Hosts and Routers
- RFC 2892 - The Cisco SRP MAC Layer Protocol
- RFC 2891 - LDAP Control Extension for Server Side Sorting of Search Results
- RFC 2890 - Key and Sequence Number Extensions to GRE
- RFC 2889 - Benchmarking Methodology for LAN Switching Devices
- RFC 2888 - Secure Remote Access with L2TP
- RFC 2887 - The Reliable Multicast Design Space for Bulk Data Transfer
- RFC 2886 - Megaco Errata
- RFC 2885 - Megaco Protocol 0.8
- RFC 2884 - Performance Evaluation of Explicit Congestion Notification (ECN) in IP Networks
- RFC 2883 - An Extension to the Selective Acknowledgement (SACK) Option for TCP
- RFC 2882 - Network Access Servers Requirements: Extended RADIUS Practices
- RFC 2881 - Network Access Server Requirements Next Generation (NASREQNG) NAS Model
- RFC 2880 - Internet Fax T.30 Feature Mapping
- RFC 2879 - Content Feature Schema for Internet Fax (V2)
- RFC 2878 - PPP Bridging Control Protocol (BCP)
- RFC 2877 - 5250 Telnet Enhancements
- RFC 2876 - Use of the KEA and SKIPJACK Algorithms in CMS
- RFC 2875 - Diffie-Hellman Proof-of-Possession Algorithms
- RFC 2874 - DNS Extensions to Support IPv6 Address Aggregation and Renumbering
- RFC 2873 - TCP Processing of the IPv4 Precedence Field
- RFC 2872 - Application and Sub Application Identity Policy Element for Use with RSVP
- RFC 2871 - A Framework for Telephony Routing over IP
- RFC 2870 - Root Name Server Operational Requirements
- RFC 2869 - RADIUS Extensions
- RFC 2868 - RADIUS Attributes for Tunnel Protocol Support
- RFC 2867 - RADIUS Accounting Modifications for Tunnel Protocol Support
- RFC 2866 - RADIUS Accounting
- RFC 2865 - Remote Authentication Dial In User Service (RADIUS)
- RFC 2864 - The Inverted Stack Table Extension to the Interfaces Group MIB
- RFC 2863 - The Interfaces Group MIB
- RFC 2862 - RTP Payload Format for Real-Time Pointers
- RFC 2861 - TCP Congestion Window Validation
- RFC 2860 - Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority
- RFC 2859 - A Time Sliding Window Three Colour Marker (TSWTCM)
- RFC 2858 - Multiprotocol Extensions for BGP-4
- RFC 2857 - The Use of HMAC-RIPEMD-160-96 within ESP and AH
- RFC 2856 - Textual Conventions for Additional High Capacity Data Types
- RFC 2855 - DHCP for IEEE 1394
- RFC 2854 - The 'text/html' Media Type
- RFC 2853 - Generic Security Service API Version 2 : Java Bindings
- RFC 2852 - Deliver By SMTP Service Extension
- RFC 2851 - Textual Conventions for Internet Network Addresses
- RFC 2850 - Charter of the Internet Architecture Board (IAB)
- RFC 2849 - The LDAP Data Interchange Format (LDIF) - Technical Specification
- RFC 2848 - The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services
- RFC 2847 - LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKM
- RFC 2846 - GSTN Address Element Extensions in E-mail Services
- RFC 2845 - Secret Key Transaction Authentication for DNS (TSIG)
- RFC 2844 - OSPF over ATM and Proxy-PAR
- RFC 2843 - Proxy-PAR
- RFC 2842 - Capabilities Advertisement with BGP-4
- RFC 2840 - TELNET KERMIT OPTION
- RFC 2839 - Internet Kermit Service
- RFC 2838 - Uniform Resource Identifiers for Television Broadcasts
- RFC 2837 - Definitions of Managed Objects for the Fabric Element in Fibre Channel Standard
- RFC 2836 - Per Hop Behavior Identification Codes
- RFC 2835 - IP and ARP over HIPPI-6400 (GSN)
- RFC 2834 - ARP and IP Broadcast over HIPPI-800
- RFC 2833 - RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
- RFC 2832 - NSI Registry Registrar Protocol (RRP) Version 1.1.0
- RFC 2831 - Using Digest Authentication as a SASL Mechanism
- RFC 2830 - Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security
- RFC 2829 - Authentication Methods for LDAP
- RFC 2828 - Internet Security Glossary
- RFC 2827 - Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
- RFC 2826 - IAB Technical Comment on the Unique DNS Root
- RFC 2825 - A Tangled Web: Issues of I18N, Domain Names, and the Other Internet protocols
- RFC 2824 - Call Processing Language Framework and Requirements
- RFC 2823 - PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like framing
- RFC 2820 - Access Control Requirements for LDAP
- RFC 2819 - Remote Network Monitoring Management Information Base
- RFC 2818 - HTTP Over TLS
- RFC 2817 - Upgrading to TLS Within HTTP/1.1
- RFC 2816 - A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies
- RFC 2815 - Integrated Service Mappings on IEEE 802 Networks
- RFC 2814 - SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networks
- RFC 2813 - Internet Relay Chat: Server Protocol
- RFC 2812 - Internet Relay Chat: Client Protocol
- RFC 2811 - Internet Relay Chat: Channel Management
- RFC 2810 - Internet Relay Chat: Architecture
- RFC 2809 - Implementation of L2TP Compulsory Tunneling via RADIUS
- RFC 2808 - The SecurID(r) SASL Mechanism
- RFC 2807 - XML Signature Requirements
- RFC 2806 - URLs for Telephone Calls
- RFC 2805 - Media Gateway Control Protocol Architecture and Requirements
- RFC 2804 - IETF Policy on Wiretapping
- RFC 2803 - Digest Values for DOM (DOMHASH)
- RFC 2802 - Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)
- RFC 2801 - Internet Open Trading Protocol - IOTP Version 1.0
- RFC 2798 - Definition of the inetOrgPerson LDAP Object Class
- RFC 2797 - Certificate Management Messages over CMS
- RFC 2796 - BGP Route Reflection - An Alternative to Full Mesh IBGP
- RFC 2795 - The Infinite Monkey Protocol Suite (IMPS)
- RFC 2794 - Mobile IP Network Access Identifier Extension for IPv4
- RFC 2793 - RTP Payload for Text Conversation
- RFC 2792 - DSA and RSA Key and Signature Encoding for the KeyNote Trust Management System
- RFC 2791 - Scalable Routing Design Principles
- RFC 2790 - Host Resources MIB
- RFC 2789 - Mail Monitoring MIB
- RFC 2788 - Network Services Monitoring MIB
- RFC 2787 - Definitions of Managed Objects for the Virtual Router Redundancy Protocol
- RFC 2786 - Diffie-Helman USM Key Management Information Base and Textual Convention
- RFC 2785 - Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for
- RFC 2784 - Generic Routing Encapsulation (GRE)
- RFC 2783 - Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0
- RFC 2782 - A DNS RR for specifying the location of services (DNS SRV)
- RFC 2781 - UTF-16, an encoding of ISO 10646
- RFC 2780 - IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
- RFC 2779 - Instant Messaging / Presence Protocol Requirements
- RFC 2778 - A Model for Presence and Instant Messaging
- RFC 2777 - Publicly Verifiable Nomcom Random Selection
- RFC 2776 - Multicast-Scope Zone Announcement Protocol (MZAP)
- RFC 2775 - Internet Transparency
- RFC 2774 - An HTTP Extension Framework
- RFC 2773 - Encryption using KEA and SKIPJACK
- RFC 2772 - 6Bone Backbone Routing Guidelines
- RFC 2771 - An Abstract API for Multicast Address Allocation
- RFC 2770 - GLOP Addressing in 233/8
- RFC 2769 - Routing Policy System Replication
- RFC 2768 - Network Policy and Services: A Report of a Workshop on Middleware
- RFC 2767 - Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)
- RFC 2766 - Network Address Translation - Protocol Translation (NAT-PT)
- RFC 2765 - Stateless IP/ICMP Translation Algorithm (SIIT)
- RFC 2764 - A Framework for IP Based Virtual Private Networks
- RFC 2763 - Dynamic Hostname Exchange Mechanism for IS-IS
- RFC 2762 - Sampling of the Group Membership in RTP
- RFC 2761 - Terminology for ATM Benchmarking
- RFC 2760 - Ongoing TCP Research Related to Satellites
- RFC 2759 - Microsoft PPP CHAP Extensions, Version 2
- RFC 2758 - Definitions of Managed Objects for Service Level Agreements Performance Monitoring
- RFC 2757 - Long Thin Networks
- RFC 2756 - Hyper Text Caching Protocol (HTCP/0.0)
- RFC 2755 - Security Negotiation for WebNFS
- RFC 2754 - RPS IANA Issues
- RFC 2753 - A Framework for Policy-based Admission Control
- RFC 2752 - Identity Representation for RSVP
- RFC 2751 - Signaled Preemption Priority Policy Element
- RFC 2750 - RSVP Extensions for Policy Control
- RFC 2749 - COPS usage for RSVP
- RFC 2748 - The COPS (Common Open Policy Service) Protocol
- RFC 2747 - RSVP Cryptographic Authentication
- RFC 2746 - RSVP Operation Over IP Tunnels
- RFC 2745 - RSVP Diagnostic Messages
- RFC 2744 - Generic Security Service API Version 2 : C-bindings
- RFC 2743 - Generic Security Service Application Program Interface Version 2, Update 1
- RFC 2742 - Definitions of Managed Objects for Extensible SNMP Agents
- RFC 2741 - Agent Extensibility (AgentX) Protocol Version 1
- RFC 2740 - OSPF for IPv6
- RFC 2739 - Calendar Attributes for vCard and LDAP
- RFC 2738 - Corrections to "A Syntax for Describing Media Feature Sets"
- RFC 2737 - Entity MIB (Version 2)
- RFC 2736 - Guidelines for Writers of RTP Payload Format Specifications
- RFC 2735 - NHRP Support for Virtual Private Networks
- RFC 2734 - IPv4 over IEEE 1394
- RFC 2733 - An RTP Payload Format for Generic Forward Error Correction
- RFC 2732 - Format for Literal IPv6 Addresses in URL's
- RFC 2731 - Encoding Dublin Core Metadata in HTML
- RFC 2730 - Multicast Address Dynamic Client Allocation Protocol (MADCAP)
- RFC 2729 - Taxonomy of Communication Requirements for Large-scale Multicast Applications
- RFC 2728 - The Transmission of IP Over the Vertical Blanking Interval of a Television Signal
- RFC 2727 - IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees
- RFC 2726 - PGP Authentication for RIPE Database Updates
- RFC 2725 - Routing Policy System Security
- RFC 2724 - RTFM: New Attributes for Traffic Flow Measurement
- RFC 2723 - SRL: A Language for Describing Traffic Flows and Specifying Actions for Flow Groups
- RFC 2722 - Traffic Flow Measurement: Architecture
- RFC 2721 - RTFM: Applicability Statement
- RFC 2720 - Traffic Flow Measurement: Meter MIB
- RFC 2719 - Framework Architecture for Signaling Transport
- RFC 2718 - Guidelines for new URL Schemes
- RFC 2717 - Registration Procedures for URL Scheme Names
- RFC 2716 - PPP EAP TLS Authentication Protocol
- RFC 2715 - Interoperability Rules for Multicast Routing Protocols
- RFC 2714 - Schema for Representing CORBA Object References in an LDAP Directory
- RFC 2713 - Schema for Representing Java(tm) Objects in an LDAP Directory
- RFC 2712 - Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)
- RFC 2711 - IPv6 Router Alert Option
- RFC 2710 - Multicast Listener Discovery (MLD) for IPv6
- RFC 2709 - Security Model with Tunnel-mode IPsec for NAT Domains
- RFC 2708 - Job Submission Protocol Mapping Recommendations for the Job Monitoring MIB
- RFC 2707 - Job Monitoring MIB - V1.0
- RFC 2706 - ECML v1: Field Names for E-Commerce
- RFC 2705 - Media Gateway Control Protocol (MGCP) Version 1.0
- RFC 2704 - The KeyNote Trust-Management System Version 2
- RFC 2703 - Protocol-independent Content Negotiation Framework
- RFC 2702 - Requirements for Traffic Engineering Over MPLS
- RFC 2701 - Nortel Networks Multi-link Multi-node PPP Bundle Discovery Protocol
- RFC 2700 - Internet Official Protocol Standards
- RFC 2699 - Request for Comments Summary RFC Numbers 2600-2699
- RFC 2698 - A Two Rate Three Color Marker
- RFC 2697 - A Single Rate Three Color Marker
- RFC 2696 - LDAP Control Extension for Simple Paged Results Manipulation
- RFC 2695 - Authentication Mechanisms for ONC RPC
- RFC 2694 - DNS extensions to Network Address Translators (DNS_ALG)
- RFC 2693 - SPKI Certificate Theory
- RFC 2692 - SPKI Requirements
- RFC 2691 - A Memorandum of Understanding for an ICANN Protocol Support Organization
- RFC 2690 - A Proposal for an MOU-Based ICANN Protocol Support Organization
- RFC 2689 - Providing Integrated Services over Low-bitrate Links
- RFC 2688 - Integrated Services Mappings for Low Speed Networks
- RFC 2687 - PPP in a Real-time Oriented HDLC-like Framing
- RFC 2686 - The Multi-Class Extension to Multi-Link PPP
- RFC 2685 - Virtual Private Networks Identifier
- RFC 2684 - Multiprotocol Encapsulation over ATM Adaptation Layer 5
- RFC 2683 - IMAP4 Implementation Recommendations
- RFC 2682 - Performance Issues in VC-Merge Capable ATM LSRs
- RFC 2681 - A Round-trip Delay Metric for IPPM
- RFC 2680 - A One-way Packet Loss Metric for IPPM
- RFC 2679 - A One-way Delay Metric for IPPM
- RFC 2678 - IPPM Metrics for Measuring Connectivity
- RFC 2677 - Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)
- RFC 2676 - QoS Routing Mechanisms and OSPF Extensions
- RFC 2675 - IPv6 Jumbograms
- RFC 2674 - Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions
- RFC 2673 - Binary Labels in the Domain Name System
- RFC 2672 - Non-Terminal DNS Name Redirection
- RFC 2671 - Extension Mechanisms for DNS (EDNS0)
- RFC 2670 - Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces
- RFC 2669 - DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems
- RFC 2668 - Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
- RFC 2667 - IP Tunnel MIB
- RFC 2666 - Definitions of Object Identifiers for Identifying Ethernet Chip Sets
- RFC 2665 - Definitions of Managed Objects for the Ethernet-like Interface Types
- RFC 2664 - FYI on Questions and Answers - Answers to Commonly Asked "New Internet User" Questions
- RFC 2663 - IP Network Address Translator (NAT) Terminology and Considerations
- RFC 2662 - Definitions of Managed Objects for the ADSL Lines
- RFC 2661 - Layer Two Tunneling Protocol "L2TP"
- RFC 2660 - The Secure HyperText Transfer Protocol
- RFC 2659 - Security Extensions For HTML
- RFC 2658 - RTP Payload Format for PureVoice(tm) Audio
- RFC 2657 - LDAPv2 Client vs
- RFC 2656 - Registration Procedures for SOIF Template Types
- RFC 2655 - CIP Index Object Format for SOIF Objects
- RFC 2654 - A Tagged Index Object for use in the Common Indexing Protocol
- RFC 2653 - CIP Transport Protocols
- RFC 2652 - MIME Object Definitions for the Common Indexing Protocol (CIP)
- RFC 2651 - The Architecture of the Common Indexing Protocol (CIP)
- RFC 2650 - Using RPSL in Practice
- RFC 2649 - An LDAP Control and Schema for Holding Operation Signatures
- RFC 2648 - A URN Namespace for IETF Documents
- RFC 2647 - Benchmarking Terminology for Firewall Performance
- RFC 2646 - The Text/Plain Format Parameter
- RFC 2645 - ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP Addresses
- RFC 2644 - Changing the Default for Directed Broadcasts in Routers
- RFC 2643 - Cabletron's SecureFast VLAN Operational Model
- RFC 2642 - Cabletron's VLS Protocol Specification
- RFC 2641 - Cabletron's VlanHello Protocol Specification Version 4
- RFC 2640 - Internationalization of the File Transfer Protocol
- RFC 2639 - Internet Printing Protocol/1.0: Implementer's Guide
- RFC 2638 - A Two-bit Differentiated Services Architecture for the Internet
- RFC 2637 - Point-to-Point Tunneling Protocol
- RFC 2636 - Wireless Device Configuration (OTASP/OTAPA) via ACAP
- RFC 2635 - DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings (spam*)
- RFC 2634 - Enhanced Security Services for S/MIME
- RFC 2633 - S/MIME Version 3 Message Specification
- RFC 2632 - S/MIME Version 3 Certificate Handling
- RFC 2631 - Diffie-Hellman Key Agreement Method
- RFC 2630 - Cryptographic Message Syntax
- RFC 2629 - Writing I-Ds and RFCs using XML
- RFC 2628 - Simple Cryptographic Program Interface (Crypto API)
- RFC 2627 - Key Management for Multicast: Issues and Architectures
- RFC 2626 - The Internet and the Millennium Problem (Year 2000)
- RFC 2625 - IP and ARP over Fibre Channel
- RFC 2624 - NFS Version 4 Design Considerations
- RFC 2623 - NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5
- RFC 2622 - Routing Policy Specification Language (RPSL
- RFC 2621 - RADIUS Accounting Server MIB
- RFC 2620 - RADIUS Accounting Client MIB
- RFC 2619 - RADIUS Authentication Server MIB
- RFC 2618 - RADIUS Authentication Client MIB
- RFC 2617 - HTTP Authentication: Basic and Digest Access Authentication
- RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1
- RFC 2615 - PPP over SONET/SDH
- RFC 2614 - An API for Service Location
- RFC 2613 - Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0
- RFC 2612 - The CAST-256 Encryption Algorithm
- RFC 2611 - URN Namespace Definition Mechanisms
- RFC 2610 - DHCP Options for Service Location Protocol
- RFC 2609 - Service Templates and Service: Schemes
- RFC 2608 - Service Location Protocol, Version 2
- RFC 2607 - Proxy Chaining and Policy Implementation in Roaming
- RFC 2606 - Reserved Top Level DNS Names
- RFC 2605 - Directory Server Monitoring MIB
- RFC 2603 - ILMI-Based Server Discovery for NHRP
- RFC 2602 - ILMI-Based Server Discovery for MARS
- RFC 2601 - ILMI-Based Server Discovery for ATMARP
- RFC 2600 - Internet Official Protocol Standards
- RFC 2599 - Request for Comments Summary RFC Numbers 2500-2599
- RFC 2598 - An Expedited Forwarding PHB
- RFC 2597 - Assured Forwarding PHB Group
- RFC 2596 - Use of Language Codes in LDAP
- RFC 2595 - Using TLS with IMAP, POP3 and ACAP
- RFC 2594 - Definitions of Managed Objects for WWW Services
- RFC 2593 - Script MIB Extensibility Protocol Version 1.0
- RFC 2592 - Definitions of Managed Objects for the Delegation of Management Script
- RFC 2591 - Definitions of Managed Objects for Scheduling Management Operations
- RFC 2590 - Transmission of IPv6 Packets over Frame Relay
- RFC 2589 - Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services
- RFC 2588 - IP Multicast and Firewalls
- RFC 2587 - Internet X.509 Public Key Infrastructure LDAPv2 Schema
- RFC 2586 - The Audio/L16 MIME content type
- RFC 2585 - Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP
- RFC 2584 - Definitions of Managed Objects for APPN/HPR in IP Networks
- RFC 2583 - Guidelines for Next Hop Client (NHC) Developers
- RFC 2582 - The NewReno Modification to TCP's Fast Recovery Algorithm
- RFC 2581 - TCP Congestion Control
- RFC 2580 - Conformance Statements for SMIv2
- RFC 2579 - Textual Conventions for SMIv2
- RFC 2578 - Structure of Management Information Version 2 (SMIv2)
- RFC 2577 - FTP Security Considerations
- RFC 2576 - Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework
- RFC 2575 - View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
- RFC 2574 - User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)
- RFC 2573 - SNMP Applications
- RFC 2572 - Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)
- RFC 2571 - An Architecture for Describing SNMP Management Frameworks
- RFC 2570 - Introduction to Version 3 of the Internet-standard Network Management Framework
- RFC 2569 - Mapping between LPD and IPP Protocols
- RFC 2568 - Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol
- RFC 2567 - Design Goals for an Internet Printing Protocol
- RFC 2566 - Internet Printing Protocol/1.0: Model and Semantics
- RFC 2565 - Internet Printing Protocol/1.0: Encoding and Transport
- RFC 2564 - Application Management MIB
- RFC 2563 - DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients
- RFC 2562 - Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)
- RFC 2561 - Base Definitions of Managed Objects for TN3270E Using SMIv2
- RFC 2560 - X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
- RFC 2559 - Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2
- RFC 2558 - Definitions of Managed Objects for the SONET/SDH Interface Type
- RFC 2557 - MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)
- RFC 2556 - OSI connectionless transport services on top of UDP Applicability Statement for Historic Status
- RFC 2555 - 30 Years of RFCs
- RFC 2554 - SMTP Service Extension for Authentication
- RFC 2553 - Basic Socket Interface Extensions for IPv6
- RFC 2552 - Architecture for the Information Brokerage in the ACTS Project GAIA
- RFC 2551 - The Roman Standards Process -- Revision III
- RFC 2550 - Y10K and Beyond
- RFC 2549 - IP over Avian Carriers with Quality of Service
- RFC 2548 - Microsoft Vendor-specific RADIUS Attributes
- RFC 2547 - BGP/MPLS VPNs
- RFC 2545 - Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
- RFC 2544 - Benchmarking Methodology for Network Interconnect Devices
- RFC 2543 - SIP: Session Initiation Protocol
- RFC 2542 - Terminology and Goals for Internet Fax
- RFC 2541 - DNS Security Operational Considerations
- RFC 2540 - Detached Domain Name System (DNS) Information
- RFC 2539 - Storage of Diffie-Hellman Keys in the Domain Name System (DNS)
- RFC 2538 - Storing Certificates in the Domain Name System (DNS)
- RFC 2537 - RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)
- RFC 2536 - DSA KEYs and SIGs in the Domain Name System (DNS)
- RFC 2535 - Domain Name System Security Extensions
- RFC 2534 - Media Features for Display, Print, and Fax
- RFC 2533 - A Syntax for Describing Media Feature Sets
- RFC 2532 - Extended Facsimile Using Internet Mail
- RFC 2530 - Indicating Supported Media Features Using Extensions to DSN and MDN
- RFC 2529 - Transmission of IPv6 over IPv4 Domains without Explicit Tunnels
- RFC 2528 - Internet X.509 Public Key Infrastructure Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure Certificates
- RFC 2527 - Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework
- RFC 2526 - Reserved IPv6 Subnet Anycast Addresses
- RFC 2525 - Known TCP Implementation Problems
- RFC 2524 - Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1.3
- RFC 2523 - Photuris: Extended Schemes and Attributes
- RFC 2522 - Photuris: Session-Key Management Protocol
- RFC 2521 - ICMP Security Failures Messages
- RFC 2520 - NHRP with Mobile NHCs
- RFC 2519 - A Framework for Inter-Domain Route Aggregation
- RFC 2518 - HTTP Extensions for Distributed Authoring -- WEBDAV
- RFC 2517 - Building Directories from DNS: Experiences from WWWSeeker
- RFC 2516 - Method for Transmitting PPP Over Ethernet (PPPoE)
- RFC 2515 - Definitions of Managed Objects for ATM Management
- RFC 2514 - Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management
- RFC 2513 - Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks
- RFC 2512 - Accounting Information for ATM Networks
- RFC 2511 - Internet X.509 Certificate Request Message Format
- RFC 2510 - Internet X.509 Public Key Infrastructure Certificate Management Protocols
- RFC 2509 - IP Header Compression over PPP
- RFC 2508 - Compressing IP/UDP/RTP Headers for Low-Speed Serial Links
- RFC 2507 - IP Header Compression
- RFC 2506 - Media Feature Tag Registration Procedure
- RFC 2505 - Anti-Spam Recommendations for SMTP MTAs
- RFC 2504 - Users' Security Handbook
- RFC 2503 - MIME Types for Use with the ISO ILL Protocol
- RFC 2502 - Limitations of Internet Protocol Suite for Distributed Simulation the Large Multicast Environment
- RFC 2501 - Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation Considerations
- RFC 2499 - Request for Comments Summary
- RFC 2497 - Transmission of IPv6 Packets over ARCnet Networks
- RFC 2496 - Definitions of Managed Object for the DS3/E3 Interface Type
- RFC 2495 - Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types
- RFC 2494 - Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type
- RFC 2493 - Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
- RFC 2492 - IPv6 over ATM Networks
- RFC 2491 - IPv6 over Non-Broadcast Multiple Access (NBMA) networks
- RFC 2490 - A Simulation Model for IP Multicast with RSVP
- RFC 2489 - Procedure for Defining New DHCP Options
- RFC 2488 - Enhancing TCP Over Satellite Channels using Standard Mechanisms
- RFC 2487 - SMTP Service Extension for Secure SMTP over TLS
- RFC 2486 - The Network Access Identifier
- RFC 2485 - DHCP Option for The Open Group's User Authentication Protocol
- RFC 2484 - PPP LCP Internationalization Configuration Option
- RFC 2483 - URI Resolution Services Necessary for URN Resolution
- RFC 2482 - Language Tagging in Unicode Plain Text
- RFC 2481 - A Proposal to add Explicit Congestion Notification (ECN) to IP
- RFC 2480 - Gateways and MIME Security Multiparts
- RFC 2479 - Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API)
- RFC 2478 - The Simple and Protected GSS-API Negotiation Mechanism
- RFC 2477 - Criteria for Evaluating Roaming Protocols
- RFC 2476 - Message Submission
- RFC 2475 - An Architecture for Differentiated Service
- RFC 2474 - Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
- RFC 2473 - Generic Packet Tunneling in IPv6 Specification
- RFC 2472 - IP Version 6 over PPP
- RFC 2471 - IPv6 Testing Address Allocation
- RFC 2470 - Transmission of IPv6 Packets over Token Ring Networks
- RFC 2469 - A Caution On The Canonical Ordering Of Link-Layer Addresses
- RFC 2468 - I REMEMBER IANA
- RFC 2467 - Transmission of IPv6 Packets over FDDI Networks
- RFC 2466 - Management Information Base for IP Version 6: ICMPv6 Group
- RFC 2465 - Management Information Base for IP Version 6: Textual Conventions and General Group
- RFC 2464 - Transmission of IPv6 Packets over Ethernet Networks
- RFC 2463 - Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
- RFC 2462 - IPv6 Stateless Address Autoconfiguration
- RFC 2461 - Neighbor Discovery for IP Version 6 (IPv6)
- RFC 2460 - Internet Protocol, Version 6 (IPv6) Specification
- RFC 2459 - Internet X.509 Public Key Infrastructure Certificate and CRL Profile
- RFC 2458 - Toward the PSTN/Internet Inter-Networking--Pre-PINT Implementations
- RFC 2457 - Definitions of Managed Objects for Extended Border Node
- RFC 2456 - Definitions of Managed Objects for APPN TRAPS
- RFC 2455 - Definitions of Managed Objects for APPN
- RFC 2454 - IP Version 6 Management Information Base for the User Datagram Protocol
- RFC 2453 - RIP Version 2
- RFC 2452 - IP Version 6 Management Information Base for the Transmission Control Protocol
- RFC 2451 - The ESP CBC-Mode Cipher Algorithms
- RFC 2450 - Proposed TLA and NLA Assignment Rule
- RFC 2449 - POP3 Extension Mechanism
- RFC 2448 - AT&T's Error Resilient Video Transmission Technique
- RFC 2447 - iCalendar Message-Based Interoperability Protocol (iMIP)
- RFC 2446 - iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries
- RFC 2445 - Internet Calendaring and Scheduling Core Object Specification (iCalendar)
- RFC 2444 - The One-Time-Password SASL Mechanism
- RFC 2443 - A Distributed MARS Service Using SCSP
- RFC 2442 - The Batch SMTP Media Type
- RFC 2441 - Working with Jon, Tribute delivered at UCLA, October 30, 1998
- RFC 2440 - OpenPGP Message Format
- RFC 2439 - BGP Route Flap Damping
- RFC 2438 - Advancement of MIB specifications on the IETF Standards Track
- RFC 2437 - PKCS #1: RSA Cryptography Specifications Version 2.0
- RFC 2436 - Collaboration between ISOC/IETF and ITU-T
- RFC 2435 - RTP Payload Format for JPEG-compressed Video
- RFC 2434 - Guidelines for Writing an IANA Considerations Section in RFCs
- RFC 2433 - Microsoft PPP CHAP Extensions
- RFC 2432 - Terminology for IP Multicast Benchmarking
- RFC 2431 - RTP Payload Format for BT.656 Video Encoding
- RFC 2430 - A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)
- RFC 2429 - RTP Payload Format for the 1998 Version of ITU-T Rec
- RFC 2428 - FTP Extensions for IPv6 and NATs
- RFC 2427 - Multiprotocol Interconnect over Frame Relay
- RFC 2426 - vCard MIME Directory Profile
- RFC 2425 - A MIME Content-Type for Directory Information
- RFC 2424 - Content Duration MIME Header Definition
- RFC 2423 - VPIM Voice Message MIME Sub-type Registration
- RFC 2422 - Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration
- RFC 2421 - Voice Profile for Internet Mail - version 2
- RFC 2420 - The PPP Triple-DES Encryption Protocol (3DESE)
- RFC 2419 - The PPP DES Encryption Protocol, Version 2 (DESE-bis)
- RFC 2418 - IETF Working Group Guidelines and Procedures
- RFC 2417 - Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks
- RFC 2416 - When TCP Starts Up With Four Packets Into Only Three Buffers
- RFC 2415 - Simulation Studies of Increased Initial TCP Window Size
- RFC 2414 - Increasing TCP's Initial Window
- RFC 2413 - Dublin Core Metadata for Resource Discovery
- RFC 2412 - The OAKLEY Key Determination Protocol
- RFC 2411 - IP Security Document Roadmap
- RFC 2410 - The NULL Encryption Algorithm and Its Use With IPsec
- RFC 2409 - The Internet Key Exchange (IKE)
- RFC 2408 - Internet Security Association and Key Management Protocol (ISAKMP)
- RFC 2407 - The Internet IP Security Domain of Interpretation for ISAKMP
- RFC 2406 - IP Encapsulating Security Payload (ESP)
- RFC 2405 - The ESP DES-CBC Cipher Algorithm With Explicit IV
- RFC 2404 - The Use of HMAC-SHA-1-96 within ESP and AH
- RFC 2403 - The Use of HMAC-MD5-96 within ESP and AH
- RFC 2402 - IP Authentication Header
- RFC 2401 - Security Architecture for the Internet Protocol
- RFC 2399 - Request for Comments Summary
- RFC 2398 - Some Testing Tools for TCP Implementors
- RFC 2397 - The "data" URL scheme
- RFC 2396 - Uniform Resource Identifiers (URI): Generic Syntax
- RFC 2395 - IP Payload Compression Using LZS
- RFC 2394 - IP Payload Compression Using DEFLATE
- RFC 2393 - IP Payload Compression Protocol (IPComp)
- RFC 2392 - Content-ID and Message-ID Uniform Resource Locators
- RFC 2391 - Load Sharing using IP Network Address Translation (LSNAT)
- RFC 2390 - Inverse Address Resolution Protocol
- RFC 2389 - Feature negotiation mechanism for the File Transfer Protocol
- RFC 2388 - Returning Values from Forms: multipart/form-data
- RFC 2387 - The MIME Multipart/Related Content-type
- RFC 2386 - A Framework for QoS-based Routing in the Internet
- RFC 2385 - Protection of BGP Sessions via the TCP MD5 Signature Option
- RFC 2384 - POP URL Scheme
- RFC 2383 - ST2+ over ATM Protocol Specification - UNI 3.1 Version
- RFC 2382 - A Framework for Integrated Services and RSVP over ATM
- RFC 2381 - Interoperation of Controlled-Load Service and Guaranteed Service with ATM
- RFC 2380 - RSVP over ATM Implementation Requirements
- RFC 2379 - RSVP over ATM Implementation Guidelines
- RFC 2378 - The CCSO Nameserver (Ph) Architecture
- RFC 2377 - Naming Plan for Internet Directory-Enabled Applications
- RFC 2376 - XML Media Types
- RFC 2375 - IPv6 Multicast Address Assignments
- RFC 2374 - An IPv6 Aggregatable Global Unicast Address Format
- RFC 2373 - IP Version 6 Addressing Architecture
- RFC 2372 - Transaction Internet Protocol - Requirements and Supplemental Information
- RFC 2371 - Transaction Internet Protocol Version 3.0
- RFC 2370 - The OSPF Opaque LSA Option
- RFC 2369 - The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields
- RFC 2368 - The mailto URL scheme
- RFC 2367 - PF_KEY Key Management API, Version 2
- RFC 2365 - Administratively Scoped IP Multicast
- RFC 2364 - PPP Over AAL5
- RFC 2363 - PPP Over FUNI
- RFC 2362 - Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification
- RFC 2361 - WAVE and AVI Codec Registries
- RFC 2360 - Guide for Internet Standards Writers
- RFC 2359 - IMAP4 UIDPLUS extension
- RFC 2357 - IETF Criteria for Evaluating Reliable Multicast Transport and Application Protocols
- RFC 2356 - Sun's SKIP Firewall Traversal for Mobile IP
- RFC 2355 - TN3270 Enhancements
- RFC 2354 - Options for Repair of Streaming Media
- RFC 2353 - APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages Document
- RFC 2352 - A Convention For Using Legal Names as Domain Names
- RFC 2351 - Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP
- RFC 2350 - Expectations for Computer Security Incident Response
- RFC 2349 - TFTP Timeout Interval and Transfer Size Options
- RFC 2348 - TFTP Blocksize Option
- RFC 2347 - TFTP Option Extension
- RFC 2346 - Making Postscript and PDF International
- RFC 2345 - Domain Names and Company Name Retrieval
- RFC 2344 - Reverse Tunneling for Mobile IP
- RFC 2343 - RTP Payload Format for Bundled MPEG
- RFC 2342 - IMAP4 Namespace
- RFC 2341 - Cisco Layer Two Forwarding (Protocol) "L2F"
- RFC 2340 - Nortel's Virtual Network Switching (VNS) Overview
- RFC 2339 - An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc
- RFC 2338 - Virtual Router Redundancy Protocol
- RFC 2337 - Intra-LIS IP multicast among routers over ATM using Sparse Mode PIM
- RFC 2336 - Classical IP to NHRP Transition
- RFC 2335 - A Distributed NHRP Service Using SCSP
- RFC 2334 - Server Cache Synchronization Protocol (SCSP)
- RFC 2333 - NHRP Protocol Applicability Statement
- RFC 2332 - NBMA Next Hop Resolution Protocol (NHRP)
- RFC 2331 - ATM Signalling Support for IP over ATM - UNI Signalling 4.0 Update
- RFC 2330 - Framework for IP Performance Metrics
- RFC 2329 - OSPF Standardization Report
- RFC 2328 - OSPF Version 2
- RFC 2327 - SDP: Session Description Protocol
- RFC 2326 - Real Time Streaming Protocol (RTSP)
- RFC 2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
- RFC 2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
- RFC 2323 - IETF Identification and Security Guidelines
- RFC 2322 - Management of IP numbers by peg-dhcp
- RFC 2321 - RITA -- The Reliable Internetwork Troubleshooting Agent
- RFC 2320 - Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB)
- RFC 2319 - Ukrainian Character Set KOI8-U
- RFC 2318 - The text/css Media Type
- RFC 2317 - Classless IN-ADDR.ARPA delegation
- RFC 2316 - Report of the IAB Security Architecture Workshop
- RFC 2315 - PKCS 7: Cryptographic Message Syntax Version 1.5
- RFC 2314 - PKCS 10: Certification Request Syntax Version 1.5
- RFC 2312 - S/MIME Version 2 Certificate Handling
- RFC 2311 - S/MIME Version 2 Message Specification
- RFC 2310 - The Safe Response Header Field
- RFC 2309 - Recommendations on Queue Management and Congestion Avoidance in the Internet
- RFC 2308 - Negative Caching of DNS Queries (DNS NCACHE)
- RFC 2307 - An Approach for Using LDAP as a Network Information Service
- RFC 2306 - Tag Image File Format (TIFF) - F Profile for Facsimile
- RFC 2305 - A Simple Mode of Facsimile Using Internet Mail
- RFC 2304 - Minimal FAX address format in Internet Mail
- RFC 2303 - Minimal PSTN address format in Internet Mail
- RFC 2302 - Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration
- RFC 2301 - File Format for Internet Fax
- RFC 2299 - Request for Comments Summary
- RFC 2298 - An Extensible Message Format for Message Disposition Notifications
- RFC 2297 - Ipsilon's General Switch Management Protocol Specification Version 2.0
- RFC 2296 - HTTP Remote Variant Selection Algorithm -- RVSA/1.0
- RFC 2295 - Transparent Content Negotiation in HTTP
- RFC 2294 - Representing the O/R Address hierarchy in the X.500 Directory Information Tree
- RFC 2293 - Representing Tables and Subtrees in the X.500 Directory
- RFC 2292 - Advanced Sockets API for IPv6
- RFC 2291 - Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web
- RFC 2290 - Mobile-IPv4 Configuration Option for PPP IPCP
- RFC 2289 - A One-Time Password System
- RFC 2288 - Using Existing Bibliographic Identifiers as Uniform Resource Names
- RFC 2287 - Definitions of System-Level Managed Objects for Applications
- RFC 2286 - Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128
- RFC 2285 - Benchmarking Terminology for LAN Switching Devices
- RFC 2284 - PPP Extensible Authentication Protocol (EAP)
- RFC 2281 - Cisco Hot Standby Router Protocol (HSRP)
- RFC 2279 - UTF-8, a transformation format of ISO 10646
- RFC 2278 - IANA Charset Registration Procedures
- RFC 2277 - IETF Policy on Character Sets and Languages
- RFC 2276 - Architectural Principles of Uniform Resource Name Resolution
- RFC 2270 - Using a Dedicated AS for Sites Homed to a Single Provider
- RFC 2269 - Using the MARS Model in non-ATM NBMA Networks
- RFC 2268 - A Description of the RC2(r) Encryption Algorithm
- RFC 2266 - Definitions of Managed Objects for IEEE 802.12 Repeater Devices
- RFC 2260 - Scalable Support for Multi-homed Multi-provider Connectivity
- RFC 2259 - Simple Nomenclator Query Protocol (SNQP)
- RFC 2258 - Internet Nomenclator Project
- RFC 2256 - A Summary of the X.500(96) User Schema for use with LDAPv3
- RFC 2255 - The LDAP URL Format
- RFC 2254 - The String Representation of LDAP Search Filters
- RFC 2253 - Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names
- RFC 2252 - Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions
- RFC 2251 - Lightweight Directory Access Protocol (v3)
- RFC 2250 - RTP Payload Format for MPEG1/MPEG2 Video
- RFC 2247 - Using Domains in LDAP/X.500 Distinguished Names
- RFC 2246 - The TLS Protocol Version 1.0
- RFC 2245 - Anonymous SASL Mechanism
- RFC 2244 - ACAP -- Application Configuration Access Protocol
- RFC 2243 - OTP Extended Responses
- RFC 2242 - NetWare/IP Domain Name and Information
- RFC 2241 - DHCP Options for Novell Directory Services
- RFC 2238 - Definitions of Managed Objects for HPR using SMIv2
- RFC 2237 - Japanese Character Encoding for Internet Messages
- RFC 2236 - Internet Group Management Protocol, Version 2
- RFC 2235 - Hobbes' Internet Timeline
- RFC 2234 - Augmented BNF for Syntax Specifications: ABNF
- RFC 2232 - Definitions of Managed Objects for DLUR using SMIv2
- RFC 2231 - MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
- RFC 2230 - Key Exchange Delegation Record for the DNS
- RFC 2229 - A Dictionary Server Protocol
- RFC 2228 - FTP Security Extensions
- RFC 2227 - Simple Hit-Metering and Usage-Limiting for HTTP
- RFC 2226 - IP Broadcast over ATM Networks
- RFC 2225 - Classical IP and ARP over ATM
- RFC 2224 - NFS URL Scheme
- RFC 2223 - Instructions to RFC Authors
- RFC 2222 - Simple Authentication and Security Layer (SASL)
- RFC 2221 - IMAP4 Login Referrals
- RFC 2220 - The Application/MARC Content-type
- RFC 2219 - Use of DNS Aliases for Network Services
- RFC 2218 - A Common Schema for the Internet White Pages Service
- RFC 2217 - Telnet Com Port Control Option
- RFC 2216 - Network Element Service Specification Template
- RFC 2215 - General Characterization Parameters for Integrated Service Network Elements
- RFC 2214 - Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2
- RFC 2213 - Integrated Services Management Information Base using SMIv2
- RFC 2212 - Specification of Guaranteed Quality of Service
- RFC 2211 - Specification of the Controlled-Load Network Element Service
- RFC 2210 - The Use of RSVP with IETF Integrated Services
- RFC 2209 - Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules
- RFC 2208 - Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment
- RFC 2207 - RSVP Extensions for IPSEC Data Flows
- RFC 2206 - RSVP Management Information Base using SMIv2
- RFC 2205 - Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
- RFC 2204 - ODETTE File Transfer Protocol
- RFC 2203 - RPCSEC_GSS Protocol Specification
- RFC 2202 - Test Cases for HMAC-MD5 and HMAC-SHA-1
- RFC 2201 - Core Based Trees (CBT) Multicast Routing Architecture
- RFC 2199 - Request for Comments Summary RFC Numbers 2100-2199
- RFC 2198 - RTP Payload for Redundant Audio Data
- RFC 2197 - SMTP Service Extension for Command Pipelining
- RFC 2196 - Site Security Handbook
- RFC 2195 - IMAP/POP AUTHorize Extension for Simple Challenge/Response
- RFC 2194 - Review of Roaming Implementations
- RFC 2193 - IMAP4 Mailbox Referrals
- RFC 2192 - IMAP URL Scheme
- RFC 2191 - VENUS - Very Extensive Non-Unicast Service
- RFC 2190 - RTP Payload Format for H.263 Video Streams
- RFC 2189 - Core Based Trees (CBT version 2) Multicast Routing
- RFC 2188 - AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2
- RFC 2187 - Application of Internet Cache Protocol (ICP), version 2
- RFC 2186 - Internet Cache Protocol (ICP), version 2
- RFC 2185 - Routing Aspects of IPv6 Transition
- RFC 2183 - Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
- RFC 2182 - Selection and Operation of Secondary DNS Servers
- RFC 2181 - Clarifications to the DNS Specification
- RFC 2180 - IMAP4 Multi-Accessed Mailbox Practice
- RFC 2179 - Network Security For Trade Shows
- RFC 2177 - IMAP4 IDLE command
- RFC 2176 - IPv4 over MAPOS Version 1
- RFC 2175 - MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing
- RFC 2174 - A MAPOS version 1 Extension - Switch-Switch Protocol
- RFC 2173 - A MAPOS version 1 Extension - Node Switch Protocol
- RFC 2172 - MAPOS Version 1 Assigned Numbers
- RFC 2171 - MAPOS - Multiple Access Protocol over SONET/SDH Version 1
- RFC 2170 - Application REQuested IP over ATM (AREQUIPA)
- RFC 2169 - A Trivial Convention for using HTTP in URN Resolution
- RFC 2168 - Resolution of Uniform Resource Identifiers using the Domain Name System
- RFC 2167 - Referral Whois (RWhois) Protocol V1.5
- RFC 2166 - APPN Implementer's Workshop Closed Pages Document DLSw v2.0 Enhancements
- RFC 2165 - Service Location Protocol
- RFC 2164 - Use of an X.500/LDAP directory to support MIXER address mapping
- RFC 2163 - Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM)
- RFC 2162 - MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mail
- RFC 2161 - A MIME Body Part for ODA
- RFC 2160 - Carrying PostScript in X.400 and MIME
- RFC 2159 - A MIME Body Part for FAX
- RFC 2158 - X.400 Image Body Parts
- RFC 2157 - Mapping between X.400 and RFC-822/MIME Message Bodies
- RFC 2156 - MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME
- RFC 2154 - OSPF with Digital Signatures
- RFC 2153 - PPP Vendor Extensions
- RFC 2152 - UTF-7 A Mail-Safe Transformation Format of Unicode
- RFC 2151 - A Primer On Internet and TCP/IP Tools and Utilities
- RFC 2150 - Humanities and Arts: Sharing Center Stage on the Internet
- RFC 2149 - Multicast Server Architectures for MARS-based ATM multicasting
- RFC 2148 - Deployment of the Internet White Pages Service
- RFC 2146 - U.S
- RFC 2145 - Use and Interpretation of HTTP Version Numbers
- RFC 2144 - The CAST-128 Encryption Algorithm
- RFC 2143 - Encapsulating IP with the Small Computer System Interface
- RFC 2142 - Mailbox Names for Common Services, Roles and Functions
- RFC 2141 - URN Syntax
- RFC 2140 - TCP Control Block Interdependence
- RFC 2137 - Secure Domain Name System Dynamic Update
- RFC 2136 - Dynamic Updates in the Domain Name System (DNS UPDATE)
- RFC 2135 - Internet Society By-Laws
- RFC 2134 - Articles of Incorporation of Internet Society
- RFC 2132 - DHCP Options and BOOTP Vendor Extensions
- RFC 2131 - Dynamic Host Configuration Protocol
- RFC 2130 - The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996
- RFC 2129 - Toshiba's Flow Attribute Notification Protocol (FANP) Specification
- RFC 2128 - Dial Control Management Information Base using SMIv2
- RFC 2127 - ISDN Management Information Base using SMIv2
- RFC 2126 - ISO Transport Service on top of TCP (ITOT)
- RFC 2125 - The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth Allocation Control Protocol (BACP)
- RFC 2124 - Cabletron's Light-weight Flow Admission Protocol Specification Version 1.0
- RFC 2123 - Traffic Flow Measurement: Experiences with NeTraMet
- RFC 2122 - VEMMI URL Specification
- RFC 2121 - Issues affecting MARS Cluster Size
- RFC 2120 - Managing the X.500 Root Naming Context
- RFC 2119 - Key words for use in RFCs to Indicate Requirement Levels
- RFC 2118 - Microsoft Point-To-Point Compression (MPPC) Protocol
- RFC 2116 - X.500 Implementations Catalog-96
- RFC 2115 - Management Information Base for Frame Relay DTEs Using SMIv2
- RFC 2114 - Data Link Switching Client Access Protocol
- RFC 2113 - IP Router Alert Option
- RFC 2109 - HTTP State Management Mechanism
- RFC 2108 - Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2
- RFC 2107 - Ascend Tunnel Management Protocol - ATMP
- RFC 2105 - Cisco Systems' Tag Switching Architecture Overview
- RFC 2104 - HMAC: Keyed-Hashing for Message Authentication
- RFC 2103 - Mobility Support for Nimrod : Challenges and Solution Approaches
- RFC 2102 - Multicast Support for Nimrod : Requirements and Solution Approaches
- RFC 2101 - IPv4 Address Behaviour Today
- RFC 2100 - The Naming of Hosts
- RFC 2099 - Request for Comments Summary RFC Numbers 2000-2099
- RFC 2098 - Toshiba's Router Architecture Extensions for ATM : Overview
- RFC 2097 - The PPP NetBIOS Frames Control Protocol (NBFCP)
- RFC 2096 - IP Forwarding Table MIB
- RFC 2094 - Group Key Management Protocol (GKMP) Architecture
- RFC 2093 - Group Key Management Protocol (GKMP) Specification
- RFC 2092 - Protocol Analysis for Triggered RIP
- RFC 2091 - Triggered Extensions to RIP to Support Demand Circuits
- RFC 2090 - TFTP Multicast Option
- RFC 2088 - IMAP4 non-synchronizing literals
- RFC 2087 - IMAP4 QUOTA extension
- RFC 2086 - IMAP4 ACL extension
- RFC 2085 - HMAC-MD5 IP Authentication with Replay Prevention
- RFC 2084 - Considerations for Web Transaction Security
- RFC 2083 - PNG (Portable Network Graphics) Specification Version 1.0
- RFC 2082 - RIP-2 MD5 Authentication
- RFC 2081 - RIPng Protocol Applicability Statement
- RFC 2080 - RIPng for IPv6
- RFC 2079 - Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)
- RFC 2077 - The Model Primary Content Type for Multipurpose Internet Mail Extensions
- RFC 2076 - Common Internet Message Headers
- RFC 2075 - IP Echo Host Service
- RFC 2072 - Router Renumbering Guide
- RFC 2071 - Network Renumbering Overview: Why would I want it and what is it anyway?
- RFC 2067 - IP over HIPPI
- RFC 2066 - TELNET CHARSET Option
- RFC 2063 - Traffic Flow Measurement: Architecture
- RFC 2062 - Internet Message Access Protocol - Obsolete Syntax
- RFC 2061 - IMAP4 Compatibility with IMAP2bis
- RFC 2060 - Internet Message Access Protocol - Version 4rev1
- RFC 2057 - Source Directed Access Control on the Internet
- RFC 2056 - Uniform Resource Locators for Z39.50
- RFC 2055 - WebNFS Server Specification
- RFC 2054 - WebNFS Client Specification
- RFC 2053 - The AM (Armenia) Domain
- RFC 2051 - Definitions of Managed Objects for APPC using SMIv2
- RFC 2050 - Internet Registry IP Allocation Guidelines
- RFC 2049 - Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
- RFC 2048 - Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
- RFC 2047 - MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
- RFC 2046 - Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
- RFC 2045 - Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
- RFC 2043 - The PPP SNA Control Protocol (SNACP)
- RFC 2042 - Registering New BGP Attribute Types
- RFC 2041 - Mobile Network Tracing
- RFC 2040 - The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms
- RFC 2039 - Applicability of Standards Track MIBs to Management of World Wide Web Servers
- RFC 2036 - Observations on the use of Components of the Class A Address Space within the Internet
- RFC 2034 - SMTP Service Extension for Returning Enhanced Error Codes
- RFC 2033 - Local Mail Transfer Protocol
- RFC 2032 - RTP Payload Format for H.261 Video Streams
- RFC 2031 - IETF-ISOC relationship
- RFC 2030 - Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI
- RFC 2029 - RTP Payload Format of Sun's CellB Video Encoding
- RFC 2028 - The Organizations Involved in the IETF Standards Process
- RFC 2026 - The Internet Standards Process -- Revision 3
- RFC 2025 - The Simple Public-Key GSS-API Mechanism (SPKM)
- RFC 2024 - Definitions of Managed Objects for Data Link Switching using SMIv2
- RFC 2022 - Support for Multicast over UNI 3.0/3.1 based ATM Networks
- RFC 2021 - Remote Network Monitoring Management Information Base Version 2 using SMIv2
- RFC 2020 - IEEE 802.12 Interface MIB
- RFC 2018 - TCP Selective Acknowledgement Options
- RFC 2017 - Definition of the URL MIME External-Body Access-Type
- RFC 2016 - Uniform Resource Agents (URAs)
- RFC 2015 - MIME Security with Pretty Good Privacy (PGP)
- RFC 2014 - IRTF Research Group Guidelines and Procedures
- RFC 2013 - SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2
- RFC 2012 - SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2
- RFC 2011 - SNMPv2 Management Information Base for the Internet Protocol using SMIv2
- RFC 2009 - GPS-Based Addressing and Routing
- RFC 2008 - Implications of Various Address Allocation Policies for Internet Routing
- RFC 2007 - Catalogue of Network Training Materials
- RFC 2006 - The Definitions of Managed Objects for IP Mobility Support using SMIv2
- RFC 2005 - Applicability Statement for IP Mobility Support
- RFC 2004 - Minimal Encapsulation within IP
- RFC 2003 - IP Encapsulation within IP
- RFC 2002 - IP Mobility Support
- RFC 1999 - Request for Comments Summary RFC Numbers 1900-1999
- RFC 1998 - An Application of the BGP Community Attribute in Multi-home Routing
- RFC 1997 - BGP Communities Attribute
- RFC 1996 - A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)
- RFC 1995 - Incremental Zone Transfer in DNS
- RFC 1994 - PPP Challenge Handshake Authentication Protocol (CHAP)
- RFC 1993 - PPP Gandalf FZA Compression Protocol
- RFC 1992 - The Nimrod Routing Architecture
- RFC 1991 - PGP Message Exchange Formats
- RFC 1990 - The PPP Multilink Protocol (MP)
- RFC 1989 - PPP Link Quality Monitoring
- RFC 1988 - Conditional Grant of Rights to Specific Hewlett-Packard Patents In Conjunction With the Internet Engineering Task Force's Internet-Standard Network Management Framework
- RFC 1987 - Ipsilon's General Switch Management Protocol Specification Version 1.1
- RFC 1986 - Experiments with a Simple File Transfer Protocol for Radio Links using Enhanced Trivial File Transfer Protocol (ETFTP)
- RFC 1985 - SMTP Service Extension for Remote Message Queue Starting
- RFC 1984 - IAB and IESG Statement on Cryptographic Technology and the Internet
- RFC 1983 - Internet Users' Glossary
- RFC 1982 - Serial Number Arithmetic
- RFC 1981 - Path MTU Discovery for IP version 6
- RFC 1980 - A Proposed Extension to HTML : Client-Side Image Maps
- RFC 1979 - PPP Deflate Protocol
- RFC 1978 - PPP Predictor Compression Protocol
- RFC 1977 - PPP BSD Compression Protocol
- RFC 1976 - PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)
- RFC 1975 - PPP Magnalink Variable Resource Compression
- RFC 1974 - PPP Stac LZS Compression Protocol
- RFC 1973 - PPP in Frame Relay
- RFC 1968 - The PPP Encryption Control Protocol (ECP)
- RFC 1967 - PPP LZS-DCP Compression Protocol (LZS-DCP)
- RFC 1966 - BGP Route Reflection An alternative to full mesh IBGP
- RFC 1965 - Autonomous System Confederations for BGP
- RFC 1964 - The Kerberos Version 5 GSS-API Mechanism
- RFC 1963 - PPP Serial Data Transport Protocol (SDTP)
- RFC 1962 - The PPP Compression Control Protocol (CCP)
- RFC 1961 - GSS-API Authentication Method for SOCKS Version 5
- RFC 1958 - Architectural Principles of the Internet
- RFC 1957 - Some Observations on Implementations of the Post Office Protocol (POP3)
- RFC 1956 - Registration in the MIL Domain
- RFC 1955 - New Scheme for Internet Routing and Addressing (ENCAPS) for IPNG
- RFC 1954 - Transmission of Flow Labelled IPv4 on ATM Data Links Ipsilon Version 1.0
- RFC 1953 - Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0
- RFC 1952 - GZIP file format specification version 4.3
- RFC 1951 - DEFLATE Compressed Data Format Specification version 1.3
- RFC 1950 - ZLIB Compressed Data Format Specification version 3.3
- RFC 1949 - Scalable Multicast Key Distribution
- RFC 1948 - Defending Against Sequence Number Attacks
- RFC 1947 - Greek Character Encoding for Electronic Mail Messages
- RFC 1946 - Native ATM Support for ST2+
- RFC 1945 - Hypertext Transfer Protocol -- HTTP/1.0
- RFC 1943 - Building an X.500 Directory Service in the US
- RFC 1942 - HTML Tables
- RFC 1941 - Frequently Asked Questions for Schools
- RFC 1940 - Source Demand Routing: Packet Format and Forwarding Specification (Version 1)
- RFC 1939 - Post Office Protocol - Version 3
- RFC 1937 - "Local/Remote" Forwarding Decision in Switched Data Link Subnetworks
- RFC 1936 - Implementing the Internet Checksum in Hardware
- RFC 1935 - What is the Internet, Anyway?
- RFC 1934 - Ascend's Multilink Protocol Plus (MP+)
- RFC 1932 - IP over ATM: A Framework Document
- RFC 1931 - Dynamic RARP Extensions for Automatic Network Address Acquisition
- RFC 1930 - Guidelines for creation, selection, and registration of an Autonomous System (AS)
- RFC 1929 - Username/Password Authentication for SOCKS V5
- RFC 1928 - SOCKS Protocol Version 5
- RFC 1927 - Suggested Additional MIME Types for Associating Documents
- RFC 1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM
- RFC 1925 - The Twelve Networking Truths
- RFC 1924 - A Compact Representation of IPv6 Addresses
- RFC 1923 - RIPv1 Applicability Statement for Historic Status
- RFC 1922 - Chinese Character Encoding for Internet Messages
- RFC 1921 - TNVIP Protocol
- RFC 1919 - Classical versus Transparent IP Proxies
- RFC 1918 - Address Allocation for Private Internets
- RFC 1917 - An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA
- RFC 1916 - Enterprise Renumbering: Experience and Information Solicitation
- RFC 1915 - Variance for The PPP Connection Control Protocol and The PPP Encryption Control Protocol
- RFC 1914 - How to Interact with a Whois++ Mesh
- RFC 1913 - Architecture of the Whois++ Index Service
- RFC 1912 - Common DNS Operational and Configuration Errors
- RFC 1910 - User-based Security Model for SNMPv2
- RFC 1909 - An Administrative Infrastructure for SNMPv2
- RFC 1907 - Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)
- RFC 1906 - Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)
- RFC 1905 - Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)
- RFC 1901 - Introduction to Community-based SNMPv2
- RFC 1900 - Renumbering Needs Work
- RFC 1899 - Request for Comments Summary RFC Numbers 1800-1899
- RFC 1898 - CyberCash Credit Card Protocol Version 0.8
- RFC 1896 - The text/enriched MIME Content-type
- RFC 1895 - The Application/CALS-1840 Content-type
- RFC 1894 - An Extensible Message Format for Delivery Status Notifications
- RFC 1893 - Enhanced Mail System Status Codes
- RFC 1892 - The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages
- RFC 1891 - SMTP Service Extension for Delivery Status Notifications
- RFC 1890 - RTP Profile for Audio and Video Conferences with Minimal Control
- RFC 1889 - RTP: A Transport Protocol for Real-Time Applications
- RFC 1888 - OSI NSAPs and IPv6
- RFC 1887 - An Architecture for IPv6 Unicast Address Allocation
- RFC 1886 - DNS Extensions to support IP version 6
- RFC 1882 - The 12-Days of Technology Before Christmas
- RFC 1881 - IPv6 Address Allocation Management
- RFC 1879 - Class A Subnet Experiment Results and Recommendations
- RFC 1878 - Variable Length Subnet Table For IPv4
- RFC 1877 - PPP Internet Protocol Control Protocol Extensions for Name Server Addresses
- RFC 1876 - A Means for Expressing Location Information in the Domain Name System
- RFC 1875 - UNINETT PCA Policy Statements
- RFC 1874 - SGML Media Types
- RFC 1873 - Message/External-Body Content-ID Access Type
- RFC 1871 - Addendum to RFC 1602 -- Variance Procedure
- RFC 1870 - SMTP Service Extension for Message Size Declaration
- RFC 1869 - SMTP Service Extensions
- RFC 1868 - ARP Extension - UNARP
- RFC 1867 - Form-based File Upload in HTML
- RFC 1866 - Hypertext Markup Language - 2.0
- RFC 1865 - EDI Meets the Internet Frequently Asked Questions about Electronic Data Interchange (EDI) on the Internet
- RFC 1864 - The Content-MD5 Header Field
- RFC 1863 - A BGP/IDRP Route Server alternative to a full mesh routing
- RFC 1862 - Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994
- RFC 1861 - Simple Network Paging Protocol - Version 3 -Two-Way Enhanced
- RFC 1859 - ISO Transport Class 2 Non-use of Explicit Flow Control over TCP RFC1006 extension
- RFC 1858 - Security Considerations for IP Fragment Filtering
- RFC 1857 - A Model for Common Operational Statistics
- RFC 1856 - The Opstat Client-Server Model for Statistics Retrieval
- RFC 1855 - Netiquette Guidelines
- RFC 1853 - IP in IP Tunneling
- RFC 1852 - IP Authentication using Keyed SHA
- RFC 1851 - The ESP Triple DES Transform
- RFC 1850 - OSPF Version 2 Management Information Base
- RFC 1848 - MIME Object Security Services
- RFC 1847 - Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
- RFC 1846 - SMTP 521 Reply Code
- RFC 1845 - SMTP Service Extension for Checkpoint/Restart
- RFC 1844 - Multimedia E-mail (MIME) User Agent Checklist
- RFC 1843 - HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters
- RFC 1842 - ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages
- RFC 1841 - PPP Network Control Protocol for LAN Extension
- RFC 1835 - Architecture of the WHOIS++ service
- RFC 1834 - Whois and Network Information Lookup Service, Whois++
- RFC 1833 - Binding Protocols for ONC RPC Version 2
- RFC 1832 - XDR: External Data Representation Standard
- RFC 1831 - RPC: Remote Procedure Call Protocol Specification Version 2
- RFC 1830 - SMTP Service Extensions for Transmission of Large and Binary MIME Messages
- RFC 1829 - The ESP DES-CBC Transform
- RFC 1828 - IP Authentication using Keyed MD5
- RFC 1824 - The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4)
- RFC 1823 - The LDAP Application Program Interface
- RFC 1822 - A Grant of Rights to Use a Specific IBM patent with Photuris
- RFC 1821 - Integration of Real-time Services in an IP-ATM Network Architecture
- RFC 1819 - Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+
- RFC 1818 - Best Current Practices
- RFC 1817 - CIDR and Classful Routing
- RFC 1815 - Character Sets ISO-10646 and ISO-10646-J-1
- RFC 1814 - Unique Addresses are Good
- RFC 1813 - NFS Version 3 Protocol Specification
- RFC 1812 - Requirements for IP Version 4 Routers
- RFC 1810 - Report on MD5 Performance
- RFC 1809 - Using the Flow Label Field in IPv6
- RFC 1808 - Relative Uniform Resource Locators
- RFC 1807 - A Format for Bibliographic Records
- RFC 1806 - Communicating Presentation Information in Internet Messages: The Content-Disposition Header
- RFC 1805 - Location-Independent Data/Software Integrity Protocol
- RFC 1804 - Schema Publishing in X.500 Directory
- RFC 1803 - Recommendations for an X.500 Production Directory Service
- RFC 1802 - Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing
- RFC 1801 - MHS use of the X.500 Directory to support MHS Routing
- RFC 1799 - Request for Comments Summary RFC Numbers 1700-1799
- RFC 1798 - Connection-less Lightweight X.500 Directory Access Protocol
- RFC 1797 - Class A Subnet Experiment
- RFC 1796 - Not All RFCs are Standards
- RFC 1795 - Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1
- RFC 1794 - DNS Support for Load Balancing
- RFC 1793 - Extending OSPF to Support Demand Circuits
- RFC 1792 - TCP/IPX Connection Mib Specification
- RFC 1791 - TCP And UDP Over IPX Networks With Fixed Path MTU
- RFC 1790 - An Agreement between the Internet Society and Sun Microsystems, Inc
- RFC 1789 - INETPhone: Telephone Services and Servers on Internet
- RFC 1788 - ICMP Domain Name Messages
- RFC 1787 - Routing in a Multi-provider Internet
- RFC 1786 - Representation of IP Routing Policies in a Routing Registry (ripe-81++)
- RFC 1785 - TFTP Option Negotiation Analysis
- RFC 1781 - Using the OSI Directory to Achieve User Friendly Naming
- RFC 1778 - The String Representation of Standard Attribute Syntaxes
- RFC 1777 - Lightweight Directory Access Protocol
- RFC 1776 - The Address is the Message
- RFC 1775 - To Be "On" the Internet
- RFC 1774 - BGP-4 Protocol Analysis
- RFC 1773 - Experience with the BGP-4 protocol
- RFC 1772 - Application of the Border Gateway Protocol in the Internet
- RFC 1771 - A Border Gateway Protocol 4 (BGP-4)
- RFC 1770 - IPv4 Option for Sender Directed Multi-Destination Delivery
- RFC 1768 - Host Group Extensions for CLNP Multicasting
- RFC 1767 - MIME Encapsulation of EDI Objects
- RFC 1766 - Tags for the Identification of Languages
- RFC 1765 - OSPF Database Overflow
- RFC 1764 - The PPP XNS IDP Control Protocol (XNSCP)
- RFC 1763 - The PPP Banyan Vines Control Protocol (BVCP)
- RFC 1762 - The PPP DECnet Phase IV Control Protocol (DNCP)
- RFC 1761 - Snoop Version 2 Packet Capture File Format
- RFC 1760 - The S/KEY One-Time Password System
- RFC 1759 - Printer MIB
- RFC 1758 - NADF Standing Documents: A Brief Overview
- RFC 1756 - Remote Write Protocol - Version 1.0
- RFC 1755 - ATM Signaling Support for IP over ATM
- RFC 1754 - IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1
- RFC 1753 - IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture
- RFC 1752 - The Recommendation for the IP Next Generation Protocol
- RFC 1751 - A Convention for Human-Readable 128-bit Keys
- RFC 1750 - Randomness Recommendations for Security
- RFC 1749 - IEEE 802.5 Station Source Routing MIB using SMIv2
- RFC 1748 - IEEE 802.5 MIB using SMIv2
- RFC 1747 - Definitions of Managed Objects for SNA Data Link Control (SDLC) using SMIv2
- RFC 1746 - Ways to Define User Expectations
- RFC 1745 - BGP4/IDRP for IP---OSPF Interaction
- RFC 1744 - Observations on the Management of the Internet Address Space
- RFC 1742 - AppleTalk Management Information Base II
- RFC 1741 - MIME Content Type for BinHex Encoded Files
- RFC 1740 - MIME Encapsulation of Macintosh Files - MacMIME
- RFC 1738 - Uniform Resource Locators (URL)
- RFC 1737 - Functional Requirements for Uniform Resource Names
- RFC 1736 - Functional Recommendations for Internet Resource Locators
- RFC 1735 - NBMA Address Resolution Protocol (NARP)
- RFC 1734 - POP3 AUTHentication command
- RFC 1733 - Distributed Electronic Mail Models in IMAP4
- RFC 1732 - IMAP4 Compatibility with IMAP2 and IMAP2bis
- RFC 1731 - IMAP4 Authentication Mechanisms
- RFC 1729 - Using the Z39.50 Information Retrieval Protocol
- RFC 1728 - Resource Transponders
- RFC 1727 - A Vision of an Integrated Internet Information Service
- RFC 1726 - Technical Criteria for Choosing IP The Next Generation (IPng)
- RFC 1724 - RIP Version 2 MIB Extension
- RFC 1722 - RIP Version 2 Protocol Applicability Statement
- RFC 1721 - RIP Version 2 Protocol Analysis
- RFC 1719 - A Direction for IPng
- RFC 1718 - The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
- RFC 1715 - The H Ratio for Address Assignment Efficiency
- RFC 1713 - Tools for DNS debugging
- RFC 1712 - DNS Encoding of Geographical Location
- RFC 1711 - Classifications in E-mail Routing
- RFC 1710 - Simple Internet Protocol Plus White Paper
- RFC 1709 - K-12 Internetworking Guidelines
- RFC 1708 - NTP PICS PROFORMA - For the Network Time Protocol Version 3
- RFC 1707 - CATNIP: Common Architecture for the Internet
- RFC 1706 - DNS NSAP Resource Records
- RFC 1705 - Six Virtual Inches to the Left: The Problem with IPng
- RFC 1704 - On Internet Authentication
- RFC 1703 - Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
- RFC 1702 - Generic Routing Encapsulation over IPv4 networks
- RFC 1701 - Generic Routing Encapsulation (GRE)
- RFC 1700 - Assigned Numbers
- RFC 1699 - Summary of 1600-1699
- RFC 1698 - Octet Sequences for Upper-Layer OSI to Support Basic Communications Applications
- RFC 1697 - Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2
- RFC 1696 - Modem Management Information Base (MIB) using SMIv2
- RFC 1694 - Definitions of Managed Objects for SMDS Interfaces using SMIv2
- RFC 1693 - An Extension to TCP : Partial Order Service
- RFC 1692 - Transport Multiplexing Protocol (TMux)
- RFC 1691 - The Document Architecture for the Cornell Digital Library
- RFC 1690 - Introducing the Internet Engineering and Planning Group (IEPG)
- RFC 1689 - A Status Report on Networked Information Retrieval: Tools and Groups
- RFC 1688 - IPng Mobility Considerations
- RFC 1687 - A Large Corporate User's View of IPng
- RFC 1686 - IPng Requirements: A Cable Television Industry Viewpoint
- RFC 1685 - Writing X.400 O/R Names
- RFC 1684 - Introduction to White Pages Services based on X.500
- RFC 1683 - Multiprotocol Interoperability In IPng
- RFC 1682 - IPng BSD Host Implementation Analysis
- RFC 1681 - On Many Addresses per Host
- RFC 1680 - IPng Support for ATM Services
- RFC 1679 - HPN Working Group Input to the IPng Requirements Solicitation
- RFC 1678 - IPng Requirements of Large Corporate Networks
- RFC 1677 - Tactical Radio Frequency Communication Requirements for IPng
- RFC 1676 - INFN Requirements for an IPng
- RFC 1675 - Security Concerns for IPng
- RFC 1674 - A Cellular Industry View of IPng
- RFC 1673 - Electric Power Research Institute Comments on IPng
- RFC 1672 - Accounting Requirements for IPng
- RFC 1671 - IPng White Paper on Transition and Other Considerations
- RFC 1670 - Input to IPng Engineering Considerations
- RFC 1669 - Market Viability as a IPng Criteria
- RFC 1668 - Unified Routing Requirements for IPng
- RFC 1667 - Modeling and Simulation Requirements for IPng
- RFC 1666 - Definitions of Managed Objects for SNA NAUs using SMIv2
- RFC 1663 - PPP Reliable Transmission
- RFC 1662 - PPP in HDLC-like Framing
- RFC 1661 - The Point-to-Point Protocol (PPP)
- RFC 1660 - Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2
- RFC 1659 - Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2
- RFC 1658 - Definitions of Managed Objects for Character Stream Devices using SMIv2
- RFC 1657 - Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2
- RFC 1652 - SMTP Service Extension for 8bit-MIMEtransport
- RFC 1649 - Operational Requirements for X.400 Management Domains in the GO-MHS Community
- RFC 1648 - Postmaster Convention for X.400 Operations
- RFC 1646 - TN3270 Extensions for LUname and Printer Selection
- RFC 1644 - T/TCP -- TCP Extensions for Transactions Functional Specification
- RFC 1643 - Definitions of Managed Objects for the Ethernet-like Interface Types
- RFC 1641 - Using Unicode with MIME
- RFC 1640 - The Process for Organization of Internet Standards Working Group (POISED)
- RFC 1639 - FTP Operation Over Big Address Records (FOOBAR)
- RFC 1636 - Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994
- RFC 1635 - How to Use Anonymous FTP
- RFC 1634 - Novell IPX Over Various WAN Media (IPXWAN)
- RFC 1633 - Integrated Services in the Internet Architecture: an Overview
- RFC 1631 - The IP Network Address Translator (NAT)
- RFC 1630 - Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web
- RFC 1629 - Guidelines for OSI NSAP Allocation in the Internet
- RFC 1628 - UPS Management Information Base
- RFC 1625 - WAIS over Z39.50-1988
- RFC 1624 - Computation of the Internet Checksum via Incremental Update
- RFC 1622 - Pip Header Processing
- RFC 1621 - Pip Near-term Architecture
- RFC 1620 - Internet Architecture Extensions for Shared Media
- RFC 1618 - PPP over ISDN
- RFC 1617 - Naming and Structuring Guidelines for X.500 Directory Pilots
- RFC 1616 - X.400(1988) for the Academic and Research Community in Europe
- RFC 1615 - Migrating from X.400(84) to X.400(88)
- RFC 1614 - Network Access to Multimedia Information
- RFC 1613 - cisco Systems X.25 over TCP (XOT)
- RFC 1612 - DNS Resolver MIB Extensions
- RFC 1611 - DNS Server MIB Extensions
- RFC 1609 - Charting Networks in the X.500 Directory
- RFC 1608 - Representing IP Information in the X.500 Directory
- RFC 1607 - A VIEW FROM THE 21ST CENTURY
- RFC 1606 - A Historical Perspective On The Usage Of IP Version 9
- RFC 1605 - SONET to Sonnet Translation
- RFC 1604 - Definitions of Managed Objects for Frame Relay Service
- RFC 1599 - Summary of 1500-1599
- RFC 1598 - PPP in X.25
- RFC 1593 - SNA APPN Node MIB
- RFC 1592 - Simple Network Management Protocol Distributed Protocol Interface Version 2.0
- RFC 1591 - Domain Name System Structure and Delegation
- RFC 1589 - A Kernel Model for Precision Timekeeping
- RFC 1588 - White Pages Meeting Report
- RFC 1587 - The OSPF NSSA Option
- RFC 1586 - Guidelines for Running OSPF Over Frame Relay Networks
- RFC 1585 - MOSPF: Analysis and Experience
- RFC 1584 - Multicast Extensions to OSPF
- RFC 1582 - Extensions to RIP to Support Demand Circuits
- RFC 1581 - Protocol Analysis for Extensions to RIP to Support Demand Circuits
- RFC 1580 - Guide to Network Resource Tools
- RFC 1579 - Firewall-Friendly FTP
- RFC 1576 - TN3270 Current Practices
- RFC 1575 - An Echo Function for CLNP (ISO 8473)
- RFC 1574 - Essential Tools for the OSI Internet
- RFC 1572 - Telnet Environment Option
- RFC 1571 - Telnet Environment Option Interoperability Issues
- RFC 1570 - PPP LCP Extensions
- RFC 1564 - DSA Metrics (OSI-DS 34 (v3))
- RFC 1562 - Naming Guidelines for the AARNet X.500 Directory Service
- RFC 1561 - Use of ISO CLNP in TUBA Environments
- RFC 1560 - The MultiProtocol Internet
- RFC 1559 - DECnet Phase IV MIB Extensions
- RFC 1557 - Korean Character Encoding for Internet Messages
- RFC 1556 - Handling of Bi-directional Texts in MIME
- RFC 1555 - Hebrew Character Encoding for Internet Messages
- RFC 1554 - ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP
- RFC 1553 - Compressing IPX Headers Over WAN Media (CIPX)
- RFC 1552 - The PPP Internetworking Packet Exchange Control Protocol (IPXCP)
- RFC 1550 - IP: Next Generation (IPng) White Paper Solicitation
- RFC 1547 - Requirements for an Internet Standard Point-to-Point Protocol
- RFC 1546 - Host Anycasting Service
- RFC 1542 - Clarifications and Extensions for the Bootstrap Protocol
- RFC 1538 - Advanced SNA/IP : A Simple SNA Transport Protocol
- RFC 1536 - Common DNS Implementation Errors and Suggested Fixes
- RFC 1535 - A Security Problem and Proposed Correction With Widely Deployed DNS Software
- RFC 1534 - Interoperation Between DHCP and BOOTP
- RFC 1530 - Principles of Operation for the TPC.INT Subdomain: General Principles and Policy
- RFC 1529 - Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies
- RFC 1528 - Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures
- RFC 1527 - What Should We Plan Given the Dilemma of the Network?
- RFC 1526 - Assignment of System Identifiers for TUBA/CLNP Hosts
- RFC 1525 - Definitions of Managed Objects for Source Routing Bridges
- RFC 1524 - A User Agent Configuration Mechanism For Multimedia Mail Format Information
- RFC 1520 - Exchanging Routing Information Across Provider Boundaries in the CIDR Environment
- RFC 1519 - Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy
- RFC 1518 - An Architecture for IP Address Allocation with CIDR
- RFC 1517 - Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR)
- RFC 1515 - Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
- RFC 1514 - Host Resources MIB
- RFC 1513 - Token Ring Extensions to the Remote Network Monitoring MIB
- RFC 1512 - FDDI Management Information Base
- RFC 1511 - Common Authentication Technology Overview
- RFC 1510 - The Kerberos Network Authentication Service (V5)
- RFC 1507 - DASS - Distributed Authentication Security Service
- RFC 1506 - A Tutorial on Gatewaying between X.400 and Internet Mail
- RFC 1505 - Encoding Header Field for Internet Messages
- RFC 1504 - Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing
- RFC 1503 - Algorithms for Automating Administration in SNMPv2 Managers
- RFC 1502 - X.400 Use of Extended Character Sets
- RFC 1501 - OS/2 User Group
- RFC 1499 - Summary of 1400-1499
- RFC 1498 - On the Naming and Binding of Network Destinations
- RFC 1496 - Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages
- RFC 1494 - Equivalences between 1988 X.400 and RFC-822 Message Bodies
- RFC 1493 - Definitions of Managed Objects for Bridges
- RFC 1492 - An Access Control Protocol, Sometimes Called TACACS
- RFC 1491 - A Survey of Advanced Usages of X.500
- RFC 1489 - Registration of a Cyrillic Character Set
- RFC 1482 - Aggregation Support in the NSFNET Policy-Based Routing Database
- RFC 1481 - IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling
- RFC 1480 - The US Domain
- RFC 1479 - Inter-Domain Policy Routing Protocol Specification: Version 1
- RFC 1478 - An Architecture for Inter-Domain Policy Routing
- RFC 1477 - IDPR as a Proposed Standard
- RFC 1476 - RAP: Internet Route Access Protocol
- RFC 1475 - TP/IX: The Next Internet
- RFC 1474 - The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol
- RFC 1473 - The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol
- RFC 1472 - The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol
- RFC 1471 - The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol
- RFC 1470 - FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
- RFC 1469 - IP Multicast over Token-Ring Local Area Networks
- RFC 1468 - Japanese Character Encoding for Internet Messages
- RFC 1467 - Status of CIDR Deployment in the Internet
- RFC 1465 - Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing
- RFC 1464 - Using the Domain Name System To Store Arbitrary String Attributes
- RFC 1463 - FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings
- RFC 1462 - FYI on "What is the Internet?"
- RFC 1461 - SNMP MIB extension for Multiprotocol Interconnect over X.25
- RFC 1459 - Internet Relay Chat Protocol
- RFC 1458 - Requirements for Multicast Protocols
- RFC 1457 - Security Label Framework for the Internet
- RFC 1456 - Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification
- RFC 1454 - Comparison of Proposals for Next Version of IP
- RFC 1453 - A Comment on Packet Video Remote Conferencing and the Transport/Network Layers
- RFC 1451 - Manager-to-Manager Management Information Base
- RFC 1447 - Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)
- RFC 1446 - Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2)
- RFC 1445 - Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)
- RFC 1441 - Introduction to version 2 of the Internet-standard Network Management Framework
- RFC 1440 - SIFT/UFT: Sender-Initiated/Unsolicited File Transfer
- RFC 1439 - The Uniqueness of Unique Identifiers
- RFC 1438 - Internet Engineering Task Force Statements Of Boredom (SOBs)
- RFC 1437 - The Extension of MIME Content-Types to a New Medium
- RFC 1436 - The Internet Gopher Protocol (a distributed document search and retrieval protocol)
- RFC 1435 - IESG Advice from Experience with Path MTU Discovery
- RFC 1433 - Directed ARP
- RFC 1432 - Recent Internet Books
- RFC 1431 - DUA Metrics (OSI-DS 33 (v2))
- RFC 1430 - A Strategic Plan for Deploying an Internet X.500 Directory Service
- RFC 1429 - Listserv Distribute Protocol
- RFC 1428 - Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME
- RFC 1424 - Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services
- RFC 1423 - Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers
- RFC 1422 - Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management
- RFC 1421 - Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures
- RFC 1420 - SNMP over IPX
- RFC 1419 - SNMP over AppleTalk
- RFC 1418 - SNMP over OSI
- RFC 1416 - Telnet Authentication Option
- RFC 1415 - FTP-FTAM Gateway Specification
- RFC 1414 - Identification MIB
- RFC 1413 - Identification Protocol
- RFC 1412 - Telnet Authentication: SPX
- RFC 1411 - Telnet Authentication: Kerberos Version 4
- RFC 1408 - Telnet Environment Option
- RFC 1403 - BGP OSPF Interaction
- RFC 1402 - There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places
- RFC 1401 - Correspondence between the IAB and DISA on the use of DNS
- RFC 1400 - Transition and Modernization of the Internet Registration Service
- RFC 1399 - Summary of 1300-1399
- RFC 1397 - Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol
- RFC 1396 - The Process for Organization of Internet Standards Working Group (POISED)
- RFC 1394 - Relationship of Telex Answerback Codes to Internet Domains
- RFC 1393 - Traceroute Using an IP Option
- RFC 1390 - Transmission of IP and ARP over FDDI Networks
- RFC 1385 - EIP: The Extended Internet Protocol
- RFC 1383 - An Experiment in DNS Based IP Routing
- RFC 1382 - SNMP MIB Extension for the X.25 Packet Layer
- RFC 1381 - SNMP MIB Extension for X.25 LAPB
- RFC 1380 - IESG Deliberations on Routing and Addressing
- RFC 1379 - Extending TCP for Transactions -- Concepts
- RFC 1378 - The PPP AppleTalk Control Protocol (ATCP)
- RFC 1377 - The PPP OSI Network Layer Control Protocol (OSINLCP)
- RFC 1375 - Suggestion for New Classes of IP Addresses
- RFC 1373 - Portable DUAs
- RFC 1372 - Telnet Remote Flow Control Option
- RFC 1371 - Choosing a Common IGP for the IP Internet
- RFC 1370 - Applicability Statement for OSPF
- RFC 1369 - Implementation Notes and Experience for the Internet Ethernet MIB
- RFC 1365 - An IP Address Extension Proposal
- RFC 1363 - A Proposed Flow Specification
- RFC 1359 - Connecting to the Internet - What Connecting Institutions Should Anticipate
- RFC 1356 - Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
- RFC 1355 - Privacy and Accuracy Issues in Network Information Center Databases
- RFC 1353 - Definitions of Managed Objects for Administration of SNMP Parties
- RFC 1352 - SNMP Security Protocols
- RFC 1351 - SNMP Administrative Model
- RFC 1350 - The TFTP Protocol (Revision 2)
- RFC 1347 - TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing
- RFC 1346 - Resource Allocation, Control, and Accounting for the Use of Network Resources
- RFC 1345 - Character Mnemonics and Character Sets
- RFC 1344 - Implications of MIME for Internet Mail Gateways
- RFC 1343 - A User Agent Configuration Mechanism for Multimedia Mail Format Information
- RFC 1339 - Remote Mail Checking Protocol
- RFC 1337 - TIME-WAIT Assassination Hazards in TCP
- RFC 1336 - Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
- RFC 1335 - A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion
- RFC 1332 - The PPP Internet Protocol Control Protocol (IPCP)
- RFC 1330 - Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community
- RFC 1329 - Thoughts on Address Resolution for Dual MAC FDDI Networks
- RFC 1328 - X.400 1988 to 1984 downgrading
- RFC 1326 - Mutual Encapsulation Considered Dangerous
- RFC 1324 - A Discussion on Computer Network Conferencing
- RFC 1323 - TCP Extensions for High Performance
- RFC 1322 - A Unified Approach to Inter-Domain Routing
- RFC 1321 - The MD5 Message-Digest Algorithm
- RFC 1320 - The MD4 Message-Digest Algorithm
- RFC 1319 - The MD2 Message-Digest Algorithm
- RFC 1314 - A File Format for the Exchange of Images in the Internet
- RFC 1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio
- RFC 1312 - Message Send Protocol 2
- RFC 1311 - Introduction to the STD Notes
- RFC 1309 - Technical Overview of Directory Services Using the X.500 Protocol
- RFC 1308 - Executive Introduction to Directory Services Using the X.500 Protocol
- RFC 1307 - Dynamically Switched Link Control Protocol
- RFC 1306 - Experiences Supporting By-Request Circuit-Switched T3 Networks
- RFC 1305 - Network Time Protocol (Version 3) Specification, Implementation
- RFC 1303 - A Convention for Describing SNMP-based Agents
- RFC 1302 - Building a Network Information Services Infrastructure
- RFC 1301 - Multicast Transport Protocol
- RFC 1300 - Remembrances of Things Past
- RFC 1299 - Summary of 1200-1299
- RFC 1297 - NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS")
- RFC 1296 - Internet Growth (1981-1991)
- RFC 1291 - Mid-Level Networks Potential Technical Services
- RFC 1288 - The Finger User Information Protocol
- RFC 1287 - Towards the Future Internet Architecture
- RFC 1285 - FDDI Management Information Base
- RFC 1282 - BSD Rlogin
- RFC 1281 - Guidelines for the Secure Operation of the Internet
- RFC 1279 - X.500 and Domains
- RFC 1278 - A string encoding of Presentation Address
- RFC 1277 - Encoding Network Addresses to Support Operation over Non-OSI Lower Layers
- RFC 1276 - Replication and Distributed Operations extensions to provide an Internet Directory using X.500
- RFC 1275 - Replication Requirements to provide an Internet Directory using X.500
- RFC 1274 - The COSINE and Internet X.500 Schema
- RFC 1273 - Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations
- RFC 1272 - Internet Accounting: Background
- RFC 1270 - SNMP Communications Services
- RFC 1269 - Definitions of Managed Objects for the Border Gateway Protocol: Version 3
- RFC 1267 - Border Gateway Protocol 3 (BGP-3)
- RFC 1266 - Experience with the BGP Protocol
- RFC 1265 - BGP Protocol Analysis
- RFC 1264 - Internet Engineering Task Force Internet Routing Protocol Standardization Criteria
- RFC 1263 - TCP Extensions Considered Harmful
- RFC 1262 - Guidelines for Internet Measurement Activities
- RFC 1261 - Transition of Nic Services
- RFC 1260 - Not Issued
- RFC 1259 - Building the open road: The NREN as test-bed for the national public network
- RFC 1258 - BSD Rlogin
- RFC 1257 - Isochronous applications do not require jitter-controlled networks
- RFC 1256 - ICMP Router Discovery Messages
- RFC 1254 - Gateway Congestion Control Survey
- RFC 1251 - Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
- RFC 1249 - DIXIE Protocol Specification
- RFC 1246 - Experience with the OSPF Protocol
- RFC 1245 - OSPF Protocol Analysis
- RFC 1242 - Benchmarking terminology for network interconnection devices
- RFC 1241 - Scheme for an internet encapsulation protocol: Version 1
- RFC 1240 - OSI connectionless transport services on top of UDP: Version 1
- RFC 1239 - Reassignment of experimental MIBs to standard MIBs
- RFC 1238 - CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542)
- RFC 1236 - IP to X.121 address mapping for DDN
- RFC 1235 - Coherent File Distribution Protocol
- RFC 1234 - Tunneling IPX traffic through IP networks
- RFC 1230 - IEEE 802.4 Token Bus MIB
- RFC 1227 - SNMP MUX protocol and MIB
- RFC 1226 - Internet protocol encapsulation of AX.25 frames
- RFC 1224 - Techniques for managing asynchronously generated alerts
- RFC 1223 - OSI CLNS and LLC1 protocols on Network Systems HYPERchannel
- RFC 1222 - Advancing the NSFNET routing architecture
- RFC 1221 - Host Access Protocol (HAP) specification: Version 2
- RFC 1219 - On the assignment of subnet numbers
- RFC 1217 - Memo from the Consortium for Slow Commotion Research (CSCR)
- RFC 1216 - Gigabit network economics and paradigm shifts
- RFC 1215 - Convention for defining traps for use with the SNMP
- RFC 1214 - OSI internet management: Management Information Base
- RFC 1213 - Management Information Base for Network Management of TCP/IP-based internets:MIB-II
- RFC 1212 - Concise MIB definitions
- RFC 1211 - Problems with the maintenance of large mailing lists
- RFC 1210 - Network and infrastructure user requirements for transatlantic research collaboration: Brussels, July 16-18, and Washington July 24-25, 1990
- RFC 1209 - Transmission of IP datagrams over the SMDS Service
- RFC 1208 - Glossary of networking terms
- RFC 1207 - FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions
- RFC 1205 - 5250 Telnet interface
- RFC 1204 - Message Posting Protocol (MPP)
- RFC 1203 - Interactive Mail Access Protocol: Version 3
- RFC 1202 - Directory Assistance service
- RFC 1201 - Transmitting IP traffic over ARCNET networks
- RFC 1199 - Request for Comments Summary Notes: 1100-1199
- RFC 1198 - FYI on the X window system
- RFC 1197 - Using ODA for translating multimedia information
- RFC 1195 - Use of OSI IS-IS for routing in TCP/IP and dual environments
- RFC 1193 - Client requirements for real-time communication services
- RFC 1192 - Commercialization of the Internet summary report
- RFC 1191 - Path MTU discovery
- RFC 1189 - Common Management Information Services and Protocols for the Internet (CMOT and CMIP)
- RFC 1188 - Proposed Standard for the Transmission of IP Datagrams over FDDI Networks
- RFC 1187 - Bulk Table Retrieval with the SNMP
- RFC 1186 - MD4 Message Digest Algorithm
- RFC 1184 - Telnet Linemode Option
- RFC 1183 - New DNS RR Definitions
- RFC 1182 - Not Issued
- RFC 1181 - RIPE Terms of Reference
- RFC 1180 - TCP/IP tutorial
- RFC 1179 - Line printer daemon protocol
- RFC 1178 - Choosing a name for your computer
- RFC 1176 - Interactive Mail Access Protocol: Version 2
- RFC 1175 - FYI on where to start: A bibliography of internetworking information
- RFC 1174 - IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet "connected" status
- RFC 1173 - Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet
- RFC 1170 - Public key standards and licenses
- RFC 1169 - Explaining the role of GOSIP
- RFC 1168 - Intermail and Commercial Mail Relay services
- RFC 1167 - Thoughts on the National Research and Education Network
- RFC 1166 - Internet numbers
- RFC 1165 - Network Time Protocol (NTP) over the OSI Remote Operations Service
- RFC 1160 - Internet Activities Board
- RFC 1159 - Message Send Protocol
- RFC 1157 - Simple Network Management Protocol (SNMP)
- RFC 1156 - Management Information Base for network management of TCP/IP-based internets
- RFC 1155 - Structure and identification of management information for TCP/IP-based internets
- RFC 1153 - Digest message format
- RFC 1152 - Workshop report: Internet research steering group workshop on very-high-speed networks
- RFC 1151 - Version 2 of the Reliable Data Protocol (RDP)
- RFC 1150 - FYI on FYI: Introduction to the FYI Notes
- RFC 1149 - Standard for the transmission of IP datagrams on avian carriers
- RFC 1146 - TCP alternate checksum options
- RFC 1144 - Compressing TCP/IP headers for low-speed serial links
- RFC 1143 - The Q Method of Implementing TELNET Option Negotiation
- RFC 1142 - OSI IS-IS Intra-domain Routing Protocol
- RFC 1141 - Incremental updating of the Internet checksum
- RFC 1137 - Mapping between full RFC 822 and RFC 822 with restricted encoding
- RFC 1136 - Administrative Domains and Routing Domains: A model for routing in the Internet
- RFC 1135 - Helminthiasis of the Internet
- RFC 1133 - Routing between the NSFNET and the DDN
- RFC 1132 - Standard for the transmission of 802.2 packets over IPX networks
- RFC 1129 - Internet time synchronization: The Network Time Protocol
- RFC 1128 - Measured performance of the Network Time Protocol in the Internet system
- RFC 1127 - Perspective on the Host Requirements RFCs
- RFC 1126 - Goals and functional requirements for inter-autonomous system routing
- RFC 1125 - Policy requirements for inter Administrative Domain routing
- RFC 1124 - Policy issues in interconnecting networks
- RFC 1123 - Requirements for Internet hosts - application and support
- RFC 1122 - Requirements for Internet hosts - communication layers
- RFC 1121 - Act one - the poems
- RFC 1118 - Hitchhikers guide to the Internet
- RFC 1112 - Host extensions for IP multicasting
- RFC 1110 - Problem with the TCP big window option
- RFC 1109 - Report of the second Ad Hoc Network Management Review Group
- RFC 1108 - U.S
- RFC 1107 - Plan for Internet directory services
- RFC 1106 - TCP big window and NAK options
- RFC 1104 - Models of policy based routing
- RFC 1102 - Policy routing in Internet protocols
- RFC 1101 - DNS encoding of network names and other types
- RFC 1099 - Request for Comments Summary: RFC Numbers 1000-1099
- RFC 1097 - Telnet subliminal-message option
- RFC 1096 - Telnet X display location option
- RFC 1094 - NFS: Network File System Protocol specification
- RFC 1093 - NSFNET routing architecture
- RFC 1092 - EGP and policy based routing in the new NSFNET backbone
- RFC 1091 - Telnet terminal-type option
- RFC 1090 - SMTP on X.25
- RFC 1089 - SNMP over Ethernet
- RFC 1088 - Standard for the transmission of IP datagrams over NetBIOS networks
- RFC 1087 - Ethics and the Internet
- RFC 1086 - ISO-TP0 bridge between TCP and X.25
- RFC 1085 - ISO presentation services on top of TCP/IP based internets
- RFC 1082 - Post Office Protocol: Version 3: Extended service offerings
- RFC 1079 - Telnet terminal speed option
- RFC 1078 - TCP port service Multiplexer (TCPMUX)
- RFC 1077 - Critical issues in high bandwidth networking
- RFC 1076 - HEMS monitoring and control language
- RFC 1075 - Distance Vector Multicast Routing Protocol
- RFC 1074 - NSFNET backbone SPF based Interior Gateway Protocol
- RFC 1073 - Telnet window size option
- RFC 1071 - Computing the Internet checksum
- RFC 1070 - Use of the Internet as a subnetwork for experimentation with the OSI network layer
- RFC 1069 - Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol
- RFC 1068 - Background File Transfer Program (BFTP)
- RFC 1061 - Not Issued
- RFC 1058 - Routing Information Protocol
- RFC 1057 - RPC: Remote Procedure Call Protocol specification: Version 2
- RFC 1056 - PCMAIL: A distributed mail system for personal computers
- RFC 1055 - Nonstandard for transmission of IP datagrams over serial lines: SLIP
- RFC 1053 - Telnet X.3 PAD option
- RFC 1052 - IAB recommendations for the development of Internet network management standards
- RFC 1049 - Content-type header field for Internet messages
- RFC 1047 - Duplicate messages and SMTP
- RFC 1046 - Queuing algorithm to provide type-of-service for IP links
- RFC 1045 - VMTP: Versatile Message Transaction Protocol: Protocol specification
- RFC 1044 - Internet Protocol on Network System's HYPERchannel: Protocol specification
- RFC 1043 - Telnet Data Entry Terminal option: DODIIS implementation
- RFC 1042 - Standard for the transmission of IP datagrams over IEEE 802 networks
- RFC 1041 - Telnet 3270 regime option
- RFC 1039 - DoD statement on Open Systems Interconnection protocols
- RFC 1037 - NFILE - a file access protocol
- RFC 1036 - Standard for interchange of USENET messages
- RFC 1035 - Domain names - implementation and specification
- RFC 1034 - Domain names - concepts and facilities
- RFC 1033 - Domain administrators operations guide
- RFC 1032 - Domain administrators guide
- RFC 1031 - MILNET name domain transition
- RFC 1030 - On testing the NETBLT Protocol over divers networks
- RFC 1029 - More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets
- RFC 1028 - Simple Gateway Monitoring Protocol
- RFC 1027 - Using ARP to implement transparent subnet gateways
- RFC 1025 - TCP and IP bake off
- RFC 1024 - HEMS variable definitions
- RFC 1022 - High-level Entity Management Protocol (HEMP)
- RFC 1021 - High-level Entity Management System (HEMS)
- RFC 1019 - Report of the Workshop on Environments for Computational Mathematics
- RFC 1018 - Some comments on SQuID
- RFC 1017 - Network requirements for scientific research: Internet task force on scientific computing
- RFC 1016 - Something a host could do with source quench: The Source Quench Introduced Delay (SQuID)
- RFC 1015 - Implementation plan for interagency research Internet
- RFC 1014 - XDR: External Data Representation standard
- RFC 1013 - X Window System Protocol, version 11: Alpha update April 1987
- RFC 1012 - Bibliography of Request For Comments 1 through 999
- RFC 1011 - Official Internet protocols
- RFC 1008 - Implementation guide for the ISO Transport Protocol
- RFC 1007 - Military supplement to the ISO Transport Protocol
- RFC 1006 - ISO transport services on top of the TCP: Version 3
- RFC 1005 - ARPANET AHIP-E Host Access Protocol (enhanced AHIP)
- RFC 1004 - Distributed-protocol authentication scheme
- RFC 1003 - Issues in defining an equations representation standard
- RFC 1002 - Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications
- RFC 1001 - Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods
- RFC 1000 - Request For Comments reference guide
- RFC 0998 - NETBLT: A bulk data transfer protocol
- RFC 0996 - Statistics server
- RFC 0995 - End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473
- RFC 0994 - Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service
- RFC 0992 - On communication support for fault tolerant process groups
- RFC 0982 - Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address
- RFC 0981 - Experimental multiple-path routing algorithm
- RFC 0980 - Protocol document order information
- RFC 0979 - PSN End-to-End functional specification
- RFC 0978 - Voice File Interchange Protocol (VFIP)
- RFC 0977 - Network News Transfer Protocol
- RFC 0976 - UUCP mail interchange format standard
- RFC 0975 - Autonomous confederations
- RFC 0974 - Mail routing and the domain system
- RFC 0972 - Password Generator Protocol
- RFC 0971 - Survey of data representation standards
- RFC 0970 - On packet switches with infinite storage
- RFC 0968 - Twas the night before start-up
- RFC 0967 - All victims together
- RFC 0965 - Format for a graphical communication protocol
- RFC 0964 - Some problems with the specification of the Military Standard Transmission Control Protocol
- RFC 0963 - Some problems with the specification of the Military Standard Internet Protocol
- RFC 0962 - TCP-4 prime
- RFC 0959 - File Transfer Protocol
- RFC 0957 - Experiments in network clock synchronization
- RFC 0956 - Algorithms for synchronizing network clocks
- RFC 0955 - Towards a transport service for transaction processing applications
- RFC 0954 - NICNAME/WHOIS
- RFC 0953 - Hostname Server
- RFC 0952 - DoD Internet host table specification
- RFC 0951 - Bootstrap Protocol
- RFC 0950 - Internet Standard Subnetting Procedure
- RFC 0949 - FTP unique-named store command
- RFC 0947 - Multi-network broadcasting within the Internet
- RFC 0946 - Telnet terminal location number option
- RFC 0942 - Transport protocols for Department of Defense data networks
- RFC 0941 - Addendum to the network service definition covering network layer addressing
- RFC 0940 - Toward an Internet standard scheme for subnetting
- RFC 0939 - Executive summary of the NRC report on transport protocols for Department of Defense data networks
- RFC 0938 - Internet Reliable Transaction Protocol functional and interface specification
- RFC 0937 - Post Office Protocol: Version 2
- RFC 0936 - Another Internet subnet addressing scheme
- RFC 0935 - Reliable link layer protocols
- RFC 0934 - Proposed standard for message encapsulation
- RFC 0933 - Output marking Telnet option
- RFC 0932 - Subnetwork addressing scheme
- RFC 0929 - Proposed Host-Front End Protocol
- RFC 0928 - Introduction to proposed DoD standard H-FP
- RFC 0927 - TACACS user identification Telnet option
- RFC 0925 - Multi-LAN address resolution
- RFC 0922 - Broadcasting Internet datagrams in the presence of subnets
- RFC 0921 - Domain name system implementation schedule - revised
- RFC 0920 - Domain requirements
- RFC 0919 - Broadcasting Internet Datagrams
- RFC 0917 - Internet subnets
- RFC 0916 - Reliable Asynchronous Transfer Protocol (RATP)
- RFC 0915 - Network mail path service
- RFC 0914 - Thinwire protocol for connecting personal computers to the Internet
- RFC 0913 - Simple File Transfer Protocol
- RFC 0911 - EGP Gateway under Berkeley UNIX 4.2
- RFC 0910 - Multimedia mail meeting notes
- RFC 0909 - Loader Debugger Protocol
- RFC 0908 - Reliable Data Protocol
- RFC 0906 - Bootstrap loading using TFTP
- RFC 0905 - ISO Transport Protocol specification ISO DP 8073
- RFC 0904 - Exterior Gateway Protocol formal specification
- RFC 0903 - Reverse Address Resolution Protocol
- RFC 0902 - ARPA Internet Protocol policy
- RFC 0899 - Request For Comments summary notes: 800-899
- RFC 0898 - Gateway special interest group meeting notes
- RFC 0897 - Domain name system implementation schedule
- RFC 0896 - Congestion control in IP/TCP internetworks
- RFC 0895 - Standard for the transmission of IP datagrams over experimental Ethernet networks
- RFC 0894 - Standard for the transmission of IP datagrams over Ethernet networks
- RFC 0893 - Trailer encapsulations
- RFC 0891 - DCN local-network protocols
- RFC 0890 - Exterior Gateway Protocol implementation schedule
- RFC 0889 - Internet delay experiments
- RFC 0888 - "STUB" Exterior Gateway Protocol
- RFC 0887 - Resource Location Protocol
- RFC 0886 - Proposed standard for message header munging
- RFC 0885 - Telnet end of record option
- RFC 0881 - Domain names plan and schedule
- RFC 0879 - TCP maximum segment size and related topics
- RFC 0878 - ARPANET 1822L Host Access Protocol
- RFC 0876 - Survey of SMTP implementations
- RFC 0875 - Gateways, architectures, and heffalumps
- RFC 0874 - Critique of X.25
- RFC 0873 - Illusion of vendor support
- RFC 0872 - TCP-on-a-LAN
- RFC 0871 - Perspective on the ARPANET reference model
- RFC 0869 - Host Monitoring Protocol
- RFC 0868 - Time Protocol
- RFC 0867 - Daytime Protocol
- RFC 0866 - Active users
- RFC 0865 - Quote of the Day Protocol
- RFC 0864 - Character Generator Protocol
- RFC 0863 - Discard Protocol
- RFC 0862 - Echo Protocol
- RFC 0861 - Telnet Extended Options: List Option
- RFC 0860 - Telnet Timing Mark Option
- RFC 0859 - Telnet Status Option
- RFC 0858 - Telnet Suppress Go Ahead Option
- RFC 0857 - Telnet Echo Option
- RFC 0856 - Telnet Binary Transmission
- RFC 0855 - Telnet Option Specifications
- RFC 0854 - Telnet Protocol Specification
- RFC 0853 - Not Issued
- RFC 0852 - ARPANET short blocking feature
- RFC 0849 - Suggestions for improved host table distribution
- RFC 0848 - Who provides the "little" TCP services?
- RFC 0847 - Summary of Smallberg surveys
- RFC 0844 - Who talks ICMP, too? - Survey of 18 February 1983
- RFC 0841 - Specification for message format for Computer Based Message Systems
- RFC 0831 - Backup access to the European side of SATNET
- RFC 0830 - Distributed system for Internet name service
- RFC 0829 - Packet satellite technology reference sources
- RFC 0828 - Data communications: IFIP's international "network" of experts
- RFC 0827 - Exterior Gateway Protocol (EGP)
- RFC 0826 - Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48.bit Ethernet address for transmission on Ethernet hardware
- RFC 0824 - CRONUS Virtual Local Network
- RFC 0823 - DARPA Internet gateway
- RFC 0822 - Standard for the format of ARPA Internet text messages
- RFC 0821 - Simple Mail Transfer Protocol
- RFC 0819 - Domain naming convention for Internet user applications
- RFC 0818 - Remote User Telnet service
- RFC 0817 - Modularity and efficiency in protocol implementation
- RFC 0816 - Fault isolation and recovery
- RFC 0815 - IP datagram reassembly algorithms
- RFC 0814 - Name, addresses, ports, and routes
- RFC 0813 - Window and Acknowledgement Strategy in TCP
- RFC 0809 - UCL facsimile system
- RFC 0808 - Summary of computer mail services meeting held at BBN on 10 January 1979
- RFC 0807 - Multimedia mail meeting notes
- RFC 0805 - Computer mail meeting notes
- RFC 0804 - CCITT draft recommendation T.4
- RFC 0803 - Dacom 450/500 facsimile data transcoding
- RFC 0801 - NCP/TCP transition plan
- RFC 0800 - Request For Comments summary notes: 700-799
- RFC 0799 - Internet name domains
- RFC 0798 - Decoding facsimile data from the Rapicom 450
- RFC 0797 - Format for Bitmap files
- RFC 0796 - Address mappings
- RFC 0795 - Service mappings
- RFC 0794 - Pre-emption
- RFC 0793 - Transmission Control Protocol
- RFC 0792 - Internet Control Message Protocol
- RFC 0791 - Internet Protocol
- RFC 0789 - Vulnerabilities of network control protocols: An example
- RFC 0787 - Connectionless data transmission survey/tutorial
- RFC 0786 - Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface
- RFC 0785 - Mail Transfer Protocol: ISI TOPS20 file definitions
- RFC 0783 - TFTP Protocol (revision 2)
- RFC 0782 - Virtual Terminal management model
- RFC 0781 - Specification of the Internet Protocol (IP) timestamp option
- RFC 0779 - Telnet send-location option
- RFC 0778 - DCNET Internet Clock Service
- RFC 0775 - Directory oriented FTP commands
- RFC 0774 - Internet Protocol Handbook: Table of contents
- RFC 0773 - Comments on NCP/TCP mail service transition strategy
- RFC 0771 - Mail transition plan
- RFC 0769 - Rapicom 450 facsimile file format
- RFC 0768 - User Datagram Protocol
- RFC 0767 - Structured format for transmission of multi-media documents
- RFC 0763 - Role mailboxes
- RFC 0761 - DoD standard Transmission Control Protocol
- RFC 0759 - Internet Message Protocol
- RFC 0757 - Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems
- RFC 0756 - NIC name server - a datagram-based information utility
- RFC 0754 - Out-of-net host addresses for mail
- RFC 0753 - Internet Message Protocol
- RFC 0752 - Universal host table
- RFC 0751 - Survey of FTP mail and MLFL
- RFC 0749 - Telnet SUPDUP-Output option
- RFC 0748 - Telnet randomly-lose option
- RFC 0747 - Recent extensions to the SUPDUP Protocol
- RFC 0746 - SUPDUP graphics extension
- RFC 0745 - JANUS interface specifications
- RFC 0744 - MARS - a Message Archiving and Retrieval Service
- RFC 0743 - FTP extension: XRSQ/XRCP
- RFC 0741 - Specifications for the Network Voice Protocol (NVP)
- RFC 0740 - NETRJS Protocol
- RFC 0738 - Time server
- RFC 0737 - FTP extension: XSEN
- RFC 0736 - Telnet SUPDUP option
- RFC 0735 - Revised Telnet byte macro option
- RFC 0734 - SUPDUP Protocol
- RFC 0732 - Telnet Data Entry Terminal option
- RFC 0730 - Extensible field addressing
- RFC 0728 - Minor pitfall in the Telnet Protocol
- RFC 0727 - Telnet logout option
- RFC 0726 - Remote Controlled Transmission and Echoing Telnet option
- RFC 0725 - RJE protocol for a resource sharing network
- RFC 0723 - Not Issued
- RFC 0722 - Thoughts on Interactions in Distributed Services
- RFC 0721 - Out-of-Band Control Signals in a Host-to-Host Protocol
- RFC 0720 - Address Specification Syntax for Network Mail
- RFC 0719 - Discussion on RCTE
- RFC 0718 - Comments on RCTE from the Tenex Implementation Experience
- RFC 0717 - Assigned Network Numbers
- RFC 0716 - Interim Revision to Appendix F of BBN 1822
- RFC 0715 - Not Issued
- RFC 0714 - Host-Host Protocol for an ARPANET-Type Network
- RFC 0713 - MSDTP-Message Services Data Transmission Protocol
- RFC 0712 - Distributed Capability Computing System (DCCS)
- RFC 0711 - Not Issued
- RFC 0710 - Not Issued
- RFC 0709 - Not Issued
- RFC 0708 - Elements of a Distributed Programming System
- RFC 0707 - High-level framework for network-based resource sharing
- RFC 0706 - On the junk mail problem
- RFC 0705 - Front-end Protocol B6700 version
- RFC 0704 - IMP/Host and Host/IMP Protocol change
- RFC 0703 - July, 1975, survey of New-Protocol Telnet Servers
- RFC 0702 - September, 1974, survey of New-Protocol Telnet servers
- RFC 0701 - August, 1974, survey of New-Protocol Telnet servers
- RFC 0700 - Protocol experiment
- RFC 0699 - Request For Comments summary notes: 600-699
- RFC 0698 - Telnet extended ASCII option
- RFC 0697 - CWD command of FTP
- RFC 0696 - Comments on the IMP/Host and Host/IMP Protocol changes
- RFC 0695 - Official change in Host-Host Protocol
- RFC 0694 - Protocol information
- RFC 0692 - Comments on IMP/Host Protocol changes (RFCs 687 and 690)
- RFC 0691 - One more try on the FTP
- RFC 0690 - Comments on the proposed Host/IMP Protocol changes
- RFC 0689 - Tenex NCP finite state machine for connections
- RFC 0688 - Tentative schedule for the new Telnet implementation for the TIP
- RFC 0686 - Leaving well enough alone
- RFC 0685 - Response time in cross network debugging
- RFC 0684 - Commentary on procedure calling as a network protocol
- RFC 0683 - FTPSRV - Tenex extension for paged files
- RFC 0681 - Network UNIX
- RFC 0680 - Message Transmission Protocol
- RFC 0679 - February, 1975, survey of New-Protocol Telnet servers
- RFC 0678 - Standard file formats
- RFC 0677 - Maintenance of duplicate databases
- RFC 0675 - Specification of Internet Transmission Control Program
- RFC 0674 - Procedure call documents: Version 2
- RFC 0672 - Multi-site data collection facility
- RFC 0671 - Note on Reconnection Protocol
- RFC 0669 - November, 1974, survey of New-Protocol Telnet servers
- RFC 0667 - BBN host ports
- RFC 0666 - Specification of the Unified User-Level Protocol
- RFC 0663 - Lost message detection and recovery protocol
- RFC 0662 - Performance improvement in ARPANET file transfers from Multics
- RFC 0661 - Protocol information
- RFC 0660 - Some changes to the IMP and the IMP/Host interface
- RFC 0659 - Announcing additional Telnet options
- RFC 0658 - Telnet output linefeed disposition
- RFC 0657 - Telnet output vertical tab disposition option
- RFC 0656 - Telnet output vertical tabstops option
- RFC 0655 - Telnet output formfeed disposition option
- RFC 0654 - Telnet output horizontal tab disposition option
- RFC 0653 - Telnet output horizontal tabstops option
- RFC 0652 - Telnet output carriage-return disposition option
- RFC 0647 - Proposed protocol for connecting host computers to ARPA-like networks via front end processors
- RFC 0645 - Network Standard Data Specification syntax
- RFC 0644 - On the problem of signature authentication for network mail
- RFC 0643 - Network Debugging Protocol
- RFC 0642 - Ready line philosophy and implementation
- RFC 0640 - Revised FTP reply codes
- RFC 0638 - IMP/TIP preventive maintenance schedule
- RFC 0637 - Change of network address for SU-DSL
- RFC 0636 - TIP/Tenex reliability improvements
- RFC 0635 - Assessment of ARPANET protocols
- RFC 0634 - Change in network address for Haskins Lab
- RFC 0632 - Throughput degradations for single packet messages
- RFC 0631 - International meeting on minicomputers and data communication: Call for papers
- RFC 0630 - FTP error code usage for more reliable mail service
- RFC 0629 - Scenario for using the Network Journal
- RFC 0628 - Status of RFC numbers and a note on pre-assigned journal numbers
- RFC 0627 - ASCII text file of hostnames
- RFC 0626 - On a possible lockup condition in IMP subnet due to message sequencing
- RFC 0625 - On-line hostnames service
- RFC 0624 - Comments on the File Transfer Protocol
- RFC 0623 - Comments on on-line host name service
- RFC 0622 - Scheduling IMP/TIP down time
- RFC 0621 - NIC user directories at SRI ARC
- RFC 0620 - Request for monitor host table updates
- RFC 0619 - Mean round-trip times in the ARPANET
- RFC 0618 - Few observations on NCP statistics
- RFC 0617 - Note on socket number assignment
- RFC 0616 - Latest network maps
- RFC 0615 - Proposed Network Standard Data Pathname syntax
- RFC 0614 - Response to RFC 607: "Comments on the File Transfer Protocol"
- RFC 0613 - Network connectivity: A response to RFC 603
- RFC 0612 - Traffic statistics (December 1973)
- RFC 0611 - Two changes to the IMP/Host Protocol to improve user/network communications
- RFC 0610 - Further datalanguage design concepts
- RFC 0609 - Statement of upcoming move of NIC/NLS service
- RFC 0606 - Host names on-line
- RFC 0603 - Response to RFC 597: Host status
- RFC 0602 - "The stockings were hung by the chimney with care"
- RFC 0601 - Traffic statistics (November 1973)
- RFC 0600 - Interfacing an Illinois plasma terminal to the ARPANET
- RFC 0597 - Host status
- RFC 0596 - Second thoughts on Telnet Go-Ahead
- RFC 0595 - Second thoughts in defense of the Telnet Go-Ahead
- RFC 0594 - Speedup of Host-IMP interface
- RFC 0593 - Telnet and FTP implementation schedule change
- RFC 0592 - Some thoughts on system design to facilitate resource sharing
- RFC 0591 - Addition to the Very Distant Host specifications
- RFC 0590 - MULTICS address change
- RFC 0589 - CCN NETRJS server messages to remote user
- RFC 0588 - London node is now up
- RFC 0587 - Announcing new Telnet options
- RFC 0586 - Traffic statistics (October 1973)
- RFC 0585 - ARPANET users interest working group meeting
- RFC 0584 - Charter for ARPANET Users Interest Working Group
- RFC 0582 - Comments on RFC 580: Machine readable protocols
- RFC 0581 - Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option
- RFC 0580 - Note to Protocol Designers and Implementers
- RFC 0579 - Traffic statistics (September 1973)
- RFC 0578 - Using MIT-Mathlab MACSYMA from MIT-DMS Muddle
- RFC 0577 - Mail priority
- RFC 0576 - Proposal for modifying linking
- RFC 0574 - Announcement of a mail facility at UCSB
- RFC 0573 - Data and file transfer: Some measurement results
- RFC 0571 - Tenex FTP problem
- RFC 0570 - Experimental input mapping between NVT ASCII and UCSB On Line System
- RFC 0569 - NETED: A Common Editor for the ARPA Network
- RFC 0568 - Response to RFC 567 - cross country network bandwidth
- RFC 0567 - Cross Country Network Bandwidth
- RFC 0566 - Traffic statistics (August 1973)
- RFC 0565 - Storing network survey data at the datacomputer
- RFC 0563 - Comments on the RCTE Telnet option
- RFC 0562 - Modifications to the Telnet specification
- RFC 0561 - Standardizing Network Mail Headers
- RFC 0560 - Remote Controlled Transmission and Echoing Telnet option
- RFC 0559 - Comments on The New Telnet Protocol and its Implementation
- RFC 0557 - Revelations in network host measurements
- RFC 0556 - Traffic statistics (July 1973)
- RFC 0555 - Responses to critiques of the proposed mail protocol
- RFC 0553 - Draft design for a text/graphics protocol
- RFC 0552 - Single access to standard protocols
- RFC 0550 - NIC NCP experiment
- RFC 0549 - Minutes of Network Graphics Group meeting, 15-17 July 1973
- RFC 0548 - Hosts using the IMP Going Down message
- RFC 0547 - Change to the Very Distant Host specification
- RFC 0546 - Tenex load averages for July 1973
- RFC 0545 - Of what quality be the UCSB resources evaluators?
- RFC 0544 - Locating on-line documentation at SRI-ARC
- RFC 0543 - Network journal submission and delivery
- RFC 0539 - Thoughts on the mail protocol proposed in RFC 524
- RFC 0538 - Traffic statistics (June 1973)
- RFC 0537 - Announcement of NGG meeting July 16-17
- RFC 0535 - Comments on File Access Protocol
- RFC 0534 - Lost message detection
- RFC 0533 - Message-ID numbers
- RFC 0532 - UCSD-CC Server-FTP facility
- RFC 0531 - Feast or famine? A response to two recent RFC's about network information
- RFC 0530 - Report on the Survey project
- RFC 0529 - Note on protocol synch sequences
- RFC 0528 - Software checksumming in the IMP and network reliability
- RFC 0527 - ARPAWOCKY
- RFC 0526 - Technical meeting: Digital image processing software systems
- RFC 0525 - MIT-MATHLAB meets UCSB-OLS -an example of resource sharing
- RFC 0524 - Proposed Mail Protocol
- RFC 0523 - SURVEY is in operation again
- RFC 0522 - Traffic statistics (May 1973)
- RFC 0521 - Restricted use of IMP DDT
- RFC 0520 - Memo to FTP group: Proposal for File Access Protocol
- RFC 0519 - Resource evaluation
- RFC 0518 - ARPANET accounts
- RFC 0516 - Lost message detection
- RFC 0515 - Specifications for datalanguage: Version 0/9
- RFC 0514 - Network make-work
- RFC 0513 - Comments on the new Telnet specifications
- RFC 0512 - More on lost message detection
- RFC 0511 - Enterprise phone service to NIC from ARPANET sites
- RFC 0510 - Request for network mailbox addresses
- RFC 0509 - Traffic statistics (April 1973)
- RFC 0508 - Real-time data transmission on the ARPANET
- RFC 0506 - FTP command naming problem
- RFC 0505 - Two solutions to a file transfer access problem
- RFC 0504 - Distributed resources workshop announcement
- RFC 0501 - Un-muddling "free file transfer"
- RFC 0500 - Integration of data management systems on a computer network
- RFC 0499 - Harvard's network RJE
- RFC 0498 - On mail service to CCN
- RFC 0497 - Traffic statistics (March 1973)
- RFC 0496 - TNLS quick reference card is available
- RFC 0495 - Telnet Protocol specifications
- RFC 0494 - Availability of MIX and MIXAL in the Network
- RFC 0493 - Graphics Protocol
- RFC 0492 - Response to RFC 467
- RFC 0491 - What is "Free"?
- RFC 0490 - Surrogate RJS for UCLA-CCN
- RFC 0489 - Comment on resynchronization of connection status proposal
- RFC 0488 - NLS classes at network sites
- RFC 0487 - Free file transfer
- RFC 0486 - Data transfer revisited
- RFC 0485 - MIX and MIXAL at UCSB
- RFC 0483 - Cancellation of the resource notebook framework meeting
- RFC 0482 - Traffic statistics (February 1973)
- RFC 0480 - Host-dependent FTP parameters
- RFC 0479 - Use of FTP by the NIC Journal
- RFC 0478 - FTP server-server interaction - II
- RFC 0477 - Remote Job Service at UCSB
- RFC 0476 - IMP/TIP memory retrofit schedule (rev 2)
- RFC 0475 - FTP and network mail system
- RFC 0474 - Announcement of NGWG meeting: Call for papers
- RFC 0473 - MIX and MIXAL?
- RFC 0472 - Illinois' reply to Maxwell's request for graphics information (NIC 14925)
- RFC 0471 - Workshop on multi-site executive programs
- RFC 0470 - Change in socket for TIP news facility
- RFC 0469 - Network mail meeting summary
- RFC 0468 - FTP data compression
- RFC 0467 - Proposed change to Host-Host Protocol: Resynchronization of connection status
- RFC 0466 - Telnet logger/server for host LL-67
- RFC 0464 - Resource notebook framework
- RFC 0463 - FTP comments and response to RFC 430
- RFC 0462 - Responding to user needs
- RFC 0461 - Telnet Protocol meeting announcement
- RFC 0460 - NCP survey
- RFC 0459 - Network questionnaires
- RFC 0458 - Mail retrieval via FTP
- RFC 0457 - TIPUG
- RFC 0456 - Memorandum: Date change of mail meeting
- RFC 0455 - Traffic statistics (January 1973)
- RFC 0454 - File Transfer Protocol - meeting announcement and a new proposed document
- RFC 0453 - Meeting announcement to discuss a network mail system
- RFC 0452 - TELENET Command at Host LL
- RFC 0451 - Tentative proposal for a Unified User Level Protocol
- RFC 0450 - MULTICS sampling timeout change
- RFC 0449 - Current flow-control scheme for IMPSYS
- RFC 0448 - Print files in FTP
- RFC 0446 - Proposal to consider a network program resource notebook
- RFC 0445 - IMP/TIP preventive maintenance schedule
- RFC 0443 - Traffic statistics (December 1972)
- RFC 0442 - Current flow-control scheme for IMPSYS
- RFC 0441 - Inter-Entity Communication - an experiment
- RFC 0440 - Scheduled network software maintenance
- RFC 0439 - PARRY encounters the DOCTOR
- RFC 0438 - FTP server-server interaction
- RFC 0437 - Data Reconfiguration Service at UCSB
- RFC 0436 - Announcement of RJS at UCSB
- RFC 0435 - Telnet issues
- RFC 0432 - Network logical map
- RFC 0431 - Update on SMFS Login and Logout
- RFC 0430 - Comments on File Transfer Protocol
- RFC 0429 - Character Generator Process
- RFC 0426 - Reconnection Protocol
- RFC 0425 - "But my NCP costs $500 a day"
- RFC 0423 - UCLA Campus Computing Network Liaison Staff for ARPANET
- RFC 0422 - Traffic statistics (November 1972)
- RFC 0421 - Software Consulting Service for Network Users
- RFC 0420 - CCA ICCC weather demo
- RFC 0419 - To: Network liaisons and station agents
- RFC 0418 - Server file transfer under TSS/360 at NASA Ames
- RFC 0417 - Link usage violation
- RFC 0416 - ARC System Will Be Unavailable for Use During Thanksgiving Week
- RFC 0415 - Tenex bandwidth
- RFC 0414 - File Transfer Protocol (FTP) status and further comments
- RFC 0413 - Traffic statistics (October 1972)
- RFC 0412 - User FTP Documentation
- RFC 0411 - New MULTICS Network Software Features
- RFC 0410 - Removal of the 30-Second Delay When Hosts Come Up
- RFC 0409 - Tenex interface to UCSB's Simple-Minded File System
- RFC 0408 - NETBANK
- RFC 0407 - Remote Job Entry Protocol
- RFC 0406 - Scheduled IMP Software Releases
- RFC 0405 - Correction to RFC 404
- RFC 0404 - Host Address Changes Involving Rand and ISI
- RFC 0403 - Desirability of a network 1108 service
- RFC 0402 - ARPA Network Mailing Lists
- RFC 0401 - Conversion of NGP-0 Coordinates to Device Specific Coordinates
- RFC 0400 - Traffic Statistics (September 1972)
- RFC 0398 - ICP Sockets
- RFC 0396 - Network Graphics Working Group Meeting - Second Iteration
- RFC 0395 - Switch Settings on IMPs and TIPs
- RFC 0394 - Two Proposed Changes to the IMP-Host Protocol
- RFC 0393 - Comments on Telnet Protocol Changes
- RFC 0392 - Measurement of host costs for transmitting network data
- RFC 0391 - Traffic statistics (August 1972)
- RFC 0390 - TSO Scenario
- RFC 0388 - NCP statistics
- RFC 0387 - Some experiences in implementing Network Graphics Protocol Level 0
- RFC 0386 - Letter to TIP users-2
- RFC 0385 - Comments on the File Transfer Protocol
- RFC 0384 - Official site idents for organizations in the ARPA Network
- RFC 0382 - Mathematical Software on the ARPA Network
- RFC 0381 - Three aids to improved network operation
- RFC 0379 - Using TSO at CCN
- RFC 0377 - Using TSO via ARPA Network Virtual Terminal
- RFC 0376 - Network Host Status
- RFC 0374 - IMP System Announcement
- RFC 0373 - Arbitrary Character Sets
- RFC 0372 - Notes on a Conversation with Bob Kahn on the ICCC
- RFC 0371 - Demonstration at International Computer Communications Conference
- RFC 0369 - Evaluation of ARPANET services January-March, 1972
- RFC 0368 - Comments on "Proposed Remote Job Entry Protocol"
- RFC 0365 - Letter to All TIP Users
- RFC 0364 - Serving remote users on the ARPANET
- RFC 0361 - Deamon Processes on Host 106
- RFC 0359 - Status of the Release of the New IMP System (2600)
- RFC 0357 - Echoing strategy for satellite links
- RFC 0356 - ARPA Network Control Center
- RFC 0355 - Response to NWG/RFC 346
- RFC 0352 - TIP Site Information Form
- RFC 0351 - Graphics information form for the ARPANET graphics resources notebook
- RFC 0350 - User Accounts for UCSB On-Line System
- RFC 0348 - Discard Process
- RFC 0347 - Echo process
- RFC 0346 - Satellite Considerations
- RFC 0345 - Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN)
- RFC 0340 - Proposed Telnet Changes
- RFC 0339 - MLTNET: A "Multi Telnet" Subsystem for Tenex
- RFC 0338 - EBCDIC/ASCII Mapping for Network RJE
- RFC 0336 - Level 0 Graphic Input Protocol
- RFC 0335 - New Interface - IMP/360
- RFC 0334 - Network Use on May 8
- RFC 0333 - Proposed experiment with a Message Switching Protocol
- RFC 0328 - Suggested Telnet Protocol Changes
- RFC 0327 - Data and File Transfer workshop notes
- RFC 0325 - Network Remote Job Entry program - NETRJS
- RFC 0324 - RJE Protocol meeting
- RFC 0323 - Formation of Network Measurement Group (NMG)
- RFC 0322 - Well known socket numbers
- RFC 0321 - CBI Networking Activity at MITRE
- RFC 0320 - Workshop on Hard Copy Line Printers
- RFC 0318 - Telnet Protocols
- RFC 0316 - ARPA Network Data Management Working Group
- RFC 0314 - Network Graphics Working Group Meeting
- RFC 0313 - Computer based instruction
- RFC 0312 - Proposed Change in IMP-to-Host Protocol
- RFC 0311 - New Console Attachments to the USCB Host
- RFC 0310 - Another Look at Data and File Transfer Protocols
- RFC 0309 - Data and File Transfer Workshop Announcement
- RFC 0308 - ARPANET host availability data
- RFC 0307 - Using network Remote Job Entry
- RFC 0305 - Unknown Host Numbers
- RFC 0304 - Data management system proposal for the ARPA network
- RFC 0302 - Exercising The ARPANET
- RFC 0301 - BBN IMP (#5) and NCC Schedule March 4, 1971
- RFC 0299 - Information Management System
- RFC 0297 - TIP Message Buffers
- RFC 0296 - DS-1 display system
- RFC 0295 - Report of the Protocol Workshop, 12 October 1971
- RFC 0294 - The Use of "Set Data Type" Transaction in File Transfer Protocol
- RFC 0292 - Graphics Protocol: Level 0 only
- RFC 0291 - Data Management Meeting Announcement
- RFC 0290 - Computer networks and data sharing: A bibliography
- RFC 0286 - Network Library Information System
- RFC 0285 - Network graphics
- RFC 0283 - NETRJT: Remote Job Service Protocol for TIPS
- RFC 0282 - Graphics meeting report
- RFC 0281 - Suggested addition to File Transfer Protocol
- RFC 0280 - A Draft of Host Names
- RFC 0278 - Revision of the Mail Box Protocol
- RFC 0276 - NIC course
- RFC 0274 - Establishing a local guide for network usage
- RFC 0273 - More on standard host names
- RFC 0271 - IMP System change notifications
- RFC 0270 - Correction to BBN Report No
- RFC 0269 - Some Experience with File Transfer
- RFC 0268 - Graphics facilities information
- RFC 0263 - "Very Distant" Host interface
- RFC 0256 - IMPSYS change notification
- RFC 0254 - Scenarios for using ARPANET computers
- RFC 0253 - Second Network Graphics meeting details
- RFC 0251 - Weather data
- RFC 0250 - Some thoughts on file transfer
- RFC 0249 - Coordination of equipment and supplies purchase
- RFC 0247 - Proffered set of standard host names
- RFC 0246 - Network Graphics meeting
- RFC 0245 - Reservations for Network Group meeting
- RFC 0242 - Data Descriptive Language for Shared Data
- RFC 0241 - Connecting computers to MLC ports
- RFC 0239 - Host mnemonics proposed in RFC 226 (NIC 7625)
- RFC 0238 - Comments on DTP and FTP proposals
- RFC 0236 - Standard host names
- RFC 0234 - Network Working Group meeting schedule
- RFC 0233 - Standardization of host call letters
- RFC 0232 - Postponement of network graphics meeting
- RFC 0231 - Service center standards for remote usage: A user's view
- RFC 0230 - Toward reliable operation of minicomputer-based terminals on a TIP
- RFC 0228 - Clarification
- RFC 0227 - Data transfer rates (Rand/UCLA)
- RFC 0225 - Rand/UCSB network graphics experiment
- RFC 0224 - Comments on Mailbox Protocol
- RFC 0223 - Network Information Center schedule for network users
- RFC 0222 - Subject: System programmer's workshop
- RFC 0219 - User's view of the datacomputer
- RFC 0218 - Changing the IMP status reporting facility
- RFC 0217 - Specifications changes for OLS, RJE/RJOR, and SMFS
- RFC 0216 - Telnet access to UCSB's On-Line System
- RFC 0215 - NCP, ICP, and Telnet: The Terminal IMP implementation
- RFC 0214 - Network checkpoint
- RFC 0213 - IMP System change notification
- RFC 0212 - NWG meeting on network usage
- RFC 0210 - Improvement of Flow Control
- RFC 0209 - Host/IMP interface documentation
- RFC 0208 - Address tables
- RFC 0206 - User Telnet - description of an initial implementation
- RFC 0205 - NETCRT - a character display protocol
- RFC 0204 - Sockets in use
- RFC 0203 - Achieving reliable communication
- RFC 0202 - Possible Deadlock in ICP
- RFC 0199 - Suggestions for a network data-tablet graphics protocol
- RFC 0197 - Initial Connection Protocol - Reviewed
- RFC 0195 - Data computers-data descriptions and access language
- RFC 0194 - The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes
- RFC 0192 - Some factors which a Network Graphics Protocol must consider
- RFC 0191 - Graphics implementation and conceptualization at Augmentation Research Center
- RFC 0190 - DEC PDP-10-IMLAC communications system
- RFC 0188 - Data management meeting announcement
- RFC 0187 - Network/440 Protocol Concept
- RFC 0186 - Network graphics loader
- RFC 0185 - NIC distribution of manuals and handbooks
- RFC 0184 - Proposed graphic display modes
- RFC 0183 - EBCDIC codes and their mapping to ASCII
- RFC 0182 - Compilation of list of relevant site reports
- RFC 0181 - Modifications to RFC 177
- RFC 0180 - File system questionnaire
- RFC 0179 - Link Number Assignments
- RFC 0178 - Network graphic attention handling
- RFC 0177 - Device independent graphical display description
- RFC 0176 - Comments on "Byte size for connections"
- RFC 0175 - Comments on "Socket Conventions Reconsidered"
- RFC 0174 - UCLA - Computer Science Graphics Overview
- RFC 0173 - Network Data Management Committee Meeting Announcement
- RFC 0169 - Computer networks
- RFC 0167 - Socket conventions reconsidered
- RFC 0166 - Data Reconfiguration Service: An implementation specification
- RFC 0165 - Proffered official Initial Connection Protocol
- RFC 0164 - Minutes of Network Working Group meeting, 5/16 through 5/19/71
- RFC 0163 - Data transfer protocols
- RFC 0162 - NETBUGGER3
- RFC 0161 - Solution to the race condition in the ICP
- RFC 0157 - Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems
- RFC 0156 - Status of the Illinois site: Response to RFC 116
- RFC 0154 - Exposition Style
- RFC 0153 - SRI ARC-NIC status
- RFC 0152 - SRI Artificial Intelligence status report
- RFC 0151 - Comments on a proffered official ICP: RFCs 123, 127
- RFC 0150 - Use of IPC Facilities: A Working Paper
- RFC 0149 - Best Laid Plans
- RFC 0148 - Comments on RFC 123
- RFC 0147 - Definition of a socket
- RFC 0146 - Views on issues relevant to data sharing on computer networks
- RFC 0144 - Data sharing on computer networks
- RFC 0142 - Time-Out Mechanism in the Host-Host Protocol
- RFC 0141 - Comments on RFC 114: A File Transfer Protocol
- RFC 0140 - Agenda for the May NWG meeting
- RFC 0139 - Discussion of Telnet Protocol
- RFC 0138 - Status report on proposed Data Reconfiguration Service
- RFC 0137 - Telnet Protocol - a proposed document
- RFC 0136 - Host accounting and administrative procedures
- RFC 0135 - Response to NWG/RFC 110
- RFC 0134 - Network Graphics meeting
- RFC 0133 - File Transfer and Recovery
- RFC 0131 - Response to RFC 116: May NWG meeting
- RFC 0130 - Response to RFC 111: Pressure from the chairman
- RFC 0129 - Request for comments on socket name structure
- RFC 0128 - Bytes
- RFC 0126 - Graphics Facilities at Ames Research Center
- RFC 0125 - Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream
- RFC 0124 - Typographical error in RFC 107
- RFC 0122 - Network specifications for UCSB's Simple-Minded File System
- RFC 0121 - Network on-line operators
- RFC 0120 - Network PL1 subprograms
- RFC 0119 - Network Fortran subprograms
- RFC 0118 - Recommendations for facility documentation
- RFC 0117 - Some comments on the official protocol
- RFC 0116 - Structure of the May NWG Meeting
- RFC 0115 - Some Network Information Center policies on handling documents
- RFC 0114 - File Transfer Protocol
- RFC 0113 - Network activity report: UCSB Rand
- RFC 0112 - User/Server Site Protocol: Network host questionnaire responses
- RFC 0111 - Pressure from the Chairman
- RFC 0110 - Conventions for using an IBM 2741 terminal as a user console for access to network server hosts
- RFC 0109 - Level III Server Protocol for the Lincoln Laboratory NIC 360/67 Host
- RFC 0108 - Attendance list at the Urbana NWG meeting, February 17-19, 1971
- RFC 0107 - Output of the Host-Host Protocol Glitch Cleaning Committee
- RFC 0106 - User/Server Site Protocol Network Host Questionnaire
- RFC 0105 - Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB
- RFC 0104 - Link 191
- RFC 0103 - Implementation of Interrupt Keys
- RFC 0102 - Output of the Host-Host Protocol glitch cleaning committee
- RFC 0101 - Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971
- RFC 0100 - Categorization and guide to NWG/RFCs
- RFC 0099 - Network Meeting
- RFC 0098 - Logger Protocol Proposal
- RFC 0097 - First Cut at a Proposed Telnet Protocol
- RFC 0096 - An Interactive Network Experiment to Study Modes of Access the Network Information Center
- RFC 0094 - Some thoughts on Network Graphics
- RFC 0093 - Initial Connection Protocol
- RFC 0091 - Proposed User-User Protocol
- RFC 0090 - CCN as a Network Service Center
- RFC 0089 - Some historic moments in networking
- RFC 0087 - Topic for Discussion at the Next Network Working Group Meeting
- RFC 0086 - Proposal for a Network Standard Format for a Data Stream to Control Graphics Display
- RFC 0085 - Network Working Group meeting
- RFC 0084 - List of NWG/RFC's 1-80
- RFC 0083 - Language-machine for data reconfiguration
- RFC 0082 - Network Meeting Notes
- RFC 0081 - Request for Reference Information
- RFC 0079 - Logger Protocol error
- RFC 0078 - NCP Status Report: UCSB/Rand
- RFC 0077 - Network meeting report
- RFC 0076 - Connection by name: User oriented protocol
- RFC 0075 - Network Meeting
- RFC 0074 - Specifications for network use of the UCSB On-Line System
- RFC 0073 - Response to NWG/RFC 67
- RFC 0072 - Proposed Moratorium on Changes to Network Protocol
- RFC 0071 - Reallocation in Case of Input Error
- RFC 0070 - Note on Padding
- RFC 0069 - Distribution List Change for MIT
- RFC 0068 - Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM
- RFC 0067 - Proposed Change to Host/IMP Spec to Eliminate Marking
- RFC 0065 - Comments on Host/Host Protocol document #1
- RFC 0064 - Getting rid of marking
- RFC 0063 - Belated Network Meeting Report
- RFC 0062 - Systems for Interprocess Communication in a Resource Sharing Computer Network
- RFC 0060 - Simplified NCP Protocol
- RFC 0059 - Flow Control - Fixed Versus Demand Allocation
- RFC 0058 - Logical Message Synchronization
- RFC 0057 - Thoughts and Reflections on NWG/RFC 54
- RFC 0056 - Third Level Protocol: Logger Protocol
- RFC 0055 - Prototypical implementation of the NCP
- RFC 0054 - Official Protocol Proffering
- RFC 0053 - Official protocol mechanism
- RFC 0052 - Updated distribution list
- RFC 0051 - Proposal for a Network Interchange Language
- RFC 0050 - Comments on the Meyer Proposal
- RFC 0049 - Conversations with S
- RFC 0048 - Possible protocol plateau
- RFC 0047 - BBN's Comments on NWG/RFC #33
- RFC 0046 - ARPA Network protocol notes
- RFC 0045 - New Protocol is Coming
- RFC 0044 - Comments on NWG/RFC 33 and 36
- RFC 0043 - Proposed Meeting
- RFC 0042 - Message Data Types
- RFC 0041 - IMP-IMP Teletype Communication
- RFC 0040 - More Comments on the Forthcoming Protocol
- RFC 0039 - Comments on Protocol Re: NWG/RFC #36
- RFC 0038 - Comments on Network Protocol from NWG/RFC #36
- RFC 0037 - Network Meeting Epilogue, etc
- RFC 0036 - Protocol Notes
- RFC 0035 - Network Meeting
- RFC 0034 - Some Brief Preliminary Notes on the Augmentation Research Center Clock
- RFC 0033 - New Host-Host Protocol
- RFC 0032 - Connecting M.I.T
- RFC 0031 - Binary Message Forms in Computer
- RFC 0030 - Documentation Conventions
- RFC 0029 - Response to RFC 28
- RFC 0028 - Time Standards
- RFC 0027 - Documentation Conventions
- RFC 0025 - No High Link Numbers
- RFC 0024 - Documentation Conventions
- RFC 0023 - Transmission of Multiple Control Messages
- RFC 0022 - Host-host control message formats
- RFC 0021 - Network meeting
- RFC 0020 - ASCII format for network interchange
- RFC 0019 - Two protocol suggestions to reduce congestion at swap bound nodes
- RFC 0018 - IMP-IMP and HOST-HOST Control Links
- RFC 0017 - Some questions re: Host-IMP Protocol
- RFC 0015 - Network subsystem for time sharing hosts
- RFC 0013 - Zero Text Length EOF Message
- RFC 0012 - IMP-Host interface flow diagrams
- RFC 0009 - Host software
- RFC 0008 - Functional specifications for the ARPA Network
- RFC 0007 - Host-IMP interface
- RFC 0006 - Conversation with Bob Kahn
- RFC 0005 - Decode Encode Language (DEL)
- RFC 0004 - Network timetable
- RFC 0002 - Host software
- RFC 0001 - Host Software

[ Index | Search | What's New | Comments | Help ]