Movatterモバイル変換

Network Working Group                                          S. GinozaRequest for Comments: 3199                                           ISICategory: Informational                                    February 2003Request for Comments Summary                         RFC Numbers 3100-3199Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs fromRFC 3100   through RFCs 3199.  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 (2003).  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---     ------          ----            -----3199    Ginoza        Feb 2003        Request for Comments SummaryThis memo.Ginoza                       Informational                      [Page 1]

RFC 3199                  Summary of 3100-3199             February 20033198    Westerinen    Nov 2001        Terminology for Policy-Based                                        ManagementThis document is a glossary of policy-related terms.  It providesabbreviations, explanations, and recommendations for use of these terms.The intent is to improve the comprehensibility and consistency ofwriting that deals with network policy, particularly Internet Standardsdocuments (ISDs).  This memo provides information for the Internetcommunity.3197    Austein       Nov 2001        Applicability Statement for                                        DNS MIB ExtensionsThis document explains why, after more than six years as proposedstandards, the DNS Server and Resolver MIB extensions were neverdeployed, and recommends retiring these MIB extensions by moving them toHistorical status.  This memo provides information for the Internetcommunity.3196    Hastings      Nov 2001        Internet Printing                                        Protocol/1.1: Implementor's                                        GuideThis document is one of a set of documents, which together describe allaspects of a new Internet Printing Protocol (IPP).  This memo providesinformation for the Internet community.3195    New           Nov 2001        Reliable Delivery for syslogThe BSD Syslog Protocol describes a number of service options related topropagating event messages.  This memo describes two mappings of thesyslog protocol to TCP connections, both useful for reliable delivery ofevent messages.  [STANDARDS TRACK]3194    Durand        Nov 2001        The Host-Density Ratio for                                        Address Assignment Efficiency:                                        An update on the H ratioThis document provides an update on the "H ratio" defined inRFC 1715.It defines a new ratio which the authors claim is easier to understand.This memo provides information for the Internet community.Ginoza                       Informational                      [Page 2]

RFC 3199                  Summary of 3100-3199             February 20033193    Patel         Nov 2001        Securing L2TP using IPsecThis document discusses how L2TP (Layer Two Tunneling Protocol) mayutilize IPsec to provide for tunnel authentication, privacy protection,integrity checking and replay protection. Both the voluntary andcompulsory tunneling cases are discussed.  [STANDARDS TRACK]3192    Allocchio     Oct 2001        Minimal FAX address format in                                        Internet MailThis memo describes a simple method of encoding Global SwitchedTelephone Network (GSTN) addresses of facsimile devices in the local-part of Internet email addresses.  [STANDARDS TRACK]3191    Allocchio     Oct 2001        Minimal GSTN address format in                                        Internet MailThis memo describes a simple method of encoding Global SwitchedTelephone Network (GSTN) addresses (commonly called "telephone numbers")in the local-part of Internet email addresses, along with an extensionmechanism to allow encoding of additional standard attributes needed foremail gateways to GSTN-based services.  [STANDARDS TRACK]3190    Kobayashi     Jan 2002        RTP Payload Format for 12-bit                                        DAT Audio and 20- and 24-bit                                        Linear Sampled AudioThis document specifies a packetization scheme for encapsulating 12-bitnonlinear, 20-bit linear, and 24-bit linear audio data streams using theReal-time Transport Protocol (RTP).  This document also specifies theformat of a Session Description Protocol (SDP) parameter to indicatewhen audio data is preemphasized before sampling.  The parameter may beused with other audio payload formats, in particular L16 (16-bitlinear).  [STANDARDS TRACK]3189    Kobayashi     Jan 2002        RTP Payload Format for DV                                        (IEC 61834) VideoThis document specifies the packetization scheme for encapsulating thecompressed digital video data streams commonly known as "DV" into apayload format for the Real-Time Transport Protocol (RTP).  [STANDARDSTRACK]Ginoza                       Informational                      [Page 3]

RFC 3199                  Summary of 3100-3199             February 20033188    Hakala        Oct 2001        Using National Bibliography                                        Numbers as Uniform Resource                                        NamesThis document discusses how national bibliography numbers (persistentand unique identifiers assigned by the national libraries) can besupported within the URN (Uniform Resource Names) framework and thesyntax for URNs defined inRFC 2141.  Much of the discussion is based onthe ideas expressed inRFC 2288.  This memo provides information for theInternet community.3187    Hakala        Oct 2001        Using International Standard                                        Book Numbers as Uniform                                        Resource NamesThis document discusses how International Standard Book Numbers (ISBN)can be supported within the URN (Uniform Resource Names) framework andthe syntax for URNs defined inRFC 2141.  Much of the discussion belowis based on the ideas expressed inRFC 2288.  This memo providesinformation for the Internet community.3186    Shimizu       Dec 2001        MAPOS/PPP Tunneling modeThis document specifies tunneling configuration over MAPOS (MultipleAccess Protocol over SONET/SDH) networks.  Using this mode, a MAPOSnetwork can provide transparent point-to-point link for PPP overSONET/SDH (Packet over SONET/SDH, POS) without any additional overhead.This memo provides information for the Internet community.3185    Farrell       Oct 2001        Reuse of CMS Content                                        Encryption KeysThis document describes a way to include a key identifier in a CMS(Cryptographic Message Syntax) enveloped data structure, so that thecontent encryption key can be re-used for further enveloped datapackets.  [STANDARDS TRACK]3184    Harris        Oct 2001        IETF Guidelines for ConductThis document provides a set of guidelines for personal interaction inthe Internet Engineering Task Force.  This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.Ginoza                       Informational                      [Page 4]

RFC 3199                  Summary of 3100-3199             February 20033183    Dean          Oct 2001        Domain Security Services using                                        S/MIMEThis document describes how the S/MIME (Secure/Multipurpose InternetMail Extensions) protocol can be processed and generated by a number ofcomponents of a communication system, such as message transfer agents,guards and gateways to deliver security services.  These services arecollectively referred to as 'Domain Security Services'.  This memodefines an Experimental Protocol for the Internet community.3182    Yadav         Oct 2001        Identity Representation for                                        RSVPThis document describes the representation of identity information inPOLICY_DATA object for supporting policy based admission control in theResource ReSerVation Protocol (RSVP).  The goal of identityrepresentation is to allow a process on a system to securely identifythe owner and the application of the communicating process (e.g., userid) and convey this information in RSVP messages (PATH or RESV) in asecure manner.  We describe the encoding of identities as RSVP policyelement.  We describe the processing rules to generate identity policyelements for multicast merged flows.  [STANDARDS TRACK]3181    Herzog        Oct 2001        Signaled Preemption Priority                                        Policy ElementThis document describes a preemption priority policy element for use bysignaled policy based admission protocols (such as the ResourceReSerVation Protocol (RSVP) and Common Open Policy Service (COPS).[STANDARDS TRACK]3180    Meyer         Sep 2001        GLOP Addressing in 233/8This document defines the policy for the use of 233/8 for statically eassigned multicast addresses.  This document specifies an Internet BestCurrent Practices for the Internet Community, and requests discussionand suggestions for improvements.Ginoza                       Informational                      [Page 5]

RFC 3199                  Summary of 3100-3199             February 20033179    Schoenwaelder Oct 2001        Script MIB Extensibility                                        Protocol Version 1.1The Script MIB extensibility protocol (SMX) defined in this memoseparates language specific runtime systems from language independentScript MIB implementations.  The IETF Script MIB defines an interfacefor the delegation of management functions based on the Internetmanagement framework.  This memo defines an Experimental Protocol forthe Internet community.3178    Hagino        Oct 2001        IPv6 Multihoming Support at                                        Site Exit RoutersThe document describes a mechanism for basic IPv6 multihoming support,and its operational requirements.  This memo provides information forthe Internet community.3177    IAB           Sep 2001        IAB/IESG Recommendations on                                        IPv6 Address Allocations to                                        SitesThis document provides recommendations to the addressing registries(APNIC, ARIN and RIPE-NCC) on policies for assigning IPv6 address blocksto end sites.  In particular, it recommends the assignment of /48 in thegeneral case, /64 when it is known that one and only one subnet isneeded and /128 when it is absolutely known that one and only one deviceis connecting.3176    Phaal         Sep 2001        InMon Corporation's sFlow: A                                        Method for Monitoring Traffic                                        in Switched and Routed NetworksThis memo defines InMon Corporation's sFlow system.  sFlow is atechnology for monitoring traffic in data networks containing switchesand routers.  In particular, it defines the sampling mechanismsimplemented in an sFlow Agent for monitoring traffic, the sFlow MIB forcontrolling the sFlow Agent, and the format of sample data used by thesFlow Agent when forwarding data to a central data collector.  This memoprovides information for the Internet community.Ginoza                       Informational                      [Page 6]

RFC 3199                  Summary of 3100-3199             February 20033175    Baker         Sep 2001        Aggregation of RSVP for IPv4                                        and IPv6 ReservationsThis document describes the use of a single RSVP (Resource ReSerVationProtocol) reservation to aggregate other RSVP reservations across atransit routing region, in a manner conceptually similar to the use ofVirtual Paths in an ATM (Asynchronous Transfer Mode) network.  Itproposes a way to dynamically create the aggregate reservation, classifythe traffic for which the aggregate reservation applies, determine howmuch bandwidth is needed to achieve the requirement, and recover thebandwidth when the sub-reservations are no longer required.  It alsocontains recommendations concerning algorithms and policies forpredictive reservations.  [STANDARDS TRACK]3174    Eastlake      Sep 2001        US Secure Hash Algorithm 1                                        (SHA1)The purpose of this document is to make the SHA-1 (Secure Hash Algorithm1) hash algorithm conveniently available to the Internet community.This memo provides information for the Internet community.3173    Shacham       Sep 2001        IP Payload Compression                                        Protocol (IPComp)This document describes a protocol intended to provide losslesscompression for Internet Protocol datagrams in an Internet environment.[STANDARDS TRACK]3172    Huston        Sep 2001        Management Guidelines &                                        Operational Requirements for                                        the Address and Routing                                        Parameter Area Domain ("arpa")This memo describes the management and operational requirements for theaddress and routing parameter area ("arpa") domain.  This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.Ginoza                       Informational                      [Page 7]

RFC 3199                  Summary of 3100-3199             February 20033171    Albanna       Aug 2001        IANA Guidelines for IPv4                                        Multicast Address AssignmentsThis memo provides guidance for the Internet Assigned Numbers Authority(IANA) in assigning IPv4 multicast addresses.  This document specifiesan Internet Best Current Practices for the Internet Community, andrequests discussion and suggestions for improvements.3170    Quinn         Sep 2001        IP Multicast Applications:                                        Challenges and SolutionsThis document describes the challenges involved with designing andimplementing multicast applications.  It is an introductory guide forapplication developers that highlights the unique considerations ofmulticast applications as compared to unicast applications.  This memoprovides information for the Internet community.3169    Beadles       Sep 2001        Criteria for Evaluating                                        Network Access Server                                        ProtocolsThis document defines requirements for protocols used by Network AccessServers (NAS).  This memo provides information for the Internetcommunity.3168    Ramakrishnan  Sep 2001        The Addition of Explicit                                        Congestion Notification (ECN)                                        to IPThis memo specifies the incorporation of ECN (Explicit CongestionNotification) to TCP and IP, including ECN's use of two bits in the IPheader.  [STANDARDS TRACK]3167    Meyer         Aug 2001        Request to MoveRFC 1745 to                                        Historic StatusRFC 1745, "BGP4/IDRP for IP---OSPF Interaction", describes technologywhich was never deployed in the public internet.  This document requeststhatRFC 1745 be moved to Historic status.  This memo providesinformation for the Internet community.Ginoza                       Informational                      [Page 8]

RFC 3199                  Summary of 3100-3199             February 20033166    Meyer         Aug 2001        Request to MoveRFC 1403 to                                        Historic StatusRFC 1403, "BGP OSPF Interaction", describes technology which is nolonger used.  This document requests thatRFC 1403 be moved to Historicstatus.  This memo provides information for the Internet community.3165    Levi          Aug 2001        Definitions of Managed Objects                                        for the Delegation of                                        Management ScriptsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes a set of managed objects that allow thedelegation of management scripts to distributed managers.  [STANDARDSTRACK]3164    Lonvick       Aug 2001        The BSD syslog ProtocolThis document describes the observed behavior of the syslog protocol.This memo provides information for the Internet community.3163    Zuccherato    Aug 2001        ISO/IEC 9798-3 Authentication                                        SASL MechanismThis document defines a SASL (Simple Authentication and Security Layer)authentication mechanism based on ISO/IEC 9798-3 and FIPS PUB 196 entityauthentication.  This memo defines an Experimental Protocol for theInternet community.3162    Aboba         Aug 2001        RADIUS and IPv6This document specifies the operation of RADIUS (Remote AuthenticationDial In User Service) when run over IPv6 as well as the RADIUSattributes used to support IPv6 network access.  [STANDARDS TRACK]Ginoza                       Informational                      [Page 9]

RFC 3199                  Summary of 3100-3199             February 20033161    Adams         Aug 2001        Internet X.509 Public Key                                        Infrastructure Time-Stamp                                        Protocol (TSP)This document describes the format of a request sent to a Time StampingAuthority (TSA) and of the response that is returned.  It alsoestablishes several security-relevant requirements for TSA operation,with regards to processing requests to generate responses.  [STANDARDSTRACK]3160    Harris        Aug 2001        The Tao of IETF - A Novice's                                        Guide to the Internet                                        Engineering Task ForceThis document describes the inner workings of IETF meetings and WorkingGroups, discusses organizations related to the IETF, and introduces thestandards process.  This memo provides information for the Internetcommunity.3159    McCloghrie    Aug 2001        Structure of Policy                                        Provisioning Information                                        (SPPI)This document, the Structure of Policy Provisioning Information (SPPI),defines the adapted subset of SNMP's Structure of Management Information(SMI) used to write Policy Information Base (PIB) modules.  [STANDARDSTRACK]3158    Perkins       Aug 2001        RTP Testing StrategiesThis memo describes a possible testing strategy for RTP (real-timetransport protocol) implementations.  This memo provides information forthe Internet community.3157    Arsenault     Aug 2001        Securely Available Credentials                                        - RequirementsThis document describes requirements to be placed on Securely AvailableCredentials (SACRED) protocols.  This memo provides information for theInternet community.Ginoza                       Informational                     [Page 10]

RFC 3199                  Summary of 3100-3199             February 20033156    Elkins        Aug 2001        MIME Security with OpenPGPThis document describes how the OpenPGP Message Format can be used toprovide privacy and authentication using the Multipurpose Internet MailExtensions (MIME) security content types described inRFC 1847.[STANDARDS TRACK]3155    Dawkins       Aug 2001        End-to-end Performance                                        Implications of Links with                                        ErrorsThis document discusses the specific TCP mechanisms that are problematicin environments with high uncorrected error rates, and discusses whatcan be done to mitigate the problems without introducing intermediatedevices into the connection.  This document specifies an Internet BestCurrent Practices for the Internet Community, and requests discussionand suggestions for improvements.3154    Kempf         Aug 2001        Requirements and Functional                                        Architecture for an IP Host                                        Alerting ProtocolThis document develops an architecture and a set of requirements neededto support alerting of hosts that are in dormant mode.  The architectureand requirements are designed to guide development of an IP protocol foralerting dormant IP mobile hosts, commonly called paging.  This memoprovides information for the Internet community.3153    Pazhyannur    Aug 2001        PPP MultiplexingThis document describes a method to reduce the PPP (Point-to-PointProtocol) framing overhead used to transport small packets over slowlinks.  [STANDARDS TRACK]3152    Bush          Aug 2001        Delegation of IP6.ARPAThis document discusses the need for delegation of the IP6.ARPA DNSzone, and specifies a plan for the technical operation thereof.  Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.Ginoza                       Informational                     [Page 11]

RFC 3199                  Summary of 3100-3199             February 20033151    Walsh         Aug 2001        A URN Namespace for Public                                        IdentifiersThis document describes a URN (Uniform Resource Name) namespace that isdesigned to allow Public Identifiers to be expressed in URI (UniformResource Identifiers) syntax.  This memo provides information for theInternet community.3150    Dawkins       Jul 2001        End-to-end Performance                                        Implications of Slow LinksThis document makes performance-related recommendations for users ofnetwork paths that traverse "very low bit-rate" links.  This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.3149    Srinath       Sep 2001        MGCP Business Phone PackagesThis document describes a collection of MGCP (Media Gateway ControlProtocol) packages that can be used to take advantage of the featurekeys and displays on digital business phones and IP-Phones.  This memoprovides information for the Internet community.3148    Mathis        Jul 2001        A Framework for Defining                                        Empirical Bulk Transfer                                        Capacity MetricsThis document defines a framework for standardizing multiple BTC (BulkTransport Capacity) metrics that parallel the permitted transportdiversity.  This memo provides information for the Internet community.3147    Christian     Jul 2001        Generic Routing Encapsulation                                        over CLNS NetworksThis document proposes a method for transporting an arbitrary protocolover a CLNS (Connectionless Network Service) network using GRE (GenericRouting Encapsulation).  This may then be used as a method to tunnelIPv4 or IPv6 over CLNS.  This memo provides information for the Internetcommunity.Ginoza                       Informational                     [Page 12]

RFC 3199                  Summary of 3100-3199             February 20033146    Fujisawa      Oct 2001        Transmission of IPv6 Packets                                        over IEEE 1394 NetworksThis document describes the frame format for transmission of IPv6packets and the method of forming IPv6 link-local addresses andstatelessly autoconfigured addresses on IEEE1394 networks.  [STANDARDSTRACK]3145    Verma         Jul 2001        L2TP Disconnect Cause                                        InformationThis document provides an extension to the Layer 2 Tunneling Protocol("L2TP"), a mechanism for tunneling Point-to-Point Protocol (PPP)sessions.  [STANDARDS TRACK]3144    Romascanu     Aug 2001        Remote Monitoring MIB                                        Extensions for Interface                                        Parameters MonitoringThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Thedocument proposes an extension to the Remote Monitoring MIB with amethod of sorting the interfaces of a monitored device according tovalues of parameters specific to this interface.  [STANDARDS TRACK]3143    Cooper        Jun 2001        Known HTTP Proxy/Caching                                        ProblemsThis document catalogs a number of known problems with World Wide Web(WWW) (caching) proxies and cache servers.  The goal of the document isto provide a discussion of the problems and proposed workarounds, andultimately to improve conditions by illustrating problems.  This memoprovides information for the Internet community.3142    Hagino        Jun 2001        An IPv6-to-IPv4 Transport                                        Relay TranslatorThe document describes an IPv6-to-IPv4 transport relay translator (TRT).This memo provides information for the Internet community.Ginoza                       Informational                     [Page 13]

RFC 3199                  Summary of 3100-3199             February 20033141    Hiller        Jun 2001        CDMA2000 Wireless Data                                        Requirements for AAAThis memo specifies cdma2000 wireless data AAA (Authentication,Authorization, Accounting) requirements associated with third generationwireless architecture that supports roaming among service providers fortraditional PPP and Mobile IP services.  This memo provides informationfor the Internet community.3140    Black         Jun 2001        Per Hop Behavior                                        Identification CodesThis document defines a 16 bit encoding mechanism for the identificationof differentiated services Per Hop Behaviors in protocol messages.  ItreplacesRFC 2836.  [STANDARDS TRACK]3139    Sanchez       Jun 2001        Requirements for Configuration                                        Management of IP-based                                        NetworksThis memo discusses different approaches to configure networks andidentifies a set of configuration management requirements for IP-basednetworks.  This memo provides information for the Internet community.3138    Meyer         Jun 2001        Extended Assignments in 233/8This memo provides describes the mapping of the GLOP addressescorresponding to the private AS space.  This memo provides informationfor the Internet community.3137    Retana        Jun 2001        OSPF Stub Router AdvertisementThis memo describes a backward-compatible technique that may be used byOSPF (Open Shortest Path First) implementations to advertiseunavailability to forward transit traffic or to lower the preferencelevel for the paths through such a router.  This memo providesinformation for the Internet community.Ginoza                       Informational                     [Page 14]

RFC 3199                  Summary of 3100-3199             February 20033136    Slutsman      Jun 2001        The SPIRITS ArchitectureThis document describes the architecture for supporting SPIRITSservices, which are those originating in the PSTN (Public SwitchedTelephone Network)and necessitating the interactions between the PSTNand the Internet.  This memo provides information for the Internetcommunity.3135    Border        Jun 2001        Performance Enhancing Proxies                                        Intended to Mitigate                                        Link-Related DegradationsThis document is a survey of Performance Enhancing Proxies (PEPs) oftenemployed to improve degraded TCP performance caused by characteristicsof specific link environments, for example, in satellite, wireless WAN,and wireless LAN environments.  This memo provides information for theInternet community.3134    Dunn          Jun 2001        Terminology for ATM ABR                                        BenchmarkingThis memo discusses and defines terms associated with performancebenchmarking tests and the results of these tests in the context ofAsynchronous Transfer Mode (ATM) based switching devices supporting ABR(Available Bit Rate).  This memo provides information for the Internetcommunity.3133    Dunn          Jun 2001        Terminology for Frame Relay                                        BenchmarkingThis memo discusses and defines terms associated with performancebenchmarking tests and the results of these tests in the context offrame relay switching devices.  This memo provides information for theInternet community.Ginoza                       Informational                     [Page 15]

RFC 3199                  Summary of 3100-3199             February 20033132    Kempf         Jun 2001        Dormant Mode Host Alerting                                        ("IP Paging") Problem                                        StatementThis memo describes paging, assesses the need for IP paging, andpresents a list of recommendations for Seamoby charter items regardingwork on paging.  This memo provides information for the Internetcommunity.3131    Bradner       Jun 2001        3GPP2-IETF Standardization                                        CollaborationThis document describes the standardization collaboration between 3GPP2and IETF.  This memo provides information for the Internet community.3130    Lewis         Jun 2001        Notes from the                                        State-Of-The-Technology:                                        DNSSECThis is a memo of a DNSSEC (Domain Name System Security Extensions)status meeting.  This memo provides information for the Internetcommunity.3129    Thomas        Jun 2001        Requirements for Kerberized                                        Internet Negotiation of KeysThe goal of this document is to produce a streamlined, fast, easilymanaged, and cryptographically sound protocol without requiring publickey.  This memo provides information for the Internet community.3128    Miller        Jun 2001        Protection Against a Variant                                        of the Tiny Fragment AttackThis document discusses howRFC 1858 compliant filters can be vulnerableto a variant of the "Tiny Fragment Attack" described insection 3.1 ofthe RFC.  This document describes the attack and recommends correctiveaction.  This memo provides information for the Internet community.Ginoza                       Informational                     [Page 16]

RFC 3199                  Summary of 3100-3199             February 20033127    Mitton        Jun 2001        Authentication, Authorization,                                        and Accounting: Protocol                                        EvaluationThis memo represents the process and findings of the Authentication,Authorization, and Accounting Working Group (AAA WG) panel evaluatingprotocols proposed against the AAA Network Access Requirements, RFC2989.  This memo provides information for the Internet community.3126    Pinkas        Sep 2001        Electronic Signature Formats                                        for long term electronic                                        signaturesThis document defines the format of an electronic signature that canremain valid over long periods.  This includes evidence as to itsvalidity even if the signer or verifying party later attempts to deny(i.e., repudiates the validity of the signature).  This memo providesinformation for the Internet community.3125    Ross          Sep 2001        Electronic Signature PoliciesThis document defines signature policies for electronic signatures.  Asignature policy is a set of rules for the creation and validation of anelectronic signature, under which the validity of signature can bedetermined.  A given legal/contractual context may recognize aparticular signature policy as meeting its requirements.  This memodefines an Experimental Protocol for the Internet community.3124    Balakrishnan  Jun 2001        The Congestion ManagerThis document describes the Congestion Manager (CM), an end-systemmodule that enables an ensemble of multiple concurrent streams from asender destined to the same receiver and sharing the same congestionproperties to perform proper congestion avoidance and control, andallows applications to easily adapt to network congestion.  [STANDARDSTRACK]Ginoza                       Informational                     [Page 17]

RFC 3199                  Summary of 3100-3199             February 20033123    Koch          Jun 2001        A DNS RR Type for Lists of                                        Address Prefixes (APL RR)The Domain Name System (DNS) is primarily used to translate domain namesinto IPv4 addresses using A RRs (Resource Records).  Several approachesexist to describe networks or address ranges.  This document specifies anew DNS RR type "APL" for address prefix lists.  This memo defines anExperimental Protocol for the Internet community.3122    Conta         Jun 2001        Extensions to IPv6 Neighbor                                        Discovery for Inverse                                        Discovery SpecificationThis memo describes extensions to the IPv6 Neighbor Discovery that allowa node to determine and advertise an IPv6 address corresponding to agiven link-layer address.  [STANDARDS TRACK]3121    Best          Jun 2001        A URN Namespace for OASISThis document describes a URN (Uniform Resource Name) namespace that isengineered by the Organization for the Advancement of StructuredInformation Standards (OASIS) for naming persistent resources publishedby OASIS (such as OASIS Standards, XML (Extensible Markup Language)Document Type Definitions, XML Schemas, Namespaces, Stylesheets, andother documents).  This memo provides information for the Internetcommunity.3120    Best          Jun 2001        A URN Namespace for XML.orgThis document describes a URN (Uniform Resource Name) namespace that isengineered by the Organization for the Advancement of StructuredInformation Standards (OASIS) for naming persistent resources stored inthe XML.org repository (such as XML (Extensible Markup Language)Document Type Definitions, XML Schemas, Namespaces, Stylesheets, andother documents).  This memo provides information for the Internetcommunity.Ginoza                       Informational                     [Page 18]

RFC 3199                  Summary of 3100-3199             February 20033119    Finlayson     Jun 2001        A More Loss-Tolerant RTP                                        Payload Format for MP3 AudioThis document describes a RTP (Real-Time Protocol) payload format fortransporting MPEG (Moving Picture Experts Group) 1 or 2, layer III audio(commonly known as "MP3").  This format is an alternative to thatdescribed inRFC 2250, and performs better if there is packet loss.[STANDARDS TRACK]3118    Droms         Jun 2001        Authentication for DHCP                                        MessagesThis document defines a new Dynamic Host Configuration Protocol (DHCP)option through which authorization tickets can be easily generated andnewly attached hosts with proper authorization can be automaticallyconfigured from an authenticated DHCP server.  [STANDARDS TRACK]3117    Rose          Nov 2001        On the Design of Application                                        ProtocolsThis memo describes the design principles for the Blocks eXtensibleeXchange Protocol (BXXP).  This memo provides information for theInternet community.3116    Dunn  Jun 2001        Methodology for ATM BenchmarkingThis document discusses and defines a number of tests that may be usedto describe the performance characteristics of ATM (AsynchronousTransfer Mode) based switching devices.  In addition to defining thetests this document also describes specific formats for reporting theresults of the tests.  This memo provides information for the Internetcommunity.3115    Dommety       Apr 2001        Mobile IP                                        Vendor/Organization-Specific                                        ExtensionsThis document defines two new extensions to Mobile IP.  These extensionswill facilitate equipment vendors and organizations to make specific useof these extensions as they see fit for research or deployment purposes.[STANDARDS TRACK]Ginoza                       Informational                     [Page 19]

RFC 3199                  Summary of 3100-3199             February 20033114    Nicolls       May 2002        Implementing Company                                        Classification Policy with the                                        S/MIME Security LabelThis document discusses how company security policy for dataclassification can be mapped to the S/MIME security label.  Actualpolicies from three companies provide worked examples.  This memoprovides information for the Internet community.3113    Rosenbrock    Jun 2001        3GPP-IETF Standardization                                        CollaborationThis document describes the standardization collaboration between 3GPPand IETF.  This memo provides information for the Internet community.3112    Zeilenga      May 2001        LDAP Authentication Password                                        SchemaThis document describes schema in support of user/passwordauthentication in a LDAP (Lightweight Directory Access Protocol)directory including the authPassword attribute type.  This memo providesinformation for the Internet community.3111    Guttman       May 2001        Service Location Protocol                                        Modifications for IPv6This document defines the Service Location Protocol Version 2's (SLPv2)use over IPv6 networks.  Since this protocol relies on UDP and TCP, thechanges to support its use over IPv6 are minor.  [STANDARDS TRACK]3110    Eastlake 3rd  May 2001        RSA/SHA-1 SIGs and RSA KEYs in                                        the Domain Name System (DNS)This document describes how to produce RSA/SHA1 SIG resource records(RRs) inSection 3 and, so as to completely replaceRFC 2537, describeshow to produce RSA KEY RRs inSection 2.  [STANDARDS TRACK]3109    Braden        May 2001        Request to Move STD 39 to                                        Historic StatusThis memo changes the status of STD 39, BBN Report 1822, "Specificationof the Interconnection of a Host and an IMP", from Standard to Historic.This memo provides information for the Internet community.Ginoza                       Informational                     [Page 20]

RFC 3199                  Summary of 3100-3199             February 20033108    Kumar         May 2001        Conventions for the use of the                                        Session Description Protocol                                        (SDP) for ATM Bearer                                        ConnectionsThis document describes conventions for using the Session DescriptionProtocol (SDP) described inRFC 2327 for controlling ATM BearerConnections, and any associated ATM Adaptation Layer (AAL).  The AALsaddressed are Type 1, Type 2 and Type 5.  [STANDARDS TRACK]3107    Rekhter       May 2001        Carrying Label Information in                                        BGP-4This document specifies the way in which the label mapping informationfor a particular route is piggybacked in the same Border GatewayProtocol (BGP) Update message that is used to distribute the routeitself.  [STANDARDS TRACK]3106    Eastlake      Apr 2001        ECML v1.1: Field                                        Specifications for E-CommerceCustomers are frequently required to enter substantial amounts ofinformation at an Internet merchant site in order to complete a purchaseor other transaction, especially the first time they go there.  Astandard set of information fields is defined as the first version of anElectronic Commerce Modeling Language (ECML) so that this task can bemore easily automated, for example by wallet software that could fill infields.  Even for the manual data entry case, customers will be lessconfused by varying merchant sites if a substantial number adopt thesestandard fields.  In addition, some fields are defined for merchant toconsumer communication.  This memo provides information for the Internetcommunity.3105    Kempf         Oct 2001        Finding an RSIP Server with                                        SLPThis document contains an SLP service type template that describes theadvertisements made by RSIP servers for their services.  This memodefines an Experimental Protocol for the Internet community.Ginoza                       Informational                     [Page 21]

RFC 3199                  Summary of 3100-3199             February 20033104    Montenegro    Oct 2001        RSIP Support for End-to-end                                        IPsecThis document proposes mechanisms that enable Realm Specific IP (RSIP)to handle end-to-end IPsec (IP Security).  This memo defines anExperimental Protocol for the Internet community.3103    Borella       Oct 2001        Realm Specific IP: Protocol                                        SpecificationThis document presents a protocol with which to implement Realm SpecificIP (RSIP).  The protocol defined herein allows negotiation of resourcesbetween an RSIP host and gateway, so that the host can lease some of thegateway's addressing parameters in order to establish a global networkpresence.  This protocol is designed to operate on the application layerand to use its own TCP or UDP port.  In particular, the protocol allowsa gateway to allocate addressing and control parameters to a host suchthat a flow policy can be enforced at the gateway.  This memo defines anExperimental Protocol for the Internet community.3102    Borella       Oct 2001        Realm Specific IP: FrameworkThis document examines the general framework of Realm Specific IP(RSIP).  RSIP is intended as a alternative to NAT in which the end-to-end integrity of packets is maintained.  We focus on implementationissues, deployment scenarios, and interaction with other layer-threeprotocols.  This memo defines an Experimental Protocol for the Internetcommunity.3101    Murphy        Jan 2003        The OSPF Not-So-Stubby Area                                        (NSSA) OptionThis memo documents an optional type of Open Shortest Path First (OSPF)area that is somewhat humorously referred to as a "not-so-stubby" area(or NSSA).  NSSAs are similar to the existing OSPF stub areaconfiguration option but have the additional capability of importing ASexternal routes in a limited fashion.The OSPF NSSA Option was originally defined inRFC 1587.  The functionaldifferences between this memo andRFC 1587 are explained inAppendix F.All differences, while expanding capability, are backward-compatible innature.  Implementations of this memo and ofRFC 1587 will interoperate.[STANDARDS TRACK]Ginoza                       Informational                     [Page 22]

RFC 3199                  Summary of 3100-3199             February 20033100                                    Never IssuedRFC 3100 was never issued.Security Considerations   Security issues are not discussed in this memo.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.eduGinoza                       Informational                     [Page 23]

RFC 3199                  Summary of 3100-3199             February 2003Full Copyright Statement   Copyright (C) The Internet Society (2003).  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 24]