<pre>Network Working Group                                          S. Ginoza
Request for Comments: 2799                                           ISI
Category: Informational                                   September 2000


                      <span class="h1">Request for Comments Summary</span>

                         RFC Numbers 2700-2799

Status of This Memo

   This RFC is a slightly annotated list of the 100 RFCs from <a href="./rfc2700">RFC 2700</a>
   through RFCs 2799.  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 (YEAR).  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-2799" href="#section-2799">2799</a>    Ginoza  </span>                        Request for Comments Summary

This memo.


<span class="h2"><a class="selflink" id="section-2798" href="#section-2798">2798</a>    Smith  </span>         Apr 2000        Definition of the
                                        inetOrgPerson LDAP Object
                                        Class

We define a new object class called inetOrgPerson for use in LDAP and
<span class="h3"><a class="selflink" id="appendix-X.500" href="#appendix-X.500">X.500</a> directory services that extends the X.521 standard</span>
organizationalPerson class to meet these needs.  This memo provides
information for the Internet community.



<span class="grey">Ginoza                       Informational                      [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2797" href="#section-2797">2797</a>    Myers  </span>         Apr 2000        Certificate Management
                                        Messages over CMS

This document defines a Certificate Management protocol using CMS (CMC).
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2796" href="#section-2796">2796</a>    Bates  </span>         Apr 2000        BGP Route Reflection - An
                                        Alternative to Full Mesh IBGP

This document describes the use and design of a method known as "Route
Reflection" to alleviate the the need for "full mesh" IBGP.  [STANDARDS
TRACK]


<span class="h2"><a class="selflink" id="section-2795" href="#section-2795">2795</a>    Christey  </span>      Mar 2000        The Infinite Monkey Protocol
                                        Suite (IMPS)

This memo describes a protocol suite which supports an infinite number
of monkeys that sit at an infinite number of typewriters in order to
determine when they have either produced the entire works of William
Shakespeare or a good television show.  This memo provides information
for the Internet community.


<span class="h2"><a class="selflink" id="section-2794" href="#section-2794">2794</a>    Calhoun  </span>       Mar 2000        Mobile IP Network Access
                                        Identifier Extension for IPv4

Our proposal defines a way for the mobile node to identify itself, by
including the NAI along with the Mobile IP Registration Request.  This
memo also updates <a href="./rfc2290">RFC 2290</a> which specifies the Mobile-IPv4 Configuration
option for IPCP, by allowing the Mobile Node's Home Address field of
this option to be zero.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2793" href="#section-2793">2793</a>    Hellstrom  </span>     May 2000        RTP Payload for Text
                                        Conversation

This memo describes how to carry text conversation session contents in
RTP packets.  Text conversation session contents are specified in ITU-T
Recommendation T.140.  [STANDARDS TRACK]










<span class="grey">Ginoza                       Informational                      [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2792" href="#section-2792">2792</a>    Blaze  </span>         Mar 2000        DSA and RSA Key and Signature
                                        Encoding for the KeyNote Trust
                                        Management System

This memo describes RSA and DSA key and signature encoding, and binary
key encoding for version 2 of the KeyNote trust-management system.  This
memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2791" href="#section-2791">2791</a>    Yu  </span>            Jul 2000        Scalable Routing Design
                                        Principles

This document identifies major factors affecting routing scalability as
well as basic principles of designing scalable routing for large
networks.  This memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2790" href="#section-2790">2790</a>    Waldbusser  </span>    Mar 2000        Host Resources MIB

This memo obsoletes <a href="./rfc1514">RFC 1514</a>, the "Host Resources MIB".  This memo
extends that specification by clarifying changes based on implementation
and deployment experience and documenting the Host Resources MIB in
SMIv2 format while remaining semantically identical to the existing
SMIv1-based MIB.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2789" href="#section-2789">2789</a>    Freed  </span>         Mar 2000        Mail Monitoring MIB

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.
Specifically, this memo extends the basic Network Services Monitoring
MIB defined in <a href="./rfc2788">RFC 2788</a> [16] to allow monitoring of Message Transfer
Agents (MTAs).  It may also be used to monitor MTA components within
gateways.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2788" href="#section-2788">2788</a>    Freed  </span>         Mar 2000        Network Services Monitoring
                                        MIB

This document defines a MIB which contains the elements common to the
monitoring of any network service application.  [STANDARDS TRACK]










<span class="grey">Ginoza                       Informational                      [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2787" href="#section-2787">2787</a>    Jewell  </span>        Mar 2000        Definitions of Managed Objects
                                        for the Virtual Router
                                        Redundancy Protocol


This specification defines an extension to the Management Information
Base (MIB) for use with SNMP-based network management.  In particular,
it defines objects for configuring, monitoring, and controlling routers
that employ the Virtual Router Redundancy Protocol (VRRP).  [STANDARDS
TRACK]


<span class="h2"><a class="selflink" id="section-2786" href="#section-2786">2786</a>    St. Johns  </span>     Mar 2000        Diffie-Helman USM Key
                                        Management Information
                                        Base and Textual Convention

This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols the Internet
community.  In particular, it defines a textual convention for doing
Diffie-Helman key agreement key exchanges an set of objects which extend
the usmUserTable to permit the use of DH key exchange in addition to the
key change method.  This memo defines an Experimental Protocol for the
Internet community.


<span class="h2"><a class="selflink" id="section-2785" href="#section-2785">2785</a>    Zuccherato  </span>    Mar 2000        Methods for Avoiding the
                                        "Small-Subgroup" Attacks on
                                        the Diffie-Hellman Key
                                        Agreement Method for S/MIME

This document will describe the situations relevant to implementations
of S/MIME version 3 in which protection is necessary and the methods
that can be used to prevent these attacks.  This memo provides
information for the Internet community.


<span class="h2"><a class="selflink" id="section-2784" href="#section-2784">2784</a>    Farinacci  </span>     Mar 2000        Generic Routing Encapsulation
                                        (GRE)

This document specifies a protocol for encapsulation of an arbitrary
network layer protocol over another arbitrary network layer protocol.
[STANDARDS TRACK]









<span class="grey">Ginoza                       Informational                      [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2783" href="#section-2783">2783</a>    Mogul  </span>         Mar 2000        Pulse-Per-Second API for
                                        UNIX-like Operating Systems,
                                        Version 1.0

<a href="./rfc1589">RFC 1589</a> did not define an API for managing the PPS facility, leaving
implementors without a portable means for using PPS sources.  This
document specifies such an API.  This memo provides information for the
Internet community.


<span class="h2"><a class="selflink" id="section-2782" href="#section-2782">2782</a>    Gulbrandsen  </span>   Feb 2000        A DNS RR for specifying the
                                        location of services (DNS SRV)

This document describes a DNS RR which specifies the location of the
server(s) for a specific protocol and domain.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2781" href="#section-2781">2781</a>    Hoffman  </span>       Feb 2000        UTF-16, an encoding of ISO
                                        10646

This document describes the UTF-16 encoding of Unicode/ISO-10646,
addresses the issues of serializing UTF-16 as an octet stream for
transmission over the Internet, discusses MIME charset naming as
described in [CHARSET-REG], and contains the registration for three MIME
charset parameter values: UTF-16BE (big-endian), UTF-16LE (little-
endian), and UTF-16.  This memo provides information for the Internet
community.


<span class="h2"><a class="selflink" id="section-2780" href="#section-2780">2780</a>    Bradner  </span>       Mar 2000        IANA Allocation Guidelines For
                                        Values In the Internet
                                        Protocol and Related Headers

This memo provides guidance for the IANA to use in assigning parameters
for fields in the IPv4, IPv6, ICMP, UDP and TCP protocol headers.  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-2779" href="#section-2779">2779</a>    Day  </span>           Feb 2000        Instant Messaging / Presence
                                        Protocol Requirements

This document defines a minimal set of requirements that IMPP must meet.
This memo provides information for the Internet community.







<span class="grey">Ginoza                       Informational                      [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2778" href="#section-2778">2778</a>    Day  </span>           Feb 2000        A Model for Presence and
                                        Instant Messaging


This document defines an abstract model for a presence and instant
messaging system.  It defines the various entities involved, defines
terminology, and outlines the services provided by the system.  This
memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2777" href="#section-2777">2777</a>    Eastlake  </span>      Feb 2000        Publicly Verifiable Nomcom
                                        Random Selection

This document describes a method for making random selections in such a
way that the unbiased nature of the choice is publicly verifiable.  This
memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2776" href="#section-2776">2776</a>    Handley  </span>       Feb 2000        Multicast-Scope Zone
                                        Announcement Protocol (MZAP)

This document defines a protocol, the Multicast-Scope Zone Announcement
Protocol (MZAP), for discovering the multicast administrative scope
zones that are relevant at a particular location.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2775" href="#section-2775">2775</a>    Carpenter  </span>     Feb 2000        Internet Transparency

This document describes the current state of the Internet from the
architectural viewpoint, concentrating on issues of end-to-end
connectivity and transparency.


<span class="h2"><a class="selflink" id="section-2774" href="#section-2774">2774</a>    Nielsen  </span>       Feb 2000        An HTTP Extension Framework

This document describes a generic extension mechanism for HTTP, which is
designed to address the tension between private agreement and public
specification and to accommodate extension of applications using HTTP
clients, servers, and proxies.  This memo defines an Experimental
Protocol for the Internet community.











<span class="grey">Ginoza                       Informational                      [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2773" href="#section-2773">2773</a>    Housley  </span>       Feb 2000        Encryption using KEA and
                                        SKIPJACK

This document defines a method to encrypt a file transfer using the FTP
specification STD 9, <a href="./rfc959">RFC 959</a>, "File Transfer Protocol (FTP)", (October
1985) and <a href="./rfc2228">RFC 2228</a>, "FTP Security Extensions" (October 1997).  This memo
defines an Experimental Protocol for the Internet community.


<span class="h2"><a class="selflink" id="section-2772" href="#section-2772">2772</a>    Rockell  </span>       Feb 2000        6Bone Backbone Routing
                                        Guidelines

This document provides a set of guidelines for all 6bone routing
equipment operators to use as a reference for efficient and stable
deployment of 6bone routing systems.  This memo provides information for
the Internet community.


<span class="h2"><a class="selflink" id="section-2771" href="#section-2771">2771</a>    Finlayson  </span>     Feb 2000        An Abstract API for Multicast
                                        Address Allocation

This document describes the "abstract service interface" for the dynamic
multicast address allocation service, as seen by applications.  This
memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2770" href="#section-2770">2770</a>    Meyer  </span>         Feb 2000        GLOP Addressing in 233/8

This describes an experimental policy for use of the class D address
space using 233/8 as the experimental statically assigned subset of the
class D address space.  This memo defines an Experimental Protocol for
the Internet community.


<span class="h2"><a class="selflink" id="section-2769" href="#section-2769">2769</a>    Villamizar  </span>    Feb 2000        Routing Policy System
                                        Replication

This document addresses the need to distribute data over multiple
repositories and delegate authority for data subsets to other
repositories without compromising the authorization model established in
Routing Policy System Security RFC.  [STANDARDS TRACK]










<span class="grey">Ginoza                       Informational                      [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2768" href="#section-2768">2768</a>    Aiken  </span>         Feb 2000        Network Policy and Services:
                                        A Report of a Workshop on
                                        Middleware

An ad hoc middleware workshop was held at the International Center for
Advanced Internet Research in December 1998.  The need for a more
organized framework for middleware R&amp;D was recognized, and a list of
specific topics needing further work was identified.  This memo provides
information for the Internet community.


<span class="h2"><a class="selflink" id="section-2767" href="#section-2767">2767</a>    Tsuchiya  </span>      Feb 2000        Dual Stack Hosts using the
                                        "Bump-In-the-Stack" Technique
                                        (BIS)

This memo proposes a mechanism of dual stack hosts using the technique
called "Bump-in-the-Stack" in the IP security area.  This memo provides
information for the Internet community.


<span class="h2"><a class="selflink" id="section-2766" href="#section-2766">2766</a>    Tsirtsis  </span>      Feb 2000        Network Address Translation -
                                        Protocol Translation (NAT-PT)

This document specifies an IPv4-to-IPv6 transition mechanism, in
addition to those already specified.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2765" href="#section-2765">2765</a>    Nordmark  </span>      Feb 2000        Stateless IP/ICMP Translation
                                        Algorithm (SIIT)

This document specifies a transition mechanism algorithm in addition to
the mechanisms already specified.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2764" href="#section-2764">2764</a>    Gleeson  </span>       Feb 2000        A Framework for IP Based
                                        Virtual Private Networks

This document describes a framework for Virtual Private Networks (VPNs)
running across IP backbones.  This memo provides information for the
Internet community.











<span class="grey">Ginoza                       Informational                      [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2763" href="#section-2763">2763</a>    Shen  </span>          Feb 2000        Dynamic Hostname Exchange
                                        Mechanism for IS-IS

This document defines a new TLV which allows the IS-IS routers to flood
their name to system ID mapping information across the IS-IS network.
This memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2762" href="#section-2762">2762</a>    Rosenberg  </span>     Feb 2000        Sampling of the Group
                                        Membership in RTP

This document discusses mechanisms for sampling of this group membership
table in order to reduce the memory requirements.  This memo defines an
Experimental Protocol for the Internet community.


<span class="h2"><a class="selflink" id="section-2761" href="#section-2761">2761</a>    Dunn  </span>          Feb 2000        Terminology for ATM
                                        Benchmarking

This memo discusses and defines terms associated with performance
benchmarking tests and the results of these tests in the context of
Asynchronous Transfer Mode (ATM) based switching devices.  This memo
provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2760" href="#section-2760">2760</a>    Allman  </span>        Feb 2000        Ongoing TCP Research Related
                                        to Satellites

This document outlines possible TCP enhancements that may allow TCP to
better utilize the available bandwidth provided by networks containing
satellite links.  This memo provides information for the Internet
community.


<span class="h2"><a class="selflink" id="section-2759" href="#section-2759">2759</a>    Zorn  </span>          Jan 2000        Microsoft PPP CHAP Extensions,
                                        Version 2

This document describes version two of Microsoft's PPP CHAP dialect
(MS-CHAP-V2).  MS-CHAP-V2 is similar to, but incompatible with, MS-CHAP
version one (MS-CHAP-V1).  This memo provides information for the
Internet community.










<span class="grey">Ginoza                       Informational                      [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2758" href="#section-2758">2758</a>    White  </span>         Feb 2000        Definitions of Managed Objects
                                        for Service Level Agreements
                                        Performance Monitoring

This memo defines a Management Information Base (MIB) for performance
monitoring of Service Level Agreements (SLAs) defined via policy
definitions.  This memo defines an Experimental Protocol for the
Internet community.


<span class="h2"><a class="selflink" id="section-2757" href="#section-2757">2757</a>    Montenegro  </span>    Jan 2000        Long Thin Networks

Our goal is to identify a TCP that works for all users, including users
of long thin networks.  This memo provides information for the Internet
community.


<span class="h2"><a class="selflink" id="section-2756" href="#section-2756">2756</a>    Vixie  </span>         Jan 2000        Hyper Text Caching Protocol
                                        (HTCP/0.0)

This document describes HTCP, a protocol for discovering HTTP caches and
cached data, managing sets of HTTP caches, and monitoring cache
activity.  This is an experimental protocol, one among several proposals
to perform these functions.  This memo defines an Experimental Protocol
for the Internet community.


<span class="h2"><a class="selflink" id="section-2755" href="#section-2755">2755</a>    Chiu  </span>          Jan 2000        Security Negotiation for
                                        WebNFS

This document describes a protocol for a WebNFS client (<a href="./rfc2054">RFC2054</a>) to
negotiate the desired security mechanism with a WebNFS server (<a href="./rfc2055">RFC2055</a>)
before the WebNFS client falls back to the MOUNT v3 protocol (<a href="./rfc1813">RFC1813</a>).
This document is provided so that people can write compatible
implementations.  This memo provides information for the Internet
community.















<span class="grey">Ginoza                       Informational                     [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2754" href="#section-2754">2754</a>    Alaettinoglu  </span>  Jan 2000        RPS IANA Issues

RPS Security requires certain RPSL objects in the IRR to be
hierarchically delegated.  The set of objects that are at the root of
this hierarchy needs to be created and digitally signed by IANA.  This
paper presents these seed objects and lists operations required from
IANA.  This memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2753" href="#section-2753">2753</a>    Yavatkar  </span>      Jan 2000        A Framework for Policy-based
                                        Admission Control

This document is concerned with specifying a framework for providing
policy-based control over admission control decisions.  This memo
provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2752" href="#section-2752">2752</a>    Yadav  </span>         Jan 2000        Identity Representation for
                                        RSVP

This document describes the representation of identity information in
POLICY_DATA object for supporting policy based admission control in
RSVP.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2751" href="#section-2751">2751</a>    Herzog  </span>        Jan 2000        Signaled Preemption Priority
                                        Policy Element

This document describes a preemption priority policy element for use by
signaled policy based admission protocols (such as RSVP and COPS).
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2750" href="#section-2750">2750</a>    Herzog  </span>        Jan 2000        RSVP Extensions for Policy
                                        Control

This memo presents a set of extensions for supporting generic policy
based admission control in RSVP.  [STANDARDS TRACK]













<span class="grey">Ginoza                       Informational                     [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2749" href="#section-2749">2749</a>    Herzog  </span>        Jan 2000        COPS usage for RSVP

This document describes usage directives for supporting COPS policy
services in RSVP environments.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2748" href="#section-2748">2748</a>    Durham  </span>        Jan 2000        The COPS (Common Open Policy
                                        Service) Protocol

This document describes a simple client/server model for supporting
policy control over QoS signaling protocols.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2747" href="#section-2747">2747</a>    Baker  </span>         Jan 2000        RSVP Cryptographic
                                        Authentication

This document describes the format and use of RSVP's INTEGRITY object to
provide hop-by-hop integrity and authentication of RSVP messages.
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2746" href="#section-2746">2746</a>    Terzis  </span>        Jan 2000        RSVP Operation Over IP Tunnels

This document describes an approach for providing RSVP protocol services
over IP tunnels.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2745" href="#section-2745">2745</a>    Terzis  </span>        Jan 2000        RSVP Diagnostic Messages

This document specifies the RSVP diagnostic facility, which allows a
user to collect information about the RSVP state along a path.
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2744" href="#section-2744">2744</a>    Wray  </span>          Jan 2000        Generic Security Service API
                                        Version 2 : C-bindings

This document specifies C language bindings for Version 2, Update 1 of
the Generic Security Service Application Program Interface (GSS-API),
which is described at a language-independent conceptual level in RFC
<span class="h2"><a class="selflink" id="section-2743" href="#section-2743">2743</a>.  [STANDARDS TRACK]</span>










<span class="grey">Ginoza                       Informational                     [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2743" href="#section-2743">2743</a>    Linn  </span>          Jan 2000        Generic Security Service
                                        Application Program Interface
                                        Version 2, Update 1

This memo obsoletes [<a href="./rfc2078">RFC-2078</a>], making specific, incremental changes in
response to implementation experience and liaison requests.  It is
intended, therefore, that this memo or a successor version thereto will
become the basis for subsequent progression of the GSS-API specification
on the standards track.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2742" href="#section-2742">2742</a>    Heintz  </span>        Jan 2000        Definitions of Managed Objects
                                        for Extensible SNMP Agents

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 managing SNMP agents that use the Agent
Extensibility (AgentX) Protocol.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2741" href="#section-2741">2741</a>    Daniele  </span>       Jan 2000        Agent Extensibility (AgentX)
                                        Protocol Version 1

This memo defines a standardized framework for extensible SNMP agents.
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2740" href="#section-2740">2740</a>    Coltun  </span>        Dec 1999        OSPF for IPv6

This document describes the modifications to OSPF to support version 6
of the Internet Protocol (IPv6).  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2739" href="#section-2739">2739</a>    Small  </span>         Jan 2000        Calendar Attributes for vCard
                                        and LDAP

This memo defines three mechanisms for obtaining a URI to a user's
calendar and free/busy time.  [STANDARDS TRACK]













<span class="grey">Ginoza                       Informational                     [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2738" href="#section-2738">2738</a>    Klyne  </span>         Dec 1999        Corrections to "A Syntax for
                                        Describing Media Feature Sets"

In <a href="./rfc2533">RFC 2533</a>, "A Syntax for Describing Media Feature Sets", an expression
format is presented for describing media feature capabilities using
simple media feature tags.  This memo contains two corrections to that
specification:  one fixes an error in the formal syntax specification,
and the other fixes an error in the rules for reducing feature
comparison predicates.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2737" href="#section-2737">2737</a>    McCloghrie  </span>    Dec 1999        Entity MIB (Version 2)

This memo defines a portion of the Management Information Base (M for
use with network management protocols in the Internet communi In
particular, it describes managed objects used for managing multiple
logical and physical entities managed by a single SNMP agent.
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2736" href="#section-2736">2736</a>    Handley  </span>       Dec 1999        Guidelines for Writers of RTP
                                        Payload Format Specifications

This document provides general guidelines aimed at assisting the authors
of RTP Payload Format specifications in deciding on good formats.  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-2735" href="#section-2735">2735</a>    Fox  </span>           Dec 1999        NHRP Support for Virtual
                                        Private Networks


The NBMA Next Hop Resolution Protocol (NHRP) is used to determine the
NBMA subnetwork addresses of the "NBMA next hop" towards a public
internetworking layer address.  This document describes the enhancements
necessary to enable NHRP to perform the same function for private
internetworking layer addresses available within the framework of a
Virtual Private Network (VPN) service on a shared NBMA network.
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2734" href="#section-2734">2734</a>    Johansson  </span>     Dec 1999        IPv4 over IEEE 1394

This document specifies how to use IEEE Std 1394-1995, Standard for a
High Performance Serial Bus (and its supplements), for the transport of
Internet Protocol Version 4 (IPv4) datagrams; it defines the necessary
methods, data structures and codes for that purpose.  [STANDARDS TRACK]



<span class="grey">Ginoza                       Informational                     [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2733" href="#section-2733">2733</a>    Rosenberg  </span>     Dec 1999        An RTP Payload Format for
                                        Generic Forward Error
                                        Correction

This document specifies a payload format for generic forward error
correction of media encapsulated in RTP.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2732" href="#section-2732">2732</a>    Hinden  </span>        Dec 1999        Format for Literal IPv6
                                        Addresses in URL's

This document defines the format for literal IPv6 Addresses in URL's for
implementation in World Wide Web browsers.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2731" href="#section-2731">2731</a>    Kunze  </span>         Dec 1999        Encoding Dublin Core Metadata
                                        in HTML

The Dublin Core is a small set of metadata elements for describing
information resources.  This document explains how these elements are
expressed using the META and LINK tags of HTML.  This memo provides
information for the Internet community.


<span class="h2"><a class="selflink" id="section-2730" href="#section-2730">2730</a>    Hanna  </span>         Dec 1999        Multicast Address Dynamic
                                        Client Allocation Protocol
                                        (MADCAP)

This document defines a protocol, Multicast Address Dynamic Client
Allocation Protocol (MADCAP), that allows hosts to request multicast
addresses from multicast address allocation servers.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2729" href="#section-2729">2729</a>    Bagnall  </span>       Dec 1999        Taxonomy of Communication
                                        Requirements for Large-scale
                                        Multicast Applications

The intention of this memo is to define a classification system for the
communication requirements of any large-scale multicast application
(LSMA).  This memo provides information for the Internet community.











<span class="grey">Ginoza                       Informational                     [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2728" href="#section-2728">2728</a>    Panabaker  </span>     Nov 1999        The Transmission of IP Over
                                        the Vertical Blanking Interval
                                        of a Television Signal

This document describes a method for broadcasting IP data in a
unidirectional manner using the vertical blanking interval of television
signals.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2727" href="#section-2727">2727</a>    Galvin  </span>        Feb 2000        IAB and IESG Selection,
                                        Confirmation, and Recall
                                        Process: Operation of the
                                        Nominating and Recall
                                        Committees

The process by which the members of the IAB and IESG are selected,
confirmed, and recalled is specified.  This document is a self-
consistent, organized compilation of the process as it was known at the
time of publication.  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-2726" href="#section-2726">2726</a>    Zsako  </span>         Dec 1999        PGP Authentication for RIPE
                                        Database Updates

This document presents the proposal for a stronger authentication method
of the updates of the RIPE database based on digital signatures.
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2725" href="#section-2725">2725</a>    Villamizar  </span>    Dec 1999        Routing Policy System Security

The implementation and deployment of a routing policy system must
maintain some degree of integrity to be of any operational use.  This
document addresses the need to assure integrity of the data by providing
an authentication and authorization model.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2724" href="#section-2724">2724</a>    Handelman  </span>     Oct 1999        RTFM: New Attributes for
                                        Traffic Flow Measurement

This document discusses RTFM flows and the attributes which they can
have, so as to provide a logical framework for extending the
architecture by adding new attributes.  This memo defines an
Experimental Protocol for the Internet community.





<span class="grey">Ginoza                       Informational                     [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2723" href="#section-2723">2723</a>    Brownlee  </span>      Oct 1999        SRL: A Language for Describing
                                        Traffic Flows and Specifying
                                        Actions for Flow Groups

This document describes a language for specifying rulesets, i.e.
configuration files which may be loaded into a traffic flow meter so as
to specify which traffic flows are measured by the meter, and the
information it will store for each flow.  This memo provides information
for the Internet community.


<span class="h2"><a class="selflink" id="section-2722" href="#section-2722">2722</a>    Brownlee  </span>      Oct 1999        Traffic Flow Measurement:
                                        Architecture

This document provides a general framework for describing network
traffic flows, presents an architecture for traffic flow measurement and
reporting, discusses how this relates to an overall network traffic flow
architecture and indicates how it can be used within the Internet.  This
memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2721" href="#section-2721">2721</a>    Brownlee  </span>      Oct 1999        RTFM: Applicability Statement

This document provides an overview covering all aspects of Realtime
Traffic Flow Measurement, including its area of applicability and its
limitations.  This memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2720" href="#section-2720">2720</a>    Brownlee  </span>      Oct 1999        Traffic Flow Measurement:
                                        Meter MIB

This document defines a Management Information Base (MIB) for use in
controlling an RTFM Traffic Meter, in particular for specifying the
flows to be measured.  It also provides an efficient mechanism for
retrieving flow data from the meter using SNMP.  Security issues
concerning the operation of traffic meters are summarised.  [STANDARDS
TRACK]


<span class="h2"><a class="selflink" id="section-2719" href="#section-2719">2719</a>    Ong  </span>           Oct 1999        Framework Architecture for
                                        Signaling Transport

This document defines an architecture framework and functional
requirements for transport of signaling information over IP.  This memo
provides information for the Internet community.






<span class="grey">Ginoza                       Informational                     [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2718" href="#section-2718">2718</a>    Masinter  </span>      Nov 1999        Guidelines for new URL Schemes

This document provides guidelines for the definition of new URL schemes.
This memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2717" href="#section-2717">2717</a>    Petke  </span>         Nov 1999        Registration Procedures for
                                        URL Scheme Names

This document defines the process by which new URL scheme names are
registered.  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-2716" href="#section-2716">2716</a>    Aboba  </span>         Oct 1999        PPP EAP TLS Authentication
                                        Protocol

The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links.The
Extensible Authentication Protocol (EAP) is a PPP extension that
provides support for additional authentication methods within PPP.  This
memo defines an Experimental Protocol for the Internet community.


<span class="h2"><a class="selflink" id="section-2715" href="#section-2715">2715</a>    Thaler  </span>        Oct 1999        Interoperability Rules for
                                        Multicast Routing Protocols

The rules described in this document will allow efficient interoperation
among multiple independent multicast routing domains.  This memo
provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2714" href="#section-2714">2714</a>    Ryan  </span>          Oct 1999        Schema for Representing CORBA
                                        Object References in an LDAP
                                        Directory

This document defines the schema for representing CORBA object
references in an LDAP directory.  This memo provides information for the
Internet community.











<span class="grey">Ginoza                       Informational                     [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2713" href="#section-2713">2713</a>    Ryan  </span>          Oct 1999        Schema for Representing
                                        Java(tm) Objects in an
                                        LDAP Directory

This document defines the schema for representing Java(tm) objects in an
LDAP directory.  This memo provides information for the Internet
community.


<span class="h2"><a class="selflink" id="section-2712" href="#section-2712">2712</a>    Medvinsky  </span>     Oct 1999        Addition of Kerberos Cipher
                                        Suites to Transport Layer
                                        Security (TLS)

This document proposes the addition of new cipher suites to the TLS
protocol to support Kerberos-based authentication.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2711" href="#section-2711">2711</a>    Partridge  </span>     Oct 1999        IPv6 Router Alert Option

This memo describes a new IPv6 Hop-by-Hop Option type that alerts
transit routers to more closely examine the contents of an IP datagram.
[STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2710" href="#section-2710">2710</a>    Deering  </span>       Oct 1999        Multicast Listener Discovery
                                        (MLD) for IPv6

This document specifies the protocol used by an IPv6 router to discover
the presence of multicast listeners (that is, nodes wishing to receive
multicast packets) on its directly attached links, and to discover
specifically which multicast addresses are of interest to those
neighboring nodes.  [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2709" href="#section-2709">2709</a>    Srisuresh  </span>     Oct 1999        Security Model with
                                        Tunnel-mode IPsec for NAT
                                        Domains

This document describes a security model by which tunnel-mode IPsec
security can be architected on NAT devices.  This memo provides
information for the Internet community.










<span class="grey">Ginoza                       Informational                     [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2708" href="#section-2708">2708</a>    Bergman  </span>       Nov 1999        Job Submission Protocol
                                        Mapping Recommendations
                                        for the Job Monitoring MIB

This document defines the recommended mapping for many currently popular
Job submission protocols to objects and attributes in the Job Monitoring
MIB.  This memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2707" href="#section-2707">2707</a>    Bergman  </span>       Nov 1999        Job Monitoring MIB - V1.0

This document provides a printer industry standard SNMP MIB for (1)
monitoring the status and progress of print jobs (2) obtaining resource
requirements before a job is processed, (3) monitoring resource
consumption while a job is being processed and (4) collecting resource
accounting data after the completion of a job.  This memo provides
information for the Internet community.


<span class="h2"><a class="selflink" id="section-2706" href="#section-2706">2706</a>    Eastlake  </span>      Oct 1999        ECML v1: Field Names for
                                        E-Commerce


A standard set of information fields is defined as the first version of
an Electronic Commerce Modeling Language (ECML) so that this task can be
more easily automated, for example by wallet software that could fill in
fields.  This memo provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2705" href="#section-2705">2705</a>    Arango  </span>        Oct 1999        Media Gateway Control Protocol
                                        (MGCP) Version 1.0

This document describes an application programming interface and a
corresponding protocol (MGCP) for controlling Voice over IP (VoIP)
Gateways from external call control elements.  MGCP assumes a call
control architecture where the call control "intelligence" is outside
the gateways and handled by external call control elements.  This memo
provides information for the Internet community.


<span class="h2"><a class="selflink" id="section-2704" href="#section-2704">2704</a>    Blaze  </span>         Sep 1999        The KeyNote Trust-Management
                                        System Version 2

This memo describes version 2 of the KeyNote trust-management system.It
specifies the syntax and semantics of KeyNote `assertions', describes
`action attribute' processing, and outlines the application architecture
into which a KeyNote implementation can be fit.  This memo provides
information for the Internet community.



<span class="grey">Ginoza                       Informational                     [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


<span class="h2"><a class="selflink" id="section-2703" href="#section-2703">2703</a>    Klyne  </span>         Sep 1999        Protocol-independent Content
                                        Negotiation Framework

This memo sets out terminology, an abstract framework and goals for
protocol-independent content negotiation, and identifies some technical
issues which may need to be addressed.  This memo provides information
for the Internet community.


<span class="h2"><a class="selflink" id="section-2702" href="#section-2702">2702</a>    Awduche  </span>       Sep 1999        Requirements for Traffic
                                        Engineering Over MPLS

This document presents a set of requirements for Traffic Engineering
over Multiprotocol Label Switching (MPLS).  It identifies the functional
capabilities required to implement policies that facilitate efficient
and reliable network operations in an MPLS domain.  This memo provides
information for the Internet community.


<span class="h2"><a class="selflink" id="section-2701" href="#section-2701">2701</a>    Malkin  </span>        Sep 1999        Nortel Networks Multi-link
                                        Multi-node PPP Bundle
                                        Discovery Protocol

This document specifies a standard way for Multi-link PPP to operate
across multiple nodes.  This memo provides information for the Internet
community.


<span class="h2"><a class="selflink" id="section-2700" href="#section-2700">2700</a>    Reynolds  </span>      Aug 2000        Internet Official Protocol
                                        Standards

This memo describes the current state of standardization of protocols
used in the Internet as determined by the Internet Engineering Task
Force (IETF).  [STANDARDS TRACK]

Security Considerations

   Security issues are not discussed in this memo.













<span class="grey">Ginoza                       Informational                     [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


Author's Address

   Sandy Ginoza
   University of Southern California
   Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA 90292

   Phone:  (310) 822-1511

   EMail: ginoza@isi.edu








































<span class="grey">Ginoza                       Informational                     [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc2799">RFC 2799</a>                  Summary of 2700-2799            September 2000</span>


Full Copyright Statement

   Copyright (C) The Internet Society (YEAR).  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.



















Ginoza                       Informational                     [Page 23]
</pre>