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