RFC 1899

Request for Comments Summary ✨

• RFC: 1899 🎀
• Working group: Network Working Group 🧚
• Author: J. Elliott, ISI 💖
• Category: Informational 🌸
• Date: January 1997 📅
• Obsoletes / Updates: neither is listed in the header 🙈
• Covers: RFC Numbers 1800-1899 💜

---

Status of This Memo 📜

okay bestie, this is the official "what even is this" part 🫶 It's a slightly annotated list of the 100 RFCs from RFC 1800 through RFCs 1899, and it's a status report on those RFCs ✨ This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited 🌈

Note 🦋

ngl this part is so important 😭 Many 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, check the latest edition of "Internet Official Protocol Standards" 💜 In the list below, RFCs on the standards track are marked [STANDARDS-TRACK] 🎀

Here's the table header, so you know what's what 💅

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

1899    Elliott      Jan 97   Requests For Comments Summary

---

1899 · Elliott · Jan 97 · Requests For Comments Summary

Obviously this memo 🙈 It's describing itself, iconic.

1898 · Eastlake · Feb 96 · CyberCash Credit Card Protocol Version 0.8

This one only covers the current CyberCash system 💸 which is one of the few operational systems in the rapidly evolving area of Internet payments 🫶 It provides information for the Internet community and does not specify an Internet standard of any kind 🌸

1897 · Hinden · Jan 96 · IPv6 Testing Address Allocation

This describes an allocation plan for IPv6 addresses to be used in testing IPv6 prototype software 🧪 It specifies an Experimental protocol for the Internet community ✨

1896 · Resnick · Feb 96 · The text/enriched MIME Content-type

This defines one particular type of MIME data, the text/enriched MIME type 🎀 It provides information for the Internet community and does not specify an Internet standard of any kind 💖

1895 · Levinson · Feb 96 · The Application/CALS-1840 Content-type

This gives guidelines for using the United States Department of Defense Military Standard MIL-STD-1840, "Automated Interchange of Technical Information," with the Internet electronic mail standards, RFC 822 and RFC 1521 💌 It provides information for the Internet community and does not specify an Internet standard of any kind 🌈

1894 · Moore · Jan 96 · An Extensible Message Format for Delivery Status Notifications

This defines a MIME content-type that a message transfer agent (MTA) or electronic mail gateway may use to report the result of an attempt to deliver a message to one or more recipients 📬 [STANDARDS-TRACK] ✨

1893 · Vaudreuil · Jan 96 · Enhanced Mail System Status Codes

bestie, this one is so relatable 😭 There currently isn't a standard mechanism for reporting mail system errors, apart from the limited set SMTP offers and the system-specific text descriptions sent in mail messages. There's a pressing need for a rich, machine-readable status code for use in delivery status notifications [DSN]. This document proposes a new set of status codes for that purpose 🔥 [STANDARDS-TRACK]

1892 · Vaudreuil · Jan 96 · The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages

The Multipart/Report MIME content-type is a general "family" or "container" type for electronic mail reports of any kind 💜 This memo only defines using it for delivery status reports, but mail processing programs benefit when one content-type is used for all kinds of reports 💅 [STANDARDS-TRACK]

1891 · Moore · Jan 96 · SMTP Service Extension for Delivery Status Notifications

This defines an extension to the SMTP service that lets an SMTP client specify:

• (a) that delivery status notifications (DSNs) should be generated under certain conditions 🎀
• (b) whether such notifications should return the contents of the message 🧁
• (c) additional information, to be returned with a DSN, that lets the sender identify both the recipient(s) the DSN was issued for and the transaction in which the original message was sent 🔍

[STANDARDS-TRACK]

1890 · A.V.T.W.G. · Jan 96 · RTP Profile for Audio and Video Conferences with Minimal Control

This describes a profile for using the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control 🎤 [STANDARDS-TRACK]

1889 · A.V.T.W.G. · Jan 96 · RTP: A Transport Protocol for Real-Time Applications

This describes RTP, the real-time transport protocol 🚀 RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services 📡 [STANDARDS-TRACK]

1888 · Bound · Aug 96 · OSI NSAPs and IPv6

This document recommends that network implementors who have planned or deployed an OSI NSAP addressing plan, and who wish to deploy or transition to IPv6, should redesign a native IPv6 addressing plan to meet their needs 🌷 This memo defines an Experimental Protocol for the Internet community.

1887 · Rekhter · Dec 95 · An Architecture for IPv6 Unicast Address Allocation

This provides an architecture for allocating IPv6 [1] unicast addresses in the Internet 🏗️ It provides information for the Internet community and does not specify an Internet standard of any kind 💖

1886 · Thomson · Dec 95 · DNS Extensions to support IP version 6

This defines the changes the Domain Name System needs to support hosts running IP version 6 (IPv6) 🌐 [STANDARDS-TRACK]

1885 · Conta · Dec 95 · Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)

This specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6) 💬 [STANDARDS-TRACK]

1884 · Hinden · Dec 95 · IP Version 6 Addressing Architecture

This specification defines the addressing architecture of the IP Version 6 protocol [IPV6] 🏛️ [STANDARDS-TRACK]

1883 · Deering · Dec 95 · Internet Protocol, Version 6 (IPv6) Specification

This specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng 👑 [STANDARDS-TRACK]

1882 · Hancock · Dec 95 · The 12-Days of Technology Before Christmas

A festive one 🎄 It provides information for the Internet community and does not specify an Internet standard of any kind ⭐

1881 · IAB & IESG · Dec 95 · IPv6 Address Allocation Management

The IPv6 address space will be managed by the IANA for the good of the Internet community 🌍 with advice from the IAB and the IESG, by delegation to the regional registries. It provides information for the Internet community and does not specify an Internet standard of any kind 🧡

1880 · I.A.B. · Nov 95 · INTERNET OFFICIAL PROTOCOL STANDARDS

This describes the state of standardization of protocols used in the Internet, as determined by the Internet Architecture Board (IAB) 📋 [STANDARDS-TRACK]

1879 · Manning · Jan 96 · Class A Subnet Experiment Results and Recommendations

This documents some experiences with the RFC 1797 [1] subnet A experiment (performed by the Net39 Test Group (see credits)) and gives a number of recommendations on future direction for both the Internet Registries and the Operations community 🧪 It provides information for the Internet community and does not specify an Internet standard of any kind 💜

1878 · Pummill · Dec 95 · Variable Length Subnet Table For IPv4

This clarifies issues surrounding subnetting IP networks by providing a standard subnet table 📊 It provides information for the Internet community and does not specify an Internet standard of any kind 🌸

1877 · Cobb · Dec 95 · PPP Internet Protocol Control Protocol Extensions for Name Server Addresses

This extends the NCP for establishing and configuring the Internet Protocol over PPP [2], defining the negotiation of primary and secondary Domain Name System (DNS) [3] and NetBIOS Name Server (NBNS) [4] addresses 🎀 It provides information for the Internet community and does not specify an Internet standard of any kind 💖

1876 · Davis · Jan 96 · A Means for Expressing Location Information in the Domain Name System

This defines a new DNS RR type for experimental purposes 🧪 It describes a mechanism to allow the DNS to carry location information about hosts, networks, and subnets 📍 This memo defines an Experimental Protocol for the Internet community.

1875 · Berge · Dec 95 · UNINETT PCA Policy Statements

This provides information about policy statements submitted by the UNINETT Policy Certification Authority (UNINETT PCA) 🔐 It provides information for the Internet community and does not specify an Internet standard of any kind ✨

1874 · Levinson · Dec 95 · SGML Media Types

This proposes new media sub-types of Text/SGML and Application/SGML 📄 This memo defines an Experimental Protocol for the Internet community.

1873 · Levinson · Dec 95 · Message/External-Body Content-ID Access Type

The existing MIME Content-Type Message/External-Body access-types allow a MIME entity (body-part) to refer to an object that isn't in the message, by specifying how to access that object 🔗 The Content-ID access method described in this document gives you the capability to refer to an object within the message 💜 This memo defines an Experimental Protocol for the Internet community.

1872 · Levinson · Dec 95 · The MIME Multipart/Related Content-type

Multipart/Related gives a common mechanism for representing objects that are aggregates of related MIME body parts 🧩 This document defines the Multipart/Related content-type and provides examples of its use 🌷 This memo defines an Experimental Protocol for the Internet community.

1871 · Postel · Nov 95 · Addendum to RFC 1602 -- Variance Procedure

This describes a modification to the IETF procedures that lets you escape from a situation where the existing procedures are not working or do not seem to apply 🛟 This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements 💬

1870 · Klensin · Nov 95 · SMTP Service Extension for Message Size Declaration

This defines an extension to the SMTP service where an SMTP client and server interact to give the server an opportunity to decline (perhaps temporarily) to accept a message, based on the client's estimate of the message size 📏 [STANDARDS-TRACK]

1869 · Klensin · Nov 95 · SMTP Service Extensions

This defines a framework for extending the SMTP service, by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports 🧩 [STANDARDS-TRACK]

1868 · Malkin · Nov 95 · ARP Extension - UNARP

okay this one's cut off in my copy 🥺 This document specifies a trivial modification to the ARP mechanism, not

I think this is the RFC index listing for RFCs 1830 to 1867, not the text of RFC 1899, and I can't tell where it fits in the earlier parts. I've rewritten exactly what you pasted, with every number, name, date and tag kept as written.

The ARP fragment at the top is the tail of an entry that started before this excerpt. Its number isn't in the text, so I haven't guessed one.

ARP tables getting updated when a node leaves the network 🦋 This memo defines an Experimental Protocol for the Internet community 🧪

📚 RFC Index Excerpt (RFCs 1830 to 1867)

RFC 1867 ✨

1867    Nebel        Nov 95   Form-based File Upload in HTML

File upload is something basically every app needs 📎 so bestie, this one proposes an HTML extension that lets information providers ask for file uploads in a uniform way, plus a MIME compatible representation for the file upload responses 💌 It's an Experimental Protocol for the Internet community.

RFC 1866 🌸

1866    Berners-Lee  Nov 95   Hypertext Markup Language - 2.0

This one defines HTML 2.0 🧡 It's named that way so nobody mixes it up with the earlier informal specs 📄 [STANDARDS-TRACK]

RFC 1865 🧚

1865    Houser       Jan 96   EDI Meets the Internet: Frequently Asked
                              Questions about Electronic Data
                              Interchange (EDI) on the Internet

This memo is for the EDI crowd who are new to the Internet, like EDI software devs, users and service providers 🛍️ It walks through the Internet and assumes you already know your EDI basics. It provides information for the Internet community, and it does not specify an Internet standard of any kind 🙈

RFC 1864 💜

1864    Myers        Oct 95   The Content-MD5 Header Field

Here we get an optional header field, Content-MD5, for MIME-conformant messages 💅 [STANDARDS-TRACK]

RFC 1863 🌈

1863    Haskin       Oct 95   A BGP/IDRP Route Server alternative to a
                              full mesh routing

This one describes the use and detailed design of Route Servers, which pass routing info around between BGP/IDRP speaking routers 🛰️ It's an Experimental Protocol for the Internet community 🧪

RFC 1862 🎀

1862    McCahill     Nov 95   Report of the IAB Workshop on Internet
                              Information Infrastructure,
                              October 12-14, 1994

This is a report on an Internet architecture workshop that the IAB started and held at MCI on October 12-14, 1994 🏛️ It mostly looked at the information infrastructure on the Internet. It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1861 📟

1861    Gwinn        Oct 95   Simple Network Paging Protocol -
                              Version 3 - Two-Way Enhanced

This RFC suggests a simple way to deliver wireless messages to the right receiving devices, whether they're one-way or two-way 📟 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1860 🍓

1860    Pummill      Oct 95   Variable Length Subnet Table For IPv4

This one itemizes the potential values for IPv4 subnets 🔢 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1859 🦋

1859    Pouffary     Oct 95   ISO Transport Class 2 Non-use of
                              Explicit Flow Control over
                              TCP RFC1006 extension

This is an extension to STD35, RFC1006, which is a standard for the Internet community 🫶 It doesn't repeat the protocol definitions in RFC1006 or International Standard ISO 8073. Instead, it adds how to implement ISO Transport Class 2 Non-use of Explicit Flow Control on top of TCP ✨ It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1858 🔥

1858    Ziemba       Oct 95   Security Considerations for
                              IP Fragment Filtering

Okay this one is spicy 🌶️ IP fragmentation can be used to disguise TCP packets from the IP filters in routers and hosts 😱 This doc describes two attack methods and the remedies to stop them 🛡️ It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1857 📊

1857    Lambert      Oct 95   A Model for Common Operational
                              Statistics

This memo describes a model for operational statistics on the Internet 📈 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1856 🧮

1856    Clark        Shpt 95   The Opstat Client-Server Model for
                              Statistics Retrieval

This doc defines a model and protocol for a set of tools that NSPs and Network Operation Centers (NOCs) could use to share data with each other and with customers 🤝 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1855 🌷

1855    Hambridge    Oct 95   Netiquette Guidelines

These are a minimum set of Network Etiquette (Netiquette) guidelines that organizations can take and adapt for their own use 💌 Be nice, be kind 🫶 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1854 🛤️

1854    Freed        Oct 95   SMTP Service Extension for
                              Command Pipelining

This memo defines an extension to the SMTP service where a server can say how well it can accept multiple commands in a single TCP send operation 🚀 [STANDARDS-TRACK]

RFC 1853 🌊

1853    Simpson      Oct 95   IP in IP Tunneling

This doc discusses implementation techniques for using IP Protocol/Payload number 4 Encapsulation for tunneling with IP Security and other protocols 🕳️ It provides information for the Internet community. It does not specify an Internet standard.

RFC 1852 🔐

1852    Metzger      Spt 95   IP Authentication using Keyed SHA

This document describes using keyed SHA with the IP Authentication Header 🗝️ It defines an Experimental Protocol for the Internet community 🧪

RFC 1851 🛡️

1851    Karn         Spt 95   The ESP Triple DES Transform

This doc describes the Triple DES-CBC security transform for the IP Encapsulating Security Payload (ESP) 🔒 It defines an Experimental Protocol for the Internet community 🧪

RFC 1850 🗺️

1850    Baker        Nov 95   OSPF Version 2 Management
                              Information Base

This memo defines a piece of the Management Information Base (MIB) for network management protocols in TCP/IP-based internets 🧭 It specifically defines objects for managing the Open Shortest Path First Routing Protocol. [STANDARDS-TRACK]

RFC 1849 💀

1849    Never Issued.

Yeah, this number never got issued 💀

RFC 1848 📬

1848    Crocker      Oct 95   MIME Object Security Services

This doc defines MIME Object Security Services (MOSS) 🔏 It's a protocol that uses the multipart/signed and multipart/encrypted framework [7] to apply digital signature and encryption services to MIME objects. [STANDARDS-TRACK]

RFC 1847 🖋️

1847    Galvin       Oct 95   Security Multiparts for MIME:
                              Multipart/Signed and Multipart/Encrypted

This one defines a framework for applying security services to MIME body parts 🧩 [STANDARDS-TRACK]

RFC 1846 🚫

1846    Durand       Spt 95   SMTP 521 Reply Code

This memo defines a brand new SMTP [1] reply code, 521 🙅 It can be used to say that an Internet host does not accept incoming mail 📭 It defines an Experimental Protocol for the Internet community 🧪

RFC 1845 ⏯️

1845    Crocker      Spt 95   SMTP Service Extension
                              for Checkpoint/Restart

This memo defines an extension to the SMTP service so an interrupted SMTP transaction can be restarted later, without having to repeat all the commands and message content sent before the interruption 🔄 It defines an Experimental Protocol for the Internet community 🧪

RFC 1844 🧐

1844    Huizer       Aug 95   Multimedia E-mail (MIME) User
                              Agent checklist

This doc gives you a checklist to help evaluate MIME capable User Agents 📋 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1843 🇨🇳

1843    Lee          Aug 95   HZ - A Data Format for Exchanging Files
                              of Arbitrarily Mixed Chinese and ASCII
                              characters

The content here is identical to an article with the same title that the author wrote on September 4, 1989 📜 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1842 🀄

1842    Wei          Aug 95   ASCII Printable Characters-Based Chinese
                              Character Encoding for Internet Messages

This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages over the Internet 💬 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1841 📡

1841    Chapman      Spt 95   PPP Network Control Protocol for
                              LAN Extension

Telecom infrastructure is getting better, offering higher bandwidth at lower cost 🚄 Access is shifting from modems to smarter devices 🧠 This informational RFC talks about a PPP Network Control Protocol for one of those smart devices. The protocol is the LAN extension interface protocol. It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1840 🫥

1840    Never Issued.

Another number that never got issued 🫥

RFC 1839 🫥

1839    Never Issued.

Also never issued 🫥

RFC 1838 🗂️

1838    Kille        Aug 95   Use of the X.500 Directory to support
                              mapping between X.400 and RFC 822
                              Addresses

This doc defines how to use the directory to support mapping between X.400 O/R Addresses and the mailboxes defined in RFC 1327 [2] 📇 It defines an Experimental Protocol for the Internet community 🧪

RFC 1837 🌳

1837    Kille        Aug 95   Representing Tables and Subtrees in the
                              X.500 Directory

This doc defines techniques for representing two types of information mapping in the OSI Directory 🌲 It defines an Experimental Protocol for the Internet community 🧪

RFC 1836 🌿

1836    Kille        Aug 95   Representing the O/R Address hierarchy
                              in the X.500 Directory Information Tree

This one defines a representation of the O/R Address hierarchy in the Directory Information Tree [6, 1] 🌿 It defines an Experimental Protocol for the Internet community 🧪

RFC 1835 🕵️

1835    Deutsch      Aug 95   Architecture of the WHOIS++ service

This doc describes WHOIS++, which extends the trivial WHOIS service from RFC 954 so WHOIS-like servers can share more structured info with the Internet 🔎 [STANDARDS-TRACK]

RFC 1834 🔍

1834    Gargano      Aug 95   Whois and Network Information
                              Lookup Service Whois++

This memo describes new features for WHOIS 🆕 It provides information for the Internet community, and it does not specify an Internet standard of any kind.

RFC 1833 🧶

1833    Srinivasan   Aug 95   Binding Protocols for ONC RPC Version 2

This document describes the binding protocols used together with the ONC Remote Procedure Call (ONC RPC Version 2) protocols 🪢 [STANDARDS-TRACK]

RFC 1832 📦

1832    Srinivasan   Aug 95   XDR: External Data Representation
                              Standard

This doc describes the External Data Representation Standard (XDR) protocol as it's currently deployed and accepted 📦 [STANDARDS-TRACK]

RFC 1831 📞

1831    Srinivasan   Aug 95   RPC: Remote Procedure Call Protocol
                              Specification Version 2

This doc describes the ONC Remote Procedure Call (ONC RPC Version 2) protocol as it's currently deployed and accepted 📞 [STANDARDS-TRACK]

RFC 1830 🌙

1830    Vaudreuil    Aug 95   SMTP Service Extensions for Transmission
                              of Large and Binary MIME Messages

The rest of this one picks up in the next part 🌙

🚨 bestie, heads up before the tea: this chunk doesn't look like RFC 1899 to me. It's an index of RFCs 1800 to 1829 with a short abstract, a Security Considerations section and an Author's Address, and there's no title block. I've rewritten exactly what you pasted. I also don't have parts 1 or 2, so if you meant a different document, paste that one and I'll redo it. 💕

okay so this memo defines two extensions to the SMTP service 💌 The first one lets an SMTP client and server negotiate an alternate DATA command, BDAT, for sending big MIME messages way more efficiently ✨ The second extension builds on BDAT so the two can agree to send unencoded binary data 🔥 This memo defines an Experimental Protocol for the Internet community 🧪

1829    Karn         Aug 95   The ESP DES-CBC Transform

Okay this one is all about the DES-CBC security transform for the IP Encapsulating Security Payload (ESP) 🔐 It's on the standards track [STANDARDS-TRACK] 💅

1828    Metzger      Aug 95   IP Authentication using Keyed MD5

This one covers using keyed MD5 with the IP Authentication Header 🔑 [STANDARDS-TRACK] 🫶

1827    Atkinson     Aug 95   IP Encapsulating Security Payload (ESP)

ESP is the mechanism that gives IP datagrams integrity and confidentiality, and it's giving main character energy 👑 [STANDARDS-TRACK]

1826    Atkinson     Aug 95   IP Authentication Header

This one describes a mechanism for cryptographic authentication of IPv4 and IPv6 datagrams. Obsessed 🛡️ [STANDARDS-TRACK]

1825    Atkinson     Aug 95   Security Architecture for the Internet
                              Protocol

This memo lays out the security mechanisms for IP version 4 (IPv4) and IP version 6 (IPv6), plus the services they provide 🏰 [STANDARDS-TRACK]

---

1824    Danisch      Aug 95   The Exponential Security System TESS:
                              An Identity-Based Cryptographic Protocol
                              for Authenticated Key-Exchange
                              (E.I.S.S.-Report 1995/4)

This informational RFC walks through the basic mechanisms and functions of an identity-based system for securely and authenticatedly exchanging cryptographic keys, generating signatures, and distributing public keys in an authentic way 🧚 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1823    Howes        Aug 95   The LDAP Application Program Interface

This one defines a C language application program interface to the lightweight directory access protocol (LDAP) 💜 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1822    Lowe         Aug 95   A Grant of Rights to Use a Specific IBM
                              patent with Photuris

This one records a grant from IBM Corporation that lets people freely use one of its patents, but only under certain conditions 🤝 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1821    Borden       Aug 95   Integration of Real-time Services in an
                              IP-ATM Network Architecture

This paper's whole purpose is to clearly lay out what needs sorting out when you connect the IP integrated services environment with an ATM service environment, so the two work as one seamless interface for end users who want real-time networking 🎀 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1820    Huizer       Aug 95   Multimedia E-mail (MIME) User Agent
                              Checklist

This document is a checklist that makes it easier to evaluate MIME-capable User Agents 📋 It also describes how to access a MIME test-responder that generates test messages 🍓 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1819    ST2 W.G.     Aug 95   Internet Stream Protocol Version 2 (ST2)
                              Protocol Specification - Version ST2+

This memo has a revised spec for the Internet STream Protocol Version 2 (ST2) 🌊 This memo defines an Experimental Protocol for the Internet community.

1818    Postel       Aug 95   Best Current Practices

This document kicks off a new series of documents about best current practices for the Internet community 📚 Documents in this series carry the endorsement of the Internet Engineering Steering Group (IESG) ✅

1817    Rekhter      Aug 95   CIDR and Classful Routing

This document shows the IAB's (Internet Architecture Board) take on what CIDR means, now and soon, for organizations that still use Classful routing technology 🗺️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1816    F.N.C.       Aug 95   U.S. Government Internet Domain Names

This memo updates and clarifies RFC 1811 ✏️ It also describes the registration policies for the top-level domain .GOV 🏛️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1815    Ohta         Jul 95   Character Sets ISO-10646 and
                              ISO-10646-J-1

Using ISO 10646 in practice needs a lot of extra profiling, like restricting which characters you can use, restricting how they combine, and adding language info 🌏 This memo gives information on that profiling and names the charset for each profiled instance 💬 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1814    Gerich       Jun 95   Unique Addresses are Good

The IAB suggests that RFC 1597 reserves IP address space for private networks that are isolated and will stay isolated from the Internet 🏝️ But any enterprise that expects external connectivity to the Internet should get a globally unique address from an Internet registry or service provider 🌐 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

---

1813    Callaghan    Jun 95   NFS Version 3 Protocol Specification

This paper describes the NFS version 3 protocol 📁 It's shared so people can write compatible implementations 🫶 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1812    Baker        Jun 95   Requirements for IP Version 4 Routers

This memo defines and discusses requirements for devices that do the network layer forwarding function of the Internet protocol suite 🚦 [STANDARDS-TRACK]

1811    F.N.C.       Jun 95   U.S. Government Internet Domain Names

This document describes the registration policies for the top-level domain .GOV 🏛️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1810    Touch        Jun 95   Report on MD5 Performance

This RFC looks at how fast MD5 can be implemented in software and in hardware, and whether it can keep up with currently available IP bandwidth 🏎️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1809    Partridge    Jun 95   Using the Flow Label Field in IPv6

The point of this memo is to distill the opinions and suggestions of the End-to-End Research Group about handling Flow Labels into a set of suggestions for IPv6 🏷️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1808    Fielding     Jun 95   Relative Uniform Resource Locators

When the base URL is well-defined and known to the parser (human or machine), it's super useful to embed URL references that inherit that context instead of re-specifying it every time 🔗 This document defines the syntax and semantics for these Relative Uniform Resource Locators. [STANDARDS-TRACK]

1807    Lasher       Jun 95   A Format for Bibliographic Records

This RFC defines a format for bibliographic records that describe technical reports 📖 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1806    Troost       Jun 95   Communicating Presentation Information
                              in Internet Messages: The
                              Content-Disposition Heade

This memo gives messages that follow the [RFC 1521] ("MIME") specification a way to carry presentational information 🎨 This memo defines an Experimental Protocol for the Internet community.

1805    Rubin        Jun 95   Location-Independent Data/Software
                              Integrity Protocol

This memo describes a protocol for adding integrity assurance to files that get distributed across the Internet 🔏 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1804    Mansfield    Jun 95   Schema Publishing in X.500 Directory

In this document, the proposed solution uses the existing mechanisms of the directory [1] itself 📂 It comes with a naming scheme for schema objects and a meta-schema for storing those objects in the directory 🗂️ This memo defines an Experimental Protocol for the Internet community.

1803    Wright       Jun 95   Recommendations for an X.500 Production
                              Directory Service

This document is a set of basic recommendations for a country-level X.500 DSA 🌍 This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

1802    Alvestrand   Jun 95   Introducing Project Long Bud: Internet
                              Pilot Project for the Deployment of
                              X.500 Directory Information in Support
                              of X.400 Routing

This memo describes a proposed Internet Pilot Project that wants to prove the MHS-DS approach on a bigger scale 🚀 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1801    Kille        Jun 95   X.400-MHS use of the X.500 Directory to
                              support X.400-MHS Routing

The key problem in routing is mapping an O/R Address onto an MTA (next hop) 🗺️ This shall be an MTA that is, in some sense, "nearer" to the destination UA 🎯 You keep doing this until the message can go straight to the recipient UA 📬 This memo defines an Experimental Protocol for the Internet community.

1800    I.A.B.       Jul 95   INTERNET OFFICIAL PROTOCOL STANDARDS

This memo describes the state of standardization of protocols used on the Internet, as determined by the Internet Architecture Board (IAB) 📜 [STANDARDS-TRACK]

---

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