📄 rfc2299.txt
字号:
RFC 2299 Summary of 2200-2299 January 19992251 Wahl Dec 1997 Lightweight Directory Access Protocol (v3)The protocol described in this document is designed to provide access todirectories supporting the X.500 models, while not incurring theresource requirements of the X.500 Directory Access Protocol (DAP).[STANDARDS-TRACK]2250 Hoffman Jan 1998 RTP Payload Format for MPEG1/MPEG2 VideoThis memo describes a packetization scheme for MPEG video and audiostreams. [STANDARDS-TRACK]2249 Freed Jan 1998 Mail Monitoring MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.Specifically, this memo extends the basic Network Services MonitoringMIB [8] to allow monitoring of Message Transfer Agents (MTAs). It mayalso be used to monitor MTA components within gateways. [STANDARDS-TRACK]2248 Freed Jan 1998 Network Services Monitoring MIBThis MIB may be used on its own for any application, and for most simpleapplications this will suffice. This MIB is also designed to serve as abuilding block which can be used in conjunction with application-specific monitoring and management. [STANDARDS-TRACK]2247 Kille Jan 1998 Using Domains in LDAP/X.500 Distinguished NamesThis document defines an algorithm by which a name registered with theInternet Domain Name Service [2] can be represented as an LDAPdistinguished name. [STANDARDS-TRACK]Ramos Informational [Page 13]RFC 2299 Summary of 2200-2299 January 19992246 Dierks Jan 1999 The TLS Protocol Version 1.0This document specifies Version 1.0 of the Transport Layer Security(TLS) protocol. The TLS protocol provides communications privacy overthe Internet. The protocol allows client/server applications tocommunicate in a way that is designed to prevent eavesdropping,tampering, or message forgery. [STANDARDS-TRACK]2245 Newman Nov 1997 Anonymous SASL MechanismAs plaintext login commands are not permitted in new IETF protocols, anew way to provide anonymous login is needed within the context of theSASL [SASL] framework. [STANDARDS-TRACK]2244 Newman Nov 1997 ACAP -- Application Configuration Access ProtocolThe Application Configuration Access Protocol (ACAP) is designed tosupport remote storage and access of program option, configuration andpreference information. [STANDARDS-TRACK]2243 Metz Nov 1997 OTP Extended ResponsesThis document provides a specification for a type of response to an OTP[RFC 1938] challenge that carries explicit indication of the response'sencoding. This document also provides a specification for a responsethat allows an OTP generator to request that a server re-initialize asequence and change parameters such as the secret pass phrase.[STANDARDS-TRACK]2242 Droms Nov 1997 NetWare/IP Domain Name and InformationThis document defines options that carry NetWare/IP domain name andNetWare/IP sub-options to DHCP clients. [STANDARDS-TRACK]Ramos Informational [Page 14]RFC 2299 Summary of 2200-2299 January 19992241 Provan Nov 1997 DHCP Options for Novell Directory ServicesThis document defines three new DHCP options for deliveringconfiguration information to clients of the Novell Directory Services.This document defines three new DHCP options for deliveringconfiguration information to clients of the Novell Directory Services.[STANDARDS-TRACK]2240 Vaughan Nov 1997 A Legal Basis for Domain Name AllocationThe purpose of this memo is to focus discussion on the particularproblems with the exhaustion of the top level domain space in theInternet and the possible conflicts that can occur when multipleorganisations are vying for the same name. This memo providesinformation for the Internet community. It does not specify an Internetstandard of any kind.2239 de Graaf Nov 1997 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2This memo defines an portion of the Management Information Base (MIB)for use with network management protocols in the Internet community. Inparticular, it defines objects for managing 10 and 100 Mb/second MediumAttachment Units (MAUs) based on IEEE Std 802.3 Section 30, "10 & 100Mb/s Management," October 26, 1995. [STANDARDS-TRACK]2238 Clouston Nov 1997 Definitions of Managed Objects for HPR using SMIv2This 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 networkdevices with HPR (High Performance Routing) capabilities. This memoidentifies managed objects for the HPR protocol. [STANDARDS-TRACK]2237 Tamaru Nov 1997 Japanese Character Encoding for Internet MessagesThis memo defines an encoding scheme for the Japanese Characters,describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822],and network news [RFC 1036]. Also this memo provides a listing of theRamos Informational [Page 15]RFC 2299 Summary of 2200-2299 January 1999Japanese Character Set that can be used in this encoding scheme. Thismemo provides information for the Internet community. It does notspecify an Internet standard of any kind.2236 Fenner Nov 1997 Internet Group Management Protocol, Version 2This memo documents IGMPv2, used by IP hosts to report their multicastgroup memberships to routers. It updates STD 5, RFC 1112. [STANDARDS-TRACK]2235 Zakon Nov 1997 Hobbes' Internet TimelineThis document presents a history of the Internet in timeline fashion,highlighting some of the key events and technologies which helped shapethe Internet as we know it today. A growth summary of the Internet andsome associated technologies is also included. This memo providesinformation for the Internet community. It does not specify an Internetstandard of any kind.2234 Crocker Nov 1997 Augmented BNF for Syntax Specifications: ABNFIn the early days of the Arpanet, each specification contained its owndefinition of ABNF. This included the email specifications, RFC733 andthen RFC822 which have come to be the common citations for definingABNF. The current document separates out that definition, to permitselective reference. Predictably, it also provides some modificationsand enhancements. [STANDARDS-TRACK]2233 McCloghrie Nov 1997 The Interfaces Group MIB using SMIv2This 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 managing NetworkInterfaces. [STANDARDS-TRACK]Ramos Informational [Page 16]RFC 2299 Summary of 2200-2299 January 19992232 Clouston Nov 1997 Definitions of Managed Objects for DLUR using SMIv2This 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 networkdevices with DLUR (Dependent LU Requester) capabilities. This memoidentifies managed objects for the DLUR protocol. [STANDARDS-TRACK]2231 Freed Nov 1997 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and ContinuationsThis memo defines extensions to the RFC 2045 media type and RFC 2183disposition parameter value mechanisms. This memo also defines anextension to the encoded words defined in RFC 2047 to allow thespecification of the language to be used for display as well as thecharacter set. [STANDARDS-TRACK]2230 Atkinson Nov 1997 Key Exchange Delegation Record for the DNSThis note describes a mechanism whereby authorisation for one node toact as key exchanger for a second node is delegated and made availablevia the Secure DNS. This mechanism is intended to be used only with theSecure DNS. This memo provides information for the Internet community.It does not specify an Internet standard of any kind.2229 Faith Oct 1997 A Dictionary Server ProtocolThe Dictionary Server Protocol (DICT) is a TCP transaction basedquery/response protocol that allows a client to access dictionarydefinitions from a set of natural language dictionary databases. Thismemo provides information for the Internet community. It does notspecify an Internet standard of any kind.2228 Horowitz Oct 1997 FTP Security ExtensionsThis document defines extensions to the FTP specification STD 9, RFC959, "FILE TRANSFER PROTOCOL (FTP)" (October 1985). [STANDARDS-TRACK]Ramos Informational [Page 17]RFC 2299 Summary of 2200-2299 January 19992227 Mogul Oct 1997 Simple Hit-Metering and Usage-Limiting for HTTPThis document proposes a simple extension to HTTP, using a new "Meter"header. [STANDARDS-TRACK]2226 Smith Oct 1997 IP Broadcast over ATM NetworksThis memo describes how the IP multicast service being developed by theIP over ATM working group may be used to support IP broadcasttransmission. [STANDARDS-TRACK]2225 Laubach Apr 1998 Classical IP and ARP over ATMThis memo defines an initial application of classical IP and ARP in anAsynchronous Transfer Mode (ATM) network environment configured as aLogical IP Subnetwork (LIS). [STANDARDS-TRACK]2224 Callaghan Oct 1997 NFS URL SchemeA new URL scheme, 'nfs' is defined. It is used to refer to files anddirectories on NFS servers using the general URL syntax defined in RFC1738, "Uniform Resource Locators (URL)". This memo provides informationfor the Internet community. It does not specify an Internet standard ofany kind.2223 Postel Oct 1997 Instructions to RFC AuthorsThis Request for Comments (RFC) provides information about thepreparation of RFCs, and certain policies relating to the publication ofRFCs. This memo provides information for the Internet community. Thismemo does not specify an Internet standard of any kind.2222 Myers Oct 1997 Simple Authentication and Security Layer (SASL)This document describes a method for adding authentication support toconnection-based protocols. [STANDARDS-TRACK]Ramos Informational [Page 18]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -