⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc1599.txt

📁 <VC++网络游戏建摸与实现>源代码
💻 TXT
📖 第 1 页 / 共 3 页
字号:
Network Working Group                                         M. KennedyRequest for Comments: 1599                                           ISICategory: Informational                                     January 1997                      Request for Comments Summary                        RFC Numbers 1500 - 1599Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs from RFC 1500   through RFCs 1599.  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---     ------       ----      -----1599    Kennedy     Jan 96   Requests For Comments SummaryThis memo.1598    Simpson      Mar 94  PPP in X.25The Point-to-Point Protocol (PPP) provides a standard method fortransporting multi-protocol datagrams over point-to-point links.  Thisdocument describes the use of X.25 for framing PPP encapsulated packets.[STANDARDS-TRACK]Kennedy                      Informational                      [Page 1]RFC 1599                  Summary of 1500-1599              January 19971597     Rekhter     Mar 94   Address Allocation for Private InternetsThis RFC describes methods to preserve IP address space by notallocating globally unique IP addresses to hosts private to anenterprise while still permitting full network layer connectivitybetween all hosts inside an enterprise as well as between all publichosts of different enterprises. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1296     Brown       Mar 94   Definitions of Managed Objects                              for Frame Relay ServiceThis memo defines an extension to the Management Information Base (MIB)for use with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing the Frame Relay Service.[STANDARDS-TRACK]1295     Brown       Mar 94   Definitions of Managed Objects                              for the SONET/SDH Interface TypeThis 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 Synchronous OpticalNetwork/Synchronous Digital Hierarchy (SONET/SDH) objects.  Thisdocument is a companion document with Definitions of Managed Objects forthe DS1/E1 and DS3/E3 Interface Types, RFC1406 and RFC1407.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1594     Marine      Mar 94   FYI on Questions and Answers                              Answers to Commonly asked "New Internet                              User" QuestionsThis FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A).The goal is to document the most commonly asked questions and answers inthe Internet. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind. [FYI 4]Kennedy                      Informational                      [Page 2]RFC 1599                  Summary of 1500-1599              January 19971593     McKenzie    Mar 94   SNA APPN Node MIBThis RFC describes IBM's SNMP support for SNA Advanced Peer-to-PeerNetworking (APPN) nodes.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1592      Wijnen     Mar 94   Simple Network Management ProtocolThis RFC describes version 2.0 of a protocol that International BusinessMachines Corporation (IBM) has been implementing in most of its SNMPagents to allow dynamic extension of supported MIBs. This memo definesan Experimental Protocol for the Internet community.  This memo does notspecify an Internet standard of any kind.1591     Postel      Mar 94   Domain Name System Structure and                              DelegationThis memo provides some information on the structure of the names in theDomain Name System (DNS), specifically the top-level domain names; andon the administration of domains. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1590    Postel      Mar 94   Media Type Registration ProcedureSeveral questions have been raised about the requirements andadministrative procedure for registering MIME content-type and subtypes,and the use of these Media Types for other applications.  This documentaddresses these issues and specifies a procedure for the registration ofnew Media Types (content-type/subtypes).  It also generalizes the scopeof use of these Media Types to make it appropriate to use the sameregistrations and specifications with other applications.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1589    Mills       Mar 94   A Kernel Model for Precision TimekeepingThis memorandum describes an engineering model which implements aprecision time-of-day function for a generic operating system. The modelis based on the principles of disciplined oscillators and phase-lockloops (PLL) often found in the engineering literature. This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.Kennedy                      Informational                      [Page 3]RFC 1599                  Summary of 1500-1599              January 19971588    Postel     Feb 94   White Pages Meeting ReportThis report describes the results of a meeting held at the November IETF(Internet Engineering Task Force) in Houston, TX, on November 2, 1993,to discuss the future of and approaches to a white pages directoryservices for the Internet. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1587     Coltun    Mar 94   The OSPF NSSA OptionThis document describes a new optional type of OSPF area, somewhathumorously referred to as a "not-so-stubby" area (or NSSA).  NSSAs aresimilar to the existing OSPF stub area configuration option but have theadditional capability of importing AS external routes in a limitedfashion. [STANDARDS-TRACK]1586     deSouza   Mar 94   Guidelines for Running OSPF                            Over Frame Relay NetworksThis memo specifies guidelines for implementors and users of the OpenShortest Path First (OSPF) routing protocol to bring about improvementsin how the protocol runs over frame relay networks. This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1585     Moy      Mar 94     MOSPF: Analysis and ExperienceThis memo documents how the MOSPF protocol satisfies the requirementsimposed on Internet routing protocols by "Internet Engineering TaskForce internet routing protocol standardization criteria" ([RFC 1264]).This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1584     Moy       Mar 94           Multicast Extensions to OSPFThis memo documents enhancements to the OSPF protocol enabling therouting of IP multicast datagrams. [STANDARDS-TRACK]1583     Moy       Mar 94           OSPF Version 2This memo documents version 2 of the OSPF protocol.  OSPF is a link-state routing protocol. [STANDARDS-TRACK]Kennedy                      Informational                      [Page 4]RFC 1599                  Summary of 1500-1599              January 19971582     Meyer     Feb 94    Extensions to RIP to Support                             Demand CircuitsThis memo defines a generalized modification which can be applied toBellman-Ford (or distance vector) algorithm information broadcastingprotocols. [STANDARDS-TRACK]1581     Meyer     Feb 94    Protocol Analysis for Extensions to RIP                             to Support Demand CircuitsAs required by Routing Protocol Criteria, this report documents the keyfeatures of Routing over Demand Circuits on Wide Area Networks - RIP andthe current implementation experience. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.1580     EARN      Mar 94    Guide to Network Resource ToolsThe purpose of this guide is to supply the basic information that anyoneon the network needs to try out and begin using tools. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind. [FYI 23]1579     Bellovin  Feb 94    Firewall-Friendly FTPThis memo describes a suggested change to the behavior of FTP clientprograms. This document provides information for the Internet community.This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1578     Sellers   Feb 94    FYI on Questions and Answers                             Answers to Commonly Asked "Primary and                             Secondary School Internet User"                             QuestionsThe goal of this FYI RFC is to document the questions most commonlyasked about the Internet by those in the primary and secondary schoolcommunity, and to provide pointers to sources which answer thosequestions. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.  [FYI 22]Kennedy                      Informational                      [Page 5]RFC 1599                  Summary of 1500-1599              January 19971577    Laubach    Jan 94    Classical IP and ARP over ATMThis memo defines an initial application of classical IP and ARP in anAsynchronous Transfer Mode (ATM) network environment configured as aLogical IP Subnetwork (LIS). [STANDARDS-TRACK]1576    Penner     Jan 94    TN3270 Current PracticesThis document describes the existing implementation of transferring 3270display terminal data using currently available telnet capabilities.The name traditionally associated with this implementation is TN3270.This memo provides information for the Internet community.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1575    Hares     Feb 94    An Echo Function for CLNP (ISO 8473)This memo defines an echo function for the connection-less network layerprotocol.  The mechanism that is mandated here is in the final processof being standardized by ISO as "Amendment X: Addition of an Echofunction to ISO 8473" an integral part of Version 2 of ISO 8473.[STANDARDS-TRACK]1574    Hares    Feb 94    Essential Tools for the OSI InternetThis document specifies the following three necessary tools to debugproblems in the deployment and maintenance of networks using ISO 8473(CLNP): ping or OSI Echo function, traceroute function which uses theOSI Echo function, and routing table dump function.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1573    McCloghrie   Jan 94    Evolution of the Interfaces                               Group of MIB-IIThis 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 NetworkInterfaces. [STANARDS-TRACK]Kennedy                      Informational                      [Page 6]RFC 1599                  Summary of 1500-1599              January 19971572    Alexander   Jan 94    Telnet Environment OptionThis document specifies a mechanism for passing environment informationbetween a telnet client and server.  Use of this mechanism enables atelnet user to propagate configuration information to a remote host whenconnecting. [STANDARDS-TRACK]1571   Borman      Jan 94    Telnet Environment Option                             Interoperability IssuesThis document describes a method for allowing implementors to ensurethat their implementation of the Environment option will beinteroperable with as many other implementations as possible, byproviding a set of heuristics that can be used to help identify whichdefinitions for VAR and VALUE are being used by the other side of theconnection. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1570    Simpson     Jan 94    PPP LCP 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.  This documentdefines several additional LCP features which have been suggested overthe past few years. [STANDARDS-TRACK]1569    Rose       Jan 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.1568    Gwinn     Jan 94     Simple Network Paging Protocol                             - Version 1(b)This 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.Kennedy                      Informational                      [Page 7]RFC 1599                  Summary of 1500-1599              January 19971567    Mansfield  Jan 94     X.500 Directory Monitoring MIBThis document defines a portion of the Management Information Base(MIB).  It defines the MIB for monitoring Directory System Agents (DSA),a component of the OSI Directory. This MIB will be used in conjunctionwith the APPLICATION-MIB for monitoring DSAs. [STANDARDS-TRACK]1566    Kille      Jan 94    Mail Monitoring MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, this memo extends the basic Network Services Monitoring MIBto allow monitoring of Message Transfer Agents (MTAs). It may also be

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -