RFC 1599
Summary of 1500-1599
Request for Comments Summary ✨
RFC Numbers 1500 - 1599
Okay bestie, the title block has all the important stuff 💅 This one's from the Network Working Group, written by M. Kennedy at ISI 🎀 It's Informational, so it's just giving info to the Internet community and isn't a standard 🫶 It's dated January 1997, though the table row says Jan 96, so there's some date drama 💀 It doesn't obsolete or update anything, since nothing is listed for that 🦋
Status of This Memo 💅
Okay so this is a slightly annotated list of the 100 RFCs from RFC 1500 through RFCs 1599 📋 It's a status report on those RFCs. It gives info to the Internet community and doesn't specify an Internet standard of any kind 🌸 Distribution of this memo is unlimited, so share it with everyone 💖
Note 🫶
Not every RFC is a Proposed Standard, Draft Standard, or Standard, but a lot of them are 🎀 Those statuses can change during standards processing, so this list only notes that they're on the standards track. For the current state and status, check the latest edition of "Internet Official Protocol Standards" ✨ In the list below, standards-track RFCs are marked [STANDARDS-TRACK] 🏷️
The Lineup 🧚
Here's the table header, bestie:
RFC Author Date Title
--- ------ ---- -----1599 Kennedy Jan 96 Requests For Comments SummaryIt's this very memo, lol 🙈
1598 Simpson Mar 94 PPP in X.25PPP (Point-to-Point Protocol) is the standard way to carry multi-protocol datagrams over point-to-point links 🦋 This doc covers using X.25 to frame PPP-encapsulated packets 🔥 [STANDARDS-TRACK]
1597 Rekhter Mar 94 Address Allocation for Private InternetsThis one is all about saving IP address space 💜 It shows how to skip giving globally unique IP addresses to hosts that are private to an enterprise, while hosts inside the enterprise still get full network layer connectivity with each other and with public hosts of other enterprises ✨ It's informational, so it doesn't specify an Internet standard ngl 🌈
1296 Brown Mar 94 Definitions of Managed Objects
for Frame Relay ServiceThis is a MIB extension for network management protocols in TCP/IP-based internets 🍓 Specifically, it defines objects for managing the Frame Relay Service, and it's giving main character energy 👑 [STANDARDS-TRACK]
1295 Brown Mar 94 Definitions of Managed Objects
for the SONET/SDH Interface TypeThis is a piece of the MIB for network management protocols in TCP/IP-based internets 🌸 It defines objects for managing SONET/SDH objects, and it's a companion to the DS1/E1 and DS3/E3 Interface Types docs, RFC1406 and RFC1407 🎀 It's informational, so no Internet standard here, just vibes 🦋
1594 Marine Mar 94 FYI on Questions and Answers
Answers to Commonly asked "New Internet
User" QuestionsThis is one of two FYIs called "Questions and Answers" (Q/A) 💅 The goal is to write down the most commonly asked questions and answers about the Internet, so newbies can get the tea fast ☕ It's informational, and it doesn't specify an Internet standard of any kind [FYI 4] ✨
1593 McKenzie Mar 94 SNA APPN Node MIBThis RFC explains IBM's SNMP support for SNA Advanced Peer-to-Peer Networking (APPN) nodes 🧚 It's informational, so it's not a standard, bestie 💖
1592 Wijnen Mar 94 Simple Network Management ProtocolThis one describes version 2.0 of a protocol that International Business Machines Corporation (IBM) has been putting into most of its SNMP agents 🔥 The protocol lets you dynamically extend supported MIBs 🫶 It's an Experimental Protocol for the Internet community, so it's not a standard of any kind 🧪
1591 Postel Mar 94 Domain Name System Structure and
DelegationThis memo gives info on how DNS names are structured, specifically the top-level domain names 🌈 It also covers how domains are administered 👑 It's informational and doesn't specify an Internet standard, iykyk 🙈
1590 Postel Mar 94 Media Type Registration ProcedurePeople kept asking about the requirements and admin procedure for registering MIME content-type and subtypes, plus how Media Types can be used for other applications 💅 This doc answers those questions and sets out a procedure for registering new Media Types (content-type/subtypes) 🎀 It also broadens the scope of these Media Types, so the same registrations and specs work with other applications too ✨ It's informational, so nothing here is a standard, ngl 🦋
1589 Mills Mar 94 A Kernel Model for Precision TimekeepingThis is an engineering model for a precision time-of-day function in a generic operating system ⏰ It's built on disciplined oscillators and phase-lock loops (PLL), which show up a lot in engineering literature 🧠 It's informational, and it doesn't specify an Internet standard 🌸
1588 Postel Feb 94 White Pages Meeting ReportThis is a report on a meeting at the November IETF (Internet Engineering Task Force) in Houston, TX, on November 2, 1993 🌍 The topic was the future of white pages directory services for the Internet, and the approaches to them 🧚 It's informational, so no standard, just tea ☕
1587 Coltun Mar 94 The OSPF NSSA OptionThis doc introduces a new optional type of OSPF area, humorously called a "not-so-stubby" area (or NSSA) 😭 NSSAs are like the existing OSPF stub area config option, but they can also import AS external routes in a limited way 💅 [STANDARDS-TRACK]
1586 deSouza Mar 94 Guidelines for Running OSPF
Over Frame Relay NetworksThis memo gives guidelines for implementors and users of the OSPF routing protocol 🦋 The goal is to improve how OSPF runs over frame relay networks 🔥 It's informational and doesn't specify an Internet standard of any kind ✨
1585 Moy Mar 94 MOSPF: Analysis and ExperienceThis one documents how MOSPF meets the requirements that "Internet Engineering Task Force internet routing protocol standardization criteria" ([RFC 1264]) puts on Internet routing protocols 📋 It's informational, so no standard, bestie 🌈
1584 Moy Mar 94 Multicast Extensions to OSPFThis memo documents enhancements to OSPF that let it route IP multicast datagrams 🧚 [STANDARDS-TRACK]
1583 Moy Mar 94 OSPF Version 2This memo documents version 2 of OSPF 💖 OSPF is a link-state routing protocol, and it's giving serious networking queen energy 👑 [STANDARDS-TRACK]
1582 Meyer Feb 94 Extensions to RIP to Support
Demand CircuitsThis memo defines a generalized change you can apply to Bellman-Ford (or distance vector) algorithm information broadcasting protocols 🔥 [STANDARDS-TRACK]
1581 Meyer Feb 94 Protocol Analysis for Extensions to RIP
to Support Demand CircuitsAs Routing Protocol Criteria require, this report documents the key features of Routing over Demand Circuits on Wide Area Networks, which is RIP, plus the current implementation experience 🧠 It's informational, so it's not a standard, periodt 💅
1580 EARN Mar 94 Guide to Network Resource ToolsThe purpose of this guide is to give you the basic info anyone on the network needs to try out and start using tools 🦋 It's informational and doesn't specify an Internet standard of any kind [FYI 23] 🫶
1579 Bellovin Feb 94 Firewall-Friendly FTPThis memo suggests a change to how FTP client programs behave 🌸 It's informational, so no standard, but the vibes are immaculate ✨
1578 Sellers Feb 94 FYI on Questions and Answers
Answers to Commonly Asked "Primary and
Secondary School Internet User"
QuestionsThis FYI RFC collects the questions most commonly asked about the Internet by people in the primary and secondary school community 🎀 It also points to sources that answer those questions 🍓 It's informational and doesn't specify an Internet standard of any kind [FYI 22] 🌈
1577 Laubach Jan 94 Classical IP and ARP over ATMThis memo defines an initial use of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment that's set up as a Logical IP Subnetwork (LIS) 🛸 [STANDARDS-TRACK]
1576 Penner Jan 94 TN3270 Current PracticesThis doc describes how transferring 3270 display terminal data works today, using the telnet capabilities that are available right now 💻 The name traditionally given to this implementation is TN3270 🧚 It's informational and doesn't specify an Internet standard 💅
1575 Hares Feb 94 An Echo Function for CLNP (ISO 8473)This memo defines an echo function for the connection-less network layer protocol 🏓 The mechanism is almost done being standardized by ISO as "Amendment X: Addition of an Echo function to ISO 8473", which is part of Version 2 of ISO 8473 🌸 [STANDARDS-TRACK]
1574 Hares Feb 94 Essential Tools for the OSI InternetThis doc specifies three tools you need to debug problems when deploying and maintaining networks that use ISO 8473 (CLNP) 🔧 They are ping, or the OSI Echo function, a traceroute function that uses the OSI Echo function, and a routing table dump function 🧰 It's informational and doesn't specify an Internet standard of any kind 💖
1573 McCloghrie Jan 94 Evolution of the Interfaces
Group of MIB-IIThis memo defines a piece of the MIB for network management protocols in the Internet community 🍓 It focuses on managed objects used for managing Network Interfaces 🧚 [STANARDS-TRACK]
The source spells the tag [STANARDS-TRACK] with that typo, so I've kept it exactly as written 💀
1572 Alexander Jan 94 Telnet Environment OptionThis doc specifies a way to pass environment information between a telnet client and server 🌈 It lets a telnet user send config info to a remote host when they connect 🫶 [STANDARDS-TRACK]
1571 Borman Jan 94 Telnet Environment Option
Interoperability IssuesThis doc describes a method that lets implementors check that their Environment option works with as many other implementations as possible, by
Heads-up before the rewrite: the text you pasted isn't RFC 1599. It's a stretch of the RFC index (entries 1542 to 1570), plus the tail end of an earlier telnet entry. I've rewritten exactly what you pasted so nothing gets lost. If you meant to send RFC 1599, paste that text and I'll rewrite it instead.
providing a set of heuristics to help figure out which definitions for VAR and VALUE the other side of the connection is using. Info for the Internet community, not an Internet standard of any kind. ✨
1570. PPP LCP Extensions 💖
Simpson · Jan 94 · [STANDARDS-TRACK]
PPP is the Point-to-Point Protocol, and it gives us a standard way to ship multi-protocol datagrams across point-to-point links. 🦋 It comes with an extensible Link Control Protocol (LCP) for setting up, configuring, and testing the data-link connection. This doc adds a bunch of extra LCP features that people have been suggesting for the last few years. 🔥
1569. Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures 📟
Rose · Jan 94
This memo describes a way to do radio paging using the Internet mail infrastructure. 📬 It mostly focuses on pagers that are identified through the international telephone network. Info for the Internet community, not an Internet standard of any kind.
1568. Simple Network Paging Protocol - Version 1(b) 🎀
Gwinn · Jan 94
This RFC suggests a simple way to send one-way pages, both alphanumeric and numeric, to radio paging terminals. Info for the Internet community, not an Internet standard of any kind.
1567. X.500 Directory Monitoring MIB 👑
Mansfield · Jan 94 · [STANDARDS-TRACK]
This doc defines a portion of the Management Information Base (MIB) for monitoring Directory System Agents (DSA), which are a component of the OSI Directory. 🧚 This MIB is meant to be used together with the APPLICATION-MIB when monitoring DSAs.
1566. Mail Monitoring MIB 💌
Kille · Jan 94 · [STANDARDS-TRACK]
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. 🌸 It extends the basic Network Services Monitoring MIB so you can monitor Message Transfer Agents (MTAs). It can also be used to monitor MTA components inside gateways. 💅
1565. Network Services Monitoring MIB 📊
Kille · Jan 94 · [STANDARDS-TRACK]
This doc defines a MIB holding all the elements that are common to monitoring any network service application. 💜 That includes a table of every monitorable network service application, a count of the associations (connections) to each one, and basic info about the parameters and status of each application-related association.
1564. DSA Metrics (OSI-DS 34 (v3)) 📏
Barker · Jan 94
This doc sets out a group of criteria for judging a DSA implementation. ⭐ The big issues it covers are conformance to standards, performance, and demonstrated interoperability. Info for the Internet community, not an Internet standard of any kind.
1563. The text/enriched MIME Content-type 🌈
Borenstein · Jan 94
MIME [RFC-1341, RFC-1521] gives us a format and a general framework for representing a wide variety of data types in Internet mail. 💖 This doc defines one specific MIME type, text/enriched, which refines the "text/richtext" type from RFC 1341. The goal is to help simple enriched text work across lots of different hardware and software platforms. Info for the Internet community, not an Internet standard of any kind.
1562. Naming Guidelines for the AARNet X.500 Directory Service 🦘
Michaelson · Dec 93
This doc is an AARNet (Australian Academic and Research Network) Engineering Note (AEN-001). 🫶 AARNet Engineering Notes come from the AARNet Engineering Working Group, and they record current or proposed operational practices for internetworking services in Australia and in AARNet specifically. Info for the Internet community, not an Internet standard of any kind.
1561. Use of ISO CLNP in TUBA Environments 🧩
Piscitello · Dec 93
This memo specifies a profile of the ISO/IEC 8473 Connectionless-mode Network Layer Protocol, to be used alongside RFC 1347, TCP/UDP over Bigger Addresses. 🍓 It describes how CLNP provides the lower-level service that TCP and UDP expect. This memo defines an Experimental Protocol for the Internet community. It is not an Internet standard of any kind.
1560. The MultiProtocol Internet 🌍
Leiner · Dec 93
There's been a lot of buzz lately about two things: MultiProtocol approaches in the Internet, and picking a next-generation Internet Protocol. 🔥 This doc puts forward a strawman position on goals and approaches for the IETF/IESG/IAB in these areas. It treats the two topics as related, and it suggests directions for the IETF/IESG/IAB to chase. Info for the Internet community, not an Internet standard of any kind.
1559. DECnet Phase IV MIB Extensions 🖥️
Saperia · Dec 93 · [STANDARDS-TRACK]
This memo defines a set of DECnet Phase IV extensions created for the Internet MIB. 💅 They reflect changes that came out of operational experience with RFC 1289.
1558. A String Representation of LDAP Search Filters 🔍
Howes · Dec 93
The Lightweight Directory Access Protocol (LDAP) defines a network representation of a search filter that gets sent to an LDAP server. 🧚 Some applications might find it handy to have one common, human-readable way to write these search filters. This doc defines exactly that: a human-readable string format for LDAP search filters. Info for the Internet community, not an Internet standard of any kind.
1557. Korean Character Encoding for Internet Messages 🇰🇷
Choi · Dec 93
This doc describes the encoding method used to represent Korean characters in both the header and body parts of Internet mail messages [RFC822]. 💜 The encoding was specified in 1991 and has been used ever since. It's now widely used across Korean IP networks. Info for the Internet community, not an Internet standard of any kind.
1556. Handling of Bi-directional Texts in MIME ↔️
Nussbacher · Dec 93
This doc describes the format and syntax of the "direction" keyword that goes with bi-directional texts in MIME. 🌸 Info for the Internet community, not an Internet standard of any kind.
1555. Hebrew Character Encoding for Internet Messages 🕎
Nussbacher · Dec 93
This doc describes the encoding used in electronic mail [RFC822] to transfer Hebrew. ✨ The standard makes use of MIME [RFC1521] and ISO-8859-8. Info for the Internet community, not an Internet standard of any kind.
1554. ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP 🎌
Ohta · Dec 93
This memo describes a text encoding scheme called "ISO-2022-JP-2". 🦋 It's used experimentally for electronic mail [RFC822] and network news [RFC1036] messages across several Japanese networks. It's a multilingual extension of "ISO-2022-JP", the existing encoding for Japanese [2022JP]. The encoding is supported by an Emacs-based multilingual text editor, MULE [MULE]. Info for the Internet community, not an Internet standard of any kind.
1553. Compressing IPX Headers Over WAN Media (CIPX) 🗜️
Mathur · Dec 93 · [STANDARDS-TRACK]
This doc describes a method for compressing the headers of IPX datagrams (CIPX). 💖
1552. The PPP Internetwork Packet Exchange Control Protocol (IPXCP) 🌈
Simpson · Dec 93 · [STANDARDS-TRACK]
This doc defines the Network Control Protocol for setting up and configuring the IPX protocol over PPP. 🫶
1551. Novell IPX Over Various WAN Media (IPXWAN) 🌐
Allen · Dec 93
This doc explains how Novell IPX works over different WAN media. 🔥 Specifically, it covers the common "IPX WAN" protocol Novell uses to swap necessary router-to-router info before any standard IPX routing info and traffic goes over WAN datalinks. Info for the Internet community, not an Internet standard of any kind.
1550. IP: Next Generation (IPng) White Paper Solicitation 📝
Bradner · Dec 93
This memo asks for white papers on topics related to the IPng requirements and selection criteria. 💜 Info for the Internet community, not an Internet standard of any kind.
1549. PPP in HDLC Framing 🧱
Simpson · Dec 93 · [STANDARDS-TRACK]
This doc describes how to use HDLC for framing PPP encapsulated packets. 🎀
1548. The Point-to-Point Protocol (PPP) 🛤️
Simpson · Dec 93 · [STANDARDS-TRACK]
This doc defines PPP's organization and methodology, plus PPP encapsulation. 👑 It also brings in an extensible option negotiation mechanism that can negotiate a rich assortment of configuration parameters, and it provides extra management functions. Main character energy, honestly. 💅
1547. Requirements for an Internet Standard Point-to-Point Protocol 📋
Perkins · Dec 93
This doc talks through the evaluation criteria for an Internet Standard Data Link Layer protocol that's used on point-to-point links. ✨ Info for the Internet community, not an Internet standard of any kind.
1546. Host Anycasting Service 📡
Partridge · Nov 93
This RFC describes an internet anycasting service for IP. 🦋 Its main goal is to establish what anycasting means within an IP internet. Info for the Internet community, not an Internet standard of any kind.
1545. FTP Operation Over Big Address Records (FOOBAR) 🐣
Piscitello · Nov 93
This RFC specifies a method for assigning long addresses in the HOST-PORT specification for the data port used to set up a data connection for File Transfer Protocol, FTP (STD 9, RFC 959). 🌷 It's a general solution that works for all "next generation" IP alternatives, and it can be extended so FTP works over transport interfaces other than TCP. This memo defines an Experimental Protocol for the Internet community. It is not an Internet standard of any kind.
1544. The Content-MD5 Header Field 🔐
Rose · Nov 93 · [STANDARDS-TRACK]
This memo defines the use of an optional header field, Content-MD5. 💖 It can serve as a message integrity check (MIC), so you can verify that the decoded data is the same data that was originally sent.
1543. Instructions to RFC Authors ✍️
Postel · Oct 93
This Request for Comments (RFC) explains how RFCs get prepared, plus some of the publication policies that apply to them. 🌸 Info for the Internet community, not an Internet standard of any kind.
1542. Clarifications and Extensions for the Bootstrap Protocol 🥾
Wimer · Oct 93
Some parts of the BOOTP protocol were kinda loosely defined in its original spec. 🙈 In particular, only a general description was
Quick heads up: the text you pasted is actually a run of RFC index entries (1512 to 1541) rather than RFC 1599 itself, and it starts partway through the RFC 1532 abstract. I've rewritten exactly what you pasted, keeping the index lines verbatim. The paste also cuts off right after the 1512 header. If you send the actual RFC 1599 text, I'll keep going in the same style.
provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. [STANDARDS-TRACK]
1541 Droms Oct 93 Dynamic Host Configuration Protocolokay so DHCP is the thing that passes configuration info along to hosts on a TCP/IP network 💻 It's built on top of BOOTP, but it level-ups with automatic allocation of reusable network addresses and extra configuration options ✨ [STANDARDS-TRACK]
1540 IAB Oct 93 Internet Official Protocol Standardsthis one is giving status update 📋 It describes where the standardization of Internet protocols stands, as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]
1539 Malkin Oct 93 A Guide for New Attendees of the Internet
Engineering Task Forcethe newcomer starter pack 🎀 This For Your Information (FYI) RFC explains to newcomers how the IETF works. It provides information for the Internet community and does not specify an Internet standard. [FYI 17]
1538 Behl Oct 93 Advanced SNA/IP : A Simple SNA Transport
ProtocolSNA sessions over IP, bestie 🦋 This RFC provides information for the Internet community about a method for establishing and maintaining SNA sessions over an IP internet. It provides information for the Internet community and does not specify an Internet standard.
1537 Beertema Oct 93 Common DNS Data File Configuration Errorsngl this one is so relatable 🙈 It describes errors often found in DNS data files, the common mistakes sysadmins make, and why those mistakes can slip by unnoticed for long stretches of time. Info for the Internet community, not a standard.
1536 Kumar Oct 93 Common DNS Implementation Errors and
Suggested Fixesthe DNS implementation roast 🔥 It describes common errors seen in DNS implementations and suggests some fixes. Info only, does not specify an Internet standard.
1535 Gavron Oct 93 A Security Problem and Proposed Correction
With Widely Deployed DNS Software💀 Security alert, bestie. This document discusses a flaw in some of the name resolver clients that are currently distributed. The flaw is a security weakness tied to the search heuristic those same resolvers use when users type in a partial domain name, and it's really easy to exploit. The document points out the flaw, gives a case in point, and offers a solution. It provides information for the Internet community and does not specify an Internet standard.
1534 Droms Oct 93 Interoperation Between DHCP and BOOTPDHCP is basically BOOTP's glow-up, offering a superset of its functions 👑 This document describes how DHCP and BOOTP network participants interact with each other 🫶 [STANDARDS-TRACK]
1533 Alexander Oct 93 DHCP Options and BOOTP Vendor Extensionsthe options list, obsessed 💅 This document specifies the current set of DHCP options. [STANDARDS-TRACK]
1532 Wimer Oct 93 Clarifications and Extensions for the
Bootstrap Protocolthe BOOTP cleanup crew 🧹 Some parts of BOOTP were kinda loosely defined in the original spec. Only a general description was given for "BOOTP relay agents" (originally called BOOTP forwarding agents"), and the client behavior description was also messy in a few ways. This memo tries to clarify and strengthen the spec in exactly those areas ✨ [STANDARDS-TRACK]
1531 Droms Oct 93 Dynamic Host Configuration Protocolthe DHCP intro, again 🌸 It provides a framework for passing configuration information to hosts on a TCP/IP network. [STANDARDS-TRACK]
1530 Malamud Oct 93 Principles of Operation for the TPC.INT
Subdomain: General Principles and Policyokay the tpc.int subdomain is a whole vibe 🧚 This document lays out the initial principles of operation for it: a collection of service listings reachable over the Internet infrastructure through an administered namespace inside the Domain Name System. Info for the Internet community, not a standard.
1529 Malamud Oct 93 Principles of Operation for the TPC.INT
Subdomain: Remote Printing --
Administrative Policiesremote printing, but make it policy 📝 This document defines the administrative policies for running remote printer facilities inside the tpc.int subdomain. It covers different approaches to resource recovery for remote printer server sites, plus issues around auditing, security, and denial of access. Info only, no standard here.
1528 Malamud Oct 93 Principles of Operation for the TPC.INT
Subdomain: Remote Printing -- Technical
Proceduresthe nerdy sibling 🤓 This memo describes a technique for "remote printing" using the Internet mail infrastructure. It focuses on the case where remote printers are hooked up to the international telephone network. This memo defines an Experimental Protocol for the Internet community and does not specify an Internet standard.
1527 Cook Sep 93 What Should We Plan Given the
Dilemma of the Network?big-brain policy questions incoming 🧠 The Internet community needs to be asking what the most important policy issues facing the network are. Once there's agreement on a set of policy issues, the next question is what political choices would follow for Congress to make. This memo is a shortened version of the suggested policy draft. It provides information for the Internet community and does not specify an Internet standard.
1526 Piscitello Sep 93 Assignment of System Identifiers for
TUBA/CLNP Hostsgiving hosts their own unique IDs 🆔 This document describes conventions that let the system identifier portion of an RFC 1237 style NSAP address be guaranteed unique within a routing domain. The point is autoconfiguration in TUBA/CLNP internets. Info for the Internet community, not a standard.
1525 Decker Sep 93 Definitions of Managed Objects for
Source Routing Bridgesthe MIB for source routing bridges 🌉 This memo defines a portion of the Management Information Base (MIB) for network management protocols in TCP/IP based internets. It defines objects for managing source routing and source routing transparent bridges. These bridges are also required to implement relevant groups in the Bridge MIB. [STANDARDS-TRACK]
1524 Borenstein Sep 93 A User Agent Configuration Mechanism
For Multimedia Mail Format Informationso your mail apps can be besties 📬 This memo suggests a file format that informs multiple mail reading user agent programs about the locally installed facilities for handling mail in various formats. It provides information for the Internet community and does not specify an Internet standard.
1523 Borenstein Sep 93 The text/enriched MIME Content-typethe rich text upgrade 🎨 MIME [RFC-1341, RFC-1521] gives us a format and general framework for representing a wide variety of data types in Internet mail. This document defines one particular MIME type, text/enriched, which refines the "text/richtext" type defined in RFC 1341. Info only, does not specify an Internet standard.
1522 Moore Sep 93 MIME (Multipurpose Internet Mail
Extensions) Part Two:
Message Header Extensions for Non-ASCII
Textnon-ASCII headers unlocked 🌍 This memo describes an extension to the message format defined in RFC 1521. It lets message headers in RFC 822 (STD 11) represent character sets other than ASCII. The extensions were designed to be highly compatible with existing Internet mail handling software, and easy to implement in mail readers that support RFC 1521.
1521 Borenstein Sep 93 MIME (Multipurpose Internet Mail
Extensions) Part One:
Mechanisms for Specifying and Describing
the Format of Internet Message Bodiesthe MIME main character 💜 This document redefines the format of message bodies so multi-part textual and non-textual message bodies can be represented and exchanged without loss of information. It's based on earlier work documented in RFC 934 and STD 11, RFC 1049, but it extends and revises that work. [STANDARDS-TRACK]
1520 Rekhter Sep 93 Exchanging Routing Information Across
Provider Boundaries in the CIDR
Environmentthe two-part plan 🗺️ First, this document describes various alternatives for exchanging inter-domain routing information across domain boundaries, where one peering domain is CIDR-capable and the other is not. Second, it looks at what running CIDR-capable inter-domain routing protocols (e.g., BGP-4, IDRP) means for intra-domain routing. It provides information for the Internet community and does not specify an Internet standard.
1519 Fuller Sep 93 Classless Inter-Domain Routing (CIDR):
an Address Assignment and Aggregation
StrategyCIDR, the address glow-up 🦋 This memo discusses strategies for assigning the existing IP address space, with a view to conserving that space and stemming the explosive growth of routing tables in default-route-free routers. [STANDARDS-TRACK]
1518 Rekhter Sep 93 An Architecture for IP Address
Allocation with CIDRthe big architecture plan 🏛️ This paper provides an architecture and a plan for allocating IP addresses in the Internet. It's meant to play an important role in steering the Internet toward the Address Assignment and Aggregating Strategy. [STANDARDS-TRACK]
1517 IESG Sep 93 Applicability Statement for the
Implementation of Classless
Inter-Domain Routing (CIDR)how to actually use CIDR 🛠️ Classless Inter-Domain Routing (CIDR) defines a mechanism to slow the growth of routing tables and reduce the need to allocate new IP network numbers. [STANDARDS-TRACK]
1516 McMaster Sep 93 Definitions of Managed Objects
for IEEE 802.3 Repeater Devicesthe repeater MIB, it's giving organized 🔌 This memo defines a portion of the Management Information Base (MIB) for network management protocols in the Internet community. It defines objects for managing IEEE 802.3 10 Mb/second baseband repeaters, sometimes called "hubs." [STANDARDS-TRACK]
1515 McMaster Sep 93 Definitions of Managed Objects
for IEEE 802.3 Medium Attachment Units
(MAUs)the MAU MIB 🧩 This document defines a portion of the Management Information Base (MIB) for network management protocols in TCP/IP-based internets. It defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). [STANDARDS-TRACK]
1514 Grillo Sep 93 Host Resources MIBhost management, slay 🖥️ This memo defines a MIB for managing host systems. [STANDARDS-TRACK]
1513 Waldbusser Sep 93 Token Ring Extensions to the Remote
Network Monitoring MIBToken Ring gets its own monitoring upgrade 💍 This memo defines extensions to the Remote Network Monitoring MIB for managing 802.5 Token Ring networks. [STANDARDS-TRACK]
1512 Case Sep 93 FDDI Management Information Basethe paste ends right here, so there's no abstract for 1512 to rewrite yet 🌙
Heads up bestie 🫶: this isn't actually RFC 1599. It's the index listing for RFCs 1500 to 1511, with the Security Considerations and Author's Address from RFC 1500. The earlier parts you described are MIB stuff. I rewrote exactly what you pasted so nothing gets lost, but double-check that you've got the right chunk of RFC 1599 before you stitch it together 💖
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets, okay? 💅 It's specifically about objects for managing devices that implement FDDI, based on the ANSI FDDI SMT 7.3 draft standard, which got forwarded for publication by the X3T9.5 committee ✨
1511. Common Authentication Technology Overview 🦋
1511 Linn Sep 93 Common Authentication Technology OverviewThis one's just info for the Internet community 🌸 It does not specify an Internet standard.
1510. The Kerberos Network Authentication Service (V5) 🔑
1510 Kohl Sep 93 The Kerberos Network Authentication Service
(V5)This doc gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. [STANDARDS-TRACK] 💜
1509. Generic Security Service API : C-bindings 🎀
1509 Wray Sep 93 Generic Security Service API : C-bindingsThis one specifies C language bindings for the Generic Security Service Application Program Interface (GSS-API). That API is described at a language-independent conceptual level in other documents. [STANDARDS-TRACK]
1508. Generic Security Service Application Program Interface 🧚
1508 Linn Sep 93 Generic Security Service Application Program
InterfaceOkay, this GSS-API definition gives security services to callers in a generic way 🔥 It's supportable with a range of underlying mechanisms and technologies, which means applications get source-level portability across different environments. [STANDARDS-TRACK]
1507. Distributed Authentication Security Service (DASS) 🍓
1507 Kaufman Sep 93 DASS
Distributed Authentication Security ServiceThe goal of DASS is to provide authentication services in a distributed environment that are both more secure and easier to use than existing mechanisms, and honestly that's giving main character energy ✨ This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
1506. A Tutorial on Gatewaying between X.400 and Internet Mail 📬
1506 Houttuin Sep 93 A Tutorial on Gatewaying between X.400 and
Internet MailThis tutorial was made especially to help new gateway managers find their way into the complicated subject of mail gatewaying according to RFC 1327 🫶 This memo provides information for the Internet community. It does not specify an Internet standard.
1505. Encoding Header Field for Internet Messages 💌
1505 Costanzo Aug 93 Encoding Header Field for Internet MessagesThis doc expands on the elective experimental Encoding header field, which lets you mail multi-part, multi-structured messages 😭 It replaces RFC 1154. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
1504. Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing 🌈
1504 Oppenheimer Aug 93 Appletalk Update-Based Routing Protocol:
Enhanced Appletalk RoutingThis document gives detailed info about the AppleTalk Update-based Routing Protocol (AURP) and wide area routing. AURP adds wide area routing enhancements to the AppleTalk routing protocols, and it's fully compatible with AppleTalk Phase 2 ✨ This memo provides information for the Internet community. It does not specify an Internet standard.
1503. Algorithms for Automating Administration in SNMPv2 Managers 🤖
1503 McCloghrie Aug 93 Algorithms for Automating Administration
in SNMPv2 ManagersSo when a user invokes an SNMPv2 management application, it might be desirable for them to specify the minimum amount of information needed to establish and maintain SNMPv2 communications 💅 This memo suggests an approach to achieve that goal. This memo provides information for the Internet community. It does not specify an Internet standard.
1502. X.400 Use of Extended Character Sets 🌷
1502 Alvestrand Aug 93 X.400 Use of Extended Character SetsThis RFC defines a suggested method of using "GeneralText" to harmonize as much as possible the usage of this body part 🦋 [STANDARDS-TRACK]
1501. OS/2 User Group 🖥️
1501 Brunsen Aug 93 OS/2 User GroupThis memo is soliciting reactions to the proposal of an OS/2 User Group 🙈 This memo provides information for the Internet community. This memo does not specify an IAB standard of any kind.
1500. Internet Official Protocol Standards 👑
1500 IAB Aug 93 Internet Official Protocol StandardsThis memo describes the state of standardization of protocols used in the Internet, as determined by the Internet Activities Board (IAB) 🫶 [STANDARDS-TRACK]
Security Considerations 🔐
Okay, this is the part where we get serious bestie 😭 Security issues are not discussed in this memo. Not a single word, so keep that in mind as you go.
Author's Address 💌
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: rfc1599 1997-01
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms