<pre>Network Working Group                                           A. Ramos
Request for Comments: 2199                                           ISI
Category: Informational                                     January 1998


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

                         RFC Numbers 2100-2199

Status of This Memo

   This RFC is a slightly annotated list of the 100 RFCs from <a href="./rfc2100">RFC 2100</a>
   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
---     ------          ----      -----


<span class="h2"><a class="selflink" id="section-2199" href="#section-2199">2199</a>    Ramos  </span>         Jan 98  Request for Comments Summary

This memo.


<span class="h2"><a class="selflink" id="section-2198" href="#section-2198">2198</a>    Perkins  </span>       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]






<span class="grey">Ramos                        Informational                      [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2197" href="#section-2197">2197</a>    Freed  </span>         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]


<span class="h2"><a class="selflink" id="section-2196" href="#section-2196">2196</a>    Fraser  </span>        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.


<span class="h2"><a class="selflink" id="section-2195" href="#section-2195">2195</a>     Klensin  </span>      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]


<span class="h2"><a class="selflink" id="section-2194" href="#section-2194">2194</a>    Aboba  </span>         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.


<span class="h2"><a class="selflink" id="section-2193" href="#section-2193">2193</a>    Gahrns  </span>        Sep 97  IMAP4 Mailbox Referrals

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


<span class="h2"><a class="selflink" id="section-2192" href="#section-2192">2192</a>    Newman  </span>        Sep 97  IMAP URL Scheme

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





<span class="grey">Ramos                        Informational                      [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2191" href="#section-2191">2191</a>    Armitage  </span>      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.


<span class="h2"><a class="selflink" id="section-2190" href="#section-2190">2190</a>    Zhu  </span>           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]


<span class="h2"><a class="selflink" id="section-2189" href="#section-2189">2189</a>    Ballardie  </span>     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.


<span class="h2"><a class="selflink" id="section-2188" href="#section-2188">2188</a>    Banan  </span>         Sep 97  AT&amp;T/Neda's Efficient Short Remote
                                Operations (ESRO) Protocol
                                Specification Version 1.2

This document specifies the service model, the notation and protocol for
Efficient Short Remote Operations (ESRO).  This memo provides
information for the Internet community.  It does not specify an Internet
standard of any kind.


<span class="h2"><a class="selflink" id="section-2187" href="#section-2187">2187</a>    Wessels  </span>       Sep 97  Application of Internet Cache Protocol
                                (ICP), version 2

This document describes the application of ICPv2 (Internet Cache
Protocol version 2, <a href="./rfc2186">RFC2186</a>) to Web caching.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.








<span class="grey">Ramos                        Informational                      [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2186" href="#section-2186">2186</a>    Wessels  </span>       Sep 97  Internet Cache Protocol (ICP), version 2

This document describes version 2 of the Internet Cache Protocol (ICPv2)
as currently implemented in two World-Wide Web proxy cache packages.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2185" href="#section-2185">2185</a>    Callon  </span>        Sep 97  Routing Aspects Of IPv6 Transition

This document gives an overview of the routing aspects of the IPv6
transition.  It is based on the protocols defined in the document
"Transition Mechanisms for IPv6 Hosts and Routers."  Readers should be
familiar with the transition mechanisms before reading this document.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2184" href="#section-2184">2184</a>    Freed  </span>         Aug 97  MIME Parameter Value and Encoded Word
                                Extensions:Character Sets, Languages,
                                and Continuations

This memo defines extensions to the <a href="./rfc2045">RFC 2045</a> media type and <a href="./rfc2183">RFC 2183</a>
disposition parameter value mechanisms. [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2183" href="#section-2183">2183</a>    Troost  </span>        Aug 97  Communicating Presentation Information
                                in Internet Messages: The Content-
                                Disposition Header Field

This memo provides a mechanism whereby messages conforming to the MIME
specifications [RFC 2045, <a href="./rfc2046">RFC 2046</a>, <a href="./rfc2047">RFC 2047</a>, <a href="./rfc2048">RFC 2048</a>, <a href="./rfc2049">RFC 2049</a>] can
convey presentational information.  It specifies the "Content-
Disposition" header field, which is optional and valid for any MIME
entity ("message" or "body part"). [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2182" href="#section-2182">2182</a>    Elz  </span>           Jul 97  Selection and Operation of Secondary
                                DNS Servers

This document discusses the selection of secondary servers for DNS
zones.The number of servers appropriate for a zone is also discussed,
and some general secondary server maintenance issues considered.  This
memo provides information for the Internet community.  This memo does
not specify an Internet standard of any kind.






<span class="grey">Ramos                        Informational                      [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2181" href="#section-2181">2181</a>    Elz  </span>           Jul 97  Clarifications to the DNS Specification

This document considers some areas that have been identified as problems
with the specification of the Domain Name System, and proposes remedies
for the defects identified. [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2180" href="#section-2180">2180</a>    Gahrns  </span>        Jul 97  IMAP4 Multi-Accessed Mailbox Practice

The behavior described in this document reflects the practice of some
existing servers or behavior that the consensus of the IMAP mailing list
has deemed to be reasonable.  The behavior described within this
document is believed to be [<a href="./rfc2060">RFC-2060</a>] compliant. However, this document
is not meant to define IMAP4 compliance, nor is it an exhaustive list of
valid IMAP4 behavior.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2179" href="#section-2179">2179</a>    Gwinn  </span>         Jul 97  Network Security For Trade Shows

This document is designed to assist vendors and other participants in
trade shows, such as Networld+Interop, in designing effective protection
against network and system attacks by unauthorized individuals.  This
memo provides information for the Internet community.  This memo does
not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2178" href="#section-2178">2178</a>    Moy  </span>           Jul 97  OSPF Version 2


This document considers some areas that have been identified as problems
with the specification of the Domain Name System, and proposes remedies
for the defects identified. [STANDARDS TRACK]


<span class="h2"><a class="selflink" id="section-2177" href="#section-2177">2177</a>    Leiba  </span>         Jun 97  IMAP4 IDLE command

This document specifies the syntax of an IDLE command, which will allow
a client to tell the server that it's ready to accept such real-time
updates. [STANDARDS-TRACK]











<span class="grey">Ramos                        Informational                      [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2176" href="#section-2176">2176</a>    Murakami  </span>      Jun 97  IPv4 over MAPOS Version 1

This memo documents a mechanism for supporting Version 4 of the Internet
Protocol (IPv4) on Version 1 of the Multiple Access Protocol over
SONET/SDH.  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2175" href="#section-2175">2175</a>     Murakami  </span>     Jun 97  SONET/SDH with 16 Bit Addressing

This memo documents MAPOS 16, a multiple access protocol for
transmission of network-protocol datagrams, encapsulated in HDLC frames
with 16 bit addressing, over SONET/SDH.  This memo provides information
for the Internet community.  This memo does not specify an Internet
standard of any kind.


<span class="h2"><a class="selflink" id="section-2174" href="#section-2174">2174</a>    Murakami  </span>     Jun 97   A MAPOS version 1 Extension -
                                Switch-Switch Protocol

This memo documents a MAPOS (Multiple Access Protocol over SONET/SDH)
version 1 extension, Switch Switch Protocol which provides dynamic
routing for unicast, broadcast, and multicast.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2173" href="#section-2173">2173</a>    Murakami  </span>     Jun 97   A MAPOS version 1 Extension - Node
                                Switch Protocol

This document describes a MAPOS extension, Node Switch Protocol, for
automatic node address assignment.  This memo provides information for
the Internet community.  This memo does not specify an Internet standard
of any kind.


<span class="h2"><a class="selflink" id="section-2172" href="#section-2172">2172</a>     Maruyama  </span>     Jun 97  MAPOS Version 1 Assigned Numbers

This memo documents the parameters used in the Multiple Access Protocol
over SONET/SDH Version 1.  This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.









<span class="grey">Ramos                        Informational                      [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2171" href="#section-2171">2171</a>    Murakami  </span>     Jun 97   MAPOS - Multiple Access Protocol over
                                SONET/SDH  Version 1

This memo documents a multiple access protocol for transmission of
network-protocol datagrams, encapsulated in High-Level Data Link Control
(HDLC) frames, over SONET/SDH.  This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


<span class="h2"><a class="selflink" id="section-2170" href="#section-2170">2170</a>    Almesberger  </span>   Jul 97  Application REQuested IP over ATM
                                (AREQUIPA)

This document specifies a method for allowing ATM-attached hosts that
have direct ATM connectivity to set up end-to-end IP over ATM
connections within the reachable ATM cloud, on request from
applications, and for the exclusive use by the requesting applications.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2169" href="#section-2169">2169</a>    Daniel  </span>        Jun 97  A Trivial Convention for using HTTP in
                                URN Resolution

This document specifies the "THTTP" resolution protocol - a trivial
convention for encoding resolution service requests and responses as
HTTP 1.0 or 1.1 requests and responses.  This memo defines an
Experimental Protocol for the Internet community.  This memo does not
specify an Internet standard of any kind.  Discussion and suggestions
for improvement are requested.


<span class="h2"><a class="selflink" id="section-2168" href="#section-2168">2168</a>    Daniel  </span>        Jun 97  Resolution of Uniform Resource
                                Identifiers using the Domain Name System

The requirements document for URN resolution systems defines the concept
of a "resolver discovery service". This document describes the first,
experimental, RDS. It is implemented by a new DNS Resource Record, NAPTR
(Naming Authority PoinTeR), that provides rules for mapping parts of
URIs to domain names.  This memo defines an Experimental Protocol for
the Internet community.










<span class="grey">Ramos                        Informational                      [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2167" href="#section-2167">2167</a>    Williamson  </span>    Jun 97  Referral Whois (RWhois) Protocol V1.5

This memo describes Version 1.5 of the client/server interaction of
RWhois.  RWhois provides a distributed system for the discovery,
retrieval, and maintenance of directory information.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2166" href="#section-2166">2166</a>    Bryant  </span>        Jun 97  APPN Implementer's Workshop
                                Closed Pages Document

This document specifies a set of extensions to <a href="./rfc1795">RFC 1795</a> designed to
improve the scalability of DLSw clarifications to <a href="./rfc1795">RFC 1795</a> in the light
of the implementation experience to-date.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2165" href="#section-2165">2165</a>    Veizades  </span>      Jun 97  Service Location Protocol

The Service Location Protocol provides a scalable framework for the
discovery and selection of network services.  Using this protocol,
computers using the Internet no longer need so much static configuration
of network services for network based applications.  This is especially
important as computers become more portable, and users less tolerant or
able to fulfill the demands of network system administration.
[STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2164" href="#section-2164">2164</a>    Kille  </span>         Jan 98  Use of an X.500/LDAP directory to
                                support MIXER address mapping

This specification defines how to represent and maintain these mappings
(MIXER Conformant Global Address Mappings of MCGAMs) in an X.500 or LDAP
directory.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2163" href="#section-2163">2163</a>    Allocchio  </span>     Jan 98  Using the Internet DNS to Distribute
                                MIXER Conformant Global Address
                                Mapping (MCGAM)

This memo is the complete technical specification to store in the
Internet Domain Name System (DNS) the mapping information (MCGAM) needed
by MIXER conformant e-mail gateways and other tools to map <a href="./rfc822">RFC822</a> domain
names into X.400 O/R names and vice versa.  [STANDARDS-TRACK]





<span class="grey">Ramos                        Informational                      [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2162" href="#section-2162">2162</a>    Allocchio  </span>     Jan 98  MaXIM-11 - Mapping between X.400 /
                                Internet mail and Mail-11 mail

The standard referred shortly into this document as "X.400" relates to
the ISO/IEC 10021 - CCITT 1984, 1988 and 1992 X.400 Series
Recommendations covering the Message Oriented Text Interchange Service
(MOTIS). This document covers the Inter Personal Messaging System (IPMS)
only.  This memo defines an Experimental Protocol for the Internet
community.


<span class="h2"><a class="selflink" id="section-2161" href="#section-2161">2161</a>    Alvestrand  </span>    Jan 98  A MIME Body Part for ODA

This document contains the definitions, originally contained in <a href="./rfc1495">RFC 1495</a>
and <a href="./rfc1341">RFC 1341</a>, on how to carry ODA in MIME, and how to translate it to
its X.400 representation.  This memo defines an Experimental Protocol
for the Internet community.


<span class="h2"><a class="selflink" id="section-2160" href="#section-2160">2160</a>    Alvestrand  </span>    Jan 98  Carrying PostScript in X.400 and MIME

This document describes methods for carrying PostScript information in
the two standard mail systems MIME and X.400, and the conversion between
them.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2159" href="#section-2159">2159</a>    Alvestrand  </span>    Jan 98  A MIME Body Part for FAX

This document contains the definitions, originally contained in RFC
1494, on how to carry CCITT G3Fax in MIME, and how to translate it to
its X.400 representation.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2158" href="#section-2158">2158</a>    Alvestrand  </span>    Jan 98  X.400 Image Body Parts

This document contains the body parts defined in <a href="./rfc1495">RFC 1495</a> for carrying
image formats that were originally defined in MIME through an X.400
system.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2157" href="#section-2157">2157</a>    Alvestrand  </span>    Jan 98  Mapping between X.400 and <a href="./rfc822">RFC-822</a>/MIME
                                Message Bodies

This document defines how to map body parts of X.400 messages into MIME
entities and vice versa, including the handling of multipart messages
and forwarded messages.  [STANDARDS-TRACK]





<span class="grey">Ramos                        Informational                      [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2156" href="#section-2156">2156</a>    Kille  </span>         Jan 98  MIXER (Mime Internet X.400 Enhanced
                                Relay): Mapping between X.400 and
                                <a href="./rfc822">RFC 822</a>/MIME

This document relates primarily to the ITU-T 1988 and 1992 X.400 Series
Recommendations / ISO IEC 10021 International Standard.  This ISO/ITU-T
standard is referred to in this document as "X.400", which is a
convenient shorthand.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2155" href="#section-2155">2155</a>    Clouston  </span>      Jun 97  Definitions of Managed Objects
                                for APPN using SMIv2

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-2154" href="#section-2154">2154</a>    Murphy  </span>        Jun 97  OSPF with Digital Signatures

This memo describes the extensions to OSPF required to add digital
signature authentication to Link State data, and to provide a
certification mechanism for router data.  Added LSA processing and key
management is detailed.  A method for migration from, or co-existence
with, standard OSPF V2 is described.  This memo defines an Experimental
Protocol for the Internet community.


<span class="h2"><a class="selflink" id="section-2153" href="#section-2153">2153</a>    Simpson  </span>       May 97   PPP Vendor 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 (LCP) for establishing,
configuring, and testing the data-link connection; and a family of
Network Control Protocols (NCPs) for establishing and configuring
different network-layer protocols.  This document provides information
for the Internet community.  It does not specify an Internet standard of
any kind.










<span class="grey">Ramos                        Informational                     [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2152" href="#section-2152">2152</a>    Goldsmith  </span>     May 97  A Mail-Safe Transformation Format
                                of Unicode

This document describes a transformation format of Unicode that contains
only 7-bit ASCII octets and is intended to be readable by humans in the
limiting case that the document consists of characters from the US-ASCII
repertoire. It also specifies how this transformation format is used in
the context of MIME and <a href="./rfc1641">RFC 1641</a>, "Using Unicode with MIME".  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2151" href="#section-2151">2151</a>    Kessler  </span>       Jun 97  A Primer On Internet and TCP/IP Tools
                                and Utilities

This memo is an introductory guide to many of the most commonly-
available TCP/IP and Internet tools and utilities. It also describes
discussion lists accessible from the Internet, ways to obtain Internet
and TCP/IP documents, and some resources that help users weave their way
through the Internet.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2150" href="#section-2150">2150</a>    Max  </span>           Oct 97  Humanities and Arts: Sharing Center
                                Stage on the Internet

The purpose of this document is to provide members of the Arts and
Humanities communities with an introduction to the Internet as a
valuable tool, resource, and medium for the creation, presentation, and
preservation of Arts and Humanities-based content.  This memo provides
information for the Internet community.  It does not specify an Internet
standard of any kind.


<span class="h2"><a class="selflink" id="section-2149" href="#section-2149">2149</a>   Talpade  </span>        May 97  Multicast Server Architectures for
                                MARS-based ATM multicasting

This memo provides details on the design and implementation of an MCS,
building on the core mechanisms defined in <a href="./rfc2022">RFC 2022</a>.  It also provides a
mechanism for using multiple MCSs per group for providing fault
tolerance.  This approach can be used with <a href="./rfc2022">RFC 2022</a> based MARS server
and clients, without needing any change in their functionality.  This
memo provides information for the Internet community.  This memo does
not specify an Internet standard of any kind.







<span class="grey">Ramos                        Informational                     [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2148" href="#section-2148">2148</a>    Alvestrand  </span>    Sep 97  Deployment of the Internet White Pages
                                Service

This document describes the way in which the Internet White Pages
Service is best exploited using today's experience, today's protocols,
today's products and today's procedures.  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-2147" href="#section-2147">2147</a>    Borman  </span>        May 97  TCP and UDP over IPv6 Jumbograms

IPv6 supports datagrams larger than 65535 bytes long, often referred to
as jumbograms, through use of the Jumbo Payload hop-by-hop option.  The
UDP protocol has a 16-bit length field that keeps it from being able to
make use of jumbograms, and though TCP does not have a length field,
both the MSS option and the Urgent field are constrained by 16-bits.
This document describes some simple changes that can be made to allow
TCP and UDP to make use of IPv6 jumbograms.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2146" href="#section-2146">2146</a>     FNC  </span>          May 97  U.S. Government Internet Domain Names


This memo provides an update and clarification to <a href="./rfc1816">RFC 1816</a>.  This
document describes the registration policies for the top-level domain
".GOV".  The purpose of the domain is to provide naming conventions that
identify US Federal government agencies in order to facilitate access to
their electronic resources.  This memo provides guidance for
registrations by Federal Agencies that avoids name duplication and
facilitates responsiveness to the public.  It restricts registrations to
coincide with the approved structure of the US government and the advice
of its Chief Information Officers.  This memo provides information for
the Internet community.  This memo does not specify an Internet standard
of any kind.


<span class="h2"><a class="selflink" id="section-2145" href="#section-2145">2145</a>    Mogul  </span>         May 97  Use and Interpretation of
                                HTTP Version Numbers

HTTP request and response messages include an HTTP protocol version
number.  Some confusion exists concerning the proper use and
interpretation of HTTP version numbers, and concerning interoperability
of HTTP implementations of different protocol versions.  This document
is an attempt to clarify the situation. This memo provides information
for the Internet community.  This memo does not specify an Internet
standard of any kind.




<span class="grey">Ramos                        Informational                     [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2144" href="#section-2144">2144</a>    Adams  </span>         May 97  The CAST-128 Encryption Algorithm

There is a need in the Internet community for an unencumbered encryption
algorithm with a range of key sizes that can provide security for a
variety of cryptographic applications and protocols.  This document
describes an existing algorithm that can be used to satisfy this
requirement.  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2143" href="#section-2143">2143</a>    Elliston  </span>      May 97  Encapsulating IP with the Small
                                Computer System Interface

This document outlines a protocol for connecting hosts running the
TCP/IP protocol suite over a Small Computer System Interface (SCSI) bus.
This memo defines an Experimental Protocol for the Internet community.
This memo does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2142" href="#section-2142">2142</a>    Crocker  </span>       May 97  MAILBOX NAMES FOR
                                COMMON SERVICES, ROLES AND FUNCTIONS

This specification enumerates and describes Internet mail addresses
(mailbox name @ host reference) to be used when contacting personnel at
an organization. [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2141" href="#section-2141">2141</a>    Moats  </span>         May 97  URN Syntax

Uniform Resource Names (URNs) are intended to serve as persistent,
location-independent, resource identifiers. This document sets forward
the canonical syntax for URNs. [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2140" href="#section-2140">2140</a>    Touch  </span>         Apr 97  TCP Control Block Interdependence

This memo makes the case for interdependent TCP control blocks, where
part of the TCP state is shared among similar concurrent connections, or
across similar connection instances. TCP state includes a combination of
parameters, such as connection state, current round-trip time estimates,
congestion control information, and process information.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.








<span class="grey">Ramos                        Informational                     [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2139" href="#section-2139">2139</a>    Rigney  </span>        Apr 97  RADIUS Accounting

This document describes a protocol for carrying accounting information
between a Network Access Server and a shared Accounting Server.  This
memo provides information for the Internet community.  This memo does
not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2138" href="#section-2138">2138</a>    Rigney  </span>        Apr 97  Remote Authentication Dial In User
                                Service (RADIUS)

This document describes a protocol for carrying authentication,
authorization, and configuration information between a Network Access
Server which desires to authenticate its links and a shared
Authentication Server. [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2137" href="#section-2137">2137</a>    Eastlake 3rd  </span>   Apr 97 Secure Domain Name System Dynamic
                                Update

This memo describes how to use DNSSEC digital signatures covering
requests and data to secure updates and restrict updates to those
authorized to perform them as indicated by the updater's possession of
cryptographic keys.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2136" href="#section-2136">2136</a>    Vixie  </span>         Apr 97  Dynamic Updates in the Domain Name
                                System (DNS UPDATE)

Using this specification of the UPDATE opcode, it is possible to add or
delete RRs or RRsets from a specified zone.  Prerequisites are specified
separately from update operations, and can specify a dependency upon
either the previous existence or nonexistence of an RRset, or the
existence of a single RR.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2135" href="#section-2135">2135</a>    ISOC BOT  </span>      Apr 97  Internet Society By-Laws


These are the by-laws of the Internet Society, as amended, as of June
<span class="h2"><a class="selflink" id="section-1996" href="#section-1996">1996</a>.  They are published for the information of the IETF community at</span>
the request of the poisson working group.  Please refer to the ISOC web
page (www.isoc.org) for the current version of the by-laws.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.






<span class="grey">Ramos                        Informational                     [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2134" href="#section-2134">2134</a>    ISOC BOT  </span>       Apr 97 ARTICLES OF INCORPORATION
                                OF INTERNET SOCIETY

These are the articles of incorporation of the Internet Society.  They
are published for the information of the IETF community at the request
of the poisson working group.  This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


<span class="h2"><a class="selflink" id="section-2133" href="#section-2133">2133</a>    Gilligan  </span>      Apr 97  Basic Socket Interface Extensions
                                for IPv6

This memo defines a set of extensions to the socket interface to support
the larger address size and new features of IPv6.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2132" href="#section-2132">2132</a>    Alexander  </span>     Mar 97  DHCP Options and BOOTP Vendor
                                Extensions

This document specifies the current set of DHCP options.  Future options
will be specified in separate RFCs.  The current list of valid options
is also available in <a href="ftp://ftp.isi.edu/in-notes/iana/assignments">ftp://ftp.isi.edu/in-notes/iana/assignments</a>.
[STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2131" href="#section-2131">2131</a>    Droms  </span>         Mar 97  Dynamic Host Configuration Protocol

The Dynamic Host Configuration Protocol (DHCP) provides a framework for
passing configuration information to hosts on a TCPIP network.  DHCP is
based on the Bootstrap Protocol (BOOTP), adding the capability of
automatic allocation of reusable network addresses and additional
configuration options.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2130" href="#section-2130">2130</a>   Weider  </span>         Apr 97  The Report of the IAB Character Set
                                Workshop held 29 February - 1 March,
                                1996

This report details the conclusions of an IAB-sponsored invitational
workshop held 29 February  - 1 March, 1996, to discuss the use of
character sets on the Internet.  It motivates the need to have character
set handling in Internet protocols which transmit text, provides a
conceptual framework for specifying character sets, recommends the use
of MIME tagging for transmitted text, recommends a default character set
*without* stating that there is no need for other character sets, and



<span class="grey">Ramos                        Informational                     [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


makes a series of recommendations to the IAB, IANA, and the IESG for
furthering the integration of the character set framework into text
transmission protocols.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2129" href="#section-2129">2129</a>    Nagami  </span>        Apr 97  Toshiba's Flow Attribute Notification
                                Protocol (FANP) Specification

This memo discusses Flow Attribute Notification Protocol (FANP), which
is a protocol between neighbor nodes for the management of cut-through
packet forwarding functionalities.  This memo provides information for
the Internet community.  This memo does not specify an Internet standard
of any kind.


<span class="h2"><a class="selflink" id="section-2128" href="#section-2128">2128</a>    Roeck  </span>         Mar 97  Dial Control Management Information
                                Base using SMIv2

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 managed objects used for managing demand access
circuits, including ISDN.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2127" href="#section-2127">2127</a>     Roeck  </span>         Mar 97 ISDN Management Information Base using
                                SMIv2

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 a minimal set of managed objects for SNMP-based
management of ISDN terminal interfaces.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2126" href="#section-2126">2126</a>    Pouffary  </span>      Mar 97  ISO Transport Service on top of TCP
                                (ITOT)

This document is a revision to STD35, <a href="./rfc1006">RFC1006</a>.  This document describes
the mechanism to allow ISO Transport Services to run over TCP over IPv4
or IPv6. It also defines a number of new features, which are not
provided in <a href="./rfc1006">RFC1006</a>.  [STANDARDS-TRACK]










<span class="grey">Ramos                        Informational                     [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2125" href="#section-2125">2125</a>    Richards  </span>      Mar 97  The PPP Bandwidth Allocation Protocol
                                (BAP), The PPP Bandwidth Allocation
                                Control Protocol (BACP)

This document proposes a method to manage the dynamic bandwidth
allocation of implementations supporting the PPP multilink protocol.
This is done by defining the Bandwidth Allocation Protocol (BAP), as
well as its associated control protocol, the Bandwidth Allocation
Control Protocol (BACP).  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2124" href="#section-2124">2124</a>    Amsden  </span>        Mar 97  Cabletron's Light-weight Flow
                                Admission Protocol Specification

This document specifies the protocol between the switch Connection
Control Entity (CCE) and the external FAS.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2123" href="#section-2123">2123</a>    Brownlee  </span>      Mar 97  Traffic Flow Measurement:  Experiences
                                with NeTraMet

This memo records experiences in implementing and using the Traffic Flow
Measurement Architecture and Meter MIB. It discusses the implementation
of NeTraMet (a traffic meter) and NeMaC (a combined manager and meter
reader), considers the writing of meter rule sets and gives some
guidance on setting up a traffic flow measurement system using NeTraMet.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2122" href="#section-2122">2122</a>    Mavrakis  </span>      Mar 97  VEMMI URL Specification

A new URL scheme, "vemmi" is defined.  VEMMI is a new international
standard for on-line multimedia services, that is both an ITU-T
(International Telecommunications Union, ex.  CCITT) International
Standard (T.107) and an European Standard (ETSI European
Telecommunications Standard Institute) standard (ETS 300 382, obsoleted
by ETS 300 709).  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2121" href="#section-2121">2121</a>   Armitage  </span>       Mar 97  Issues affecting MARS Cluster Size

This document provides a qualitative look at the issues constraining a
MARS Cluster's size, including the impact of VC limits in switches and
NICs, geographical distribution of cluster members, and the use of VC




<span class="grey">Ramos                        Informational                     [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


Mesh or MCS modes to support multicast groups.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2120" href="#section-2120">2120</a>    Chadwick  </span>      Mar 97  Managing the X.500 Root Naming Context

This document describes the use of 1993 ISO X.500 Standard protocols for
managing the root context. Whilst the ASN.1 is compatible with that of
the X.500 Standard, the actual settings of the parameters are
supplementary to that of the X.500 Standard.  This memo defines an
Experimental Protocol for the Internet community.


<span class="h2"><a class="selflink" id="section-2119" href="#section-2119">2119</a>    Bradner  </span>       Mar 97  Key words for use in RFCs to Indicate
                                Requirement Levels

In many standards track documents several words are used to signify the
requirements in the specification.  These words are often capitalized.
This document defines these words as they should be interpreted in IETF
documents.  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-2118" href="#section-2118">2118</a>    Pall  </span>          Mar 97  Microsoft Point-To-Point Compression
                                (MPPC) Protocol

This document describes the use of the Microsoft Point to Point
Compression protocol (also referred to as MPPC in this document) for
compressing PPP encapsulated packets.  This memo provides information
for the Internet community.  This memo does not specify an Internet
standard of any kind.


<span class="h2"><a class="selflink" id="section-2117" href="#section-2117">2117</a>    Estrin  </span>        Jun 97  Protocol Independent Multicast-Sparse
                                Mode (PIM-SM): Protocol Specification

This document describes a protocol for efficiently routing to multicast
groups that may span wide-area (and inter-domain) internets.  This memo
defines an Experimental Protocol for the Internet community.










<span class="grey">Ramos                        Informational                     [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2116" href="#section-2116">2116</a>    Apple  </span>         Apr 97  X.500 Implementations Catalog-96

This document is a revision to [<a href="./rfc1632">RFC 1632</a>]: A Revised Catalog of
Available X.500 Implementations and is based on the results of data
collection via a WWW home page that enabled implementors to submit new
or updated descriptions of currently available implementations of X.500,
including commercial products and openly available offerings. [<a href="./rfc1632">RFC 1632</a>]
is a revision of [<a href="./rfc1292">RFC 1292</a>].  This document contains detailed
description of 31 X.500 implementations - DSAs, DUAs, and DUA
interfaces.  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2115" href="#section-2115">2115</a>    Brown  </span>         Sep 97  Management Information Base for Frame
                                Relay DTEs Using SMIv2

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP- based internets.  In
particular, it defines objects for managing Frame Relay interfaces on
DTEs.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2114" href="#section-2114">2114</a>    Chiang  </span>        Feb 97  Data Link Switching Client Access
                                Protocol

This memo describes the Data Link Switching Client Access Protocol that
is used between workstations and routers to transport SNA/ NetBIOS
traffic over TCP sessions.  This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


<span class="h2"><a class="selflink" id="section-2113" href="#section-2113">2113</a>    Katz  </span>          Feb 97  IP Router Alert Option

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


<span class="h2"><a class="selflink" id="section-2112" href="#section-2112">2112</a>    Levinson  </span>      Mar 97  The MIME Multipart/Related
                                Content-type

The Multipart/Related content-type provides a common mechanism for
representing objects that are aggregates of related MIME body parts.
This document defines the Multipart/Related content-type and provides
examples of its use.  [STANDARDS-TRACK]






<span class="grey">Ramos                        Informational                     [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2111" href="#section-2111">2111</a>    Levinson  </span>      Mar 97  Content-ID and Message-ID Uniform
                                Resource Locators

The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow
references to messages and the body parts of messages.  For example,
within a single multipart message, one HTML body part might include
embedded references to other parts of the same message.  [STANDARDS-
TRACK]


<span class="h2"><a class="selflink" id="section-2110" href="#section-2110">2110</a>    Palme  </span>         Mar 97  MIME E-mail Encapsulation of Aggregate
                                Documents, such as HTML (MHTML)

This document describes a set of guidelines that will allow conforming
mail user agents to be able to send, deliver and display these objects,
such as HTML objects, that can contain links represented by URIs.
[STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2109" href="#section-2109">2109</a>    Kristol  </span>       Feb 97  HTTP State Management Mechanism

This document specifies a way to create a stateful session with HTTP
requests and responses.  It describes two new headers, Cookie and Set-
Cookie, which carry state information between participating origin
servers and user agents.  The method described here differs from
Netscape's Cookie proposal, but it can interoperate with HTTP/1.0 user
agents that use Netscape's method.  [STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2108" href="#section-2108">2108</a>    de Graaf  </span>      Feb 97  Definitions of Managed Objects
                                for IEEE 802.3 Repeater Device
                                using SMIv2

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 managing IEEE 802.3 10 and 100
Mb/second baseband repeaters based on IEEE Std 802.3 <a href="#section-30">Section 30</a>, "10 &amp;
<span class="h2"><a class="selflink" id="section-100" href="#section-100">100</a> Mb/s Management," October 26, 1995.  </span>[STANDARDS-TRACK]


<span class="h2"><a class="selflink" id="section-2107" href="#section-2107">2107</a>    Hamzeh  </span>        Feb 97  Ascend Tunnel Management Protocol - ATMP

This document specifies a generic tunnel management protocol that allows
remote dial-in users to access their home network as if they were
directly attached to the home network.  This memo provides information
for the Internet community.  This memo does not specify an Internet
standard of any kind.




<span class="grey">Ramos                        Informational                     [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2106" href="#section-2106">2106</a>    Chiang  </span>        Feb 97  Data Link Switching Remote Access
                                Protocol


This memo describes the Data Link Switching Remote Access Protocol that
is used between workstations and routers to transport SNA/ NetBIOS
traffic over TCP sessions.  This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


<span class="h2"><a class="selflink" id="section-2105" href="#section-2105">2105</a>    Rekhter  </span>       Feb 97  Cisco Systems' Tag Switching
                                Architecture Overview

This document provides an overview of a novel approach to network layer
packet forwarding, called tag switching. The two main components of  the
tag switching architecture - forwarding and control - are described.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2104" href="#section-2104">2104</a>    Krawcyzk  </span>      Feb 97  HMAC: Keyed-Hashing for Message
                                Authentication

This document describes HMAC, a mechanism for message authentication
using cryptographic hash functions. HMAC can be used with any iterative
cryptographic hash function, e.g., MD5, SHA-1, in combination with a
secret shared key.  The cryptographic strength of HMAC depends on the
properties of the underlying hash function.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind


<span class="h2"><a class="selflink" id="section-2103" href="#section-2103">2103</a>    Ramanathan  </span>    Feb 97  Mobility Support for Nimrod :
                                Challenges and Solution Approaches

We discuss the issue of mobility in Nimrod.  While a mobility solution
is not part of the Nimrod architecture, Nimrod does require that the
solution have certain characteristics.  We identify the requirements
that Nimrod has of any solution for mobility support.  We also classify
and compare existing approaches for supporting mobility within an
internetwork and discuss their advantages and disadvantages.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.







<span class="grey">Ramos                        Informational                     [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


<span class="h2"><a class="selflink" id="section-2102" href="#section-2102">2102</a>    Ramanathan  </span>    Feb 97  Multicast Support for Nimrod :
                                Challenges and Solution Approaches

Nimrod does not specify a particular solution for multicasting.  Rather,
Nimrod may use any of a number of emerging multicast techniques.  We
identify the requirements that Nimrod has of a solution for multicast
support.  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2101" href="#section-2101">2101</a>    Carpenter  </span>     Feb 97  IPv4 Address Behaviour Today

The main purpose of this note is to clarify the current interpretation
of the 32-bit IP version 4 address space, whose significance has changed
substantially since it was originally defined.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


<span class="h2"><a class="selflink" id="section-2100" href="#section-2100">2100</a>    Ashworth  </span>      Apr 97  The Naming of Hosts

This RFC is a commentary on the difficulty of deciding upon an
acceptably distinctive hostname for one's computer, a problem which
grows in direct proportion to the logarithmically increasing size of the
Internet.  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.

Security Considerations

   Security issues are not discussed in this memo.

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: ramos@isi.edu









<span class="grey">Ramos                        Informational                     [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc2199">RFC 2199</a>                  Summary of 2100-2199              January 1998</span>


Full Copyright Statement

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
























Ramos                        Informational                     [Page 23]
</pre>