Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group A. DeLaCruzRequest for Comments: 2599 ISICategory: Informational March 2000Request for Comments Summary RFC Numbers 2500-2599Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 2500 through RFCs 2599. 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 (2000). 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--- ------ ---- -----2599 Delacruz Mar 2000 Request for Comments SummaryThis memo.2598 Jacobson Jun 1999 An Expedited Forwarding PHBThe definition of PHBs (per-hop forwarding behaviors) is a critical partof the work of the Diffserv Working Group. This document describes aPHB called Expedited Forwarding. [STANDARDS-TRACK]DeLaCruz Informational [Page 1]
RFC 2599 Summary of 2500-2599 March 20002597 Heinanen Jun 1999 Assured Forwarding PHB GroupThis document defines a general use Differentiated Services (DS)Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF).[STANDARDS-TRACK]2596 Wahl May 1999 Use of Language Codes in LDAPThis document describes how language codes are carried in LDAP and areto be interpreted by LDAP servers. [STANDARDS-TRACK]2595 Newman Jun 1999 Using TLS with IMAP, POP3 and ACAPRecognizing that such sites will desire simple password authenticationin combination with TLS encryption, this specification defines the PLAINSASL mechanism for use with protocols which lack a simple passwordauthentication command such as ACAP and SMTP. [STANDARDS-TRACK]2594 Hazewinkel May 1999 Definitions of Managed Objects for WWW ServicesThis 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 objects for managing World Wide Web(WWW) services. [STANDARDS-TRACK]2593 Schoenwaelder May 1999 Script MIB Extensibility Protocol Version 1.0The Script MIB extensibility protocol (SMX) defined in this memoseparates language specific runtime systems from language independentScript MIB implementations. This memo defines an Experimental Protocolfor the Internet community.DeLaCruz Informational [Page 2]
RFC 2599 Summary of 2500-2599 March 20002592 Levi May 1999 Definitions of Managed Objects for the Delegation of Management ScriptsThis memo defines a portion of the Management Information Base (MIB)for use with network management protocols in the Internet community.In particular, it describes a set of managed objects that allow thedelegation of management scripts to distributed managers.[STANDARDS-TRACK]2591 Levi May 1999 Definitions of Managed Objects for Scheduling Management OperationsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.[STANDARDS-TRACK]2590 Conta May 1999 Transmission of IPv6 Packets over Frame Relay Networks SpecificationThis memo describes mechanisms for the transmission of IPv6 packets overFrame Relay networks. [STANDARDS-TRACK]2589 Yaacovi May 1999 Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory ServicesThis document defines the requirements for dynamic directory servicesand specifies the format of request and response extended operations forsupporting client-server interoperation in a dynamic directoriesenvironment. [STANDARDS-TRACK]2588 Finlayson May 1999 IP Multicast and FirewallsIn this document, we discuss the issues surrounding the traversal of IPmulticast traffic across a firewall, and describe possible ways in whicha firewall can implement and control this traversal. We also explainwhy some firewall mechanisms - such as SOCKS - that were designedspecifically for unicast traffic, are less appropriate for multicast.This memo provides information for the Internet community.DeLaCruz Informational [Page 3]
RFC 2599 Summary of 2500-2599 March 20002587 Boeyen Jun 1999 Internet X.509 Public Key Infrastructure LDAPv2 SchemaThe schema defined in this document is a minimal schema to support PKIXin an LDAPv2 environment, as defined inRFC 2559. Only PKIX-specificcomponents are specified here. [STANDARDS-TRACK]2586 Salsman May 1999 The Audio/L16 MIME content typeThis document defines the audio/L16 MIME type, a reasonable qualityaudio format for use in Internet applications. This memo providesinformation for the Internet community.2585 Housley May 1999 Internet X.509 Public Key Infrastructure Operational The protocol conventions Protocols: FTP and HTTPThe protocol conventions described in this document satisfy some of theoperational requirements of the Internet Public Key Infrastructure(PKI). This document specifies the conventions for using the FileTransfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP) toobtain certificates and certificate revocation lists (CRLs) from PKIrepositories. [STANDARDS-TRACK]2584 Clouston May 1999 Definitions of Managed Objects for APPN/HPR in IP NetworksThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines objects for monitoring and controlling HPR (HighPerformance Routing) network devices which have the capability tocommunicate in IP (Internet Protocol) networks. [STANDARDS-TRACK]2583 Carlson May 1999 Guidelines for Next Hop Client (NHC) DevelopersThis document provides guidelines for developers of the Next HopResolution Protocol Clients (NHC). The intent is to define theinteraction between the NHC code and the TCP/IP protocol stack of thelocal host operating system. This memo provides information for theInternet community.DeLaCruz Informational [Page 4]
RFC 2599 Summary of 2500-2599 March 20002582 Floyd Apr 1999 The NewReno Modification to TCP's Fast Recovery AlgorithmThis document describes a specific algorithm for responding to partialacknowledgments, referred to as NewReno. This memo defines anExperimental Protocol for the Internet community.2581 Allman Apr 1999 TCP Congestion ControlThis document defines TCP's four intertwined congestion controlalgorithms: slow start, congestion avoidance, fast retransmit, and fastrecovery. In addition, the document specifies how TCP should begintransmission after a relatively long idle period, as well as discussingvarious acknowledgment generation methods. [STANDARDS-TRACK]2580 McCloghrie Apr 1999 Conformance Statements for SMIv2Collections of related objects are defined in MIB modules. It may beuseful to define the acceptable lower-bounds of implementation, alongwith the actual level of implementation achieved. It is the purposeof this document to define the notation used for these purposes.[STANDARDS-TRACK]2579 McCloghrie Apr 1999 Textual Conventions for SMIv2It is the purpose of this document to define the initial set of textualconventions available to all MIB modules. [STANDARDS-TRACK]2578 McCloghrie Apr 1999 Structure of Management Information Version 2 (SMIv2)It is the purpose of this document, the Structure of ManagementInformation Version 2 (SMIv2), to define that adapted subset, and toassign a set of associated administrative values. [STANDARDS-TRACK]2577 Allman May 1999 FTP Security ConsiderationsThis document provides suggestions for system administrators and thoseimplementing FTP servers that will decrease the security problemsassociated with FTP. This memo provides information for the Internetcommunity.DeLaCruz Informational [Page 5]
RFC 2599 Summary of 2500-2599 March 20002576 Frye March 2000 Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management FrameworkThe purpose of this document is to describe coexistence betweenversion 3 of the Internet-standard Network Management Framework,(SNMPv3), version 2 of the Internet-standard Network ManagementFramework (SNMPv2), and the original Internet-standard NetworkManagement Framework (SNMPv1). [STANDARDS TRACK]2575 Wijnen Apr 1999 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)This document describes the View-based Access Control Model for use inthe SNMP architecture (RFC2571). It defines the Elements of Procedurefor controlling access to management information. This document alsoincludes a MIB for remotely managing the configuration parameters forthe View-based Access Control Model. [STANDARDS-TRACK]2574 Blumenthal Apr 1999 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)This document describes the User-based Security Model (USM) for SNMPversion 3 for use in the SNMP architecture. It defines the Elementsof Procedure for providing SNMP message level security. This documentalso includes a MIB for remotely monitoring/managing the configurationparameters for this Security Model. [STANDARDS-TRACK]2573 Levi Apr 1999 SNMP ApplicationsThis memo describes five types of SNMP applications which make use ofan SNMP engine. This memo also defines MIB modules for specifyingtargets of management operations, for notification filtering, and forproxy fowarding. [STANDARDS-TRACK]DeLaCruz Informational [Page 6]
RFC 2599 Summary of 2500-2599 March 20002572 Case May 1999 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)This document describes the Message Processing and Dispatching forSNMP messages within the SNMP architecture. It defines the proceduresfor dispatching potentially multiple versions of SNMP messages to theproper SNMP Message Processing Models, and for dispatching PDUs toSNMP applications. This document also describes one MessageProcessing Model - the SNMPv3 Message Processing Model.[STANDARDS-TRACK]2571 Harrington May 1999 An Architecture for Describing SNMP Management FrameworksThis document describes an architecture for describing SNMP ManagementFrameworks. [STANDARDS-TRACK]2570 Case Apr 1999 Introduction to Version 3 of the Internet-standard Network Management FrameworkThe purpose of this document is to provide an overview of the thirdversion of the Internet-standard Management Framework, termed the SNMPversion 3 Framework (SNMPv3). This memo provides information for theInternet community.2569 Herriot Apr 1999 Mapping between LPD and IPP ProtocolsThis document is one of a set of documents, which together describe allaspects of a new Internet Printing Protocol (IPP). One of the purposesof this document is to compare the functionality of the two protocols.Another purpose is to facilitate implementation of gateways between LPDand IPP. This memo defines an Experimental Protocol for the Internetcommunity.DeLaCruz Informational [Page 7]
RFC 2599 Summary of 2500-2599 March 20002568 Zilles Apr 1999 Rationale for the Structure of the Model and Protocol for the Internet Printing ProtocolThis document describes IPP from a high level view, defines a roadmapfor the various documents that form the suite of IPP specifications, andgives background and rationale for the IETF working group's majordecisions. This memo defines an Experimental Protocol for the Internetcommunity.2567 Wright Apr 1999 Design Goals for an Internet Printing ProtocolThis document takes a broad look at distributed printing functionality,and it enumerates real-life scenarios that help to clarify the featuresthat need to be included in a printing protocol for the Internet. Itidentifies requirements for three types of users: end users, operators,and administrators. This memo defines an Experimental Protocol for theInternet community.2566 deBry Apr 1999 Internet Printing Protocol/1.0: Model and SemanticsThis document describes a simplified model consisting of abstractobjects, their attributes, and their operations that is independent ofencoding and transport. This document also addresses security,internationalization, and directory issues. This memo defines anExperimental Protocol for the Internet community.2565 Herriot Apr 1999 Internet Printing Protocol/1.0: Encoding and TransportThis document defines the rules for encoding IPP operations and IPPattributes into a new Internet mime media type called "application/ipp".This document also defines the rules for transporting over HTTP amessage body whose Content-Type is "application/ipp". This documentdefines an Experimental protocol for the Internet community.DeLaCruz Informational [Page 8]
RFC 2599 Summary of 2500-2599 March 20002564 Kalbfleisch May 1999 Application Management MIBThis memo defines a standards track portion of the ManagementInformation Base (MIB) for use with network management protocols in theInternet Community. In particular, it defines objects used for themanagement of applications. [STANDARDS-TRACK]2563 Troll May 1999 DHCP Option to Disable Stateless Auto-Configuration in IPv4 ClientsThis document describes a mechanism by which DHCP servers are able totell clients that they do not have an IP address to offer, and that theclient should not generate an IP address it's own. [STANDARDS-TRACK]2562 White Apr 1999 Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)This memo defines the protocol and the Management Information Base (MIB)for performing response time data collection on TN3270 and TN3270Esessions by a TN3270E server. [STANDARDS-TRACK]2561 White Apr 1999 Base Definitions of Managed Objects for TN3270E Using SMIv2This memo defines a Management Information Base (MIB) for configuringand managing TN3270E servers. The MIB defined by this memo providesgeneric support for both host and gateway TN3270E serverimplementations. [STANDARDS-TRACK]2560 Myers Jun 1999 X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSPThis document specifies a protocol useful in determining the currentstatus of a digital certificate without requiring CRLs. [STANDARDS-TRACK]DeLaCruz Informational [Page 9]
RFC 2599 Summary of 2500-2599 March 20002559 Boeyen Apr 1999 Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2Specifically, this document addresses requirements to provide access toPublic Key Infrastructure (PKI) repositories for the purposes ofretrieving PKI information and managing that same information.[STANDARDS-TRACK]2558 Tesink Mar 1999 Definitions of Managed Objects for the SONET/SDH Interface TypeThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets. Inparticular, it defines objects for managing Synchronous OpticalNetwork/Synchronous Digital Hierarchy (SONET/SDH) interfaces. Thisdocument is a companion to the documents that define Managed Objects forthe DS1/E1/DS2/E2 and DS3/E3 Interface Types. [STANDARDS-TRACK]2557 Palme Mar 1999 MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)This document a) defines the use of a MIME multipart/related structureto aggregate a text/html root resource and the subsidiary resources itreferences, and b) specifies a MIME content-header (Content-Location)that allow URIs in a multipart/related text/html root body part toreference subsidiary resources in other body parts of the samemultipart/related structure. [STANDARDS-TRACK]2556 Bradner Mar 1999 OSI connectionless transport services on top of UDP Applicability Statement for Historic StatusRFC 1240, "OSI connectionless transport services on top of UDP", waspublished as a Proposed Standard in June 1991 but at this time there donot seem to be any implementations which followRFC 1240. In additionthere is a growing concern over using UDP-based transport protocols inenvironments where congestion is a possibility This memo providesinformation for the Internet community.DeLaCruz Informational [Page 10]
RFC 2599 Summary of 2500-2599 March 20002555 RFC Editor Apr 1999 30 Years of RFCsThe rest of this document contains a brief recollection from the presentRFC Editor Joyce K. Reynolds, followed by recollections from threepioneers: Steve Crocker who wroteRFC 1, Vint Cerf whose long-rangevision continues to guide us, and Jake Feinler who played a key role inthe middle years of the RFC series. This memo provides information forthe Internet community.2554 Myers Mar 1999 SMTP Service ExtensionThis document defines an SMTP service extension [ESMTP] whereby an SMTPclient may indicate an authentication mechanism to the server, performan authentication protocol exchange, and optionally negotiate a securitylayer for subsequent protocol interactions. [STANDARDS-TRACK]2553 Gilligan Mar 1999 Basic Socket Interface Extensions for IPv6TCP/IP applications written using the sockets API have in the pastenjoyed a high degree of portability and we would like the sameportability with IPv6 applications. But changes are required to thesockets API to support IPv6 and this memo describes these changes.These include a new socket address structure to carry IPv6 addresses,new address conversion functions, and some new socket options. Thismemo provides information for the Internet community.2552 Blinov Apr 1999 Architecture for Information Brokerage in the ACTS Project GAIAThis memo introduces a domain and supplier independent genericarchitecture for information brokerage, designed as part of the ACTSproject GAIA (Generic Architecture for Information Availability). Thismemo provides information for the Internet community.DeLaCruz Informational [Page 11]
RFC 2599 Summary of 2500-2599 March 20002551 Bradner 1 Apr 1999 The Roman Standards Process -- Revision IIIThis memo documents the process used by the Roman community for thestandardization of protocols and procedures. It defines the stages inthe standardization process, the requirements for moving a documentbetween stages and the types of documents used during this process. Italso addresses the intellectual property rights and copyright issuesassociated with the standards process.2550 Glassman 1 Apr 1999 Y10K and BeyondThis specification provides a solution to the "Y10K" problem which hasalso been called the "YAK" problem (hex) and the "YXK" problem (Romannumerals). This memo provides information for the Internet community.2549 Waitzman 1 Apr 1999 IP over Avian Carriers with Quality of ServiceThis memo amendsRFC 1149, "A Standard for the Transmission of IPDatagrams on Avian Carriers", with Quality of Service information. Thisis an experimental, not recommended standard. This memo defines anExperimental Protocol for the Internet community.2548 Zorn Mar 1999 Microsoft Vendor-specific RADIUS AttributesThis document describes the set of Microsoft vendor-specific RADIUSattributes. This memo provides information for the Internet community.2547 Rosen Mar 1999 BGP/MPLS VPNsThis document describes a method by which a Service Provider with an IPbackbone may provide VPNs (Virtual Private Networks) for its customers.This memo provides information for the Internet community.DeLaCruz Informational [Page 12]
RFC 2599 Summary of 2500-2599 March 20002546 Durand Mar 1999 6Bone Routing PracticeThis memo identifies guidelines on how 6Bone sites might operate, sothat the 6Bone can remain a quality experimentation environment and toavoid pathological situations that have been encountered in the past.It defines the 'best current practice' acceptable in the 6Bone for theconfiguration of both Interior Gateway Protocols and Exterior GatewayProtocols. This memo provides information for the Internet community.2545 Marques Mar 1999 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain RoutingBGP-4 Multiprotocol Extensions (BGP-MP) defines the format of two BGPattributes (MP_REACH_NLRI and MP_UNREACH_NLRI) that can be used toannounce and withdraw the announcement of reachability information.This document defines how compliant systems should make use of thoseattributes for the purpose of conveying IPv6 routing information.[STANDARDS-TRACK]2544 Bradner Mar 1999 Benchmarking Methodology for Network Interconnect DevicesThis document is a republication ofRFC 1944 correcting the values forthe IP addresses which were assigned to be used as the default addressesfor networking test equipment. This memo provides information for theInternet community.2543 Handley Mar 1999 SIP: Session Initiation ProtocolThe Session Initiation Protocol (SIP) is an application-layer control(signaling) protocol for creating, modifying and terminating sessionswith one or more participants. [STANDARDS-TRACK]2542 Masinter Mar 1999 Terminology and Goals for Internet FaxThis document defines a number of terms useful for the discussion ofInternet Fax. In addition, it describes the goals of the Internet Faxworking group and establishes a baseline of desired functionalityagainst which protocols for Internet Fax can be judged. This memoprovides information for the Internet community.DeLaCruz Informational [Page 13]
RFC 2599 Summary of 2500-2599 March 20002541 Eastlake Mar 1999 DNS Security Operational ConsiderationThis document discusses these operational aspects for keys andsignatures used in connection with the KEY and SIG DNS resource records.This memo provides information for the Internet community.2540 Eastlake Mar 1999 Detached Domain Name System (DNS) InformationA standard format is defined for representing detached DNS information.This is anticipated to be of use for storing information retrieved fromthe Domain Name System (DNS), including security information, inarchival contexts or contexts not connected to the Internet. This memodefines an Experimental Protocol for the Internet community.2539 Eastlake Mar 1999 Storage of Diffie-Hellman Keys in the Domain Name System (DNS)A standard method for storing Diffie-Hellman keys in the Domain NameSystem is described which utilizes DNS KEY resource records.[STANDARDS-TRACK]2538 Eastlake Mar 1999 Storing Certificates in the Domain Name System (DNS)Cryptographic public key are frequently published and their authenticitydemonstrated by certificates. A CERT resource record (RR) is defined sothat such certificates and related certificate revocation lists can bestored in the Domain Name System (DNS). [STANDARDS-TRACK]2537 Eastlake Mar 1999 RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)A standard method for storing RSA keys and and RSA/MD5 based signaturesin the Domain Name System is described which utilizes DNS KEY and SIGresource records. [STANDARDS-TRACK]DeLaCruz Informational [Page 14]
RFC 2599 Summary of 2500-2599 March 20002536 Eastlake Mar 1999 DSA KEYs and SIGs in the Domain Name System (DNS)A standard method for storing US Government Digital Signature Algorithmkeys and signatures in the Domain Name System is described whichutilizes DNS KEY and SIG resource records. [STANDARDS-TRACK]2535 Eastlake Mar 1999 Domain Name System Security ExtensionsThis document incorporates feedback onRFC 2065 from early implementersand potential users. [STANDARDS-TRACK]2534 Masinter Mar 1999 Media Features for Display, Print, and FaxThis specification defines some common media features for describingimage resolution, size, color, and image representation methods that arecommon to web browsing, printing, and facsimile applications.[STANDARDS-TRACK]2533 Klyne Mar 1999 A Syntax for Describing Media Feature SetsThis document introduces and describes a syntax that can be used todefine feature sets which are formed from combinations and relationsinvolving individual media features. [STANDARDS-TRACK]2532 Masinter Mar 1999 Extended Facsimile Using Internet MailThis document describes extensions to "Simple Mode of Facsimile UsingInternet Mail", and describes additional features, includingtransmission of enhanced document characteristics (higher resolution,color) and confirmation of delivery and processing. [STANDARDS-TRACK]2531 Klyne Mar 1999 Content Feature Schema for Internet FaxThis document defines a content feature schema that is a profile of themedia feature registration mechanisms for use in performing capabilityidentification between extended Internet fax systems. [STANDARDS-TRACK]DeLaCruz Informational [Page 15]
RFC 2599 Summary of 2500-2599 March 20002530 Wing Mar 1999 Indicating Supported Media Features Using Extensions to DSN and MDNThis memo describes a format for generating Message DispositionNotifications and Delivery Status Notifications which contain suchinformation. [STANDARDS-TRACK]2529 Carpenter Mar 1999 Transmission of IPv6 over IPv4 Domains without Explicit TunnelsThis memo specifies the frame format for transmission of IPv6 (IPV6)packets and the method of forming IPv6 link-local addresses over IPv4domains. It also specifies the content of the Source/Target Link-layerAddress option used in the Router Solicitation, Router Advertisement,Neighbor Solicitation, and Neighbor Advertisement and Redirect messages,when those messages are transmitted on an IPv4 multicast network.[STANDARDS-TRACK]2528 Housley Mar 1999 Internet X.509 Public Key InfrastructureThis specification contains guidance on the use of the Internet PublicKey Infrastructure certificates to convey Key Exchange Algorithm (KEA)keys. This memo provides information for the Internet community.2527 Chokhani Mar 1999 Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkThis document presents a framework to assist the writers of certificatepolicies or certification practice statements for certificationauthorities and public key infrastructures. In particular, theframework provides a comprehensive list of topics that potentially (atthe writer's discretion) need to be covered in a certificate policydefinition or a certification practice statement. This memo providesinformation for the Internet community.DeLaCruz Informational [Page 16]
RFC 2599 Summary of 2500-2599 March 20002526 Johnson Mar 1999 Reserved IPv6 Subnet Anycast AddressesThis document defines a set of reserved anycast addresses within eachsubnet prefix, and lists the initial allocation of these reserved subnetanycast addresses. [STANDARDS-TRACK]2525 Paxson Mar 1999 Known TCP Implementation ProblemsThis memo catalogs a number of known TCP implementation problems. Thismemo provides information for the Internet community.2524 Banan Feb 1999 Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1.3This specification narrowly focuses on submission and delivery of shortmail messages with a clear emphasis on efficiency. This memo providesinformation for the Internet community.2523 Karn Mar 1999 Photuris: Extended Schemes and AttributesPhoturis is a session-key management protocol. Extensible Exchange-Schemes are provided to enable future implementation changes withoutaffecting the basic protocol. This document defines an ExperimentalProtocol for the Internet community.2522 Karn Mar 1999 Photuris: Session-Key Management ProtocolThis document defines the basic protocol mechanisms. This documentdefines an Experimental Protocol for the Internet community.2521 Karn Mar 1999 ICMP Security Failures MessagesThis document specifies ICMP messages for indicating failures when usingIP Security Protocols (AH and ESP). This document defines anExperimental Protocol for the Internet community.DeLaCruz Informational [Page 17]
RFC 2599 Summary of 2500-2599 March 20002520 Luciani Feb 1999 NHRP with Mobile NHCsis document describes an extension to NHRP which would allow Mobile NHCsto perform a registration with and attach to an NHS in their home LIS inan authenticated manner. This memo defines an Experimental Protocol forthe Internet community.2519 Chen Feb 1999 A Framework for Inter-Domain Route AggregationThis document presents a framework for inter-domain route aggregationand shows an example router configuration which 'implements' thisframework. This memo provides information for the Internet community2518 Goland Feb 1999 HTTP Extensions for Distributed Authoring -- WEBDAThis document specifies a set of methods, headers, and content-typesancillary to HTTP/1.1 for the management of resource properties,creation and management of resource collections, namespace manipulation,and resource locking (collision avoidance). [STANDARDS-TRACK]2517 Moats Feb 1999 Building Directories from DNS: Experiences from WWWSeekerThis memo discusses lessons that were learned during InterNIC Directoryand Database Services' development and operation of WWWSeeker, anapplication that finds a web site given information about the name andlocation of an organization. This memo provides information for theInternet community.2516 Mamakos Feb 1999 A Method for Transmitting PPP Over Ethernet (PPPoE)This document describes how to build PPP sessions and encapsulate PPPpackets over Ethernet. This memo provides information for the Internetcommunity.DeLaCruz Informational [Page 18]
RFC 2599 Summary of 2500-2599 March 20002515 Tesink Feb 1999 Definitions of Managed Objects for ATM ManagementThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes objects used for managing ATM-based interfaces,devices, networks and services. [STANDARDS-TRACK]2514 Noto Feb 1999 Definitions of Textual Conventions and OBJECT- IDENTITIES for ATM MEanagementThis memo describes Textual Conventions and OBJECT-IDENTITIES used formanaging ATM-based interfaces, devices, networks and services.[STANDARDS-TRACK]2513 McCloghrie Feb 1999 Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection- Oriented NetworksThis 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 controlling thecollection and storage of accounting information for connection-orientednetworks such as ATM. [STANDARDS-TRACK]2512 McCloghrie Feb 1999 Accounting Information for ATM NetworksThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Thismemo defines a set of ATM-specific accounting information which can becollected for connections on ATM networks. [STANDARDS-TRACK]2511 Myers Mar 1999 Internet X.509 Certificate Request Message FormatThis document describes the Certificate Request Message Format (CRMF).[STANDARDS-TRACK]DeLaCruz Informational [Page 19]
RFC 2599 Summary of 2500-2599 March 20002510 Adams Mar 1999 Internet X.509 Public Key Infrastructure Certificate Management ProtocolsThis document describes the Internet X.509 Public Key Infrastructure(PKI) Certificate Management Protocols. [STANDARDS-TRACK]2509 Engan Feb 1999 IP Header Compression over PPPThis document describes an option for negotiating the use of headercompression on IP datagrams transmitted over the Point-to-PointProtocol. It defines extensions to the PPP Control Protocols for IPv4and IPv6. [STANDARDS-TRACK]2508 Casner Feb 1999 Compressing IP/UDP/RT Headers for Low-Speed Serial LinksThis document describes a method for compressing the headers ofIP/UDP/RTP datagrams to reduce overhead on low-speed serial links.[STANDARDS-TRACK]2507 Degermark Feb 1999 IP Header CompressionThis document describes how to compress multiple IP headers and TCP andUDP headers per hop over point to point links. [STANDARDS-TRACK]2506 Holtman Mar 1999 Media Feature Tag Registration ProcedureThis document defines a registration procedure which uses the InternetAssigned Numbers Authority (IANA) as a central registry for the mediafeature vocabulary. This document specifies an Internet Best CurrentPractices for the Internet Community, and requests discussion andsuggestions for improvements.2505 Lindberg Feb 1999 Anti-Spam Recommendations for SMTP MTAsThis memo gives a number of implementation recommendations for SMTP,MTAs (Mail Transfer Agents, e.g. sendmail,) to make them more capable ofreducing the impact of spam. This document specifies an Internet BestCurrent Practices for the Internet Community, and requests discussionand suggestions for improvements.DeLaCruz Informational [Page 20]
RFC 2599 Summary of 2500-2599 March 20002504 Guttman Feb 1999 Users' Security HandbookThe Users' Security Handbook is the companion to the Site SecurityHandbook (SSH). It is intended to provide users with the informationthey need to help keep their networks and systems secure. This memoprovides information for the Internet community.2503 Moulton Feb 1999 MIME Types for Use with the ISO ILL ProtocolThis memorandum describes a set of MIME types for use with the ISOInterlibrary Loan Protocol (ISO 10160/10161). This memo providesinformation for the Internet community.2502 Pullen Feb 1999 Limitations of Internet Protocol Suite for Distributed Simulation the Large Multicast EnvironmentThis memo defines services that LSMA has found to be required, andaspects of the Internet protocols that LSMA has found to need furtherdevelopment in order to meet these requirements. This memo providesinformation for the Internet community.2501 Corson Jan 1999 Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation ConsiderationsThis memo first describes the characteristics of Mobile Ad hoc Networks(MANETs), and their idiosyncrasies with respect to traditional,hardwired packet networks. It then discusses the effect thesedifferences have on the design and evaluation of network controlprotocols with an emphasis on routing performance evaluationconsiderations. This memo provides information for the Internetcommunity.2500 IETF Jun 1999 Internet Official Protocol StandardsThis memo summarizes the status of Internet protocols andspecifications. [STANDARDS-TRACK]DeLaCruz Informational [Page 21]
RFC 2599 Summary of 2500-2599 March 2000Security Considerations This memo does not affect the technical security of the Internet, but it does cite some security specifications.Author's Address Alison De La Cruz University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: delacruz@isi.eduDeLaCruz Informational [Page 22]
RFC 2599 Summary of 2500-2599 March 2000Full Copyright Statement Copyright (C) The Internet Society (2000). 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.DeLaCruz Informational [Page 23]
[8]ページ先頭