As per Relevance of the word provides, we have this rfc below:
Network Working Group S.
Request for Comments: 2899
Category: Informational May 2001
Request for Comments
RFC Numbers 2800-2899
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 2800
through RFCs 2899. 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 (2001). 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
--- ------ ---- -----
2899 Ginoza May 2001 Request for Comments
This memo
2898 Kaliski Sep 2000 PKCS #5: Password-
Cryptography
Version 2.0
This document provides recommendations for the implementation
password-based cryptography, covering key derivation functions
encryption schemes, message-authentication schemes, and ASN.1
identifying the techniques. This memo provides information for
Internet community
Ginoza Informational [Page 1]
RFC 2899 Summary of 2800-2899 May 2001
2897 Cromwell Aug 2000 Proposal for an MGCP
Audio
This document is a proposal to add a new event/signal package to
MGCP (Media Gateway Control Protocol) protocol to control an ARF (
Resource Function) which may reside on a Media Gateway or
Audio Server. This memo provides information for the
community
2896 Bierman Aug 2000 Remote Network Monitoring
Protocol Identifier
This memo contains various protocol identifier examples, which can
used to produce valid protocolDirTable INDEX encodings, as defined
the Remote Network Monitoring MIB and the RMON Protocol
Reference. This memo provides information for the Internet community
2895 Bierman Aug 2000 Remote Network Monitoring
Protocol Identifier
This memo defines a notation describing protocol layers in a
encapsulation, specifically for use in encoding INDEX values for
protocolDirTable, found in the RMON-2 MIB. [STANDARDS TRACK
2894 Crawford Aug 2000 Router Renumbering for IPv
This document defines a mechanism called Router Renumbering ("RR")
allows address prefixes on routers to be configured and
almost as easily as the combination of Neighbor Discovery and
Autoconfiguration works for hosts. [STANDARDS TRACK
2893 Gilligan Aug 2000 Transition Mechanisms for IPv
Hosts and
This document specifies IPv4 compatibility mechanisms that can
implemented by IPv6 hosts and routers. [STANDARDS TRACK
Ginoza Informational [Page 2]
RFC 2899 Summary of 2800-2899 May 2001
2892 Tsiang Aug 2000 The Cisco SRP MAC
This document specifies the MAC layer protocol, "Spatial Reuse Protocol
(SRP) for use with ring based media. This is a second version of
protocol (V2). This memo provides information for the
community
2891 Howes Aug 2000 LDAP Control Extension
Server Side Sorting of
This document describes two LDAPv3 control extensions for server
sorting of search results. These controls allows a client to
the attribute types and matching rules a server should use
returning the results to an LDAP search request. [STANDARDS TRACK
2890 Dommety Sep 2000 Key and Sequence
Extensions to
This document describes extensions by which two fields, Key and
Number, can be optionally carried in the GRE Header. [STANDARDS TRACK
2889 Mandeville Aug 2000 Benchmarking Methodology
LAN Switching
This document is intended to provide methodology for the benchmarking
local area network (LAN) switching devices. This memo
information for the Internet community
2888 Srisuresh Aug 2000 Secure Remote Access with L2
The objective of this document is to extend security characteristics
IPsec to remote access users, as they dial-in through the Internet
This memo provides information for the Internet community
2887 Handley Aug 2000 The Reliable Multicast
Space for Bulk Data
This document provides an overview of the design space and the ways
which application constraints affect possible solutions. This
provides information for the Internet community
Ginoza Informational [Page 3]
RFC 2899 Summary of 2800-2899 May 2001
2886 Taylor Sep 2000 Megaco
This document records the errors found in the Megaco/H.248
document, along with the changes proposed in the text of that
to resolve them. [STANDARDS TRACK
2885 Cuervo Sep 2000 Megaco Protocol version 0.8
This document is common text with Recommendation H.248 as
in Geneva, February 2000. It must be read in conjunction with
Megaco Errata, RFC 2886. [STANDARDS TRACK
2884 Hadi Salim Jul 2000 Performance Evaluation
Explicit
Notification (ECN) in
This memo presents a performance study of the Explicit
Notification (ECN) mechanism in the TCP/IP protocol using
implementation on the Linux Operating System. This memo
information for the Internet community
2883 Floyd Jul 2000 An Extension to the
Acknowledgement (SACK)
for
This note defines an extension of the Selective Acknowledgement (SACK
Option for TCP. [STANDARDS TRACK
2882 Mitton Jul 2000 Network Access
Requirements: Extended
This document describes current practices implemented in NAS
that go beyond the scope of the RADIUS (Remote Authentication Dial
User Service) RFCs 2138, 2139. This memo provides information for
Internet community
Ginoza Informational [Page 4]
RFC 2899 Summary of 2800-2899 May 2001
2881 Mitton Jul 2000 Network Access
Requirements Next
(NASREQNG) NAS
This document describes the terminology and gives a model of
Network Access Server (NAS). This memo provides information for
Internet community
2880 McIntyre Aug 2000 Internet Fax T.30
This document describes how to map Group 3 fax capability
bits, described in ITU T.30, into the Internet fax feature
described in "Content feature schema for Internet fax". This
provides information for the Internet community
2879 Klyne Aug 2000 Content Feature Schema
Internet Fax (V2)
This document defines a content media feature schema for Internet fax
[STANDARDS TRACK
2878 Higashiyama Jul 2000 PPP Bridging Control
(BCP
This document defines the Network Control Protocol for establishing
configuring Remote Bridging for PPP links. [STANDARDS TRACK
2877 Murphy, Jr. Jul 2000 5250 Telnet
This memo describes the interface to the IBM 5250 Telnet server
allows client Telnet to request a Telnet terminal or printer
using a specific device name. This memo provides information for
Internet community
2876 Pawling Jul 2000 Use of the KEA and
Algorithms in
This document describes the conventions for using the Key
Algorithm (KEA) and SKIPJACK encryption algorithm in conjunction
the Cryptographic Message Syntax [CMS] enveloped-data and encrypted
data content types. This memo provides information for the
community
Ginoza Informational [Page 5]
RFC 2899 Summary of 2800-2899 May 2001
2875 Prafullchandra Jul 2000 Diffie-
Proof-of-Possession
This document describes two methods for producing an integrity
value from a Diffie-Hellman key pair. [STANDARDS TRACK
2874 Crawford Jul 2000 DNS Extensions to Support IPv
Address Aggregation
This document defines changes to the Domain Name System to
renumberable and aggregatable IPv6 addressing. [STANDARDS TRACK
2873 Xiao Jun 2000 TCP Processing of the IPv
Precedence
This memo describes a conflict between TCP and DiffServ on the use
the three leftmost bits in the TOS octet of an IPv4 header. [
TRACK
2872 Bernet Jun 2000 Application and
Application Identity
Element for Use with
RSVP signaling messages typically include policy data objects, which
turn contain policy elements. Policy elements may describe user and/
application information, which may be used by RSVP aware
elements to apply appropriate policy decisions to a traffic flow.
memo details the usage of policy elements that provide
information. [STANDARDS TRACK
2871 Rosenberg Jun 2000 A Framework for
Routing over
This document serves as a framework for Telephony Routing over
(TRIP), which supports the discovery and exchange of IP
gateway routing tables between providers. This memo
information for the Internet community
Ginoza Informational [Page 6]
RFC 2899 Summary of 2800-2899 May 2001
2870 Bush Jun 2000 Root Name Server
The primary focus of this document is to provide guidelines
operation of the root name servers. This document specifies an
Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
2869 Rigney Jun 2000 RADIUS
This document describes additional attributes for
authentication, authorization and accounting information between
Network Access Server (NAS) and a shared Accounting Server using
Remote Authentication Dial In User Service (RADIUS) protocol
in RFC 2865 and RFC 2866. This memo provides information for
Internet community
2868 Zorn Jun 2000 RADIUS Attributes for
Protocol
This document defines a set of RADIUS (Remote Authentication Dial
User Service) attributes designed to support the provision of
tunneling in dial-up networks. This memo provides information for
Internet community
2867 Zorn Jun 2000 RADIUS
Modifications for
Protocol
This document defines new RADIUS (Remote Authentication Dial In
Service) accounting Attributes and new values for the existing Acct
Status-Type Attribute designed to support the provision of
tunneling in dial-up networks. This memo provides information for
Internet community
2866 Rigney Jun 2000 RADIUS
This document describes a protocol for carrying accounting
between a Network Access Server and a shared Accounting Server.
memo provides information for the Internet community
Ginoza Informational [Page 7]
RFC 2899 Summary of 2800-2899 May 2001
2865 Rigney Jun 2000 Remote Authentication Dial
User Service (RADIUS
This document describes a protocol for carrying authentication
authorization, and configuration information between a Network
Server which desires to authenticate its links and a
Authentication Server. [STANDARDS TRACK
2864 McCloghrie Jun 2000 The Inverted Stack
Extension to the
Group
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 which provide an
mapping of the interface stack table used for managing
interfaces. [STANDARDS TRACK
2863 McCloghrie Jun 2000 The Interfaces Group
This memo discusses the 'interfaces' group of MIB-II, especially
experience gained from the definition of numerous media-specific
modules for use in conjunction with the 'interfaces' group for
various sub-layers beneath the internetwork-layer. It
clarifications to, and extensions of, the architectural issues
the MIB-II model of the 'interfaces' group. [STANDARDS TRACK
2862 Civanlar Jun 2000 RTP Payload Format
Real-Time
This document describes an RTP payload format for transporting
coordinates of a dynamic pointer that may be used during a presentation
[STANDARDS TRACK
2861 Handley Jun 2000 TCP Congestion
This document describes a simple modification to TCP's
control algorithms to decay the congestion window cwnd after
transition from a sufficiently-long application-limited period,
using the slow-start threshold ssthresh to save information about
previous value of the congestion window. This memo defines
Experimental Protocol for the Internet community
Ginoza Informational [Page 8]
RFC 2899 Summary of 2800-2899 May 2001
2860 Carpenter Jun 2000 Memorandum of
Concerning the Technical
of the Internet
Numbers
This document places on record the text of the Memorandum
Understanding concerning the technical work of the IANA that was
on March 1, 2000 between the IETF and ICANN, and ratified by the
Board on March 10, 2000. This memo provides information for
Internet community
2859 Fang Jun 2000 A Time Sliding Window
This memo defines a
This memo defines a Time Sliding Window Three Colour Marker (TSWTCM),
which can be used as a component in a Diff-Serv traffic conditioner
This memo defines an Experimental Protocol for the Internet community
2858 Bates Jun 2000 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...). [STANDARDS TRACK
2857 Keromytis Jun 2000 The Use of HMAC-RIPEMD-160-96
within ESP and
This memo describes the use of the HMAC algorithm in conjunction
the RIPEMD-160 algorithm as an authentication mechanism within
revised IPSEC Encapsulating Security Payload (ESP) and the revised
Authentication Header (AH). [STANDARDS TRACK
2856 Bierman Jun 2000 Textual Conventions
Additional High Capacity
This memo specifies new textual conventions for additional high
data types, intended for SNMP implementations which already support
Counter64 data type. [STANDARDS TRACK
Ginoza Informational [Page 9]
RFC 2899 Summary of 2800-2899 May 2001
2855 Fujisawa Jun 2000 DHCP for IEEE 1394
This memo describes specific usage of some fields of DHCP (Dynamic
Configuration Protocol) messages. IEEE Std 1394-1995 is a standard
a High Performance Serial Bus. Since 1394 uses a different link-
addressing method than conventional IEEE802/Ethernet, the usage of
fields must be clarified to achieve interoperability. [STANDARDS TRACK
2854 Connolly Jun 2000 The 'text/html' Media
This document summarizes the history of HTML development, and
the "text/html" MIME type by pointing to the relevant W3
recommendations. This memo provides information for the
community
2853 Kabat Jun 2000 Generic Security Service
Version 2 : Java
This document specifies the Java bindings for GSS-API (Generic
Service Application Program Interface) which is described at a
independent conceptual level in RFC 2743. [STANDARDS TRACK
2852 Newman Jun 2000 Deliver By SMTP
This memo defines a mechanism whereby a SMTP client can request,
transmitting a message to a SMTP server, that the server deliver
message within a prescribed period of time. [STANDARDS TRACK
2851 Daniele Jun 2000 Textual Conventions
Internet Network
This MIB module defines textual conventions to represent commonly
Internet network layer addressing information. [STANDARDS TRACK
2850 IAB May 2000 Charter of the
Architecture Board (IAB
This memo documents the composition, selection, roles, and
of the Internet Architecture Board. It replaces RFC 1601.
document specifies an Internet Best Current Practices for the
Community, and requests discussion and suggestions for improvements
Ginoza Informational [Page 10]
RFC 2899 Summary of 2800-2899 May 2001
2849 Good Jun 2000 The LDAP Data
Format (LDIF) -
This document describes a file format suitable for describing
information or modifications made to directory information. [
TRACK
2848 Petrack Jun 2000 The PINT Service Protocol
Extensions to SIP and SDP
IP Access to Telephone
This document contains the specification of the PINT Service
1.0, which defines a protocol for invoking certain telephone
from an IP network. [STANDARDS TRACK
2847 Eisler Jun 2000 LIPKEY - A Low
Public Key Mechanism Using
This memorandum describes a method whereby one can use GSS-API (
Security Service Application Program Interface) to supply a
channel between a client and server, authenticating the client with
password, and a server with a public key certificate. [STANDARDS TRACK
2846 Allocchio Jun 2000 GSTN Address
Extensions in E-mail
This memo defines a full syntax for a specific application in
there is a need to represent GSTN (Global Switched Telephone Network
addressing and Internet addressing. [STANDARDS TRACK
2845 Vixie May 2000 Secret Key
Authentication for DNS (TSIG
This protocol allows for transaction level authentication using
secrets and one way hashing. It can be used to authenticate
updates as coming from an approved client, or to authenticate
as coming from an approved recursive name server. [STANDARDS TRACK
Ginoza Informational [Page 11]
RFC 2899 Summary of 2800-2899 May 2001
2844 Przygienda May 2000 OSPF over ATM and Proxy-
This memo specifies, for OSPF implementors and users,
describing how the protocol operates in ATM networks over PVC (
Virtual Connections) and SVC (Switched Virtual Circuit) meshes with
presence of Proxy-PAR (PNNI Augmented Routing). This memo defines
Experimental Protocol for the Internet community
2843 Droz May 2000 Proxy-
The intention of this document is to provide general information
Proxy-PAR (PNNI Augmented Routing). [STANDARDS TRACK
2842 Chandra May 2000 Capabilities
with BGP-4
This document defines new Optional Parameter, called Capabilities,
is expected to facilitate introduction of new capabilities in BGP
providing graceful capability advertisement without requiring that
peering be terminated. [STANDARDS TRACK
2841 Metzger Nov 2000 IP Authentication using
SHA1 with Interleaved
(IP-MAC
This document describes the use of keyed SHA1 (Secure Hash Algorithm
with the IP Authentication Header. This memo defines a
Document for the Internet community
2840 Altman May 2000 TELNET KERMIT
This document describes an extension to the Telnet protocol to allow
negotiation, coordination, and use of the Kermit file transfer
management protocol over an existing Telnet protocol connection.
memo provides information for the Internet community
2839 da Cruz May 2000 Internet Kermit
This document describes a new file transfer service for the
based on Telnet Protocol for option negotiation and Kermit Protocol
file transfer and management. This memo provides information for
Internet community
Ginoza Informational [Page 12]
RFC 2899 Summary of 2800-2899 May 2001
2838 Zigmond May 2000 Uniform Resource
for Television
This document describes a widely-implemented URI scheme, as World-
Web browsers are starting to appear on a variety of consumer
devices, such as television sets and television set-top boxes, which
capable of receiving television programming from either
broadcast, satellite broadcast, or cable. In this context there is
need to reference television broadcasts using the URI format
in RFC 2396. This memo provides information for the Internet community
2837 Teow May 2000 Definitions of Managed
for the Fabric Element
Fibre Channel
This memo defines an extension to the Management Information Base (MIB
for use with network management protocols in TCP/IP-based internets.
particular, it defines the objects for managing the operations of
Fabric Element portion of the Fibre Channel Standards. [
TRACK
2836 Brim May 2000 Per Hop
Identification
This document defines a binary encoding to uniquely identify PHBs (
Hop Behaviors) and/or sets of PHBs in protocol messages. [
TRACK
2835 Pittet May 2000 IP and ARP over HIPPI-6400
(GSN
This document further specifies a method for resolving IP addresses
HIPPI-6400 (High-Performance Parallel Interface) hardware
(HARP) and for emulating IP broadcast in a logical IP subnet (LIS) as
direct extension of HARP. Furthermore, it is the goal of this memo
define a IP and HARP that will allow interoperability for HIPPI-800
HIPPI-6400 equipment both broadcast and non-broadcast capable networks
[STANDARDS TRACK
Ginoza Informational [Page 13]
RFC 2899 Summary of 2800-2899 May 2001
2834 Pittet May 2000 ARP and IP Broadcast
HIPPI-800
This document specifies a method for resolving IP addresses to
High-Performance Parallel Interface (HIPPI) hardware addresses and
emulating IP broadcast in a logical IP subnet (LIS) as a
extension of HARP (hardware addresses). This memo defines a HARP
will interoperate between HIPPI-800 and HIPPI-6400 (also known
Gigabyte System Network, GSN). This document (when combined with
2067 "IP over HIPPI") obsoletes RFC 1374. [STANDARDS TRACK
2833 Schulzrinne May 2000 RTP Payload for DTMF Digits
Telephony Tones and
This memo describes how to carry dual-tone multifrequency (DTMF
signaling, other tone signals and telephony events in RTP packets
[STANDARDS TRACK
2832 Hollenbeck May 2000 NSI Registry
Protocol (RRP) Version 1.1.0
This document describes a protocol for the registration and
of second level domain names and associated name servers in both
Top Level Domains (gTLDs) and country code Top Level Domains (ccTLDs).
This memo provides information for the Internet community
2831 Leach May 2000 Using Digest Authentication
a SASL
This specification defines how HTTP Digest Authentication can be used
a SASL mechanism for any protocol that has a SASL (Simple
and Security Layer) profile. [STANDARDS TRACK
2830 Hodges May 2000 Lightweight Directory
Protocol (v3): Extension
Transport Layer
This document defines the "Start Transport Layer Security (TLS
Operation" for LDAP. [STANDARDS TRACK
Ginoza Informational [Page 14]
RFC 2899 Summary of 2800-2899 May 2001
2829 Wahl May 2000 Authentication Methods
This document specifies particular combinations of security
which are required and recommended in LDAP implementations. [
TRACK
2828 Shirey May 2000 Internet Security
This Glossary provides abbreviations, explanations, and
for use of information system security terminology. This memo
information for the Internet community
2827 Ferguson May 2000 Network Ingress Filtering
Defeating Denial of
Attacks which employ IP
Address
This paper discusses a simple, effective, and straightforward method
using ingress traffic filtering to prohibit DoS (Denial of Service
attacks which use forged IP addresses to be propagated from 'behind'
Internet Service Provider's (ISP) aggregation point. This
specifies an Internet Best Current Practices for the Internet Community
and requests discussion and suggestions for improvements
2826 IAB May 2000 IAB Technical Comment on
Unique DNS
This document discusses the existence of a globally unique public
space in the Internet called the DNS (Domain Name System). This
space is a hierarchical name space derived from a single,
unique root. It is a technical constraint inherent in the design of
DNS. One root must be supported by a set of coordinated root
administered by a unique naming authority. It is not
feasible for there to be more than one root in the public DNS.
memo provides information for the Internet community
Ginoza Informational [Page 15]
RFC 2899 Summary of 2800-2899 May 2001
2825 IAB May 2000 A Tangled Web: Issues of I18N
Domain Names, and the
Internet
This document is a statement by the Internet Architecture Board. It
not a protocol specification, but an attempt to clarify the range
architectural issues that the internationalization of domain
faces. This memo provides information for the Internet community
2824 Lennox May 2000 Call Processing
Framework and
This document describes an architectural framework we call a
language, as a simple and standardized way for implementing
deploying Internet telephony. A large number of the services we wish
make possible for Internet telephony require fairly
combinations of signalling operations, often in network devices,
complete. It also outlines requirements for such a language. This
provides information for the Internet community
2823 Carlson May 2000 PPP over Simple Data
(SDL) using SONET/SDH
ATM-like
This document extends methods found in the Point-to-Point Protocol (PPP
and RFCs 1662 and 2615 to include a new encapsulation for PPP
Simple Data Link (SDL). SDL provides a standard method for
multi-protocol datagrams over point-to-point links, and RFCs 1662
2615 provide a means to carry PPP over Synchronous Optical
(SONET) and Synchronous Digital Hierarchy (SDH) circuits. SDL
a very low overhead alternative to HDLC-like encapsulation, and can
be used on SONET/SDH links. This memo defines an Experimental
for the Internet community
2822 Resnick Apr 2001 Internet Message
This document specifies a syntax for text messages that are sent
computer users, within the framework of "electronic mail" messages
[STANDARDS TRACK
Ginoza Informational [Page 16]
RFC 2899 Summary of 2800-2899 May 2001
2821 Klensin Apr 2001 Simple Mail Transfer
This document is a self-contained specification of the basic
for the Internet electronic mail transport. [STANDARDS TRACK
2820 Stokes May 2000 Access Control
for
This document describes the fundamental requirements of an
control list (ACL) model for the Lightweight Directory
Protocol (LDAP) directory service. This memo provides information
the Internet community
2819 Waldbusser May 2000 Remote Network
Management 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
2818 Rescorla May 2000 HTTP Over
This memo describes how to use Transport Layer Security (TLS) to
Hypertext Transfer Protocol (HTTP) connections over the Internet.
memo provides information for the Internet community
2817 Khare May 2000 Upgrading to TLS
HTTP/1.1
This memo explains how to use the Upgrade mechanism in HTTP/1.1
initiate Transport Layer Security (TLS) over an existing TCP connection
[STANDARDS TRACK
2816 Ghanwani May 2000 A Framework for
Services Over Shared
Switched IEEE 802
This memo describes a framework for supporting IETF Integrated
on shared and switched LAN infrastructure. This memo
information for the Internet community
Ginoza Informational [Page 17]
RFC 2899 Summary of 2800-2899 May 2001
2815 Seaman May 2000 Integrated Service Mappings
IEEE 802
This document describes mappings of IETF Integrated Services over
built from IEEE 802 network segments which may be interconnected by
802.1D MAC Bridges (switches). [STANDARDS TRACK
2814 Yavatkar May 2000 SBM (Subnet
Manager): A Protocol
RSVP-based Admission
over IEEE 802-style
This document describes a signaling method and protocol for RSVP-
admission control over IEEE 802-style LANs. [STANDARDS TRACK
2813 Kalt Apr 2000 Internet Relay Chat:
This document defines the protocol used by servers to talk to
other. This memo provides information for the Internet community
2812 Kalt Apr 2000 Internet Relay Chat:
This document defines the Client Protocol, and assumes that the
is familiar with the IRC Architecture. This memo provides
for the Internet community
2811 Kalt Apr 2000 Internet Relay Chat:
This document specifies how channels, their characteristics
properties are managed by IRC servers. This memo provides
for the Internet community
2810 Kalt Apr 2000 Internet Relay Chat
This document is an update describing the architecture of the
IRC protocol and the role of its different components. Other
describe in detail the protocol used between the various
defined here. This memo provides information for the
community
Ginoza Informational [Page 18]
RFC 2899 Summary of 2800-2899 May 2001
2809 Aboba Apr 2000 Implementation of L2
Compulsory Tunneling
This document discusses implementation issues arising in
provisioning of compulsory tunneling in dial-up networks using the L2
(Layer Two Tunneling Protocol) protocol. This memo provides
for the Internet community
2808 Nystrom Apr 2000 The SecurID(r) SASL
This document defines a SASL (Simple Authentication and Security Layer
authentication mechanism using SecurID (a hardware token card
(or software emulation thereof) produced by RSA Security Inc., which
used for end-user authentication), thereby providing a means for
tokens to be used in SASL environments. This mechanism is only is
for authentication, and has no effect on the protocol encoding and
not designed to provide integrity or confidentiality services.
memo provides information for the Internet community
2807 Reagle Jul 2000 XML Signature
This document lists the design principles, scope, and requirements
the XML Digital Signature specification. It includes requirements
they relate to the signature syntax, data model, format,
processing, and external requirements and coordination. This
provides information for the Internet community
2806 Vaha-Sipila Apr 2000 URLs for Telephone
This document specifies URL (Uniform Resource Locator) schemes "tel",
"fax" and "modem" for specifying the location of a terminal in the
network and the connection types (modes of operation) that can be
to connect to that entity. [STANDARDS TRACK
Ginoza Informational [Page 19]
RFC 2899 Summary of 2800-2899 May 2001
2805 Greene Apr 2000 Media Gateway Control
Architecture and
This document describes protocol requirements for the Media
Control Protocol between a Media Gateway Controller and a Media Gateway
This memo provides information for the Internet community
2804 IAB May 2000 IETF Policy on
This document describes the position that the Internet Engineering
Force (IETF) has taken regarding the inclusion into IETF standards-
documents of functionality designed to facilitate wiretapping.
memo explains what the IETF thinks the question means, why its answer
"no", and what that answer means. This memo provides information
the Internet community
2803 Maruyama Apr 2000 Digest Values for DOM (DOMHASH
This memo defines a clear and unambiguous definition of digest (hash
values of the XML objects regardless of the surface string variation
XML. This memo provides information for the Internet community
2802 Davidson Apr 2000 Digital Signatures for
v1.0 Internet Open
Protocol (IOTP
This document describes the syntax and procedures for the
and verification of digital signatures for use within Version 1.0 of
Internet Open Trading Protocol (IOTP). This memo provides
for the Internet community
2801 Burdett Apr 2000 Internet Open Trading
- IOTP Version 1.0
This document discusses the Internet Open Trading Protocol (IOTP)
its provision of an interoperable framework for Internet commerce.
memo provides information for the Internet community
Ginoza Informational [Page 20]
RFC 2899 Summary of 2800-2899 May 2001
2800 Reynolds May 2001 Internet Official
This memo contains a snapshot of the state of standardization
protocols used in the Internet as of April 17, 2001. It lists
official protocol standards RFCs; it is not a complete index to the
series. [STANDARDS TRACK
Security
This memo does not affect the technical security of the Internet,
may cite important security specifications
Author's
Sandy
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: ginoza@isi.
Ginoza Informational [Page 21]
RFC 2899 Summary of 2800-2899 May 2001
Full Copyright
Copyright (C) The Internet Society (2001). 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
Ginoza Informational [Page 22]
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
