Request for Comments Summary RFC Numbers 2100-2199
RFC 2199

Document Type RFC - Informational (January 1998; 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 2199 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           A. Ramos
Request for Comments: 2199                                           ISI
Category: Informational                                     January 1998

                      Request for Comments Summary

                         RFC Numbers 2100-2199

Status of This Memo

   This RFC is a slightly annotated list of the 100 RFCs from RFC 2100
   through RFCs 2199.  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 (1998).  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
---     ------          ----      -----

2199    Ramos           Jan 98  Request for Comments Summary

This memo.

2198    Perkins         Sep 97  RTP Payload for Redundant Audio Data

This document describes a payload format for use with the real-time
transport protocol (RTP), version 2, for encoding redundant audio data.
[STANDARDS-TRACK]

Ramos                        Informational                      [Page 1]
RFC 2199                  Summary of 2100-2199              January 1998

2197    Freed           Sep 97  SMTP Service Extension
                                for Command Pipelining

This memo defines an extension to the SMTP service whereby a server can
indicate the extent of its ability to accept multiple commands in a
single TCP send operation. [STANDARDS-TRACK]

2196    Fraser          Sep 97  Site Security Handbook

This handbook is a guide to developing computer security policies and
procedures for sites that have systems on the Internet.  The purpose of
this handbook is to provide practical guidance to administrators trying
to secure their information and services.  The subjects covered include
policy content and formation, a broad range of technical system and
network security topics, and security incident response.  This memo
provides information for the Internet community.  It does not specify an
Internet standard of any kind.

2195     Klensin        Sep 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]

2194    Aboba           Sep 97  Review of Roaming Implementations

This document reviews the design and functionality of existing roaming
implementations.  Examples of cases where roaming capability might be
required include ISP "confederations" and ISP-provided corporate network
access support.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.

2193    Gahrns          Sep 97  IMAP4 Mailbox Referrals

Mailbox referrals allow clients to seamlessly access mailboxes that are
distributed across several IMAP4 servers. [STANDARDS-TRACK]

2192    Newman          Sep 97  IMAP URL Scheme

This document defines a URL scheme for referencing objects on an IMAP
server. [STANDARDS-TRACK]

Ramos                        Informational                      [Page 2]
RFC 2199                  Summary of 2100-2199              January 1998

2191    Armitage        Sep 97  VENUS - Very Extensive Non-Unicast Service

This document focuses exclusively on the problems associated with
extending the MARS model to cover multiple clusters or clusters spanning
more than one subnet. It describes a hypothetical solution, dubbed "Very
Extensive NonUnicast Service" (VENUS), and shows how complex such a
service would be.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.

2190    Zhu             Sep 97  RTP Payload Format for H.263 Video Streams

This document specifies the payload format for encapsulating an H.263
bitstream in the Real-Time Transport Protocol (RTP). [STANDARDS TRACK]

2189    Ballardie       Sep 97  Core Based Trees (CBT version 2)
                                Multicast Routing

This document describes the Core Based Tree (CBT version 2) network
layer multicast routing protocol. CBT builds a shared multicast
distribution tree per group, and is suited to inter- and intra-domain
multicast routing.  This memo defines an Experimental Protocol for the
Internet community.

2188    Banan           Sep 97  AT&T/Neda's Efficient Short Remote
                                Operations (ESRO) Protocol
Show full document text