RFC 3199
Request for Comments Summary RFC Numbers 3100-3199
Title Block ✨
okay bestie, this is RFC 3199, and it's giving "summary of the last 100 RFCs" 📚. It's titled Request for Comments Summary and covers RFC Numbers 3100-3199. S. Ginoza wrote it at ISI, it's in the Informational category, and the date is February 2003. The header doesn't list anything it obsoletes or updates 🫶
Status of This Memo ✨
This RFC is a slightly annotated list of the 100 RFCs from RFC 3100 through RFCs 3199. It's a status report on those RFCs, and it's for the Internet community. It does not specify an Internet standard of any kind, so chill 🌸 Distribution of this memo is unlimited 🦋
Copyright Notice 🎀
Copyright (C) The Internet Society (2003). All Rights Reserved. Very official, very iconic 💅
Note 💜
Okay so, lots of RFCs are Proposed Standards, Draft Standards, or Standards, but not all of them. The status can change during standards processing, so this doc only says whether they're on the standards track. If you want the current state and status, go check the latest edition of "Internet Official Protocol Standards" 📖 In the list below, standards-track RFCs are marked [STANDARDS-TRACK] (the entries themselves sometimes write it as [STANDARDS TRACK], which is the same vibe 🙈)
RFC Listing 🌸
Here's the header for the list, exactly as it appears:
RFC Author Date Title
--- ------ ---- -----3199
3199 Ginoza Feb 2003 Request for Comments SummaryThis memo. Yep, it's literally this one, the summary itself 💖
3198
3198 Westerinen Nov 2001 Terminology for Policy-Based
ManagementThis one is a glossary of policy-related terms 📝 It gives abbreviations, explanations, and recommendations for using these terms. The goal is to make writing about network policy clearer and more consistent, especially in Internet Standards documents (ISDs). It provides information for the Internet community ✨
3197
3197 Austein Nov 2001 Applicability Statement for
DNS MIB ExtensionsNgl this one is a little sad 🥺 After more than six years as proposed standards, the DNS Server and Resolver MIB extensions were never deployed. So it explains why, and recommends moving them to Historical status. It provides information for the Internet community 🍓
3196
3196 Hastings Nov 2001 Internet Printing
Protocol/1.1: Implementor's
GuideThis is one of a set of documents that together describe all aspects of a new Internet Printing Protocol (IPP) 🖨️💅 It provides information for the Internet community.
3195
3195 New Nov 2001 Reliable Delivery for syslogThe BSD Syslog Protocol has a bunch of service options for propagating event messages. This memo describes two ways to map syslog onto TCP connections, and both are useful for reliable delivery of event messages 🔥 [STANDARDS TRACK]
3194
3194 Durand Nov 2001 The Host-Density Ratio for
Address Assignment Efficiency:
An update on the H ratioThis is an update on the "H ratio" defined in RFC 1715 🧚 It defines a new ratio that the authors claim is easier to understand, which is honestly giving main character energy. It provides information for the Internet community.
3193
3193 Patel Nov 2001 Securing L2TP using IPsecThis one discusses how L2TP (Layer Two Tunneling Protocol) can use IPsec to provide tunnel authentication, privacy protection, integrity checking, and replay protection 🔐 It covers both voluntary and compulsory tunneling cases. [STANDARDS TRACK]
3192
3192 Allocchio Oct 2001 Minimal FAX address format in
Internet MailThis memo describes a simple way to encode Global Switched Telephone Network (GSTN) addresses of fax machines in the local-part of Internet email addresses 📠 [STANDARDS TRACK]
3191
3191 Allocchio Oct 2001 Minimal GSTN address format in
Internet MailSame energy as 3192, but for regular GSTN addresses (aka "telephone numbers") 📞 It puts them in the local-part of Internet email addresses. It also adds an extension mechanism so email gateways can include extra standard attributes they need for GSTN-based services. [STANDARDS TRACK]
3190
3190 Kobayashi Jan 2002 RTP Payload Format for 12-bit
DAT Audio and 20- and 24-bit
Linear Sampled AudioThis document sets out a packetization scheme for putting 12-bit nonlinear, 20-bit linear, and 24-bit linear audio streams into RTP 🎧 It also defines a Session Description Protocol (SDP) parameter that says whether audio was preemphasized before sampling. That parameter can be used with other audio payload formats too, especially L16 (16-bit linear) 🫶 [STANDARDS TRACK]
3189
3189 Kobayashi Jan 2002 RTP Payload Format for DV
(IEC 61834) VideoThis one is the packetization scheme for the compressed digital video streams people call "DV", packed into an RTP payload format 🎥 [STANDARDS TRACK]
3188
3188 Hakala Oct 2001 Using National Bibliography
Numbers as Uniform Resource
NamesThis document talks about how national bibliography numbers (persistent, unique IDs given out by national libraries) can work inside the URN (Uniform Resource Names) framework 📚 It also covers the URN syntax from RFC 2141. A lot of the discussion is built on the ideas in RFC 2288. It provides information for the Internet community 🦋
3187
3187 Hakala Oct 2001 Using International Standard
Book Numbers as Uniform
Resource NamesSister doc to 3188 📖 It covers how International Standard Book Numbers (ISBN) can be supported within the URN framework and the URN syntax from RFC 2141. Again, much of the discussion builds on the ideas in RFC 2288. It provides information for the Internet community 💜
3186
3186 Shimizu Dec 2001 MAPOS/PPP Tunneling modeThis document specifies tunneling configuration over MAPOS (Multiple Access Protocol over SONET/SDH) networks 🌈 In this mode, a MAPOS network can give you a transparent point-to-point link for PPP over SONET/SDH (Packet over SONET/SDH, POS) with no extra overhead. It provides information for the Internet community ✨
3185
3185 Farrell Oct 2001 Reuse of CMS Content
Encryption KeysThis one describes how to include a key identifier in a CMS (Cryptographic Message Syntax) enveloped data structure 🔑 That way the content encryption key can be reused for more enveloped data packets. [STANDARDS TRACK]
3184
3184 Harris Oct 2001 IETF Guidelines for ConductThis is a set of guidelines for personal interaction in the Internet Engineering Task Force 🫶 It's an Internet Best Current Practices document for the Internet Community, and it asks for discussion and suggestions for improvements. Be nice, bestie 🌸
3183
3183 Dean Oct 2001 Domain Security Services using
S/MIMEThis document describes how the S/MIME (Secure/Multipurpose Internet Mail Extensions) protocol can be processed and generated by components like message transfer agents, guards, and gateways to deliver security services 🛡️ Those services are collectively called 'Domain Security Services'. This memo defines an Experimental Protocol for the Internet community 🧪
3182
3182 Yadav Oct 2001 Identity Representation for
RSVPThis one is about representing identity info in the POLICY_DATA object, which supports policy-based admission control in the Resource ReSerVation Protocol (RSVP) 🪪 The big goal is to let a process on a system securely identify the owner and the application of the communicating process (for example, a user id), and carry that info in RSVP messages (PATH or RESV) in a secure way. The doc describes how identities get encoded as RSVP policy elements, and it covers the processing rules for generating identity policy elements for multicast merged flows 💅 [STANDARDS TRACK]
3181
3181 Herzog Oct 2001 Signaled Preemption Priority
Policy ElementThis document describes a preemption priority policy element for signaled policy-based admission protocols, like the Resource ReSerVation Protocol (RSVP) and Common Open Policy Service (COPS) ⚡ [STANDARDS TRACK]
3180
3180 Meyer Sep 2001 GLOP Addressing in 233/8This document defines the policy for using 233/8 for statically assigned multicast addresses 🌐 It's an Internet Best Current Practices document for the Internet Community, and it asks for discussion and suggestions for improvements.
3179
3179 Schoenwaelder Oct 2001 Script MIB Extensibility
Protocol Version 1.1The Script MIB extensibility protocol (SMX) in this memo separates language-specific runtime systems from language-independent Script MIB implementations 🧚 The IETF Script MIB defines an interface for delegating management functions, based on the Internet management framework. This memo defines an Experimental Protocol for the Internet community 🧪
3178
3178 Hagino Oct 2001 IPv6 Multihoming Support at
Site Exit RoutersThis one describes a mechanism for basic IPv6 multihoming support, plus its operational requirements 🌸 It provides information for the Internet community.
3177
3177 IAB Sep 2001 IAB/IESG Recommendations on
IPv6 Address Allocations to
SitesThis document gives recommendations to the addressing registries (APNIC, ARIN, and RIPE-NCC) on policies for assigning IPv6 address blocks to end sites 🌍 It recommends a /48 in the general case, a /64 when it's known that one and only one subnet is needed, and a /128 when it's absolutely known that one and only one device is connecting. Iconic 👑
3176
3176 Phaal Sep 2001 InMon Corporation's sFlow: A
Method for Monitoring Traffic
in Switched and Routed NetworksThis memo defines InMon Corporation's sFlow system, which is a technology for monitoring traffic in data networks with switches and routers 📊 It defines the sampling mechanisms in an sFlow Agent, the sFlow MIB for controlling that agent, and the format of the sample data the agent sends to a central data collector when it forwards data. It provides information for the Internet community ✨
3175
3175 Baker Sep 2001 Aggregation of RSVP for IPv4
and IPv6 ReservationsOkay so this one is about using a single RSVP (Resource ReSerVation Protocol) reservation to aggregate other RSVP reservations across a transit routing region 🦋 It's kind of like Virtual Paths in an ATM (Asynchronous Transfer Mode) network. It proposes a way to dynamically create the aggregate reservation and classify
RFC 3174 ✨
3174 Eastlake Sep 2001 US Secure Hash Algorithm 1
(SHA1)okay so this one is all about making the SHA-1 (Secure Hash Algorithm 1) hash algorithm easy for the whole Internet community to grab 🔐 this memo provides information for the Internet community 💖
RFC 3173 🎀
3173 Shacham Sep 2001 IP Payload Compression
Protocol (IPComp)bestie, this one is giving lossless compression for Internet Protocol datagrams 🗜️ the whole point is shrinking IP packets in an Internet environment without losing a single bit ✨ it's a [STANDARDS TRACK] doc, so it's serious business 👑
RFC 3172 🌸
3172 Huston Sep 2001 Management Guidelines &
Operational Requirements for
the Address and Routing
Parameter Area Domain ("arpa")this one lays out the management and operational requirements for the address and routing parameter area ("arpa") domain 🏠 it's a BCP (Best Current Practice) for the Internet Community, and it's basically inviting everyone to drop their discussion and suggestions for improvements 🗣️💅
RFC 3171 🦋
3171 Albanna Aug 2001 IANA Guidelines for IPv4
Multicast Address Assignmentsthis memo gives guidance to the Internet Assigned Numbers Authority (IANA) on how to assign IPv4 multicast addresses 📮 it's also a BCP (Best Current Practice) for the Internet Community, with an open invitation for discussion and suggestions for improvements 🌈
RFC 3170 💜
3170 Quinn Sep 2001 IP Multicast Applications:
Challenges and Solutionsngl this one is so helpful 🧚 it describes the challenges of designing and implementing multicast applications, and it's an introductory guide for application developers 📚 it highlights how multicast apps are different from unicast apps, which is a whole vibe 🙈 this memo provides information for the Internet community ✨
RFC 3169 🍓
3169 Beadles Sep 2001 Criteria for Evaluating
Network Access Server
Protocolsthis doc defines the requirements for protocols used by Network Access Servers (NAS) 🖥️ this memo provides information for the Internet community 🫶
RFC 3168 👑
3168 Ramakrishnan Sep 2001 The Addition of Explicit
Congestion Notification (ECN)
to IPmain character energy alert 🚨 this memo specifies adding ECN (Explicit Congestion Notification) to TCP and IP, including how ECN uses two bits in the IP header 🔥 it's a [STANDARDS TRACK] doc, so it's iconic ✨
RFC 3167 🌷
3167 Meyer Aug 2001 Request to Move RFC 1745 to
Historic Statusso RFC 1745, "BGP4/IDRP for IP---OSPF Interaction", describes technology that was never deployed in the public internet 🥲 this document requests that RFC 1745 be moved to Historic status 📜 this memo provides information for the Internet community 💅
RFC 3166 🍒
3166 Meyer Aug 2001 Request to Move RFC 1403 to
Historic Statussame energy, different RFC 💀 RFC 1403, "BGP OSPF Interaction", describes technology that is no longer used, so this document requests that it be moved to Historic status 🕰️ this memo provides information for the Internet community 🦋
RFC 3165 🎀
3165 Levi Aug 2001 Definitions of Managed Objects
for the Delegation of
Management Scriptsthis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community 🗂️ specifically, it describes a set of managed objects that let you delegate management scripts to distributed managers 🧩 it's a [STANDARDS TRACK] doc, lowkey iconic ✨
RFC 3164 🌈
3164 Lonvick Aug 2001 The BSD syslog Protocolthis document describes the observed behavior of the syslog protocol 👀 it's not a rulebook, it's what people actually see in the wild 🌿 this memo provides information for the Internet community 🫶
RFC 3163 🧚
3163 Zuccherato Aug 2001 ISO/IEC 9798-3 Authentication
SASL Mechanismthis doc defines a SASL (Simple Authentication and Security Layer) authentication mechanism based on ISO/IEC 9798-3 and FIPS PUB 196 entity authentication 🔑 this memo defines an Experimental Protocol for the Internet community 🧪 bestie, it's experimental, so it's still cooking 🍳
RFC 3162 💖
3162 Aboba Aug 2001 RADIUS and IPv6this document specifies how RADIUS (Remote Authentication Dial In User Service) works when it runs over IPv6 🌐 it also covers the RADIUS attributes used to support IPv6 network access 📶 [STANDARDS TRACK] means it's the real deal 💅
RFC 3161 🦢
3161 Adams Aug 2001 Internet X.509 Public Key
Infrastructure Time-Stamp
Protocol (TSP)this one describes the format of a request sent to a Time Stamping Authority (TSA) and of the response that comes back ⏰ it also sets out several security-relevant requirements for TSA operation, specifically around processing requests to generate responses 🔐 security is not playing around here 💀 [STANDARDS TRACK] ✨
RFC 3160 🌸
3160 Harris Aug 2001 The Tao of IETF - A Novice's
Guide to the Internet
Engineering Task Forcethis document is the ultimate beginner's guide 🧭 it describes the inner workings of IETF meetings and Working Groups, talks about organizations related to the IETF, and introduces the standards process 🎓 this memo provides information for the Internet community 🫶
RFC 3159 🍓
3159 McCloghrie Aug 2001 Structure of Policy
Provisioning Information
(SPPI)okay so the Structure of Policy Provisioning Information (SPPI) is an adapted subset of SNMP's Structure of Management Information (SMI) 🧱 it's used to write Policy Information Base (PIB) modules 📘 [STANDARDS TRACK] 🔥
RFC 3158 🦋
3158 Perkins Aug 2001 RTP Testing Strategiesthis memo describes a possible testing strategy for RTP (real-time transport protocol) implementations 🎥 it's a helpful idea to have, not a rule 🌷 this memo provides information for the Internet community ✨
RFC 3157 🌙
3157 Arsenault Aug 2001 Securely Available Credentials
- Requirementsthis document describes the requirements that Securely Available Credentials (SACRED) protocols need to meet 🗝️ this memo provides information for the Internet community 🫶
RFC 3156 💜
3156 Elkins Aug 2001 MIME Security with OpenPGPthis doc shows how the OpenPGP Message Format can be used to provide privacy and authentication through the Multipurpose Internet Mail Extensions (MIME) security content types described in RFC 1847 ✉️🔒 [STANDARDS TRACK] means it's legit 💅
RFC 3155 🌊
3155 Dawkins Aug 2001 End-to-end Performance
Implications of Links with
Errorsthis one talks about the specific TCP mechanisms that are problematic in environments with high uncorrected error rates 📉 it also discusses what can be done to mitigate those problems without introducing intermediate devices into the connection 🙌 it's a BCP (Best Current Practice) for the Internet Community, and it's inviting discussion and suggestions for improvements 🗣️💖
RFC 3154 🐚
3154 Kempf Aug 2001 Requirements and Functional
Architecture for an IP Host
Alerting Protocolthis document develops an architecture and a set of requirements for alerting hosts that are in dormant mode 🔔 the goal is to guide an IP protocol for alerting dormant IP mobile hosts, which is commonly called paging 📟 this memo provides information for the Internet community ✨
RFC 3153 🍭
3153 Pazhyannur Aug 2001 PPP Multiplexingthis one describes a method to reduce the PPP (Point-to-Point Protocol) framing overhead that's used to transport small packets over slow links 🐢 less wasted bytes, more vibes 💅 [STANDARDS TRACK] ✨
RFC 3152 🌸
3152 Bush Aug 2001 Delegation of IP6.ARPAthis document discusses why the IP6.ARPA DNS zone needs to be delegated, and it lays out a plan for how that technical operation should work 🧾 it's a BCP (Best Current Practice) for the Internet Community, and it's open for discussion and suggestions for improvements 🫶
RFC 3151 🎀
3151 Walsh Aug 2001 A URN Namespace for Public
Identifiersthis document describes a URN (Uniform Resource Name) namespace designed so that Public Identifiers can be written in URI (Uniform Resource Identifiers) syntax 🔗 this memo provides information for the Internet community 🦋
RFC 3150 🌧️
3150 Dawkins Jul 2001 End-to-end Performance
Implications of Slow Linksthis document makes performance-related recommendations for users of network paths that traverse "very low bit-rate" links 🐌 it's a BCP (Best Current Practice) for the Internet Community, and it's also asking for discussion and suggestions for improvements 💜
RFC 3149 📞
3149 Srinath Sep 2001 MGCP Business Phone Packagesthis doc describes a collection of MGCP (Media Gateway Control Protocol) packages that can take advantage of the feature keys and displays on digital business phones and IP-Phones 📱 this memo provides information for the Internet community 🫶
RFC 3148 📊
3148 Mathis Jul 2001 A Framework for Defining
Empirical Bulk Transfer
Capacity Metricsthis one defines a framework for standardizing multiple BTC (Bulk Transport Capacity) metrics that parallel the permitted transport diversity 📈 it's giving data nerd energy, and I'm here for it 🤓 this memo provides information for the Internet community ✨
RFC 3147 🌍
3147 Christian Jul 2001 Generic Routing Encapsulation
over CLNS Networksthis doc proposes a method for transporting an arbitrary protocol over a CLNS (Connectionless Network Service) network using GRE (Generic Routing Encapsulation) 📦 it says this can then be used to tunnel IPv4 or IPv6 over CLNS 🚇 this memo provides information for the Internet community 🦋
RFC 3146 🌈
3146 Fujisawa Oct 2001 Transmission of IPv6 Packets
over IEEE 1394 Networksthis document describes the frame format for sending IPv6 packets, plus how to form IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE1394 networks 🔥 [STANDARDS TRACK] means it's the real thing 👑
RFC 3145 ⚡
3145 Verma Jul 2001 L2TP Disconnect Cause
Informationthis document is an extension to the Layer 2 Tunneling Protocol ("L2TP"), which is a mechanism for tunneling Point-to-Point Protocol (PPP) sessions 🚇 [STANDARDS TRACK] ✨
RFC 3144 🧭
3144 Romascanu Aug 2001 Remote Monitoring MIB
Extensions for Interface
Parameters Monitoringthis memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community 🗂️ it proposes an extension to the Remote Monitoring MIB with a method of sorting the interfaces of a monitored device according to values of parameters specific to each interface 📊 [STANDARDS TRACK] 💖
RFC 3143 🍄
3143 Cooper Jun 2001 Known HTTP Proxy/Caching
ProblemsThis doc is basically a catalogue of all the drama around World Wide Web (caching) proxies and cache servers 💅 The whole point is to talk through the problems and the workarounds, and to make things better by showing exactly where they break 🔍 This memo provides information for the Internet community 🧚
RFC 3142 · Hagino · Jun 2001 · An IPv6-to-IPv4 Transport Relay Translator 🦋 Okay so this one describes an IPv6-to-IPv4 transport relay translator (TRT), which is basically a bridge between the two worlds ✨ It provides information for the Internet community.
RFC 3141 · Hiller · Jun 2001 · CDMA2000 Wireless Data Requirements for AAA 📡 This memo spells out the cdma2000 wireless data AAA (Authentication, Authorization, Accounting) requirements for third generation wireless architecture. That setup supports roaming between service providers for traditional PPP and Mobile IP services 🌸 It provides information for the Internet community.
RFC 3140 · Black · Jun 2001 · Per Hop Behavior Identification Codes 💜 This one defines a 16 bit encoding mechanism for identifying differentiated services Per Hop Behaviors in protocol messages 🎀 It replaces RFC 2836. [STANDARDS TRACK]
RFC 3139 · Sanchez · Jun 2001 · Requirements for Configuration Management of IP-based Networks 🛠️ Here we talk through different ways to configure networks and pin down a set of configuration management requirements for IP-based networks 💅 It provides information for the Internet community.
RFC 3138 · Meyer · Jun 2001 · Extended Assignments in 233/8 🍓 This memo describes how the GLOP addresses map onto the private AS space. It provides information for the Internet community.
RFC 3137 · Retana · Jun 2001 · OSPF Stub Router Advertisement 🌈 This one describes a backward-compatible technique that OSPF (Open Shortest Path First) implementations can use to advertise that they're unavailable to forward transit traffic, or to lower the preference level for paths through that router 😭 It provides information for the Internet community.
RFC 3136 · Slutsman · Jun 2001 · The SPIRITS Architecture 📞 This doc lays out the architecture for supporting SPIRITS services, which originate in the PSTN (Public Switched Telephone Network) and need the PSTN and the Internet to talk to each other 🫶 It provides information for the Internet community.
RFC 3135 · Border · Jun 2001 · Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations 🚀 This is a survey of Performance Enhancing Proxies (PEPs) that people often use to fix degraded TCP performance caused by specific link environments, like satellite, wireless WAN, and wireless LAN 🛰️ It provides information for the Internet community.
RFC 3134 · Dunn · Jun 2001 · Terminology for ATM ABR Benchmarking 📊 This memo discusses and defines the terms for performance benchmarking tests, and for their results, in the context of ATM (Asynchronous Transfer Mode) switching devices that support ABR (Available Bit Rate) 💖 It provides information for the Internet community.
RFC 3133 · Dunn · Jun 2001 · Terminology for Frame Relay Benchmarking 📈 Same energy as the last one, but for frame relay switching devices ✨ It provides information for the Internet community.
RFC 3132 · Kempf · Jun 2001 · Dormant Mode Host Alerting ("IP Paging") Problem Statement 🔔 This memo describes paging, assesses whether IP paging is actually needed, and lists recommendations for Seamoby charter items on paging work 👑 It provides information for the Internet community.
RFC 3131 · Bradner · Jun 2001 · 3GPP2-IETF Standardization Collaboration 🤝 This doc describes the standardization collaboration between 3GPP2 and the IETF 🌟 It provides information for the Internet community.
RFC 3130 · Lewis · Jun 2001 · Notes from the State-Of-The-Technology: DNSSEC 🔐 This is a memo from a DNSSEC (Domain Name System Security Extensions) status meeting 📝 It provides information for the Internet community.
RFC 3129 · Thomas · Jun 2001 · Requirements for Kerberized Internet Negotiation of Keys 🗝️ The goal here is a streamlined, fast, easily managed, cryptographically sound protocol that doesn't need public keys 💜 It provides information for the Internet community.
RFC 3128 · Miller · Jun 2001 · Protection Against a Variant of the Tiny Fragment Attack 🛡️ This one is a warning shot. It explains how RFC 1858 compliant filters can be vulnerable to a variant of the "Tiny Fragment Attack" described in section 3.1 of the RFC. It describes the attack and recommends corrective action 😱 It provides information for the Internet community.
RFC 3127 · Mitton · Jun 2001 · Authentication, Authorization, and Accounting: Protocol Evaluation 🧾 This memo covers the process and findings of the Authentication, Authorization, and Accounting Working Group (AAA WG) panel, which evaluated protocols proposed against the AAA Network Access Requirements, RFC 2989 🍵 It provides information for the Internet community.
RFC 3126 · Pinkas · Sep 2001 · Electronic Signature Formats for long term electronic signatures ✍️ This document defines the format of an electronic signature that can stay valid over long periods. That includes evidence of its validity even if the signer or verifying party later tries to deny (that is, repudiate) the validity of the signature 💅 It provides information for the Internet community.
RFC 3125 · Ross · Sep 2001 · Electronic Signature Policies 📜 This one defines signature policies for electronic signatures. A signature policy is a set of rules for creating and validating an electronic signature, and it's what lets you decide whether a signature is valid. A given legal or contractual context may recognize a particular signature policy as meeting its requirements 💖 This memo defines an Experimental Protocol for the Internet community. 🧪
RFC 3124 · Balakrishnan · Jun 2001 · The Congestion Manager 🚦 This doc describes the Congestion Manager (CM), an end-system module that lets an ensemble of multiple concurrent streams from one sender to the same receiver (sharing the same congestion properties) do proper congestion avoidance and control. It also lets applications easily adapt to network congestion 🌊 [STANDARDS TRACK]
RFC 3123 · Koch · Jun 2001 · A DNS RR Type for Lists of Address Prefixes (APL RR) 📋 Quick context: the Domain Name System (DNS) mostly uses A RRs (Resource Records) to translate domain names into IPv4 addresses, and there are a few ways to describe networks or address ranges. This document specifies a new DNS RR type, "APL", for address prefix lists 🗂️ This memo defines an Experimental Protocol for the Internet community. 🧪
RFC 3122 · Conta · Jun 2001 · Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification 🔍 This memo describes extensions to IPv6 Neighbor Discovery that let a node figure out and advertise the IPv6 address that goes with a given link-layer address 🪞 [STANDARDS TRACK]
RFC 3121 · Best · Jun 2001 · A URN Namespace for OASIS 🏷️ This document describes a URN (Uniform Resource Name) namespace engineered by the Organization for the Advancement of Structured Information Standards (OASIS). It's for naming persistent resources OASIS publishes, like OASIS Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents 📚 It provides information for the Internet community.
RFC 3120 · Best · Jun 2001 · A URN Namespace for XML.org 🗄️ Same vibe as the last one, but this namespace is for naming persistent resources stored in the XML.org repository, like XML Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents 🎀 It provides information for the Internet community.
RFC 3119 · Finlayson · Jun 2001 · A More Loss-Tolerant RTP Payload Format for MP3 Audio 🎵 This doc describes an RTP (Real-Time Protocol) payload format for carrying MPEG (Moving Picture Experts Group) 1 or 2, layer III audio, which people know as "MP3" 🎧 It's an alternative to the one in RFC 2250, and it does better when packets get lost 🙌 [STANDARDS TRACK]
RFC 3118 · Droms · Jun 2001 · Authentication for DHCP Messages 🎟️ This document defines a new Dynamic Host Configuration Protocol (DHCP) option. Through it, authorization tickets can be easily generated, and newly attached hosts with proper authorization can be configured automatically by an authenticated DHCP server 🔑 [STANDARDS TRACK]
RFC 3117 · Rose · Nov 2001 · On the Design of Application Protocols 🧩 This memo describes the design principles for the Blocks eXtensible eXchange Protocol (BXXP) 🫧 It provides information for the Internet community.
RFC 3116 · Dunn · Jun 2001 · Methodology for ATM Benchmarking 🧮 This document discusses and defines a number of tests that can describe the performance characteristics of ATM (Asynchronous Transfer Mode) switching devices. On top of the tests, it also describes specific formats for reporting the results 📏 It provides information for the Internet community.
RFC 3115 · Dommety · Apr 2001 · Mobile IP Vendor/Organization-Specific Extensions 🧩 This document defines two new extensions to Mobile IP. They help equipment vendors and organizations use these extensions however they like, for research or deployment 🌷 [STANDARDS TRACK]
RFC 3114 · Nicolls · May 2002 · Implementing Company Classification Policy with the S/MIME Security Label 🏢 This doc shows how a company's security policy for data classification can be mapped onto the S/MIME security label. It includes worked examples from three real companies 🧠 It provides information for the Internet community.
RFC 3113 · Rosenbrock · Jun 2001 · 3GPP-IETF Standardization Collaboration 🤝 This document describes the standardization collaboration between 3GPP
and IETF. This memo provides information for the Internet community. 🌸
3112 · Zeilenga · May 2001 · LDAP Authentication Password Schema 🔐
Okay so this one is giving user/password auth realness ✨ It describes a schema for user and password authentication inside an LDAP (Lightweight Directory Access Protocol) directory, including the authPassword attribute type. It's info for the Internet community, so no cap, it's a good read 🫶
3111 · Guttman · May 2001 · Service Location Protocol Modifications for IPv6 🦋
This one defines how Service Location Protocol Version 2 (SLPv2) gets used over IPv6 networks. Lowkey the changes are minor because SLP runs on UDP and TCP, so it already has what it needs 💅 [STANDARDS TRACK]
3110 · Eastlake 3rd · May 2001 · RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS) 🎀
Bestie, this is so specific and I'm obsessed 😭 It explains how to make RSA/SHA1 SIG resource records (RRs) in Section 3, and, so as to completely replace RFC 2537, how to make RSA KEY RRs in Section 2. [STANDARDS TRACK]
3109 · Braden · May 2001 · Request to Move STD 39 to Historic Status 🍓
This memo changes the status of STD 39, BBN Report 1822, "Specification of the Interconnection of a Host and an IMP", from Standard to Historic. Retiring an old legend, iconic 👑 It's info for the Internet community.
3108 · Kumar · May 2001 · Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections 🌈
This one gives conventions for using the Session Description Protocol (SDP) from RFC 2327 to control ATM Bearer Connections and any associated ATM Adaptation Layer (AAL). The AALs covered are Type 1, Type 2 and Type 5. Main character energy 🧚 [STANDARDS TRACK]
3107 · Rekhter · May 2001 · Carrying Label Information in BGP-4 🦋
Okay, the way this one works is so clean 😍 It specifies how the label mapping info for a route gets piggybacked in the same Border Gateway Protocol (BGP) Update message that carries the route itself. One message, two jobs, slay ✨ [STANDARDS TRACK]
3106 · Eastlake · Apr 2001 · ECML v1.1: Field Specifications for E-Commerce 🛒
Customers keep having to type a ton of info into merchant sites just to buy something, especially the first time, and it's exhausting 😩 So this defines a standard set of fields as version 1 of the Electronic Commerce Modeling Language (ECML), so it's easier to automate. Wallet software could fill them in, for example. Even for manual entry, people won't get confused by every site looking different if a lot of merchants adopt the same fields. Some fields are also defined for merchant-to-consumer communication. Info for the Internet community 💖
3105 · Kempf · Oct 2001 · Finding an RSIP Server with SLP 🔍
This one has an SLP service type template that describes the advertisements RSIP servers make for their services. It defines an Experimental Protocol for the Internet community 🧪
3104 · Montenegro · Oct 2001 · RSIP Support for End-to-end IPsec 🔒
This document proposes mechanisms that let Realm Specific IP (RSIP) handle end-to-end IPsec (IP Security). Experimental Protocol for the Internet community ✨
3103 · Borella · Oct 2001 · Realm Specific IP: Protocol Specification 🧩
This is the protocol itself, bestie 💅 It lets an RSIP host and gateway negotiate resources, so the host can lease some of the gateway's addressing parameters to get a global network presence. It's designed to run at the application layer and use its own TCP or UDP port. The big deal is that the gateway can hand out addressing and control parameters so a flow policy gets enforced at the gateway. Experimental Protocol for the Internet community 🎀
3102 · Borella · Oct 2001 · Realm Specific IP: Framework 🌸
This one looks at the general framework of Realm Specific IP (RSIP). RSIP is meant to be an alternative to NAT where the end-to-end integrity of packets stays intact. It focuses on implementation issues, deployment scenarios, and how it interacts with other layer-three protocols. Experimental Protocol for the Internet community 🦋
3101 · Murphy · Jan 2003 · The OSPF Not-So-Stubby Area (NSSA) Option 🌲
This memo documents an optional kind of Open Shortest Path First (OSPF) area that's jokingly called a "not-so-stubby" area (or NSSA) 😭 NSSAs are like the existing OSPF stub area option, but they can also import AS external routes in a limited way.
The OSPF NSSA Option was first defined in RFC 1587. The functional differences between this memo and RFC 1587 are explained in Appendix F. All the differences expand capability and are backward-compatible, so implementations of this memo and RFC 1587 will interoperate 🫶 [STANDARDS TRACK]
3100 · Never Issued 🙈
RFC 3100 was never issued. Ghosted by the RFC index, lol 💀
Security Considerations 🔐
Security issues are not discussed in this memo. Zero threats in this one, but still treat it with respect 🫡
Author's Address 📮
Sandy Ginoza
University of Southern California
Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: ginoza@isi.eduFull Copyright Statement ⚖️
Legal bits are not the place to get creative, so here's the notice exactly as written 🫶
Copyright (C) The Internet Society (2003). All Rights Reserved.
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.
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.Acknowledgement 💖
Funding for the RFC Editor function is currently provided by the Internet Society. Thank you, Internet Society, you're the real MVP 👑
Heads up, bestie: the text you pasted is actually the RFC index listing for RFCs 3100 to 3112 plus the closing boilerplate, not the body of RFC 3199. I rewrote exactly what was pasted, so if you meant to send RFC 3199's text, send that part and I'll slay it too 🧚
📦 where this page comes from
- ietf: rfc3199 2003-02
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms