As per Relevance of the word provides, we have this rfc below:
Network Working Group M.
Request for Comments: 1799
Category: Informational January 1997
Request for Comments
RFC Numbers 1700-1799
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 1700
through RFCs 1799. 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
--- ------ ---- -----
1799 Kennedy Jan 97 Requests For Comments
This memo
1798 Young Jun 95 Connection-less Lightweight X.500
Directory Access
The protocol described in this document is designed to provide access
the Directory while not incurring the resource requirements of
Directory Access Protocol (DAP). [STANDARDS-TRACK
Kennedy Informational [Page 1]
RFC 1799 Summary of 1700-1799 January 1997
1797 IANA Apr 95 Class A Subnet
There appears to be some interest in experimenting with subnetting
class A addresses. It is suggested that conducting an experiment now
identify and fix any software that does not properly handle
class A addresses would be useful and important. This document
an Experimental Protocol for the Internet community. This does
specify an Internet standard of any kind
1796 Huitema Apr 95 Not All RFCs are
This document discusses the relationship of the Request for
(RFCs) notes to Internet Standards. This memo provides information
the Internet community. This memo does not specify an Internet
of any kind
1795 Wells Apr 95 Data Link Switching: Switch-to-
AIW DLSw RIG: DLSw Closed Pages,
Standard Version 1.0
This RFC describes use of Data Link Switching over TCP/IP. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1794 Brisco Apr 95 DNS Support for Load
This RFC is meant to first chronicle a foray into the IETF DNS
Group, discuss other possible alternatives to provide/simulate
balancing support for DNS, and to provide an ultimate, flexible
for providing DNS support for balancing loads of many types. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1793 Moy Apr 95 Extending OSPF to Support Demand
This memo defines enhancements to the OSPF protocol that allow
operation over "demand circuits". [STANDARDS-TRACK
Kennedy Informational [Page 2]
RFC 1799 Summary of 1700-1799 January 1997
1792 Sung Apr 95 TCP/IPX Connection Mib
New MIB objects, tcpIpxConnTable, udpIpxTable, tcpUnspecConnTable
udpUnspecTable are presented in this paper, to be used in place
tcpConnTable and udpListenerTable when TCP and UDP are running over IPX
This document defines an Experimental Protocol for the
community. This does not specify an Internet standard of any kind
1791 Sung Apr 95 TCP And UDP Over IPX Networks
Fixed Path
TCP/IPX allows TCP/IP applications to run over IPX networks by
TCP and UDP run over IPX. And this memo specifies the packet format
operational procedures for running TCP and UDP over IPX. This
defines an Experimental Protocol for the Internet community. This
not specify an Internet standard of any kind
1790 Cerf Apr 95 An Agreement between the
Society and Sun Microsystems, Inc
in the Matter of ONC RPC and
This RFC is an official public record of an agreement between
Microsystems and the Internet Society. This memo provides
for the Internet community. It does not specify an Internet standard
any kind
1789 Yang Apr 95 INETPhone: Telephone Services
Servers on
This RFC presents a true telephone service, called INETPhone,
supports voice communication through the Internet. This memo
information for the Internet community. It does not specify an
standard of any kind
1788 Simpson Apr 95 ICMP Domain Name
This document specifies ICMP messages for learning the Fully
Domain Name associated with an IP address. This document defines
Experimental Protocol for the Internet community. This does not
an Internet standard of any kind
Kennedy Informational [Page 3]
RFC 1799 Summary of 1700-1799 January 1997
1787 Rekhter Apr 95 Routing in a Multi-provider
This document presents some of the issues related to network
routing in a multi-provider Internet, and specifically to the
routing. This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1786 Bates Mar 95 Representation of IP Routing
This document is an update to the original `ripe-81' proposal
representing and storing routing polices within the RIPE database.
incorporates several extensions proposed by Merit Inc. and gives
of a generalized IP routing policy representation to be used by
Internet routing registries. It acts as both tutorial and
details of database objects and attributes that use and make up
routing registry. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1785 Malkin Mar 95 TFTP Option Negotiation
This document was written to allay concerns that the presence of
in a TFTP Request packet might cause pathological behavior on
which do not support TFTP option negotiation. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1784 Malkin Mar 95 TFTP Timeout Interval and
Size
This document describes two TFTP options. The first allows the
and server to negotiate the Timeout Interval. The second allows
side receiving the file to determine the ultimate size of the
before it begins. [STANDARDS-TRACK
1783 Malkin Mar 95 TFTP Blocksize
This document describes a TFTP option which allows the client and
to negotiate a blocksize more applicable to the network medium
[STANDARDS-TRACK
Kennedy Informational [Page 4]
RFC 1799 Summary of 1700-1799 January 1997
1782 Malkin Mar 95 TFTP Option
The Trivial File Transfer Protocol is a simple, lock-step, file
protocol which allows a client to get or put a file onto a remote host
This document describes a simple extension to TFTP to allow
negotiation prior to the file transfer
1781 Kille Mar 95 Using the OSI Directory to
User Friendly
This proposal sets out some conventions for representing names in
friendly manner, and shows how this can be used to achieve
friendly naming. [STANDARDS-TRACK
1780 IAB Mar 95 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
1779 Kille Mar 95 A String Representation of
The OSI Directory uses distinguished names as the primary keys
entries in the directory. Distinguished Names are encoded in ASN.1.
When a distinguished name is communicated between to users not using
directory protocol (e.g., in a mail message), there is a need to have
user-oriented string representation of distinguished name.
specification defines a string format for representing names, which
designed to give a clean representation of commonly used names,
being able to represent any distinguished name. [STANDARDS-TRACK
1778 Howes Mar 95 The String Representation of
Attribute
The Lightweight Directory Access Protocol (LDAP) requires that
contents of AttributeValue fields in protocol elements be octet strings
This document defines the requirements that must be satisfied
encoding rules used to render X.500 Directory attribute syntaxes into
form suitable for use in the LDAP, then goes on to define the
rules for the standard set of attribute syntaxes. [STANDARDS-TRACK
Kennedy Informational [Page 5]
RFC 1799 Summary of 1700-1799 January 1997
1777 Yeong Mar 95 Lightweight Directory Access
The protocol described in this document is designed to provide access
the X.500 Directory while not incurring the resource requirements of
Directory Access Protocol (DAP).This protocol is specifically
at simple management applications and browser applications that
simple read/write interactive access to the X.500 Directory, and
intended to be a complement to the DAP itself. [STANDARDS-TRACK
1776 Crocker Apr 95 The Address is the
Declaring that the address is the message, the IPng WG has selected
packet format which includes 1696 bytes of address space. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1775 Crocker Mar 95 To Be "On" the
The Internet permits different levels of access for consumers
providers of service. The nature of those differences is
important in the capabilities They afford. Hence, it is appropriate
provide terminology that distinguishes among the range, so that
Internet community can gain some clarity when distinguishing whether
user (or an organization) is "on" the Internet. This document
four terms, for distinguishing the major classes of access. This
provides information for the Internet community. This memo does
specify an Internet standard of any kind
1774 Traina Mar 95 BGP-4 Protocol
The purpose of this report is to document how the requirements
advancing a routing protocol to Draft Standard have been satisfied
the Border Gateway Protocol version 4 (BGP-4). This report
the key features of BGP, and analyzes the protocol with respect
scaling and performance. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
Kennedy Informational [Page 6]
RFC 1799 Summary of 1700-1799 January 1997
1773 Traina Mar 95 Experience with the BGP-4
The purpose of this memo is to document how the requirements
advancing a routing protocol to Draft Standard have been satisfied
Border Gateway Protocol version 4 (BGP-4). This report
experience with BGP. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1772 Rekhter Mar 95 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. This document describes the usage of the BGP in
Internet. [STANDARDS-TRACK
1771 Rekhter Mar 95 A Border Gateway Protocol 4 (BGP-4)
This document, together with its companion document, "Application of
Border Gateway Protocol in the Internet", define an inter-
system routing protocol for the Internet. [STANDARDS-TRACK
1770 Graff Mar 95 IPv4 Option for Sender
Multi-Destination
This memo defines an IPv4 option to provide a sender directed multi
destination delivery mechanism called Selective Directed Broadcast
(SDBM). This memo provides information for the Internet community.
memo does not specify an Internet standard of any kind
1769 Mills Mar 95 Simple Network Time Protocol (SNTP
This memorandum describes the Simple Network Time Protocol (SNTP),
is an adaptation of the Network Time Protocol (NTP) used to
computer clocks in the Internet. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
Kennedy Informational [Page 7]
RFC 1799 Summary of 1700-1799 January 1997
1768 Marlow Mar 95 Host Group Extensions for CLNP
This memo provides a specification for multicast extensions to the
protocol similar to those provided to IP by RFC1112. This memo
an Experimental Protocol for the Internet community. This memo does
specify an Internet standard of any kind
1767 Crocker Mar 95 MIME Encapsulation of EDI
Since there are many different EDI specifications, the current
defines three distinct categories as three different MIME content-types
[STANDARDS-TRACK
1766 Alvestrand Mar 95 Tags for the Identification of
This document describes a language tag for use in cases where it
desired to indicate the language used in an information object
[STANDARDS-TRACK
1765 Moy Mar 95 OSPF Database
This memo details a way of gracefully handling unanticipated
overflows. This memo defines an Experimental Protocol for the
community. This memo does not specify an Internet standard of any kind
1764 Senum Mar 95 The PPP XNS IDP Control Protocol (XNSCP
This document defines the Network Control Protocol for establishing
configuring the Xerox Network Systems (XNS) Internet Datagram
(IDP) over PPP. [STANDARDS-TRACK
1763 Senum Mar 95 The PPP Banyan Vines Control Protocol (BVCP
This document defines the Network Control Protocol for establishing
configuring the Banyan VINES protocol over PPP. [STANDARDS-TRACK
Kennedy Informational [Page 8]
RFC 1799 Summary of 1700-1799 January 1997
1762 Senum Mar 95 The PPP DECnet Phase IV Control
(DNCP
This document defines the NCP for establishing and configuring Digital'
DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This
applies only to DNA Phase IV Routing messages (both data and control),
and not to other DNA Phase IV protocols (MOP, LAT, etc). [STANDARDS
TRACK
1761 Callaghan Feb 95 Snoop Version 2 Packet Capture File
This paper describes the file format used by "snoop", a
monitoring and capture program developed by Sun. This paper is
so that people can write compatible programs to generate and
snoop packet capture files. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
1760 Haller Feb 95 The S/KEY One-Time Password
This document describes the S/KEY* One-Time Password system as
for public use by Bellcore. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
1759 Smith Mar 95 Printer
A printer is the physical device that takes media from an input source
produces marks on that media according to some page description or
control language and puts the result in some output destination
possibly with finishing applied. The information needed in
management of the physical printer and the management of a printing
overlap highly and many of the tasks in each management area require
same or similar information. [STANDARDS-TRACK
1758 N.A.D.F. Feb 95 NADF Standing Documents: A Brief
The purpose of this document is to provide a brief overview of
NADF's Standing Document series. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
Kennedy Informational [Page 9]
RFC 1799 Summary of 1700-1799 January 1997
1757 Waldbusser Feb 95 Remote Network Monitoring
Information
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 remote network
devices. [STANDARDS-TRACK
1756 Rinne Jan 95 REMOTE WRITE PROTOCOL - VERSION 1.0
This document describes a simple Remote Write Protocol (RWP). This
defines an Experimental Protocol for the Internet community. This
does not specify an Internet standard of any kind
1755 Perez Feb 95 ATM Signaling Support for IP over
This memo describes the ATM call control signaling exchanges needed
support Classical IP over ATM implementations as described in RFC 1577.
[STANDARDS-TRACK
1754 Laubach Jan 95 IP over ATM Working Group'
Recommendations for the ATM Forum'
Multiprotocol
Version 1
This document represents an initial list of requirements submitted
the ATM Forum's Multiprotocol BOF for the operation of IP over
networks as determined by the IETF IP over ATM Working Group and
working groups. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1753 Chiappa Dec 94 IPng Technical
Of the Nimrod Routing and
This document presents the requirements that the Nimrod routing
addressing architecture has upon the internetwork layer protocol. To
most useful to Nimrod, any protocol selected as the IPng should
these requirements. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
Kennedy Informational [Page 10]
RFC 1799 Summary of 1700-1799 January 1997
1752 Bradner Jan 95 The Recommendation for the IP
Generation
This document presents the recommendation of the IPng Area Directors
what should be used to replace the current version of the
Protocol. [STANDARDS-TRACK
1751 McDonald Dec 94 A Convention for Human-Readable 128-
This memo proposes a convention for use with Internet applications &
protocols using 128-bit cryptographic keys. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1750 Eastlake Dec 94 Randomness Recommendations for
Choosing random quantities to foil a resourceful and motivated
is surprisingly difficult. This paper points out many pitfalls in
traditional pseudo-random number generation techniques for choosing
quantities. It recommends the use of truly random hardware
and shows that the existing hardware on many systems can be used
this purpose. This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1749 McCloghrie Dec 94 IEEE 802.5 Station Source Routing
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 by IEEE 802.5 end-
for managing source routes on a Token Ring network where IEEE source
routing is in use. [STANDARDS-TRACK
1748 McCloghrie Dec 94 IEEE 802.5 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
which use the IEEE 802.5 Token Ring technology described in 802.5
Ring Access Method and Physical Layer Specifications, IEEE
802.5-1989. [STANDARDS-TRACK
Kennedy Informational [Page 11]
RFC 1799 Summary of 1700-1799 January 1997
1747 Hilgeman Jan 95 Definitions of Managed Objects for
Data Link Control (SDLC) using SMIv
This specification defines an extension to the Management
Base (MIB) for use with SNMP-based network management. In particular
it defines objects for managing the configuration, monitoring
control of data link controls in an SNA environment. [STANDARDS-TRACK
1746 Manning Dec 94 Ways to Define User
This paper covers basic fundamentals that must be understood when
defines, interprets, or implements methods to control user
on or over the Internet. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1745 Varadhan Dec 94 BGP4/IDRP for IP---OSPF
This memo defines the various criteria to be used when designing
Autonomous System Border Router (ASBR) that will run either BGP4 or
for IP with other ASBRs external to the AS and OSPF as its IGP
[STANDARDS-TRACK
1744 Huston Dec 94 Observations on the Management
the Internet Address
This memo examines some of the issues associated with the
management practices of the Internet IPv4 address space, and
the potential outcomes of these practices as the unallocated
pool shrinks in size. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1743 McCloghrie Dec 94 IEEE 802.5 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
which use the IEEE 802.5 Token Ring technology described in 802.5
Ring Access Method and Physical Layer Specifications, IEEE
802.5-1989. [STANDARDS-TRACK
Kennedy Informational [Page 12]
RFC 1799 Summary of 1700-1799 January 1997
1742 Waldbusser Jan 95 AppleTalk Management Information Base
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 AppleTalk networks
[STANDARDS-TRACK
1741 Falstrom Dec 94 MIME Content Type for BinHex Encoded
This memo describes the format to use when sending BinHex4.0 files
MIME [BORE93]. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1740 Falstron Dec 94 MIME Encapsulation of Macintosh Files -
This memo describes the format to use when sending Apple Macintosh
via MIME [BORE93]. [STANDARDS-TRACK
1739 Kessler Dec 94 A Primer On Internet and TCP/IP
This memo is an introductory guide to some of the TCP/IP and
tools and utilities that allow users to access the wide variety
information on the network, from determining if a particular host is
to viewing a multimedia thesis on foreign policy. It also
discussion lists accessible from the Internet, ways to obtain
documents, and resources that help users weave their way through
Internet. This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1738 Berners-Lee Dec 94 Uniform Resource Locators (URL
This document specifies a Uniform Resource Locator (URL), the syntax
semantics of formalized information for location and access of
via the Internet. [STANDARDS-TRACK
1737 Sollins Dec 94 Functional Requirements for
Resource
This document specifies a minimum set of requirements for a kind
Internet resource identifier known as Uniform Resource Names (URNs).
This memo provides information for the Internet community. This
does not specify an Internet standard of any kind
Kennedy Informational [Page 13]
RFC 1799 Summary of 1700-1799 January 1997
1736 Kunze Feb 95 Functional Recommendations
Internet Resource
This document specifies a minimum set of requirements for
resource locators, which convey location and access information
resources. This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1735 Heinanen Dec 94 NBMA Address Resolution Protocol (NARP
This document describes the NBMA Address Resolution Protocol (NARP).
NARP can be used by a source terminal (host or router) connected to
Non-Broadcast, Multi-Access link layer (NBMA) network to find out
NBMA addresses of the a destination terminal provided that
destination terminal is connected to the same NBMA network. This
defines an Experimental Protocol for the Internet community. This
does not specify an Internet standard of any kind
1734 Myers Dec 94 POP3 AUTHentication
This document describes the optional AUTH command, for indicating
authentication mechanism to the server, performing an
protocol exchange, and optionally negotiating a protection mechanism
subsequent protocol interactions. [STANDARDS-TRACK
1733 Crispin Dec 94 Distributed Electronic
Models in IMAP
There are three fundamental models of client/server email: offline
online, and disconnected use. IMAP4 can be used in any one of
three models. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1732 Crispin Dec 94 IMAP4 COMPATIBILITY WITH IMAP
AND IMAP2
This is a summary of hints and recommendations to enable an IMAP
implementation to interoperate with implementations that conform
earlier specifications. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
Kennedy Informational [Page 14]
RFC 1799 Summary of 1700-1799 January 1997
1731 Myers Dec 94 IMAP4 Authentication
The Internet Message Access Protocol, Version 4 [IMAP4] contains
AUTHENTICATE command, for identifying and authenticating a user to
IMAP4 server and for optionally negotiating a protection mechanism
subsequent protocol interactions. This document describes
authentication mechanisms for use by the IMAP4 AUTHENTICATE command
[STANDARDS-TRACK
1730 Crispin Dec 94 Internet Message Access
- Version 4
The Internet Message Access Protocol, Version 4 (IMAP4) allows a
to access and manipulate electronic mail messages on a server. IMAP
permits manipulation of remote message folders, called "mailboxes", in
way that is functionally equivalent to local mailboxes. IMAP4
provides the capability for an offline client to resynchronize with
server. [STANDARDS-TRACK
1729 Lynch Dec 94 Using the Z39.50
Retrieval Protocol in the
This memo describes an approach to the implementation of the ANSI/
Z39.50-1992 Standard for Information Retrieval in the TCP/IP
which is currently in wide use by the Z39.50 implementor community.
memo provides information for the Internet community. This memo
not specify an Internet standard of any kind
1728 Weider Dec 94 Resource
This paper describes an automatic mechanism, the resource transponder
for maintaining resource location information. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
1727 Weider Dec 94 A Vision of an Integrated
Information
This paper lays out a vision of how Internet information services
be integrated over the next few years, and discusses in some detail
steps will be needed to achieve this integration. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
Kennedy Informational [Page 15]
RFC 1799 Summary of 1700-1799 January 1997
1726 Partridge Dec 94 Technical Criteria for
IP The Next Generation (IPng
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
1725 Myers Nov 94 Post Office Protocol - Version 3
This memo is a revision to RFC 1460, a Draft Standard. [STANDARDS-TRACK
1724 Malkin Nov 94 RIP Version 2 MIB
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 RIP Version 2. [STANDARDS
TRACK
1723 Malkin Nov 94 RIP Version 2
Carrying Additional
This document specifies an extension of the Routing Information
(RIP), o expand the amount of useful information carried in RIP
and to add a measure of security. This memo obsoletes RFC 1388,
specifies an update to the "Routing Information Protocol" STD 34,
1058. [STANDARDS-TRACK
1722 Malkin Nov 94 RIP Version 2 Protocol
As required by Routing Protocol Criteria (RFC 1264), this report
the applicability of the RIP-2 protocol within the Internet.
report is a prerequisite to advancing RIP-2 on the standards track
[STANDARDS-TRACK
Kennedy Informational [Page 16]
RFC 1799 Summary of 1700-1799 January 1997
1721 Malkin Nov 94 RIP Version 2 Protocol
As required by Routing Protocol Criteria (RFC 1264), this
documents the key features of the RIP-2 protocol and the
implementation experience. This report is a prerequisite to
RIP-2 on the standards track. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
1720 IAB Nov 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
1719 Gross Dec 94 A Direction for
Specification and
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
1718 IETF Secretariat Nov 94 The Tao of
A Guide for New Attendees of
Internet Engineering Task
The purpose of this For Your Information (FYI) RFC is to explain to
newcomers how the IETF works. This memo provides information for
Internet community. It does not specify an Internet standard. [FYI 17]
1717 Sklower Nov 94 The PPP Multilink Protocol (MP
This document proposes a method for splitting, recombining
sequencing datagrams across multiple logical data links. [STANDARDS
TRACK
Kennedy Informational [Page 17]
RFC 1799 Summary of 1700-1799 January 1997
1716 Almquist Nov 94 Towards Requirements for IP
The goal of this work is to replace RFC-1009, Requirements for
Gateways ([INTRO:1]) with a new document. It defines and
requirements for devices which perform the network layer
function of the Internet protocol suite. This memo provides
for the Internet community. This memo does not specify an
standard of any kind
1715 Huitema Nov 94 The H Ratio for Address
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
1714 Williamson Nov 94 Referral Whois Protocol (RWhois
This memo describes version 1.0 of the client/server interaction
RWhois. RWhois provides a distributed system for the display
hierarchical information. This memo provides information for
Internet community. This memo does not specify an Internet standard
any kind
1713 Romao Nov 94 Tools for DNS
Although widely used (and most of the times unnoticed), DNS (Domain
System) is too much overlooked, in the sense that people,
administrators, tend to ignore possible anomalies as long
applications that need name-to-address mapping continue to work.
document presents some tools available for domain administrators
detect and correct those anomalies. This memo provides information
the Internet community. This memo does not specify an Internet
of any kind
1712 Farrell Nov 94 DNS Encoding of Geographical
This document defines the format of a new Resource Record (RR) for
Domain Naming System (DNS), and reserves a corresponding DNS
mnemonic and numerical code. This memo defines an Experimental
for the Internet community. This memo does not specify an
standard of any kind
Kennedy Informational [Page 18]
RFC 1799 Summary of 1700-1799 January 1997
1711 Houttuin Oct 94 Classifications in E-mail
This paper presents a classification for e-mail routing issues.
memo provides information for the Internet community. This memo
not specify an Internet standard of any kind
1710 Hinden Oct 94 Simple Internet Protocol
White
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
1709 Gargano Nov 94 K-12 Internetworking
The K-12 community traditionally has not had this level of
available for telecommunications planning. This document is intended
bridge that gap and provides a recommended technical direction,
introduction to the role the Internet now plays in K-12 education
technical guidelines for building a campus data
infrastructure that provides internetworking services and connections
the Internet. This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1708 Gowin Oct 94 NTP PICS
For the Network Time
Version 3
This RFC describes a PICS Proforma translated into an
acceptable form. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1707 McGovern Oct 94 CATNIP: Common Architecture
the
This document was submitted to the IETF IPng area in response to
1550. This paper describes a common architecture for the network
protocol. This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
Kennedy Informational [Page 19]
RFC 1799 Summary of 1700-1799 January 1997
1706 Manning Oct 94 DNS NSAP Resource
This document defines the format of one new Resource Record (RR) for
DNS for domain name-to-NSAP mapping. The RR may be used with any
address format. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1705 Carlson Oct 94 Six Virtual Inches to the Left
The Problem with
This document was submitted to the IETF IPng area in response to
1550. This RFC suggests that a new version of TCP (TCPng), and UDP,
developed and deployed. This memo provides information for the
community. This memo does not specify an Internet standard of any kind
1704 Haller Oct 94 On Internet
This document describes a spectrum of authentication technologies
provides suggestions to protocol developers on what kinds
authentication might be suitable for some kinds of protocols
applications used in the Internet. This document provides
for the Internet community. This memo does not specify an
standard of any kind
1703 Rose Oct 94 Principles of Operation for the TPC.
Subdomain
Radio Paging -- Technical
This memo describes a technique for radio paging using the Internet
infrastructure. In particular, this memo focuses on the case in
radio pagers are identified via the international telephone network
This memo provides information for the Internet community. This
does not specify an Internet standard of any kind
1702 Hanks Oct 94 Generic Routing Encapsulation
IPv4
This memo addresses the case of using IP as the delivery protocol or
payload protocol and the special case of IP as both the delivery
payload. This memo also describes using IP addresses and
system numbers as part of a GRE source route. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
Kennedy Informational [Page 20]
RFC 1799 Summary of 1700-1799 January 1997
1701 Hanks Oct 94 Generic Routing Encapsulation (GRE
This document specifies a protocol for performing encapsulation of
arbitrary network layer protocol over another arbitrary network
protocol. This memo provides information for the Internet community
This memo does not specify an Internet standard of any kind
1700 Reynolds Oct 94 Assigned
This RFC is a snapshot of the ongoing process of the assignment
protocol parameters for the Internet protocol suite. To make
current information readily available the assignments are kept up-to
date in a set of online text files. This memo is a status report on
parameters (i.e., numbers and keywords) used in protocols in
Internet community
Security
Security issues are not discussed in this memo
Author's
Mary
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: MKENNEDY@ISI.
Kennedy 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
