As per Relevance of the word provides, we have this rfc below:
Network Working Group A.
Request for Comments: 2499
Category: Informational July 1999
Request for Comments
RFC Numbers 2400-2499
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 2400
through RFCs 2499. 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
--- ------ ---- -----
2499 Ramos July 1999 Request for Comments
This memo
2498 Mahdavi Jan 1999 IPPM Metrics for
This memo defines a series of metrics for connectivity between a pair
Internet hosts. It builds on notions introduced and discussed in
2330, the IPPM framework document. This memo defines an
Protocol for the Internet community
Ramos Informational [Page 1]
RFC 2499 Summary of 2400-2499 July 1999
2497 Souvatzis Jan 1999 Transmission of IPv6
over ARCnet
This memo specifies a frame format for transmission of IPv6 packets
the method of forming IPv6 link-local and statelessly
addresses on ARCnet networks. It also specifies the content of
Source/Target Link-layer Address option used by the Router Solicitation
Router Advertisement, Neighbor Solicitation, Neighbor Advertisement
Redirect messages described in, when those messages are transmitted
an ARCnet. [STANDARDS-TRACK
2496 Fowler Jan 1999 Definitions of Managed
for the DS3/E3 Interface
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 DS3 and E
interfaces. This document is a companion document with Definitions
Managed Objects for the DS0 (RFC 2494), DS1/E1/DS2/E2 (RFC 2495),
the work in progress SONET/SDH Interface Types. [STANDARDS-TRACK
2495 Fowler Jan 1999 Definitions of Managed
for the DS1, E1, DS2 and E
Interface
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 DS1, E1, DS2 and E
interfaces. This document is a companion document with Definitions
Managed Objects for the DS0 (RFC 2494), DS3/E3 (RFC 2496), and the
in progress, SONET/SDH Interface Types. [STANDARDS-TRACK
2494 Fowler Jan 1999 Definitions of Managed
for the DS0 and DS0
Interface
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 DS0 and DS0
interfaces. This document is a companion document with Definitions
Managed Objects for the DS1/E1/DS2/E2 (RFC 2495), DS3/E3 (RFC 2496),
the work in progress, SONET/SDH Interface Types. [STANDARDS-TRACK
Ramos Informational [Page 2]
RFC 2499 Summary of 2400-2499 July 1999
2493 Tesink Jan 1999 Textual Conventions for
Modules Using
History Based on 15
This document defines a set of Textual Conventions for MIB modules
make use of performance history data based on 15 minute intervals
[STANDARDS-TRACK
2492 Armitage Jan 1999 IPv6 over ATM
This document is a companion to the ION working group's
document, "IPv6 over Non Broadcast Multiple Access (NBMA) networks".
provides specific details on how to apply the IPv6 over
architecture to ATM networks. This architecture allows
host-side operation of the IPv6 Neighbor Discovery protocol, while
supporting the establishment of 'shortcut' ATM forwarding paths (
using SVCs). Operation over administratively configured Point to
PVCs is also supported. [STANDARDS-TRACK
2491 Armitage Jan 1999 IPv6 over Non-
Multiple Access (NBMA)
This document describes a general architecture for IPv6 over
networks. [STANDARDS-TRACK
2490 Pullen Jan 1999 A Simulation Model for
Multicast with
This document describes a detailed model of IPv4 multicast with
that has been developed using the OPNET simulation package,
protocol procedures defined in the C language. This memo
information for the Internet community
2489 Droms Jan 1999 Procedure for Defining
DHCP
This document describes the procedure for defining new DHCP options
This document specifies an Internet Best Current Practices for
Internet Community, and requests discussion and suggestions
improvements
Ramos Informational [Page 3]
RFC 2499 Summary of 2400-2499 July 1999
2488 Allman Jan 1999 Enhancing TCP Over
Channels using
The Transmission Control Protocol (TCP) provides reliable delivery
data across any network path, including network paths
satellite channels. While TCP works over satellite channels there
several IETF standardized mechanisms that enable TCP to more
utilize the available capacity of the network path. This
outlines some of these TCP mitigations. This document specifies
Internet Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
2487 Hoffman Jan 1999 SMTP Service Extension
Secure SMTP over
This document describes an extension to the SMTP service that allows
SMTP server and client to use transport-layer security to
private, authenticated communication over the Internet. This gives
agents the ability to protect some or all of their communications
eavesdroppers and attackers. [STANDARDS-TRACK
2486 Aboba Jan 1999 The Network Access
This document proposes syntax for the Network Access Identifier (NAI),
the userID submitted by the client during PPP authentication
[STANDARDS-TRACK
2485 Drach Jan 1999 DHCP Option for The
Group's User
This document defines a DHCP option that contains a list of pointers
User Authentication Protocol servers that provide user
services for clients that conform to The Open Group Network
Client Technical Standard. [STANDARDS-TRACK
Ramos Informational [Page 4]
RFC 2499 Summary of 2400-2499 July 1999
2484 Zorn Jan 1999 PPP LCP
Configuration
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 (LCP), which
negotiation of an Authentication Protocol for authenticating its
before allowing Network Layer protocols to transmit over the link
[STANDARDS-TRACK
2483 Mealling Jan 1999 URI Resolution
Necessary for URN
Retrieving the resource identified by a Uniform Resource
(URI) is only one of the operations that can be performed on a URI.
might also ask for and get a list of other identifiers that are
for the original URI or a bibliographic description of the resource
URI denotes, for example. This applies to both Uniform Resource
(URNs) and Uniform Resource Locators (URLs). Uniform
Characteristics (URCs) are discussed in this document but only
descriptions of resources rather than identifiers. This memo defines
Experimental Protocol for the Internet community
2482 Whistler Jan 1999 Language Tagging in
Plain
This document proposed a mechanism for language tagging in plain text
This memo provides information for the Internet community
2481 Ramakrishnan Jan 1999 A Proposal to add
Congestion Notification (ECN
to
This note describes a proposed addition of ECN (Explicit
Notification) to IP. This memo defines an Experimental Protocol for
Internet community
2480 Freed Jan 1999 Gateways and MIME
This document examines the problems associated with use of MIME
multiparts and gateways to non-MIME environments. [STANDARDS-TRACK
Ramos Informational [Page 5]
RFC 2499 Summary of 2400-2499 July 1999
2479 Adams Dec 1998 Independent Data
Protection Generic Security
Application Program
(IDUP-GSS-API
The IDUP-GSS-API extends the GSS-API for applications
protection of a generic data unit (such as a file or message) in a
which is independent of the protection of any other data unit
independent of any concurrent contact with designated "receivers" of
data unit. This memo provides information for the Internet community
2478 Baize Dec 1998 The Simple and
GSS-API Negotiation
This document specifies a Security Negotiation Mechanism for the
Security Service Application Program Interface (GSS-API). [STANDARDS
TRACK
2477 Aboba Jan 1999 Criteria for
Roaming
This document describes requirements for the provisioning of "
capability" for dialup Internet users. "Roaming capability" is
as the ability to use multiple Internet service providers (ISPs),
maintaining a formal, customer-vendor relationship with only one.
memo provides information for the Internet community
2476 Gellens Dec 1998 Message
This memo describes a low cost, deterministic means for messages to
identified as submissions, and specifies what actions are to be taken
a submission server. [STANDARDS-TRACK
2475 Blake Dec 1998 An Architecture
Differentiated
This document defines an architecture for implementing scalable
differentiation in the Internet. This memo provides information for
Internet community
Ramos Informational [Page 6]
RFC 2499 Summary of 2400-2499 July 1999
2474 Nichols Dec 1998 Definition of
Differentiated Services
(DS Field) in the IPv4
IPv6
This document defines the IP header field, called the DS (
differentiated services) field. [STANDARDS-TRACK
2473 Conta Dec 1998 Generic Packet Tunneling
IPv6
This document defines the model and generic mechanisms for IPv
encapsulation of Internet packets, such as IPv6 and IPv4. [STANDARDS
TRACK
2472 Haskin Dec 1998 IP Version 6 over
This document defines the method for transmission of IP Version 6
packets over PPP links as well as the Network Control Protocol (NCP)
establishing and configuring the IPv6 over PPP. It also specifies
method of forming IPv6 link-local addresses on PPP links. [STANDARDS
TRACK
2471 Hinden Dec 1998 IPv6 Testing Address
This document describes an allocation plan for IPv6 addresses to be
in testing IPv6 prototype software. This memo defines an
Protocol for the Internet community
2470 Crawford Dec 1998 Transmission of IPv6
over Token Ring
This memo specifies the MTU and frame format for transmission of IPv
packets on Token Ring networks. [STANDARDS-TRACK
Ramos Informational [Page 7]
RFC 2499 Summary of 2400-2499 July 1999
2469 Narten Dec 1998 A Caution On The
Ordering Of Link-Layer
Protocols such as ARP and Neighbor Discovery have data fields
contain link-layer addresses. In order to interoperate properly,
sender setting such a field must insure that the receiver extracts
bits and interprets them correctly. In most cases, such fields must
in "canonical form". Unfortunately, not all LAN adaptors are
in their use of canonical form, and implementations may need
explicitly bit swap individual bytes in order to obtain the
format. This document provides information to implementors to help
avoid the pitfall of using non-canonical forms when canonical forms
required. This memo provides information for the Internet community
2468 Cerf Oct 1998 I REMEMBER
A long time ago, in a network, far far away, a great adventure
place!. This memo provides information for the Internet community
2467 Crawford Dec 1998 Transmission of IPv6
over FDDI
This document specifies the frame format for transmission of IPv
packets and the method of forming IPv6 link-local addresses
statelessly autoconfigured addresses on FDDI networks. [STANDARDS
TRACK
2466 Haskin Dec 1998 Management Information
for IP Version 6: ICMPv6
This document is one in the series of documents that define various
object groups for IPv6. Specifically, the ICMPv6 group is defined
this document. [STANDARDS-TRACK
2465 Haskin Dec 1998 Management Information
for IP Version 6:
Conventions and General
This document is one in the series of documents that provide
definitions for for IP Version 6. Specifically, the IPv6 MIB
conventions as well as the IPv6 MIB General group is defined in
document. [STANDARDS-TRACK
Ramos Informational [Page 8]
RFC 2499 Summary of 2400-2499 July 1999
2464 Crawford Dec 1998 Transmission of IPv6
over Ethernet
This document specifies the frame format for transmission of IPv
packets and the method of forming IPv6 link-local addresses
statelessly autoconfigured addresses on Ethernet networks. It
specifies the content of the Source/Target Link-layer Address
used in Router Solicitation, Router Advertisement,
Solicitation, Neighbor Advertisement and Redirect messages when
messages are transmitted on an Ethernet. [STANDARDS-TRACK
2463 Conta Dec 1998 Internet Control
Protocol (ICMPv6) for
Internet Protocol Version 6
(IPv6)
This document specifies a set of Internet Control Message
(ICMP) messages for use with version 6 of the Internet Protocol (IPv6).
[STANDARDS-TRACK
2462 Thomson Dec 1998 IPv6 Stateless
This document specifies the steps a host takes in deciding how
autoconfigure its interfaces in IP version 6. [STANDARDS-TRACK
2461 Narten Dec 1998 Neighbor Discovery for
Version 6 (IPv6)
This document specifies the Neighbor Discovery protocol for IP
6. [STANDARDS-TRACK
2460 Deering Dec 1998 Internet Protocol, Version 6
(IPv6)
This document specifies version 6 of the Internet Protocol (IPv6),
sometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK
Ramos Informational [Page 9]
RFC 2499 Summary of 2400-2499 July 1999
2459 Housley Jan 1999 Internet X.509 Public
Infrastructure Certificate
CRL
This memo profiles the X.509 v3 certificate and X.509 v2 CRL for use
the Internet. [STANDARDS-TRACK
2458 Lu Nov 1998 Toward the PSTN/
Inter-Networking --Pre-
This document contains the information relevant to the development
the inter-networking interfaces underway in the Public
Telephone Network (PSTN)/Internet Inter-Networking (PINT) Working Group
This memo provides information for the Internet community
2457 Clouston Nov 1998 Definitions of Managed
for Extended Border
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 APPN (Advanced Peer-to-Peer Network) EBN (Extended
Node) capabilities. This memo identifies managed objects for the
architecture. [STANDARDS-TRACK
2456 Clouston Nov 1998 Definitions of Managed
for APPN
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 receiving notifications from
devices with APPN (Advanced Peer-to-Peer Network) and DLUR (Dependent
Requester) capabilities. This memo identifies notifications for
APPN and DLUR architecture. [STANDARDS-TRACK
Ramos Informational [Page 10]
RFC 2499 Summary of 2400-2499 July 1999
2455 Clouston Nov 1998 Definitions of Managed
for
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 APPN (Advanced Peer-to-Peer Networking) capabilities.
memo identifies managed objects for the APPN protocol. [STANDARDS
TRACK
2454 Daniele Dec 1998 IP Version 6
Information Base for the
Datagram
This document is one in the series of documents that define various
objects for IPv6. Specifically, this document is the MIB module
defines managed objects for implementations of the User
Protocol (UDP) over IP Version 6 (IPv6). [STANDARDS-TRACK
2453 Malkin Nov 1998 RIP Version 2
This document specifies an extension of the Routing Information
(RIP) to expand the amount of useful information carried in RIP
and to add a measure of security. [STANDARDS-TRACK
2452 Daniele Dec 1998 IP Version 6
Information Base for
Transmission Control
This document is one in the series of documents that define various
objects for IPv6. Specifically, this document is the MIB module
defines managed objects for implementations of the Transmission
Protocol (TCP) over IP Version 6 (IPv6). [STANDARDS-TRACK
2451 Pereira Nov 1998 The ESP CBC-Mode
This document describes how to use CBC-mode cipher algorithms with
IPSec ESP (Encapsulating Security Payload) Protocol. It not
clearly states how to use certain cipher algorithms, but also how to
all CBC-mode cipher algorithms. [STANDARDS-TRACK
Ramos Informational [Page 11]
RFC 2499 Summary of 2400-2499 July 1999
2450 Hinden Dec 1998 Proposed TLA and
Assignment
This document proposes rules for Top-Level Aggregation Identifiers (
ID) and Next-Level Aggregation Identifiers (NLA ID). This memo
information for the Internet community
2449 Gellens Nov 1998 POP3 Extension
This memo updates RFC 1939 to define a mechanism to announce support
optional commands, extensions, and unconditional server behavior
[STANDARDS-TRACK
2448 Civanlar Nov 1998 AT&T's Error Resilient
Transmission
This document describes a set of techniques for packet loss
transmission of compressed video bitstreams based on reliable
of their vital information-carrying segments. This memo
information for the Internet community
2447 Dawson Nov 1998 iCalendar Message-
Interoperability Protocol (iMIP
This document specifies a binding from the iCalendar Transport
independent Interoperability Protocol (iTIP) to Internet email-
transports. [STANDARDS-TRACK
2446 Silverberg Nov 1998 iCalendar Transport-
Interoperability Protocol (iTIP
Scheduling Events, BusyTime
To-dos and Journal
This document specifies how calendaring systems use iCalendar objects
interoperate with other calendar systems. It does so in a general way
as to allow multiple methods of communication between systems
[STANDARDS-TRACK
Ramos Informational [Page 12]
RFC 2499 Summary of 2400-2499 July 1999
2445 Dawson Nov 1998 Internet Calendaring
Scheduling Core
Specification (iCalendar
This memo has been defined to provide the definition of a common
for openly exchanging calendaring and scheduling information across
Internet. [STANDARDS-TRACK
2444 Newman Oct 1998 The One-Time-Password
OTP provides a useful authentication mechanism for situations
there is limited client or server trust. Currently, OTP is added
protocols in an ad-hoc fashion with heuristic parsing.
specification defines an OTP SASL mechanism so it can be easily
formally integrated into many application protocols. [STANDARDS-TRACK
2443 Luciani Nov 1998 A Distributed MARS
Using
This document describes a method for distributing a MARS service
a LIS. This method uses the Server Cache Synchronization
(SCSP) to synchronize the MARS Server databases within a LIS. When
is used to synchronize the caches of MARS Servers in a LIS, the
defines the boundary of an SCSP Server Group (SG). [STANDARDS-TRACK
2442 Freed Nov 1998 The Batch SMTP Media
This document defines a MIME content type suitable for tunneling
ESMTP transaction through any MIME-capable transport. This
provides information for the Internet
2441 Cohen Nov 1998 Working with
Tribute delivered at UCLA
October 30, 1998
This memo provides information for the Internet community
2440 Callas Nov 1998 OpenPGP Message
This document is maintained in order to publish all
information needed to develop interoperable applications based on
OpenPGP format. [STANDARDS-TRACK
Ramos Informational [Page 13]
RFC 2499 Summary of 2400-2499 July 1999
2439 Villamizar Nov 1998 BGP Route Flap
A usage of the BGP routing protocol is described which is capable
reducing the routing traffic passed on to routing peers and
the load on these peers without adversely affecting route
time for relatively stable routes. [STANDARDS-TRACK
2438 O'Dell Oct 1998 Advancement of
specifications on the
Standards
This document specifies the process which the IESG will use to
if a MIB specification document meets these requirements. It
discusses the rationale for this process. This document specifies
Internet Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
2437 Kaliski Oct 1998 PKCS #1: RSA
Specifications Version 2.0
This memo is the successor to RFC 2313. This document
recommendations for the implementation of public-key cryptography
on the RSA algorithm. This memo provides information for the
community
2436 Brett Oct 1998 Collaboration
ISOC/IETF and ITU-
This document describes the collaboration process between the ITU-T
ISOC/IETF. This memo provides information for the Internet community
2435 Berc Oct 1998 RTP Payload Format
JPEG-compressed
This memo describes the RTP payload format for JPEG video streams
[STANDARDS-TRACK
Ramos Informational [Page 14]
RFC 2499 Summary of 2400-2499 July 1999
2434 Narten Oct 1998 Guidelines for Writing an
Considerations Section in
This document discusses issues that should be considered in
a policy for assigning values to a name space and provides guidelines
document authors on the specific text that must be included in
that place demands on the IANA. This document specifies an
Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
2433 Zorn Oct 1998 Microsoft PPP CHAP
The Point-to-Point Protocol (PPP) provides a standard method
transporting multi-protocol datagrams over point-to-point links.
defines an extensible Link Control Protocol and a family of
Control Protocols (NCPs) for establishing and configuring
network-layer protocols. This memo provides information for
Internet community
2432 Dubray Oct 1998 Terminology for IP
The purpose of this document is to define terminology specific to
benchmarking of multicast IP forwarding devices. This memo
information for the Internet community
2431 Tynan Oct 1998 RTP Payload Format for BT.656
Video
This document specifies the RTP payload format for encapsulating
Recommendation BT.656-3 video streams in the Real-Time
Protocol (RTP). [STANDARDS-TRACK
2430 Li Oct 1998 A Provider Architecture
Differentiated Services
Traffic Engineering (PASTE
This document describes the Provider Architecture for
Services and Traffic Engineering (PASTE) for Internet Service
(ISPs). This memo provides information for the Internet community
Ramos Informational [Page 15]
RFC 2499 Summary of 2400-2499 July 1999
2429 Bormann Oct 1998 RTP Payload Format for
1998 Version of ITU-
Rec. H.263 Video (H.263+)
This document specifies an RTP payload header format applicable to
transmission of video streams generated based on the 1998 version
ITU-T Recommendation H.263. [STANDARDS-TRACK
2428 Allman Sep 1998 FTP Extensions for IPv6 and
This paper specifies extensions to FTP that will allow the protocol
work over IPv4 and IPv6. [STANDARDS-TRACK
2427 Brown Sep 1998 Multiprotocol
over Frame
This memo describes an encapsulation method for carrying
interconnect traffic over a Frame Relay backbone. It covers aspects
both Bridging and Routing. [STANDARDS-TRACK
2426 Dawson Sep 1998 vCard MIME Directory
This memo defines the profile of the MIME Content-Type for
information for a white-pages person object, based on a vCard
business card. [STANDARDS-TRACK
2425 Howes Sep 1998 A MIME Content-Type
Directory
This document defines a MIME Content-Type for holding
information. [STANDARDS-TRACK
2424 Vaudreuil Sep 1998 Content Duration MIME
This document describes the MIME header Content-Duration that
intended for use with any timed media content (typically audio/*
video/*). [STANDARDS-TRACK
Ramos Informational [Page 16]
RFC 2499 Summary of 2400-2499 July 1999
2423 Vaudreuil Sep 1998 VPIM Voice Message
Sub-type
This document describes the registration of the MIME sub-
multipart/voice-message for use with the Voice Profile for Internet
(VPIM). [STANDARDS-TRACK
2422 Vaudreuil Sep 1998 Toll Quality Voice - 32 kbit/
ADPCM MIME Sub-type
This document describes the registration of the MIME sub-
audio/32KADPCM for toll quality audio. [STANDARDS-TRACK
2421 Vaudreuil Sep 1998 Voice Profile for
Mail - version 2
This document profiles Internet mail for voice messaging. [STANDARDS
TRACK
2420 Kummert Sep 1998 The PPP Triple-DES
Protocol (3DESE
This document provides specific details for the use of the Triple-
standard (3DES) for encrypting PPP encapsulated packets. [STANDARDS
TRACK
2419 Sklower Sep 1998 The PPP DES
Protocol, Version 2 (DESE-bis
This document provides specific details for the use of the DES
for encrypting PPP encapsulated packets. [STANDARDS-TRACK
2418 Bradner Sep 1998 IETF Working
Guidelines and
This document describes the guidelines and procedures for formation
operation of IETF working groups. This document specifies an
Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
Ramos Informational [Page 17]
RFC 2499 Summary of 2400-2499 July 1999
2417 Chung Sep 1998 Definitions of Managed
for Multicast over UNI 3.0/3.1
based ATM
This memo specifies a MIB module in a manner that is both compliant
the SNMPv2 SMI, and semantically identical to the peer SNMPv
definitions. [STANDARDS-TRACK
2416 Shepard Sep 1998 When TCP Starts Up With
Packets Into Only Three
This memo is to document a simple experiment. The experiment
that in the case of a TCP receiver behind a 9600 bps modem link at
edge of a fast Internet where there are only 3 buffers before the
(and the fourth packet of a four-packet start will surely be dropped),
no significant degradation in performance is experienced by a
sending with a four-packet start when compared with a normal slow
(which starts with just one packet). This memo provides information
the Internet community
2415 Poduri Sep 1998 Simulation Studies
Increased Initial TCP Window
This document covers some simulation studies of the effects
increasing the initial window size of TCP. This memo
information for the Internet community
2414 Allman Sep 1998 Increasing TCP's Initial
This document specifies an increase in the permitted initial window
TCP from one segment to roughly 4K bytes. This memo defines
Experimental Protocol for the Internet community
2413 Weibel Sep 1998 Dublin Core Metadata
Resource
This is the first of a set of Informational RFCs describing the
Core. Its purpose is to introduce the Dublin Core and to describe
consensus reached on the semantics of each of the 15 elements.
memo provides information for the Internet community
Ramos Informational [Page 18]
RFC 2499 Summary of 2400-2499 July 1999
2412 Orman Nov 1998 The OAKLEY Key
This document describes a protocol, named OAKLEY, by which
authenticated parties can agree on secure and secret keying material
The basic mechanism is the Diffie-Hellman key exchange algorithm.
memo provides information for the Internet community
2411 Thayer Nov 1998 IP Security Document
This document is intended to provide guidelines for the development
collateral specifications describing the use of new encryption
authentication algorithms with the ESP protocol, described in and
authentication algorithms used with the AH protocol. This memo
information for the Internet community
2410 Glenn Nov 1998 The NULL Encryption
and Its Use With
This memo defines the NULL encryption algorithm and its use with
IPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK
2409 Harkins Nov 1998 The Internet Key Exchange (IKE
This memo describes a hybrid protocol. The purpose is to negotiate,
provide authenticated keying material for, security associations in
protected manner. [STANDARDS-TRACK
2408 Maughan Nov 1998 Internet Security
and Key Management
(ISAKMP
This memo describes a protocol utilizing security concepts necessary
establishing Security Associations (SA) and cryptographic keys in
Internet environment. [STANDARDS-TRACK
2407 Piper Nov 1998 The Internet IP
Domain of Interpretation
This document defines the Internet IP Security DOI (IPSEC DOI),
instantiates ISAKMP for use with IP when IP uses ISAKMP to
security associations. [STANDARDS-TRACK
Ramos Informational [Page 19]
RFC 2499 Summary of 2400-2499 July 1999
2406 Kent Nov 1998 IP Encapsulating
Payload (ESP
The Encapsulating Security Payload (ESP) header is designed to provide
mix of security services in IPv4 and IPv6. [STANDARDS-TRACK
2405 Madson Nov 1998 The ESP DES-CBC
Algorithm With Explicit
This document describes the use of the DES Cipher algorithm in
Block Chaining Mode, with an explicit IV, as a confidentiality
within the context of the IPSec Encapsulating Security Payload (ESP).
[STANDARDS-TRACK
2404 Madson Nov 1998 The Use of HMAC-SHA-1-96
within ESP and
This memo describes the use of the HMAC algorithm in conjunction
the SHA-1 algorithm as an authentication mechanism within the
IPSEC Encapsulating Security Payload and the revised
Authentication Header. [STANDARDS-TRACK
2403 Madson Nov 1998 The Use of HMAC-MD5-96
ESP and
This memo describes the use of the HMAC algorithm in conjunction
the MD5 algorithm as an authentication mechanism within the
IPSEC Encapsulating Security Payload and the revised
Authentication Header. [STANDARDS-TRACK
2402 Kent Nov 1998 IP Authentication
The IP Authentication Header (AH) is used to provide
integrity and data origin authentication for IP datagrams (
referred to as just "authentication"), and to provide protection
replays. [STANDARDS-TRACK
Ramos Informational [Page 20]
RFC 2499 Summary of 2400-2499 July 1999
2401 Kent Nov 1998 Security Architecture for
Internet
This memo specifies the base architecture for IPsec compliant systems
[STANDARDS-TRACK
2400 IAB Sep 1998 INTERNET OFFICIAL
This memo describes the state of standardization of protocols used
the Internet as determined by the Internet Architecture Board (IAB).
This memo is an Internet Standard. [STANDARDS-TRACK
Security
This memo does not affect the technical security of the Internet,
it does cite some security specifications
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 21]
RFC 2499 Summary of 2400-2499 July 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
Funding for the RFC Editor function is currently provided by
Internet Society
Ramos 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
