RFC 1999
Request for Comments Summary RFC Numbers 1900-1999
Part 1 of 4 🎀
Request for Comments Summary 💖
Okay bestie, RFC 1999 is basically the group chat recap for RFCs 1900 through 1999 🦋 It's from the Network Working Group, written by J. Elliott at ISI, dated January 1997, and it's filed as Informational ✨ It doesn't obsolete or update anything, since the header doesn't list any, and it's a tour guide for the RFC numbers 1900-1999, not a new spec. 💅
Status of This Memo ✨
So this RFC is a slightly annotated list of the 100 RFCs from RFC 1900 all the way through RFCs 1999 🌸 It's a status report on those RFCs. It provides information for the Internet community, and it does not specify an Internet standard of any kind. Distribution of this memo is unlimited 💜
Note 🧚
Many RFCs, but not all, are Proposed Standards, Draft Standards, or Standards. Since their status can change during standards processing, this memo only notes that they're on the standards track 🔥 For the current state and status, check the latest edition of "Internet Official Protocol Standards." Standards-track RFCs are marked [STANDARDS-TRACK] in the list below 🎀
Here's the table layout the list follows:
RFC Author Date Title
--- ------ ---- -----1999 · Elliott · Jan 97 💖 Requests For Comments Summary
This memo. Yes, this is the one you're reading right now 🙈
1998 · Chen · Aug 96 🦋 An Application of the BGP Community Attribute in Multi-home Routing
This document presents an application of the BGP community attribute [2] in simplifying the implementation and configuration of routing policies in the multi-provider Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1997 · Chandra · Aug 96 🌈 BGP Communities Attribute
This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. [STANDARDS-TRACK]
1996 · Vixie · Aug 96 ⭐ A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)
This memo describes the NOTIFY opcode for DNS, by which a master server advises a set of slave servers that the master's data has been changed and that a query should be initiated to discover the new data. [STANDARDS-TRACK]
1995 · Ohta · Aug 96 🍓 Incremental Zone Transfer in DNS
This document proposes extensions to the DNS protocols to provide an incremental zone transfer (IXFR) mechanism. [STANDARDS-TRACK]
1994 · Simpson · Aug 96 🫶 PPP Challenge Handshake Authentication Protocol (CHAP)
This document defines a method for Authentication using PPP, which uses a random Challenge, with a cryptographically hashed Response which depends upon the Challenge and a secret key. [STANDARDS-TRACK]
1993 · Barbir · Aug 96 🧚 PPP Gandalf FZA Compression Protocol
This document describes the use of the Gandalf FZA data compression algorithm [3] for compressing PPP encapsulated packets. This memo provides information for the Internet community. It does not specify an Internet standard.
1992 · Castineyra · Aug 96 👑 The Nimrod Routing Architecture
Nimrod is a scalable routing architecture designed to accommodate a continually expanding and diversifying internetwork. First suggested by Noel Chiappa, the Nimrod architecture has undergone revision and refinement through the efforts of the Nimrod working group of the IETF. In this document, we present a detailed description of this architecture. This memo provides information for the Internet community. It does not specify an Internet standard.
1991 · Atkins · Aug 96 💜 PGP Message Exchange Formats
This document describes the format of "PGP files", i.e., messages that have been encrypted and/or signed with PGP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1990 · Sklower · Aug 96 🌸 The PPP Multilink Protocol (MP)
This document proposes a method for splitting, recombining and sequencing datagrams across multiple logical data links. [STANDARDS-TRACK]
1989 · Simpson · Aug 96 ✨ PPP Link Quality Monitoring
This document defines a protocol for generating Link-Quality-Reports. [STANDARDS-TRACK]
1988 · McAnally · Aug 96 🔥 Conditional Grant of Rights to Specific Hewlett-Packard Patents In Conjunction With the Internet Engineering Task Force's Internet-Standard Network Management Framework
This grant is made to help facilitate inclusion of certain patented search address technology covering network device mapping in IETF standards-track Management Information Base (MIB) modules. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1987 · Newman · Aug 96 🦋 Ipsilon's General Switch Management Protocol Specification Version 1.1
The General Switch Management Protocol (GSMP), is a general purpose protocol to control an ATM switch. GSMP allows a controller to establish and release connections across the switch; add and delete leaves on a point-to-multipoint connection; manage switch ports; request configuration information; and request statistics. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1986 · Polites · Aug 96 🎀 Experiments with a Simple File Transfer Protocol for Radio Links using Enhanced Trivial File Transfer Protocol (ETFTP)
This document is a description of the Enhanced Trivial File Transfer Protocol (ETFTP). This protocol is an experimental implementation of the NETwork BLock Transfer Protocol (NETBLT), RFC 998 [1], as a file transfer application program. This memo defines an Experimental Protocol for the Internet community.
1985 · De Winter · Aug 96 💅 SMTP Service Extension for Remote Message Queue Starting
This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to start the processing of its queues for messages to go to a given host. [STANDARDS-TRACK]
…continued in part 2 🦋
🫶 heads up bestie: this text is actually an RFC index listing for RFCs 1934 to 1966, not RFC 1999, and the "sections already covered" bit doesn't match it either. So I rewrote exactly what's here. If you meant RFC 1999, paste that one and I'll slay it properly 💅
This memo does not specify an Internet standard of any kind. 💅
1966 Bates Jun 96 BGP Route Reflection
An alternative to full mesh IBGPokay so this one is all about Route Reflection 🦋, a method built to alleviate the need for "full mesh" IBGP 💜 It's an Experimental Protocol for the Internet community 🧪
1965 Traina Jun 96 Autonomous System Confederations for BGPthis doc is giving BGP extension energy ✨ It describes how to make a confederation of autonomous systems that looks like ONE single autonomous system to any BGP peers outside it 👑 It's also an Experimental Protocol for the Internet community 🔬
1964 Linn Jun 96 The Kerberos Version 5 GSS-API Mechanismthis spec is so put-together 🎀 It defines the protocols, procedures and conventions peers use when they implement the Generic Security Service Application Program Interface (as specified in RFCs 1508 and 1509) with Kerberos Version 5 tech (as specified in RFC 1510). [STANDARDS-TRACK] 🔐
1963 Schneider Aug 96 PPP Serial Data Transport Protocol
(SDTP)ngl this one's so cool 🌊 From the PPP point of view it's a brand new Network level protocol, the PPP Serial Data Transport Protocol. It gives you encapsulation plus an associated control protocol for moving serial data streams across a PPP link 🧚 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1962 Rand Jun 96 The PPP Compression Control Protocol
(CCP)okay this one is about negotiating data compression over PPP links 🗜️✨ [STANDARDS-TRACK] 💖
1961 McMahon Jun 96 GSS-API Authentication Method for SOCKS
Version 5this is the spec for the SOCKS V5 GSS-API authentication protocol 🧦 It also defines a GSS-API-based encapsulation that gives you integrity, authentication and optional confidentiality 🔏 [STANDARDS-TRACK]
1960 Howes Jun 96 A String Representation of LDAP
Search Filtersso the Lightweight Directory Access Protocol (LDAP) [1] describes a network representation of a search filter that gets sent to an LDAP server 🔎 Some apps would love a shared, human-readable way to write these filters, so this doc defines exactly that string format 📝 [STANDARDS-TRACK]
1959 Howes Jun 96 An LDAP URL Formatthis one describes an LDAP Uniform Resource Locator format 🔗 It lets Internet clients get direct access to the LDAP protocol, which is so convenient 🥰 [STANDARDS-TRACK]
1958 Carpenter Jun 96 Architectural Principles of the Internetthe Internet grew up in an evolutionary way, not from some Grand Plan 🌱 That evolution is a big reason it's been so successful, so this doc records a snapshot of the current architectural principles 📸 It's meant for general guidance and general interest, and it is in no way a formal or invariant reference model 🙈 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1957 Nelson Jun 96 Some Observations on Implementations
of the Post Office Protocol (POP3)this memo is just sharing some observations on how POP3 implementations are going 📬 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🌸
1956 Engebretson Jun 96 Registration in the MIL Domainthis RFC lays out the policy for registering second level domains under the ".MIL" domain 🪖 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1955 Hinden Jun 96 New Scheme for Internet Routing and
Addressing (ENCAPS) for IPNGthis paper proposes a new scheme that the author believes is a good medium term solution to the routing and address problems of the internet 🧠 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🦋
1954 Newman May 96 Transmission of Flow Labelled IPv4 on
ATM Data Links Ipsilon Version 1.0this doc specifies how to send IPv4 datagrams over an ATM data link 💫 It covers the default way and also the case where flow labelling is in play via the Ipsilon Flow Management Protocol [IFMP] 🌈 This document provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1953 Newman May 96 Ipsilon Flow Management Protocol
Specification for IPv4 Version 1.0the Ipsilon Flow Management Protocol (IFMP) lets a node tell an adjacent node to attach a layer 2 label to a specified IP flow 🏷️ This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🫶
1952 Deutsch May 96 GZIP file format specification
version 4.3this spec defines a lossless compressed data format that's compatible with the widely used GZIP utility 🗜️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🍓
1951 Deutsch May 96 DEFLATE Compressed Data Format
Specification version 1.3this one is a lossless compressed data format that mixes the LZ77 algorithm with Huffman coding 🧩 Its efficiency is comparable to the best currently available general-purpose compression methods, which is honestly iconic 👑 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1950 Deutsch May 96 ZLIB Compressed Data Format
Specification version 3.3this spec defines a lossless compressed data format 🗃️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 💜
1949 Ballarde May 96 Scalable Multicast Key Distributionthis memo offers a scalable solution to the multicast key distribution problem 🔑 It defines an Experimental Protocol for the Internet community 🧪
1948 Bellovin May 96 Defending Against Sequence Number
Attacks🚨 okay bestie, this one is serious. IP spoofing attacks based on sequence number spoofing have become a serious threat on the Internet (CERT Advisory CA-95:01).
ubiquitous cryptographic authentication is the right answer 🔐 but this memo proposes a simple modification to TCP implementations that should be a very substantial block to the current wave of attacks 🛡️ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1947 Spinellis May 96 Greek Character Encoding for Electronic
Mail Messagesthis doc describes a standard encoding for electronic mail [RFC822] that contains Greek text 🇬🇷 It also gives implementation guide-lines 📖 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1946 Jackowski May 96 Native ATM Support for ST2+this memo describes a working implementation that lets applications directly invoke ATM services in these environments: ATM to internet, internet to ATM, and internet to internet across ATM ⚡ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1945 Berners-Lee May 96 Hypertext Transfer Protocol -- HTTP/1.0the Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed needed for distributed, collaborative, hypermedia information systems 🌐 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 💖
1944 Bradner May 96 Benchmarking Methodology for Network
Interconnect Devicesthis document discusses and defines a bunch of tests that can describe the performance characteristics of a network interconnecting device 📊 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1943 Jennings May 96 Building an X.500 Directory Service
in the USthis doc gives definitions and recommends the considerations you must take into account to run an X.500 Directory Service in the United States 🇺🇸 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 📚
1942 Raggett May 96 HTML Tablesthis spec extends HTML to support a wide variety of tables 🧁 This memo defines an Experimental Protocol for the Internet community.
1941 Sellers May 96 Frequently Asked Questions for Schoolsthis FYI doc was produced by the Internet School Networking (ISN) group in the User Services Area of the Internet Engineering Task Force (IETF) 🏫 Its goal is to introduce the Internet to faculty, administration and other school staff in primary and secondary schools 🍎 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1940 Estrin May 96 Source Demand Routing: Packet Format and
Forwarding Specification (Version 1).the purpose of SDRP is to support source-initiated selection of routes 🗺️ It complements the route selection that existing routing protocols already provide, for both inter-domain and intra-domain routes 🧭 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1939 Myers May 96 Post Office Protocol - Version 3the Post Office Protocol - Version 3 (POP3) lets a workstation dynamically access a maildrop on a server host in a useful way 📫 [STANDARDS-TRACK] 💌
1938 Haller May 96 A One-Time Password Systemthis doc describes a one-time password authentication system (OTP) 🔢 [STANDARDS-TRACK] 🔐
1937 Rekhter May 96 "Local/Remote" Forwarding Decision in
Switched Data Link Subnetworksthis doc describes extensions to the IP architecture that relax these constraints 🪄 That means you get full use of the services that SVC-based Data Link subnetworks provide 🦋 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1936 Touch Apr 96 Implementing the Internet Checksum in
Hardwarethis memo presents techniques for implementing the Internet Checksum in hardware efficiently 🛠️ It includes PLD code for programming a single, low-cost part to do checksumming at 1.26 Gbps 🚀 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🔥
1935 Quarterman Apr 96 What is the Internet, Anyway?this memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🤷♀️✨
1934 Smith Apr 96 Ascend's Multilink Protocol Plus (MP+)this doc proposes an extension to the PPP Multilink Protocol (MP) [1] 🌟 Multilink Protocol Plus (MP+) is a brand new control protocol for managing multiple data links that are bundled by MP 🧷 This memo provides information for the Internet community. This memo does not specify an
RFC>>>
to be continued 🧚✨
Internet standard of any kind. 🫶
1933
1933 Gilligan Apr 96 Transition Mechanisms for IPv6 Hosts
and Routersokay so this one is about IPv4 compatibility mechanisms that IPv6 hosts and routers can implement 🦋 it's giving bridge-building energy between the two protocols 🌉 [STANDARDS-TRACK]
1932
1932 Cole Apr 96 IP over ATM: A Framework Documentthis doc classifies ATM approaches and issues, and it's hoped that this will help the IP over ATM working group focus their direction 🎯 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 💅
1931
1931 Brownell Apr 96 Dynamic RARP Extensions for
Automatic Network Address Acquisitionbestie, this memo describes extensions to the Reverse Address Resolution Protocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-RARP) 🎀 This memo provides information for the Internet community. This memo does not define an Internet standard of any kind.
1930
1930 Hawkinson Mar 96 Guidelines for creation, selection, and
registration of an Autonomous System (AS)this one is all about when it makes sense to register and use an Autonomous System (AS), plus a list of criteria for that 📋 This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 🌸
1929
1929 Leech Mar 96 Username/Password Authentication for
SOCKS V5so the SOCKS Version 5 protocol spec is a generalized framework for using arbitrary authentication protocols during the initial socks connection setup 🧚 this doc is one of those protocols, slotting into the SOCKS Version 5 authentication "subnegotiation" 🔐 [STANDARDS-TRACK]
1928
1928 Leech Mar 96 SOCKS Protocol Version 5this memo describes a protocol that evolves from the previous version, version 4 [1] 📈 it's built from active discussions and prototype implementations, so it's giving real-world receipts 🧾 [STANDARDS-TRACK]
1927
1927 Rogers Apr 96 Suggested Additional MIME Types for
Associating Documentsseven new MIME types are suggested in this document 🍓 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1926
1926 Eriksson Apr 96 An Experimental Encapsulation of IP
Datagrams on Top of ATMthis RFC describes a way to encapsulate IP datagrams on top of Acoustical Transmission Media (ATM) 🎶 This is a non-recommended standard. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🦋
1925
1925 Callon Apr 96 The Twelve Networking Truthsthe main character of networking docs 👑 this memo documents the fundamental truths of networking for the Internet community. it does not specify a standard, except in the sense that all standards must implicitly follow the fundamental truths 💖 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1924
1924 Elz Apr 96 A Compact Representation of IPv6 Addressesthis document specifies a more compact way to represent IPv6 addresses, one that permits encoding in a mere 20 bytes ✨ it's so efficient it's rude 💅 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1923
1923 Halpern Mar 96 RIPv1 Applicability Statement for
Historic Statusngl this one is a little dramatic 🥀 RIP Version 1 [RFC-1058] has been declared an historic document, and this Applicability statement is the supporting motivation for that declaration. the primary reason, as described below, is the Classful nature of RIPv1 📉 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1922
1922 Zhu Mar 96 Chinese Character Encoding for Internet
Messagesthis memo describes methods for transporting Chinese characters in Internet services that carry text, like electronic mail [RFC-822], network news [RFC-1036], telnet [RFC-854] and the World Wide Web [RFC-1866] 🌏 This memo provides information for the Internet community. It does not specify an Internet standard. 🎀
1921
1921 Dujonc Mar 96 TNVIP Protocolthe goal of this document is to specify a Telnet profile for VIP terminal emulation, so you can access the BULL hosts applications through a TCP/IP network 💻 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🌈
1920
1920 I.A.B. Mar 96 INTERNET OFFICIAL PROTOCOL STANDARDSthis memo describes the state of standardization of protocols used on the Internet, as determined by the Internet Architecture Board (IAB) 🗂️ [STANDARDS-TRACK]
1919
1919 Chatel Mar 96 Classical versus Transparent IP Proxiesthis document explains "classical" and "transparent" proxy techniques, and it tries to give rules for figuring out when each proxy system may be used without causing problems 🔍 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 💜
1918
1918 Rekhter Feb 96 Address Allocation for Private Internetsthis document describes address allocation for private internets 🏠 This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 🍑
1917
1917 Nesser Feb 96 An Appeal to the Internet Community to
Return Unused IP Networks (Prefixes)
to the IANAthis is a sweet little appeal 🥺 to the Internet community, asking folks to return unused address space (any block of consecutive IP prefixes) to the Internet Assigned Numbers Authority (IANA) or any of the delegated registries, for reapportionment 🌷 This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
1916
1916 Berkowitz Feb 96 Enterprise Renumbering: Experience and
Information Solicitationrenumbering IP networks is urgent and genuinely hard 😭 so the PIER working group is putting together a series of documents to help sites with their renumbering efforts 🧁 the intent is to give both educational and practical information to the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
1915
1915 Kastenholz Feb 96 Variance for The PPP Connection Control
Protocol and The PPP Encryption Control
Protocolthe PPP Working group developed two protocols 🔧 the first is the Compression Control Protocol (CCP), which controls compression on PPP links, documented in draft-ietf-pppext-compression-04.txt 🗜️ the second is the Encryption Control Protocol (ECP), which controls encryption on serial links, documented in draft-ietf-pppext-encryption-03.txt 🔒 This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
1914
1914 Faltstrom Feb 96 How to Interact with a Whois++ Meshin the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is done by the client 🧭 since each server 'refers' the client to the next appropriate server(s), the client is the one doing the walking 🚶♀️ [STANDARDS-TRACK]
1913
1913 Weider Feb 96 Architecture of the Whois++ Index Servicethe authors describe an architecture for indexing in distributed databases, and they apply this to the WHOIS++ protocol 🗃️ [STANDARDS-TRACK]
1912
1912 Barr Feb 96 Common DNS Operational and Configuration
Errorsthis memo describes errors that show up often, both in how Domain Name System (DNS) servers operate and in the data those DNS servers contain 🙈 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 💀
1911
1911 Vaudreuil Feb 96 Voice Profiule of Internet Mailthe following document is a profile of the Internet standard MIME and ESMTP protocols, for use as a digital voice networking protocol 🎙️ This memo defines an Experimental Protocol for the Internet community. 🧚
1910
1910 Waters Feb 96 User-based Security Model for SNMPv2in this administrative framework, a security model defines the mechanisms used to reach an administratively-defined level of security for protocol interactions 🔐 many security models might be defined, but this document, User-based Security Model for SNMPv2, is the first, and, as of this writing, only, security model for this administrative framework 💖 This memo defines an Experimental Protocol for the Internet community.
1909
1909 McClogherie Feb 96 An Administrative Infrastructure for
SNMPv2the purpose of this document, An Administrative Infrastructure for SNMPv2, is to define an administrative framework that realizes effective management across a variety of configurations and environments 🗂️ This memo defines an Experimental Protocol for the Internet community.
1908
1908 Case Jan 96 Coexistence between Version 1 and
Version 2 of the Internet-standard
Network Management Frameworkthis document is all about coexistence 🤝 between version 2 of the Internet-standard Network Management Framework [1-6], termed the SNMP version 2 framework (SNMPv2), and the original Internet-standard Network Management Framework (SNMPv1>. [STANDARDS-TRACK]
1907
1907 Case Jan 96 Management Information Base for Version
2 of the Simple Network Management
Protocol (SNMPv2)the purpose of this document is to define managed objects that describe the behavior of an SNMPv2 entity 📦 [STANDARDS-TRACK]
1906
1906 Case Jan 96 Transport Mappings for Version 2 of the
Simple Network Management Protocol (SNMPv2)the purpose of this document is to define how SNMPv2 maps onto an initial set of transport domains 🗺️ [STANDARDS-TRACK]
1905
1905 Case Jan 96 Protocol Operations for Version 2 of the
Simple Network Management Protocol (SNMPv2)the purpose of this document, Protocol Operations for SNMPv2, is to define the operations of the protocol with respect to the sending and receiving of the PDUs 📨 [STANDARDS-TRACK]
1904
1904 Case Jan 96 Conformance Statements for Version 2 of
the Simple Network Management Protocol
(SNMPv2)it may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved 📊 this document defines the notation used for those purposes 🧾 [STANDARDS-TRACK]
1903
1903 Case Jan 96 Textual Conventions for Version 2 of the
Simple Network Management Protocol (SNMPv2)the purpose of this document is to define the initial set of textual conventions available to all MIB modules 🎀 [STANDARDS-TRACK]
1902
1902 Case Jan 96 Structure of Management Information for
Version 2 of the Simple Network
Management Protocol (SNMPv2)the purpose of this document, the Structure of Management Information (SMI), is to define that adapted subset and to assign a set of associated administrative values 🧩 [STANDARDS-TRACK]
1901
1901 Case Jan 96 Introduction to Community-based SNMPv2the purpose of this document is to define the Community-based
Administrative Framework for the SNMP version 2 framework (SNMPv2) 🎀
okay bestie, this one is marked as an Experimental protocol for the Internet community 🧪✨
1900 Carpenter Feb 96 Renumbering Needs WorkRenumbering Needs Work 🌸
okay so hosts on an IP network are identified by their IP addresses, and the IP address prefixes of subnets get advertised by routing protocols 🛰️ when that IP addressing info for a host or subnet changes, that's called "renumbering" 💅 this memo is giving info to the Internet community 🧚 but it does not specify an Internet standard of any kind, so it's more of a vibe check than a spec 💖
Security Considerations 🔒
security issues are not discussed in this memo 💀 no cap, it just doesn't get into them at all 🙈
Author's Address 💌
Josh Elliott
University of Southern California
Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: elliott@isi.edu📦 where this page comes from
- ietf: rfc1999 1997-01
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms