Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group J. ElliottRequest for Comments: 1899 ISICategory: Informational January 1997Request for Comments Summary RFC Numbers 1800-1899Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 1800 through RFCs 1899. 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.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--- ------ ---- -----1899 Elliott Jan 97 Requests For Comments SummaryThis memo.1898 Eastlake Feb 96 CyberCash Credit Card Protocol Version 0.8This document covers only the current CyberCash system which is one ofthe few operational systems in the rapidly evolving area of Internetpayments. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.Elliott Informational [Page 1]
RFC 1899 Summary of 1800-1899 January 19971897 Hinden Jan 96 IPv6 Testing Address AllocationThis document describes an allocation plan for IPv6 addresses to be usedin testing IPv6 prototype software. This document specifies anExperimental protocol for the Internet community.1896 Resnick Feb 96 The text/enriched MIME Content-typeThis document defines one particular type of MIME data, thetext/enriched MIME type. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1895 Levinson Feb 96 The Application/CALS-1840 Content-typeThis memorandum provides guidelines for using the United StatesDepartment of Defense Military Standard MIL-STD-1840, "AutomatedInterchange of Technical Information," with the Internet electronic mailstandards,RFC 822 andRFC 1521. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1894 Moore Jan 96 An Extensible Message Format for Delivery Status NotificationsThis memo defines a MIME content-type that may be used by a messagetransfer agent (MTA) or electronic mail gateway to report the result ofan attempt to deliver a message to one or more recipients. [STANDARDS-TRACK]1893 Vaudreuil Jan 96 Enhanced Mail System Status CodesThere currently is not a standard mechanism for the reporting of mailsystem errors except for the limited set offered by SMTP and the systemspecific text descriptions sent in mail messages. There is a pressingneed for a rich machine readable status code for use in delivery statusnotifications [DSN]. This document proposes a new set of status codesfor this purpose. [STANDARDS-TRACK]Elliott Informational [Page 2]
RFC 1899 Summary of 1800-1899 January 19971892 Vaudreuil Jan 96 The Multipart/Report Content Type for the Reporting of Mail System Administrative MessagesThe Multipart/Report MIME content-type is a general "family" or"container" type for electronic mail reports of any kind. Although thismemo defines only the use of the Multipart/Report content-type withrespect to delivery status reports, mail processing programs willbenefit if a single content-type is used to for all kinds of reports.[STANDARDS-TRACK]1891 Moore Jan 96 SMTP Service Extension for Delivery Status NotificationsThis memo defines an extension to the SMTP service, which allows an SMTPclient to specify (a) that delivery status notifications (DSNs) shouldbe generated under certain conditions, (b) whether such notificationsshould return the contents of the message, and (c) additionalinformation, to be returned with a DSN, that allows the sender toidentify both the recipient(s) for which the DSN was issued, and thetransaction in which the original message was sent. [STANDARDS-TRACK]1890 A.V.T.W.G. Jan 96 RTP Profile for Audio and Video Conferences with Minimal ControlThis memo describes a profile for the use of the real-time transportprotocol (RTP), version 2, and the associated control protocol, RTCP,within audio and video multiparticipant conferences with minimalcontrol. [STANDARDS-TRACK]1889 A.V.T.W.G. Jan 96 RTP: A Transport Protocol for Real-Time ApplicationsThis memorandum describes RTP, the real-time transport protocol. RTPprovides end-to-end network transport functions suitable forapplications transmitting real-time data, such as audio, video orsimulation data, over multicast or unicast network services.[STANDARDS-TRACK]Elliott Informational [Page 3]
RFC 1899 Summary of 1800-1899 January 19971888 Bound Aug 96 OSI NSAPs and IPv6This document recommends that network implementors who have planned ordeployed an OSI NSAP addressing plan, and who wish to deploy ortransition to IPv6, should redesign a native IPv6 addressing plan tomeet their needs. This memo defines an Experimental Protocol for theInternet community.1887 Rekhter Dec 95 An Architecture for IPv6 Unicast Address AllocationThis document provides an architecture for allocating IPv6 [1] unicastaddresses in the Internet. This document provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1886 Thomson Dec 95 DNS Extensions to support IP version 6This document defines the changes that need to be made to the DomainName System to support hosts running IP version 6 (IPv6). [STANDARDS-TRACK]1885 Conta Dec 95 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)This document specifies a set of Internet Control Message Protocol(ICMP) messages for use with version 6 of the Internet Protocol (IPv6).[STANDARDS-TRACK]1884 Hinden Dec 95 IP Version 6 Addressing ArchitectureThis specification defines the addressing architecture of the IP Version6 protocol [IPV6].[STANDARDS-TRACK]1883 Deering Dec 95 Internet Protocol, Version 6 (IPv6) SpecificationThis document specifies version 6 of the Internet Protocol (IPv6), alsosometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK]Elliott Informational [Page 4]
RFC 1899 Summary of 1800-1899 January 19971882 Hancock Dec 95 The 12-Days of Technology Before ChristmasThis memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1881 IAB & IESG Dec 95 IPv6 Address Allocation ManagementThe IPv6 address space will be managed by the IANA for the good of theInternet community, with advice from the IAB and the IESG, by delegationto the regional registries. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1880 I.A.B. Nov 95 INTERNET OFFICIAL PROTOCOL STANDARDSThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Architecture Board (IAB).[STANDARDS-TRACK]1879 Manning Jan 96 Class A Subnet Experiment Results and RecommendationsThis memo documents some experiences with theRFC 1797 [1] subnet Aexperiment (performed by the Net39 Test Group (see credits)) andprovides a number of recommendations on future direction for both theInternet Registries and the Operations community. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1878 Pummill Dec 95 Variable Length Subnet Table For IPv4This memo clarifies issues surrounding subnetting IP networks byproviding a standard subnet table. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.Elliott Informational [Page 5]
RFC 1899 Summary of 1800-1899 January 19971877 Cobb Dec 95 PPP Internet Protocol Control Protocol Extensions for Name Server AddressesThis document extends the NCP for establishing and configuring theInternet Protocol over PPP [2], defining the negotiation of primary andsecondary Domain Name System (DNS) [3] and NetBIOS Name Server (NBNS)[4] addresses. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1876 Davis Jan 96 A Means for Expressing Location Information in the Domain Name SystemThis memo defines a new DNS RR type for experimental purposes. This RFCdescribes a mechanism to allow the DNS to carry location informationabout hosts, networks, and subnets. This memo defines an ExperimentalProtocol for the Internet community.1875 Berge Dec 95 UNINETT PCA Policy StatementsThis document provides information about policy statements submitted bythe UNINETT Policy Certification Authority (UNINETT PCA). This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1874 Levinson Dec 95 SGML Media TypesThis document proposes new media sub-types of Text/SGML andApplication/SGML. This memo defines an Experimental Protocol for theInternet community.1873 Levinson Dec 95 Message/External-Body Content-ID Access TypeThe existing MIME Content-Type Message/External-Body access-types allowa MIME entity (body-part) to refer to an object that is not in themessage by specifying how to access that object. The Content-ID accessmethod described in this document provides the capability to refer to anobject within the message. This memo defines an Experimental Protocolfor the Internet community.Elliott Informational [Page 6]
RFC 1899 Summary of 1800-1899 January 19971872 Levinson Dec 95 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. This memo defines an Experimental Protocol for theInternet community.1871 Postel Nov 95 Addendum toRFC 1602 -- Variance ProcedureThis document describes a modification to the IETF procedures to allowan escape from a situation where the existing procedures are not workingor do not seem to apply. This document specifies an Internet BestCurrent Practices for the Internet Community, and requests discussionand suggestions for improvements.1870 Klensin Nov 95 SMTP Service Extension for Message Size DeclarationThis memo defines an extension to the SMTP service whereby an SMTPclient and server may interact to give the server an opportunity todecline to accept a message (perhaps temporarily) based on the client'sestimate of the message size. [STANDARDS-TRACK]1869 Klensin Nov 95 SMTP Service ExtensionsThis memo defines a framework for extending the SMTP service by defininga means whereby a server SMTP can inform a client SMTP as to the serviceextensions it supports. [STANDARDS-TRACK]1868 Malkin Nov 95 ARP Extension - UNARPThis document specifies a trivial modification to the ARP mechanism, notthe packet format, which allows a node to announce that it is leavingthe network and that all other nodes should modify their ARP tablesaccordingly. This memo defines an Experimental Protocol for theInternet community.Elliott Informational [Page 7]
RFC 1899 Summary of 1800-1899 January 19971867 Nebel Nov 95 Form-based File Upload in HTMLSince file-upload is a feature that will benefit many applications, thisproposes an extension to HTML to allow information providers to expressfile upload requests uniformly, and a MIME compatible representation forfile upload responses. This memo defines an Experimental Protocol forthe Internet community.1866 Berners-LeeNov 95 Hypertext Markup Language - 2.0This document defines a HTML 2.0 (to distinguish it from the previousinformal specifications). [STANDARDS-TRACK]1865 Houser Jan 96 EDI Meets the Internet: Frequently Asked Questions about Electronic Data Interchange (EDI) on the InternetThis memo is targeted towards the EDI community that is unfamiliar withthe Internet, including EDI software developers, users, and serviceproviders. The memo introduces the Internet and assumes a basicknowledge of EDI. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1864 Myers Oct 95 The Content-MD5 Header FieldThis memo specifies an optional header field, Content-MD5, for use withMIME-conformant messages. [STANDARDS-TRACK]1863 Haskin Oct 95 A BGP/IDRP Route Server alternative to a full mesh routingThis document describes the use and detailed design of Route Servers fordissemination of routing information among BGP/IDRP speaking routers.This memo defines an Experimental Protocol for the Internet community.Elliott Informational [Page 8]
RFC 1899 Summary of 1800-1899 January 19971862 McCahill Nov 95 Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994This document is a report on an Internet architecture workshop,initiated by the IAB and held at MCI on October 12-14, 1994. Thisworkshop generally focused on aspects of the information infrastructureon the Internet. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1861 Gwinn Oct 95 Simple Network Paging Protocol - Version 3 - Two-Way EnhancedThis RFC suggests a simple way for delivering wireless messages, bothone and two-way, to appropriate receiving devices. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1860 Pummill Oct 95 Variable Length Subnet Table For IPv4This document itemizes the potential values for IPv4 subnets. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1859 Pouffary Oct 95 ISO Transport Class 2 Non-use of Explicit Flow Control over TCPRFC1006 extensionThis document is an extension to STD35,RFC1006, a standard for theInternet community. The document does not duplicate the protocoldefinitions contained inRFC1006 and in International Standard ISO 8073.It supplements that information with the description of how to implementISO Transport Class 2 Non-use of Explicit Flow Control on top of TCP.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.Elliott Informational [Page 9]
RFC 1899 Summary of 1800-1899 January 19971858 Ziemba Oct 95 Security Considerations for IP Fragment FilteringIP fragmentation can be used to disguise TCP packets from IP filtersused in routers and hosts. This document describes two methods of attackas well as remedies to prevent them. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.1857 Lambert Oct 95 A Model for Common Operational StatisticsThis memo describes a model for operational statistics in the Internet.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1856 Clark Shpt 95 The Opstat Client-Server Model for Statistics RetrievalThis document defines a model and protocol for a set of tools whichcould be used by NSPs and Network Operation Centers (NOCs) to share dataamong themselves and with customers. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.1855 Hambridge Oct 95 Netiquette GuidelinesThis document provides a minimum set of guidelines for Network Etiquette(Netiquette) which organizations may take and adapt for their own use.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1854 Freed Oct 95 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]Elliott Informational [Page 10]
RFC 1899 Summary of 1800-1899 January 19971853 Simpson Oct 95 IP in IP TunnelingThis document discusses implementation techniques for using IPProtocol/Payload number 4 Encapsulation for tunneling with IP Securityand other protocols. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1852 Metzger Spt 95 IP Authentication using Keyed SHAThis document describes the use of keyed SHA with the IP AuthenticationHeader. This document defines an Experimental Protocol for the Internetcommunity.1851 Karn Spt 95 The ESP Triple DES TransformThis document describes the Triple DES-CBC security transform for the IPEncapsulating Security Payload (ESP). This document defines anExperimental Protocol for the Internet community.1850 Baker Nov 95 OSPF Version 2 Management Information BaseThis 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 the Open Shortest Path FirstRouting Protocol. [STANDARDS-TRACK]1849 Never Issued.1848 Crocker Oct 95 MIME Object Security ServicesThis document defines MIME Object Security Services (MOSS), a protocolthat uses the multipart/signed and multipart/encrypted framework [7] toapply digital signature and encryption services to MIME objects.[STANDARDS-TRACK]1847 Galvin Oct 95 Security Multiparts for MIME: Multipart/Signed and Multipart/EncryptedThis document defines a framework within which security services may beapplied to MIME body parts. [STANDARDS-TRACK]Elliott Informational [Page 11]
RFC 1899 Summary of 1800-1899 January 19971846 Durand Spt 95 SMTP 521 Reply CodeThis memo defines a new Simple Mail Transfer Protocol (SMTP) [1] replycode, 521, which one may use to indicate that an Internet host does notaccept incoming mail. This memo defines an Experimental Protocol forthe Internet community.1845 Crocker Spt 95 SMTP Service Extension for Checkpoint/RestartThis memo defines an extension to the SMTP service whereby aninterrupted SMTP transaction can be restarted at a later time withouthaving to repeat all of the commands and message content sent prior tothe interruption. This memo defines an Experimental Protocol for theInternet community.1844 Huizer Aug 95 Multimedia E-mail (MIME) User Agent checklistThis document presents a checklist to facilitate evaluation of MIMEcapable User Agents. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1843 Lee Aug 95 HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII charactersThe content of this memo is identical to an article of the same titlewritten by the author on September 4, 1989. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1842 Wei Aug 95 ASCII Printable Characters-Based Chinese Character Encoding for Internet MessagesThis document describes the encoding used in electronic mail [RFC822]and network news [RFC1036] messages over the Internet. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.Elliott Informational [Page 12]
RFC 1899 Summary of 1800-1899 January 19971841 Chapman Spt 95 PPP Network Control Protocol for LAN ExtensionTelecommunications infrastructure is improving to offer higher bandwidthconnections at lower cost. Access to the network is changing from modemsto more intelligent devices. This informational RFC discusses a PPPNetwork Control Protocol for one such intelligent device. The protocolis the LAN extension interface protocol. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.1840 Never Issued.1839 Never Issued.1838 Kille Aug 95 Use of the X.500 Directory to support mapping between X.400 andRFC 822 AddressesThis document defines how to use directory to support the mappingbetween X.400 O/R Addresses and mailboxes defined inRFC 1327 [2]. Thismemo defines an Experimental Protocol for the Internet community.1837 Kille Aug 95 Representing Tables and Subtrees in the X.500 DirectoryThis document defines techniques for representing two types ofinformation mapping in the OSI Directory. This memo defines anExperimental Protocol for the Internet community.1836 Kille Aug 95 Representing the O/R Address hierarchy in the X.500 Directory Information TreeThis document defines a representation of the O/R Address hierarchy inthe Directory Information Tree [6, 1]. This memo defines anExperimental Protocol for the Internet community.Elliott Informational [Page 13]
RFC 1899 Summary of 1800-1899 January 19971835 Deutsch Aug 95 Architecture of the WHOIS++ serviceThis document describes WHOIS++, an extension to the trivial WHOISservice described inRFC 954 to permit WHOIS-like servers to makeavailable more structured information to the Internet. [STANDARDS-TRACK]1834 Gargano Aug 95 Whois and Network Information Lookup Service Whois++This memo describes new features for WHOIS. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1833 Srinivasan Aug 95 Binding Protocols for ONC RPC Version 2This document describes the binding protocols used in conjunction withthe ONC Remote Procedure Call (ONC RPC Version 2) protocols.[STANDARDS-TRACK]1832 Srinivasan Aug 95 XDR: External Data Representation StandardThis document describes the External Data Representation Standard (XDR)protocol as it is currently deployed and accepted. [STANDARDS-TRACK]1831 Srinivasan Aug 95 RPC: Remote Procedure Call Protocol Specification Version 2This document describes the ONC Remote Procedure Call (ONC RPC Version2) protocol as it is currently deployed and accepted. [STANDARDS-TRACK]1830 Vaudreuil Aug 95 SMTP Service Extensions for Transmission of Large and Binary MIME MessagesThis memo defines two extensions to the SMTP service. The first serviceenables a SMTP client and server to negotiate the use of an alternateDATA command "BDAT" for efficiently sending large MIME messages. Thesecond extension takes advantage of the BDAT command to permit thenegotiated sending of unencoded binary data. This memo defines anExperimental Protocol for the Internet community.Elliott Informational [Page 14]
RFC 1899 Summary of 1800-1899 January 19971829 Karn Aug 95 The ESP DES-CBC TransformThis document describes the DES-CBC security transform for the IPEncapsulating Security Payload (ESP). [STANDARDS-TRACK]1828 Metzger Aug 95 IP Authentication using Keyed MD5This document describes the use of keyed MD5 with the IP AuthenticationHeader. [STANDARDS-TRACK]1827 Atkinson Aug 95 IP Encapsulating Security Payload (ESP)This document describes the IP Encapsulating Security Payload (ESP).ESP is a mechanism for providing integrity and confidentiality to IPdatagrams. [STANDARDS-TRACK]1826 Atkinson Aug 95 IP Authentication HeaderThis document describes a mechanism for providing cryptographicauthentication for IPv4 and IPv6 datagrams. [STANDARDS-TRACK]1825 Atkinson Aug 95 Security Architecture for the Internet ProtocolThis memo describes the security mechanisms for IP version 4 (IPv4) andIP version 6 (IPv6) and the services that they provide. [STANDARDS-TRACK]1824 Danisch Aug 95 The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4)This informational RFC describes the basic mechanisms and functions ofan identity based system for the secure authenticated exchange ofcryptographic keys, the generation of signatures, and the authenticdistribution of public keys. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.Elliott Informational [Page 15]
RFC 1899 Summary of 1800-1899 January 19971823 Howes Aug 95 The LDAP Application Program InterfaceThis document defines a C language application program interface to thelightweight directory access protocol (LDAP). This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1822 Lowe Aug 95 A Grant of Rights to Use a Specific IBM patent with PhoturisThis Request for Comments records a grant by IBM Corporation to permitthe conditional free use of one of its patents. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1821 Borden Aug 95 Integration of Real-time Services in an IP-ATM Network ArchitectureThe purpose of this paper is to provide a clear statement of what issuesneed to be addressed in interfacing the IP integrated servicesenvironment with an ATM service environment so as to create a seamlessinterface between the two in support of end users desiring real-timenetworking services. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1820 Huizer Aug 95 Multimedia E-mail (MIME) User Agent ChecklistThis document presents a checklist to facilitate evaluation of MIMEcapable User Agents. Access to a MIME test-responder, that generatestest-messages is described. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1819 ST2 W.G. Aug 95 Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+This memo contains a revised specification of the Internet STreamProtocol Version 2 (ST2). This memo defines an Experimental Protocolfor the Internet community.Elliott Informational [Page 16]
RFC 1899 Summary of 1800-1899 January 19971818 Postel Aug 95 Best Current PracticesThis document describes a new series of documents which describe bestcurrent practices for the Internet community. Documents in this seriescarry the endorsement of the Internet Engineering Steering Group (IESG).1817 Rekhter Aug 95 CIDR and Classful RoutingThis document represents the IAB's (Internet Architecture Board)evaluation of the current and near term implications of CIDR onorganizations that use Classful routing technology. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1816 F.N.C. Aug 95 U.S. Government Internet Domain NamesThis memo provides an update and clarification toRFC 1811. Thisdocument describes the registration policies for the top-level domain".GOV". This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1815 Ohta Jul 95 Character Sets ISO-10646 and ISO-10646-J-1For the practical use of ISO 10646, a lot of external profiling such asrestriction of characters, restriction of combination of characters andaddition of language information is necessary. This memo providesinformation on such profiling, along with charset names to each profiledinstance. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1814 Gerich Jun 95 Unique Addresses are GoodThe IAB suggests that whileRFC 1597 establishes reserved IP addressspace for the use of private networks which are isolated and will remainisolated from the Internet, any enterprise which anticipates externalconnectivity to the Internet should apply for a globally unique addressfrom an Internet registry or service provider. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.Elliott Informational [Page 17]
RFC 1899 Summary of 1800-1899 January 19971813 Callaghan Jun 95 NFS Version 3 Protocol SpecificationThis paper describes the NFS version 3 protocol. This paper is providedso that people can write compatible implementations. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1812 Baker Jun 95 Requirements for IP Version 4 RoutersThis memo defines and discusses requirements for devices that performthe network layer forwarding function of the Internet protocol suite.[STANDARDS-TRACK]1811 F.N.C. Jun 95 U.S. Government Internet Domain NamesThis document describes the registration policies for the top-leveldomain ".GOV". This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1810 Touch Jun 95 Report on MD5 PerformanceThis RFC addresses how fast MD5 can be implemented in software andhardware, and whether it supports currently available IP bandwidth.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1809 Partridge Jun 95 Using the Flow Label Field in IPv6The purpose of this memo is to distill various opinions and suggestionsof the End-to-End Research Group regarding the handling of Flow Labelsinto a set of suggestions for IPv6. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.1808 Fielding Jun 95 Relative Uniform Resource LocatorsIn situations where the base URL is well-defined and known to the parser(human or machine), it is useful to be able to embed URL referenceswhich inherit that context rather than re-specifying it in everyinstance. This document defines the syntax and semantics for suchRelative Uniform Resource Locators. [STANDARDS-TRACK]Elliott Informational [Page 18]
RFC 1899 Summary of 1800-1899 January 19971807 Lasher Jun 95 A Format for Bibliographic RecordsThis RFC defines a format for bibliographic records describing technicalreports. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1806 Troost Jun 95 Communicating Presentation Information in Internet Messages: The Content-Disposition HeadeThis memo provides a mechanism whereby messages conforming to the [RFC1521] ("MIME") specification can convey presentational information.This memo defines an Experimental Protocol for the Internet community.1805 Rubin Jun 95 Location-Independent Data/Software Integrity ProtocolThis memo describes a protocol for adding integrity assurance to filesthat are distributed across the Internet. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1804 Mansfield Jun 95 Schema Publishing in X.500 DirectoryIn this document we propose a solution using the existing mechanisms ofthe directory [1] itself. We present a naming scheme for naming schemaobjects and a meta-schema for storing schema objects in the directory.This memo defines an Experimental Protocol for the Internet community.1803 Wright Jun 95 Recommendations for an X.500 Production Directory ServiceThis document contains a set of basic recommendations for a country-level X.500 DSA. This memo provides information for the Internetcommunity. It does not specify an Internet standard of any kind.Elliott Informational [Page 19]
RFC 1899 Summary of 1800-1899 January 19971802 Alvestrand Jun 95 Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 RoutingThis memo describes a proposed Internet Pilot Project that seeks toprove the MHS-DS approach on a larger scale. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1801 Kille Jun 95 X.400-MHS use of the X.500 Directory to support X.400-MHS RoutingThe key problem in routing is to map from an O/R Address onto an MTA(next hop). This shall be an MTA which in some sense is "nearer" to thedestination UA. This is done repeatedly until the message can bedirectly delivered to the recipient UA. This memo defines anExperimental Protocol for the Internet community.1800 I.A.B. Jul 95 INTERNET OFFICIAL PROTOCOL STANDARDSThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Architecture Board (IAB).[STANDARDS-TRACK]Security Considerations Security issues are not discussed in this memo.Author's Address Josh Elliott University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: elliott@isi.eduElliott Informational [Page 20]
[8]ページ先頭