📄 rfc2899.txt
字号:
use with network management protocols in the Internet community. Inparticular, it describes managed objects which provide an invertedmapping of the interface stack table used for managing networkinterfaces. [STANDARDS TRACK]2863 McCloghrie Jun 2000 The Interfaces Group MIBThis memo discusses the 'interfaces' group of MIB-II, especially theexperience gained from the definition of numerous media-specific MIBmodules for use in conjunction with the 'interfaces' group for managingvarious sub-layers beneath the internetwork-layer. It specifiesclarifications to, and extensions of, the architectural issues withinthe MIB-II model of the 'interfaces' group. [STANDARDS TRACK]2862 Civanlar Jun 2000 RTP Payload Format for Real-Time PointersThis document describes an RTP payload format for transporting thecoordinates of a dynamic pointer that may be used during a presentation.[STANDARDS TRACK]2861 Handley Jun 2000 TCP Congestion Window ValidationThis document describes a simple modification to TCP's congestioncontrol algorithms to decay the congestion window cwnd after thetransition from a sufficiently-long application-limited period, whileusing the slow-start threshold ssthresh to save information about theprevious value of the congestion window. This memo defines anExperimental Protocol for the Internet community.Ginoza Informational [Page 8]RFC 2899 Summary of 2800-2899 May 20012860 Carpenter Jun 2000 Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers AuthorityThis document places on record the text of the Memorandum ofUnderstanding concerning the technical work of the IANA that was signedon March 1, 2000 between the IETF and ICANN, and ratified by the ICANNBoard on March 10, 2000. This memo provides information for theInternet community.2859 Fang Jun 2000 A Time Sliding Window Three This memo defines a TimeThis memo defines a Time Sliding Window Three Colour Marker (TSWTCM),which can be used as a component in a Diff-Serv traffic conditioner.This memo defines an Experimental Protocol for the Internet community.2858 Bates Jun 2000 Multiprotocol Extensions for BGP-4This document defines extensions to BGP-4 to enable it to carry routinginformation for multiple Network Layer protocols (e.g., IPv6, IPX,etc...). [STANDARDS TRACK]2857 Keromytis Jun 2000 The Use of HMAC-RIPEMD-160-96 within ESP and AHThis memo describes the use of the HMAC algorithm in conjunction withthe RIPEMD-160 algorithm as an authentication mechanism within therevised IPSEC Encapsulating Security Payload (ESP) and the revised IPSECAuthentication Header (AH). [STANDARDS TRACK]2856 Bierman Jun 2000 Textual Conventions for Additional High Capacity Data TypesThis memo specifies new textual conventions for additional high capacitydata types, intended for SNMP implementations which already support theCounter64 data type. [STANDARDS TRACK]Ginoza Informational [Page 9]RFC 2899 Summary of 2800-2899 May 20012855 Fujisawa Jun 2000 DHCP for IEEE 1394This memo describes specific usage of some fields of DHCP (Dynamic HostConfiguration Protocol) messages. IEEE Std 1394-1995 is a standard fora High Performance Serial Bus. Since 1394 uses a different link-layeraddressing method than conventional IEEE802/Ethernet, the usage of somefields must be clarified to achieve interoperability. [STANDARDS TRACK]2854 Connolly Jun 2000 The 'text/html' Media TypeThis document summarizes the history of HTML development, and definesthe "text/html" MIME type by pointing to the relevant W3Crecommendations. This memo provides information for the Internetcommunity.2853 Kabat Jun 2000 Generic Security Service API Version 2 : Java BindingsThis document specifies the Java bindings for GSS-API (Generic SecurityService Application Program Interface) which is described at a languageindependent conceptual level in RFC 2743. [STANDARDS TRACK]2852 Newman Jun 2000 Deliver By SMTP Service ExtensionThis memo defines a mechanism whereby a SMTP client can request, whentransmitting a message to a SMTP server, that the server deliver themessage within a prescribed period of time. [STANDARDS TRACK]2851 Daniele Jun 2000 Textual Conventions for Internet Network AddressesThis MIB module defines textual conventions to represent commonly usedInternet network layer addressing information. [STANDARDS TRACK]2850 IAB May 2000 Charter of the Internet Architecture Board (IAB)This memo documents the composition, selection, roles, and organizationof the Internet Architecture Board. It replaces RFC 1601. Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.Ginoza Informational [Page 10]RFC 2899 Summary of 2800-2899 May 20012849 Good Jun 2000 The LDAP Data Interchange Format (LDIF) - Technical SpecificationThis document describes a file format suitable for describing directoryinformation or modifications made to directory information. [STANDARDSTRACK]2848 Petrack Jun 2000 The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call ServicesThis document contains the specification of the PINT Service Protocol1.0, which defines a protocol for invoking certain telephone servicesfrom an IP network. [STANDARDS TRACK]2847 Eisler Jun 2000 LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKMThis memorandum describes a method whereby one can use GSS-API (GenericSecurity Service Application Program Interface) to supply a securechannel between a client and server, authenticating the client with apassword, and a server with a public key certificate. [STANDARDS TRACK]2846 Allocchio Jun 2000 GSTN Address Element Extensions in E-mail ServicesThis memo defines a full syntax for a specific application in whichthere is a need to represent GSTN (Global Switched Telephone Network)addressing and Internet addressing. [STANDARDS TRACK]2845 Vixie May 2000 Secret Key Transaction Authentication for DNS (TSIG)This protocol allows for transaction level authentication using sharedsecrets and one way hashing. It can be used to authenticate dynamicupdates as coming from an approved client, or to authenticate responsesas coming from an approved recursive name server. [STANDARDS TRACK]Ginoza Informational [Page 11]RFC 2899 Summary of 2800-2899 May 20012844 Przygienda May 2000 OSPF over ATM and Proxy-PARThis memo specifies, for OSPF implementors and users, mechanismsdescribing how the protocol operates in ATM networks over PVC (PermanentVirtual Connections) and SVC (Switched Virtual Circuit) meshes with thepresence of Proxy-PAR (PNNI Augmented Routing). This memo defines anExperimental Protocol for the Internet community.2843 Droz May 2000 Proxy-PARThe intention of this document is to provide general information aboutProxy-PAR (PNNI Augmented Routing). [STANDARDS TRACK]2842 Chandra May 2000 Capabilities Advertisement with BGP-4This document defines new Optional Parameter, called Capabilities, thatis expected to facilitate introduction of new capabilities in BGP byproviding graceful capability advertisement without requiring that BGPpeering be terminated. [STANDARDS TRACK]2841 Metzger Nov 2000 IP Authentication using Keyed SHA1 with Interleaved Padding (IP-MAC)This document describes the use of keyed SHA1 (Secure Hash Algorithm)with the IP Authentication Header. This memo defines a HistoricDocument for the Internet community.2840 Altman May 2000 TELNET KERMIT OPTIONThis document describes an extension to the Telnet protocol to allow thenegotiation, coordination, and use of the Kermit file transfer andmanagement protocol over an existing Telnet protocol connection. Thismemo provides information for the Internet community.2839 da Cruz May 2000 Internet Kermit ServiceThis document describes a new file transfer service for the Internetbased on Telnet Protocol for option negotiation and Kermit Protocol forfile transfer and management. This memo provides information for theInternet community.Ginoza Informational [Page 12]RFC 2899 Summary of 2800-2899 May 20012838 Zigmond May 2000 Uniform Resource Identifiers for Television BroadcastsThis document describes a widely-implemented URI scheme, as World-WideWeb browsers are starting to appear on a variety of consumer electronicdevices, such as television sets and television set-top boxes, which arecapable of receiving television programming from either terrestrialbroadcast, satellite broadcast, or cable. In this context there is aneed to reference television broadcasts using the URI format describedin RFC 2396. This memo provides information for the Internet community.2837 Teow May 2000 Definitions of Managed Objects for the Fabric Element in Fibre Channel StandardThis memo defines an extension to the Management Information Base (MIB)for use with network management protocols in TCP/IP-based internets. Inparticular, it defines the objects for managing the operations of theFabric Element portion of the Fibre Channel Standards. [STANDARDSTRACK]2836 Brim May 2000 Per Hop Behavior Identification CodesThis document defines a binary encoding to uniquely identify PHBs (PerHop Behaviors) and/or sets of PHBs in protocol messages. [STANDARDSTRACK]2835 Pittet May 2000 IP and ARP over HIPPI-6400 (GSN)This document further specifies a method for resolving IP addresses toHIPPI-6400 (High-Performance Parallel Interface) hardware addresses(HARP) and for emulating IP broadcast in a logical IP subnet (LIS) as adirect extension of HARP. Furthermore, it is the goal of this memo todefine a IP and HARP that will allow interoperability for HIPPI-800 andHIPPI-6400 equipment both broadcast and non-broadcast capable networks.[STANDARDS TRACK]Ginoza Informational [Page 13]RFC 2899 Summary of 2800-2899 May 20012834 Pittet May 2000 ARP and IP Broadcast over HIPPI-800This document specifies a method for resolving IP addresses to ANSIHigh-Performance Parallel Interface (HIPPI) hardware addresses and foremulating IP broadcast in a logical IP subnet (LIS) as a directextension of HARP (hardware addresses). This memo defines a HARP thatwill interoperate between HIPPI-800 and HIPPI-6400 (also known asGigabyte System Network, GSN). This document (when combined with RFC2067 "IP over HIPPI") obsoletes RFC 1374. [STANDARDS TRACK]2833 Schulzrinne May 2000 RTP Payload for DTMF Digits, Telephony Tones and Telephony SignalsThis memo describes how to carry dual-tone multifrequency (DTMF)signaling, other tone signals and telephony events in RTP packets.[STANDARDS TRACK]2832 Hollenbeck May 2000 NSI Registry Registrar Protocol (RRP) Version 1.1.0This document describes a protocol for the registration and managementof second level domain names and associated name servers in both genericTop Level Domains (gTLDs) and country code Top Level Domains (ccTLDs).This memo provides information for the Internet community.2831 Leach May 2000 Using Digest Authentication as a SASL MechanismThis specification defines how HTTP Digest Authentication can be used asa SASL mechanism for any protocol that has a SASL (Simple Authenticationand Security Layer) profile. [STANDARDS TRACK]2830 Hodges May 2000 Lightweight Directory Access Protocol (v3): Extension for Transport Layer SecurityThis document defines the "Start Transport Layer Security (TLS)Operation" for LDAP. [STANDARDS TRACK]Ginoza Informational [Page 14]RFC 2899 Summary of 2800-2899 May 20012829 Wahl May 2000 Authentication Methods for LDAPThis document specifies particular combinations of security mechanismswhich are required and recommended in LDAP implementations. [STANDARDSTRACK]2828 Shirey May 2000 Internet Security GlossaryThis Glossary provides abbreviations, explanations, and recommendationsfor use of information system security terminology. This memo providesinformation for the Internet community.2827 Ferguson May 2000 Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingThis paper discusses a simple, effective, and straightforward method forusing ingress traffic filtering to prohibit DoS (Denial of Service)attacks which use forged IP addresses to be propagated from 'behind' anInternet Service Provider's (ISP) aggregation point. This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.2826 IAB May 2000 IAB Technical Comment on the Unique DNS RootThis document discusses the existence of a globally unique public namespace in the Internet called the DNS (Domain Name System). This namespace is a hierarchical name space derived from a single, globally
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -