As per Relevance of the word provides, we have this rfc below:
Network Working Group A.
Request for Comments: 2299
Category: Informational January 1999
Request for Comments
RFC Numbers 2200-2299
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 2200
through RFCs 2299. 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
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
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
--- ------ ---- -----
2299 Ramos Jan 1999 Request for Comments
This memo
2298 Fajman Mar 1998 An Extensible Message
This memo defines a MIME content-type that may be used by a mail
agent (UA) or electronic mail gateway to report the disposition of
message after it has been sucessfully delivered to a recipient
[STANDARDS-TRACK
Ramos Informational [Page 1]
RFC 2299 Summary of 2200-2299 January 1999
2297 Newman Mar 1998 Ipsilon's General
Management
Specification Version 2.0
This memo specifies enhancements to the General Switch
Protocol (GSMP) [RFC1987]. This memo provides information for
Internet community. It does not specify an Internet standard of
kind
2296 Holtman Mar 1998 HTTP Remote Variant
Algorithm -- RVSA/1.0
HTTP allows web site authors to put multiple versions of the
information under a single URL. Transparent content negotiation is
mechanism for automatically selecting the best version when the URL
accessed. A remote variant selection algorithm can be used to speed
the transparent negotiation process. This document defines the
variant selection algorithm with the version number 1.0. This
defines an Experimental Protocol for the Internet community. It
not specify an Internet standard of any kind. Discussion
suggestions for improvement are requested
2295 Holtman Mar 1998 Transparent
Negotiation in
HTTP allows web site authors to put multiple versions of the
information under a single URL. Transparent content negotiation is
extensible negotiation mechanism, layered on top of HTTP,
automatically selecting the best version when the URL is accessed.
enables the smooth deployment of new web data formats and markup tags
This memo defines an Experimental Protocol for the Internet community
It does not specify an Internet standard of any kind. Discussion
suggestions for improvement are requested
2294 Kille Mar 1998 Representing the O/R
hierarchy in the X.500
Directory Information
This document defines a representation of the O/R Address hierarchy
the Directory Information Tree. [STANDARDS-TRACK
Ramos Informational [Page 2]
RFC 2299 Summary of 2200-2299 January 1999
2293 Kille Mar 1998 Representing Tables
Subtrees in the X.500
This document defines techniques for representing two types
information mapping in the OSI Directory: Mapping from a key to a
(or set of values), as might be done in a table lookup, and mapping
a distinguished name to an associated value (or values), where
values are not defined by the owner of the entry. This is achieved
use of a directory subtree. [STANDARDS-TRCK
2292 Stevens Feb 1998 Advanced Sockets API for IPv
The current document defines some the "advanced" features of the
API that are required for applications to take advantage of
features of IPv6. This memo provides information for the
community. It does not specify an Internet standard of any kind
2291 Slein Feb 1998 Requirements for a
Authoring and
Protocol for the World Wide
This document presents a list of features in the form of
for a Web Distributed Authoring and Versioning protocol which,
implemented, would improve the efficiency of common remote
operations, provide a locking mechanism to prevent overwrite conflicts
improve link management support between non-HTML data types, provide
simple attribute-value metadata facility, provide for the creation
reading of container data types, and integrate versioning into the WWW
This memo provides information for the Internet community. It does
specify an Internet standard of any kind
2290 Solomon Feb 1998 Mobile-IPv4
Option for PPP
Mobile IP [RFC 2002] defines media-independent procedures by which
Mobile Node can maintain existing transport and application-
connections despite changing its point-of-attachment to the Internet
without changing its IP address. PPP [RFC 1661] provides a
method for transporting multi-protocol packets over point-to-
links. As currently specified, Mobile IP Foreign Agents which
Mobile Node connections via PPP can do so only by first assigning
addresses to those Mobile Nodes, defeating one of the primary
of Foreign Agents. This documents corrects this problem by defining
Mobile-IPv4 Configuration Option to the Internet Protocol
Protocol (IPCP) [RFC 1332]. Using this option, two peers
Ramos Informational [Page 3]
RFC 2299 Summary of 2200-2299 January 1999
communicate their support for Mobile IP during the IPCP phase of PPP
Familiarity with Mobile IP [RFC 2002], IPCP [RFC 1332], and PPP [
1661] is assumed. [STANDARDS-TRACK
2289 Haller Feb 1998 A One-Time Password
This document describes a one-time password authentication system (OTP).
The system provides authentication for system access (login) and
applications requiring authentication that is secure against
attacks based on replaying captured reusable passwords. [STANDARDS
TRACK
2288 Lynch Feb 1998 Using Existing
Identifiers as
Resource
This document discusses how three major bibliographic identifiers (
ISBN, ISSN and SICI) can be supported within the URN framework and
currently proposed syntax for URNs. This memo provides information
the Internet community. It does not specify an Internet standard of
kind
2287 Krupczak Feb 1998 Definitions of System-
Managed Objects for
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it describes a basic set of managed objects for fault
configuration and performance management of applications from a
perspective. [STANDARDS-TRACK
2286 Kapp Feb 1998 Test Cases for HMAC-RIPEMD160
and HMAC-RIPEMD128
This document provides two sets of test cases for HMAC-RIPEMD160
HMAC-RIPEMD128. This memo provides information for the
community. It does not specify an Internet standard of any kind
Ramos Informational [Page 4]
RFC 2299 Summary of 2200-2299 January 1999
2285 Mandeville Feb 1998 Benchmarking Terminology
LAN Switching
This document is intended to provide terminology for the benchmarking
local area network (LAN) switching devices. It extends the
already defined for benchmarking network interconnect devices in
1242 and 1944 to switching devices. This memo provides information
the Internet community. It does not specify an Internet standard of
kind
2284 Blunk Mar 1998 PPP Extensible
Protocol (EAP
The Point-to-Point Protocol (PPP) provides a standard method
transporting multi-protocol datagrams over point-to-point links.
also defines an extensible Link Control Protocol, which
negotiation of an Authentication Protocol for authenticating its
before allowing Network Layer protocols to transmit over the link.
document defines the PPP Extensible Authentication Protocol
[STANDARDS-TRACK
2283 Bates Feb 1998 Multiprotocol Extensions
BGP-4
This document defines extensions to BGP-4 to enable it to carry
information for multiple Network Layer protocols (e.g., IPv6, IPX
etc...). The extensions are backward compatible - a router that
the extensions can interoperate with a router that doesn't support
extensions. [STANDARDS-TRACK
2282 Galvin Feb 1998 IAB and IESG Selection
Confirmation, and
Process: Operation of
Nominating and
The process by which the members of the IAB and IESG are selected
confirmed, and recalled is specified. This document specifies
Internet Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
Ramos Informational [Page 5]
RFC 2299 Summary of 2200-2299 January 1999
2281 Li Mar 1998 Cisco Hot Standby
Protocol (HSRP
The memo specifies the Hot Standby Router Protocol (HSRP). The goal
the protocol is to allow hosts to appear to use a single router and
maintain connectivity even if the actual first hop router they are
fails. This memo provides information for the Internet community.
does not specify an Internet standard of any kind
2280 Alaettinoglu Jan 1998 Routing Policy
Language (RPSL
This memo is the reference document for the Routing Policy
Language (RPSL). RPSL allows a network operator to be able to
routing policies at various levels in the Internet hierarchy;
example at the Autonomous System (AS) level. At the same time,
can be specified with sufficient detail in RPSL so that low level
configurations can be generated from them. RPSL is extensible;
routing protocols and new protocol features can be introduced at
time. [STANDARDS-TRACK
2279 Yergeau Jan 1998 UTF-8, a transformation
of ISO 10646
UTF-8, the object of this memo, has the characteristic of preserving
full US-ASCII range, providing compatibility with file systems,
and other software that rely on US-ASCII values but are transparent
other values. This memo updates and replaces RFC 2044, in
addressing the question of versions of the relevant standards
[STANDARDS-TRACK
2278 Freed Jan 1998 IANA
Registration
MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other
Internet protocols are capable of using many different charsets. This
turn means that the ability to label different charsets is essential
This registration procedure exists solely to associate a specific
or names with a given charset and to give an indication of whether
not a given charset can be used in MIME text objects. This
specifies an Internet Best Current Practices for the Internet Community
and requests discussion and suggestions for improvements
Ramos Informational [Page 6]
RFC 2299 Summary of 2200-2299 January 1999
2277 Alvestrand Jan 1998 IETF Policy on Character
and
This document is the current policies being applied by the
Engineering Steering Group (IESG) towards the standardization efforts
the Internet Engineering Task Force (IETF) in order to help
protocols fulfill these requirements. This document specifies
Internet Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
2276 Sollins Jan 1998 Architectural Principles
Uniform Resource Name
This document addresses the issues of the discovery of URN (
Resource Name) resolver services that in turn will directly
URNs into URLs (Uniform Resource Locators) and URCs (Uniform
Characteristics). This memo provides information for the
community. It does not specify an Internet standard of any kind
2275 Wijnen Jan 1998 View-based Access
Model (VACM) for
Simple Network
Protocol (SNMP
This document describes the View-based Access Control Model for use
the SNMP architecture [RFC2261]. It defines the Elements of
for controlling access to management information. This document
includes a MIB for remotely managing the configuration parameters
the View-based Access Control Model. [STANDARDS-TRACK
2274 Blumenthal Jan 1998 User-based Security
(USM) for version 3 of
Simple Network
Protocol (SNMPv3)
This document describes the User-based Security Model (USM) for
version 3 for use in the SNMP architecture [RFC2261]. It defines
Elements of Procedure for providing SNMP message level security.
document also includes a MIB for remotely monitoring/managing
configuration parameters for this Security Model. [STANDARDS-TRACK
Ramos Informational [Page 7]
RFC 2299 Summary of 2200-2299 January 1999
2273 Levi Jan 1998 SNMPv3
This memo describes five types of SNMP applications which make use of
SNMP engine as described in [RFC2261]. The types of
described are Command Generators, Command Responders,
Originators, Notification Receivers, and Proxy Forwarders. This
also defines MIB modules for specifying targets of
operations, for notification filtering, and for proxy forwarding
[STANDARDS-TRACK
2272 Case Jan 1998 Message Processing
Dispatching for the
Network Management
(SNMP
This document describes the Message Processing and Dispatching for
messages within the SNMP architecture [RFC2271]. It defines
procedures for dispatching potentially multiple versions of
messages to the proper SNMP Message Processing Models, and
dispatching PDUs to SNMP applications. This document also describes
Message Processing Model - the SNMPv3 Message Processing Model
[STANDARDS-TRACK
2271 Harrington Jan 1998 An Architecture for
SNMP Management
This document describes an architecture for describing SNMP
Frameworks. The architecture is designed to be modular to allow
evolution of the SNMP protocol standards over time. [STANDARDS-TRACK
2270 Stewart Jan 1998 Using a Dedicated AS for
Homed to a Single
With the increased growth of the Internet, the number of customers
BGP4 has grown significantly. RFC1930 outlines a set of guidelines
when one needs and should use an AS. However, the customer and
provider (ISP) are left with a problem as a result of this in that
there is no need for an allocated AS under the guidelines,
conditions make the use of BGP4 a very pragmatic and perhaps only way
connect a customer homed to a single ISP. This paper proposes
solution to this problem in line with recommendations set forth
RFC1930. This memo provides information for the Internet community.
does not specify an Internet standard of any kind
Ramos Informational [Page 8]
RFC 2299 Summary of 2200-2299 January 1999
2269 Armitage Jan 1998 Using the MARS Model
non-ATM NBMA
This document is intended to state the obvious equivalences, and
the less obvious implications. This memo provides information for
Internet community. It does not specify an Internet standard of
kind
2268 Rivest Mar 1998 A Description of the RC2(r
Encryption
This memo describes a conventional (secret-key) block
algorithm, called RC2, which may be considered as a proposal for a
replacement. This memo provides information for the Internet community
It does not specify an Internet standard of any kind
2267 Ferguson Jan 1998 Network Ingress Filtering
Defeating Denial of
Attacks which
IP Source Address
This paper discusses a simple, effective, and straightforward method
using ingress traffic filtering to prohibit DoS attacks which use
IP addresses to be propagated from 'behind' an Internet
Provider's (ISP) aggregation point. This memo provides information
the Internet community. It does not specify an Internet standard of
kind
2266 Flick Jan 1998 Definitions of Managed
for IEEE 802.12 Repeater
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 network repeaters based
IEEE 802.12. [STANDARDS-TRACK
Ramos Informational [Page 9]
RFC 2299 Summary of 2200-2299 January 1999
2265 Wijnen Jan 1998 View-based Access
Model (VACM) for
Simple Network
Protocol (SNMP
This document describes the View-based Access Control Model for use
the SNMP architecture [RFC2261]. It defines the Elements of
for controlling access to management information. This document
includes a MIB for remotely managing the configuration parameters
the View-based Access Control Model. [STANDARDS-TRACK
2264 Blumenthal Jan 1998 User-based Security
(USM) for version 3 of
Simple Network
Protocol (SNMPv3)
This document describes the User-based Security Model (USM) for
version 3 for use in the SNMP architecture [RFC2261]. It defines
Elements of Procedure for providing SNMP message level security.
document also includes a MIB for remotely monitoring/managing
configuration parameters for this Security Model. [STANDARDS-TRACK
2263 Levi Jan 1998 SNMPv3
This memo describes five types of SNMP applications which make use of
SNMP engine as described in [RFC2261]. The types of
described are Command Generators, Command Responders,
Originators, Notification Receivers, and Proxy Forwarders. This
also defines MIB modules for specifying targets of
operations, for notification filtering, and for proxy forwarding
[STANDARDS-TRACK
2262 Case Jan 1998 Message Processing
Dispatching for the
Network Management
(SNMP
This document describes the Message Processing and Dispatching for
messages within the SNMP architecture [RFC2261]. It defines
procedures for dispatching potentially multiple versions of
messages to the proper SNMP Message Processing Models, and
dispatching PDUs to SNMP applications. This document also describes
Message Processing Model - the SNMPv3 Message Processing Model
[STANDARDS-TRACK
Ramos Informational [Page 10]
RFC 2299 Summary of 2200-2299 January 1999
2261 Harrington Jan 1998 An Architecture for
SNMP Management
This document describes an architecture for describing SNMP
Frameworks. The architecture is designed to be modular to allow
evolution of the SNMP protocol standards over time. [STANDARDS-TRACK
2260 Bates Jan 1998 Scalable Support
Multi-homed Multi-
This document describes addressing and routing strategies for multi
homed enterprises attached to multiple Internet Service Providers (ISPs
that are intended to reduce the routing overhead due to
enterprises in the global Internet routing system. This memo
information for the Internet community. It does not specify an
standard of any kind
2259 Elliott Jan 1998 Simple Nomenclator
Protocol (SNQP
The Simple Nomenclator Query Protocol (SNQP) allows a client
communicate with a descriptive name service or other relational-
query service. This memo provides information for the
community. It does not specify an Internet standard of any
2258 Ordille Jan 1998 Internet Nomenclator
The goal of the Internet Nomenclator Project is to integrate
hundreds of publicly available CCSO servers from around the world.
document provides an overview of the Nomenclator system, describes
to register a CCSO server in the Internet Nomenclator Project, and
to use the Nomenclator search engine to find people on the Internet
This memo provides information for the Internet community. It does
specify an Internet standard of any kind
2257 Daniele Jan 1998 Agent Extensibility (AgentX
Protocol Version 1
This memo defines a standardized framework for extensible SNMP agents
It defines processing entities called master agents and subagents,
protocol (AgentX) used to communicate between them, and the elements
procedure by which the extensible agent processes SNMP
messages. [STANDARDS-TRACK
Ramos Informational [Page 11]
RFC 2299 Summary of 2200-2299 January 1999
2256 Wahl Dec 1997 A Summary of the X.500(96)
User Schema for use with LDAPv
This document provides an overview of the attribute types and
classes defined by the ISO and ITU-T committees in the X.500 documents
in particular those intended for use by directory clients. [STANDARDS
TRACK
2255 Howes Dec 1997 The LDAP URL
This document describes a format for an LDAP Uniform Resource Locator
[STANDARDS-TRACK
2254 Howes Dec 1997 The String Representation
LDAP Search
This document defines a human-readable string format for
LDAP search filters. [STANDARDS-TRACK
2253 Wahl Dec 1997 Lightweight Directory
Protocol (v3): UTF-8
Representation
Distinguished
This specification defines the string format for representing names
which is designed to give a clean representation of commonly
distinguished names, while being able to represent any
name. [STANDARDS-TRACK
2252 Wahl Dec 1997 Lightweight Directory
Protocol (v3):
Syntax
This document defines a set of syntaxes for LDAPv3, and the rules
which attribute values of these syntaxes are represented as
strings for transmission in the LDAP protocol. [STANDARDS-TRACK
Ramos Informational [Page 12]
RFC 2299 Summary of 2200-2299 January 1999
2251 Wahl Dec 1997 Lightweight Directory
Protocol (v3)
The protocol described in this document is designed to provide access
directories supporting the X.500 models, while not incurring
resource requirements of the X.500 Directory Access Protocol (DAP).
[STANDARDS-TRACK
2250 Hoffman Jan 1998 RTP Payload Format
MPEG1/MPEG2
This memo describes a packetization scheme for MPEG video and
streams. [STANDARDS-TRACK
2249 Freed Jan 1998 Mail Monitoring
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community
Specifically, this memo extends the basic Network Services
MIB [8] to allow monitoring of Message Transfer Agents (MTAs). It
also be used to monitor MTA components within gateways. [STANDARDS
TRACK
2248 Freed Jan 1998 Network Services Monitoring
This MIB may be used on its own for any application, and for most
applications this will suffice. This MIB is also designed to serve as
building block which can be used in conjunction with application
specific monitoring and management. [STANDARDS-TRACK
2247 Kille Jan 1998 Using Domains in LDAP/X.500
Distinguished
This document defines an algorithm by which a name registered with
Internet Domain Name Service [2] can be represented as an
distinguished name. [STANDARDS-TRACK
Ramos Informational [Page 13]
RFC 2299 Summary of 2200-2299 January 1999
2246 Dierks Jan 1999 The TLS Protocol Version 1.0
This document specifies Version 1.0 of the Transport Layer
(TLS) protocol. The TLS protocol provides communications privacy
the Internet. The protocol allows client/server applications
communicate in a way that is designed to prevent eavesdropping
tampering, or message forgery. [STANDARDS-TRACK
2245 Newman Nov 1997 Anonymous SASL
As plaintext login commands are not permitted in new IETF protocols,
new way to provide anonymous login is needed within the context of
SASL [SASL] framework. [STANDARDS-TRACK
2244 Newman Nov 1997 ACAP --
Configuration Access
The Application Configuration Access Protocol (ACAP) is designed
support remote storage and access of program option, configuration
preference information. [STANDARDS-TRACK
2243 Metz Nov 1997 OTP Extended
This document provides a specification for a type of response to an
[RFC 1938] challenge that carries explicit indication of the response'
encoding. This document also provides a specification for a
that allows an OTP generator to request that a server re-initialize
sequence and change parameters such as the secret pass phrase
[STANDARDS-TRACK
2242 Droms Nov 1997 NetWare/IP Domain Name
This document defines options that carry NetWare/IP domain name
NetWare/IP sub-options to DHCP clients. [STANDARDS-TRACK
Ramos Informational [Page 14]
RFC 2299 Summary of 2200-2299 January 1999
2241 Provan Nov 1997 DHCP Options for
Directory
This document defines three new DHCP options for
configuration information to clients of the Novell Directory Services
This document defines three new DHCP options for
configuration information to clients of the Novell Directory Services
[STANDARDS-TRACK
2240 Vaughan Nov 1997 A Legal Basis for Domain
The purpose of this memo is to focus discussion on the
problems with the exhaustion of the top level domain space in
Internet and the possible conflicts that can occur when
organisations are vying for the same name. This memo
information for the Internet community. It does not specify an
standard of any kind
2239 de Graaf Nov 1997 Definitions of Managed
for IEEE 802.3
Attachment Units (MAUs) using SMIv
This memo defines an portion of the Management Information Base (MIB
for use with network management protocols in the Internet community.
particular, it defines objects for managing 10 and 100 Mb/second
Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, "10 & 100
Mb/s Management," October 26, 1995. [STANDARDS-TRACK
2238 Clouston Nov 1997 Definitions of Managed
for HPR 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 monitoring and controlling
devices with HPR (High Performance Routing) capabilities. This
identifies managed objects for the HPR protocol. [STANDARDS-TRACK
2237 Tamaru Nov 1997 Japanese Character
for Internet
This memo defines an encoding scheme for the Japanese Characters
describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822],
and network news [RFC 1036]. Also this memo provides a listing of
Ramos Informational [Page 15]
RFC 2299 Summary of 2200-2299 January 1999
Japanese Character Set that can be used in this encoding scheme.
memo provides information for the Internet community. It does
specify an Internet standard of any kind
2236 Fenner Nov 1997 Internet Group
Protocol, Version 2
This memo documents IGMPv2, used by IP hosts to report their
group memberships to routers. It updates STD 5, RFC 1112. [STANDARDS
TRACK
2235 Zakon Nov 1997 Hobbes' Internet
This document presents a history of the Internet in timeline fashion
highlighting some of the key events and technologies which helped
the Internet as we know it today. A growth summary of the Internet
some associated technologies is also included. This memo
information for the Internet community. It does not specify an
standard of any kind
2234 Crocker Nov 1997 Augmented BNF for
Specifications:
In the early days of the Arpanet, each specification contained its
definition of ABNF. This included the email specifications, RFC733
then RFC822 which have come to be the common citations for
ABNF. The current document separates out that definition, to
selective reference. Predictably, it also provides some
and enhancements. [STANDARDS-TRACK
2233 McCloghrie Nov 1997 The Interfaces Group MIB
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
Interfaces. [STANDARDS-TRACK
Ramos Informational [Page 16]
RFC 2299 Summary of 2200-2299 January 1999
2232 Clouston Nov 1997 Definitions of Managed
for DLUR 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 monitoring and controlling
devices with DLUR (Dependent LU Requester) capabilities. This
identifies managed objects for the DLUR protocol. [STANDARDS-TRACK
2231 Freed Nov 1997 MIME Parameter Value
Encoded Word Extensions
Character Sets, Languages,
This memo defines extensions to the RFC 2045 media type and RFC 2183
disposition parameter value mechanisms. This memo also defines
extension to the encoded words defined in RFC 2047 to allow
specification of the language to be used for display as well as
character set. [STANDARDS-TRACK
2230 Atkinson Nov 1997 Key Exchange Delegation
for the
This note describes a mechanism whereby authorisation for one node
act as key exchanger for a second node is delegated and made
via the Secure DNS. This mechanism is intended to be used only with
Secure DNS. This memo provides information for the Internet community
It does not specify an Internet standard of any kind
2229 Faith Oct 1997 A Dictionary Server
The Dictionary Server Protocol (DICT) is a TCP transaction
query/response protocol that allows a client to access
definitions from a set of natural language dictionary databases.
memo provides information for the Internet community. It does
specify an Internet standard of any kind
2228 Horowitz Oct 1997 FTP Security
This document defines extensions to the FTP specification STD 9,
959, "FILE TRANSFER PROTOCOL (FTP)" (October 1985). [STANDARDS-TRACK
Ramos Informational [Page 17]
RFC 2299 Summary of 2200-2299 January 1999
2227 Mogul Oct 1997 Simple Hit-Metering
Usage-Limiting for
This document proposes a simple extension to HTTP, using a new "Meter
header. [STANDARDS-TRACK
2226 Smith Oct 1997 IP Broadcast over ATM
This memo describes how the IP multicast service being developed by
IP over ATM working group may be used to support IP
transmission. [STANDARDS-TRACK
2225 Laubach Apr 1998 Classical IP and ARP over
This memo defines an initial application of classical IP and ARP in
Asynchronous Transfer Mode (ATM) network environment configured as
Logical IP Subnetwork (LIS). [STANDARDS-TRACK
2224 Callaghan Oct 1997 NFS URL
A new URL scheme, 'nfs' is defined. It is used to refer to files
directories on NFS servers using the general URL syntax defined in
1738, "Uniform Resource Locators (URL)". This memo provides
for the Internet community. It does not specify an Internet standard
any kind
2223 Postel Oct 1997 Instructions to RFC
This Request for Comments (RFC) provides information about
preparation of RFCs, and certain policies relating to the publication
RFCs. This memo provides information for the Internet community.
memo does not specify an Internet standard of any kind
2222 Myers Oct 1997 Simple Authentication
Security Layer (SASL
This document describes a method for adding authentication support
connection-based protocols. [STANDARDS-TRACK
Ramos Informational [Page 18]
RFC 2299 Summary of 2200-2299 January 1999
2221 Gahrns Oct 1997 IMAP4 Login
When dealing with large amounts of users and many IMAP4 [RFC-2060]
servers, it is often necessary to move users from one IMAP4 server
another. Login referrals allow clients to transparently connect to
alternate IMAP4 server, if their home IMAP4 server has changed
[STANDARDS-TRACK
2220 Guenther Oct 1997 The Application/MARC Content
This memorandum provides a mechanism for representing objects which
files of Machine-Readable Cataloging records (MARC). The MARC
are standards for the representation and communication of
and related information. A MARC record contains metadata for
information resource following MARC format specifications. This
provides information for the Internet community. It does not specify
Internet standard of any kind
2219 Hamilton Oct 1997 Use of DNS Aliases for
It has become a common practice to use symbolic names (usually CNAMEs
in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to refer
network services such as anonymous FTP [RFC-959] servers, Gopher [RFC
1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers
This is desirable for a number of reasons. It provides a way of
services from one machine to another transparently, and a mechanism
which people or agents may programmatically discover that
organization runs, say, a World-Wide Web server. Although this
has been almost universally adopted, there is no standards document
similar specification for these commonly used names. This
seeks to rectify this situation by gathering together the
'folklore' on naming conventions, and proposes a mechanism
accommodating new protocols. This document specifies an Internet
Current Practices for the Internet Community, and requests
and suggestions for improvements
2218 Genovese Oct 1997 A Common Schema for
Internet White Pages
This document specifies the minimum set of core attributes of a
Pages entry for an individual and describes how new objects with
attributes can be defined and published. [STANDARDS-TRACK
Ramos Informational [Page 19]
RFC 2299 Summary of 2200-2299 January 1999
2217 Clark Oct 1997 Telnet Com Port Control
This memo proposes a protocol to allow greater use of modems attached
a network for outbound dialing purposes. This memo defines
Experimental Protocol for the Internet community
2216 Shenker Sep 1997 Network Element
Specification
This document defines a framework for specifying services provided
network elements, and available to applications, in an
which offers multiple qualities of service. The document first
some necessary context -- including relevant definitions and
data formats -- and then specifies a "template" which
specification documents should follow. This memo provides
for the Internet community. It does not specify an Internet standard
any kind
2215 Shenker Sep 1997 General
Parameters for
Service Network
This memo defines a set of general control and
parameters for network elements supporting the IETF integrated
QoS control framework. [STANDARDS-TRACK
2214 Baker Sep 1997 Integrated Services
Information Base
Service Extensions 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 the the interface
defined in the Guaranteed Service of the Integrated Services Model
[STANDARDS-TRACK
2213 Baker Sep 1997 Integrated Services
Information Base 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 the the interface
defined in the Integrated Services Model. [STANDARDS-TRACK
Ramos Informational [Page 20]
RFC 2299 Summary of 2200-2299 January 1999
2212 Shenker Sep 1997 Specification of
Quality of
This memo describes the network element behavior required to deliver
guaranteed service (guaranteed delay and bandwidth) in the Internet
[STANDARDS-TRACK
2211 Wroclawski Sep 1997 Specification of
Controlled-Load
Element
This memo specifies the network element behavior required to
Controlled-Load service in the Internet. [STANDARDS-TRACK
2210 Wroclawski Sep 1997 The Use of RSVP with
Integrated
This note describes the use of the RSVP resource reservation
with the Controlled-Load and Guaranteed QoS control services
[STANDARDS-TRACK
2209 Braden Sep 1997 Resource ReSerVation
(RSVP) -- Version 1
Processing
This memo contains an algorithmic description of the rules used by
RSVP implementation for processing messages. It is intended to
the version 1 RSVP protocol specification. This memo
information for the Internet community. It does not specify an
standard of any kind
2208 Mankin Sep 1997 Resource ReSerVation
(RSVP) Version 1
Statement Some Guidelines
This document describes the applicability of RSVP along with
Integrated Services protocols and other components of
reservation and offers guidelines for deployment of resource
at this time. This memo provides information for the Internet community
It does not specify an Internet standard of any kind
Ramos Informational [Page 21]
RFC 2299 Summary of 2200-2299 January 1999
2207 Berger Sep 1997 RSVP Extensions for IPSEC
This document presents extensions to Version 1 of RSVP.
extensions permit support of individual data flows using RFC 1826,
Authentication Header (AH) or RFC 1827, IP Encapsulating
Payload (ESP). [STANDARDS-TRACK
2206 Baker Sep 1997 RSVP Management
This memo defines a portion
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 the Resource
Protocol (RSVP) within the interface attributes defined in
Integrated Services Model. [STANDARDS-TRACK
2205 Braden Sep 1997 Resource ReSerVation
(RSVP)--Version 1
This memo describes version 1 of RSVP, a resource reservation
protocol designed for an integrated services Internet. RSVP
receiver-initiated setup of resource reservations for multicast
unicast data flows, with good scaling and robustness properties
[STANDARDS-TRACK
2204 Nash Sep 1997 ODETTE File Transfer
This memo describes a file transfer protocol to facilitate
data interchange between trading partners. This memo
information for the Internet community. It does not specify an
standard of any kind
2203 Eisler Sep 1997 RPCSEC_GSS Protocol
This memo describes an ONC/RPC security flavor that allows RPC
to access the Generic Security Services Application
Interface (referred to henceforth as GSS-API). [STANDARDS-TRACK
Ramos Informational [Page 22]
RFC 2299 Summary of 2200-2299 January 1999
2202 Cheng Sep 1997 Test Cases for HMAC-MD5
HMAC-SHA-1
This document provides two sets of test cases for HMAC-MD5 and HMAC
SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of
HMAC [HMAC] message authentication function using the MD5 [MD5]
function and the SHA-1 [SHA] hash function. This memo
information for the Internet community. This memo does not specify
Internet standard of any kind
2201 Ballardie Sep 1997 Core Based Trees (CBT
Multicast Routing
CBT is a multicast routing architecture that builds a single
tree per group which is shared by all of the group's senders
receivers. This memo defines an Experimental Protocol for the
community
2200 IAB Jun 1997 INTERNET OFFICIAL
A discussion of the standardization process and the RFC document
is presented first, followed by an explanation of the terms.
6.2 - 6.10 contain the lists of protocols in each stage
standardization. Finally are pointers to references and contacts
further information. [STANDARDS-TRACK
Security
There are no security issues in this Informational RFC
Author's
Alegre
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: ramos@isi.
Ramos Informational [Page 23]
RFC 2299 Summary of 2200-2299 January 1999
Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Ramos Informational [Page 24]
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
