📄 rfc1699.txt
字号:
RFC 1699 Summary of 1600-1699 January 19971667 Symington Aug 94 Modeling and Simulation Requirements for IPngThis white paper summarizes the Distributed Interactive Simulationenvironment that is under development, with regard to its real-timenature, scope and magnitude of networking requirements. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1666 Kielczewski Aug 94 Definitions of Managed Objects for SNA NAUs 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 the configuration,monitoring and control of Physical Units (PUs) and Logical Units (LUs)in an SNA environment. [STANDARDS-TRACK]1665 Kielczewski Jul 94 Definitions of Managed Objects for SNA NAUs 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 the configuration,monitoring and control of Physical Units (PUs) and Logical Units (LUs)in an SNA environment. [STANDARDS-TRACK]1664 Allocchio Aug 94 Using the Internet DNS to Distribute RFC1327 Mail Address Mapping TablesThis memo defines how to store in the Internet Domain Name System themapping information needed by e-mail gateways and other tools to mapRFC822 domain names into X.400 O/R names and vice versa. This memodefines an Experimental Protocol for the Internet community.1663 Rand Jul 94 PPP Reliable TransmissionThis document defines a method for negotiating and using Numbered-Mode,as defined by ISO 7776 [2], to provide a reliable serial link.[STANDARDS-TRACK]Elliott Informational [Page 8]RFC 1699 Summary of 1600-1699 January 19971662 Simpson Jul 94 PPP in HDLC-Like FramingThis document describes the use of HDLC-like framing for PPPencapsulated packets. [STANDARDS-TRACK]1661 Simpson Jul 94 The Ponit-to-Point Protocol (PPP)This document defines the PPP organization and methodology, and the PPPencapsulation, together with an extensible option negotiation mechanismwhich is able to negotiate a rich assortment of configuration parametersand provides additional management functions. [STANDARDS-TRACK]1660 Stewart Jul 94 Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2This memo defines an extension to the Management Information Base (MIB)for use with network management protocols in the Internet community. Inparticular, it defines objects for the management of Parallel-printer-like devices. [STANDARDS-TRACK]1659 Stewart Jul 94 Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2This memo defines an extension to the Management Information Base (MIB)for use with network management protocols in the Internet community. Inparticular, it defines objects for the management of RS-232-likedevices. [STANDARDS-TRACK]1658 Stewart Jul 94 Definitions of Managed Objects for Character Stream Devices using SMIv2This memo defines an extension to the Management Information Base (MIB)for use with network management protocols in the Internet community. Inparticular, it defines objects for the management of character streamdevices. [STANDARDS-TRACK]Elliott Informational [Page 9]RFC 1699 Summary of 1600-1699 January 19971657 Willis Jul 94 Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) 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 the BorderGateway Protocol Version 4 or lower [1, 2]. [STANDARDS-TRACK]1656 Traina Jul 94 BGP-4 Protocol Document Roadmap and Implementation ExperienceBorder Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous Systemrouting protocol. It is built on experience gained with BGP as definedin RFC-1267 [2] and BGP usage in the connected Internet as described inRFC-1268 [3]. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1655 Rekhter Jul 94 Application of the Border Gateway Protocol in the InternetThis document, together with its companion document, "A Border GatewayProtocol 4 (BGP-4)", define an inter-autonomous system routing protocolfor the Internet. [STANDARDS-TRACK]1654 Rekhter Jul 94 A Border Gateway Protocol 4 (BGP-4)This document defines an inter-autonomous system routing protocol forthe Internet. [STANDARDS-TRACK]1653 Klensin Jul 94 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]Elliott Informational [Page 10]RFC 1699 Summary of 1600-1699 January 19971652 Klensin Jul 94 SMTP Service Extension for 8bit-MIMEtransportThis memo defines an extension to the SMTP service whereby an SMTPcontent body consisting of text containing octets outside of the US-ASCII octet range (hex 00-7F) may be relayed using SMTP. [STANDARDS-TRACK]1651 Klensin Jul 94 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]1650 Kastenholz Aug 94 Definitions of Managed Objects for the Ethernet-like Interface Types 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 ethernet-like objects.[STANDARDS-TRACK]1649 Hagens Jul 94 Operational Requirements for X.400 Management Domains in the GO-MHS CommunityThe goal of this document is to unite regionally operated X.400 serviceson the various continents into one GO-MHS Community (as seen from anend-user's point of view). This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1648 Cargille Jul 94 Postmaster Convention for X.400 OperationsThis paper extends this concept to X.400 mail domains which haveregistered RFC 1327 mapping rules, and which therefore appear to havenormal RFC822-style addresses. [STANDARDS-TRACK]Elliott Informational [Page 11]RFC 1699 Summary of 1600-1699 January 19971647 Kelly Jul 94 TN3270 EnhancementsThis document describes a protocol that more fully supports 3270 devicesthan do the existing tn3270 practices. [STANDARDS-TRACK]1646 Graves Jul 94 TN3270 Extensions for LUname and Printer SelectionThis document describes protocol extensions to TN3270. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1645 Gwinn Jul 94 Simple Network Paging Protocol - Version 2This RFC suggests a simple way for delivering both alphanumeric andnumeric pages (one-way) to radio paging terminals. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1644 Braden Jul 94 T/TCP -- TCP Extensions for Transactions Functional SpecificationThis memo specifies T/TCP, an experimental TCP extension for efficienttransaction-oriented (request/response) service. This memo describes anExperimental Protocol for the Internet community.1643 Kastenholz Jul 94 Definitions of Managed Objects for the Ethernet-like Interface TypesThis 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 ethernet-like objects.[STANDARDS-TRACK]1642 Goldsmith Jul 94 A Mail-Safe Transformation Format of UnicodeThis document describes a new transformation format of Unicode thatcontains only 7-bit ASCII characters and is intended to be readable byhumans in the limiting case that the document consists of charactersfrom the US-ASCII repertoire. This memo defines an ExperimentalProtocol for the Internet community.Elliott Informational [Page 12]RFC 1699 Summary of 1600-1699 January 19971641 Goldsmith Jul 94 Using Unicode with MIMEThis document specifies the usage of Unicode within MIME. This memodefines an Experimental Protocol for the Internet community.1640 Crocker Jun 94 The Process for Organization of Internet Standards Working Group (POISED)This report, originally prepared in January 1993 provides a summary ofthe POISED WG, starting from the events leading to the formation of theWG to the end of 1992. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1639 Piscitello Jun 94 FTP Operation Over Big Address Records (FOOBAR)This RFC specifies a method for assigning addresses other than 32-bitIPv4 addresses to data ports through the specification of a "long Port(LPRT)" command and "Long Passive (LPSV)" reply, each having as itsargument a <long-host-port>, which allows for additional addressfamilies, variable length network addresses and variable length portnumbers. This memo defines an Experimental Protocol for the Internetcommunity.1638 Baker Jun 94 PPP Bridging Control Protocol (BCP)This document defines the Network Control Protocol for establishing andconfiguring Remote Bridging for PPP links. [STANDARDS-TRACK]1637 Manning Jun 94 DNS NSAP Resource RecordsThis document defines the format of one new Resource Record (RR) for theDNS for domain name-to-NSAP mapping. This memo defines an ExperimentalProtocol for the Internet community.Elliott Informational [Page 13]RFC 1699 Summary of 1600-1699 January 19971636 Braden Jun 94 Report of IAB Workshop on Security in the Internet ArchitectureThis document is a report on an Internet architecture workshop,initiated by the IAB and held at USC Information Sciences Institute onFebruary 8-10, 1994. This workshop generally focused on security issuesin the Internet architecture. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1635 Deutsch May 94 How to Use Anonymous FTPThis document provides information for the novice Internet user aboutusing the File Transfer Protocol (FTP). It explains what FTP is, whatanonymous FTP is, and what an anonymous FTP archive site is. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1634 Allen May 94 Novell IPX Over Various WAN Media (IPXWAN)This document describes how Novell IPX operates over various WAN media.Specifically, it describes the common "IPX WAN" protocol Novell uses toexchange necessary router to router information prior to exchangingstandard IPX routing information and traffic over WAN datalinks. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.1633 Braden Jun 94 Integrated Services in the Internet Architecture: an OverviewThis memo discusses a proposed extension to the Internet architectureand protocols to provide integrated services, i.e., to support real-timeas well as the current non-real-time service of IP. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.Elliott Informational [Page 14]RFC 1699 Summary of 1600-1699 January 1997
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -