Movatterモバイル変換

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

RFC 3099                  Summary of 3000-30993098    Gavin         Apr 2001        How to Advertise Responsibly                                        Using E-Mail and Newsgroups or                                        - how NOT to $$$$$  MAKE                                        ENEMIES FAST!  $$$$$This memo offers useful suggestions for responsible advertisingtechniques that can be used via the internet in an environment where theadvertiser, recipients, and the Internet Community can coexist in aproductive and mutually respectful fashion.  This memo providesinformation for the Internet community.3097    Braden        Apr 2001        RSVP Cryptographic                                        Authentication -- Updated                                        Message Type ValueThis memo resolves a duplication in the assignment of RSVP MessageTypes, by changing the Message Types assigned byRFC 2747 to Challengeand Integrity Response messages.  [STANDARDS TRACK]3096    Degermark     Jul 2001        Requirements for robust                                        IP/UDP/RTP header compressionThis document contains requirements for robust IP/UDP/RTP (InternetProtocol/User Datagram Protocol/Real-Time Transport Protocol) headercompression to be developed by the ROHC (Robust Header Compression) WG.It is based on the ROHC charter, discussions in the WG, the 3GPPdocument "3GPP TR 23.922", version 1.0.0 of October 1999, as well ascontributions from 3G.IP.  This memo provides information for theInternet community.3095    Bormann       Jul 2001        RObust Header Compression                                        (ROHC): Framework and four                                        profiles: RTP, UDP, ESP, and                                        uncompressedThis document specifies a highly robust and efficient header compressionscheme for RTP/UDP/IP (Real-Time Transport Protocol, User DatagramProtocol, Internet Protocol), UDP/IP, and ESP/IP (Encapsulating SecurityPayload) headers.  [STANDARDS TRACK]Ginoza                       Informational                      [Page 2]

RFC 3099                  Summary of 3000-30993094    Sprague       Apr 2001        Tekelec's Transport Adapter                                        Layer InterfaceThis document proposes the interfaces of a Signaling Gateway, whichprovides interworking between the Switched Circuit Network (SCN) and anIP network.  This memo provides information for the Internet community.3093    Gaynor        1 Apr 2001      Firewall Enhancement Protocol                                        (FEP)Internet Transparency via the end-to-end architecture of the Internethas allowed vast innovation of new technologies and services [1].However, recent developments in Firewall technology have altered thismodel and have been shown to inhibit innovation.  We propose theFirewall Enhancement Protocol (FEP) to allow innovation, withoutviolating the security model of a Firewall.  This memo providesinformation for the Internet community.3092    Eastlake      1 Apr 2001      Etymology of "Foo"Approximately 212 RFCs so far, starting withRFC 269, contain the terms`foo', `bar', or `foobar' as metasyntactic variables without any properexplanation or definition.  This document rectifies that deficiency.This memo provides information for the Internet community.3091    Kennedy       1 Apr 2001      Pi Digit Generation ProtocolThis memo defines a protocol to provide the Pi digit generation service(PIgen) used between clients and servers on host computers.  This memoprovides information for the Internet community.3090    Lewis         Mar 2001        DNS Security Extension                                        Clarification on Zone StatusThe definition of a secured zone is presented, clarifying and updatingsections ofRFC 2535.RFC 2535 defines a zone to be secured based on aper algorithm basis, e.g., a zone can be secured with RSA keys, and notsecured with DSA keys.  This document changes this to define a zone tobe secured or not secured regardless of the key algorithm used (or notused).  To further simplify the determination of a zone's status,"experimentally secure" status is deprecated.  [STANDARDS TRACK]Ginoza                       Informational                      [Page 3]

RFC 3099                  Summary of 3000-30993089    Kitamura      Apr 2001        A SOCKS-based IPv6/IPv4                                        Gateway MechanismThis document describes a SOCKS-based IPv6/IPv4 gateway mechanism thatenables smooth heterogeneous communications between the IPv6 nodes andIPv4 nodes.  This memo provides information for the Internet community.3088    Zeilenga      Apr 2001        OpenLDAP Root Service An                                        experimental LDAP referral                                        serviceThe OpenLDAP Project is operating an experimental LDAP (LightweightDirectory Access Protocol) referral service known as the "OpenLDAP RootService".  The automated system generates referrals based upon servicelocation information published in DNS SRV RRs (Domain Name Systemlocation of services resource records).  This document describes thisservice.  This memo defines an Experimental Protocol for the Internetcommunity.3087    Campbell      Apr 2001        Control of Service Context                                        using SIP Request-URIThis memo describes a useful way to conceptualize the use of thestandard SIP (Session Initiation Protocol) Request-URI (Uniform ResourceIdentifier) that the authors and many members of the SIP community thinkis suitable as a convention.  It does not define any new protocol withrespect toRFC 2543.  This memo provides information for the Internetcommunity.3086    Nichols       Apr 2001        Definition of Differentiated                                        Services Per Domain Behaviors                                        and Rules for their SpecificationThis document defines and discusses Per-Domain Behaviors in detail andlays out the format and required content for contributions to theDiffserv WG on PDBs and the procedure that will be applied forindividual PDB specifications to advance as WG products.  This format isspecified to expedite working group review of PDB submissions.  Thismemo provides information for the Internet community.Ginoza                       Informational                      [Page 4]

RFC 3099                  Summary of 3000-30993085    Coates        Mar 2001        URN Namespace for NewsML                                        ResourcesThis document describes a URN (Uniform Resource Name) namespace foridentifying NewsML NewsItems.  This memo provides information for theInternet community.3084    Chan          Mar 2001        COPS Usage for Policy                                        Provisioning (COPS-PR)This document describes the use of the Common Open Policy Service (COPS)protocol for support of policy provisioning (COPS-PR).  [STANDARDSTRACK]3083    Woundy        Mar 2001        Baseline Privacy Interface                                        Management Information Base                                        for DOCSIS Compliant Cable                                        Modems and Cable Modem                                        Termination SystemsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines a basic set of managed objects for SNMP-based(Simple Network Management Protocol) management of the Baseline PrivacyInterface (BPI), which provides data privacy for DOCSIS 1.0 (Data-Over-Cable Service Interface Specifications) compliant Cable Modems and CableModem Termination Systems.  This MIB is defined as an extension to theDOCSIS Radio Frequency Interface MIB,RFC 2670.  This memo providesinformation for the Internet community.3082    Kempf         Mar 2001        Notification and Subscription                                        for SLPThe Service Location Protocol (SLP) provides mechanisms whereby serviceagent clients can advertise and user agent clients can query forservices.  The design is very much demand-driven, so that user agentsonly obtain service information when they specifically ask for it.There exists another class of user agent applications, however, thatrequires notification when a new service appears or disappears. In theRFC 2608 design, these applications are forced to poll the network tocatch changes.  In this document, we describe a protocol for allowingsuch clients to be notified when a change occurs, removing the need forpolling.  This memo defines an Experimental Protocol for the Internetcommunity.Ginoza                       Informational                      [Page 5]

RFC 3099                  Summary of 3000-30993081    Rose          Mar 2001        Mapping the BEEP Core onto TCPThis memo describes how a BEEP (Blocks Extensible Exchange Protocol)session is mapped onto a single TCP (Transmission Control Protocol)connection.  [STANDARDS TRACK]3080    Rose          Mar 2001        The Blocks Extensible Exchange                                        Protocol CoreThis memo describes a generic application protocol kernel forconnection-oriented, asynchronous interactions called the BEEP (BlocksExtensible Exchange Protocol) core.  [STANDARDS TRACK]3079    Zorn          Mar 2001        Deriving Keys for use with                                        Microsoft Point-to-Point                                        Encryption (MPPE)This document describes the method used to derive initial MPPE sessionkeys from a variety of credential types.  It is expected that this memowill be updated whenever Microsoft defines a new key derivation methodfor MPPE, since its primary purpose is to provide an open, easilyaccessible reference for third-parties wishing to interoperate withMicrosoft products.  This memo provides information for the Internetcommunity.3078    Pall          Mar 2001        Microsoft Point-To-Point                                        Encryption (MPPE) ProtocolThis document describes the use of the Microsoft Point to PointEncryption (MPPE) to enhance the confidentiality of PPP-encapsulatedpackets.  This memo provides information for the Internet community.3077    Duros         Mar 2001        A Link-Layer Tunneling                                        Mechanism for Unidirectional                                        LinksThis document describes a mechanism to emulate full bidirectionalconnectivity between all nodes that are directly connected by aunidirectional link.  [STANDARDS TRACK]Ginoza                       Informational                      [Page 6]

RFC 3099                  Summary of 3000-30993076    Boyer         Mar 2001        Canonical XML Version 1.0This specification describes a method for generating a physicalrepresentation, the canonical form, of an XML document that accounts forthe permissible changes.  This memo provides information for theInternet community.3075    Eastlake      Mar 2001        XML-Signature Syntax and                                        ProcessingThis document specifies XML (Extensible Markup Language) digitalsignature processing rules and syntax.  [STANDARDS TRACK]3074    Volz          Feb 2001        DHC Load Balancing AlgorithmThis document proposes a method of algorithmic load balancing.[STANDARDS TRACK]3073    Collins       Mar 2001        Portable Font Resource (PFR) -                                        application/font-tdpfr MIME                                        Sub-type RegistrationThis document describes the registration of the Multipurpose InternetMail Extensions (MIME) sub-type application/font-tdpfr.  The encoding isdefined by the PFR Specification.  This memo provides information forthe Internet community.3072    Wildgrube     Mar 2001        Structured Data Exchange                                        Format (SDXF)This specification describes an all-purpose interchange format for useas a file format or for net-working.  This memo provides information forthe Internet community.Ginoza                       Informational                      [Page 7]

RFC 3099                  Summary of 3000-30993071    Klensin       Feb 2001        Reflections on the DNS,RFC1591, and Categories of                                        DomainsThis document is being published primarily for historical context andcomparative purposes, essentially to document some thoughts about how1591 might have been interpreted and adjusted by the Internet AssignedNumbers Authority (IANA) and ICANN to better reflect today's world whileretaining characteristics and policies that have proven to be effectivein supporting Internet growth and stability.  This memo providesinformation for the Internet community.3070    Rawat         Feb 2001        Layer Two Tunneling Protocol                                        (L2TP) over Frame RelayThis document describes how L2TP is implemented over Frame RelayPermanent Virtual Circuits (PVCs) and Switched Virtual Circuits (SVCs).[STANDARDS TRACK]3069    McPherson     Feb 2001        VLAN Aggregation for Efficient                                        IP Address AllocationThis document introduces the concept of Virtual Local Area Network(VLAN) aggregation as it relates to IPv4 address allocation.  This memoprovides information for the Internet community.3068    Huitema       Jun 2001        An Anycast Prefix for 6to4                                        Relay RoutersThis memo introduces a "6to4 anycast address" in order to simplify theconfiguration of 6to4 routers.  It also defines how this address will beused by 6to4 relay routers, how the corresponding "6to4 anycast prefix"will be advertised in the IGP and in the EGP.  The memo documents thereservation by IANA (Internet Assigned Numbers Authority) of the "6to4relay anycast prefix."  [STANDARDS TRACK]Ginoza                       Informational                      [Page 8]

RFC 3099                  Summary of 3000-30993067    Arvidsson     Feb 2001        TERENA's Incident Object                                        Description and Exchange                                        Format RequirementsThe purpose of the Incident Object Description and Exchange Format is todefine a common data format for the description, archiving and exchangeof information about incidents between CSIRTs (Computer SecurityIncident Response Teams) (including alert, incident in investigation,archiving, statistics, reporting, etc.).  This document describes thehigh-level requirements for such a description and exchange format,including the reasons for those requirements.  This memo providesinformation for the Internet community.3066    Alvestrand    Jan 2001        Tags for the Identification of                                        LanguagesThis document describes a language tag for use in cases where it isdesired to indicate the language used in an information object, how toregister values for use in this language tag, and a construct formatching such language tags.  This document specifies an Internet BestCurrent Practices for the Internet Community, and requests discussionand suggestions for improvements.3065    Traina        Feb 2001        Autonomous System                                        Confederations for BGPThis document describes an extension to BGP which may be used to createa confederation of autonomous systems that is represented as a singleautonomous system to BGP peers external to the confederation, therebyremoving the "full mesh" requirement.  The intention of this extensionis to aid in policy administration and reduce the management complexityof maintaining a large autonomous system.  [STANDARDS TRACK]3064    Foster        Feb 2001        MGCP CAS PackagesThis document contains a collection of media gateway Channel AssociatedSignaling (CAS) packages for R1 CAS, North American CAS, CAS PBXinterconnect as well as basic FXO support.  This memo providesinformation for the Internet community.Ginoza                       Informational                      [Page 9]

RFC 3099                  Summary of 3000-30993063    Ohba          Feb 2001        MPLS Loop Prevention MechanismThis paper presents a simple mechanism, based on "threads", which can beused to prevent Multiprotocol Label Switching (MPLS) from setting uplabel switched path (LSPs) which have loops.  This memo defines anExperimental Protocol for the Internet community.3062    Zeilenga      Feb 2001        LDAP Password Modify Extended                                        OperationThis document describes an LDAP extended operation to allow modificationof user passwords which is not dependent upon the form of theauthentication identity nor the password storage mechanism used.[STANDARDS TRACK]3061    Mealling      Feb 2001        A URN Namespace of Object                                        IdentifiersThis document describes a Uniform Resource Name (URN) namespace thatcontains Object Identifiers (OIDs).  This memo provides information forthe Internet community.3060    Moore         Feb 2001        Policy Core Information Model                                        -- Version 1 SpecificationThis document presents the object-oriented information model forrepresenting policy information developed jointly in the IETF PolicyFramework WG and as extensions to the Common Information Model (CIM)activity in the Distributed Management Task Force (DMTF).  [STANDARDSTRACK]3059    Guttman       Feb 2001        Attribute List Extension for                                        the Service Location ProtocolThis document specifies a SLPv2 extension which allows a User Agent (UA)to request a service's attributes be included as an extension to ServiceReply messages.  This will eliminate the need for multiple round tripmessages for a UA to acquire all service information.  [STANDARDS TRACK]Ginoza                       Informational                     [Page 10]

RFC 3099                  Summary of 3000-30993058    Teiwes        Feb 2001        Use of the IDEA Encryption                                        Algorithm in CMSThis memo specifies how to incorporate International Data EncryptionAlgorithm (IDEA) into CMS or S/MIME as an additional strong algorithmfor symmetric encryption.  This memo provides information for theInternet community.3057    Morneault     Feb 2001        ISDN Q.921-User Adaptation                                        LayerThis document defines a protocol for backhauling of ISDN Q.921 Usermessages over IP using the Stream Control Transmission Protocol (SCTP).This protocol would be used between a Signaling Gateway (SG) and MediaGateway Controller (MGC).  [STANDARDS TRACK]3056    Carpenter     Feb 2001        Connection of IPv6 Domains via                                        IPv4 CloudsThis memo specifies an optional interim mechanism for IPv6 sites tocommunicate with each other over the IPv4 network without explicittunnel setup, and for them to communicate with native IPv6 domains viarelay routers.  [STANDARDS TRACK]3055    Krishnaswamy  Feb 2001        Management Information Base                                        for the PINT Services                                        ArchitectureThis memo describes a proposed Management Information Base (MIB) for thePSTN/Internet Interworking (PINT) Services Architecture.  [STANDARDSTRACK]3054    Blatherwick   Jan 2001        Megaco IP Phone Media Gateway                                        Application ProfileThis document specifies a particular application of the Megaco/H.248Protocol for control of Internet telephones and similar appliances:  theMegaco IP Phone Media Gateway.  This memo provides information for theInternet community.Ginoza                       Informational                     [Page 11]

RFC 3099                  Summary of 3000-30993053    Durand        Jan 2001        IPv6 Tunnel BrokerThe motivation for the development of the tunnel broker model is to helpearly IPv6 adopters to hook up to an existing IPv6 network (e.g., the6bone) and to get stable, permanent IPv6 addresses and DNS names.  Theconcept of the tunnel broker was first presented at Orlando's IETF inDecember 1998.  Two implementations were demonstrated during theGrenoble IPng & NGtrans interim meeting in February 1999.  This memoprovides information for the Internet community.3052    Eder          Jan 2001        Service Management                                        Architectures Issues and                                        ReviewThe purpose of this document is to explore the problems of defining aService management framework and to examine some of the issues thatstill need to be resolved.  This memo provides information for theInternet community.3051    Heath         Jan 2001        IP Payload Compression Using                                        ITU-T V.44 Packet MethodThis document describes a compression method based on the datacompression algorithm described in International Telecommunication Union(ITU-T) Recommendation V.44.  This document defines the application ofV.44 Packet Method to the Internet Protocol (IP) Payload CompressionProtocol (RFC 2393).  This memo provides information for the Internetcommunity.3050    Lennox        Jan 2001        Common Gateway Interface for                                        SIPThis document defines a SIP CGI interface for providing SIP services ona SIP server.  This memo provides information for the Internetcommunity.Ginoza                       Informational                     [Page 12]

RFC 3099                  Summary of 3000-30993049    Naugle        Jan 2001        TN3270E Service Location and                                        Session BalancingThis document discusses the implementation of Service Location Protocol(SLP) and session balancing with a TN3270E emulator in a client serverimplementation with a TN3270E server.  [STANDARDS TRACK]3048    Whetten       Jan 2001        Reliable Multicast Transport                                        Building Blocks for                                        One-to-Many Bulk-Data TransferThis document describes a framework for the standardization of bulk-datareliable multicast transport.  This memo provides information for theInternet community.3047    Luthi         Jan 2001        RTP Payload Format for ITU-T                                        Recommendation G.722.1This document describes the payload format for including G.722.1generated bit streams within an RTP packet.  Also included here are thenecessary details for the use of G.722.1 with MIME and SDP.  [STANDARDSTRACK]3046    Patrick       Jan 2001        DHCP Relay Agent Information                                        OptionNewer high-speed public Internet access technologies call for a high-speed modem to have a local area network (LAN) attachment to one or morecustomer premise hosts.  It is advantageous to use the Dynamic HostConfiguration Protocol (DHCP) as defined inRFC 2131 to assign customerpremise host IP addresses in this environment.  However, a number ofsecurity and scaling problems arise with such "public" DHCP use.  Thisdocument describes a new DHCP option to address these issues.  Thisoption extends the set of DHCP options as defined inRFC 2132.[STANDARDS TRACK]3045    Meredith      Jan 2001        Storing Vendor Information in                                        the LDAP root DSEThis document specifies two Lightweight Directory Access Protocol (LDAP)attributes, vendorName and vendorVersion that MAY be included in theroot DSA-specific Entry (DSE) to advertise vendor-specific information.This memo provides information for the Internet community.Ginoza                       Informational                     [Page 13]

RFC 3099                  Summary of 3000-30993044    Rozenfeld     Jan 2001        Using The ISSN (International                                        Serial Standard Number) as URN                                        (Uniform Resource Names)                                        within an ISSN-URN NamespaceThis document presents how the ISSN - International Standard SerialNumber - which is a persistent number for unique identification ofserials widely recognised and used in the bibliographic world, can besupported within the Uniform Resource Name (URN) framework as a specificURN namespace identifier.  This memo provides information for theInternet community.3043    Mealling      Jan 2001        The Network Solutions Personal                                        Internet Name (PIN): A URN                                        Namespace for People and                                        OrganizationsThis document describes a Uniform Resource Name (URN) namespace that isengineered by Network Solutions, Inc. for naming people andorganizations.  This memo provides information for the Internetcommunity.3042    Allman        Jan 2001        Enhancing TCP's Loss Recovery                                        Using Limited TransmitThis document proposes a new Transmission Control Protocol (TCP)mechanism that can be used to more effectively recover lost segmentswhen a connection's congestion window is small, or when a large numberof segments are lost in a single transmission window.  [STANDARDS TRACK]3041    Narten        Jan 2001        Privacy Extensions for                                        Stateless Address                                        Autoconfiguration in IPv6This document describes an extension to IPv6 stateless addressautoconfiguration for interfaces whose interface identifier is derivedfrom an IEEE identifier.  [STANDARDS TRACK]Ginoza                       Informational                     [Page 14]

RFC 3099                  Summary of 3000-30993040    Cooper        Jan 2001        Internet Web Replication and                                        Caching TaxonomyThis memo specifies standard terminology and the taxonomy of webreplication and caching infrastructure as deployed today.  It introducesstandard concepts, and protocols used today within this applicationdomain.  This memo provides information for the Internet community.3039    Santesson     Jan 2001        Internet X.509 Public Key                                        Infrastructure Qualified                                        Certificates ProfileThis document forms a certificate profile for Qualified Certificates,based onRFC 2459, for use in the Internet.  The goal of this documentis to define a general syntax independent of local legal requirements.[STANDARDS TRACK]3038    Nagami        Jan 2001        VCID Notification over ATM                                        link for LDPThis document specifies the procedures for the communication of VCIDvalues between neighboring ATM-LSRs that must occur in order to ensurethis property.  [STANDARDS TRACK]3037    Thomas        Jan 2001        LDP ApplicabilityA fundamental concept in MPLS is that two Label Switching Routers (LSRs)must agree on the meaning of the labels used to forward traffic betweenand through them.  This common understanding is achieved by using a setof procedures, called a label distribution protocol, by which one LSRinforms another of label bindings it has made.  This document describesthe applicability of a set of such procedures called LDP (for LabelDistribution Protocol) by which LSRs distribute labels to support MPLSforwarding along normally routed paths.  This memo provides informationfor the Internet community.Ginoza                       Informational                     [Page 15]

RFC 3099                  Summary of 3000-30993036    Andersson     Jan 2001        LDP SpecificationA fundamental concept in MPLS is that two Label Switching Routers (LSRs)must agree on the meaning of the labels used to forward traffic betweenand through them.  This common understanding is achieved by using a setof procedures, called a label distribution protocol, by which one LSRinforms another of label bindings it has made.  This document defines aset of such procedures called LDP (for Label Distribution Protocol) bywhich LSRs distribute labels to support MPLS forwarding along normallyrouted paths.  [STANDARDS TRACK]3035    Davie         Jan 2001        MPLS using LDP and ATM VC                                        SwitchingThis document extends and clarifies the relevant portions ofRFC 3031andRFC 3036 by specifying in more detail the procedures which to beused when distributing labels to or from ATM-LSRs, when those labelsrepresent Forwarding Equivalence Classes (FECs, seeRFC 3031) for whichthe routes are determined on a hop-by-hop basis by network layer routingalgorithms.  [STANDARDS TRACK]3034    Conta         Jan 2001        Use of Label Switching on                                        Frame Relay Networks                                        SpecificationThis document defines the model and generic mechanisms for MultiprotocolLabel Switching on Frame Relay networks.  [STANDARDS TRACK]3033    Suzuki        Jan 2001        The Assignment of the                                        Information Field and Protocol                                        Identifier in the Q.2941 Generic                                        Identifier and Q.2957                                        User-to-user Signaling for the                                        Internet ProtocolThe purpose of this document is to specify the assignment of theinformation field and protocol identifier in the Q.2941 GenericIdentifier and Q.2957 User-to-user Signaling for the Internet protocol.[STANDARDS TRACK]Ginoza                       Informational                     [Page 16]

RFC 3099                  Summary of 3000-30993032    Rosen         Jan 2001        MPLS Label Stack EncodingThis document specifies the encoding to be used by an LSR in order totransmit labeled packets on Point-to-Point Protocol (PPP) data links, onLAN data links, and possibly on other data links as well.  This documentalso specifies rules and procedures for processing the various fields ofthe label stack encoding.  [STANDARDS TRACK]3031    Rosen         Jan 2001        Multiprotocol Label Switching                                        ArchitectureThis document specifies the architecture for Multiprotocol LabelSwitching (MPLS).  [STANDARDS TRACK]3030    Vaudreuil     Dec 2000        SMTP Service Extensions for                                        Transmission of Large and                                        Binary MIME MessagesThis memo defines two extensions to the SMTP (Simple Mail TransferProtocol) service.  [STANDARDS TRACK]3029    Adams         Feb 2001        Internet X.509 Public Key                                        Infrastructure Data Validation                                        and Certification Server                                        ProtocolsThis document describes a general Data Validation and CertificationServer (DVCS) and the protocols to be used when communicating with it.This memo defines an Experimental Protocol for the Internet community.3028    Showalter     Jan 2001        Sieve: A Mail Filtering                                        LanguageThis document describes a language for filtering e-mail messages at timeof final delivery.  [STANDARDS TRACK]Ginoza                       Informational                     [Page 17]

RFC 3099                  Summary of 3000-30993027    Holdrege      Jan 2001        Protocol Complications with                                        the IP Network Address                                        TranslatorThe purpose of this document is to identify the protocols andapplications that break with NAT enroute.  The document also attempts toidentify any known workarounds.  This document attempts to capture asmuch information as possible, but is by no means a comprehensivecoverage.  This memo provides information for the Internet community.3026    Blane         Jan 2001        Liaison to IETF/ISOC on ENUMWorking Party 1/2, of the International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) held a meeting of itscollaborators in Berlin Germany 19-26 October 2000.  This liaison fromWP1/2 to the IETF/ISOC conveys the understandings of the WP1/2collaborators resulting from the discussions.  This memo providesinformation for the Internet community.3025    Dommety       Feb 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]3024    Montenegro    Jan 2001        Reverse Tunneling for Mobile                                        IP, revisedThis document proposes backwards-compatible extensions to Mobile IP tosupport topologically correct reverse tunnels.  This document does notattempt to solve the problems posed by firewalls located between thehome agent and the mobile node's care-of address.  [STANDARDS TRACK]Ginoza                       Informational                     [Page 18]

RFC 3099                  Summary of 3000-30993023    Murata        Jan 2001        XML Media TypesThis document standardizes five new media types -- text/xml,application/xml, text/xml-external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd -- for use in exchangingnetwork entities that are related to the Extensible Markup Language(XML).  This document also standardizes a convention (using the suffix'+xml') for naming media types outside of these five types when thosemedia types represent XML MIME (Multipurpose Internet Mail Extensions)entities.  [STANDARDS TRACK]3022    Srisuresh     Jan 2001        Traditional IP Network Address                                        Translator (Traditional NAT)The NAT operation described in this document extends address translationintroduced inRFC 1631 and includes a new type of network address andTCP/UDP port translation.  In addition, this document corrects theChecksum adjustment algorithm published inRFC 1631 and attempts todiscuss NAT operation and limitations in detail.  This memo providesinformation for the Internet community.3021    Retana        Dec 2000        Using 31-Bit Prefixes on IPv4                                        Point-to-Point LinksWith ever-increasing pressure to conserve IP address space on theInternet, it makes sense to consider where relatively minor changes canbe made to fielded practice to improve numbering efficiency.  One suchchange, proposed by this document, is to halve the amount of addressspace assigned to point-to-point links (common throughout the Internetinfrastructure) by allowing the use of 31-bit subnet masks in a verylimited way.  [STANDARDS TRACK]3020    Pate          Dec 2000        Definitions of Managed Objects                                        for Monitoring and Controlling                                        the UNI/NNI Multilink Frame                                        Relay FunctionThis memo defines a Management Information Base (MIB) for monitoring andcontrolling a UNI/NNI Multilink Frame Relay Function as defined in FrameRelay Forum FRF.16.  [STANDARDS TRACK]Ginoza                       Informational                     [Page 19]

RFC 3099                  Summary of 3000-30993019    Haberman      Jan 2001        IP Version 6 Management                                        Information Base for The                                        Multicast Listener Discovery                                        ProtocolThis document defines a portion of the Management Information Base (MIB)for use with network management protocols in Internet Protocol Version 6internets.  Specifically, this document is the MIB module that definesmanaged objects for implementations of the Multicast Listener DiscoveryProtocol [RFC2710].  [STANDARDS TRACK]3018    Bogdanov      Dec 2000        Unified Memory Space Protocol                                        SpecificationThis document specifies Unified Memory Space Protocol (UMSP), whichgives a capability of immediate access to memory of the remote nodes.This memo defines an Experimental Protocol for the Internet community.3017    Riegel        Dec 2000        XML DTD for Roaming Access                                        Phone BookThis document defines the syntax as well as the semantics of theinformation to be included in the phone book for roaming applications.[STANDARDS TRACK]3016    Kikuchi       Nov 2000        RTP Payload Format for MPEG-4                                        Audio/Visual StreamsThis document describes Real-Time Transport Protocol (RTP) payloadformats for carrying each of MPEG-4 Audio and MPEG-4 Visual bitstreamswithout using MPEG-4 Systems.  [STANDARDS TRACK]3015    Cuervo        Nov 2000        Megaco Protocol Version 1.0This document defines the protocol used between elements of a physicallydecomposed multimedia gateway, i.e. a Media Gateway and a Media GatewayController.  [STANDARDS TRACK]Ginoza                       Informational                     [Page 20]

RFC 3099                  Summary of 3000-30993014    Kavasseri     Nov 2000        Notification Log MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes managed objects used for logging Simple NetworkManagement Protocol (SNMP) Notifications.  [STANDARDS TRACK]3013    Killalea      Nov 2000        Recommended Internet Service                                        Provider Security Services and                                        ProceduresThe purpose of this document is to express what the engineeringcommunity as represented by the IETF expects of Internet ServiceProviders (ISPs) with respect to security.  This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.3012    Perkins       Nov 2000        Mobile IPv4 Challenge/Response                                        ExtensionsIn this specification, we define extensions for the Mobile IP AgentAdvertisements and the Registration Request that allow a foreign agentto use a challenge/response mechanism to authenticate the mobile node.[STANDARDS TRACK]3011    Waters        Nov 2000        The IPv4 Subnet Selection                                        Option for DHCPThis memo defines a new Dynamic Host Configuration Protocol (DHCP)option for selecting the subnet on which to allocate an address.[STANDARDS TRACK]3010    Shepler       Dec 2000        NFS version 4 ProtocolNFS (Network File System) version 4 is a distributed file systemprotocol which owes heritage to NFS protocol versions 2 [RFC1094] and 3[RFC1813].  Unlike earlier versions, the NFS version 4 protocol supportstraditional file access while integrating support for file locking andthe mount protocol.  In addition, support for strong security (and itsnegotiation), compound operations, client caching, andinternationalization have been added.  Of course, attention has beenapplied to making NFS version 4 operate well in an Internet environment.[STANDARDS TRACK]Ginoza                       Informational                     [Page 21]

RFC 3099                  Summary of 3000-30993009    Rosenberg     Nov 2000        Registration of parityfec MIME                                        typesThe RTP (Real-time Transport Protocol) payload format for genericforward error correction allows RTP participants to improve lossresiliency through the use of traditional parity-based channel codes.This payload format requires four new MIME types, audio/parityfec,video/parityfec, text/parityfec and application/parityfec.  Thisdocument serves as the MIME type registration for those formats.[STANDARDS TRACK]3008    Wellington    Nov 2000        Domain Name System Security                                        (DNSSEC) Signing AuthorityThis document proposes a revised model of Domain Name System Security(DNSSEC) Signing Authority.  The revised model is designed to clarifyearlier documents and add additional restrictions to simplify the secureresolution process.  Specifically, this affects the authorization ofkeys to sign sets of records.  [STANDARDS TRACK]3007    Wellington    Nov 2000        Secure Domain Name System                                        (DNS) Dynamic UpdateThis document proposes a method for performing secure Domain Name System(DNS) dynamic updates.  [STANDARDS TRACK]3006    Davie         Nov 2000        Integrated Services in the                                        Presence of Compressible FlowsThis specification describes an extension to the TSpec which enables asender of potentially compressible data to provide hints to int-servrouters about the compressibility they may obtain.  [STANDARDS TRACK]Ginoza                       Informational                     [Page 22]

RFC 3099                  Summary of 3000-30993005    Harris        Nov 2000        IETF Discussion List CharterThe Internet Engineering Task Force (IETF) discussion mailing listfurthers the development and specification of Internet technologythrough discussion of technical issues, and hosts discussions of IETFdirection, policy, meetings, and procedures.  As this is the mostgeneral IETF mailing list, considerable latitude is allowed.Advertising, whether to solicit business or promote employmentopportunities, falls well outside the range of acceptable topics, as dodiscussions of a personal nature.  This document specifies an InternetBest Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.3004    Stump         Nov 2000        The User Class Option for DHCPThis option is used by a Dynamic Host Configuration Protocol (DHCP)client to optionally identify the type or category of user orapplications it represents.  The information contained in this option isan opaque field that represents the user class of which the client is amember.  Based on this class, a DHCP server selects the appropriateaddress pool to assign an address to the client and the appropriateconfiguration parameters.  This option should be configurable by a user.[STANDARDS TRACK]3003    Nilsson       Nov 2000        The audio/mpeg Media TypeThe audio layers of the MPEG-1 and MPEG-2 standards are in frequent useon the internet, but there is no uniform Multipurpose Internet MailExtension (MIME) type for these files.  The intention of this documentis to define the media type audio/mpeg to refer to this kind ofcontents.  [STANDARDS TRACK]3002    Mitzel        Dec 2000        Overview of 2000 IAB Wireless                                        Internetworking WorkshopThis document provides an overview of a workshop held by the InternetArchitecture Board (IAB) on wireless internetworking.  This memoprovides information for the Internet community.Ginoza                       Informational                     [Page 23]

RFC 3099                  Summary of 3000-30993001    Mealling      Nov 2000        A URN Namespace of Object                                        IdentifiersThis document describes a Uniform Resource Names (URN) namespace thatcontains Object Identifiers (OIDs).  This memo provides information forthe Internet community.3000    Reynolds      Nov 2001        Internet Official Protocol                                        StandardsThis memo contains a snapshot of the state of standardization ofprotocols used in the Internet as of October 25, 2001.  It listsofficial protocol standards and Best Current Practice RFCs; it is not acomplete index to the RFC series.  The latest version of this memo isdesignated STD 1.  [STANDARDS TRACK]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 24]

RFC 3099                  Summary of 3000-3099Full Copyright Statement   Copyright (C) The Internet Society (2001).  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 25]