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

📄 rfc1600.txt

📁 著名的RFC文档,其中有一些文档是已经翻译成中文的的.
💻 TXT
📖 第 1 页 / 共 5 页
字号:
      1556 - Handling of Bi-directional Texts in MIME             This is an information document and does not specify any             level of standard.      1555 - Hebrew Character Encoding for Internet Messages             This is an information document and does not specify any             level of standard.Internet Architecture Board                                    [Page 17]RFC 1600                   Internet Standards                 March 1994      1554 - ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP             This is an information document and does not specify any             level of standard.      1553 - Compressing IPX Headers Over WAM Media (CIPX)             A Proposed Standard protocol.      1552 - The PPP Internetworking Packet Exchange Control Protocol             (IPXCP)             A Proposed Standard protocol.      1551 - Novell IPX Over Various WAN Media (IPXWAN)             This is an information document and does not specify any             level of standard.      1550 - IP: Next Generation (IPng) White Paper Solicitation             This is an information document and does not specify any             level of standard.      1549 - PPP in HDLC Framing             A Draft Standard protocol.      1548 - The Point-to-Point Protocol (PPP)             A Draft Standard protocol.      1547 - Requirements for an Internet Standard Point-to-Point             Protocol             This is an information document and does not specify any             level of standard.      1546 - Host Anycasting Service             This is an information document and does not specify any             level of standard.      1545 - FTP Operation Over Big Address Records (FOOBAR)             An Experimental protocol.Internet Architecture Board                                    [Page 18]RFC 1600                   Internet Standards                 March 1994      1544 - The Content-MD5 Header Field             A Proposed Standard protocol.      1543 - Instructions to RFC Authors             This is an information document and does not specify any             level of standard.      1542 - Clarifications and Extensions for the Bootstrap Protocol             A Proposed Standard protocol.      1541 - Dynamic Host Configuration Protocol             A Proposed Standard protocol.6.1.2.  Other Changes:   The following are changes to protocols listed in the previous   edition.      1356 - Multiprotocol Interconnect on X.25 and ISDN in the Packet             Mode             Moved to Draft Standard.      1408 - Telnet Environment Option             Moved to Historic.Internet Architecture Board                                    [Page 19]RFC 1600                   Internet Standards                 March 19946.2.  Standard ProtocolsProtocol   Name                                      Status    RFC STD *========   =====================================     ======== ==== === =--------   Internet Official Protocol Standards      Req      1600   1--------   Assigned Numbers                          Req      1340   2--------   Host Requirements - Communications        Req      1122   3--------   Host Requirements - Applications          Req      1123   3--------   Gateway Requirements                      Req      1009   4IP         Internet Protocol                         Req       791   5            as amended by:----------------     IP Subnet Extension                     Req       950   5--------     IP Broadcast Datagrams                  Req       919   5--------     IP Broadcast Datagrams with Subnets     Req       922   5ICMP       Internet Control Message Protocol         Req       792   5IGMP       Internet Group Multicast Protocol         Rec      1112   5UDP        User Datagram Protocol                    Rec       768   6TCP        Transmission Control Protocol             Rec       793   7TELNET     Telnet Protocol                           Rec   854,855   8FTP        File Transfer Protocol                    Rec       959   9SMTP       Simple Mail Transfer Protocol             Rec       821  10MAIL       Format of Electronic Mail Messages        Rec       822  11CONTENT    Content Type Header Field                 Rec      1049  11NTPV2      Network Time Protocol (Version 2)         Rec      1119  12DOMAIN     Domain Name System                        Rec 1034,1035  13DNS-MX     Mail Routing and the Domain System        Rec       974  14SNMP       Simple Network Management Protocol        Rec      1157  15SMI        Structure of Management Information       Rec      1155  16Concise-MIB Concise MIB Definitions                  Rec      1212  16MIB-II     Management Information Base-II            Rec      1213  17EGP        Exterior Gateway Protocol                 Rec       904  18NETBIOS    NetBIOS Service Protocols                 Ele 1001,1002  19ECHO       Echo Protocol                             Rec       862  20DISCARD    Discard Protocol                          Ele       863  21CHARGEN    Character Generator Protocol              Ele       864  22QUOTE      Quote of the Day Protocol                 Ele       865  23USERS      Active Users Protocol                     Ele       866  24DAYTIME    Daytime Protocol                          Ele       867  25TIME       Time Server Protocol                      Ele       868  26TFTP       Trivial File Transfer Protocol            Ele      1350  33RIP        Routing Information Protocol              Ele      1058  34TP-TCP     ISO Transport Service on top of the TCP   Ele      1006  35[Note: an asterisk at the end of a line indicates a change from theprevious edition of this document.]Internet Architecture Board                                    [Page 20]RFC 1600                   Internet Standards                 March 1994Applicability Statements:   IGMP -- The Internet Architecture Board intends to move towards   general adoption of IP multicasting, as a more efficient solution   than broadcasting for many applications.  The host interface has been   standardized in RFC-1112; however, multicast-routing gateways are in   the experimental stage and are not widely available.  An Internet   host should support all of RFC-1112, except for the IGMP protocol   itself which is optional; see RFC-1122 for more details.  Even   without IGMP, implementation of RFC-1112 will provide an important   advance: IP-layer access to local network multicast addressing.  It   is expected that IGMP will become recommended for all hosts and   gateways at some future date.   SMI, MIB-II SNMP -- The Internet Architecture Board recommends that   all IP and TCP implementations be network manageable.  At the current   time, this implies implementation of the Internet MIB-II (RFC-1213),   and at least the recommended management protocol SNMP (RFC-1157).   RIP -- The Routing Information Protocol (RIP) is widely implemented   and used in the Internet.  However, both implementors and users   should be aware that RIP has some serious technical limitations as a   routing protocol.  The IETF is currently developing several   candidates for a new standard "open" routing protocol with better   properties than RIP.  The IAB urges the Internet community to track   these developments, and to implement the new protocol when it is   standardized; improved Internet service will result for many users.   TP-TCP -- As OSI protocols become more widely implemented and used,   there will be an increasing need to support interoperation with the   TCP/IP protocols.  The Internet Engineering Task Force is formulating   strategies for interoperation.  RFC-1006 provides one interoperation   mode, in which TCP/IP is used to emulate TP0 in order to support OSI   applications.  Hosts that wish to run OSI connection-oriented   applications in this mode should use the procedure described in RFC-   1006.  In the future, the IAB expects that a major portion of the   Internet will support both TCP/IP and OSI (inter-)network protocols   in parallel, and it will then be possible to run OSI applications   across the Internet using full OSI protocol "stacks".Internet Architecture Board                                    [Page 21]RFC 1600                   Internet Standards                 March 19946.3.  Network-Specific Standard ProtocolsAll Network-Specific Standards have Elective status.Protocol   Name                                    State    RFC   STD *========   =====================================   =====   =====  === =IP-ATM     Classical IP and ARP over ATM            Prop   1577       *IP-FR      Multiprotocol over Frame Relay           Draft  1490ATM-ENCAP  Multiprotocol Encapsulation over ATM     Prop   1483IP-TR-MC   IP Multicast over Token-Ring LANs        Prop   1469IP-FDDI    Transmission of IP and ARP over FDDI Net Std    1390    36IP-HIPPI   IP and ARP on HIPPI                      Prop   1374IP-X.25    X.25 and ISDN in the Packet Mode         Draft  1356       *IP-SMDS    IP Datagrams over the SMDS Service       Prop   1209IP-FDDI    Internet Protocol on FDDI Networks       Draft  1188ARP        Address Resolution Protocol              Std     826    37RARP       A Reverse Address Resolution Protocol    Std     903    38IP-ARPA    Internet Protocol on ARPANET             Std BBN1822    39IP-WB      Internet Protocol on Wideband Network    Std     907    40IP-E       Internet Protocol on Ethernet Networks   Std     894    41IP-EE      Internet Protocol on Exp. Ethernet Nets  Std     895    42IP-IEEE    Internet Protocol on IEEE 802            Std    1042    43IP-DC      Internet Protocol on DC Networks         Std     891    44IP-HC      Internet Protocol on Hyperchannel        Std    1044    45IP-ARC     Transmitting IP Traffic over ARCNET Nets Std    1201    46IP-SLIP    Transmission of IP over Serial Lines     Std    1055    47IP-NETBIOS Transmission of IP over NETBIOS          Std    1088    48IP-IPX     Transmission of 802.2 over IPX Networks  Std    1132    49[Note: an asterisk at the end of a line indicates a change from theprevious edition of this document.]Applicability Statements:   It is expected that a system will support one or more physical   networks and for each physical network supported the appropriate   protocols from the above list must be supported.  That is, it is   elective to support any particular type of physical network, and for   the physical networks actually supported it is required that they be   supported exactly according to the protocols in the above list.  See   also the Host and Gateway Requirements RFCs for more specific   information on network-specific ("link layer") protocols.Internet Architecture Board                                    [Page 22]RFC 1600                   Internet Standards                 March 19946.4.  Draft Standard ProtocolsProtocol   Name                                     Status          RFC========   =====================================    ============== =====ISO-TS-ECHO Echo for ISO-8473                       Elective       1575*DECNET-MIB DECNET MIB                               Elective       1559*PPP_HDLC   PPP in HDLC Framing                      Elective       1549*PPP        Point-to-Point Protocol (PPP)            Elective       1548*-------    Message Header Ext. of Non-ASCII Text    Elective       1522MIME       Multipurpose Internet Mail Extensions    Elective       1521802.3-MIB  IEEE 802.3 Repeater MIB                  Elective       1516BRIDGE-MIB BRIDGE-MIB                               Elective       1493ETHER-MIB  Ethernet MIB                             Elective       1398NTPV3      Network Time Protocol (Version 3)        Elective       1305

⌨️ 快捷键说明

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