RFC 2399
Request for Comments Summary
The Basics 🎀
okay bestie, this is RFC 2399: Request for Comments Summary ✨ It was written by A. Ramos at ISI, it's Informational (so it's just info for the Internet community, not a standard 💅), and it's dated January 1999. It covers RFC Numbers 2300-2399. The header doesn't list anything this one obsoletes or updates, so no drama there 🫶
Status of This Memo 🌸
this RFC is a slightly annotated list of the 100 RFCs from RFC 2300 through RFC 2399. it's basically a status report on those RFCs. it gives info to the Internet community and does not specify an Internet standard of any kind. distribution of this memo is unlimited 🦋
Copyright Notice 🌈
the copyright belongs to The Internet Society: Copyright (C) The Internet Society (1999). All Rights Reserved.
Note 📝
so, many RFCs (but not all) are Proposed Standards, Draft Standards, or Standards. the status can change during standards processing, so this doc only says whether each one is 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] 💜
The RFCs 📚
RFC 2399: Request for Comments Summary 💖
Ramos, Jan 1999. This memo, obviously 🙈
RFC 2398: Some Testing Tools for TCP Implementors 🔧
Parker, Aug 1998. this one lists only tools that can evaluate one or more TCP implementations, or that can provide specific results describing or evaluating the TCP being tested. it's informational, so no standard here 💅
RFC 2397: The "data" URL scheme 🧚
Masinter, Aug 1998. this defines a new URL scheme, "data". it lets you include small data items as "immediate" data, like they were included externally. [STANDARDS-TRACK] ✨
RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax 👑
Berners-Lee, Aug 1998. this defines a grammar that's a superset of all valid URIs. the point is that an implementation can parse the common parts of a URI reference without knowing the scheme-specific rules of every possible identifier type. [STANDARDS-TRACK] 🫶
RFC 2395: IP Payload Compression Using LZS 🍓
Friend, Dec 1998. this describes a compression method based on the LZS algorithm, and defines how LZS applies to the IP Payload Compression Protocol. informational 💜
RFC 2394: IP Payload Compression Using DEFLATE 🌈
Pereira, Dec 1998. this describes a compression method based on the DEFLATE algorithm, and defines how DEFLATE applies to the IP Payload Compression Protocol. informational, obviously 💅
RFC 2393: IP Payload Compression Protocol (IPComp) 🔥
Shacham, Dec 1998. this describes a protocol for lossless compression of Internet Protocol datagrams in an Internet environment. [STANDARDS-TRACK] 💖
RFC 2392: Content-ID and Message-ID Uniform Resource Locators 🦋
Levinson, Aug 1998. the URL schemes "cid:" and "mid:" let you reference messages and their body parts. like, inside one multipart message, an HTML body part might embed references to other parts of that same message. [STANDARDS-TRACK] 🎀
RFC 2391: Load Sharing using IP Network Address Translation (LSNAT) 🌸
Srisuresh, Aug 1998. this extends the use of NATs to offer a load sharing feature, so session load can be spread across a pool of servers instead of going to one single server. informational ✨
RFC 2390: Inverse Address Resolution Protocol 🧚
Bradley, Sep 1998. this adds to ARP so a station can ask for the protocol address that goes with a given hardware address. [STANDARDS-TRACK] 👑
RFC 2389: Feature negotiation mechanism for the File Transfer Protocol 💜
Hethmon, Aug 1998. this gives FTP clients a way to discover which new features a particular FTP server supports. [STANDARDS-TRACK] 🫶
RFC 2388: Returning Values from Forms: multipart/form-data 🍓
Masinter, Aug 1998. this defines the Internet Media Type multipart/form-data. it can be used by lots of applications and carried by lots of protocols to return a set of values from a user filling out a form. [STANDARDS-TRACK] 🌈
RFC 2387: The MIME Multipart/Related Content-type 💖
Levinson, Aug 1998. this defines the Multipart/Related content-type and gives examples of how to use it. [STANDARDS-TRACK] 🦋
RFC 2386: A Framework for QoS-based Routing in the Internet 🔥
Crawley, Aug 1998. this describes some QoS-based routing issues and requirements, then proposes a framework for QoS-based routing in the Internet. informational 💅
RFC 2385: Protection of BGP Sessions via the TCP MD5 Signature Option 🔐
Heffernan, Aug 1998. this describes a TCP extension that boosts security for BGP. [STANDARDS-TRACK] ✨
RFC 2384: POP URL Scheme 📬
Gellens, Aug 1998. this defines a URL scheme for referencing a POP mailbox. [STANDARDS-TRACK] 🌸
RFC 2383: ST2+ over ATM Protocol Specification - UNI 3.1 Version ⚡
Suzuki, Aug 1998. this specifies an ATM-based protocol for communication between ST2+ agents. informational 🧚
RFC 2382: A Framework for Integrated Services and RSVP over ATM 🌐
Crawley, Aug 1998. this outlines the issues and framework for providing IP Integrated Services with RSVP over ATM. informational 👑
RFC 2381: Interoperation of Controlled-Load Service and Guaranteed Service with ATM 🍓
Garrett, Aug 1998. this gives guidelines for mapping service classes, plus traffic management features and parameters, between Internet and ATM technologies. [STANDARDS-TRACK] 💜
RFC 2380: RSVP over ATM Implementation Requirements 📋
Berger, Aug 1998. this presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). the requirements make sure implementations interoperate and conform to the RSVP and Integrated Services specifications. [STANDARDS-TRACK] 🫶
RFC 2379: RSVP over ATM Implementation Guidelines 🛠️
Berger, Aug 1998. this presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). this one is an Internet Best Current Practices document for the Internet community, and it asks for discussion and suggestions for improvements 🌈
RFC 2378: The CCSO Nameserver (Ph) Architecture 🗂️
Hedberg, Sep 1998. the Ph Nameserver from the Computing and Communications Services Office (CCSO) at the University of Illinois at Urbana-Champaign has been used by several organizations as a publicly available database of information about people and other things. this document gives a formal definition of the client-server protocol. informational 💖
RFC 2377: Naming Plan for Internet Directory-Enabled Applications 🦋
Grimstad, Sep 1998. the authors found that the conventional X.500 approach to naming has been an obstacle to wide deployment of directory-enabled applications on the Internet. so they propose a new directory naming plan that borrows the strengths of the most popular Internet naming schemes for naming objects in a hierarchical directory. informational 🔥
RFC 2376: XML Media Types 📄
Whitehead, Jul 1998. this proposes two new media subtypes, text/xml and application/xml, for exchanging network entities that are conforming Extensible Markup Language (XML). informational ✨
RFC 2375: IPv6 Multicast Address Assignments 🌸
Hinden, Jul 1998. this defines the initial assignment of IPv6 multicast addresses. informational 🧚
RFC 2374: An IPv6 Aggregatable Global Unicast Address Format 👑
Hinden, Jul 1998. this defines an IPv6 aggregatable global unicast address format for use in the Internet. [STANDARDS-TRACK] 💜
RFC 2373: IP Version 6 Addressing Architecture 🍓
Hinden, Jul 1998. this specifies the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK] 🫶
RFC 2372: Transaction Internet Protocol - Requirements and Supplemental Information 🌈
Evans, Jul 1998. this describes the purpose (usage scenarios) and the requirements for the Transaction Internet Protocol. informational 💅
RFC 2371: Transaction Internet Protocol Version 3.0 ⭐
Lyon, Jul 1998. in lots of apps where different nodes cooperate on some work, you need to guarantee the work happens atomically. that means every node has to reach the same conclusion about whether the work gets completed, even when things fail. this doc proposes a simple, easy-to-implement protocol for that. [STANDARDS-TRACK] 🔥
RFC 2370: The OSPF Opaque LSA Option 🗺️
Coltun, Jul 1998. this defines enhancements to OSPF that support a new class of link-state advertisements (LSAs) called Opaque LSAs. [STANDARDS-TRACK] ✨
RFC 2369: The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields 📮
Neufeld, Jul 1998. okay so the mailing list command specification header fields are a set of… 👀
the rest of this entry, plus all the good stuff after it, is coming up in part 2 🎀💖
structured fields tucked into email messages sent out by email distribution lists 💌
bestie, when list servers include these header fields, mail clients can whip up automated tools so users can run list functions right from their inbox ✨. That could look like a menu item, a push button, or some other UI element 🎀. The whole vibe is simplifying things: one common interface for the super cryptic, all-over-the-place mailing list manager commands 💅 [STANDARDS-TRACK]
2368 Hoffman Jul 1998 The mailto URL schemethis one defines the format of URLs (Uniform Resource Locators) for pointing at electronic mail addresses 📧 [STANDARDS-TRACK]
2367 McDonald Jul 1998 PF_KEY Key Management API,
Version 2a generic key management API is presented here, and it's not just for IP Security. It can serve other network security services too 🔐 This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
2366 Chung Jul 1998 Definitions of Managed Objects
for Multicast over UNI 3.0/3.1
based ATM Networksthis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community 📊 It's specifically about managed objects for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based ATM Networks'. [STANDARDS-TRACK]
2365 Meyer Jul 1998 Administratively Scoped IP
Multicastthis document defines the "administratively scoped IPv4 multicast space" as the range 239.0.0.0 to 239.255.255.255 🌈 It also describes a simple set of semantics for implementing Administratively Scoped IP Multicast. Finally, it maps the IPv6 multicast address classes [RFC1884] onto IPv4 multicast address classes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
2364 Gross Jul 1998 PPP Over AAL5this document describes using ATM Adaptation Layer 5 (AAL5) for framing PPP encapsulated packets 🦋 [STANDARDS-TRACK]
2363 Gross Jul 1998 PPP Over FUNIthis document describes using ATM Frame User Network Interface (FUNI) for framing PPP encapsulated packets 🦋 [STANDARDS-TRACK]
2362 Estrin Jun 1998 Protocol Independent
Multicast-Sparse Mode (PIM-SM):
Protocol Specificationthis document describes a protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets 🌸 This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
2361 Fleischman Jun 1998 WAVE and AVI Codec Registriesthe purpose here is to set up a mechanism so that codecs registered within Microsoft's WAVE and AVI Registries can be referenced within the IANA Namespace by Internet applications 🎬 This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
2360 Scott Jun 1998 Guide for Internet Standards
Writersthis is a guide for Internet standard writers 📝 It defines the characteristics that make standards coherent, unambiguous, and easy to interpret. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
2359 Myers Jun 1998 IMAP4 UIDPLUS extensionthe UIDPLUS extension of the Internet Message Access Protocol [IMAP4] gives you a set of features meant to cut down the time and resources some client operations eat up ⏱️ [STANDARDS-TRACK]
2358 Flick Jun 1998 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 the Internet community 🔧 This memo obsoletes RFC 1650 "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2". It extends that specification by including management information useful for managing 100 Mb/s Ethernet interfaces. [STANDARDS-TRACK]
2357 Mankin Jun 1998 IETF Criteria for Evaluating
Reliable Multicast Transport
and Application Protocolsthis memo describes the procedures and criteria for reviewing reliable multicast protocols within the Transport Area (TSV) of the IETF 🧐 Within today's Internet, there are important applications that need a reliable multicast service. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
2356 Montenegro Jun 1998 Sun's SKIP Firewall Traversal
for Mobile IPthe Mobile IP specification establishes the mechanisms that let a mobile host keep using the same IP address as it changes its point of attachment to the network 🚀 The mechanisms in this document let a mobile node out on a public sector of the internet negotiate access past a SKIP firewall, and build a secure channel into its home network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
2355 Kelly Jun 1998 TN3270 Enhancementsthis document describes a protocol that supports 3270 devices more fully than traditional tn3270 practices do 🖥️ [STANDARDS-TRACK]
2354 Perkins Jun 1998 Options for Repair of
Streaming Mediathis document sums up a range of possible techniques for repairing continuous media streams that suffer packet loss 🛠️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
2353 Dudley May 1998 APPN/HPR in IP Networks
APPN Implementers' Workshop
Closed Pages Documentthis memo defines a method that lets HPR nodes use IP networks for communication, along with the enhancements to APPN that this method requires 🌐 It also describes an option set that uses the APPN connection network model, so HPR nodes can communicate over IP networks without having to predefine link connections. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
2352 Vaughan May 1998 A Convention For Using Legal
Names as Domain Namesthe purpose of this memo is to focus discussion on the specific problems with exhausting the top level domain space in the Internet, and the possible conflicts that happen when multiple organisations vie for the same name 🏷️ This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
2351 Robert May 1998 Mapping of Airline
Reservation, Ticketing,
and Messaging Traffic over IPthis memo specifies a protocol for encapsulating the airline-specific protocol over IP ✈️ This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
2250 Brownlee Jun 1998 Expectations for Computer
Security Incident Responsethe purpose of this document is to express the general Internet community's expectations of Computer Security Incident Response Teams (CSIRTs) 🛡️ It isn't possible to define a set of requirements that's appropriate for every team, but it is possible and helpful to list and describe the general set of topics and issues that matter to constituent communities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
2349 Malkin May 1998 TFTP Timeout Interval and
Transfer Size Optionsthe Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol that lets a client get or put a file onto a remote host 📁 This document describes two TFTP options. [STANDARDS-TRACK]
2348 Malkin May 1998 TFTP Blocksize Optionthe Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol that lets a client get or put a file onto a remote host 📁 This document describes a TFTP option that lets the client and server negotiate a blocksize more applicable to the network medium. [STANDARDS-TRACK]
2347 Malkin May 1998 TFTP Option Extensionthe Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol that lets a client get or put a file onto a remote host 📁 This document describes a simple extension to TFTP that allows option negotiation prior to the file transfer. [STANDARDS-TRACK]
2346 Palme May 1998 Making Postscript and PDF
Internationalcertain text formats, like Postscript (MIME-Type: application/postscript; file extension .ps) and Portable Document Format (MIME-Type: application/pdf; file extension .pdf), specify exactly the page layout of the printed document 🖨️ The commonly used paper format differs between North America and the rest of the world. North America uses the 'Letter' format, while the rest of the world mostly uses the ISO-standard 'A4' format. That means documents formatted on one continent may not be easily printable on another. This memo gives advice on producing documents that print equally well in the Letter and the A4 formats. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
2345 Klensin May 1998 Domain Names and Company Name
Retrievalthis document proposes a company name to URL mapping service based on the oldest and least complex of Internet directory protocols, whois 🔍 The goal is to explore whether an extremely simple and widely-deployed protocol can succeed where more complex and powerful options have failed or been excessively delayed. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
2344 Montenegro May 1998 Reverse Tunneling for Mobile IPthis document proposes backwards-compatible extensions to Mobile IP so it can support topologically correct reverse tunnels 🔄 [STANDARDS-TRACK]
2343 Civanlar May 1998 RTP Payload Format for Bundled
MPEGthis document describes a payload type for bundled, MPEG-2 encoded video and audio data that may be used with RTP, version 2 🎞️ This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions
Okay so the last bit of the previous part was literally "Discussion and suggestions for improvement are requested" 🫶 and we're picking up right there 💅
2342 Gahrns May 1998 IMAP4 NamespaceBestie, this one gives us a NAMESPACE command 🧚 so a client can figure out which prefixes a server uses for personal mailboxes, other users' mailboxes, and shared mailboxes. [STANDARDS-TRACK]
2341 Valencia May 1998 Cisco Layer Two Forwarding
(Protocol) "L2F"This one describes the Layer Two Forwarding protocol (L2F) 🦋 which lets you tunnel the link layer (HDLC, async HDLC, or SLIP frames) of higher level protocols. It's a historic protocol for the Internet community, so it doesn't specify an Internet standard of any kind 🕰️
2340 Jamoussi May 1998 Nortel's Virtual Network
Switching (VNS) OverviewQuick overview of Virtual Network Switching (VNS) 🌸 It's information for the Internet community and doesn't specify an Internet standard of any kind.
2339 ISOC May 1998 An Agreement Between the
Internet Society, the IETF,
and Sun Microsystems, Inc. in
the matter of NFS V.4 ProtocolsNgl this is a whole saga 📜 It records an agreement between Sun Microsystems and the Internet Society that lets Sun's Network File System specifications flow into the IETF's Internet Standards process. Informational only, not an Internet standard of any kind 💜
2338 Knight Apr 1998 Virtual Router Redundancy ProtocolVRRP is the star here ⭐ It's an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. [STANDARDS-TRACK]
2337 Farinacci Apr 1998 Intra-LIS IP multicast among
routers over ATM using Sparse
Mode PIMThis one is so clever 🧠 It shows how intra-LIS IP multicast can be efficiently supported among routers over ATM without using the Multicast Address Resolution Server (MARS). It's an Experimental Protocol for the Internet community and doesn't specify an Internet standard of any kind. Discussion and suggestions for improvement are requested 🍓
2336 Luciani Jul 1998 Classical IP and ARP over ATM
to NHRP TransitionOkay this one is all about moving gracefully from an ATMARP LIS to an NHRP LIS network model over ATM 🔥 Methods and procedures included. It's information for the Internet community, not an Internet standard of any kind.
2335 Luciani Apr 1998 A Distributed NHRP Service
Using SCSPHere we describe a way to distribute an NHRP service within a LIS 🌈 [STANDARDS-TRACK]
2334 Luciani Apr 1998 Server Cache Synchronization
Protocol (SCSP)SCSP is giving synchronization energy ✨ It's written in terms of its use within Non Broadcast Multiple Access (NBMA) networks, though a somewhat straight forward usage is applicable to BMA networks too. [STANDARDS-TRACK]
2333 Cansever Apr 1998 NHRP Protocol Applicability
StatementAs required by the Routing Protocol Criteria [RFC 1264], this one looks at where the Next Hop Resolution Protocol (NHRP) fits when routing IP datagrams over Non-Broadcast Multiple Access (NBMA) networks, like ATM, SMDS and X.25 🎀 [STANDARDS-TRACK]
2332 Luciani Apr 1998 NBMA Next Hop Resolution
Protocol (NHRP)NHRP is the main character here 👑 A source station (host or router) connected to a Non-Broadcast, Multi-Access (NBMA) subnetwork can use it to find the internetworking layer address and NBMA subnetwork addresses of the "NBMA next hop" toward a destination station. [STANDARDS-TRACK]
2331 Maher Apr 1998 ATM Signalling Support for IP
over ATM - UNI Signalling 4.0
UpdateThis memo explains how to efficiently use the ATM call control signalling procedures from UNI Signalling 4.0 to support IP over ATM environments, as described in RFC 2225 and in RFC 2332 💖 [STANDARDS-TRACK]
2330 Paxson May 1998 Framework for IP Performance
MetricsBestie, this is the framework 🦋 It defines a general framework for particular metrics to be developed by the IETF's IP Performance Metrics effort. It's information for the Internet community and doesn't specify an Internet standard of any kind.
2329 Moy Apr 1998 OSPF Standardization ReportThis one documents how the requirements for advancing a routing protocol to Full Standard have been met for OSPFv2 🏆 Information for the Internet community only. It doesn't specify an Internet standard of any kind.
2328 Moy Apr 1998 OSPF Version 2Version 2 of OSPF, documented here 🌟 OSPF is a link-state routing protocol. [STANDARDS-TRACK]
2327 Handley Apr 1998 SDP: Session Description ProtocolSDP is for describing multimedia sessions for session announcement, session invitation, and other forms of multimedia session initiation 🎶 [STANDARDS-TRACK]
2326 Schulzrinne Apr 1998 Real Time Streaming Protocol
(RTSP)RTSP is an application-level protocol for controlling the delivery of data with real-time properties 🎬 It gives you an extensible framework for controlled, on-demand delivery of real-time data, like audio and video. [STANDARDS-TRACK]
2325 Slavitch 1 Apr 1998 Definitions of Managed Objects
for Drip-Type Heated Beverage
Hardware Devices using SMIv2Okay the vibes are immaculate ☕🙈 This memo extends the Management Information Base (MIB) for network management protocols in the Internet community, with objects for managing coffee-brewing and maintenance devices. It's information for the Internet community and doesn't specify an Internet standard of any kind.
2324 Masinter 1 Apr 1998 Hyper Text Coffee Pot Control
Protocol (HTCPCP/1.0)HTCPCP describes a protocol for controlling, monitoring, and diagnosing coffee pots ☕💀 Information for the Internet community, not an Internet standard of any kind.
2323 Ramos 1 Apr 1998 IETF Identification and
Security GuidelinesThis RFC is a guideline so that IETF conferences can run more efficiently when it comes to identification and security protocols 🧔 It pays special attention to a particular sub-group within the IETF: "facial hairius extremis". Information for the Internet community, and it doesn't specify an Internet standard of any kind.
2322 van den Hout 1 Apr 1998 Management of IP numbers by
peg-dhcpThis RFC describes a protocol that dynamically hands out ip-numbers on field networks and small events that don't necessarily have a clear organisational body 🎪 Information for the Internet community, not an Internet standard of any kind.
2321 Bressen 1 Apr 1998 RITA -- The Reliable
Internetwork Troubleshooting
AgentRITA is so iconic 🫶 It describes how to use Nondeterministic Troubleshooting and Diagnostic Methodologies on today's complex nondeterministic networks and environments. Information for the Internet community, and no Internet standard of any kind is specified.
2320 Greene Apr 1998 Definitions of Managed Objects
for Classical IP and ARP Over
ATM Using SMIv2This memo defines the Management Information Base (MIB) for supporting Classical IP and ARP over ATM, as specified in Classical IP and ARP over ATM 📊 [STANDARDS-TRACK]
2319 KOI8-U WG Apr 1998 Ukrainian Character Set KOI8-UKOI8-U is a character encoding (KOI8 Ukrainian) that's a de-facto standard in the Ukrainian Internet community 🇺🇦🌻 Information for the Internet community, not an Internet standard of any kind.
2318 Lie Mar 1998 The text/css Media TypeInfo about the text/css Media Type, for the Internet community 🎨 It doesn't specify an Internet standard of any kind.
2317 Eidnes Mar 1998 Classless IN-ADDR.ARPA delegationThis one describes doing IN-ADDR.ARPA delegation on non-octet boundaries for address spaces covering fewer than 256 addresses 🧩 It specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
2316 Bellovin Apr 1998 Report of the IAB Security
Architecture WorkshopOn 3-5 March 1997, the IAB held a security architecture workshop at Bell Labs in Murray Hill, NJ 🏛️ They identified the core security components of the architecture and specified several documents that need to be written. The big takeaway is that security was not optional, and it needed to be designed in from the beginning 🔐 Information for the Internet community, not an Internet standard of any kind.
2315 Kaliski Mar 1998 PKCS #7: Cryptographic Message
Syntax Version 1.5This describes a general syntax for data that may have cryptography applied to it, like digital signatures and digital envelopes 🔏 Information for the Internet community, not an Internet standard of any kind.
2314 Kaliski Mar 1998 PKCS #10: Certification
Request Syntax Version 1.5A syntax for certification requests 📜 Information for the Internet community, not an Internet standard of any kind.
2313 Kaliski Mar 1998 PKCS #1: RSA Encryption
Version 1.5This one describes a method for encrypting data using the RSA public-key cryptosystem 🗝️ Information for the Internet community, not an Internet standard of any kind.
2312 Dusse Mar 1998 S/MIME Version 2 Certificate
HandlingThis memo describes the mechanisms S/MIME uses to create and validate keys using certificates 🎟️ Information for the Internet community, not an Internet standard of any kind.
2311 Dusse Mar 1998 S/MIME Version 2 Message
SpecificationAnd we're cutting off here for this part 🎀 The rest of this one picks up in the next part!
Okay bestie, this one's a whole ✨ lineup ✨. This document describes a protocol for adding cryptographic signature and encryption services to MIME data 🎀 This memo provides information for the Internet community, and it does not specify an Internet standard of any kind. Lowkey iconic that it's just here to inform, no pressure 💅
2310 · Holtman · Apr 1998 · The Safe Response Header Field 🦋
Okay so this one defines an HTTP response header field called Safe 💖 It can be used to say that repeating an HTTP request is safe, which is giving "you can retry this without worry" energy 🫶 This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind, but discussion and suggestions for improvement are requested, so speak up, bestie 📣
2309 · Braden · Apr 1998 · Recommendations on Queue Management and Congestion Avoidance in the Internet 🌊
This memo is serving two recommendations to the Internet community about measures to improve and preserve Internet performance 💅 First, it strongly recommends testing, standardization, and widespread deployment of active queue management in routers, so today's Internet can run better ✨ Second, it urges a concerted effort of research, measurement, and ultimate deployment of router mechanisms that protect the Internet from flows that are not sufficiently responsive to congestion notification. Iconic behaviour from the Internet's protectors 🛡️ This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
2308 · Andrews · Mar 1998 · Negative Caching of DNS Queries (DNS NCACHE) 🧚
Okay so RFC1034 described how to cache negative responses 🍓 The tea is that it had a fundamental flaw: it did not allow a name server to hand out those cached responses to other resolvers, which greatly reduced the effect of the caching 💀 This document addresses issues raised in light of experience and replaces RFC1034 Section 4.3.4. Glow-up era for DNS caching 💜 [STANDARDS-TRACK]
2307 · Howard · Mar 1998 · An Approach for Using LDAP as a Network Information Service 🌸
This document describes an experimental mechanism for mapping entities related to TCP/IP and the UNIX system into X.500 entries, so they can be resolved with the Lightweight Directory Access Protocol [RFC2251] 🧠 This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested, so drop your thoughts 💖
2306 · Parsons · Mar 1998 · Tag Image File Format (TIFF) - F Profile for Facsimile 📠
This document goes into detail about the definition of TIFF-F, which is used to store facsimile images 🖨️ This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Fax, but make it aesthetic 🎀
2305 · Toyoda · Mar 1998 · A Simple Mode of Facsimile Using Internet Mail 💌
This specification provides for "simple mode" carriage of facsimile data over the Internet, which is so simple it's giving main character energy 🦋 [STANDARDS-TRACK]
2304 · Allocchio · Mar 1998 · Minimal FAX address format in Internet Mail 📬
This memo describes the MINIMAL addressing method and standard extensions for encoding FAX addresses in e-mail addresses 💜 It's minimal, but it's not basic 💅 [STANDARDS-TRACK]
2303 · Allocchio · Mar 1998 · Minimal PSTN address format in Internet Mail ☎️
This memo describes the MINIMAL addressing method for encoding PSTN addresses into e-mail addresses, plus the standard extension mechanism that lets people define further standard elements 🌈 Extensible and minimal, so iconic 👑 [STANDARDS-TRACK]
2302 · Parsons · Mar 1998 · Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration 🗂️
This document describes the registration of the MIME sub-type image/tiff. Officially registered, so it's real 💅 [STANDARDS-TRACK]
2301 · McIntyre · Mar 1998 · File Format for Internet Fax 📄
This document describes the TIFF (Tag Image File Format) representation of image data specified by the ITU-T Recommendations for black-and-white and color facsimile 🖤🤍 It's the format for fax, fr fr ✨ [STANDARDS-TRACK]
2300 · IAB · May 1998 · INTERNET OFFICIAL PROTOCOL STANDARDS 👑
Okay so this one starts with a discussion of the standardization process and the RFC document series, then explains the terms 📚 Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization, which is the ultimate tea 🍵 Finally, there are pointers to references and contacts for further information 🫶 [STANDARDS-TRACK]
Security Considerations 💀
There are no security issues in this Informational RFC. Literally the most relaxing security section ever 🫶🌸
Author's Address 🖋️
Alegre Ramos
University of Southern California
Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: ramos@isi.eduFull Copyright Statement ⭐
Copyright (C) The Internet Society (1999). All Rights Reserved. Legally protected and iconic 💅
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards, in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. 🌍
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. Forever and ever, periodt 💜
This document and the information contained herein is provided on an "AS IS" basis, and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 🫶
📦 where this page comes from
- ietf: rfc2399 1999-01
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms