RFC 1499
Summary of 1400-1499
RFC 1499: Request for Comments Summary 🎀
Okay bestie, let's start with the basics 💖. This is RFC 1499, titled Request for Comments Summary, and it covers RFC Numbers 1400-1499. It was written by J. Elliott from ISI, it's an Informational doc, and it's dated January 1997 🗓️. The header doesn't list anything it obsoletes or updates, so no drama there ✨.
Status of This Memo 💅
This one is a slightly annotated list of the 100 RFCs from RFC 1400 through RFCs 1499, so it's basically a status report on them 📋. It gives info to the Internet community, but it does not specify an Internet standard of any kind, so no cap, it's not a rulebook 🙅♀️. Distribution of this memo is unlimited 🌈.
Note 🫶
Many RFCs, but not all, are Proposed Standards, Draft Standards, or Standards. The status of these can change during standards processing, so the note just says they're on the standards track 🛤️. For the current state and status, check the latest edition of "Internet Official Protocol Standards" 📚. In the list below, standards-track RFCs are marked [STANDARDS-TRACK] 🏷️.
The Index 📚
RFC Author Date Title
--- ------ ---- -----
1499 Elliott Jan 97 Requests For Comments Summary
1498 Saltzer Aug 93 On the Naming and Binding of Network
Destinations
1497 Reynolds Aug 93 BOOTP Vendor Information Extensions
1496 Alverstrand Aug 93 Rules for Downgrading Messages from
X.400/88 to X.400/84 When MIME
Content-Types are Present in the
Messages
1495 Alverstrand Aug 93 Mapping between X.400 and RFC-822
Message Bodies
1494 Alverstrand Aug 93 Equivalences between 1988 X.400 and
RFC-822 Message Bodies
1493 Decker Jul 93 Definitions of Managed Objects
for Bridges
1492 Finseth Jul 93 An Access Control Protocol, Sometimes
Called TACACS
1491 Weider Jul 93 A Survey of Advanced Usages of X.500
1490 Bradley Jul 93 Multiprotocol Interconnect over Frame
Relay
1489 Chernov Jul 93 Registration of a Cyrillic Character Set
1488 Howes Jul 93 The X.500 String Representation of
Standard Attribute Syntaxes
1487 Yeong Jul 93 X.500 Lightweight Directory Access
Protocol
1486 Rose Jul 93 An Experiment in Remote Printing
1485 Kille Jul 93 A String Representation of Distinguished
Names (OSI-DS 23 (v5))
1484 Kille Jul 93 Using the OSI Directory to achieve
User Friendly Naming (OSI-DS 24 (v1.2))
1483 Heinanen Jul 93 Multiprotocol Encapsulation over ATM
Adaptation Layer 5
1482 Knopper Jun 93 Aggregation Support in the NSFNET
Policy-Based Routing Database
1481 Huitema Jul 93 IAB Recommendation for an Intermediate
Strategy to Address the Issue of Scaling
1480 Cooper Jun 93 The US Domain
1479 Steenstrup Jul 93 Inter-Domain Policy Routing Protocol
Specification: Version 1
1478 Steenstrup Jul 93 An Architecture for Inter-Domain Policy
Routing
1477 Steenstrup Jul 93 IDPR as a Proposed Standard
1476 Ullman Jun 93 RAP: Internet Route Access Protocol
1475 Ullman Jun 93 TP/IX: The Next Internet
1474 Kastrenholz Jun 93 The Definitions of Managed Objects for
the Bridge Network Control Protocol of
the Point-to-Point Protocol
1473 Kastrenholz Jun 93 The Definitions of Managed Objects for
the IP Network Control Protocol of
the Point-to-Point Protocol
1472 Kastrenholz Jun 93 The Definitions of Managed Objects for
the Security Protocols of
the Point-to-Point ProtocolThe Tea on Each RFC ☕
RFC 1499: Requests For Comments Summary 🪞
This memo. Yep, it's the one you're reading right now 🫣.
RFC 1498: On the Naming and Binding of Network Destinations 🧭
This brief paper is a perspective on names for destinations in data communication networks 🌐. It has two big ideas. First, it's helpful to tell apart four different kinds of objects that can be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe how those four kinds of objects relate to each other 🔗. It provides information for the Internet community and does not specify an Internet standard 🙌.
RFC 1497: BOOTP Vendor Information Extensions 🧸
This is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo 👑. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP) 🥾.
RFC 1496: Rules for Downgrading Messages from X.400/88 to X.400/84 When MIME Content-Types are Present in the Messages 📨
This one is giving very specific energy 😭. It describes how RFC-1328 must be modified to support these scenarios:
SMTP(MIME) -> X.400(84)
X.400(84) -> SMTP(MIME)It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT obsoleted 🙅♀️. [STANDARDS-TRACK] 🏷️
RFC 1495: Mapping between X.400 and RFC-822 Message Bodies 🔁
Ever since X.400(84) showed up, people have been working on mappings between MHS and RFC-822 💌. The latest is RFC-1327 [3], which mainly focuses on translating the envelope and headers. This document complements RFC-1327 because it focuses on translating the message body 🫶. [STANDARDS-TRACK]
RFC 1494: Equivalences between 1988 X.400 and RFC-822 Message Bodies 📋
This document describes the content of the "IANA MHS/MIME Equivalence table" and defines the initial configuration of that table 🗂️. Mappings for new MIME content-types and/or X.400 body part types should be registered with the IANA, so there's less redundancy and better interoperability 🤝. [STANDARDS-TRACK]
RFC 1493: Definitions of Managed Objects for Bridges 🌉
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets 🖥️. In particular, it defines objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments 🧩. [STANDARDS-TRACK]
RFC 1492: An Access Control Protocol, Sometimes Called TACACS 🔐
This RFC documents the extended TACACS protocol as used by Cisco Systems terminal servers 🖲️. The same protocol is also used by the University of Minnesota's distributed authentication system 🏫. This memo provides information for the Internet community and does not specify an Internet standard 💁♀️.
RFC 1491: A Survey of Advanced Usages of X.500 🔍
This document came from a survey asking people to detail their advanced usages of X.500 📊. It shows how various organizations are using X.500 in ways that go beyond the view of X.500 as a "White Pages" service 📒. This RFC is a product of the Integrated Directory Services Working Group of the Application and User Services Areas of the IETF 🧑💻. This memo provides information for the Internet community and does not specify an Internet standard 🙌.
RFC 1490: Multiprotocol Interconnect over Frame Relay 🎞️
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone 🚚. It covers both Bridging and Routing aspects 🌉. It also describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU 📦. [STANDARDS-TRACK]
RFC 1489: Registration of a Cyrillic Character Set 🇷🇺
Okay, so the proposed character set "koi8-r" isn't currently an international standard, but a very large user community supports it, including Relcom Net 🫂. Factually, "koi8-r" is the de-facto standard for Unix and global network applications in the former Soviet Union 💻. That's why the Society of Unix User Groups (SUUG) believes "koi8-r" should be registered 📝. This memo provides information for the Internet community and does not specify an Internet standard 🌸.
RFC 1488: The X.500 String Representation of Standard Attribute Syntaxes 🪡
This document sets out the requirements that encoding rules must satisfy when rendering Directory attribute syntaxes into a form suitable for use in LDAP 🧵. Then it defines the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3] 📐. [STANDARDS-TRACK]
RFC 1487: X.500 Lightweight Directory Access Protocol 🪶
This protocol is designed to give access to the Directory without the resource requirements of the Directory Access Protocol (DAP) 💫. It's the lighter option, bestie 🏃♀️. [STANDARDS-TRACK]
RFC 1486: An Experiment in Remote Printing 🖨️
This memo describes a technique for "remote printing" that uses the Internet mail infrastructure 📬. It focuses on the case where remote printers are connected to the international telephone network ☎️. This memo defines an Experimental Protocol for the Internet community and does not specify an Internet standard 🧪.
RFC 1485: A String Representation of Distinguished Names (OSI-DS 23 (v5)) 🏷️
When a distinguished name gets communicated to users who aren't using a directory protocol (like in a mail message), you need a user-oriented string representation of it 💬. [STANDARDS-TRACK]
RFC 1484: Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2)) 💖
This proposal sets out conventions for representing names in a friendly way, and shows how that can be used to achieve really friendly naming 🥰. This memo defines an Experimental Protocol for the Internet community and does not specify an Internet standard 🧪.
RFC 1483: Multiprotocol Encapsulation over ATM Adaptation Layer 5 🧮
This memo describes two encapsulation methods for carrying network interconnect traffic over ATM AAL5 ✈️. [STANDARDS-TRACK]
RFC 1482: Aggregation Support in the NSFNET Policy-Based Routing Database 🗺️
This document describes plans for supporting route aggregation, as specified in the descriptions of Classless Inter-Domain Routing (CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network Service 🛣️. This memo provides information for the Internet community and does not specify an Internet standard 🌷.
RFC 1481: IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling 📈
CIDR is proposed as an immediate-term strategy to extend the life of the current 32 bit IP address space ⏳. This memo provides information for the Internet community and does not specify an Internet standard 🫶.
RFC 1480: The US Domain 🇺🇸
This is a description of the US Top Level Domains on the Internet 🌐. This memo provides information for the Internet community and does not specify an Internet standard 💁♀️.
RFC 1479: Inter-Domain Policy Routing Protocol Specification: Version 1 🛰️
This one presents the set of protocols and procedures that make up Inter-Domain Policy Routing (IDPR) 🧠. [STANDARDS-TRACK]
RFC 1478: An Architecture for Inter-Domain Policy Routing 🏛️
This one presents an architecture for inter-domain policy routing (IDPR) 🗿. [STANDARDS-TRACK]
RFC 1477: IDPR as a Proposed Standard 📝
This document discusses inter-domain policy routing (IDPR), including an overview of its functionality and a discussion of experiments 🧪. This memo provides information for the Internet community and does not specify an Internet standard ✨.
RFC 1476: RAP: Internet Route Access Protocol 🛤️
This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider 🌍. This memo defines an Experimental Protocol for the Internet community and does not specify an Internet standard 🧪.
RFC 1475: TP/IX: The Next Internet 🔮
This memo presents the specification for version 7 of the Internet Protocol, along with version 7 of TCP and the user datagram protocol 🧚. This memo defines an Experimental Protocol for the Internet community and does not specify an Internet standard 🧪.
RFC 1474: The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol 🌈
This memo defines a portion of the MIB for use with network management protocols in TCP/IP-based internets 🖥️. In particular, it describes managed objects used for managing the bridge Network Control Protocol [10] on subnetwork interfaces using the family of Point-to-Point Protocols 🔧. [STANDARDS-TRACK]
RFC 1473: The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol 💜
This memo defines a portion of the MIB for use with network management protocols in TCP/IP-based internets 🖥️. In particular, it describes managed objects used for managing the IP Network Control Protocol on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, & 12] 🧩. [STANDARDS-TRACK]
RFC 1472: The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol 🔒
This memo defines a portion of the MIB for use with network management protocols in TCP/IP-based internets 🖥️. In particular, it describes managed objects used for managing the Security Protocols on subnetwork interfaces using the family of Point-to-Point
Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK] 💅
Heads up, bestie: the text pasted here is actually an index listing for RFCs 1442 through 1471, not RFC 1499 itself. I rewrote exactly what's in front of me, so every detail is kept.
1471 · Kastrenholz · Jun 93 🦋
The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol
Okay so this memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. Specifically, it describes managed objects for managing the Link Control Protocol and Link Quality Monitoring on subnetwork interfaces that use the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK] 💖
1470 · Enger · Jun 93 🌸
FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
The goal of this FYI memo is to give an update to FYI 2, RFC 1147 [1], which gave practical info to site administrators and network managers. This memo provides information for the Internet community. It does not specify an Internet standard. 🧚
1469 · Pusateri · Jun 93 🎀
IP Multicast over Token-Ring Local Area Networks
This document specifies a method for sending IP multicast datagrams over Token-Ring Local Area Networks. [STANDARDS-TRACK] ✨
1468 · Murai · Jun 93 🍓
Japanese Character Encoding for Internet Messages
This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. This memo provides information for the Internet community. It does not specify an Internet standard. 🌈
1467 · Topolcic · Aug 93 🌸
Status of CIDR Deployment in the Internet
This document describes the current status of the development and deployment of CIDR technology into the Internet. It replaces RFC 1367, which was a schedule for deploying IP address space management procedures to support route aggregation. This memo provides information for the Internet community. It does not specify an Internet standard. 👑
1466 · Gerich · May 93 💅
Guidelines for Management of IP Address Space
This document proposes a plan that will move forward the implementation of RFC 1174, and that defines the allocation and assignment of the network number space. This memo provides information for the Internet community. It does not specify an Internet standard. 🫶
1465 · Eppenberger · May 93 🦋
Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing
This document proposes short-term solutions for maintaining and distributing routing information, and shows how messages can travel over different networks by using multi stack MTAs as relays. This memo defines an Experimental Protocol for the Internet community. 🧪
1464 · Rosenbaum · May 93 💜
Using the Domain Name System To Store Arbitrary String Attributes
This paper describes a simple means to associate arbitrary string information (ASCII text) with attributes that have not been defined by the DNS. This memo defines an Experimental Protocol for the Internet community. 🌸
1463 · Hoffman · May 93 📚
FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings for the Network Novice
This bibliography offers a short list of recent information resources that help the network novice get familiar with the Internet, including its associated networks, resources, protocols, and history. This memo provides information for the Internet community. It does not specify an Internet standard. 🌟
1462 · Krol · May 93 🌈
FYI on "What is the Internet?"
This FYI RFC answers the question, "What is the Internet?" and is produced by the User Services Working Group of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard. 💫
1461 · Throop · May 93 🧚
SNMP MIB extension for Multiprotocol Interconnect over X.25
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. Specifically, it defines objects for managing Multiprotocol Interconnect (including IP) traffic carried over X.25. [STANDARDS-TRACK] 🎀
1460 · Rose · Jun 93 💖
Post Office Protocol - Version 3
This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS-TRACK] 📬
1459 · Oikarinen · May 93 💬
Internet Relay Chat Protocol
The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server. This memo defines an Experimental Protocol for the Internet community. 🦋
1458 · Braudes · May 93 🌷
Requirements for Multicast Protocols
This memo discusses some of these unresolved issues, and provides a high-level design for a new multicast transport protocol, a group address and membership authority, and modifications to existing routing protocols. This memo provides information for the Internet community. It does not specify an Internet standard. 🔥
1457 · Housley · May 93 🔒
Security Label Framework for the Internet
This memo presents a security labeling framework for the Internet. The framework is intended to help protocol designers determine what, if any, security labeling should be supported by their protocols. This memo provides information for the Internet community. It does not specify an Internet standard. 🛡️
1456 · V.S.W.G. · May 93 🌏
Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: Vietnamese Quoted-Readable Specification Revision 1.1
This document provides information to the Internet community on the currently used conventions for encoding Vietnamese characters into 7-bit US ASCII and in an 8-bit form. This memo provides information for the Internet community. It does not specify an Internet standard. 🇻🇳
1455 · Eastlake · May 93 🔐
Physical Link Security Type of Service
This RFC documents an experimental protocol providing a Type of Service (TOS) to request maximum physical link security. It is an addition to the types of service enumerated in RFC 1349: Type of Service in the Internet Protocol Suite. This memo defines an Experimental Protocol for the Internet community. 💜
1454 · Dixon · May 93 🌙
Comparison of Proposals for Next Version of IP
This is a slightly edited reprint of RARE Technical Report (RTC(93)004). This memo provides information for the Internet community. It does not specify an Internet standard. 📑
1453 · Chimiak · Apr 93 🎬
A Comment on Packet Video Remote Conferencing and the Transport/Network Layers
This RFC is a vehicle to inform the Internet community about XTP, as it benefits from past Internet activity and targets general-purpose applications and multimedia applications with the emerging ATM networks in mind. This memo provides information for the Internet community. It does not specify an Internet standard. 📹
1452 · Case · Apr 93 🌸
Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework
The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS-TRACK] 🤝
1451 · Case · Apr 93 🌼
Manager-to-Manager Management Information Base
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity acting in both a manager role and an agent role. [STANDARDS-TRACK] 🧠
1450 · Case · Apr 93 🌺
Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK] 📊
1449 · Case · Apr 93 🚚
Transport Mapplings for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK] 🗺️
1448 · Case · Apr 93 ⚙️
Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK] 📨
1447 · McCloghrie · Apr 93 🗝️
Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)
The Administrative Model for SNMPv2 document [3] defines the properties associated with SNMPv2 parties, SNMPv2 contexts, and access control policies. It is the purpose of this document, the Party MIB for SNMPv2, to define managed objects which correspond to these properties. [STANDARDS-TRACK] 🎉
1446 · Galvin · Apr 93 🔑
Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document, Security Protocols for SNMPv2, to define one such authentication and one such privacy protocol. [STANDARDS-TRACK] 🛡️
1445 · Galvin · Apr 93 🏗️
Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document, the Administrative Model for SNMPv2, to define how the administrative framework is applied to realize effective network management in a variety of configurations and environments. [STANDARDS-TRACK] 🌟
1444 · Case · Apr 93 📏
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. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK] ✅
1443 · Case · Apr 93 🧩
Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] 💅
1442 · Case · Apr 93 🏛️
Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)
Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1]. It is the purpose of this document, the Structure of Management Information (SMI), to define that subset. 🧚♀️
1441. Introduction to version 2 of the Internet-standard Network Management Framework ✨
Case · Apr 93
Okay bestie, 1441 is basically the front door to SNMPv2 🚪 Its whole job is to give you an overview of version 2 of the Internet-standard Network Management Framework, which is also called the SNMP version 2 framework (SNMPv2). It's on the standards track too, so this one matters 💅 [STANDARDS-TRACK]
1440. SIFT/UFT: Sender-Initiated/Unsolicited File Transfer 🌸
Troth · Jul 93
This one describes the Sender-Initiated File Transfer (SIFT) protocol, which people also call the Unsolicited File Transfer (UFT) protocol 🫶 It defines an Experimental Protocol for the Internet community, so it's still in its experimental era 🧪
1439. The Uniqueness of Unique Identifiers 🧚
Finseth · Mar 93
Ngl this one is pure info vibes 🌈 It's useful when you're picking a method for assigning unique identifiers to people. It provides information for the Internet community and does not specify an Internet standard, so no pressure 💖
1438. IETF Statements Of Boredom (SOB)s 💀
Chapin · Apr 93
Okay this one is iconic 😭 It creates a brand new subseries of RFCs, called IETF Statements Of Boredom (SOBs). It provides information for the Internet community and does not specify an Internet standard. The name is doing so much work 🙈
1437. The Extension of MIME Content-Types to a New Medium 🦋
Borenstein · Apr 93
This one defines one particular type of MIME data, the matter-transport/sentient-life-form type 👽 It provides information for the Internet community and does not specify an Internet standard. Main character energy, no cap 🌟
1436. The Internet Gopher Protocol 🍓
Anklesaria · Mar 93
It describes the protocol, lists some of the implementations that are available right now, and gives an overview of how to implement new client and server applications 🧑💻 It provides information for the Internet community and does not specify an Internet standard.
1435. IESG Advice from Experience with Path MTU Discovery 🙈
Knowles · Mar 93
So when people were reviewing the MTU Discovery protocol for possible elevation to Draft Standard, they ran into a real operational problem 😬 The problem comes from the optional suppression of ICMP messages that some routers do. This memo outlines a modification to that practice so MTU Discovery can work correctly. It provides information for the Internet community and does not specify an Internet standard. Fixing the drama 🫶
1434. Data Link Switching: Switch-to-Switch Protocol 🔥
Dixon · Mar 93
This RFC describes IBM's support of Data Link Switching over TCP/IP 💼 It provides information for the Internet community and does not specify an Internet standard.
1433. Directed ARP 💜
Garrett · Mar 93
Directed ARP is a dynamic address resolution procedure. It lets hosts and routers resolve advertised potential next-hop IP addresses on foreign IP networks to their associated link level addresses 🔗 This memo defines an Experimental Protocol for the Internet community.
1432. Recent Internet Books 📚
Quarterman · Mar 93
Here's a list of books related to using the Internet, perfect for your reading list bestie 🎀 It provides information for the Internet community and does not specify an Internet standard.
1431. DUA Metrics ⭐
Barker · Feb 93
This document sets out a set of criteria for judging a DUA implementation, or more precisely a Directory user interface 👀 It provides information for the Internet community and does not specify an Internet standard.
1430. A Strategic Plan for Deploying an Internet X.500 Directory Service 👑
Kille · Feb 93
This one lays out an overall strategy for deploying a Directory Service on the Internet, based on the OSI X.500 Directory Service 🗺️ It provides information for the Internet community and does not specify an Internet standard.
1429. Listserv Distribute Protocol 🫶
Thomas · Feb 93
This memo specifies a subset of the distribution protocol that BITNET LISTSERV uses to deliver mail messages to large amounts of recipients 📬 It provides information for the Internet community and does not specify an Internet standard.
1428. Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME 🌈
Vaudreuil · Feb 93
This one outlines the problems in this environment and an approach to minimizing the cost of moving from current non-MIME 8bit messages to MIME 🌈 This RFC provides information for the Internet community and does not specify an Internet standard.
1427. SMTP Service Extension for Message Size Declaration 🎀
Klensin · Feb 93
This memo defines an extension to the SMTP service where an SMTP client and server interact. The server gets a chance to decline a message, maybe just temporarily, based on the client's estimate of the message size 📏 [STANDARDS-TRACK]
1426. SMTP Service Extension for 8bit-MIMEtransport 🌸
Klensin · Feb 93
This memo defines an extension to the SMTP service. An SMTP content body containing octets outside of the US ASCII octet range (hex 00-7F) can be relayed using SMTP 💌 [STANDARDS-TRACK]
1425. SMTP Service Extensions ✨
Klensin · Feb 93
This memo defines a framework for extending the SMTP service. It does that by giving a means where a server SMTP can tell a client SMTP which service extensions it supports 🧩 [STANDARDS-TRACK]
1424. Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services 🔥
Kaliski · Feb 93
This document describes three types of service supporting Internet Privacy-Enhanced Mail (PEM) [1-3]: key certification, certificate-revocation list (CRL) storage, and CRL retrieval 🔐 [STANDARDS-TRACK]
1423. Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers 💖
Balenson · Feb 93
This one provides definitions, formats, references, and citations for cryptographic algorithms, usage modes, and associated identifiers and parameters used in support of Privacy Enhanced Mail (PEM) in the Internet community 🧁 [STANDARDS-TRACK]
1422. Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management 🦋
Kent · Feb 93
This is one of a series of documents defining privacy enhancement mechanisms for electronic mail sent using Internet mail protocols 🔏 [STANDARDS-TRACK]
1421. Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures 💅
Linn · Feb 93
This document defines message encryption and authentication procedures, so privacy-enhanced mail (PEM) services can work for electronic mail transfer in the Internet 🔐 The whole series starts here, periodt ✨ [STANDARDS-TRACK]
1420. SNMP over IPX 🧚
Bostock · Mar 93
This document defines a convention for wrapping Simple Network Management Protocol (SNMP) [1] packets inside the transport mechanism provided by the Internetwork Packet Exchange (IPX) protocol [2] 📦 [STANDARDS-TRACK]
1419. SNMP over AppleTalk 🌈
Minshall · Mar 93
This memo describes how the Simple Network Management Protocol (SNMP) as specified in [1] can be used over AppleTalk protocols [2], instead of the Internet UDP/IP protocol stack 🍎 [STANDARDS-TRACK]
1418. SNMP over OSI 💜
Rose · Mar 93
This memo addresses some concerns by defining a framework for running SNMP in an environment that supports the OSI connectionless-mode transport service 🌐 [STANDARDS-TRACK]
1417. NADF Standing Documents: A Brief Overview 🍓
N.A.D.F. · Feb 93
The purpose of this one is to give a brief overview of the NADF's Standing Document series 📑 It provides information for the Internet community and does not specify an Internet standard.
1416. Telnet Authentication Option 🔥
Borman · Feb 93
This RFC replaces RFC 1409, which has an important typo in the example on page 6. One "REPLY" should actually be "IS" 🙈 This memo defines an Experimental Protocol for the Internet community.
1415. FTP-FTAM Gateway Specification 🎀
Mindel · Jan 93
This memo describes a dual protocol stack application layer gateway. In an interactive environment, it does protocol translation between the FTP and FTAM file transfer protocols 🔄 [STANDARDS-TRACK]
1414. Identification MIB 🌈
St. Johns · Feb 93
This memo defines a MIB for identifying the users associated with TCP connections 🪪 It gives functionality approximately equivalent to that of the protocol defined in RFC 1413 [1]. [STANDARDS-TRACK]
1413. Identification Protocol 🫶
St. Johns · Feb 93
The Identification Protocol used to be called the Authentication Server Protocol. It got renamed to better reflect what it actually does 🏷️ [STANDARDS-TRACK]
1412. Telnet Authentication: SPX 🌸
Alagappan · Jan 93
This memo defines an Experimental Protocol for the Internet community 🧪
1411. Telnet Authentication: Kerberos Version 4 ✨
Borman · Jan 93
This memo defines an Experimental Protocol for the Internet community 🧪
1410. IAB OFFICIAL PROTOCOL STANDARDS 👑
I.A.B · Mar 93
This memo describes the state of standardization of protocols used in the Internet, as determined by the Internet Architecture Board (IAB) 📋
1409. Telnet Authentication Option 💅
Borman · Jan 93
This memo defines an Experimental Protocol for the Internet community 🧪
1408. Telnet Environment Option 🧚
Borman · Jan 93
This document specifies a mechanism for passing environment information between a telnet client and server 🌿 [STANDARDS-TRACK]
1407. Definitions of Managed Objects for the DS3/E3 Interface Type 🦋
Cox · Jan 93
This memo extends the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. Specifically, it defines objects for managing DS3 and E3 Interfaces 📡 [STANDARDS-TRACK]
1406. Definitions of Managed Objects for the DS1 and E1 Interface Types 💖
Basker · Jan 93
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. It defines objects for managing DS1 Interfaces, including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links 📶 [STANDARDS-TRACK]
1405. Mapping between X.400(1984/1988) and Mail-11 (DECnet mail) 🌈
Allocchio · Jan 93
This document describes a set of mappings that enable interworking between systems running the CCITT X.400 (1984 / 1988) Recommendations on Message Handling Systems and systems running the Mail-11 (also known as DECnet mail) protocol 💌 This memo defines an Experimental Protocol for the Internet community.
1404. A Model for Common Operational Statistics 💜
Stockman · Jan 93
This memo describes a model for operational statistics in the Internet 📊 It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats. It provides information for the Internet community and does not specify an Internet standard.
1403. BGP OSPF Interaction 🔥
Varadhan · Jan 93
This memo defines the various criteria to be used when designing an Autonomous System Border Routers (ASBR) that's gonna run BGP with other
ASBRs external to the AS and OSPF as its IGP. 🎀 [STANDARDS-TRACK]
1402 Martin Jan 93 There's Gold in them thar Networks!
Searching for Treasure in all the Wrong
PlacesOkay, this one is giving treasure hunt 💎. The big goal is to make the route to these sources of info totally invisible to you ✨, and rn that is not easy to do 😭. Martin walks through some techniques to make those nuggets easier to grab so we can all get richer 💰. It's for the Internet community as information only, and it does not specify an Internet standard 🫶.
1401 I.A.B. Jan 93 Correspondence between the IAB and DISA
on the use of DNS throughout the
InternetThis memo is a collection of three letters between the Internet Activities Board (IAB) and the Defense Information Systems Agency (DISA) 📬. They're all about how important it is to use the Domain Name System (DNS) across the whole Internet, and about phasing out the old host name to address tables, like "hosts.txt" 👑. Also informational for the Internet community, and not an Internet standard 🌸.
1400 Williamson Mar 93 Transition and Modernization
of the Internet Registration ServiceOkay, so this one is about a big reshuffle 🦋. Because of the NREN NIS award from the National Science Foundation, non-DDN registration services are about to move from the DDN NIC to the new Internet Registration Service, which is part of something called the InterNIC 🌈. Again, this memo provides information for the Internet community, and it does not specify an Internet standard 💜.
Security Considerations
Security issues are not discussed in this memo. 💀 Yes, really, not one word on it, so don't go assuming it's covered. 🙈
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: rfc1499 1997-01
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms