Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group A. RamosRequest for Comments: 2199 ISICategory: Informational January 1998Request for Comments Summary RFC Numbers 2100-2199Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 2100 through RFCs 2199. 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 (1998). 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--- ------ ---- -----2199 Ramos Jan 98 Request for Comments SummaryThis memo.2198 Perkins Sep 97 RTP Payload for Redundant Audio DataThis document describes a payload format for use with the real-timetransport protocol (RTP), version 2, for encoding redundant audio data.[STANDARDS-TRACK]Ramos Informational [Page 1]
RFC 2199 Summary of 2100-2199 January 19982197 Freed Sep 97 SMTP Service Extension for Command PipeliningThis memo defines an extension to the SMTP service whereby a server canindicate the extent of its ability to accept multiple commands in asingle TCP send operation. [STANDARDS-TRACK]2196 Fraser Sep 97 Site Security HandbookThis handbook is a guide to developing computer security policies andprocedures for sites that have systems on the Internet. The purpose ofthis handbook is to provide practical guidance to administrators tryingto secure their information and services. The subjects covered includepolicy content and formation, a broad range of technical system andnetwork security topics, and security incident response. This memoprovides information for the Internet community. It does not specify anInternet standard of any kind.2195 Klensin Sep 97 IMAP/POP AUTHorize Extension for Simple Challenge/ResponseThis specification provides a simple challenge-response authenticationprotocol that is suitable for use with IMAP4. [STANDARDS TRACK]2194 Aboba Sep 97 Review of Roaming ImplementationsThis document reviews the design and functionality of existing roamingimplementations. Examples of cases where roaming capability might berequired include ISP "confederations" and ISP-provided corporate networkaccess support. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.2193 Gahrns Sep 97 IMAP4 Mailbox ReferralsMailbox referrals allow clients to seamlessly access mailboxes that aredistributed across several IMAP4 servers. [STANDARDS-TRACK]2192 Newman Sep 97 IMAP URL SchemeThis document defines a URL scheme for referencing objects on an IMAPserver. [STANDARDS-TRACK]Ramos Informational [Page 2]
RFC 2199 Summary of 2100-2199 January 19982191 Armitage Sep 97 VENUS - Very Extensive Non-Unicast ServiceThis document focuses exclusively on the problems associated withextending the MARS model to cover multiple clusters or clusters spanningmore than one subnet. It describes a hypothetical solution, dubbed "VeryExtensive NonUnicast Service" (VENUS), and shows how complex such aservice would be. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.2190 Zhu Sep 97 RTP Payload Format for H.263 Video StreamsThis document specifies the payload format for encapsulating an H.263bitstream in the Real-Time Transport Protocol (RTP). [STANDARDS TRACK]2189 Ballardie Sep 97 Core Based Trees (CBT version 2) Multicast RoutingThis document describes the Core Based Tree (CBT version 2) networklayer multicast routing protocol. CBT builds a shared multicastdistribution tree per group, and is suited to inter- and intra-domainmulticast routing. This memo defines an Experimental Protocol for theInternet community.2188 Banan Sep 97 AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2This document specifies the service model, the notation and protocol forEfficient Short Remote Operations (ESRO). This memo providesinformation for the Internet community. It does not specify an Internetstandard of any kind.2187 Wessels Sep 97 Application of Internet Cache Protocol (ICP), version 2This document describes the application of ICPv2 (Internet CacheProtocol version 2,RFC2186) to Web caching. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.Ramos Informational [Page 3]
RFC 2199 Summary of 2100-2199 January 19982186 Wessels Sep 97 Internet Cache Protocol (ICP), version 2This document describes version 2 of the Internet Cache Protocol (ICPv2)as currently implemented in two World-Wide Web proxy cache packages.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.2185 Callon Sep 97 Routing Aspects Of IPv6 TransitionThis document gives an overview of the routing aspects of the IPv6transition. It is based on the protocols defined in the document"Transition Mechanisms for IPv6 Hosts and Routers." Readers should befamiliar with the transition mechanisms before reading this document.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.2184 Freed Aug 97 MIME Parameter Value and Encoded Word Extensions:Character Sets, Languages, and ContinuationsThis memo defines extensions to theRFC 2045 media type andRFC 2183disposition parameter value mechanisms. [STANDARDS-TRACK]2183 Troost Aug 97 Communicating Presentation Information in Internet Messages: The Content- Disposition Header FieldThis memo provides a mechanism whereby messages conforming to the MIMEspecifications [RFC 2045,RFC 2046,RFC 2047,RFC 2048,RFC 2049] canconvey presentational information. It specifies the "Content-Disposition" header field, which is optional and valid for any MIMEentity ("message" or "body part"). [STANDARDS-TRACK]2182 Elz Jul 97 Selection and Operation of Secondary DNS ServersThis document discusses the selection of secondary servers for DNSzones.The number of servers appropriate for a zone is also discussed,and some general secondary server maintenance issues considered. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.Ramos Informational [Page 4]
RFC 2199 Summary of 2100-2199 January 19982181 Elz Jul 97 Clarifications to the DNS SpecificationThis document considers some areas that have been identified as problemswith the specification of the Domain Name System, and proposes remediesfor the defects identified. [STANDARDS TRACK]2180 Gahrns Jul 97 IMAP4 Multi-Accessed Mailbox PracticeThe behavior described in this document reflects the practice of someexisting servers or behavior that the consensus of the IMAP mailing listhas deemed to be reasonable. The behavior described within thisdocument is believed to be [RFC-2060] compliant. However, this documentis not meant to define IMAP4 compliance, nor is it an exhaustive list ofvalid IMAP4 behavior. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.2179 Gwinn Jul 97 Network Security For Trade ShowsThis document is designed to assist vendors and other participants intrade shows, such as Networld+Interop, in designing effective protectionagainst network and system attacks by unauthorized individuals. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.2178 Moy Jul 97 OSPF Version 2This document considers some areas that have been identified as problemswith the specification of the Domain Name System, and proposes remediesfor the defects identified. [STANDARDS TRACK]2177 Leiba Jun 97 IMAP4 IDLE commandThis document specifies the syntax of an IDLE command, which will allowa client to tell the server that it's ready to accept such real-timeupdates. [STANDARDS-TRACK]Ramos Informational [Page 5]
RFC 2199 Summary of 2100-2199 January 19982176 Murakami Jun 97 IPv4 over MAPOS Version 1This memo documents a mechanism for supporting Version 4 of the InternetProtocol (IPv4) on Version 1 of the Multiple Access Protocol overSONET/SDH. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.2175 Murakami Jun 97 SONET/SDH with 16 Bit AddressingThis memo documents MAPOS 16, a multiple access protocol fortransmission of network-protocol datagrams, encapsulated in HDLC frameswith 16 bit addressing, over SONET/SDH. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.2174 Murakami Jun 97 A MAPOS version 1 Extension - Switch-Switch ProtocolThis memo documents a MAPOS (Multiple Access Protocol over SONET/SDH)version 1 extension, Switch Switch Protocol which provides dynamicrouting for unicast, broadcast, and multicast. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.2173 Murakami Jun 97 A MAPOS version 1 Extension - Node Switch ProtocolThis document describes a MAPOS extension, Node Switch Protocol, forautomatic node address assignment. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.2172 Maruyama Jun 97 MAPOS Version 1 Assigned NumbersThis memo documents the parameters used in the Multiple Access Protocolover SONET/SDH Version 1. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.Ramos Informational [Page 6]
RFC 2199 Summary of 2100-2199 January 19982171 Murakami Jun 97 MAPOS - Multiple Access Protocol over SONET/SDH Version 1This memo documents a multiple access protocol for transmission ofnetwork-protocol datagrams, encapsulated in High-Level Data Link Control(HDLC) frames, over SONET/SDH. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.2170 Almesberger Jul 97 Application REQuested IP over ATM (AREQUIPA)This document specifies a method for allowing ATM-attached hosts thathave direct ATM connectivity to set up end-to-end IP over ATMconnections within the reachable ATM cloud, on request fromapplications, and for the exclusive use by the requesting applications.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.2169 Daniel Jun 97 A Trivial Convention for using HTTP in URN ResolutionThis document specifies the "THTTP" resolution protocol - a trivialconvention for encoding resolution service requests and responses asHTTP 1.0 or 1.1 requests and responses. This memo defines anExperimental Protocol for the Internet community. This memo does notspecify an Internet standard of any kind. Discussion and suggestionsfor improvement are requested.2168 Daniel Jun 97 Resolution of Uniform Resource Identifiers using the Domain Name SystemThe requirements document for URN resolution systems defines the conceptof a "resolver discovery service". This document describes the first,experimental, RDS. It is implemented by a new DNS Resource Record, NAPTR(Naming Authority PoinTeR), that provides rules for mapping parts ofURIs to domain names. This memo defines an Experimental Protocol forthe Internet community.Ramos Informational [Page 7]
RFC 2199 Summary of 2100-2199 January 19982167 Williamson Jun 97 Referral Whois (RWhois) Protocol V1.5This memo describes Version 1.5 of the client/server interaction ofRWhois. RWhois provides a distributed system for the discovery,retrieval, and maintenance of directory information. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.2166 Bryant Jun 97 APPN Implementer's Workshop Closed Pages DocumentThis document specifies a set of extensions toRFC 1795 designed toimprove the scalability of DLSw clarifications toRFC 1795 in the lightof the implementation experience to-date. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.2165 Veizades Jun 97 Service Location ProtocolThe Service Location Protocol provides a scalable framework for thediscovery and selection of network services. Using this protocol,computers using the Internet no longer need so much static configurationof network services for network based applications. This is especiallyimportant as computers become more portable, and users less tolerant orable to fulfill the demands of network system administration.[STANDARDS-TRACK]2164 Kille Jan 98 Use of an X.500/LDAP directory to support MIXER address mappingThis specification defines how to represent and maintain these mappings(MIXER Conformant Global Address Mappings of MCGAMs) in an X.500 or LDAPdirectory. [STANDARDS-TRACK]2163 Allocchio Jan 98 Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM)This memo is the complete technical specification to store in theInternet Domain Name System (DNS) the mapping information (MCGAM) neededby MIXER conformant e-mail gateways and other tools to mapRFC822 domainnames into X.400 O/R names and vice versa. [STANDARDS-TRACK]Ramos Informational [Page 8]
RFC 2199 Summary of 2100-2199 January 19982162 Allocchio Jan 98 MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mailThe standard referred shortly into this document as "X.400" relates tothe ISO/IEC 10021 - CCITT 1984, 1988 and 1992 X.400 SeriesRecommendations covering the Message Oriented Text Interchange Service(MOTIS). This document covers the Inter Personal Messaging System (IPMS)only. This memo defines an Experimental Protocol for the Internetcommunity.2161 Alvestrand Jan 98 A MIME Body Part for ODAThis document contains the definitions, originally contained inRFC 1495andRFC 1341, on how to carry ODA in MIME, and how to translate it toits X.400 representation. This memo defines an Experimental Protocolfor the Internet community.2160 Alvestrand Jan 98 Carrying PostScript in X.400 and MIMEThis document describes methods for carrying PostScript information inthe two standard mail systems MIME and X.400, and the conversion betweenthem. [STANDARDS-TRACK]2159 Alvestrand Jan 98 A MIME Body Part for FAXThis document contains the definitions, originally contained in RFC1494, on how to carry CCITT G3Fax in MIME, and how to translate it toits X.400 representation. [STANDARDS-TRACK]2158 Alvestrand Jan 98 X.400 Image Body PartsThis document contains the body parts defined inRFC 1495 for carryingimage formats that were originally defined in MIME through an X.400system. [STANDARDS-TRACK]2157 Alvestrand Jan 98 Mapping between X.400 andRFC-822/MIME Message BodiesThis document defines how to map body parts of X.400 messages into MIMEentities and vice versa, including the handling of multipart messagesand forwarded messages. [STANDARDS-TRACK]Ramos Informational [Page 9]
RFC 2199 Summary of 2100-2199 January 19982156 Kille Jan 98 MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 andRFC 822/MIMEThis document relates primarily to the ITU-T 1988 and 1992 X.400 SeriesRecommendations / ISO IEC 10021 International Standard. This ISO/ITU-Tstandard is referred to in this document as "X.400", which is aconvenient shorthand. [STANDARDS-TRACK]2155 Clouston Jun 97 Definitions of Managed Objects for APPN 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 APPN (Advanced Peer-to-Peer Networking) capabilities. Thismemo identifies managed objects for the APPN protocol. [STANDARDS-TRACK]2154 Murphy Jun 97 OSPF with Digital SignaturesThis memo describes the extensions to OSPF required to add digitalsignature authentication to Link State data, and to provide acertification mechanism for router data. Added LSA processing and keymanagement is detailed. A method for migration from, or co-existencewith, standard OSPF V2 is described. This memo defines an ExperimentalProtocol for the Internet community.2153 Simpson May 97 PPP Vendor ExtensionsThe Point-to-Point Protocol (PPP) provides a standard method fortransporting multi-protocol datagrams over point-to-point links. PPPdefines an extensible Link Control Protocol (LCP) for establishing,configuring, and testing the data-link connection; and a family ofNetwork Control Protocols (NCPs) for establishing and configuringdifferent network-layer protocols. This document provides informationfor the Internet community. It does not specify an Internet standard ofany kind.Ramos Informational [Page 10]
RFC 2199 Summary of 2100-2199 January 19982152 Goldsmith May 97 A Mail-Safe Transformation Format of UnicodeThis document describes a transformation format of Unicode that containsonly 7-bit ASCII octets and is intended to be readable by humans in thelimiting case that the document consists of characters from the US-ASCIIrepertoire. It also specifies how this transformation format is used inthe context of MIME andRFC 1641, "Using Unicode with MIME". This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.2151 Kessler Jun 97 A Primer On Internet and TCP/IP Tools and UtilitiesThis memo is an introductory guide to many of the most commonly-available TCP/IP and Internet tools and utilities. It also describesdiscussion lists accessible from the Internet, ways to obtain Internetand TCP/IP documents, and some resources that help users weave their waythrough the Internet. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.2150 Max Oct 97 Humanities and Arts: Sharing Center Stage on the InternetThe purpose of this document is to provide members of the Arts andHumanities communities with an introduction to the Internet as avaluable tool, resource, and medium for the creation, presentation, andpreservation of Arts and Humanities-based content. This memo providesinformation for the Internet community. It does not specify an Internetstandard of any kind.2149 Talpade May 97 Multicast Server Architectures for MARS-based ATM multicastingThis memo provides details on the design and implementation of an MCS,building on the core mechanisms defined inRFC 2022. It also provides amechanism for using multiple MCSs per group for providing faulttolerance. This approach can be used withRFC 2022 based MARS serverand clients, without needing any change in their functionality. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.Ramos Informational [Page 11]
RFC 2199 Summary of 2100-2199 January 19982148 Alvestrand Sep 97 Deployment of the Internet White Pages ServiceThis document describes the way in which the Internet White PagesService is best exploited using today's experience, today's protocols,today's products and today's procedures. This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.2147 Borman May 97 TCP and UDP over IPv6 JumbogramsIPv6 supports datagrams larger than 65535 bytes long, often referred toas jumbograms, through use of the Jumbo Payload hop-by-hop option. TheUDP protocol has a 16-bit length field that keeps it from being able tomake use of jumbograms, and though TCP does not have a length field,both the MSS option and the Urgent field are constrained by 16-bits.This document describes some simple changes that can be made to allowTCP and UDP to make use of IPv6 jumbograms. [STANDARDS-TRACK]2146 FNC May 97 U.S. Government Internet Domain NamesThis memo provides an update and clarification toRFC 1816. Thisdocument describes the registration policies for the top-level domain".GOV". The purpose of the domain is to provide naming conventions thatidentify US Federal government agencies in order to facilitate access totheir electronic resources. This memo provides guidance forregistrations by Federal Agencies that avoids name duplication andfacilitates responsiveness to the public. It restricts registrations tocoincide with the approved structure of the US government and the adviceof its Chief Information Officers. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.2145 Mogul May 97 Use and Interpretation of HTTP Version NumbersHTTP request and response messages include an HTTP protocol versionnumber. Some confusion exists concerning the proper use andinterpretation of HTTP version numbers, and concerning interoperabilityof HTTP implementations of different protocol versions. This documentis an attempt to clarify the situation. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.Ramos Informational [Page 12]
RFC 2199 Summary of 2100-2199 January 19982144 Adams May 97 The CAST-128 Encryption AlgorithmThere is a need in the Internet community for an unencumbered encryptionalgorithm with a range of key sizes that can provide security for avariety of cryptographic applications and protocols. This documentdescribes an existing algorithm that can be used to satisfy thisrequirement. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.2143 Elliston May 97 Encapsulating IP with the Small Computer System InterfaceThis document outlines a protocol for connecting hosts running theTCP/IP protocol suite over a Small Computer System Interface (SCSI) bus.This memo defines an Experimental Protocol for the Internet community.This memo does not specify an Internet standard of any kind.2142 Crocker May 97 MAILBOX NAMES FOR COMMON SERVICES, ROLES AND FUNCTIONSThis specification enumerates and describes Internet mail addresses(mailbox name @ host reference) to be used when contacting personnel atan organization. [STANDARDS-TRACK]2141 Moats May 97 URN SyntaxUniform Resource Names (URNs) are intended to serve as persistent,location-independent, resource identifiers. This document sets forwardthe canonical syntax for URNs. [STANDARDS-TRACK]2140 Touch Apr 97 TCP Control Block InterdependenceThis memo makes the case for interdependent TCP control blocks, wherepart of the TCP state is shared among similar concurrent connections, oracross similar connection instances. TCP state includes a combination ofparameters, such as connection state, current round-trip time estimates,congestion control information, and process information. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.Ramos Informational [Page 13]
RFC 2199 Summary of 2100-2199 January 19982139 Rigney Apr 97 RADIUS AccountingThis document describes a protocol for carrying accounting informationbetween a Network Access Server and a shared Accounting Server. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.2138 Rigney Apr 97 Remote Authentication Dial In User Service (RADIUS)This document describes a protocol for carrying authentication,authorization, and configuration information between a Network AccessServer which desires to authenticate its links and a sharedAuthentication Server. [STANDARDS-TRACK]2137 Eastlake 3rd Apr 97 Secure Domain Name System Dynamic UpdateThis memo describes how to use DNSSEC digital signatures coveringrequests and data to secure updates and restrict updates to thoseauthorized to perform them as indicated by the updater's possession ofcryptographic keys. [STANDARDS-TRACK]2136 Vixie Apr 97 Dynamic Updates in the Domain Name System (DNS UPDATE)Using this specification of the UPDATE opcode, it is possible to add ordelete RRs or RRsets from a specified zone. Prerequisites are specifiedseparately from update operations, and can specify a dependency uponeither the previous existence or nonexistence of an RRset, or theexistence of a single RR. [STANDARDS-TRACK]2135 ISOC BOT Apr 97 Internet Society By-LawsThese are the by-laws of the Internet Society, as amended, as of June1996. They are published for the information of the IETF community atthe request of the poisson working group. Please refer to the ISOC webpage (www.isoc.org) for the current version of the by-laws. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.Ramos Informational [Page 14]
RFC 2199 Summary of 2100-2199 January 19982134 ISOC BOT Apr 97 ARTICLES OF INCORPORATION OF INTERNET SOCIETYThese are the articles of incorporation of the Internet Society. Theyare published for the information of the IETF community at the requestof the poisson working group. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.2133 Gilligan Apr 97 Basic Socket Interface Extensions for IPv6This memo defines a set of extensions to the socket interface to supportthe larger address size and new features of IPv6. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.2132 Alexander Mar 97 DHCP Options and BOOTP Vendor ExtensionsThis document specifies the current set of DHCP options. Future optionswill be specified in separate RFCs. The current list of valid optionsis also available inftp://ftp.isi.edu/in-notes/iana/assignments.[STANDARDS-TRACK]2131 Droms Mar 97 Dynamic Host Configuration ProtocolThe Dynamic Host Configuration Protocol (DHCP) provides a framework forpassing configuration information to hosts on a TCPIP network. DHCP isbased on the Bootstrap Protocol (BOOTP), adding the capability ofautomatic allocation of reusable network addresses and additionalconfiguration options. [STANDARDS-TRACK]2130 Weider Apr 97 The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996This report details the conclusions of an IAB-sponsored invitationalworkshop held 29 February - 1 March, 1996, to discuss the use ofcharacter sets on the Internet. It motivates the need to have characterset handling in Internet protocols which transmit text, provides aconceptual framework for specifying character sets, recommends the useof MIME tagging for transmitted text, recommends a default character set*without* stating that there is no need for other character sets, andRamos Informational [Page 15]
RFC 2199 Summary of 2100-2199 January 1998makes a series of recommendations to the IAB, IANA, and the IESG forfurthering the integration of the character set framework into texttransmission protocols. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.2129 Nagami Apr 97 Toshiba's Flow Attribute Notification Protocol (FANP) SpecificationThis memo discusses Flow Attribute Notification Protocol (FANP), whichis a protocol between neighbor nodes for the management of cut-throughpacket forwarding functionalities. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.2128 Roeck Mar 97 Dial Control Management Information Base 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 demand accesscircuits, including ISDN. [STANDARDS-TRACK]2127 Roeck Mar 97 ISDN Management Information Base using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines a minimal set of managed objects for SNMP-basedmanagement of ISDN terminal interfaces. [STANDARDS-TRACK]2126 Pouffary Mar 97 ISO Transport Service on top of TCP (ITOT)This document is a revision to STD35,RFC1006. This document describesthe mechanism to allow ISO Transport Services to run over TCP over IPv4or IPv6. It also defines a number of new features, which are notprovided inRFC1006. [STANDARDS-TRACK]Ramos Informational [Page 16]
RFC 2199 Summary of 2100-2199 January 19982125 Richards Mar 97 The PPP Bandwidth Allocation Protocol (BAP), The PPP Bandwidth Allocation Control Protocol (BACP)This document proposes a method to manage the dynamic bandwidthallocation of implementations supporting the PPP multilink protocol.This is done by defining the Bandwidth Allocation Protocol (BAP), aswell as its associated control protocol, the Bandwidth AllocationControl Protocol (BACP). [STANDARDS-TRACK]2124 Amsden Mar 97 Cabletron's Light-weight Flow Admission Protocol SpecificationThis document specifies the protocol between the switch ConnectionControl Entity (CCE) and the external FAS. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.2123 Brownlee Mar 97 Traffic Flow Measurement: Experiences with NeTraMetThis memo records experiences in implementing and using the Traffic FlowMeasurement Architecture and Meter MIB. It discusses the implementationof NeTraMet (a traffic meter) and NeMaC (a combined manager and meterreader), considers the writing of meter rule sets and gives someguidance on setting up a traffic flow measurement system using NeTraMet.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.2122 Mavrakis Mar 97 VEMMI URL SpecificationA new URL scheme, "vemmi" is defined. VEMMI is a new internationalstandard for on-line multimedia services, that is both an ITU-T(International Telecommunications Union, ex. CCITT) InternationalStandard (T.107) and an European Standard (ETSI EuropeanTelecommunications Standard Institute) standard (ETS 300 382, obsoletedby ETS 300 709). [STANDARDS-TRACK]2121 Armitage Mar 97 Issues affecting MARS Cluster SizeThis document provides a qualitative look at the issues constraining aMARS Cluster's size, including the impact of VC limits in switches andNICs, geographical distribution of cluster members, and the use of VCRamos Informational [Page 17]
RFC 2199 Summary of 2100-2199 January 1998Mesh or MCS modes to support multicast groups. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.2120 Chadwick Mar 97 Managing the X.500 Root Naming ContextThis document describes the use of 1993 ISO X.500 Standard protocols formanaging the root context. Whilst the ASN.1 is compatible with that ofthe X.500 Standard, the actual settings of the parameters aresupplementary to that of the X.500 Standard. This memo defines anExperimental Protocol for the Internet community.2119 Bradner Mar 97 Key words for use in RFCs to Indicate Requirement LevelsIn many standards track documents several words are used to signify therequirements in the specification. These words are often capitalized.This document defines these words as they should be interpreted in IETFdocuments. This document specifies an Internet Best Current Practicesfor the Internet Community, and requests discussion and suggestions forimprovements.2118 Pall Mar 97 Microsoft Point-To-Point Compression (MPPC) ProtocolThis document describes the use of the Microsoft Point to PointCompression protocol (also referred to as MPPC in this document) forcompressing PPP encapsulated packets. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.2117 Estrin Jun 97 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol SpecificationThis document describes a protocol for efficiently routing to multicastgroups that may span wide-area (and inter-domain) internets. This memodefines an Experimental Protocol for the Internet community.Ramos Informational [Page 18]
RFC 2199 Summary of 2100-2199 January 19982116 Apple Apr 97 X.500 Implementations Catalog-96This document is a revision to [RFC 1632]: A Revised Catalog ofAvailable X.500 Implementations and is based on the results of datacollection via a WWW home page that enabled implementors to submit newor updated descriptions of currently available implementations of X.500,including commercial products and openly available offerings. [RFC 1632]is a revision of [RFC 1292]. This document contains detaileddescription of 31 X.500 implementations - DSAs, DUAs, and DUAinterfaces. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.2115 Brown Sep 97 Management Information Base for Frame Relay DTEs Using SMIv2This 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 Frame Relay interfaces onDTEs. [STANDARDS-TRACK]2114 Chiang Feb 97 Data Link Switching Client Access ProtocolThis memo describes the Data Link Switching Client Access Protocol thatis used between workstations and routers to transport SNA/ NetBIOStraffic over TCP sessions. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.2113 Katz Feb 97 IP Router Alert OptionThis memo describes a new IP Option type that alerts transit routers tomore closely examine the contents of an IP packet. [STANDARDS-TRACK]2112 Levinson Mar 97 The MIME Multipart/Related Content-typeThe Multipart/Related content-type provides a common mechanism forrepresenting objects that are aggregates of related MIME body parts.This document defines the Multipart/Related content-type and providesexamples of its use. [STANDARDS-TRACK]Ramos Informational [Page 19]
RFC 2199 Summary of 2100-2199 January 19982111 Levinson Mar 97 Content-ID and Message-ID Uniform Resource LocatorsThe Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allowreferences to messages and the body parts of messages. For example,within a single multipart message, one HTML body part might includeembedded references to other parts of the same message. [STANDARDS-TRACK]2110 Palme Mar 97 MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)This document describes a set of guidelines that will allow conformingmail user agents to be able to send, deliver and display these objects,such as HTML objects, that can contain links represented by URIs.[STANDARDS-TRACK]2109 Kristol Feb 97 HTTP State Management MechanismThis document specifies a way to create a stateful session with HTTPrequests and responses. It describes two new headers, Cookie and Set-Cookie, which carry state information between participating originservers and user agents. The method described here differs fromNetscape's Cookie proposal, but it can interoperate with HTTP/1.0 useragents that use Netscape's method. [STANDARDS-TRACK]2108 de Graaf Feb 97 Definitions of Managed Objects for IEEE 802.3 Repeater Device 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 managing IEEE 802.3 10 and 100Mb/second baseband repeaters based on IEEE Std 802.3Section 30, "10 &100 Mb/s Management," October 26, 1995.[STANDARDS-TRACK]2107 Hamzeh Feb 97 Ascend Tunnel Management Protocol - ATMPThis document specifies a generic tunnel management protocol that allowsremote dial-in users to access their home network as if they weredirectly attached to the home network. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.Ramos Informational [Page 20]
RFC 2199 Summary of 2100-2199 January 19982106 Chiang Feb 97 Data Link Switching Remote Access ProtocolThis memo describes the Data Link Switching Remote Access Protocol thatis used between workstations and routers to transport SNA/ NetBIOStraffic over TCP sessions. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.2105 Rekhter Feb 97 Cisco Systems' Tag Switching Architecture OverviewThis document provides an overview of a novel approach to network layerpacket forwarding, called tag switching. The two main components of thetag switching architecture - forwarding and control - are described.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.2104 Krawcyzk Feb 97 HMAC: Keyed-Hashing for Message AuthenticationThis document describes HMAC, a mechanism for message authenticationusing cryptographic hash functions. HMAC can be used with any iterativecryptographic hash function, e.g., MD5, SHA-1, in combination with asecret shared key. The cryptographic strength of HMAC depends on theproperties of the underlying hash function. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind2103 Ramanathan Feb 97 Mobility Support for Nimrod : Challenges and Solution ApproachesWe discuss the issue of mobility in Nimrod. While a mobility solutionis not part of the Nimrod architecture, Nimrod does require that thesolution have certain characteristics. We identify the requirementsthat Nimrod has of any solution for mobility support. We also classifyand compare existing approaches for supporting mobility within aninternetwork and discuss their advantages and disadvantages. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.Ramos Informational [Page 21]
RFC 2199 Summary of 2100-2199 January 19982102 Ramanathan Feb 97 Multicast Support for Nimrod : Challenges and Solution ApproachesNimrod does not specify a particular solution for multicasting. Rather,Nimrod may use any of a number of emerging multicast techniques. Weidentify the requirements that Nimrod has of a solution for multicastsupport. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.2101 Carpenter Feb 97 IPv4 Address Behaviour TodayThe main purpose of this note is to clarify the current interpretationof the 32-bit IP version 4 address space, whose significance has changedsubstantially since it was originally defined. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.2100 Ashworth Apr 97 The Naming of HostsThis RFC is a commentary on the difficulty of deciding upon anacceptably distinctive hostname for one's computer, a problem whichgrows in direct proportion to the logarithmically increasing size of theInternet. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.Security Considerations Security issues are not discussed in this memo.Author's Address Alegre Ramos University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: ramos@isi.eduRamos Informational [Page 22]
RFC 2199 Summary of 2100-2199 January 1998Full Copyright Statement Copyright (C) The Internet Society (1998). 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.Ramos Informational [Page 23]
[8]ページ先頭