RFC 1699

Summary of 1600-1699

๐Ÿ“… published January 1997, from ietf

Request for Comments Summary ๐ŸŽ€

RFC 1699 is a summary by J. Elliott at ISI, filed as Informational and dated January 1997. It's called Request for Comments Summary and covers RFC Numbers 1600-1699. The header doesn't say it obsoletes or updates anything ๐Ÿ’….

Status of This Memo โœจ

Okay bestie, this is a slightly annotated list of the 100 RFCs from RFC 1600 through RFCs 1699 ๐Ÿฆ‹. It's a status report on those RFCs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited ๐Ÿ’–.

Note ๐Ÿ“

Lowkey, many RFCs (but not all) are Proposed Standards, Draft Standards, or Standards ๐Ÿซถ. The status can change during standards processing, so here we only point out which ones are on the standards track. For the current state and status of these RFCs, check the latest edition of "Internet Official Protocol Standards" ๐Ÿ“š. Anything on the standards track is marked [STANDARDS-TRACK] in this list.

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

1699    Elliott      Jan 97   Requests For Comments Summary

RFC 1699 ๐Ÿ’œ

1699    Elliott      Jan 97   Requests For Comments Summary

This memo, obviously ๐Ÿ™ˆ. It's the one you're reading right now.

RFC 1698 ๐ŸŒธ

1698    Furniss      Oct 94   Octet Sequences for Upper-Layer OSI
                              to Support Basic Communications
                              Applications

This one spells out particular octet sequences that make up the OSI upper-layer protocols (Session, Presentation and ACSE) when they're used for applications with "basic communications requirements" โœจ. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

RFC 1697 ๐Ÿฆ‹

1697    Brower       Aug 94   Relational Database Management System
                              (RDBMS) Management Information Base
                              (MIB) using SMIv2

This memo defines a portion of the Management Information Base (MIB) for network management protocols in the Internet community ๐Ÿ› ๏ธ. It's all about managed objects for managing relational database (RDBMS) implementations. [STANDARDS-TRACK]

RFC 1696 ๐Ÿ“

1696    Barnes       Aug 94   Modem Management Information Base (MIB)
                              using SMIv2

Another MIB chunk for network management protocols in the Internet community. This one covers managed objects for dial-up modems and similar dial-up devices. [STANDARDS-TRACK]

RFC 1695 ๐Ÿ”ฅ

1695    Ahmed        Aug 94   Definitions of Managed Objects
                              for ATM Management Version 8.0
                              using SMIv2

Also a MIB portion for network management protocols in the Internet community. It describes objects for managing ATM-based interfaces, devices, networks and services ๐Ÿ‘‘. [STANDARDS-TRACK]

RFC 1694 ๐Ÿงš

1694    Brown        Aug 94   Definitions of Managed Objects
                              for SMDS Interfaces using SMIv2

This one defines a portion of the MIB for network management protocols in TCP/IP-based internets. Specifically, it defines objects for managing objects for SMDS access interfaces ๐Ÿ˜ญ. [STANDARDS-TRACK]

RFC 1693 ๐ŸŒˆ

1693    Connolly     Nov 94   An Extension to TCP : Partial Order
                              Service

This RFC introduces a new transport mechanism for TCP based on partial ordering โœจ. The goal is to explain the concepts of partial ordering and get people talking about whether it's useful in network communications. This memo defines an Experimental Protocol for the Internet community ๐Ÿงช.

RFC 1692 ๐Ÿ’…

1692    Cameron      Aug 94   Transport Multiplexing Protocol (TMux)

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. It does not specify an Internet standard.

RFC 1691 ๐ŸŽ€

1691    Turner       Aug 94   The Document Architecture for the
                              Cornell Digital Library

This memo defines an architecture for storing and retrieving the digital versions of books, journals, photographic images, and so on, collected in a large organized digital library ๐Ÿ“–. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1690 โญ

1690    Huston       Aug 94   Introducing the Internet Engineering
                              and Planning Group (IEPG)

This one introduces the IEPG to the Internet community ๐Ÿค. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1689 ๐Ÿฆ‹

1689    Foster       Aug 94   A Status Report on Networked Information
                              Retrieval: Tools and Groups

The point of this report is to make people more aware of Networked Information Retrieval ๐Ÿ”Ž. It pulls together info in one spot about the various networked information retrieval tools, their developers, the organisations involved, and other activities around producing, sharing, and supporting NIR tools. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1688 ๐ŸŒธ

1688    Simpson      Aug 94   IPng Mobility Considerations

This RFC lists criteria related to mobility, to be considered when designing and choosing the Next Generation of IP ๐Ÿš€. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1687 ๐Ÿ“

1687    Fleischman   Aug 94   A Large Corporate User's View of IPng

This paper looks at what IPng means for Fortune 100 corporations. They've invested heavily in TCP/IP to reach their non-computer business goals ๐Ÿ’ผ. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1686 ๐Ÿงš

1686    Vecchi       Aug 94   IPng Requirements: A Cable Television
                              Industry Viewpoint

This paper comments on topics related to IPng requirements and selection criteria, from a cable television industry point of view ๐Ÿ“บ. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1685 ๐Ÿ’œ

1685    Alvestrand   Aug 94   Writing X.400 O/R Names

People who use X.400 systems need a uniform way to write down O/R names, and this memo talks about exactly that โœ๏ธ. This memo provides information for the Internet Community. It does not specify an Internet Standard of any kind.

RFC 1684 ๐ŸŒˆ

1684    Jurg         Aug 94   Introduction to White Pages Services
                              based on X.500

This document introduces the international ITU-T (formerly CCITT) X.500 and ISO 9594 standard ๐ŸŒ. It's especially good for an integrated local and global electronic White Pages Service. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1683 โœจ

1683    Clark        Aug 94   Multiprotocol Interoperability In IPng

This document points out several features that affect how well a protocol can work in a multiprotocol environment ๐Ÿ”ง. It then proposes building these features into IPng. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1682 ๐Ÿ”ฅ

1682    Bound        Aug 94   IPng BSD Host Implementation Analysis

This IPng white paper was sent to the IPng Directorate to give them a BSD host reference point ๐Ÿ–ฅ๏ธ. It was meant to help with engineering considerations during the IETF process of selecting an IPng proposal. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1681 ๐Ÿ‘‘

1681    Bellovin     Aug 94   On Many Addresses per Host

This document was submitted to the IETF IPng area in response to RFC 1550 ๐Ÿ“ฌ. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1680 ๐Ÿซถ

1680    Bradziunas   Aug 94   IPng Support for ATM Services

This white paper describes engineering considerations for IPng, as solicited by RFC 1550 [1] ๐Ÿ“. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1679 ๐Ÿ“

1679    Green        Aug 94   HPN Working Group Input to the IPng
                              Requirements Solicitation

This document shares what the HPN working group sees as requirements for an IPng protocol set ๐Ÿ—ณ๏ธ. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1678 ๐ŸŒธ

1678    Britton      Aug 94   IPng Requirements of Large Corporate
                              Networks

This draft summarizes some of the requirements large corporate networks have for the next generation of the Internet protocol suite ๐Ÿข. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1677 ๐ŸŽ€

1677    Adamson      Aug 94   Tactical Radio Frequency Communication
                              Requirments for IPng

This paper describes requirements for IPng candidates, specifically for their use in military tactical radio frequency (RF) communication networks ๐ŸŽ–๏ธ. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1676 ๐Ÿงš

1676    Ghiselli     Aug 94   INFN Requirements for an IPng

This paper is about the key points the authors would want to consider if they were put in charge of an IPng plan ๐Ÿงญ. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1675 ๐Ÿšจ

1675    Bellovin     Aug 94   Security Concerns for IPng

Okay, this one is serious bestie ๐Ÿ˜ฌ. A number of the IPng candidates have features that are somewhat worrisome from a security perspective. IPng doesn't have to be an improvement over IPv4, but it is mandatory that it not make things worse ๐Ÿ”’. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1674 ๐Ÿ’œ

1674    Taylor       Aug 94   A Cellular Industry View of IPng

This is a draft of the IPng requirements as seen by representatives of the Cellular Digital Packet Data (CDPD) consortium of service providers ๐Ÿ“ฑ. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1673 ๐ŸŒˆ

1673    Skelton      Aug 94   Electric Power Research Institute
                              Comments on IPng

This document was submitted to the IETF IPng area in response to RFC 1550 โšก. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1672 ๐Ÿ“

1672    Brownless    Aug 94   Accounting Requirements for IPng

This white paper discusses accounting requirements for IPng ๐Ÿงพ. It recommends that all IPng packets carry accounting tags, which would vary in size. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1671 โœจ

1671    Carpenter    Aug 94   IPng White Paper on Transition and Other
                              Considerations

This white paper outlines some general requirements for IPng in selected areas ๐Ÿ—บ๏ธ. This memo provides information for the Internet community and does not specify an Internet standard of any kind.

RFC 1670 ๐Ÿฆ‹

1670    Heagerty     Aug 94   Input to IPng Engineering Considerations

This white paper expresses some personal opinions on IPng engineering

considerations, based on experience with DECnet Phase V transition ๐Ÿ’… It basically breaks the IPng decisions and transition tasks into smaller, bite-sized pieces so the right experts can grab them early โœจ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1669    Curran       Aug 94   Market Viability as a IPng Criteria

"Viability in the Marketplace" is a huge deal for any IPng candidate ๐Ÿ’ฐโœจ This paper tries to sum up the key factors for figuring out whether IPng proposals are actually market viable, no cap ๐Ÿซถ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1668    Estrin       Aug 94   Unified Routing Requirements for IPng

This one lays out IPng requirements from the point of view of the Unified Routing Architecture, the one described in RFC 1322 ๐Ÿฆ‹ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1667    Symington    Aug 94   Modeling and Simulation Requirements for
                              IPng

This white paper gives a recap of the Distributed Interactive Simulation environment, which is still under development ๐Ÿ› ๏ธ It looks at how real-time it is, plus its scope and how big its networking needs are ๐ŸŒˆ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1666    Kielczewski  Aug 94   Definitions of Managed Objects
                              for SNA NAUs using SMIv2

Okay so this memo defines a chunk of the Management Information Base (MIB) for network management protocols in the Internet community ๐Ÿ’œ Specifically, it defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. [STANDARDS-TRACK]

1665    Kielczewski  Jul 94   Definitions of Managed Objects
                              for SNA NAUs using SMIv2

Same energy as the one above, just from July ๐ŸŒธ This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. It defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. [STANDARDS-TRACK]

1664    Allocchio    Aug 94   Using the Internet DNS to Distribute
                              RFC1327 Mail Address Mapping Tables

This memo explains how to store, in the Internet Domain Name System, the mapping info that e-mail gateways and other tools need to turn RFC822 domain names into X.400 O/R names and back again ๐Ÿ“ This memo defines an Experimental Protocol for the Internet community.

1663    Rand         Jul 94   PPP Reliable Transmission

This document defines a way to negotiate and use Numbered-Mode, as defined by ISO 7776 [2], so you get a reliable serial link ๐Ÿ”ฅ [STANDARDS-TRACK]

1662    Simpson      Jul 94   PPP in HDLC-Like Framing

This document describes how to use HDLC-like framing for PPP encapsulated packets ๐Ÿ“ฆ [STANDARDS-TRACK]

1661    Simpson      Jul 94   The Ponit-to-Point Protocol (PPP)

This document defines the PPP organization and methodology, plus the PPP encapsulation, together with an extensible option negotiation mechanism ๐ŸŽ€ That mechanism can negotiate a rich assortment of configuration parameters and also provides additional management functions. (Yes, the title really says "Ponit" in the index, typo and all ๐Ÿ™ˆ) [STANDARDS-TRACK]

1660    Stewart      Jul 94   Definitions of Managed Objects for
                              Parallel-printer-like Hardware Devices
                              using SMIv2

This memo extends the Management Information Base (MIB) for use with network management protocols in the Internet community ๐Ÿ–จ๏ธ Specifically, it defines objects for managing Parallel-printer-like devices. [STANDARDS-TRACK]

1659    Stewart      Jul 94   Definitions of Managed Objects for
                              RS-232-like Hardware Devices using SMIv2

Another MIB extension for network management protocols in the Internet community ๐Ÿงš This one defines objects for managing RS-232-like devices. [STANDARDS-TRACK]

1658    Stewart      Jul 94   Definitions of Managed Objects for
                              Character Stream Devices using SMIv2

Yep, another MIB extension for network management protocols in the Internet community ๐Ÿ’… This one defines objects for managing character stream devices. [STANDARDS-TRACK]


1657    Willis       Jul 94   Definitions of Managed Objects for the
                              Fourth Version of the Border Gateway
                              Protocol (BGP-4) using SMIv2

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community โœจ In particular, it describes managed objects used for managing the Border Gateway Protocol Version 4 or lower [1, 2]. [STANDARDS-TRACK]

1656    Traina       Jul 94   BGP-4 Protocol Document Roadmap and
                              Implementation Experience

Okay so Border Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous System routing protocol ๐ŸŒ It's built on the experience gained with BGP as defined in RFC-1267 [2], plus BGP usage in the connected Internet as described in RFC-1268 [3] ๐Ÿ’œ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1655    Rekhter      Jul 94   Application of the Border Gateway
                              Protocol in the Internet

This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", defines an inter-autonomous system routing protocol for the Internet ๐Ÿซถ [STANDARDS-TRACK]

1654    Rekhter      Jul 94   A Border Gateway Protocol 4 (BGP-4)

This document defines an inter-autonomous system routing protocol for the Internet ๐Ÿ‘‘ [STANDARDS-TRACK]

1653    Klensin      Jul 94   SMTP Service Extension for Message Size
                              Declaration

This memo defines an SMTP service extension where an SMTP client and server can chat so the server gets a chance to decline a message (maybe temporarily) based on the client's estimate of the message size ๐Ÿ“ฌ [STANDARDS-TRACK]

1652    Klensin      Jul 94   SMTP Service Extension for
                              8bit-MIMEtransport

This memo defines an SMTP service extension for relaying a content body made of text with octets outside the US-ASCII octet range (hex 00-7F) using SMTP ๐ŸŒˆ [STANDARDS-TRACK]

1651    Klensin      Jul 94   SMTP Service Extensions

This memo gives a framework for extending the SMTP service. It lets a server SMTP tell a client SMTP which service extensions it supports ๐Ÿฆ‹ [STANDARDS-TRACK]

1650    Kastenholz   Aug 94   Definitions of Managed Objects for the
                              Ethernet-like Interface Types using
                              SMIv2

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community ๐Ÿ”Œ It defines objects for managing ethernet-like objects. [STANDARDS-TRACK]

1649    Hagens       Jul 94   Operational Requirements for X.400
                              Management Domains in the GO-MHS
                              Community

The goal here is to unite regionally operated X.400 services on the various continents into one GO-MHS Community, as seen from an end-user's point of view ๐ŸŒโœจ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1648    Cargille     Jul 94   Postmaster Convention for X.400
                              Operations

This paper takes the idea further and applies it to X.400 mail domains that have registered RFC 1327 mapping rules, so they appear to have normal RFC822-style addresses ๐Ÿ’Œ [STANDARDS-TRACK]

1647    Kelly        Jul 94   TN3270 Enhancements

This document describes a protocol that supports 3270 devices more fully than the existing tn3270 practices do ๐Ÿ–ฅ๏ธ๐Ÿ’– [STANDARDS-TRACK]

1646    Graves       Jul 94   TN3270 Extensions for LUname and
                              Printer Selection

This document describes protocol extensions to TN3270 ๐ŸŒธ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1645    Gwinn        Jul 94   Simple Network Paging Protocol -
                              Version 2

This RFC suggests a simple way to deliver both alphanumeric and numeric pages (one-way) to radio paging terminals ๐Ÿ“Ÿ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1644    Braden       Jul 94   T/TCP -- TCP Extensions for Transactions
                              Functional Specification

This memo specifies T/TCP, an experimental TCP extension for efficient transaction-oriented (request/response) service โšก This memo describes an Experimental Protocol for the Internet community.

1643    Kastenholz   Jul 94   Definitions of Managed Objects for the
                              Ethernet-like Interface Types

Okay this one is a portion of the MIB for network management protocols in the Internet community ๐Ÿงฉ It defines objects for managing ethernet-like objects. [STANDARDS-TRACK]

1642    Goldsmith    Jul 94   A Mail-Safe Transformation Format of
                              Unicode

This document describes a new transformation format of Unicode that contains only 7-bit ASCII characters ๐Ÿ”ค It's meant to be readable by humans in the limiting case where the document is made up of characters from the US-ASCII repertoire ๐Ÿ™Œ This memo defines an Experimental Protocol for the Internet community.

1641    Goldsmith    Jul 94   Using Unicode with MIME

This document specifies how to use Unicode within MIME ๐ŸŒˆ This memo defines an Experimental Protocol for the Internet community.

1640    Crocker      Jun 94   The Process for Organization of Internet
                              Standards Working Group (POISED)

This report was originally prepared in January 1993 and summarizes the POISED WG, from the events that led to forming the WG up to the end of 1992 ๐Ÿ“œ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

1639    Piscitello   Jun 94   FTP Operation Over Big Address Records
                              (FOOBAR)

This RFC specifies a way to assign addresses other than 32-bit IPv4 addresses to data ports, using a "long Port (LPRT)" command and a "Long Passive (LPSV)" reply ๐Ÿฆ‹ Each one takes a <long-host-port> as its argument, which allows for extra address families, variable length network addresses and variable length port numbers ๐Ÿ’– This memo defines an Experimental Protocol for the Internet community.

1638    Baker        Jun 94   PPP Bridging Control Protocol (BCP)

This document defines the Network Control Protocol for setting up and configuring Remote Bridging for PPP links ๐ŸŒ‰ [STANDARDS-TRACK]

1637    Manning      Jun 94   DNS NSAP Resource Records

This document defines the format of one new Resource Record (RR) for the DNS, used for mapping domain names to NSAPs ๐Ÿงญ This memo defines an Experimental Protocol for the Internet community.

1636    Braden       Jun 94   Report of IAB Workshop on Security in
                              the Internet Architecture

This document is a report on an Internet architecture workshop ๐Ÿ” The IAB started it, and it was held at USC Information Sciences Institute on February 8-10, 1994 โœจ This workshop generally focused on security issues

...in the Internet architecture ๐Ÿฆ‹ okay so this one is just info for the Internet community, and it's not an Internet standard of any kind ๐Ÿ’…


1635 ยท Deutsch ยท May 94 ยท How to Use Anonymous FTP ๐ŸŒธ

This doc is a cute beginner's guide for novice Internet users who want to try the File Transfer Protocol (FTP) ๐Ÿ“ It explains what FTP is, what anonymous FTP is, and what an anonymous FTP archive site is โœจ It's info for the Internet community, not a standard, bestie ๐Ÿซถ


1634 ยท Allen ยท May 94 ยท Novell IPX Over Various WAN Media (IPXWAN) ๐ŸŒˆ

Okay this one is giving WAN realness ๐Ÿ’œ It describes how Novell IPX runs over different WAN media โœจ Specifically, it's about the common "IPX WAN" protocol Novell uses so routers can swap the info they need to know about each other before they start trading standard IPX routing info and traffic over WAN datalinks ๐Ÿ”ฅ It's info for the Internet community. It is not an Internet standard of any kind ๐ŸŽ€


1633 ยท Braden ยท Jun 94 ยท Integrated Services in the Internet Architecture: an Overview ๐Ÿงš

This memo is giving big proposed-extension energy ๐Ÿ’… It talks about extending the Internet architecture and protocols to provide integrated services, which means supporting real-time traffic as well as the regular non-real-time service IP already does ๐Ÿ˜ญ It's info for the Internet community and not an Internet standard of any kind, periodt ๐Ÿ’–


1632 ยท Getchell ยท May 94 ยท A Revised Catalog of Available X.500 Implementations ๐Ÿ“š

This doc is the result of a survey collecting new or updated descriptions of the X.500 implementations that are out there right now, both commercial products and openly available offerings ๐Ÿ“ It's a revision of RFC 1292 โœจ Info for the Internet community. Not an Internet standard of any kind ๐Ÿ’œ


1631 ยท Egevang ยท May 94 ยท The IP Network Address Translator (NAT) ๐Ÿฆ‹

Okay so this memo proposes another short-term fix called address reuse ๐Ÿ’ซ It complements CIDR, or even makes it unnecessary, iykyk ๐Ÿ™ˆ The trick is to place Network Address Translators (NAT) at the borders of stub domains โœจ It's info for the Internet community, not an Internet standard of any kind, bestie ๐ŸŒธ


1630 ยท Berners-Lee ยท Jun 94 ยท Universal Resource Identifiers in WWW ๐Ÿ•ธ๏ธ

This document defines the syntax the World-Wide Web initiative uses to encode the names and addresses of objects on the Internet ๐Ÿ’… Main character energy ๐Ÿ‘‘ It's info for the Internet community. It's not an Internet standard of any kind ๐ŸŽ€


1629 ยท Colella ยท May 94 ยท Guidelines for OSI NSAP Allocation in the Internet ๐Ÿ”ฅ

This paper gives guidelines for allocating NSAP addresses in the Internet, and ngl they were the basis for the first deployment of CLNP in the Internet ๐Ÿ˜ญ They've been super valuable for scaling CLNP routing and for address administration โœจ [STANDARDS-TRACK]


1628 ยท Case ยท May 94 ยท UPS Management Information Base ๐Ÿ”‹

This memo defines a chunk of the Management Information Base (MIB) for network management protocols in the Internet community โญ Specifically, it defines objects for managing uninterruptible power supply (UPS) systems ๐Ÿ’– [STANDARDS-TRACK]


1627 ยท Lear ยท Jul 94 ยท Network 10 Considered Harmful (Some Practices Shouldn't be Codified) ๐Ÿ’€

This doc restates the arguments for keeping a unique address space ๐Ÿซถ It explores concerns for Internet architecture and operations, plus IETF procedure โœจ Info for the Internet community. Not an Internet standard of any kind, iykyk ๐ŸŒˆ


1626 ยท Atkinson ยท May 94 ยท Default IP MTU for use over ATM AAL5 ๐Ÿงš

There are a bunch of good reasons to have a reasonably large default MTU value for IP over ATM AAL5, and this paper presents the default IP MIU for use over ATM AAL5 ๐Ÿ’… [STANDARDS-TRACK]


1625 ยท St. Pierre ยท Jun 94 ยท WAIS over Z39.50-1988 ๐Ÿ“–

The purpose of this memo is to kick off a discussion about a migration path for WAIS technology ๐ŸŒท It moves from Z39.50-1988 Information Retrieval Service Definitions and Protocol Specification for Library Applications [1] to Z39.50-1992 [2], and then on to Z39.50-1994 [3] ๐Ÿ’œ Info for the Internet community, not an Internet standard of any kind ๐ŸŽ€


1624 ยท Rijsinghani ยท May 94 ยท Computation of the Internet Checksum via Incremental Update ๐Ÿงฎ

This memo describes an updated technique for incremental computation of the standard Internet checksum ๐Ÿ’ซ It updates the method described in RFC 1141 โœจ Info for the Internet community. It does not specify an Internet standard of any kind ๐ŸŒธ


1623 ยท Kastenholz ยท May 94 ยท Definitions of Managed Objects for the Ethernet-like Interface Types ๐Ÿ”Œ

This memo defines another portion of the MIB for network management protocols in the Internet community ๐Ÿ“ In particular, it defines objects for managing ethernet-like objects ๐Ÿซถ [STANDARDS-TRACK]


1622 ยท Francis ยท May 94 ยท Pip Header Processing ๐ŸŒŠ

The purpose of this RFC and its companion RFC, "Pip Near-term Architecture," is to record the ideas of Pip, the good and the bad ๐Ÿ™ˆ Info for the Internet community. Not an Internet standard of any kind, bestie ๐Ÿ’…


1621 ยท Francis ยท May 94 ยท Pip Near-term Architecture ๐ŸŒŠ

Same energy as 1622 ๐Ÿฆ‹ The purpose of this RFC and its companion RFC, "Pip Header Processing," is to record the ideas (good and bad) of Pip โœจ Info for the Internet community. It does not specify an Internet standard of any kind ๐Ÿ’œ


1620 ยท Braden ยท May 94 ยท Internet Architecture Extensions for Shared Media ๐ŸŒ

This memo talks through alternative approaches to extending the Internet architecture so that some or all unnecessary hops get eliminated ๐Ÿ”ฅ Info for the Internet community. Not an Internet standard of any kind, periodt ๐ŸŽ€


1619 ยท Simpson ยท May 94 ยท PPP over SONET/SDH โšก

This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Heirarchy (SDH) circuits ๐Ÿ’– [STANDARDS-TRACK]


1618 ยท Simpson ยท May 94 ยท PPP over ISDN ๐Ÿ“ž

This document describes the use of PPP over Integrated Services Digital Network (ISDN) switched circuits โœจ [STANDARDS-TRACK]


1617 ยท Barker ยท May 94 ยท Naming and Structuring Guidelines for X.500 Directory Pilots ๐Ÿ—‚๏ธ

This doc defines a bunch of naming and structuring guidelines focused on White Pages usage ๐Ÿ’… Alignment to these guidelines is recommended for directory pilots ๐Ÿซถ Info for the Internet community. It does not specify an Internet standard of any kind, iykyk ๐ŸŒˆ


1616 ยท RARE WG-MSG ยท May 94 ยท A report by the RARE Task Force on X.400(1988) of the RARE Working Group on Mail & Messaging ๐Ÿ“ฌ

This report documents the results of a task force on X.400(1988) deployment from the RARE Mails and Messaging Work Group, covering November 1992 until October 1993 ๐ŸŒธ Info for the Internet community, not an Internet standard of any kind ๐Ÿ’œ


1615 ยท Houttuin ยท May 94 ยท Migrating from X.400(84) to X.400(88) ๐Ÿงณ

This document compares X.400(88) to X.400(84) and describes what problems can be anticipated in the migration ๐Ÿ™ˆ It's especially about moving from the existing X.400(84) infrastructure created by the COSINE MHS project to an X.400(88) infrastructure ๐Ÿ˜ญ Info for the Internet community. Not an Internet standard of any kind, bestie ๐ŸŽ€


1614 ยท Adie ยท May 94 ยท Network Access to Multimedia Information ๐ŸŽฌ

This report summarises what research and academic network users need when it comes to network access to multimedia information ๐Ÿ“ Info for the Internet community. It does not specify an Internet standard of any kind โœจ


1613 ยท Foster ยท May 94 ยท cisco Systems X.25 over TCP (XOT) ๐Ÿ”

This memo documents a method of sending X.25 packets over IP internets by encapsulating the X.25 Packet Level in TCP packets ๐Ÿซถ Info for the Internet community. Not an Internet standard of any kind ๐Ÿ’…


1612 ยท Austein ยท May 94 ยท DNS Resolver MIB Extensions ๐Ÿงญ

This memo defines a portion of the MIB for network management protocols in the Internet community ๐Ÿ’– It describes a set of extensions that instrument DNS resolver functions, and it was produced by the DNS working group ๐ŸŒท [STANDARDS-TRACK]


1611 ยท Austein ยท May 94 ยท DNS Server MIB Extensions ๐Ÿงญ

Same squad as 1612 ๐Ÿฆ‹ This memo defines a portion of the MIB for network management protocols in the Internet community, and it describes extensions that instrument DNS name server functions ๐Ÿ’ซ It was produced by the DNS working group ๐ŸŒธ [STANDARDS-TRACK]


1610 ยท I.A.B ยท Jul 94 ยท INTERNET OFFICIAL PROTOCOL STANDARDS ๐Ÿ›๏ธ

This memo describes the state of standardization of protocols used in the Internet, as determined by the Internet Architecture Board (IAB) ๐Ÿ‘‘ It's literally the official roll call ๐Ÿ˜ญ [STANDARDS-TRACK]


1609 ยท Mansfield ยท Mar 94 ยท Charting Networks in the X.500 Directory ๐Ÿ—บ๏ธ

This document presents a model where a communication network, with all its related details and descriptions, can be represented in the X.500 Directory โœจ This memo defines an Experimental Protocol for the Internet community ๐Ÿงช


1608 ยท Johannsen ยท Mar 94 ยท Representing IP Information in the X.500 Directory ๐ŸŒ

This document describes the objects needed to include information about IP networks and IP numbers in the X.500 Directory ๐Ÿ’… It extends the work "Charting networks in the X.500 Directory" [1], which presents a general framework for representing networks in the Directory, by applying it to IP networks ๐Ÿซถ This memo defines an Experimental Protocol for the Internet community ๐Ÿงช


1607 ยท Cerf ยท Apr 94 ยท A VIEW FROM THE 21ST CENTURY ๐Ÿ”ฎ

This document is a composition of letters discussing a possible future ๐Ÿงš Info for the Internet community. It does not specify an Internet standard of any kind ๐Ÿ’œ


1606 ยท Onion ยท Apr 94 ยท A Historical Perspective On The Usage Of IP Version 9 ๐Ÿ•ฐ๏ธ

This paper reviews the usages of the old IP version protocol, looking at some of its successes and its failures ๐Ÿ’€ Info for the Internet community. Not an Internet standard of any kind ๐ŸŒธ


1605 ยท Shakespeare ยท Apr 94 ยท SONET to Sonnet Translation ๐ŸŽญ

Because SONET transmits data in frames of bytes, it's pretty easy to imagine ways to compress SONET frames for higher bandwidth over a given fiber optic link ๐ŸŒŠ This memo describes one particular method, SONET Over Novel English Translation (SONNET) ๐Ÿ“œ Info for the Internet community. It does not specify an Internet standard of any kind ๐ŸŽ€


1604 ยท Brown ยท Mar 94 ยท Definitions of Managed Objects for Frame Relay Service ๐Ÿ“ก

This memo defines an extension to the MIB for network management protocols in TCP/IP-based internets ๐Ÿซถ In particular, it defines objects for managing the Frame Relay Service ๐Ÿ’– [STANDARDS-TRACK]


1603 ยท Huizer ยท Mar 94 ยท IETF Working Group Guidelines and Procedures ๐Ÿ“‹

This document describes the guidelines and procedures for formation and

operation of IETF working groups, bestie ๐Ÿซถ This one is all about the formal relationship between IETF participants WG and the Internet Engineering Steering Group (IESG) ๐Ÿ’… It's basically the official rules for how the two sides work together โœจ This memo is just information for the Internet community ๐ŸŒธ It does not specify an Internet standard of any kind ๐Ÿซง


Next up is the Internet Standards Process, Revision 2 ๐Ÿ“œ

1602    I.A.B.       Mar 94   The Internet Standards Process --
                              Revision 2

This one is a revision of RFC 1310, which laid out the official procedures for creating and documenting Internet Standards ๐Ÿฆ‹ So if you're wondering how standards actually get made, this is the glow-up version ๐Ÿ’– This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind ๐ŸŒˆ


Now for the Internet Architecture Board charter ๐ŸŽ€

1601    Huitema      Mar 94   Charter of the Internet Architecture
                              Board (IAB)

This memo documents the composition, selection, roles, and organization of the Internet Architecture Board and its subsidiary organizations ๐Ÿงš It's the full who's-who and who-does-what breakdown ๐Ÿ‘‘ This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind โœจ


And finally, the big list of official protocol standards ๐Ÿ”ฅ

1600    I.A.B.       Mar 94   INTERNET OFFICIAL PROTOCOL STANDARDS

This memo describes the state of standardization of protocols used in the Internet, as determined by the Internet Architecture Board (IAB) ๐Ÿ’œ It's giving "here's where everything stands right now" energy ๐Ÿ“ [STANDARDS-TRACK]


Security Considerations ๐Ÿ’€

Security issues are not discussed in this memo. ๐Ÿ˜ญ Not one word on it, so no security content lives in this document ๐Ÿ”’

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