RFC 1399
Summary of 1300-1399
RFC 1399: Request for Comments Summary 💖
Okay bestie, so this is RFC 1399 🎀 by J. Elliott at ISI, part of the Network Working Group ✨. It's filed as Informational and dated January 1997. It's a summary of RFC numbers 1300-1399, and its header doesn't list anything it obsoletes or updates 🧚
Status of This Memo 🌸
This RFC is a slightly annotated list of the 100 RFCs from RFC 1300 through RFCs 1399. It's a status report on those RFCs. This memo provides information for the Internet community, and it does not specify an Internet standard of any kind. Distribution of this memo is unlimited 💅
Note 🦋
Plenty of these RFCs (but not all!) are Proposed Standards, Draft Standards, or Standards. Their status can change during standards processing, so we're only noting here that they're on the standards track. For the current state and status of these RFCs, check the latest edition of "Internet Official Protocol Standards" 📚 In the list below, RFCs on the standards track are marked [STANDARDS-TRACK] 🫶
The Index 🎀
RFC Author Date Title
--- ------ ---- -----
1399 Elliott Jan 97 Requests For Comments SummaryRFC 1399 ✨
This is literally just "This memo." 🙈 Which, fair, it's this doc!
RFC 1398 💖
1398 Kastenholz Jan 93 Definitions of Managed Objects for the
Ethernet-like Interface TypesThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. It's giving objects for managing Ethernet-like objects 🔥 [STANDARDS-TRACK]
RFC 1397 🌈
1397 Haskin Jan 93 Default Route Advertisement In BGP2 and
BGP3 Versions of the Border Gateway
ProtocolThis document spells out the recommendation of the BGP Working Group on default route advertisement support in BGP2 [1] and BGP3 [2] versions of the Border Gateway Protocol. [STANDARDS-TRACK] 🦋
RFC 1396 🌸
1396 Crocker Jan 93 The Process for Organization of Internet
StandardsThis report summarizes the POISED Working Group (WG), from the events that led to forming the WG through the end of 1992. This memo provides information for the Internet community. It does not specify an Internet standard 📚
RFC 1395 🧚
1395 Reynolds Jan 93 BOOTP Vendor Information ExtensionsThis RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo will be updated as additional tags are defined. This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16 for Swap Server, and Tag 17 for Root Path 🎀 It's a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP) ✨
RFC 1394 💜
1394 Robinson Jan 93 Relationship of Telex Answerback Codes
to Internet DomainsThis RFC gives the list, as best known, of all common Internet domains and the conversion between specific country telex answerback codes and Internet country domain identifiers. It also lists the telex code and international dialing code, wherever it's available. It will also list major Internet "Public" E-Mail addresses. This memo provides information for the Internet community. It does not specify an Internet standard 💅
RFC 1393 🍓
1393 Malkin Jan 93 Traceroute Using an IP OptionThis document specifies a new IP option and ICMP message type. It duplicates the functionality of the existing traceroute method while generating fewer packets and completing in a shorter time. This memo defines an Experimental Protocol for the Internet community ⭐
RFC 1392 🫶
1392 Malkin Jan 93 Internet Users' GlossaryThere are many networking glossaries out there. This one concentrates on terms that are specific to the Internet 📖 This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1391 🌈
1391 Malkin Jan 93 The Tao of IETF
A Guide for New Attendees of the
Internet Engineering Task ForceThe purpose of this For Your Information (FYI) RFC is to explain to newcomers how the IETF works. It'll give them a warm, fuzzy feeling and help them make the meeting more productive for everyone 🥰 This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1390 🦋
1390 Katz Jan 93 Transmission of IP and ARP over FDDI
NetworksThis memo defines a method for encapsulating Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] ✨
RFC 1389 💖
1389 Malkin Jan 93 RIP Version 2 MIB ExtensionThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] 🔥
RFC 1388 👑
1388 Malkin Jan 93 RIP Version 2
Carrying Additional InformationThis document specifies an extension of the Routing Information Protocol (RIP), as defined in [1]. It expands the amount of useful information carried in RIP packets and adds a measure of security 🔐 [STANDARDS-TRACK]
RFC 1387 🌸
1387 Malkin Jan 93 RIP Version 2 Protocol AnalysisAs required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This memo provides information for the Internet community. It does not specify an Internet standard 📚
RFC 1386 🎀
1386 Cooper Dec 92 The US DomainThis is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard 🇺🇸
RFC 1385 🧚
1385 Wang Nov 92 EIP: The Extended Internet Protocol
A Framework for Maintaining Backward
CompatibilityEIP can substantially reduce the amount of modifications needed to current Internet systems and greatly ease the difficulties of transition. This is an "idea" paper, and discussion is strongly encouraged on Big-Internet@munnari.oz.au. This memo provides information for the Internet community. It does not specify an Internet standard 💡
RFC 1384 🫶
1384 Barker Jan 93 Naming Guidelines for Directory PilotsThis document defines a number of naming guidelines. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. It does not specify an Internet standard 🌷
RFC 1383 💜
1383 Huitema Dec 92 An Experiment in DNS Based IP RoutingPotential solutions to the routing explosion. This memo defines an Experimental Protocol for the Internet community 🧪
RFC 1382 🍓
1382 Throop Nov 92 SNMP MIB Extension for the X.25 Packet
LayerThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] ✨
RFC 1381 🌈
1381 Throop Nov 92 SNMP MIB Extension for X.25 LAPBThis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Link Layer of X.25, LAPB. [STANDARDS-TRACK] 🦋
RFC 1380 🌸
1380 Gross Nov 92 IESG Deliberations on Routing and
AddressingThis memo summarizes issues surrounding the routing and addressing scaling problems in the IP architecture. It also gives a brief background of the ROAD group and related activities in the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard 🗺️
RFC 1379 👑
1379 Braden Nov 92 Extending TCP for Transactions --
ConceptsThis memo discusses extending TCP to provide transaction-oriented service, without altering its virtual-circuit operation. This memo provides information for the Internet community. It does not specify an Internet standard 💅
RFC 1378 🎀
1378 Parker Nov 92 The PPP AppleTalk Control Protocol
(ATCP)This document defines the NCP for establishing and configuring the AppleTalk Protocol [3] over PPP. [STANDARDS-TRACK] 🍎
RFC 1377 💖
1377 Katz Nov 92 The PPP OSI Network Layer Control
Protocol (OSINLCP)This document defines the NCP for establishing and configuring OSI Network Layer Protocols. [STANDARDS-TRACK] 🔧
RFC 1376 🧚
1376 Senum Nov 92 The PPP DECnet Phase IV Control
Protocol (DNCP)This document defines the NCP for establishing and configuring Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. It applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc.). [STANDARDS-TRACK] 🌐
RFC 1375 🌈
1375 Robinson Oct 92 Suggestion for New Classes of IP
AddressesThis RFC suggests changing the method of specifying the IP address to add new classes of networks called F, G, H, and K. The goal is to reduce wasted address space and increase the available IP address number space, especially for smaller organizations or classes of connectors that don't need or want a full Class C IP address 🫧 This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1374 🦋
1374 Renwick Oct 92 IP and ARP on HIPPIThe ANSI X3T9.3 committee has drafted a proposal for encapsulating IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. Another X3T9.3 draft describes the operation of HIPPI physical switches. X3T9.3 chose to leave HIPPI networking issues largely outside the scope of their standards. This document discusses ways to use ANSI standard HIPPI hardware and protocols in the context of the Internet, including using HIPPI switches as LANs and interoperating with other networks. This memo is intended to become an Internet Standard. [STANDARDS-TRACK] ⚡
RFC 1373 🌸
1373 Tignor Oct 92 PORTABLE DUAsThis document comes in two parts. The first part is for regular people who want to set up their own DUAs (Directory User Interfaces) to access the Directory. The second part is for ISODE-maintainers who want to provide portable DUAs to users. It gives instructions in a similar but longer, step-by-step format. This memo provides information for the Internet community. It does not specify an Internet standard 📝
RFC 1372 💜
1372 Hedrick Oct 92 Telnet Remote Flow Control OptionThis document specifies an extended version of the Telnet Remote Flow Control Option, RFC 1080, with the addition of the RESTART-ANY and RESTART-XON suboptions. [STANDARDS-TRACK] 🎛️
RFC 1371 👑
1371 Gross Oct 92 Choosing a "Common IGP" for the IP
Internet
(The IESG's Recommendation to the IAB)This memo presents the motivation, rationale, and other background information behind the IESG's recommendation to the IAB for a single "common IGP" for the IP portions of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard 🗳️
RFC 1370 🍓
1370 I.A.B. Oct 92 Applicability Statement for OSPFThis Applicability Statement places a requirement on vendors claiming conformance to this standard. It's there to make sure users have the option of deploying OSPF when they need a multivendor, interoperable IGP in their environment. [STANDARDS-TRACK] 🛠️
RFC 1369 🫶
1369 Kastenholz Oct 92 Implementation Notes and Experience for
The Internet Ethernet MIBThis document reflects the currently known status of 11 different
to be continued in part 2 🧚💜
implementations of the MIB, built by 7 different vendors on 7 different Ethernet interface chips 💅 This one's info for the Internet community, not a standard, so no pressure to implement it 🫶
Heads up: this stretch is actually the RFC index listing (RFCs 1339 to 1368), not RFC 1399's body text, so I've kept the entries as they're listed.
RFC 1368 · McMaster · Oct 92 Definitions of Managed Objects for IEEE 802.3 Repeater Devices
This one defines a chunk of the Management Information Base (MIB) for network management protocols in TCP/IP-based internets 🧚 Specifically, it's all about objects for managing IEEE 802.3 10 Mb/second baseband repeaters, aka "hubs" 🔥 [STANDARDS-TRACK]
RFC 1367 · Topolcic · Oct 92 Schedule for IP Address Space Management Guidelines
This memo suggests a schedule for putting the IP network number allocation plan from RFC 1366 into action 📅 Info for the Internet community, not a standard 🌸
RFC 1366 · Gerich · Oct 92 Guidelines for Management of IP Address Space
This doc got reviewed by the Federal Engineering Task Force (FEPG) on behalf of the Federal Networking Council (FNC), plus the co-chairs of the International Engineering Planning Group (IEPG) and the Reseaux IP Europeens (RIPE) 👑 Those groups generally agreed to back the recommendations for managing the IP address space ✨ Info only, not a standard.
RFC 1365 · Siyan · Spt 92 An IP Address Extension Proposal
This RFC proposes an extension to IP to fix the shortage of IP addresses problem, and it's asking for discussion and suggestions for improvements 🦋 Info only, not a standard.
RFC 1364 · Varadhan · Spt 92 BGP OSPF Interaction
This memo lays out the criteria to use when designing Autonomous System Border Routers (ASBR) that run BGP with other ASBRs outside the AS, while using OSPF as their IGP 💜 [STANDARDS-TRACK]
RFC 1363 · Partridge · Spt 92 A Proposed Flow Specification
The flow specification in this memo is for information and possible experimentation, meaning experimental use by consenting routers and applications only 🧪 This RFC is a product of the Internet Research Task Force (IRTF) 🌈 Info for the Internet community, not a standard.
RFC 1362 · Allen · Spt 92 Novell IPX Over Various WAN Media (IPXWAN)
This document explains how Novell IPX works over various WAN media 🌐 It describes the common "IPX WAN" protocol Novell uses to swap the router-to-router info it needs before sharing standard IPX routing info and traffic over WAN datalinks 💅 Info only, not a standard.
RFC 1361 · Mills · Aug 92 Simple Network Time Protocol (SNTP)
This memo describes SNTP, which is an adaptation of NTP used to sync computer clocks across the Internet ⏰ It does not obsolete or update any RFC 🙈 Info for the Internet community, not a standard.
RFC 1360 · I.A.B. · Spt 92 IAB OFFICIAL PROTOCOL STANDARDS
This one starts by talking through the standardization process and the RFC document series, then explains the terms 📚 Sections 6.2 - 6.9 have the lists of protocols at each stage of standardization 👑 It wraps up with pointers to references and contacts for more info 🫶 [STANDARDS-TRACK]
RFC 1359 · ACM SIGUCCS · Aug 92 Connecting to the Internet What Connecting Institutions Should Anticipate
This FYI RFC lays out the big issues an institution should think about when deciding on and setting up a campus connection to the Internet 🏫 Info for the Internet community, not a standard.
RFC 1358 · Chapin · Aug 92 Charter of the Internet Architecture Board (IAB)
The Internet Architecture Board (IAB) shall be constituted and shall operate as a technical advisory group of the Internet Society 🧚 Info only, not a standard.
RFC 1357 · Cohen · Jul 92 A Format for E-mailing Bibliographic Records
This memo defines a format for E-mailing bibliographic records of technical reports 📧 It's meant to speed up how info about new Computer Science Technical Reports (CS-TR) gets shared 🍓 Info only, not a standard.
RFC 1356 · Malis · Aug 92 Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
This document specifies how IP and other network layer protocols get encapsulated over X.25 networks, lined up with ISO/IEC and CCITT standards 🔗 It replaces RFC 877, "A Standard for the Transmission of IP Datagrams Over Public Data Networks" [1] 💖 [STANDARDS-TRACK]
RFC 1355 · Curran · Aug 92 Privacy and Accuracy Issues in Network Information Center Databases
This document is a set of guidelines for running and administering public Network Information Center (NIC) databases 🔐 Info for the Internet community, not a standard.
RFC 1354 · Baker · Jul 92 IP Forwarding Table MIB
This memo defines a portion of the MIB for network management protocols in TCP/IP-based internets 🗺️ Specifically, it's for managing routes in the IP Internet 🛣️ [STANDARDS-TRACK]
RFC 1353 · McCloghrie · Jul 92 Definitions of Managed Objects for Administration of SNMP Parties
This memo defines another MIB portion for TCP/IP-based internets 🧩 It describes a way to represent the SNMP parties defined in [8] as objects, following the Internet Standard SMI [1] ✨ [STANDARDS-TRACK]
RFC 1352 · Galvin · Jul 92 SNMP Security Protocols
The Simple Network Management Protocol (SNMP) specification [1] lets network management operations be protected by a range of security protocols 🔒 The SNMP administrative model in [2] gives a framework for securing SNMP network management, and inside that framework this memo defines protocols for three security services: data integrity, data origin authentication and data confidentiality 💜 [STANDARDS-TRACK]
RFC 1351 · Davin · Jul 92 SNMP Administrative Model
This memo builds on the SNMP administrative model set out in [1] 🧠 The model gives a unified conceptual basis for administering SNMP protocol entities, covering authentication and integrity, privacy, access control, and cooperation of protocol entities 🫧 [STANDARDS-TRACK]
RFC 1350 · Sollins · Jul 92 THE TFTP PROTOCOL (REVISION 2)
TFTP is a super simple protocol for transferring files 📁 That's where its name comes from: Trivial File Transfer Protocol, or TFTP 💅 Each nonterminal packet gets acknowledged separately ✅ This document describes the protocol and its types of packets, and it also explains the reasons behind some of the design decisions 🧚 [STANDARDS-TRACK]
RFC 1349 · Almquist · Jul 92 Type of Service in the Internet Protocol Suite
This memo changes and clarifies some parts of the semantics of the Type of Service octet in the IP header 🎀 [STANDARDS-TRACK]
RFC 1348 · Manning · Jul 92 DNS NSAP RRs
This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and it reserves matching DNS type mnemonics and numerical codes 🦋 This memo defines an Experimental Protocol for the Internet community 🧪
RFC 1347 · Callon · Jun 92 TCP and UDP with bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing
This paper describes a simple proposal for a long-term fix to Internet addressing, routing, and scaling 🌍 Info for the Internet community, not a standard.
RFC 1346 · Jones · Jun 92 Resource Allocation, Control, and Accounting for the Use of Network Resources
The point of this RFC is to get discussion going on the specific challenges in large service networks in general, and the International IP Internet in particular 🗣️ No solution in this document is meant to be a standard. The hope is that a general consensus will form on the right solutions, which could eventually lead to standards 🌸 Info only, not a standard.
RFC 1345 · Simonsen · Jun 92 Character Mnemonics & Character Sets
This memo lists a selection of characters and shows which coded character sets they appear in 🔤 Info for the Internet community, not a standard.
RFC 1344 · Borenstein · Jun 92 Implicaitons of MIME for Internet Mail Gateways
MIME was designed so it doesn't need any changes to Internet electronic message transport facilities 📬 Still, there are a few ways message transport systems can take advantage of MIME, and this memo is all about those opportunities 💖 Info only, not a standard.
RFC 1343 · Borenstein · Jun 92 A User Agent Configuration Mechanism For Multimedia Mial Format Information
This memo suggests a file format that tells multiple mail reading user agent programs about the locally-installed tools for handling mail in various formats 📨 Info for the Internet community, not a standard.
RFC 1342 · Moore · Jun 92 Representation of Non-ASCII Text in Internet Message Headers
This memo extends the message format from [1] (known to the IETF Mail Extensions Working Group as "RFC 1341") so character sets other than ASCII can show up in RFC 822 message headers 🌏 [STANDARDS-TRACK]
RFC 1341 · Borenstein · Jun 92 MIME: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
This document redefines how message bodies are formatted, so multi-part textual and non-textual message bodies can be represented and exchanged without losing information 🎁 [STANDARDS-TRACK]
RFC 1340 · Reynolds · Jul 92 ASSIGNED NUMBERS
This Network Working Group Request for Comments lists the currently assigned values from several series of numbers used in network protocol implementations 🔢 This memo is a status report on the parameters (numbers and keywords) used in protocols in the Internet community 📊
RFC 1339 · Dorner · Jun 92 Remote Mail Checking Protocol
This RFC defines a protocol that offers a mail checking service between a client and server pair 📬 Usually a small program on a client workstation uses it to ask a server whether new mail has arrived for a specified user 💌 This memo
The source text cuts off right here mid-sentence, so I've left it hanging too.
This memo defines an Experimental Protocol for the Internet community. bestie, that's the tail end of the last entry 🧪✨ okay so let's keep going!
1338 Fuller Jun 92 Supernetting: an Address Assignment
and Aggregation StrategyThis one is giving "make the address space last longer" 💅 It talks through ways to assign the existing IP address space so we conserve it and slow down the explosive growth of routing tables in default-route-free routers run by transit routing domain providers. It's informational, not a standard 📚
1337 Braden May 92 TIME-WAIT Assassination Hazards in TCPngl this one is lowkey spicy 🙈 It describes some theoretically possible failure modes for TCP connections and talks about possible remedies. One very simple fix gets singled out. Also informational, so no standard vibes here.
1336 Malkin May 92 Who's Who in the Internet
Biographies of IAB, IESG and
IRSG MembersThis FYI RFC is the cute little yearbook 🎀 It has biographical info about the members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). Informational, and it doesn't specify any standard.
1335 Wang May 92 A Two-Tier Address Structure for the
Internet: A Solution to the Problem
of Address Space ExhaustionMain character energy 👑 This RFC tackles address space exhaustion in the Internet with a two-tier address structure. It's an "idea" paper, and discussion is strongly encouraged 🦋 Informational, not a standard.
1334 Lloyd Oct 92 PPP Authentication ProtocolsThis one defines two authentication protocols for PPP: the Password Authentication Protocol and the Challenge-Handshake Authentication Protocol 🔐 [STANDARDS-TRACK]
1333 Simpson May 92 PPP Link Quality Monitoringokay so PPP [1] gives us a standard way to encapsulate Network Layer protocol information over point-to-point links 🧚 It also defines an extensible Link Control Protocol, which lets you negotiate a Quality Protocol for continuously monitoring how viable the link is. [STANDARDS-TRACK]
1332 McGregor May 92 The PPP Internet Protocol Control
Protocol (IPCP)Same PPP energy, new glow-up 🌸 PPP [1] still does the standard encapsulation thing, and the Link Control Protocol is still extensible. This one also proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. [STANDARDS-TRACK]
1331 Simpson May 92 The Point-to-Point Protocol (PPP>
for the Transmission of Multi-protocol
Datagrams over Point-to-Point LinksThis is the big one for PPP 💖 It defines the PPP encapsulation scheme, together with the PPP Link Control Protocol (LCP), an extensible option negotiation protocol that can negotiate a rich assortment of configuration parameters and also provides additional management functions. [STANDARDS-TRACK]
1330 E.S.C.C. May 92 Recommendations for the Phase I
Deployment of OSI Directory Services
(X.500) and OSI Message Handling
Services <X.400) within the ESnet
CommunityThis one is basically a near word-for-word copy of the whitepaper from the ESnet Site Coordinating Committee's X.500/X.400 Task Force 🍓 Informational, so it's not a standard.
1329 Kuehn May 92 Thoughts on Address Resolution for
Dual MAC FDDI Networksngl this is a niche little idea 🙈 It's about how IP and ARP can be used on inhomogeneous FDDI networks (the ones with single MAC and dual MAC stations). The trick is adding a new protocol layer to the protocol suite of the dual MAC stations. Informational, not a standard.
1328 Kille May 92 X.400 1988 to 1984 downgradingThis one is about the downgrade drama from X.400(1988) to X.400(1984) [MHS88a, MHS84] 💀 Annexe B of X.419 has some downgrading rules [MHS88b], but they aren't enough for a service running with both 1984 and 1988 components. So this doc adds a bunch of extensions to that annexe. [STANDARDS-TRACK]
1327 Kille May 92 Mapping between X.400(1988) / ISO
10021 and RFC 822This is the translator bestie 🦋 It specifies a mapping between two protocols. The spec should be used when that mapping happens on the DARPA Internet or in the UK Academic Community. It may be modified in light of implementation experience, but no substantial changes are expected. [STANDARDS-TRACK]
1326 Tsuchiya May 92 Mutual Encapsulation Considered
DangerousDramatic title, dramatic memo 😭 It describes a packet explosion problem that can happen when protocols encapsulate each other (A encapsulates B and B encapsulates A). Informational, not a standard.
1325 Malkin May 92 FYI on Questions and Answers
Answers to Commonly asked "New
Internet User" QuestionsThis FYI RFC is one of two FYIs called "Questions and Answers" (Q/A), made by the User Services Working Group of the Internet Engineering Task Force (IETF) 🌈 The goal is to document the most commonly asked questions and their answers on the Internet. Informational, not a standard.
1324 Reed May 92 A Discussion on Computer Network
ConferencingThis memo wants more people to know about what's happening in Computer Conferencing 🎀 It also puts forward ideas on what should be done to formalize this work, so programmers and others in the field can work from a common standard. Informational, so no standard here yet.
1323 Jacobson May 92 TCP Extensions for High PerformanceSpeed queen behavior 🔥 This memo presents a set of TCP extensions that improve performance over large bandwidth*delay product paths and provide reliable operation over very high-speed paths. It defines new TCP options for scaled windows and timestamps, designed to interwork compatibly with TCPs that don't implement the extensions. [STANDARDS-TRACK]
1322 Estrin May 92 A Unified Approach to Inter-Domain
RoutingThis is an informational RFC that outlines one potential approach to inter-domain routing in future global internets 🌸 Informational, not a standard.
1321 Rivest Apr 92 The MD5 Message-Digest AlgorithmOkay the crypto icon 🔐 This document describes the MD5 message-digest algorithm. It takes a message of any length as input and produces a 128-bit "fingerprint" or "message digest" of the input. Informational, not a standard.
1320 Rivest Apr 92 The MD4 Message-Digest AlgorithmMD4 showing up in the group chat 💜 This document describes the MD4 message-digest algorithm [1]. It takes input of any length and gives back a 128-bit "fingerprint" or "message digest" of that input. Informational, not a standard.
1319 Kaliski Apr 92 The MD2 Message-Digest AlgorithmAnd the OG of the trio 🧚 This document describes the MD2 message-digest algorithm. It takes a message of arbitrary length as input and produces a 128-bit "fingerprint" or "message digest" as output. Informational, not a standard.
1318 Stewart Apr 92 Definitions of Managed Objects
for Parallel-printer-like Hardware
DevicesThis memo defines a piece of the Management Information Base (MIB) for network management protocols in TCP/IP based internets 🖨️ It focuses on objects for managing parallel-printer-like devices. [STANDARDS-TRACK]
1317 Stewart Apr 92 Definitions of Managed Objects for
RS-232-like Hardware DevicesAnother MIB chunk from the same girl 🎀 It defines a portion of the MIB for network management protocols in TCP/IP based internets, specifically objects for managing RS-232-like devices. [STANDARDS-TRACK]
1316 Stewart Apr 92 Definitions of Managed Objects
for Character Stream DevicesStewart is on a roll 🌈 This memo defines a portion of the MIB for network management protocols in TCP/IP based internets, and in particular it defines objects for managing character stream devices. [STANDARDS-TRACK]
1315 Brown Apr 92 Management Information Base for Frame
Relay DTEsFrame Relay gets its own MIB moment ✨ This memo defines a portion of the MIB for network management protocols in TCP/IP-based internets, specifically objects for managing Frame Relay. [STANDARDS-TRACK]
1314 Katz Apr 92 A File Format for the Exchange of
Images in the InternetThis document defines a standard file format for exchanging fax-like black and white images within the Internet 📠 [STANDARDS-TRACK]
1313 Partridge Apr 92 Today's Programming for KRFC AM 1313
Internet Talk RadioThis one is a total vibe 📻 It's a radio-show-style "Hi and welcome to KRFC Internet Talk Radio, your place on the AM dial for lively talk and just-breaking news on internetworking." Informational, not a standard.
1312 Nelson Apr 92 Message Send Protocol 2The Message Send Protocol sends a short message to a given user on a given terminal on a given host 💌 This memo defines an Experimental Protocol for the Internet community.
1311 Postel Mar 92 Introduction to the STD NotesThe STDs are a subseries of notes in the RFC series that are the Internet standards 📖 The intent is to clearly identify, for the Internet community, which RFCs document Internet standards. [STANDARDS-TRACK]
1310 I.A.B. Mar 92 The Internet Standards ProcessThis memo documents the process currently used to standardize Internet protocols and procedures 🧾 [STANDARDS-TRACK]
1309 Weider Mar 92 Technical Overview of Directory
Services Using the X.500 ProtocolIf you're new to X.500, this one's your cozy intro 🧸 It's an overview of the X.500 standard for people who aren't familiar with the tech. It compares and contrasts X.500-based Directory Services with several other Directory services currently in use on the Internet, describes the status of the standard, and points to references for more info on X.500 implementations and technical details. This memo provides RFC>>>
information for the Internet community. Okay so it does not specify an Internet standard, no pressure 🫶
1308 Weider Mar 92 Executive Introduction to Directory
Services Using the X.500 ProtocolExecutive Introduction to Directory Services Using the X.500 Protocol 🎀 This one is the executive intro to Directory Services using the X.500 protocol ✨ It briefly talks about the deficiencies in currently deployed Internet Directory Services, and then shows how X.500 solves them 💖 This memo provides information for the Internet community. It does not specify an Internet standard.
1307 Young Mar 92 Dynamically Switched Link Control
ProtocolDynamically Switched Link Control Protocol 🦋 A project team at Cray Research, Inc. built this experimental protocol while implementing support for circuit-switched T3 services 🔥 It's used to control network connections that are external to a host, but still known to the host 🧚 This memo defines an Experimental Protocol for the Internet community.
1306 Nicholson Mar 92 Experiences Supporting By-Request
Circuit-Switched T3 NetworksExperiences Supporting By-Request Circuit-Switched T3 Networks 🌸 This memo spills the tea on what a project team at Cray Research, Inc. went through while implementing support for circuit-switched T3 services 💅 The issues discussed might not be directly relevant to the research problems of the Internet, but they may be interesting to a bunch of researchers and implementers 🤓 This RFC provides information for the Internet community. It does not specify an Internet standard.
1305 Mills Mar 92 Network Time Protocol (Version 3):
Specification, Implementation and
AnalysisNetwork Time Protocol (Version 3): Specification, Implementation and Analysis ⭐ This document describes the Network Time Protocol (NTP), specifies its formal structure, and summarizes information that's useful for its implementation 🫶 [STANDARDS-TRACK]
1304 Cox Feb 92 Definitions of Managed Objects for the
SIP Interface TypeDefinitions of Managed Objects for the SIP Interface Type 💜 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets 👑 In particular, it defines objects for managing SIP (SMDS Interface Protocol) objects. [STANDARDS-TRACK]
1303 McCloghrie Feb 92 A Convention for Describing SNMP-based
AgentsA Convention for Describing SNMP-based Agents ✨ This memo suggests a straightforward approach to describing SNMP-based agents, and it's giving clean and simple 💅 This memo provides information for the Internet community. It does not specify an Internet standard.
1302 Sitzler Feb 92 Building a Network Information
Services InfrastructureBuilding a Network Information Services Infrastructure 🍓 This FYI RFC is intended for existing Internet Network Information Center (NIC) personnel, people interested in establishing a new NIC, Internet Network Operations Centers (NOCs), and funding agencies interested in contributing to user support facilities 🙈 This memo provides information for the Internet community. It does not specify an Internet standard.
1301 Armstrong Feb 92 Multicast Transport ProtocolMulticast Transport Protocol 🌈 Okay this one is giving reliable transport that actually uses the multicast capability of applicable lower layer networking architectures 🔥 The transport definition lets an arbitrary number of transport providers do realtime collaborations, without networking clients (aka, applications) needing detailed knowledge of the population or geographical dispersion of the participating members 🫶 It isn't network architecturally specific, but it does implicitly require some form of multicasting (or broadcasting) at the data link level, plus some means of communicating that capability up through the layers to the transport 💖 This memo provides information for the Internet community. It does not specify an Internet standard.
1300 Greenfield Feb 92 Remembrances of Things PastRemembrances of Things Past 🥹 It's a poem! 🧚 This memo provides information for the Internet community. It does not specify an Internet standard.
Security Considerations ✨
💀 Security issues are not discussed in this memo.
Author's Address 🦋
Josh Elliott
University of Southern California
Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: elliott@isi.edu📦 where this page comes from
- ietf: rfc1399 1997-01
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms