Request for Comments Summary RFC Numbers 2000-2099
RFC 2099

Document Type RFC - Informational (March 1997; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 2099 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Elliott
Request for Comments: 2099                                           ISI
Category: Informational                                       March 1997

                      Request for Comments Summary

                         RFC Numbers 2000-2099

Status of This Memo

   This RFC is a slightly annotated list of the 100 RFCs from RFC 2000
   through RFCs 2099.  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.

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
---     ------       ----      -----

2099    Elliott      Mar 97   Request for Comments Summary

This memo.

2098    Katsube      Feb 97   Toshiba's Router Architecture Extensions
                              for ATM : Overview

This memo describes a new internetworking architecture which makes
better use of the property of ATM.  This memo provides information for
the Internet community.  This memo does not specify an Internet standard
of any kind.

Elliott                      Informational                      [Page 1]
RFC 2099                  Summary of 2000-2099                March 1997

2097    Pall         Jan 97   The PPP NetBIOS Frames Control Protocol
                              (NBFCP)

This document defines the Network Control Protocol for establishing and
configuring the NBF protocol over PPP.  The NBFCP protocol is only
applicable for an end system to connect to a peer system or the LAN that
peer system is connected to.  [STANDARDS-TRACK]

2096    Baker        Jan 97   IP Forwarding Table MIB

This memo defines an update to RFC 1354.  The significant difference
between this MIB and RFC 1354 is the recognition (explicitly discussed
but by consensus left to future work) that CIDR routes may have the same
network number but different network masks.  [STANDARDS-TRACK]

2095    Klensin      Jan 97   IMAP/POP AUTHorize Extension for Simple
                              Challenge/Response

This specification provides a simple challenge-response authentication
protocol that is suitable for use with IMAP4.  [STANDARDS-TRACK]

2094    Harney       Mar 97   Group Key Management Protocol (GKMP)
                              Architecture

This specification proposes a protocol to create grouped symmetric keys
and distribute them amongst communicating peers.  This memo defines an
Experimental Protocol for the Internet community.

2093    Harney       Mar 97   Group Key Management Protocol (GKMP)
                              Specification

This specification proposes a protocol to create grouped symmetric keys
and distribute them amongst communicating peers.  This memo defines an
Experimental Protocol for the Internet community.

2092    Sherry       Jan 97   Protocol Analysis for Triggered RIP

As required by Routing Protocol Criteria [1], this report documents the
key features of Triggered Extensions to RIP to Support Demand Circuits
[2] and the current implementation experience.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.

Elliott                      Informational                      [Page 2]
RFC 2099                  Summary of 2000-2099                March 1997

2091    Meyer        Jan 97   Triggered Extensions to RIP to Support
                              Demand Circuits

This document defines a modification which can be applied to Bellman-
Ford (distance vector) algorithm information broadcasting protocols.
[STANDARDS-TRACK]

2090    Emberson     Feb 97   TFTP Multicast Option

This document describes a new TFTP option. This new option will allow
the multiple clients to receive the same file concurrently through the
use of Multicast packets.  This memo defines an Experimental Protocol
for the Internet community.

2089    Wijnen       Jan 97   V2ToV1 Mapping SNMPv2 onto SNMPv1 within
                              a bi-lingual SNMP agent

The goal of this memo is to document a common way of mapping an SNMPv2
response into an SNMPv1 response within a bi-lingual SNMP agent (one
that supports both SNMPv1 and SNMPv2).  This memo provides information
for the Internet community.  This memo does not specify an Internet
standard of any kind.

2088    Myers        Jan 97   IMAP4 non-synchronizing literals

The Internet Message Access Protocol [IMAP4] contains the "literal"
syntactic construct for communicating strings.  When sending a literal
Show full document text