As per Relevance of the word describe, we have this rfc below:
Network Working Group A.
Request for Comments: 2599
Category: Informational March 2000
Request for Comments
RFC Numbers 2500-2599
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 2500
through RFCs 2599. 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 (2000). 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
--- ------ ---- -----
2599 Delacruz Mar 2000 Request for Comments
This memo
2598 Jacobson Jun 1999 An Expedited Forwarding
The definition of PHBs (per-hop forwarding behaviors) is a critical
of the work of the Diffserv Working Group. This document describes
PHB called Expedited Forwarding. [STANDARDS-TRACK
DeLaCruz Informational [Page 1]
RFC 2599 Summary of 2500-2599 March 2000
2597 Heinanen Jun 1999 Assured Forwarding PHB
This document defines a general use Differentiated Services (DS
Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF).
[STANDARDS-TRACK
2596 Wahl May 1999 Use of Language Codes in
This document describes how language codes are carried in LDAP and
to be interpreted by LDAP servers. [STANDARDS-TRACK
2595 Newman Jun 1999 Using TLS with IMAP, POP
and
Recognizing that such sites will desire simple password
in combination with TLS encryption, this specification defines the
SASL mechanism for use with protocols which lack a simple
authentication command such as ACAP and SMTP. [STANDARDS-TRACK
2594 Hazewinkel May 1999 Definitions of
Objects for WWW
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 objects for managing World Wide
(WWW) services. [STANDARDS-TRACK
2593 Schoenwaelder May 1999 Script MIB
Protocol Version 1.0
The Script MIB extensibility protocol (SMX) defined in this
separates language specific runtime systems from language
Script MIB implementations. This memo defines an Experimental
for the Internet community
DeLaCruz Informational [Page 2]
RFC 2599 Summary of 2500-2599 March 2000
2592 Levi May 1999 Definitions of Managed
for the Delegation
Management
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it describes a set of managed objects that allow
delegation of management scripts to distributed managers
[STANDARDS-TRACK
2591 Levi May 1999 Definitions of Managed
for Scheduling
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community
[STANDARDS-TRACK
2590 Conta May 1999 Transmission of IPv6
over Frame Relay
This memo describes mechanisms for the transmission of IPv6 packets
Frame Relay networks. [STANDARDS-TRACK
2589 Yaacovi May 1999 Lightweight Directory
Protocol (v3): Extensions
Dynamic Directory
This document defines the requirements for dynamic directory
and specifies the format of request and response extended operations
supporting client-server interoperation in a dynamic
environment. [STANDARDS-TRACK
2588 Finlayson May 1999 IP Multicast and
In this document, we discuss the issues surrounding the traversal of
multicast traffic across a firewall, and describe possible ways in
a firewall can implement and control this traversal. We also
why some firewall mechanisms - such as SOCKS - that were
specifically for unicast traffic, are less appropriate for multicast
This memo provides information for the Internet community
DeLaCruz Informational [Page 3]
RFC 2599 Summary of 2500-2599 March 2000
2587 Boeyen Jun 1999 Internet X.509 Public
Infrastructure LDAPv2
The schema defined in this document is a minimal schema to support
in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-
components are specified here. [STANDARDS-TRACK
2586 Salsman May 1999 The Audio/L16 MIME content
This document defines the audio/L16 MIME type, a reasonable
audio format for use in Internet applications. This memo
information for the Internet community
2585 Housley May 1999 Internet X.509 Public
Infrastructure
The protocol
Protocols: FTP and
The protocol conventions described in this document satisfy some of
operational requirements of the Internet Public Key
(PKI). This document specifies the conventions for using the
Transfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP)
obtain certificates and certificate revocation lists (CRLs) from
repositories. [STANDARDS-TRACK
2584 Clouston May 1999 Definitions of Managed
for APPN/HPR in IP
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 HPR (
Performance Routing) network devices which have the capability
communicate in IP (Internet Protocol) networks. [STANDARDS-TRACK
2583 Carlson May 1999 Guidelines for Next Hop
(NHC)
This document provides guidelines for developers of the Next
Resolution Protocol Clients (NHC). The intent is to define
interaction between the NHC code and the TCP/IP protocol stack of
local host operating system. This memo provides information for
Internet community
DeLaCruz Informational [Page 4]
RFC 2599 Summary of 2500-2599 March 2000
2582 Floyd Apr 1999 The NewReno Modification
TCP's Fast Recovery
This document describes a specific algorithm for responding to
acknowledgments, referred to as NewReno. This memo defines
Experimental Protocol for the Internet community
2581 Allman Apr 1999 TCP Congestion
This document defines TCP's four intertwined congestion
algorithms: slow start, congestion avoidance, fast retransmit, and
recovery. In addition, the document specifies how TCP should
transmission after a relatively long idle period, as well as
various acknowledgment generation methods. [STANDARDS-TRACK
2580 McCloghrie Apr 1999 Conformance Statements for SMIv
Collections of related objects are defined in MIB modules. It may
useful to define the acceptable lower-bounds of implementation,
with the actual level of implementation achieved. It is the
of this document to define the notation used for these purposes
[STANDARDS-TRACK
2579 McCloghrie Apr 1999 Textual Conventions for SMIv
It is the purpose of this document to define the initial set of
conventions available to all MIB modules. [STANDARDS-TRACK
2578 McCloghrie Apr 1999 Structure of
Information Version 2 (SMIv2)
It is the purpose of this document, the Structure of
Information Version 2 (SMIv2), to define that adapted subset, and
assign a set of associated administrative values. [STANDARDS-TRACK
2577 Allman May 1999 FTP Security
This document provides suggestions for system administrators and
implementing FTP servers that will decrease the security
associated with FTP. This memo provides information for the
community
DeLaCruz Informational [Page 5]
RFC 2599 Summary of 2500-2599 March 2000
2576 Frye March 2000 Coexistence between Version 1,
Version 2, and Version 3
the Internet-standard
Management
The purpose of this document is to describe coexistence
version 3 of the Internet-standard Network Management Framework
(SNMPv3), version 2 of the Internet-standard Network
Framework (SNMPv2), and the original Internet-standard
Management Framework (SNMPv1). [STANDARDS TRACK
2575 Wijnen Apr 1999 View-based Access
Model (VACM) for the
Network
Protocol (SNMP
This document describes the View-based Access Control Model for use
the SNMP architecture (RFC2571). 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
2574 Blumenthal Apr 1999 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. It defines the
of Procedure for providing SNMP message level security. This
also includes a MIB for remotely monitoring/managing the
parameters for this Security Model. [STANDARDS-TRACK
2573 Levi Apr 1999 SNMP
This memo describes five types of SNMP applications which make use
an SNMP engine. This memo also defines MIB modules for
targets of management operations, for notification filtering, and
proxy fowarding. [STANDARDS-TRACK
DeLaCruz Informational [Page 6]
RFC 2599 Summary of 2500-2599 March 2000
2572 Case May 1999 Message Processing
Dispatching for the
Network Management
(SNMP
This document describes the Message Processing and Dispatching
SNMP messages within the SNMP architecture. It defines the
for dispatching potentially multiple versions of SNMP messages to
proper SNMP Message Processing Models, and for dispatching PDUs
SNMP applications. This document also describes one
Processing Model - the SNMPv3 Message Processing Model
[STANDARDS-TRACK
2571 Harrington May 1999 An Architecture for
SNMP Management
This document describes an architecture for describing SNMP
Frameworks. [STANDARDS-TRACK
2570 Case Apr 1999 Introduction to Version 3
of the Internet-
Network Management
The purpose of this document is to provide an overview of the
version of the Internet-standard Management Framework, termed the
version 3 Framework (SNMPv3). This memo provides information for
Internet community
2569 Herriot Apr 1999 Mapping between LPD and
This document is one of a set of documents, which together describe
aspects of a new Internet Printing Protocol (IPP). One of the
of this document is to compare the functionality of the two protocols
Another purpose is to facilitate implementation of gateways between
and IPP. This memo defines an Experimental Protocol for the
community
DeLaCruz Informational [Page 7]
RFC 2599 Summary of 2500-2599 March 2000
2568 Zilles Apr 1999 Rationale for the Structure
the Model and Protocol for
Internet Printing
This document describes IPP from a high level view, defines a
for the various documents that form the suite of IPP specifications,
gives background and rationale for the IETF working group's
decisions. This memo defines an Experimental Protocol for the
community
2567 Wright Apr 1999 Design Goals for an
Printing
This document takes a broad look at distributed printing functionality
and it enumerates real-life scenarios that help to clarify the
that need to be included in a printing protocol for the Internet.
identifies requirements for three types of users: end users, operators
and administrators. This memo defines an Experimental Protocol for
Internet community
2566 deBry Apr 1999 Internet
Protocol/1.0: Model
This document describes a simplified model consisting of
objects, their attributes, and their operations that is independent
encoding and transport. This document also addresses security
internationalization, and directory issues. This memo defines
Experimental Protocol for the Internet community
2565 Herriot Apr 1999 Internet
Protocol/1.0: Encoding
This document defines the rules for encoding IPP operations and
attributes into a new Internet mime media type called "application/ipp".
This document also defines the rules for transporting over HTTP
message body whose Content-Type is "application/ipp". This
defines an Experimental protocol for the Internet community
DeLaCruz Informational [Page 8]
RFC 2599 Summary of 2500-2599 March 2000
2564 Kalbfleisch May 1999 Application Management
This memo defines a standards track portion of the
Information Base (MIB) for use with network management protocols in
Internet Community. In particular, it defines objects used for
management of applications. [STANDARDS-TRACK
2563 Troll May 1999 DHCP Option to
Stateless Auto-Configuration
IPv4
This document describes a mechanism by which DHCP servers are able
tell clients that they do not have an IP address to offer, and that
client should not generate an IP address it's own. [STANDARDS-TRACK
2562 White Apr 1999 Definitions of Protocol
Managed Objects for TN3270
Response Time Collection
SMIv2 (TN3270E-RT-MIB
This memo defines the protocol and the Management Information Base (MIB
for performing response time data collection on TN3270 and TN3270
sessions by a TN3270E server. [STANDARDS-TRACK
2561 White Apr 1999 Base Definitions of
Objects for TN3270E Using SMIv
This memo defines a Management Information Base (MIB) for
and managing TN3270E servers. The MIB defined by this memo
generic support for both host and gateway TN3270E
implementations. [STANDARDS-TRACK
2560 Myers Jun 1999 X.509 Internet Public
Infrastructure
Certificate
Protocol -
This document specifies a protocol useful in determining the
status of a digital certificate without requiring CRLs. [STANDARDS
TRACK
DeLaCruz Informational [Page 9]
RFC 2599 Summary of 2500-2599 March 2000
2559 Boeyen Apr 1999 Internet X.509 Public
Infrastructure
Protocols - LDAPv
Specifically, this document addresses requirements to provide access
Public Key Infrastructure (PKI) repositories for the purposes
retrieving PKI information and managing that same information
[STANDARDS-TRACK
2558 Tesink Mar 1999 Definitions of Managed
for the SONET/SDH Interface
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 Synchronous
Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces.
document is a companion to the documents that define Managed Objects
the DS1/E1/DS2/E2 and DS3/E3 Interface Types. [STANDARDS-TRACK
2557 Palme Mar 1999 MIME Encapsulation
Aggregate Documents,
as HTML (MHTML
This document a) defines the use of a MIME multipart/related
to aggregate a text/html root resource and the subsidiary resources
references, and b) specifies a MIME content-header (Content-Location
that allow URIs in a multipart/related text/html root body part
reference subsidiary resources in other body parts of the
multipart/related structure. [STANDARDS-TRACK
2556 Bradner Mar 1999 OSI connectionless
services on top of
Applicability Statement
Historic
RFC 1240, "OSI connectionless transport services on top of UDP",
published as a Proposed Standard in June 1991 but at this time there
not seem to be any implementations which follow RFC 1240. In
there is a growing concern over using UDP-based transport protocols
environments where congestion is a possibility This memo
information for the Internet community
DeLaCruz Informational [Page 10]
RFC 2599 Summary of 2500-2599 March 2000
2555 RFC Editor Apr 1999 30 Years of
The rest of this document contains a brief recollection from the
RFC Editor Joyce K. Reynolds, followed by recollections from
pioneers: Steve Crocker who wrote RFC 1, Vint Cerf whose long-
vision continues to guide us, and Jake Feinler who played a key role
the middle years of the RFC series. This memo provides information
the Internet community
2554 Myers Mar 1999 SMTP Service
This document defines an SMTP service extension [ESMTP] whereby an
client may indicate an authentication mechanism to the server,
an authentication protocol exchange, and optionally negotiate a
layer for subsequent protocol interactions. [STANDARDS-TRACK
2553 Gilligan Mar 1999 Basic Socket
Extensions for IPv
TCP/IP applications written using the sockets API have in the
enjoyed a high degree of portability and we would like the
portability with IPv6 applications. But changes are required to
sockets API to support IPv6 and this memo describes these changes
These include a new socket address structure to carry IPv6 addresses
new address conversion functions, and some new socket options.
memo provides information for the Internet community
2552 Blinov Apr 1999 Architecture for
Brokerage in the ACTS
This memo introduces a domain and supplier independent
architecture for information brokerage, designed as part of the
project GAIA (Generic Architecture for Information Availability).
memo provides information for the Internet community
DeLaCruz Informational [Page 11]
RFC 2599 Summary of 2500-2599 March 2000
2551 Bradner 1 Apr 1999 The Roman Standards Process --
Revision
This memo documents the process used by the Roman community for
standardization of protocols and procedures. It defines the stages
the standardization process, the requirements for moving a
between stages and the types of documents used during this process.
also addresses the intellectual property rights and copyright
associated with the standards process
2550 Glassman 1 Apr 1999 Y10K and
This specification provides a solution to the "Y10K" problem which
also been called the "YAK" problem (hex) and the "YXK" problem (
numerals). This memo provides information for the Internet community
2549 Waitzman 1 Apr 1999 IP over Avian Carriers
Quality of
This memo amends RFC 1149, "A Standard for the Transmission of
Datagrams on Avian Carriers", with Quality of Service information.
is an experimental, not recommended standard. This memo defines
Experimental Protocol for the Internet community
2548 Zorn Mar 1999 Microsoft Vendor-
RADIUS
This document describes the set of Microsoft vendor-specific
attributes. This memo provides information for the Internet community
2547 Rosen Mar 1999 BGP/MPLS
This document describes a method by which a Service Provider with an
backbone may provide VPNs (Virtual Private Networks) for its customers
This memo provides information for the Internet community
DeLaCruz Informational [Page 12]
RFC 2599 Summary of 2500-2599 March 2000
2546 Durand Mar 1999 6Bone Routing
This memo identifies guidelines on how 6Bone sites might operate,
that the 6Bone can remain a quality experimentation environment and
avoid pathological situations that have been encountered in the past
It defines the 'best current practice' acceptable in the 6Bone for
configuration of both Interior Gateway Protocols and Exterior
Protocols. This memo provides information for the Internet community
2545 Marques Mar 1999 Use of BGP-4
Extensions for IPv
Inter-Domain
BGP-4 Multiprotocol Extensions (BGP-MP) defines the format of two
attributes (MP_REACH_NLRI and MP_UNREACH_NLRI) that can be used
announce and withdraw the announcement of reachability information
This document defines how compliant systems should make use of
attributes for the purpose of conveying IPv6 routing information
[STANDARDS-TRACK
2544 Bradner Mar 1999 Benchmarking
for Network Interconnect
This document is a republication of RFC 1944 correcting the values
the IP addresses which were assigned to be used as the default
for networking test equipment. This memo provides information for
Internet community
2543 Handley Mar 1999 SIP: Session Initiation
The Session Initiation Protocol (SIP) is an application-layer
(signaling) protocol for creating, modifying and terminating
with one or more participants. [STANDARDS-TRACK
2542 Masinter Mar 1999 Terminology and Goals
Internet
This document defines a number of terms useful for the discussion
Internet Fax. In addition, it describes the goals of the Internet
working group and establishes a baseline of desired
against which protocols for Internet Fax can be judged. This
provides information for the Internet community
DeLaCruz Informational [Page 13]
RFC 2599 Summary of 2500-2599 March 2000
2541 Eastlake Mar 1999 DNS Security
This document discusses these operational aspects for keys
signatures used in connection with the KEY and SIG DNS resource records
This memo provides information for the Internet community
2540 Eastlake Mar 1999 Detached Domain Name
(DNS)
A standard format is defined for representing detached DNS information
This is anticipated to be of use for storing information retrieved
the Domain Name System (DNS), including security information,
archival contexts or contexts not connected to the Internet. This
defines an Experimental Protocol for the Internet community
2539 Eastlake Mar 1999 Storage of Diffie-
Keys in the Domain
System (DNS
A standard method for storing Diffie-Hellman keys in the Domain
System is described which utilizes DNS KEY resource records
[STANDARDS-TRACK
2538 Eastlake Mar 1999 Storing Certificates in
Domain Name System (DNS
Cryptographic public key are frequently published and their
demonstrated by certificates. A CERT resource record (RR) is defined
that such certificates and related certificate revocation lists can
stored in the Domain Name System (DNS). [STANDARDS-TRACK
2537 Eastlake Mar 1999 RSA/MD5 KEYs and SIGs
the Domain Name System (DNS
A standard method for storing RSA keys and and RSA/MD5 based
in the Domain Name System is described which utilizes DNS KEY and
resource records. [STANDARDS-TRACK
DeLaCruz Informational [Page 14]
RFC 2599 Summary of 2500-2599 March 2000
2536 Eastlake Mar 1999 DSA KEYs and SIGs in
Domain Name System (DNS
A standard method for storing US Government Digital Signature
keys and signatures in the Domain Name System is described
utilizes DNS KEY and SIG resource records. [STANDARDS-TRACK
2535 Eastlake Mar 1999 Domain Name System
This document incorporates feedback on RFC 2065 from early
and potential users. [STANDARDS-TRACK
2534 Masinter Mar 1999 Media Features for Display
Print, and
This specification defines some common media features for
image resolution, size, color, and image representation methods that
common to web browsing, printing, and facsimile applications
[STANDARDS-TRACK
2533 Klyne Mar 1999 A Syntax for Describing
Feature
This document introduces and describes a syntax that can be used
define feature sets which are formed from combinations and
involving individual media features. [STANDARDS-TRACK
2532 Masinter Mar 1999 Extended Facsimile
Internet
This document describes extensions to "Simple Mode of Facsimile
Internet Mail", and describes additional features,
transmission of enhanced document characteristics (higher resolution
color) and confirmation of delivery and processing. [STANDARDS-TRACK
2531 Klyne Mar 1999 Content Feature Schema
Internet
This document defines a content feature schema that is a profile of
media feature registration mechanisms for use in performing
identification between extended Internet fax systems. [STANDARDS-TRACK
DeLaCruz Informational [Page 15]
RFC 2599 Summary of 2500-2599 March 2000
2530 Wing Mar 1999 Indicating Supported
Features Using Extensions
DSN and
This memo describes a format for generating Message
Notifications and Delivery Status Notifications which contain
information. [STANDARDS-TRACK
2529 Carpenter Mar 1999 Transmission of IPv6 over IPv
Domains without Explicit
This memo specifies the frame format for transmission of IPv6 (IPV6)
packets and the method of forming IPv6 link-local addresses over IPv
domains. It also specifies the content of the Source/Target Link-
Address option used in the Router Solicitation, Router Advertisement
Neighbor Solicitation, and Neighbor Advertisement and Redirect messages
when those messages are transmitted on an IPv4 multicast network
[STANDARDS-TRACK
2528 Housley Mar 1999 Internet X.509 Public
This specification contains guidance on the use of the Internet
Key Infrastructure certificates to convey Key Exchange Algorithm (KEA
keys. This memo provides information for the Internet community
2527 Chokhani Mar 1999 Internet X.509 Public
Infrastructure
Policy and
Practices
This document presents a framework to assist the writers of
policies or certification practice statements for
authorities and public key infrastructures. In particular,
framework provides a comprehensive list of topics that potentially (
the writer's discretion) need to be covered in a certificate
definition or a certification practice statement. This memo
information for the Internet community
DeLaCruz Informational [Page 16]
RFC 2599 Summary of 2500-2599 March 2000
2526 Johnson Mar 1999 Reserved IPv6 Subnet
This document defines a set of reserved anycast addresses within
subnet prefix, and lists the initial allocation of these reserved
anycast addresses. [STANDARDS-TRACK
2525 Paxson Mar 1999 Known TCP
This memo catalogs a number of known TCP implementation problems.
memo provides information for the Internet community
2524 Banan Feb 1999 Neda's Efficient
Submission and Delivery (EMSD
Protocol
Version 1.3
This specification narrowly focuses on submission and delivery of
mail messages with a clear emphasis on efficiency. This memo
information for the Internet community
2523 Karn Mar 1999 Photuris: Extended
and
Photuris is a session-key management protocol. Extensible Exchange
Schemes are provided to enable future implementation changes
affecting the basic protocol. This document defines an
Protocol for the Internet community
2522 Karn Mar 1999 Photuris: Session-
Management
This document defines the basic protocol mechanisms. This
defines an Experimental Protocol for the Internet community
2521 Karn Mar 1999 ICMP Security Failures
This document specifies ICMP messages for indicating failures when
IP Security Protocols (AH and ESP). This document defines
Experimental Protocol for the Internet community
DeLaCruz Informational [Page 17]
RFC 2599 Summary of 2500-2599 March 2000
2520 Luciani Feb 1999 NHRP with Mobile
is document describes an extension to NHRP which would allow Mobile
to perform a registration with and attach to an NHS in their home LIS
an authenticated manner. This memo defines an Experimental Protocol
the Internet community
2519 Chen Feb 1999 A Framework for Inter-
Route
This document presents a framework for inter-domain route
and shows an example router configuration which 'implements'
framework. This memo provides information for the Internet
2518 Goland Feb 1999 HTTP Extensions
Distributed Authoring --
This document specifies a set of methods, headers, and content-
ancillary to HTTP/1.1 for the management of resource properties
creation and management of resource collections, namespace manipulation
and resource locking (collision avoidance). [STANDARDS-TRACK
2517 Moats Feb 1999 Building Directories from DNS
Experiences from
This memo discusses lessons that were learned during InterNIC
and Database Services' development and operation of WWWSeeker,
application that finds a web site given information about the name
location of an organization. This memo provides information for
Internet community
2516 Mamakos Feb 1999 A Method for Transmitting
Over Ethernet (PPPoE
This document describes how to build PPP sessions and encapsulate
packets over Ethernet. This memo provides information for the
community
DeLaCruz Informational [Page 18]
RFC 2599 Summary of 2500-2599 March 2000
2515 Tesink Feb 1999 Definitions of Managed
for ATM
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
2514 Noto Feb 1999 Definitions of
Conventions and OBJECT
IDENTITIES for ATM
This memo describes Textual Conventions and OBJECT-IDENTITIES used
managing ATM-based interfaces, devices, networks and services
[STANDARDS-TRACK
2513 McCloghrie Feb 1999 Managed Objects
Controlling the
and Storage of
Information for Connection
Oriented
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 controlling
collection and storage of accounting information for connection-
networks such as ATM. [STANDARDS-TRACK
2512 McCloghrie Feb 1999 Accounting Information for
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
memo defines a set of ATM-specific accounting information which can
collected for connections on ATM networks. [STANDARDS-TRACK
2511 Myers Mar 1999 Internet X.509
Request Message
This document describes the Certificate Request Message Format (CRMF).
[STANDARDS-TRACK
DeLaCruz Informational [Page 19]
RFC 2599 Summary of 2500-2599 March 2000
2510 Adams Mar 1999 Internet X.509 Public
Infrastructure
Management
This document describes the Internet X.509 Public Key
(PKI) Certificate Management Protocols. [STANDARDS-TRACK
2509 Engan Feb 1999 IP Header Compression over
This document describes an option for negotiating the use of
compression on IP datagrams transmitted over the Point-to-
Protocol. It defines extensions to the PPP Control Protocols for IPv
and IPv6. [STANDARDS-TRACK
2508 Casner Feb 1999 Compressing IP/UDP/RT
for Low-Speed Serial
This document describes a method for compressing the headers
IP/UDP/RTP datagrams to reduce overhead on low-speed serial links
[STANDARDS-TRACK
2507 Degermark Feb 1999 IP Header
This document describes how to compress multiple IP headers and TCP
UDP headers per hop over point to point links. [STANDARDS-TRACK
2506 Holtman Mar 1999 Media Feature Tag
This document defines a registration procedure which uses the
Assigned Numbers Authority (IANA) as a central registry for the
feature vocabulary. This document specifies an Internet Best
Practices for the Internet Community, and requests discussion
suggestions for improvements
2505 Lindberg Feb 1999 Anti-Spam Recommendations
SMTP
This memo gives a number of implementation recommendations for SMTP
MTAs (Mail Transfer Agents, e.g. sendmail,) to make them more capable
reducing the impact of spam. This document specifies an Internet
Current Practices for the Internet Community, and requests
and suggestions for improvements
DeLaCruz Informational [Page 20]
RFC 2599 Summary of 2500-2599 March 2000
2504 Guttman Feb 1999 Users' Security
The Users' Security Handbook is the companion to the Site
Handbook (SSH). It is intended to provide users with the
they need to help keep their networks and systems secure. This
provides information for the Internet community
2503 Moulton Feb 1999 MIME Types for Use with
ISO ILL
This memorandum describes a set of MIME types for use with the
Interlibrary Loan Protocol (ISO 10160/10161). This memo
information for the Internet community
2502 Pullen Feb 1999 Limitations of Internet
Suite for Distributed
the Large Multicast
This memo defines services that LSMA has found to be required,
aspects of the Internet protocols that LSMA has found to need
development in order to meet these requirements. This memo
information for the Internet community
2501 Corson Jan 1999 Mobile Ad hoc Networking (MANET):
Routing Protocol
Issues and
This memo first describes the characteristics of Mobile Ad hoc
(MANETs), and their idiosyncrasies with respect to traditional
hardwired packet networks. It then discusses the effect
differences have on the design and evaluation of network
protocols with an emphasis on routing performance
considerations. This memo provides information for the
community
2500 IETF Jun 1999 Internet Official
This memo summarizes the status of Internet protocols
specifications. [STANDARDS-TRACK
DeLaCruz Informational [Page 21]
RFC 2599 Summary of 2500-2599 March 2000
Security
This memo does not affect the technical security of the Internet,
it does cite some security specifications
Author's
Alison De La
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: delacruz@isi.
DeLaCruz Informational [Page 22]
RFC 2599 Summary of 2500-2599 March 2000
Full Copyright
Copyright (C) The Internet Society (2000). 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
Funding for the RFC Editor function is currently provided by
Internet Society
DeLaCruz Informational [Page 23]
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
