📄 rfc1899.txt
字号:
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 to RFC 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 while RFC 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]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -