📄 rfc1799.txt
字号:
1731 Myers Dec 94 IMAP4 Authentication MechanismsThe Internet Message Access Protocol, Version 4 [IMAP4] contains theAUTHENTICATE command, for identifying and authenticating a user to anIMAP4 server and for optionally negotiating a protection mechanism forsubsequent protocol interactions. This document describes severalauthentication mechanisms for use by the IMAP4 AUTHENTICATE command.[STANDARDS-TRACK]1730 Crispin Dec 94 Internet Message Access Protocol - Version 4The Internet Message Access Protocol, Version 4 (IMAP4) allows a clientto access and manipulate electronic mail messages on a server. IMAP4permits manipulation of remote message folders, called "mailboxes", in away that is functionally equivalent to local mailboxes. IMAP4 alsoprovides the capability for an offline client to resynchronize with theserver. [STANDARDS-TRACK]1729 Lynch Dec 94 Using the Z39.50 Information Retrieval Protocol in the Internet EnvironmentThis memo describes an approach to the implementation of the ANSI/NISOZ39.50-1992 Standard for Information Retrieval in the TCP/IP environmentwhich is currently in wide use by the Z39.50 implementor community. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.1728 Weider Dec 94 Resource TranspondersThis paper describes an automatic mechanism, the resource transponder,for maintaining resource location information. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1727 Weider Dec 94 A Vision of an Integrated Internet Information ServiceThis paper lays out a vision of how Internet information services mightbe integrated over the next few years, and discusses in some detail whatsteps will be needed to achieve this integration. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.Kennedy Informational [Page 15]RFC 1799 Summary of 1700-1799 January 19971726 Partridge Dec 94 Technical Criteria for Choosing IP The Next Generation (IPng)This RFC specifies criteria related to mobility for consideration indesign and selection of the Next Generation of IP. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1725 Myers Nov 94 Post Office Protocol - Version 3This memo is a revision to RFC 1460, a Draft Standard. [STANDARDS-TRACK]1724 Malkin Nov 94 RIP Version 2 MIB ExtensionThis 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 RIP Version 2. [STANDARDS-TRACK]1723 Malkin Nov 94 RIP Version 2 Carrying Additional InformationThis document specifies an extension of the Routing Information Protocol(RIP), o expand the amount of useful information carried in RIP messagesand to add a measure of security. This memo obsoletes RFC 1388, whichspecifies an update to the "Routing Information Protocol" STD 34, RFC1058. [STANDARDS-TRACK]1722 Malkin Nov 94 RIP Version 2 Protocol Applicability StatementAs required by Routing Protocol Criteria (RFC 1264), this report definesthe applicability of the RIP-2 protocol within the Internet. Thisreport is a prerequisite to advancing RIP-2 on the standards track.[STANDARDS-TRACK]Kennedy Informational [Page 16]RFC 1799 Summary of 1700-1799 January 19971721 Malkin Nov 94 RIP Version 2 Protocol AnalysisAs required by Routing Protocol Criteria (RFC 1264), this reportdocuments the key features of the RIP-2 protocol and the currentimplementation experience. This report is a prerequisite to advancingRIP-2 on the standards track. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1720 IAB Nov 94 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]1719 Gross Dec 94 A Direction for IPng Specification and ImplementationThis RFC specifies criteria related to mobility for consideration indesign and selection of the Next Generation of IP. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1718 IETF Secretariat Nov 94 The Tao of IETF A Guide for New Attendees of the Internet Engineering Task ForceThe purpose of this For Your Information (FYI) RFC is to explain to thenewcomers how the IETF works. This memo provides information for theInternet community. It does not specify an Internet standard. [FYI 17]1717 Sklower Nov 94 The PPP Multilink Protocol (MP)This document proposes a method for splitting, recombining andsequencing datagrams across multiple logical data links. [STANDARDS-TRACK]Kennedy Informational [Page 17]RFC 1799 Summary of 1700-1799 January 19971716 Almquist Nov 94 Towards Requirements for IP RoutersThe goal of this work is to replace RFC-1009, Requirements for InternetGateways ([INTRO:1]) with a new document. It defines and discussesrequirements for devices which perform the network layer forwardingfunction of the Internet protocol suite. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.1715 Huitema Nov 94 The H Ratio for Address Assignment EfficiencyThis document was submitted to the IETF IPng area in response to RFC1550. This memo provides information for the Internet community. Thismemo does not specify an Internet standard of any kind.1714 Williamson Nov 94 Referral Whois Protocol (RWhois)This memo describes version 1.0 of the client/server interaction ofRWhois. RWhois provides a distributed system for the display ofhierarchical information. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1713 Romao Nov 94 Tools for DNS debuggingAlthough widely used (and most of the times unnoticed), DNS (Domain NameSystem) is too much overlooked, in the sense that people, especiallyadministrators, tend to ignore possible anomalies as long asapplications that need name-to-address mapping continue to work. Thisdocument presents some tools available for domain administrators todetect and correct those anomalies. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.1712 Farrell Nov 94 DNS Encoding of Geographical LocationThis document defines the format of a new Resource Record (RR) for theDomain Naming System (DNS), and reserves a corresponding DNS typemnemonic and numerical code. This memo defines an Experimental Protocolfor the Internet community. This memo does not specify an Internetstandard of any kind.Kennedy Informational [Page 18]RFC 1799 Summary of 1700-1799 January 19971711 Houttuin Oct 94 Classifications in E-mail RoutingThis paper presents a classification for e-mail routing issues. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.1710 Hinden Oct 94 Simple Internet Protocol Plus White PaperThis document was submitted to the IETF IPng area in response to RFC1550. This memo provides information for the Internet community. Thismemo does not specify an Internet standard of any kind.1709 Gargano Nov 94 K-12 Internetworking GuidelinesThe K-12 community traditionally has not had this level of staffingavailable for telecommunications planning. This document is intended tobridge that gap and provides a recommended technical direction, anintroduction to the role the Internet now plays in K-12 education andtechnical guidelines for building a campus data communicationsinfrastructure that provides internetworking services and connections tothe Internet. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1708 Gowin Oct 94 NTP PICS PROFORMA For the Network Time Protocol Version 3This RFC describes a PICS Proforma translated into an Internetacceptable form. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1707 McGovern Oct 94 CATNIP: Common Architecture for the InternetThis document was submitted to the IETF IPng area in response to RFC1550. This paper describes a common architecture for the network layerprotocol. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.Kennedy Informational [Page 19]RFC 1799 Summary of 1700-1799 January 19971706 Manning Oct 94 DNS NSAP Resource RecordsThis document defines the format of one new Resource Record (RR) for theDNS for domain name-to-NSAP mapping. The RR may be used with any NSAPaddress format. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1705 Carlson Oct 94 Six Virtual Inches to the Left: The Problem with IPngThis document was submitted to the IETF IPng area in response to RFC1550. This RFC suggests that a new version of TCP (TCPng), and UDP, bedeveloped and deployed. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1704 Haller Oct 94 On Internet AuthenticationThis document describes a spectrum of authentication technologies andprovides suggestions to protocol developers on what kinds ofauthentication might be suitable for some kinds of protocols andapplications used in the Internet. This document provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.1703 Rose Oct 94 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical ProceduresThis memo describes a technique for radio paging using the Internet mailinfrastructure. In particular, this memo focuses on the case in whichradio pagers are identified via the international telephone network.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1702 Hanks Oct 94 Generic Routing Encapsulation over IPv4 networksThis memo addresses the case of using IP as the delivery protocol or thepayload protocol and the special case of IP as both the delivery andpayload. This memo also describes using IP addresses and autonomoussystem numbers as part of a GRE source route. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.Kennedy Informational [Page 20]RFC 1799 Summary of 1700-1799 January 19971701 Hanks Oct 94 Generic Routing Encapsulation (GRE)This document specifies a protocol for performing encapsulation of anarbitrary network layer protocol over another arbitrary network layerprotocol. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1700 Reynolds Oct 94 Assigned NumbersThis RFC is a snapshot of the ongoing process of the assignment ofprotocol parameters for the Internet protocol suite. To make thecurrent information readily available the assignments are kept up-to-date in a set of online text files. This memo is a status report on theparameters (i.e., numbers and keywords) used in protocols in theInternet community.Security Considerations Security issues are not discussed in this memo.Author's Address Mary Kennedy University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: MKENNEDY@ISI.EDUKennedy Informational [Page 21]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -