As per Relevance of the word management, we have this rfc below:
Network Working Group J.
Request for Comments: 1699
Category: Informational January 1997
Request for Comments
RFC Numbers 1600-1699
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 1600
through RFCs 1699. This is a status report on these RFCs. This
provides information for the Internet community. It does not
an Internet standard of any kind. Distribution of this memo
unlimited
Many RFCs, but not all, are Proposed Standards, Draft Standards,
Standards. Since the status of these RFCs may change during
standards processing, we note here only that they are on
standards track. Please see the latest edition of "Internet
Protocol Standards" for the current state and status of these RFCs
In the following, RFCs on the standards track are marked [STANDARDS
TRACK].
RFC Author Date
--- ------ ---- -----
1699 Elliott Jan 97 Requests For Comments
This memo
1698 Furniss Oct 94 Octet Sequences for Upper-Layer
to Support Basic
This document states particular octet sequences that comprise the
upper-layer protocols (Session, Presentation and ACSE) when used
support applications with "basic communications requirements".
memo provides information for the Internet community. This memo
not specify an Internet standard of any kind
Elliott Informational [Page 1]
RFC 1699 Summary of 1600-1699 January 1997
1697 Brower Aug 94 Relational Database Management
(RDBMS) Management Information
(MIB) using SMIv
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it describes managed objects used for managing
database (RDBMS) implementations. [STANDARDS-TRACK
1696 Barnes Aug 94 Modem Management Information Base (MIB
using SMIv
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it describes managed objects used for managing dial-
modems and similar dial-up devices. [STANDARDS-TRACK
1695 Ahmed Aug 94 Definitions of Managed
for ATM Management Version 8.0
using SMIv
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it describes objects used for managing ATM-based interfaces
devices, networks and services. [STANDARDS-TRACK
1694 Brown Aug 94 Definitions of Managed
for SMDS Interfaces using SMIv
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it defines objects for managing objects for SMDS
interfaces. [STANDARDS-TRACK
1693 Connolly Nov 94 An Extension to TCP : Partial
This RFC introduces a new transport mechanism for TCP based upon
ordering. The aim is to present the concepts of partial ordering
promote discussions on its usefulness in network communications.
memo defines an Experimental Protocol for the Internet community
Elliott Informational [Page 2]
RFC 1699 Summary of 1600-1699 January 1997
1692 Cameron Aug 94 Transport Multiplexing Protocol (TMux
This RFC documents the extended TACACS protocol use by the Cisco
terminal servers. This same protocol is used by the University
Minnesota's distributed authentication system. This memo
information for the Internet community. It does not specify an
standard
1691 Turner Aug 94 The Document Architecture for
Cornell Digital
This memo defines an architecture for the storage and retrieval of
digital representations for books, journals, photographic images, etc.,
which are collected in a large organized digital library. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1690 Huston Aug 94 Introducing the Internet
and Planning Group (IEPG
This memo introduces the IEPG to the Internet Community. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1689 Foster Aug 94 A Status Report on Networked
Retrieval: Tools and
The purpose of this report is to increase the awareness of
Information Retrieval by bringing together in one place
about the various networked information retrieval tools,
developers, interested organisations, and other activities that
to the production, dissemination, and support of NIR tools. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1688 Simpson Aug 94 IPng Mobility
This RFC specifies criteria related to mobility for consideration
design and selection of the Next Generation of IP. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
Elliott Informational [Page 3]
RFC 1699 Summary of 1600-1699 January 1997
1687 Fleischman Aug 94 A Large Corporate User's View of
The goal of this paper is to examine the implications of IPng from
point of view of Fortune 100 corporations which have heavily invested
TCP/IP technology in order to achieve their (non-computer related
business goals.This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1686 Vecchi Aug 94 IPng Requirements: A Cable
Industry
This paper provides comments on topics related to the IPng
and selection criteria from a cable television industry viewpoint.
memo provides information for the Internet community. This memo
not specify an Internet standard of any kind
1685 Alvestrand Aug 94 Writing X.400 O/R
There is a need for human beings who use X.400 systems to be able
write down O/R names in a uniform way. This memo is a discussion
this topic. This memo provides information for the Internet Community
It does not specify an Internet Standard of any kind
1684 Jurg Aug 94 Introduction to White Pages
based on X.500
The document provides an introduction to the international ITU-
(formerly CCITT) X.500 and ISO 9594 standard, which is
suited for providing an integrated local and global electronic
Pages Service. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1683 Clark Aug 94 Multiprotocol Interoperability In
In this document, we identify several features that affect a protocol'
ability to operate in a multiprotocol environment and propose
incorporation of these features into IPng. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
Elliott Informational [Page 4]
RFC 1699 Summary of 1600-1699 January 1997
1682 Bound Aug 94 IPng BSD Host Implementation
This IPng white paper, IPng BSD Host Implementation Analysis,
submitted to the IPng Directorate to provide a BSD host point
reference to assist with the engineering considerations during the
process to select an IPng proposal. This memo provides information
the Internet community. This memo does not specify an Internet
of any kind
1681 Bellovin Aug 94 On Many Addresses per
This document was submitted to the IETF IPng area in response to
1550.This memo provides information for the Internet community.
memo does not specify an Internet standard of any kind
1680 Bradziunas Aug 94 IPng Support for ATM
This white paper describes engineering considerations for IPng
solicited by RFC 1550 [1]. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
1679 Green Aug 94 HPN Working Group Input to the
Requirements
The purpose of this document is to provide what the HPN working
perceives as requirements for an IPng protocol set. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1678 Britton Aug 94 IPng Requirements of Large
This draft summarizes some of the requirements of large
networks for the next generation of the Internet protcol suite.
memo provides information for the Internet community. This memo
not specify an Internet standard of any kind
Elliott Informational [Page 5]
RFC 1699 Summary of 1600-1699 January 1997
1677 Adamson Aug 94 Tactical Radio Frequency
Requirments for
This paper describes requirements for Internet Protocol next
(IPng) candidates with respect to their application to military
radio frequency (RF) communication networks. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1676 Ghiselli Aug 94 INFN Requirements for an
With this paper we would like to emphasize the key points that we
to consider if charged with IPng plan. This memo provides
for the Internet community. This memo does not specify an
standard of any kind
1675 Bellovin Aug 94 Security Concerns for
A number of the candidates for IPng have some features that are
worrisome from a security perspective. While it is not necessary
IPng be an improvement over IPv4, it is mandatory that it not
things worse. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1674 Taylor Aug 94 A Cellular Industry View of
This is a draft of the requirements for IPng as envisioned
representatives of the Cellular Digital Packet Data (CDPD) consortium
service providers. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1673 Skelton Aug 94 Electric Power Research
Comments on
This document was submitted to the IETF IPng area in response to
1550. This memo provides information for the Internet community.
memo does not specify an Internet standard of any kind
Elliott Informational [Page 6]
RFC 1699 Summary of 1600-1699 January 1997
1672 Brownless Aug 94 Accounting Requirements for
This white paper discusses accounting requirements for IPng.
recommends that all IPng packets carry accounting tags, which would
in size. This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1671 Carpenter Aug 94 IPng White Paper on Transition and
This white paper outlines some general requirements for IPng in
areas. This memo provides information for the Internet community.
memo does not specify an Internet standard of any kind
1670 Heagerty Aug 94 Input to IPng Engineering
This white paper expresses some personal opinions on IPng
considerations, based on experience with DECnet Phase V transition.
suggests breaking down the IPng decisions and transition tasks
smaller parts so they can be tackled early by the relevant experts
This memo provides information for the Internet community. This
does not specify an Internet standard of any kind
1669 Curran Aug 94 Market Viability as a IPng
"Viability in the Marketplace" is an important requirement for any
candidate and this paper is an attempt to summarize some
factors in determing market viability of IPng proposals. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1668 Estrin Aug 94 Unified Routing Requirements for
The document provides requirements on the IPng from the perspective
the Unified Routing Architecture, as described in RFC 1322. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
Elliott Informational [Page 7]
RFC 1699 Summary of 1600-1699 January 1997
1667 Symington Aug 94 Modeling and Simulation Requirements
This white paper summarizes the Distributed Interactive
environment that is under development, with regard to its real-
nature, scope and magnitude of networking requirements. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1666 Kielczewski Aug 94 Definitions of Managed
for SNA NAUs using SMIv
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, 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
for SNA NAUs using SMIv
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, 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
RFC1327 Mail Address Mapping
This memo defines how to store in the Internet Domain Name System
mapping information needed by e-mail gateways and other tools to
RFC822 domain names into X.400 O/R names and vice versa. This
defines an Experimental Protocol for the Internet community
1663 Rand Jul 94 PPP Reliable
This document defines a method for negotiating and using Numbered-Mode
as defined by ISO 7776 [2], to provide a reliable serial link
[STANDARDS-TRACK
Elliott Informational [Page 8]
RFC 1699 Summary of 1600-1699 January 1997
1662 Simpson Jul 94 PPP in HDLC-Like
This document describes the use of HDLC-like framing for
encapsulated packets. [STANDARDS-TRACK
1661 Simpson Jul 94 The Ponit-to-Point Protocol (PPP
This document defines the PPP organization and methodology, and the
encapsulation, together with an extensible option negotiation
which is able to negotiate a rich assortment of configuration
and provides additional management functions. [STANDARDS-TRACK
1660 Stewart Jul 94 Definitions of Managed Objects
Parallel-printer-like Hardware
using SMIv
This memo defines an extension to the Management Information Base (MIB
for use with network management protocols in the Internet community.
particular, it defines objects for the management of Parallel-printer
like devices. [STANDARDS-TRACK
1659 Stewart Jul 94 Definitions of Managed Objects
RS-232-like Hardware Devices using SMIv
This memo defines an extension to the Management Information Base (MIB
for use with network management protocols in the Internet community.
particular, it defines objects for the management of RS-232-
devices. [STANDARDS-TRACK
1658 Stewart Jul 94 Definitions of Managed Objects
Character Stream Devices using SMIv
This memo defines an extension to the Management Information Base (MIB
for use with network management protocols in the Internet community.
particular, it defines objects for the management of character
devices. [STANDARDS-TRACK
Elliott Informational [Page 9]
RFC 1699 Summary of 1600-1699 January 1997
1657 Willis Jul 94 Definitions of Managed Objects for
Fourth Version of the Border
Protocol (BGP-4) using SMIv
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it describes managed objects used for managing the
Gateway Protocol Version 4 or lower [1, 2]. [STANDARDS-TRACK
1656 Traina Jul 94 BGP-4 Protocol Document Roadmap
Implementation
Border Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous
routing protocol. It is built on experience gained with BGP as
in RFC-1267 [2] and BGP usage in the connected Internet as described
RFC-1268 [3]. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1655 Rekhter Jul 94 Application of the Border
Protocol in the
This document, together with its companion document, "A Border
Protocol 4 (BGP-4)", define an inter-autonomous system routing
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
the Internet. [STANDARDS-TRACK
1653 Klensin Jul 94 SMTP Service Extension for Message
This memo defines an extension to the SMTP service whereby an
client and server may interact to give the server an opportunity
decline to accept a message (perhaps temporarily) based on the client'
estimate of the message size. [STANDARDS-TRACK
Elliott Informational [Page 10]
RFC 1699 Summary of 1600-1699 January 1997
1652 Klensin Jul 94 SMTP Service Extension
8bit-
This memo defines an extension to the SMTP service whereby an
content body consisting of text containing octets outside of the US
ASCII octet range (hex 00-7F) may be relayed using SMTP. [STANDARDS
TRACK
1651 Klensin Jul 94 SMTP Service
This memo defines a framework for extending the SMTP service by
a means whereby a server SMTP can inform a client SMTP as to the
extensions it supports. [STANDARDS-TRACK
1650 Kastenholz Aug 94 Definitions of Managed Objects for
Ethernet-like Interface Types
SMIv
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it defines objects for managing ethernet-like objects
[STANDARDS-TRACK
1649 Hagens Jul 94 Operational Requirements for X.400
Management Domains in the GO-
The goal of this document is to unite regionally operated X.400
on the various continents into one GO-MHS Community (as seen from
end-user's point of view). This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
1648 Cargille Jul 94 Postmaster Convention for X.400
This paper extends this concept to X.400 mail domains which
registered RFC 1327 mapping rules, and which therefore appear to
normal RFC822-style addresses. [STANDARDS-TRACK
Elliott Informational [Page 11]
RFC 1699 Summary of 1600-1699 January 1997
1647 Kelly Jul 94 TN3270
This document describes a protocol that more fully supports 3270
than do the existing tn3270 practices. [STANDARDS-TRACK
1646 Graves Jul 94 TN3270 Extensions for LUname
Printer
This document describes protocol extensions to TN3270. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1645 Gwinn Jul 94 Simple Network Paging Protocol -
Version 2
This RFC suggests a simple way for delivering both alphanumeric
numeric pages (one-way) to radio paging terminals. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1644 Braden Jul 94 T/TCP -- TCP Extensions for
Functional
This memo specifies T/TCP, an experimental TCP extension for
transaction-oriented (request/response) service. This memo describes
Experimental Protocol for the Internet community
1643 Kastenholz Jul 94 Definitions of Managed Objects for
Ethernet-like Interface
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it defines objects for managing ethernet-like objects
[STANDARDS-TRACK
1642 Goldsmith Jul 94 A Mail-Safe Transformation Format
This document describes a new transformation format of Unicode
contains only 7-bit ASCII characters and is intended to be readable
humans in the limiting case that the document consists of
from the US-ASCII repertoire. This memo defines an
Protocol for the Internet community
Elliott Informational [Page 12]
RFC 1699 Summary of 1600-1699 January 1997
1641 Goldsmith Jul 94 Using Unicode with
This document specifies the usage of Unicode within MIME. This
defines an Experimental Protocol for the Internet community
1640 Crocker Jun 94 The Process for Organization of
Standards Working Group (POISED
This report, originally prepared in January 1993 provides a summary
the POISED WG, starting from the events leading to the formation of
WG to the end of 1992. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1639 Piscitello Jun 94 FTP Operation Over Big Address
(FOOBAR
This RFC specifies a method for assigning addresses other than 32-
IPv4 addresses to data ports through the specification of a "long
(LPRT)" command and "Long Passive (LPSV)" reply, each having as
argument a , which allows for additional
families, variable length network addresses and variable length
numbers. This memo defines an Experimental Protocol for the
community
1638 Baker Jun 94 PPP Bridging Control Protocol (BCP
This document defines the Network Control Protocol for establishing
configuring Remote Bridging for PPP links. [STANDARDS-TRACK
1637 Manning Jun 94 DNS NSAP Resource
This document defines the format of one new Resource Record (RR) for
DNS for domain name-to-NSAP mapping. This memo defines an
Protocol for the Internet community
Elliott Informational [Page 13]
RFC 1699 Summary of 1600-1699 January 1997
1636 Braden Jun 94 Report of IAB Workshop on Security
the Internet
This document is a report on an Internet architecture workshop
initiated by the IAB and held at USC Information Sciences Institute
February 8-10, 1994. This workshop generally focused on security
in the Internet architecture. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
1635 Deutsch May 94 How to Use Anonymous
This document provides information for the novice Internet user
using the File Transfer Protocol (FTP). It explains what FTP is,
anonymous FTP is, and what an anonymous FTP archive site is. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1634 Allen May 94 Novell IPX Over Various WAN
(IPXWAN
This document describes how Novell IPX operates over various WAN media
Specifically, it describes the common "IPX WAN" protocol Novell uses
exchange necessary router to router information prior to
standard IPX routing information and traffic over WAN datalinks.
memo provides information for the Internet community. This memo
not specify an Internet standard of any kind
1633 Braden Jun 94 Integrated Services in the
Architecture: an
This memo discusses a proposed extension to the Internet
and protocols to provide integrated services, i.e., to support real-
as well as the current non-real-time service of IP. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
Elliott Informational [Page 14]
RFC 1699 Summary of 1600-1699 January 1997
1632 Getchell May 94 A Revised Catalog of Available X.500
This document is the result of a survey that gathered new or
descriptions of currently available implementations of X.500,
commercial products and openly available offerings. This document is
revision of RFC 1292. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1631 Egevang May 94 The IP Network Address Translator (NAT
This memo proposes another short-term solution, address reuse,
complements CIDR or even makes it unnecessary. The address
solution is to place Network Address Translators (NAT) at the borders
stub domains. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1630 Berners-Lee Jun 94 Universal Resource Identifiers in
This document defines the syntax used by the World-Wide Web
to encode the names and addresses of objects on the Internet. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1629 Colella May 94 Guidelines for OSI NSAP Allocation
the
This paper provides guidelines for allocating NSAP addresses in
Internet. The guidelines provided in this paper have been the basis
initial deployment of CLNP in the Internet, and have proven
valuable both as an aid to scaling of CLNP routing, and for
administration. [STANDARDS-TRACK
1628 Case May 94 UPS Management Information
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it defines objects for managing uninterruptible power
(UPS) systems. [STANDARDS-TRACK
Elliott Informational [Page 15]
RFC 1699 Summary of 1600-1699 January 1997
1627 Lear Jul 94 Network 10 Considered
(Some Practices Shouldn't be Codified
This document restates the arguments for maintaining a unique
space. Concerns for Internet architecture and operations, as well
IETF procedure, are explored. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
1626 Atkinson May 94 Default IP MTU for use over ATM AAL
There are a number of good reasons to have a reasonably large
MTU value for IP over ATM AAL5. This paper presents the default IP
for use over ATM AAL5. [STANDARDS-TRACK
1625 St. Pierre Jun 94 WAIS over Z39.50-1988
The purpose of this memo is to initiate a discussion for a
path of the WAIS technology from Z39.50-1988 Information
Service Definitions and Protocol Specification for Library
[1] to Z39.50-1992 [2] and then to Z39.50-1994 [3]. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1624 Rijsinghani May 94 Computation of the Internet
via Incremental
This memo describes an updated technique for incremental computation
the standard Internet checksum. It updates the method described in
1141. This memo provides information for the Internet community.
memo does not specify an Internet standard of any kind
1623 Kastenholz May 94 Definitions of Managed Objects for
Ethernet-like Interface
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it defines objects for managing ethernet-like objects
[STANDARDS-TRACK
Elliott Informational [Page 16]
RFC 1699 Summary of 1600-1699 January 1997
1622 Francis May 94 Pip Header
The purpose of this RFC and the companion RFC "Pip Near-
Architecture" are to record the ideas (good and bad) of Pip. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1621 Francis May 94 Pip Near-term
The purpose of this RFC and the companion RFC "Pip Header Processing
are to record the ideas (good and bad) of Pip. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1620 Braden May 94 Internet Architecture Extensions
Shared
This memo discusses alternative approaches to extending the
architecture to eliminate some or all unnecessary hops. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1619 Simpson May 94 PPP over SONET/
This document describes the use of PPP over Synchronous Optical
(SONET) and Synchronous Digital Heirarchy (SDH) circuits. [STANDARDS
TRACK
1618 Simpson May 94 PPP over
This document describes the use of PPP over Integrated Services
Network (ISDN) switched circuits. [STANDARDS-TRACK
1617 Barker May 94 Naming and Structuring Guidelines
X.500 Directory
This document defines a number of naming and structuring
focused on White Pages usage. Alignment to these guidelines
recommended for directory pilots. This memo provides information
the Internet community. This memo does not specify an Internet
of any kind
Elliott Informational [Page 17]
RFC 1699 Summary of 1600-1699 January 1997
1616 RARE WG-MSG May 94 A report by the RARE Task Force
X.400(1988) of the RARE Working Group
Mail &
The report documents the results of a task force on X.400(1988)
deployment of the RARE Mails and Messaging Work Group during the
from November 1992 until October 1993. This memo provides
for the Internet community. This memo does not specify an
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
problems can be anticipated in the migration, especially considering
migration from the existing X.400(84) infrastructure created by
COSINE MHS project to an X.400(88) infrastructure. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1614 Adie May 94 Network Access to Multimedia
This report summarises the requirements of research and academic
users for network access to multimedia information. This memo
information for the Internet community. This memo does not specify
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
by encapsulating the X.25 Packet Level in TCP packets. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1612 Austein May 94 DNS Resolver MIB
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it describes a set of extensions which instrument
resolver functions. This memo was produced by the DNS working group
[STANDARDS-TRACK
Elliott Informational [Page 18]
RFC 1699 Summary of 1600-1699 January 1997
1611 Austein May 94 DNS Server MIB
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it describes a set of extensions which instrument DNS
server functions. This memo was produced by the DNS working group
[STANDARDS-TRACK
1610 I.A.B Jul 94 INTERNET OFFICIAL PROTOCOL
This memo describes the state of standardization of protocols used
the Internet as determined by the Internet Architecture Board (IAB).
[STANDARDS-TRACK
1609 Mansfield Mar 94 Charting Networks in the X.500
This document presents a model in which a communication network with
its related details and descriptions can be represented in the X.500
Directory. This memo defines an Experimental Protocol for the
community
1608 Johannsen Mar 94 Representing IP Information in the X.500
This document describes the objects necessary to include
about IP networks and IP numbers in the X.500 Directory. It extends
work "Charting networks in the X.500 Directory" [1] where a
framework is presented for representing networks in the Directory
applying it to IP networks. This memo defines an Experimental
for the Internet community
1607 Cerf Apr 94 A VIEW FROM THE 21ST
This document is a composition of letters discussing a possible future
This memo provides information for the Internet community. This
does not specify an Internet standard of any kind
Elliott Informational [Page 19]
RFC 1699 Summary of 1600-1699 January 1997
1606 Onion Apr 94 A Historical Perspective On The Usage
IP Version 9
This paper reviews the usages of the old IP version protocol.
considers some of its successes and its failures. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1605 Shakespeare Apr 94 SONET to Sonnet
Because Synchronous Optical Network (SONET) transmits data in frames
bytes, it is fairly easy to envision ways to compress SONET frames
yield higher bandwidth over a given fiber optic link. This
describes a particular method, SONET Over Novel English
(SONNET). This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1604 Brown Mar 94 Definitions of Managed
for Frame Relay
This memo defines an extension to the Management Information Base (MIB
for use with network management protocols in TCP/IP-based internets.
particular, it defines objects for managing the Frame Relay Service
[STANDARDS-TRACK
1603 Huizer Mar 94 IETF Working
Guidelines and
This document describes the guidelines and procedures for formation
operation of IETF working groups. It describes the formal
between IETF participants WG and the Internet Engineering Steering
(IESG). This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1602 I.A.B. Mar 94 The Internet Standards Process --
Revision 2
This document is a revision of RFC 1310, which defined the
procedures for creating and documenting Internet Standards. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
Elliott Informational [Page 20]
RFC 1699 Summary of 1600-1699 January 1997
1601 Huitema Mar 94 Charter of the Internet
Board (IAB
This memo documents the composition, selection, roles, and
of the Internet Architecture Board and its subsidiary organizations
This memo provides information for the Internet community. This
does not specify an Internet standard of any kind
1600 I.A.B. Mar 94 INTERNET OFFICIAL PROTOCOL
This memo describes the state of standardization of protocols used
the Internet as determined by the Internet Architecture Board (IAB).
[STANDARDS-TRACK
Security
Security issues are not discussed in this memo
Author's
Josh
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: elliott@isi.
Elliott Informational [Page 21]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
