RFC 1799

Request for Comments Summary RFC Numbers 1700-1799

📅 published January 1997, from ietf

Request for Comments Summary ✨

okay bestie, this one is RFC 1799, the "Request for Comments Summary" 🎀 It's a list covering RFC 1700 through RFC 1799 (RFC Numbers 1700-1799), written by M. Kennedy from ISI. It's an Informational RFC dated January 1997, and its header doesn't list anything it obsoletes or updates 💅

Status of This Memo

okay so this section explains what the doc even is 🧐 It's a slightly annotated list of the 100 RFCs from RFC 1700 through RFC 1799, and it's basically a status report on them. It gives info to the Internet community but doesn't specify an Internet standard of any kind. Distribution is unlimited, so share it with everyone 💖

Note

ngl this part is so important 🫶 Lots of RFCs (but not all!) are Proposed Standards, Draft Standards, or Standards. Since their status can change during standards processing, this list only says whether they're on the standards track. For the current state, go check the latest edition of "Internet Official Protocol Standards" 📚 In the list below, anything on the standards track gets tagged [STANDARDS-TRACK] 🔥

RFC List: 1799 Down to 1771 📋

Here's the table header, exactly as it's written:

RFC     Author       Date      Title
---     ------       ----      -----

RFC 1799

1799    Kennedy     Jan 97     Requests For Comments Summary

okay this is literally this memo, the summary itself 🌸

RFC 1798

1798    Young       Jun 95      Connection-less Lightweight X.500
                                Directory Access Protocol

this one is giving access to the Directory without the heavy resource needs of the Directory Access Protocol (DAP) 🧚 It's on the standards track: [STANDARDS-TRACK] ✨

RFC 1797

1797    IANA        Apr 95     Class A Subnet Experiment

people are curious about subnetting class A addresses, so this one suggests running an experiment now 🧪 The goal is to find and fix any software that doesn't handle subnetted class A addresses properly. It defines an Experimental Protocol for the Internet community, and it doesn't specify an Internet standard of any kind 🦋

RFC 1796

1796    Huitema     Apr 95      Not All RFCs are Standards

this one talks about how RFCs relate to Internet Standards, which is so relevant 🙈 It's informational and doesn't specify an Internet standard of any kind 💜

RFC 1795

1795     Wells      Apr 95      Data Link Switching: Switch-to-Switch
                                Protocol
                                AIW DLSw RIG: DLSw Closed Pages, DLSw
                                Standard Version 1.0

this one describes using Data Link Switching over TCP/IP 🌈 It's informational and doesn't specify an Internet standard of any kind 🍓

RFC 1794

1794     Brisco     Apr 95     DNS Support for Load Balancing

this one is a whole story 📖 It starts with a trip into the IETF DNS Working Group, looks at other ways to provide or simulate load balancing for DNS, and then aims for a flexible solution that can balance many kinds of loads. It's informational and doesn't specify an Internet standard of any kind ✨

RFC 1793

1793     Moy         Apr 95    Extending OSPF to Support Demand Circuits

this one adds enhancements to OSPF so it can run efficiently over "demand circuits" ⚡ It's on the standards track: [STANDARDS-TRACK] 💅

RFC 1792

1792     Sung        Apr 95    TCP/IPX Connection Mib Specification

this one brings in new MIB objects (tcpIpxConnTable, udpIpxTable, tcpUnspecConnTable and udpUnspecTable) 🎀 They replace tcpConnTable and udpListenerTable when TCP and UDP run over IPX. It's an Experimental Protocol and doesn't specify an Internet standard of any kind 🦋

RFC 1791

1791    Sung        Apr 95    TCP And UDP Over IPX Networks With
                               Fixed Path MTU

this one lets TCP/IP applications run over IPX networks by running TCP and UDP over IPX 🌸 It also specifies the packet format and operational procedures for doing that. It's an Experimental Protocol and doesn't specify an Internet standard of any kind 💖

RFC 1790

1790    Cerf         Apr 95    An Agreement between the Internet
                               Society and Sun Microsystems, Inc.
                               in the Matter of ONC RPC and XDR
                               Protocols

this one is an official public record of an agreement between SUN Microsystems and the Internet Society 📜 It's informational and doesn't specify an Internet standard of any kind 🫶

RFC 1789

1789    Yang        Apr 95     INETPhone: Telephone Services and
                               Servers on Internet

this one presents a real telephone service called INETPhone, which supports voice calls over the Internet 📞 It's informational and doesn't specify an Internet standard of any kind 🧚

RFC 1788

1788    Simpson     Apr 95     ICMP Domain Name Messages

this one specifies ICMP messages for learning the Fully Qualified Domain Name tied to an IP address 🔍 It's an Experimental Protocol and doesn't specify an Internet standard of any kind 🦋

RFC 1787

1787    Rekhter    Apr 95     Routing in a Multi-provider Internet

this one looks at the issues in network layer routing across a multi-provider Internet, especially unicast routing 🌐 It's informational and doesn't specify an Internet standard of any kind 💜

RFC 1786

1786    Bates      Mar 95     Representation of IP Routing Policies

this one is an update to the original `ripe-81' proposal for representing and storing routing policies in the RIPE database 🗂️ It adds several extensions proposed by Merit Inc. and gives details of a generalized IP routing policy representation for all Internet routing registries. It works as both a tutorial and a detailed guide to the database objects and attributes that make up a routing registry 🍓 It's informational and doesn't specify an Internet standard of any kind ✨

RFC 1785

1785    Malkin     Mar 95     TFTP Option Negotiation Analysis

this one was written to ease worries that options in a TFTP Request packet could cause pathological behavior on servers that don't support TFTP option negotiation 🙏 It's informational and doesn't specify an Internet standard of any kind 🌸

RFC 1784

1784    Malkin     Mar 95    TFTP Timeout Interval and Transfer
                             Size Options

this one describes two TFTP options 🧁 The first lets the client and server negotiate the Timeout Interval. The second lets the side receiving the file find out the final size of the transfer before it starts. It's on the standards track: [STANDARDS-TRACK] 🔥

RFC 1783

1783    Malkin     Mar 95    TFTP Blocksize Option

this one describes a TFTP option that lets the client and server negotiate a blocksize that fits the network medium better 📦 It's on the standards track: [STANDARDS-TRACK] 💅

RFC 1782

1782    Malkin     Mar 95    TFTP Option Extension

okay so TFTP is a simple, lock-step file transfer protocol that lets a client get or put a file onto a remote host 🗃️ This one adds a simple extension that allows option negotiation before the transfer happens ✨

RFC 1781

1781    Kille     Mar 95     Using the OSI Directory to Achieve
                            User Friendly Naming

this one sets out some conventions for representing names in a friendly way and shows how that can lead to really friendly naming 💖 It's on the standards track: [STANDARDS-TRACK] 🫶

RFC 1780

1780   IAB       Mar 95    Internet Official Protocol Standards

this one describes the state of standardization for protocols used on the Internet, as determined by the Internet Architecture Board (IAB) 👑 It's on the standards track: [STANDARDS-TRACK] 🔥

RFC 1779

1779   Kille     Mar 95     A String Representation of Distinguished
                            Names

okay so the OSI Directory uses distinguished names as the primary keys for its entries, and they're encoded in ASN.1 🧠 When they get passed between users who aren't using a directory protocol (like in a mail message), you need a user-friendly string version. This spec defines a string format that cleanly represents commonly used names and can still represent any distinguished name 💜 It's on the standards track: [STANDARDS-TRACK] 🌈

RFC 1778

1778   Howes    Mar 95     The String Representation of Standard
                           Attribute Syntaxes

the Lightweight Directory Access Protocol (LDAP) needs the contents of AttributeValue fields in protocol elements to be octet strings 🧩 This doc lays out the requirements that encoding rules must satisfy when they turn X.500 Directory attribute syntaxes into a form LDAP can use. Then it defines those encoding rules for the standard set of attribute syntaxes 🎀 It's on the standards track: [STANDARDS-TRACK] 💅

RFC 1777

1777   Yeong     Mar 95     Lightweight Directory Access Protocol

this one is LDAP itself 🧚 It's designed to give access to the X.500 Directory without the heavy resource needs of the Directory Access Protocol (DAP). It's aimed at simple management applications and browser apps that want simple read/write interactive access to the X.500 Directory, and it's meant to complement DAP itself 🫶 It's on the standards track: [STANDARDS-TRACK] 🔥

RFC 1776

1776   Crocker   Apr 95     The Address is the Message

the IPng WG said "the address is the message" and picked a packet format with 1696 bytes of address space 🫣 It's informational and doesn't specify an Internet standard of any kind 💜

RFC 1775

1775   Crocker   Mar 95    To Be "On" the Internet

okay so the Internet offers different levels of access to consumers and providers, and those differences matter a lot for what you can do 🌐 This doc suggests four terms to tell the major classes of access apart, so the community can be clear about whether a user (or an organization) is "on" the Internet 🦋 It's informational and doesn't specify an Internet standard of any kind ✨

RFC 1774

1774   Traina   Mar 95    BGP-4 Protocol Analysis

this report documents how BGP-4 meets the requirements for moving a routing protocol to Draft Standard 📊 It summarizes BGP's key features and analyzes the protocol for scaling and performance 💖 It's informational and doesn't specify an Internet standard of any kind 🍓

RFC 1773

1773    Traina  Mar 95   Experience with the BGP-4 protocol

this memo also documents how BGP-4 meets the requirements for moving a routing protocol to Draft Standard 🌸 This one focuses on experience with BGP. It's informational and doesn't specify an Internet standard of any kind 🫶

RFC 1772

1772   Rekhter  Mar 95   Application of the Border Gateway
                         Protocol in the Internet

this one works together with its companion document, "A Border Gateway Protocol 4 (BGP-4)" 🌉 Together they define an inter-autonomous system routing protocol for the Internet. This doc describes how BGP is used on the Internet. It's on the standards track: [STANDARDS-TRACK] 👑

RFC 1771

1771   Rekhter  Mar 95   A Border Gateway Protocol 4 (BGP-4)

the description for this entry isn't included in this part, so it picks up in the next part 🧚 stay tuned, bestie 💜

Okay so this one's a pair with its companion doc, "Application of the Border Gateway Protocol in the Internet" 💖. Together they define an inter-autonomous system routing protocol for the Internet 🌐 [STANDARDS-TRACK]

1770   Graff   Mar 95   IPv4 Option for Sender Directed
                        Multi-Destination Delivery

Bestie, this one defines an IPv4 option 🎀 that gives you a sender directed multi-destination delivery mechanism, aka Selective Directed Broadcast Mode (SDBM) ✨ It's info for the Internet community, and it doesn't specify an Internet standard of any kind 🫶

1769   Mills   Mar 95   Simple Network Time Protocol (SNTP)

This one describes SNTP 🕰️, which is a lighter adaptation of NTP for syncing computer clocks across the Internet ⏰ Just info for the Internet community. It doesn't specify an Internet standard of any kind 💅

1768   Marlow  Mar 95   Host Group Extensions for CLNP Multicasting

Okay this spec gives CLNP multicast extensions that are giving IPv4 RFC1112 vibes 🦋 It defines an Experimental Protocol for the Internet community, and it doesn't specify an Internet standard of any kind 🧪

1767   Crocker  Mar 95   MIME Encapsulation of EDI Objects

Since there are so many different EDI specs 📦 this doc sorts them into three distinct categories, each one its own MIME content-type 💜 [STANDARDS-TRACK]

1766   Alvestrand Mar 95  Tags for the Identification of Languages

This doc is all about a language tag 🌍 for when you want to indicate which language an information object is in ✨ [STANDARDS-TRACK]

1765   Moy       Mar 95   OSPF Database Overflow

Here's a way to handle unexpected database overflows gracefully in OSPF 🌊 It defines an Experimental Protocol for the Internet community, and it doesn't specify an Internet standard of any kind 🙈

1764   Senum     Mar 95   The PPP XNS IDP Control Protocol (XNSCP)

This one defines the Network Control Protocol for setting up and configuring Xerox Network Systems (XNS) Internet Datagram Protocol (IDP) over PPP 🎀 [STANDARDS-TRACK]

1763   Senum     Mar 95   The PPP Banyan Vines Control Protocol (BVCP)

Same energy as the one above, but for Banyan VINES over PPP 💅 It defines the Network Control Protocol for establishing and configuring Banyan VINES 🧚 [STANDARDS-TRACK]

1762   Senum     Mar 95   The PPP DECnet Phase IV Control Protocol
                          (DNCP)

Bestie this is the NCP for setting up and configuring Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP 🌸 Important tea: it only applies to DNA Phase IV Routing messages (both data and control) 🫢 It does not apply to other DNA Phase IV protocols (MOP, LAT, etc) 🙅‍♀️ [STANDARDS-TRACK]

1761   Callaghan  Feb 95  Snoop Version 2 Packet Capture File Format

This paper describes the file format used by "snoop", a packet monitoring and capture program developed by Sun 🔍 It's shared so people can write compatible programs that generate and interpret snoop packet capture files 🛠️ Info for the Internet community, no Internet standard of any kind 💖

1760   Haller     Feb 95  The S/KEY One-Time Password System

This one describes the S/KEY* One-Time Password system, as Bellcore released it for public use 🔐 It's info for the Internet community, and it doesn't specify an Internet standard of any kind 🫶

1759   Smith      Mar 95  Printer MIB

So a printer is the physical device that takes media from an input source, makes marks on it based on a page description or page control language, and sends the result to an output destination, maybe with finishing applied 🖨️ Managing the physical printer and managing a print job overlap a LOT, and lots of tasks in each area need the same or similar info 🌈 [STANDARDS-TRACK]

1758   N.A.D.F.   Feb 95    NADF Standing Documents: A Brief Overview

This doc gives a quick overview of the NADF's Standing Document series 📚 It's info for the Internet community, and it doesn't specify an Internet standard of any kind ✨

1757   Waldbusser Feb 95   Remote Network Monitoring Management
                           Information Base

This memo defines a piece of the Management Information Base (MIB) for network management protocols in TCP/IP-based internets 👑 Specifically, it defines objects for managing remote network monitoring devices 📡 [STANDARDS-TRACK]

1756    Rinne     Jan 95   REMOTE WRITE PROTOCOL - VERSION 1.0

Bestie, this one describes a simple Remote Write Protocol (RWP) 💌 It defines an Experimental Protocol for the Internet community, and it doesn't specify an Internet standard of any kind 🧪

1755    Perez     Feb 95   ATM Signaling Support for IP over ATM

This memo describes the ATM call control signaling exchanges needed to support Classical IP over ATM, the way RFC 1577 describes it 🦋 [STANDARDS-TRACK]

1754    Laubach   Jan 95   IP over ATM Working Group's
                           Recommendations for the ATM Forum's
                           Multiprotocol BOF
                           Version 1

This doc is an initial list of requirements sent to the ATM Forum's Multiprotocol BOF for running IP over ATM networks 🌐 It was put together by the IETF IP over ATM Working Group and other working groups 🫶 It's info for the Internet community, and it doesn't specify an Internet standard of any kind 💅

1753     Chiappa   Dec 94   IPng Technical Requirements
                            Of the Nimrod Routing and Addressing
                            Architecture

This doc lays out the requirements the Nimrod routing and addressing architecture puts on the internetwork layer protocol 🧚 To be most useful to Nimrod, any protocol picked as the IPng should satisfy these requirements ✨ It's info for the Internet community, and it doesn't specify an Internet standard of any kind 🌸

1752     Bradner   Jan 95   The Recommendation for the IP Next
                            Generation Protocol

This doc is the IPng Area Directors' pick for what should replace the current version of the Internet Protocol 👑 [STANDARDS-TRACK]

1751     McDonald   Dec 94   A Convention for Human-Readable 128-bit
                             Keys

This memo proposes a convention for Internet apps and protocols that use 128-bit cryptographic keys 🔑 It's info for the Internet community, and it doesn't specify an Internet standard of any kind 💖

1750     Eastlake    Dec 94  Randomness Recommendations for Security

Choosing random quantities to foil a resourceful and motivated adversary is SO much harder than it sounds 😭 This paper calls out a bunch of pitfalls in using traditional pseudo-random number generation for picking those quantities 🎲 It recommends truly random hardware techniques, and shows that the hardware already on many systems can be used for this 🔥 It's info for the Internet community, and it doesn't specify an Internet standard of any kind 🫶

1749   McCloghrie    Dec 94   IEEE 802.5 Station Source Routing MIB
                              using SMIv2

This memo defines a piece of the Management Information Base (MIB) for network management protocols in the Internet community 🛰️ It describes managed objects used by IEEE 802.5 end-stations to manage source routes on a Token Ring network where IEEE source-routing is in use 🌊 [STANDARDS-TRACK]

1748   McCloghrie    Dec 94   IEEE 802.5 MIB using SMIv2

This memo defines another piece of the MIB for network management protocols in the Internet community 🧩 It describes managed objects for subnetworks that use the IEEE 802.5 Token Ring technology from 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989 💍 [STANDARDS-TRACK]

1747   Hilgeman     Jan 95   Definitions of Managed Objects for SNA
                             Data Link Control (SDLC) using SMIv2

This spec extends the MIB for SNMP-based network management 🧠 It defines objects for managing the configuration, monitoring and control of data link controls in an SNA environment 🌷 [STANDARDS-TRACK]

1746   Manning      Dec 94   Ways to Define User Expectations

This paper covers the basics you need to understand when you define, interpret, or implement ways to control user expectations on or over the Internet 🧸 It's info for the Internet community, and it doesn't specify an Internet standard of any kind ✨

1745    Varadhan     Dec 94   BGP4/IDRP for IP---OSPF Interaction

Bestie, this memo sets out the criteria for designing an Autonomous System Border Router (ASBR) that runs either BGP4 or IDRP for IP 🌉 It talks to other ASBRs outside the AS, and uses OSPF as its IGP 🦋 [STANDARDS-TRACK]

1744     Huston      Dec 94   Observations on the Management of
                              the Internet Address Space

This memo looks at the issues with how the current IPv4 address space is managed on the Internet 🌍 It also looks at what could happen as the unallocated address pool shrinks 😬 It's info for the Internet community, and it doesn't specify an Internet standard of any kind 💜

1743     McCloghrie  Dec 94    IEEE 802.5 MIB using SMIv2

Yep, another MIB for the Internet community 🧩 This one describes managed objects for subnetworks running IEEE 802.5 Token Ring tech, as laid out in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989 🎀 [STANDARDS-TRACK]

1742     Waldbusser  Jan 95    AppleTalk Management Information Base II

This memo defines a piece of the MIB for network management protocols in TCP/IP-based internets 🍎 In particular, it defines objects for managing AppleTalk networks 🌈 [STANDARDS-TRACK]

1741     Falstrom     Dec 94  MIME Content Type for BinHex Encoded Files

This memo describes the format to use when sending BinHex4.0 files via MIME [BORE93] 📁 It's info for the Internet community, and it doesn't specify an Internet standard of any kind 💖

1740     Falstron     Dec 94   MIME Encapsulation of Macintosh Files -
                               MacMIME

This one describes the format for sending Apple Macintosh files via MIME [BORE93] 🍏 [STANDARDS-TRACK]

1739     Kessler       Dec 94   A Primer On Internet and TCP/IP Tools

Bestie, this is the intro guide to a bunch of TCP/IP and Internet tools and utilities 🧭 They let you do everything from checking if a host is up to viewing a multimedia thesis on foreign policy 🎓 It also covers discussion lists you can reach from the Internet, ways to get Internet documents, and resources for finding your way around the Internet 🗺️ It's info for the Internet community, and it doesn't specify an Internet standard of any kind 🫶

1738     Berners-Lee   Dec 94   Uniform Resource Locators (URL)

Okay this one specifies a Uniform Resource Locator (URL) 🔗 It's giving the syntax and semantics of formalized information for location and access of resources 💕

...zipping across the Internet. [STANDARDS-TRACK]

Heads up, bestie: the text you pasted is the RFC index listing for RFCs 1706 through 1737, not the body of RFC 1799, so this part rewrites that listing. If you meant RFC 1799 itself, send me its text and I'll redo it properly. 🎀

1737. Functional Requirements for Uniform Resource Names ✨

1737     Sollins       Dec 94   Functional Requirements for Uniform
                                Resource Names

okay so this one sets the minimum requirements for URNs (Uniform Resource Names), which are a kind of Internet resource identifier 🆔. It's giving "here's the bare minimum you need to have a URN that actually works." This memo is just information for the Internet community. It doesn't specify an Internet standard of any kind 💅

1736. Functional Recommendations for Internet Resource Locators 🌸

1736     Kunze        Feb 95    Functional Recommendations for
                                Internet Resource Locators

this doc lays out a minimum set of requirements for Internet resource locators, the things that carry location and access info for resources 📍 Info-only vibes for the Internet community. Not a standard of any kind, bestie 🫶

1735. NBMA Address Resolution Protocol (NARP) 🦋

1735     Heinanen     Dec 94    NBMA Address Resolution Protocol (NARP)

ngl this one is so cute. NARP describes how a source terminal (a host or a router) connected to a Non-Broadcast, Multi-Access (NBMA) link layer network can find out the NBMA addresses of a destination terminal. The catch is the destination has to be connected to that same NBMA network 🔍 This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind ✨

1734. POP3 AUTHentication command 💜

1734     Myers        Dec 94   POP3 AUTHentication command

okay this is giving authentication glow-up 🔐 The doc covers the optional AUTH command, which tells the server which authentication mechanism you want, runs the authentication exchange, and can also negotiate a protection mechanism for the stuff you do afterwards. [STANDARDS-TRACK] 🎀

1733. Distributed Electronic Mail Models in IMAP4 📬

1733     Crispin      Dec 94   Distributed Electronic Mail
                               Models in IMAP4

there are three fundamental models of client/server email: offline, online, and disconnected use 🌈 IMAP4 works with any one of those three. This memo provides information for the Internet community, and it doesn't specify an Internet standard of any kind 💖

1732. IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS 🍓

1732     Crispin      Dec 94   IMAP4 COMPATIBILITY WITH IMAP2
                               AND IMAP2BIS

this is a little summary of hints and recommendations so an IMAP4 implementation can play nicely with implementations that follow the earlier specs 🤝 Info for the Internet community, no standard here, bestie.

1731. IMAP4 Authentication Mechanisms 🔑

1731    Myers         Dec 94   IMAP4 Authentication Mechanisms

so the Internet Message Access Protocol, Version 4 [IMAP4] has the AUTHENTICATE command. That's how you identify and authenticate a user to an IMAP4 server, and you can optionally negotiate a protection mechanism for later interactions too 🛡️ This doc describes several authentication mechanisms you can use with AUTHENTICATE. [STANDARDS-TRACK] ✨

1730. Internet Message Access Protocol - Version 4 📧

1730    Crispin       Dec 94   Internet Message Access Protocol
                               - Version 4

the Internet Message Access Protocol, Version 4 (IMAP4) is the one that lets a client access and manipulate email messages sitting on a server 💌 It handles remote message folders, called "mailboxes", in a way that works just like local mailboxes. It also lets an offline client resynchronize with the server once it's back online 🔄 [STANDARDS-TRACK] 👑

1729. Using the Z39.50 Information Retrieval Protocol in the Internet Environment 📚

1729    Lynch        Dec 94    Using the Z39.50 Information
                               Retrieval Protocol in the Internet
                               Environment

this memo describes one way to implement the ANSI/NISO Z39.50-1992 Standard for Information Retrieval in a TCP/IP environment 📖 It's already in wide use by the Z39.50 implementor community, so it's a real-life slay. Info only for the Internet community, not a standard of any kind.

1728. Resource Transponders 🧚

1728    Weider      Dec 94    Resource Transponders

this paper describes an automatic mechanism called the resource transponder, which keeps resource location information up to date ⭐ It's information for the Internet community, and it doesn't specify an Internet standard of any kind.

1727. A Vision of an Integrated Internet Information Service 🌟

1727    Weider      Dec 94    A Vision of an Integrated Internet
                              Information Service

this paper is giving big vision energy 🔮 It lays out how Internet information services might get integrated over the next few years, and it gets into the steps needed to make that happen. Info for the Internet community only, no standard here 💜

1726. Technical Criteria for Choosing IP The Next Generation (IPng) 🦋

1726    Partridge   Dec 94   Technical Criteria for Choosing
                             IP The Next Generation (IPng)

this RFC lays out criteria related to mobility that you should think about when designing and picking the Next Generation of IP 🌈 It's info for the Internet community, and it doesn't specify an Internet standard of any kind.

1725. Post Office Protocol - Version 3 📮

1725    Myers       Nov 94   Post Office Protocol - Version 3

ok so this memo is a revision to RFC 1460, which was a Draft Standard 🎀 [STANDARDS-TRACK] 💅

1724. RIP Version 2 MIB Extension 🎀

1724    Malkin      Nov 94   RIP Version 2 MIB Extension

this memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets 🛠️ Specifically, it defines objects for managing RIP Version 2. [STANDARDS-TRACK] ✨

1723. RIP Version 2 Carrying Additional Information 🍓

1723     Malkin     Nov 94    RIP Version 2
                             Carrying Additional Information

this document extends the Routing Information Protocol (RIP) so it can carry more useful info in RIP messages and add a little bit of security 🔐 This memo obsoletes RFC 1388, which was an update to the "Routing Information Protocol" STD 34, RFC 1058. [STANDARDS-TRACK] 👑

1722. RIP Version 2 Protocol Applicability Statement 🌸

1722     Malkin     Nov 94    RIP Version 2 Protocol Applicability
                             Statement

as required by Routing Protocol Criteria (RFC 1264), this report defines where RIP-2 applies within the Internet 🗺️ It's a prerequisite for moving RIP-2 forward on the standards track. [STANDARDS-TRACK] 🫶

1721. RIP Version 2 Protocol Analysis 🔍

1721    Malkin    Nov 94    RIP Version 2 Protocol Analysis

as required by Routing Protocol Criteria (RFC 1264), this report documents the key features of RIP-2 and the implementation experience so far 🧠 It's also a prerequisite for advancing RIP-2 on the standards track. This memo provides information for the Internet community, and it doesn't specify an Internet standard of any kind.

1720. Internet Official Protocol Standards 🏛️

1720    IAB       Nov 94    Internet Official Protocol Standards

this memo describes where the protocols used on the Internet stand in terms of standardization, as determined by the Internet Architecture Board (IAB) 👑 [STANDARDS-TRACK] ✨

1719. A Direction for IPng Specification and Implementation 🧭

1719    Gross     Dec 94    A Direction for IPng
                              Specification and Implementation

this RFC specifies criteria related to mobility that you should consider when designing and selecting the Next Generation of IP 🌈 It's info for the Internet community, and it doesn't specify an Internet standard of any kind 💖

1718. The Tao of IETF 🧘‍♀️

1718    IETF Secretariat  Nov 94   The Tao of IETF
                                   A Guide for New Attendees of the
                                   Internet Engineering Task Force

the purpose of this For Your Information (FYI) RFC is to explain to newcomers how the IETF works 🎀 This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17] 🫶

1717. The PPP Multilink Protocol (MP) 🔗

1717    Sklower        Nov 94     The PPP Multilink Protocol (MP)

this document proposes a method for splitting datagrams across multiple logical data links, recombining them, and sequencing them 🧩 [STANDARDS-TRACK] 🔥

1716. Towards Requirements for IP Routers 🛣️

1716    Almquist       Nov 94     Towards Requirements for IP Routers

the goal here is to replace RFC-1009, Requirements for Internet Gateways ([INTRO:1]), with a new document 💅 It defines and discusses requirements for devices that perform the network layer forwarding function of the Internet protocol suite. This memo provides information for the Internet community, and it doesn't specify an Internet standard of any kind ✨

1715. The H Ratio for Address Assignment Efficiency 📊

1715    Huitema        Nov 94     The H Ratio for Address Assignment
                                  Efficiency

this document was submitted to the IETF IPng area in response to RFC 1550 🌸 It's info for the Internet community, and it doesn't specify an Internet standard of any kind.

1714. Referral Whois Protocol (RWhois) 🔎

1714    Williamson     Nov 94     Referral Whois Protocol (RWhois)

this memo describes version 1.0 of the client/server interaction in RWhois 🤓 RWhois gives you a distributed system for displaying hierarchical information. Info for the Internet community, not a standard of any kind, bestie 💜

1713. Tools for DNS debugging 🛠️

1713    Romao          Nov 94      Tools for DNS debugging

ngl DNS is everywhere and most of the time nobody even notices it 🙈 People, especially administrators, tend to overlook possible anomalies as long as the apps that need name-to-address mapping keep working. This document presents some tools domain administrators can use to detect and correct those anomalies 🔧 This memo provides information for the Internet community, and it doesn't specify an Internet standard of any kind.

1712. DNS Encoding of Geographical Location 🌍

1712    Farrell        Nov 94     DNS Encoding of Geographical Location

this document defines the format of a new Resource Record (RR) for the Domain Naming System (DNS), and it reserves a matching DNS type mnemonic and numerical code 🗺️ This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind 🧪

1711. Classifications in E-mail Routing 📨

1711     Houttuin      Oct 94     Classifications in E-mail Routing

this paper presents a classification for e-mail routing issues 🗂️ It's info for the Internet community, and it doesn't specify an Internet standard of any kind.

1710. Simple Internet Protocol Plus White Paper ⚡

1710     Hinden       Oct 94      Simple Internet Protocol Plus
                                  White Paper

this document was submitted to the IETF IPng area in response to RFC 1550 💖 It's info for the Internet community, and it doesn't specify an Internet standard of any kind ✨

1709. K-12 Internetworking Guidelines 🏫

1709     Gargano      Nov 94     K-12 Internetworking Guidelines

the K-12 community traditionally hasn't had this level of staffing for telecommunications planning 😭 This document is meant to bridge that gap. It gives a recommended technical direction, an intro to the role the Internet now plays in K-12 education, and technical guidelines for building a campus data communications infrastructure that offers internetworking services and connections to the Internet 🎒 This memo provides information for the Internet community, and it doesn't specify an Internet standard of any kind.

1708. NTP PICS PROFORMA For the Network Time Protocol Version 3 ⏰

1708     Gowin       Oct 94      NTP PICS PROFORMA
                                 For the Network Time Protocol
                                 Version 3

this RFC describes a PICS Proforma that's been translated into an Internet-friendly form 🎀 It's info for the Internet community, and it doesn't specify an Internet standard of any kind.

1707. CATNIP: Common Architecture for the Internet 🐈

1707     McGovern    Oct 94     CATNIP: Common Architecture for
                                the Internet

this document was submitted to the IETF IPng area in response to RFC 1550 🌈 This paper describes a common architecture for the network layer protocol. This memo provides information for the Internet community, and it doesn't specify an Internet standard of any kind 💜

1706. DNS NSAP Resource Records 🧩

1706    Manning     Oct 94     DNS NSAP Resource Records

this document defines the format of one new Resource Record (RR) for the DNS, used for mapping domain names to NSAPs 🗺️ The RR can be used with any NSAP address format. Status-wise, this memo provides information for the Internet

community. This memo does not specify an Internet standard of any kind. So yeah, it's just info for the Internet community, and it's not a standard of any kind 🙅‍♀️✨

1705    Carlson     Oct 94      Six Virtual Inches to the Left:
                                The Problem with IPng

Okay this one is so iconic 💅 It was submitted to the IETF IPng area as a response to RFC 1550. The big idea is a brand new TCP (TCPng) and UDP, which should be developed and deployed. It's info only, not a standard 🦋

1704    Haller      Oct 94      On Internet Authentication

Haller goes through a whole spectrum of authentication technologies 🔐 and gives protocol developers tips on which kinds of authentication could fit which kinds of protocols and applications used on the Internet. Also info only, bestie, not a standard 💜

1703    Rose       Oct 94      Principles of Operation for the TPC.INT
                               Subdomain:
                               Radio Paging -- Technical Procedures

This one is giving pager nostalgia 📟 It describes a technique for radio paging using the Internet mail infrastructure. It focuses on the case where radio pagers are identified through the international telephone network 📞 Info for the community, not a standard 🌸

1702    Hanks       Oct 94    Generic Routing Encapsulation over
                              IPv4 networks

Hanks is talking about using IP as the delivery protocol, or as the payload protocol, and the extra spicy case where IP is both the delivery and the payload 🍓 It also describes using IP addresses and autonomous system numbers as part of a GRE source route. Info only, not a standard 🧚

1701    Hanks       Oct 94   Generic Routing Encapsulation (GRE)

This one is the main event 👑 It specifies a protocol for encapsulating an arbitrary network layer protocol inside another arbitrary network layer protocol. Yes, you read that right, it's that flexible. Info for the community, not a standard 🌈

1700    Reynolds     Oct 94      Assigned Numbers

This is basically a snapshot of an ongoing process 📸 It's where protocol parameters for the Internet protocol suite get assigned. To keep things easy to find, the assignments live in a set of online text files that stay up-to-date. This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community 🎀

Security Considerations ✨

Security issues are not discussed in this memo. 🙈 It doesn't go there at all, so don't go assuming it covers any of this, bestie.

Author's Address 💌

Mary Kennedy at the University of Southern California's Information Sciences Institute is the one behind this, and here's how to reach her 🫶

   Mary Kennedy
   University of Southern California
   Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA 90292

   Phone:  (310) 822-1511

   EMail:  MKENNEDY@ISI.EDU

📦 where this page comes from

ietf: rfc1799 1997-01
💖 girlified by claude-haiku-5-5 on 2026-10-15: a language model's rewrite of the original, under its terms