Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group J. ElliottRequest for Comments: 1399 ISICategory: Informational January 1997Request for Comments Summary RFC Numbers 1300-1399Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 1300 through RFCs 1399. 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--- ------ ---- -----1399 Elliott Jan 97 Requests For Comments SummaryThis memo.1398 Kastenholz Jan 93 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 TCP/IP-based internets. Inparticular, it defines objects for managing ehternet-like objects.[STANDARDS-TRACK]Elliott Informational [Page 1]
RFC 1399 Summary of 1300-1399 January 19971397 Haskin Jan 93 Default Route Advertisement In BGP2 and BGP3 Versions of the Border Gateway ProtocolThis document speficies the recommendation of the BGP Working Group ondefault route advertisement support in BGP2 [1] and BGP3 [2] versions ofthe Border Gateway Protocol. [STANDARDS-TRACK]1396 Crocker Jan 93 The Process for Organization of Internet StandardsThis report provides a summary of the POISED Working Group (WG),starting from the events leading to the formation of the WG to the endof 1992. This memo provides information for the Internet community. Itdoes not specify an Internet standard.1395 Reynolds Jan 93 BOOTP Vendor Information ExtensionsThis RFC is a slight revision and extension ofRFC-1048 by PhilipPrindeville, who should be credited with the original work in this memo.This memo will be updated as additional tags are defined. This editionintroduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16for Swap Server and Tag 17 for Root Path. This memo is a status reporton the vendor information extensions used int the Bootstrap Protocol(BOOTP).1394 Robinson Jan 93 Relationship of Telex Answerback Codes to Internet DomainsThis RFC gives the list, as best known, of all common Internet domainsand the conversion between specific country telex answerback codes andInternet country domain identifiers. It also lists the telex code andinternational dialing code, wherever it is available. It will also listmajor Internet "Public" E-Mail addresses. This memo providesinformation for the Internet community. It does not specify an Internetstandard.1393 Malkin Jan 93 Traceroute Using an IP OptionThis document specifies a new IP option and ICMP message type whichduplicates the functionality of the existing traceroute method whilegenerating fewer packets and completing in a shorter time. This memodefines an Experimental Protocol for the Internet community.Elliott Informational [Page 2]
RFC 1399 Summary of 1300-1399 January 19971392 Malkin Jan 93 Internet Users' GlossaryThere are many networking glossaries in existence. This glossaryconcentrates on terms which are specific to the Internet. This memoprovides information for the Internet community. It does not specify anInternet standard.1391 Malkin Jan 93 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 will give them a warm, fuzzy feelingand enable them to make the meeting more productive for everyone. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1390 Katz Jan 93 Transmission of IP and ARP over FDDI NetworksThis memo defines a method of encapsulating the Internet Protocol (IP)datagrams and Address Resolution Protocol (ARP) requests and replies onFiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK]1389 Malkin Jan 93 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.[STANDARDS-TRACK]1388 Malkin Jan 93 RIP Version 2 Carrying Additional InformationThis document specifies an extension of the Routing Information Protocol(RIP), as defined in [1], to expand the amount of useful informationcarried in RIP packets and to add a measure of security. [STANDARDS-TRACK]Elliott Informational [Page 3]
RFC 1399 Summary of 1300-1399 January 19971387 Malkin Jan 93 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 memo provides information for theInternet community. It does not specify an Internet standard.1386 Cooper Dec 92 The US DomainThis is a description of the US Top Level Domains on the Internet. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1385 Wang Nov 92 EIP: The Extended Internet Protocol A Framework for Maintaining Backward CompatibilityEIP can substantially reduce the amount of modifications needed to thecurrent Internet systems and greatly ease the difficulties oftransition. This is an "idea" paper and discussion is stronglyencouraged on Big-Internet@munnari.oz.au. This memo providesinformation for the Internet community. It does not specify an Internetstandard.1384 Barker Jan 93 Naming Guidelines for Directory PilotsThis document defines a number of naming guidelines. Alignment to theseguidelines is recommended for directory pilots. This memo providesinformation for the Internet community. It does not specify an Internetstandard.1383 Huitema Dec 92 An Experiment in DNS Based IP RoutingPotential solutions to the routing explosion. This memo defines anExperimental Protocol for the Internet community.1382 Throop Nov 92 SNMP MIB Extension for the X.25 Packet LayerThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.[STANDARDS-TRACK]Elliott Informational [Page 4]
RFC 1399 Summary of 1300-1399 January 19971381 Throop Nov 92 SNMP MIB Extension for X.25 LAPBThis 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 the Link Layer of X.25,LAPB. [STANDARDS-TRACK]1380 Gross Nov 92 IESG Deliberations on Routing and AddressingThis memo summarizes issues surrounding the routing and addressingscaling problems in the IP architecture, and it provides a briefbackground of the ROAD group and related activities in the InternetEngineering Task Force (IETF). This memo provides information for theInternet community. It does not specify an Internet standard.1379 Braden Nov 92 Extending TCP for Transactions -- ConceptsThis memo discusses extension of TCP to provide transaction-orientedservice, without altering its virtual-circuit operation. This memoprovides information for the Internet community. It does not specify anInternet standard.1378 Parker Nov 92 The PPP AppleTalk Control Protocol (ATCP)This document defines the NCP for establishing and configuring theAppleTalk Protocol [3] over PPP. [STANDARDS-TRACK]1377 Katz Nov 92 The PPP OSI Network Layer Control Protocol (OSINLCP)This document defines the NCP for establishing and configuring OSINetwork Layer Protocols. [STANDARDS-TRACK]Elliott Informational [Page 5]
RFC 1399 Summary of 1300-1399 January 19971376 Senum Nov 92 The PPP DECnet Phase IV Control Protocol (DNCP)This document defines the NCP for establishing and configuring Digital'sDNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This documentapplies only to DNA Phase IV Routing messages (both data and control),and not to other DNA Phase IV protocols (MOP, LAT, etc.). [STANDARDS-TRACK]1375 Robinson Oct 92 Suggestion for New Classes of IP AddressesThis RFC suggests a change in the method of specifying the IP address toadd new classes of networks to be called F, G, H, and K, to reduce theamount of wasted address space, and to increase the available IP addressnumber space, especially for smaller organizations or classes ofconnectors that do not need or do not want a full Class C IP address.This memo provides information for the Internet community. It does notspecify an Internet standard.1374 Renwick Oct 92 IP and ARP on HIPPIThe ANSI X3T9.3 committee has drafted a proposal for the encapsulationof IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. Another X3T9.3draft describes the operation of HIPPI physical switches. X3T9.3 choseto leave HIPPI networking issues largely outside the scope of theirstandards; this document discusses methods of using of ANSI standardHIPPI hardware and protocols in the context of the Internet, includingthe use of HIPPI switches as LANs and interoperation with othernetworks. This memo is intended to become an Internet Standard.[STANDARDS-TRACK]1373 Tignor Oct 92 PORTABLE DUAsThis document comes in two parts. The first part is for regular peoplewho wish to set up their own DUAs (Directory User Interfaces) to accessthe Directory. The second part is for ISODE-maintainers wishing toprovide portable DUAs to users. This part gives instructions in asimilar but longer, step-by-step format. This memo provides informationfor the Internet community. It does not specify an Internet standard.Elliott Informational [Page 6]
RFC 1399 Summary of 1300-1399 January 19971372 Hedrick Oct 92 Telnet Remote Flow Control OptionThis document specifies an extended version of the Telnet Remote FlowControl Option,RFC 1080, with the addition of the RESTART-ANY andRESTART-XON suboptions. [STANDARDS-TRACK]1371 Gross Oct 92 Choosing a "Common IGP" for the IP Internet (The IESG's Recommendation to the IAB)This memo presents motivation, rationale and other surroundingbackground information leading to the IESG's recommendation to the IABfor a single "common IGP" for the IP portions of the Internet. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1370 I.A.B. Oct 92 Applicability Statement for OSPFThis Applicability Statement places a requirement on vendors claimingconformance to this standard, in order to assure that users will havethe option of deploying OSPF when they need a multivendor, interoperableIGP in their environment. [STANDARDS-TRACK]1369 Kastenholz Oct 92 Implementation Notes and Experience for The Internet Ethernet MIBThis document reflects the currently known status of 11 differentimplementations of the MIB by 7 different vendors on 7 differentEthernet interface chips. This memo provides information for theInternet community. It does not specify an Internet standard.1368 McMaster Oct 92 Definitions of Managed Objects for IEEE 802.3 Repeater DevicesThis 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 IEEE 802.3 10 Mb/secondbaseband repeaters, sometimes referred to as "hubs". [STANDARDS-TRACK]Elliott Informational [Page 7]
RFC 1399 Summary of 1300-1399 January 19971367 Topolcic Oct 92 Schedule for IP Address Space Management GuidelinesThis memo suggests a schedule for the implementation of the IP networknumber allocation plan described inRFC 1366. This memo providesinformation for the Internet community. It does not specify an Internetstandard.1366 Gerich Oct 92 Guidelines for Management of IP Address SpaceThis document has been reviewed by the Federal Engineering Task Force(FEPG) on behalf of the Federal Networking Council (FNC), the co-chairsof the International Engineering Planning Group (IEPG), and the ReseauxIP Europeens (RIPE). There was general consensus by those groups tosupport the recommendations proposed in this document for management ofthe IP address space. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1365 Siyan Spt 92 An IP Address Extension ProposalThis RFC suggests an extension to the IP protocol to solve the shortageof IP address problem, and requests discussion and suggestions forimprovements. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1364 Varadhan Spt 92 BGP OSPF InteractionThis memo defines the various criteria to be used when designingAutonomous System Border Routers (ASBR) that will run BGP with otherASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK]1363 Partridge Spt 92 A Proposed Flow SpecificationThe flow specification defined in this memo is intended for informationand possible experimentation (i.e., experimental use by consentingrouters and applications only). This RFC is a product of the InternetResearch Task Force (IRTF). This memo provides information for theInternet community. It does not specify an Internet standard.Elliott Informational [Page 8]
RFC 1399 Summary of 1300-1399 January 19971362 Allen Spt 92 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. It does notspecify an Internet standard.1361 Mills Aug 92 Simple Network Time Protocol (SNTP)This memorandum describes the Simple Network Time Protocol (SNTP), whichis an adaptation of the Network Time Protocol (NTP) used to synchronizecomputer clocks in the Internet. This memorandum does not obsolete orupdate any RFC. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1360 I.A.B. Spt 92 IAB OFFICIAL PROTOCOL STANDARDSDiscussion of the standardization process and the RFC document series ispresented first, followed by an explanation of the terms. Sections6.2-6.9 contain the lists of protocols in each stage of standardization.Finally come pointers to references and contacts for furtherinformation. [STANDARDS-TRACK]1359 ACM SIGUCCS Aug 92 Connecting to the Internet What Connecting Institutions Should AnticipateThis FYI RFC outlines the major issues an institution should consider inthe decision and implementation of a campus connection to the Internet.This memo provides information for the Internet community. It does notspecify an Internet standard.1358 Chapin Aug 92 Charter of the Internet Architecture Board (IAB)The Internet Architecture Board (IAB) shall be constituted and shalloperate as a technical advisory group of the Internet Society. Thismemo provides information for the Internet community. It does notspecify an Internet standard.Elliott Informational [Page 9]
RFC 1399 Summary of 1300-1399 January 19971357 Cohen Jul 92 A Format for E-mailing Bibliographic RecordsThis memo defines a format for E-mailing bibliographic records oftechnical reports. It is intended to accelerate the dissemination ofinformation about new Computer Science Technical Reports (CS-TR). Thismemo provides information for the Internet community. It does notspecify an Internet standard.1356 Malis Aug 92 Multiprotocol Interconnect on X.25 and ISDN in the Packet ModeThis document specifies the encapsulation of IP and other network layerprotocols over X.25 networks, in accordance and alignment with ISO/IECand CCITT standards. It is a replacement forRFC 877, "A Standard forthe Transmission of IP Datagrams Over Public Data Networks" [1].[STANDARDS-TRACK]1355 Curran Aug 92 Privacy and Accuracy Issues in Network Information Center DatabasesThis document provides a set of guidelines for the administration andoperation of public Network Information Center (NIC) databases. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1354 Baker Jul 92 IP Forwarding Table MIBThis 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 routes in the IP Internet.[STANDARDS-TRACK]1353 McCloghrie Jul 92 Definitions of Managed Objects for Administration of SNMP PartiesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets. Inparticular, it describes a representation of the SNMP parties defined in[8] as objects defined according to the Internet Standard SMI [1].[STANDARDS-TRACK]Elliott Informational [Page 10]
RFC 1399 Summary of 1300-1399 January 19971352 Galvin Jul 92 SNMP Security ProtocolsThe Simple Network Management Protocol (SNMP) specification [1] allowsfor the protection of network management operations by a variety ofsecurity protocols. The SNMP administrative model described in [2]provides a framework for securing SNMP network management. In thecontext of that framework, this memo defines protocols to support thefollowing three security services: data integrity, data originauthentication and data confidentiality. [STANDARDS-TRACK]1351 Davin Jul 92 SNMP Administrative ModelThis memo presents an elaboration of the SNMP administrative model setforth in [1]. This model provides a unified conceptual basis foradministering SNMP protocol entities to support: authenticaiton andintegrity, privacy, access control, and cooperation of protocolentities. [STANDARDS-TRACK]1350 Sollins Jul 92 THE TFTP PROTOCOL (REVISION 2)TFTP is a very simple protocol used to transfer files. It is from thisthat its name comes, Trivial File Transfer Protocol or TFTP. Eachnonterminal packet is acknowledged separately. This document describesthe protocol and its types of packets. The document also explains thereasons behind some of the design decisions. [STANDARDS-TRACK]1349 Almquist Jul 92 Type of Service in the Internet Protocol SuiteThis memo changes and clarifies some aspects of the semantics of theType of Service octet in the Internet Protocol (IP) header.[STANDARDS-TRACK]1348 Manning Jul 92 DNS NSAP RRsThis RFC defines the format of two new Resource Records (RRs) for theDomain Name System (DNS), and reserves corresponding DNS type mnemonicand numerical codes. This memo defines an Experimental Protocol for theInternet community.Elliott Informational [Page 11]
RFC 1399 Summary of 1300-1399 January 19971347 Callon Jun 92 TCP and UDP with bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and RoutingThis paper describes a simple proposal which provides a long-termsolution to Internet addressing, routing, and scaling. This memoprovides information for the Internet community. It does not specify anInternet standard.1346 Jones Jun 92 Resource Allocation, Control, and Accounting for the Use of Network ResourcesThe purpose of this RFC is to focus discussion on particular challengesin large service networks in general, and the International IP Internetin particular. No solution discussed in this document is intended as astandard. Rather, it is hoped that a general consensus will emerge asto the appropriate solutions, leading eventually to the adoption ofstandards. This memo provides information for the Internet community.It does not specify an Internet standard.1345 Simonsen Jun 92 Character Mnemonics & Character SetsThis memo lists a selection of characters and their presence in somecoded character sets. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1344 Borenstein Jun 92 Implicaitons of MIME for Internet Mail GatewaysWhile MIME was carefully designed so that it does not require anychanges to Internet electronic message transport facilities, there areseveral ways in which message transport systems may want to takeadvantage of MIME. These opportunities are the subject of this memo.This memo provides information for the Internet community. It does notspecify an Internet standard.1343 Borenstein Jun 92 A User Agent Configuration Mechanism For Multimedia Mial Format InformationThis memo suggests a file format to be used to inform multiple mailreading user agent programs about the locally-installed facilities forhandling mail in various formats. This memo provides information forthe Internet community. It does not specify an Internet standard.Elliott Informational [Page 12]
RFC 1399 Summary of 1300-1399 January 19971342 Moore Jun 92 Representation of Non-ASCII Text in Internet Message HeadersThis memo describes an extension to the message format defined in [1](known to the IETF Mail Extensions Working Group as "RFC 1341"), toallow the representation of character sets other than ASCII inRFC 822message headers. [STANDARDS-TRACK]1341 Borenstein Jun 92 MIME: Mechanisms for Specifying and Describing the Format of Internet Message BodiesThis document redefines the format of message bodies to allow multi-parttextual and non-textual message bodies to be represented and exchangedwithout loss of information. [STANDARDS-TRACK]1340 Reynolds Jul 92 ASSIGNED NUMBERSThis Network Working Group Request for Comments documents the currentlyassigned values from several series of numbers used in network protocolimplementations. This memo is a status report on the parameters (i.e.,numbers and keywords) used in protocols in the Internet community.1339 Dorner Jun 92 Remote Mail Checking ProtocolThis RFC defines a protocol to provide a mail checking service to beused between a client and server pair. Typically, a small program on aclient workstation would use the protocol to query a server in order tofind out whether new mail has arrived for a specified user. This memodefines an Experimental Protocol for the Internet community.1338 Fuller Jun 92 Supernetting: an Address Assignment and Aggregation StrategyThis memo discusses strategies for address assignment of the existing IPaddress space with a view to conserve the address space and stem theexplosive growth of routing tables in default-route-free routers run bytransit routing domain providers. This memo provides information forthe Internet community. It does not specify an Internet standard.Elliott Informational [Page 13]
RFC 1399 Summary of 1300-1399 January 19971337 Braden May 92 TIME-WAIT Assassination Hazards in TCPThis note describes some theoretically-possible failure modes for TCPconnections and discusses possible remedies. In particular, one verysimple fix is identified. This memo provides information for theInternet community. It does not specify an Internet standard.1336 Malkin May 92 Who's Who in the Internet Biographies of IAB, IESG and IRSG MembersThis FYI RFC contains biographical information about members of theInternet Activities Board (IAB), the Internet Engineering Steering Group(IESG) of the Internet Engineering Task Force (IETF), and the theInternet Research Steering Group (IRSG) of the Internet Research TaskForce (IRTF). This memo provides information for the Internetcommunity. It does not specify any standard.1335 Wang May 92 A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space ExhaustionThis RFC presents a solution to problem of address space exhaustion inthe Internet. It proposes a two-tier address structure for theInternet. This is an "idea" paper and discussion is stronglyencouraged. This memo provides information for the Internet community.It does not specify an Internet standard.1334 Lloyd Oct 92 PPP Authentication ProtocolsThis document defines two protocols for Authentication: the PasswordAuthentication Protocol and the Challenge-Handshake AuthenticationProtocol. [STANDARDS-TRACK]1333 Simpson May 92 PPP Link Quality MonitoringThe Point-to-Point Protocol (PPP) [1] provides a standard method ofencapsulating Network Layer protocol information over point-to-pointlinks. PPP also defines an extensible Link Control Protocol, whichallows negotiation of a Quality Protocol for continuous monitoring ofthe viability of the link. [STANDARDS-TRACK]Elliott Informational [Page 14]
RFC 1399 Summary of 1300-1399 January 19971332 McGregor May 92 The PPP Internet Protocol Control Protocol (IPCP)The Point-to-Point Protocol (PPP) [1] provides a standard method ofencapsulating Network Layer protocol information over point-to-pointlinks. PPP also defines an extensible Link Control Protocol, andproposes a family of Network Control Protocols (NCPs) for establishingand configuring different network-layer protocols. [STANDARDS-TRACK]1331 Simpson May 92 The Point-to-Point Protocol (PPP> for the Transmission of Multi-protocol Datagrams over Point-to-Point LinksThis document defines the PPP encapsulation scheme, together with thePPP Link Control Protocol (LCP), an extensible option negotiationprotocol which is able to negotiate a rich assortment of configurationparameters and provides additional management functions. [STANDARDS-TRACK]1330 E.S.C.C. May 92 Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services <X.400) within the ESnet CommunityThis RFC is a near verbatim copy of the whitepaper produced by the ESnetSite Coordinating Committee's X.500/X.400 Task Force. This memoprovides information for the Internet community. It does not specify anInternet standard.1329 Kuehn May 92 Thoughts on Address Resolution for Dual MAC FDDI NetworksIn this document an idea is submitted how IP and ARP can be used oninhomogeneous FDDI networks (FDDI networks with single MAC and dual MACstations) by introducing a new protocol layer in the protocol suite ofthe dual MAC stations. This memo provides information for the Internetcommunity. It does not specify an Internet standard.Elliott Informational [Page 15]
RFC 1399 Summary of 1300-1399 January 19971328 Kille May 92 X.400 1988 to 1984 downgradingThis document considers issues of downgrading from X.400(1988) toX.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies somedowngrading rules [MHS88b], but these are not sufficient for provisionof service in an environment containing both 1984 and 1988 components.This document defines a number of extensions to this annexe.[STANDARDS-TRACK]1327 Kille May 92 Mapping between X.400(1988) / ISO 10021 andRFC 822This document specifies a mapping between two protocols. Thisspecification should be used when this mapping is performed on the DARPAInternet or in the UK Academic Community. This specification may bemodified in the light of implementation experience, but no substantialchanges are expected. [STANDARDS-TRACK]1326 Tsuchiya May 92 Mutual Encapsulation Considered DangerousThis memo describes a packet explosion problem that can occur withmutual encapsulation of protocols (A encapsulates B and B encapsulatesA). This memo provides information for the Internet community. It doesnot specify an Internet standard.1325 Malkin May 92 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),produced by the User Services Working Group of the Internet EngineeringTask Force (IETF). The goal is to document the most commonly askedquestions and answers in the Internet. This memo provides informationfor the Internet community. It does not specify an Internet standard.Elliott Informational [Page 16]
RFC 1399 Summary of 1300-1399 January 19971324 Reed May 92 A Discussion on Computer Network ConferencingThis memo is intended to make more people aware of the presentdevelopments in the Computer Conferencing field as well as put forwardideas on what should be done to formalize this work so that there is acommon standard for programmers and others who are involved in thisfield to work with. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1323 Jacobson May 92 TCP Extensions for High PerformanceThis memo presents a set of TCP extensions to improve performance overlarge bandwidth*delay product paths and to provide reliable operationover very high-speed paths. It defines new TCP options for scaledwindows and timestamps, which are designed to provide compatibleinterworking with TCP's that do not implement the extensions.[STANDARDS-TRACK]1322 Estrin May 92 A Unified Approach to Inter-Domain RoutingThis memo is an informational RFC which outlines one potential approachfor inter-domain routing in future global internets. This memo providesinformation for the Internet community. It does not specify an Internetstandard.1321 Rivest Apr 92 The MD5 Message-Digest AlgorithmThis document describes the MD5 message-digest algorithm. The algorithmtakes as input a message of arbitrary length and produces as output a128-bit "fingerprint" or "message digest" of the input. This memoprovides information for the Internet community. It does not specify anInternet standard.1320 Rivest Apr 92 The MD4 Message-Digest AlgorithmThis document describes the MD4 message-digest algorithm [1]. Thealgorithm takes as input a message of arbitrary length and produces asoutput a 128-bit "fingerprint" or "message digest" of the input. Thismemo provides information for the Internet community. It does notspecify an Internet standard.Elliott Informational [Page 17]
RFC 1399 Summary of 1300-1399 January 19971319 Kaliski Apr 92 The MD2 Message-Digest AlgorithmThis document describes the MD2 message-digest algorithm. The algorithmtakes as input a message of arbitrary length and produces as output a128-bit "fingerprint" or "message digest" of the input. This memoprovides information for the Internet community. It does not specify anInternet standard.1318 Stewart Apr 92 Definitions of Managed Objects for Parallel-printer-like Hardware DevicesThis 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 the management of parallel-printer-like devices. [STANDARDS-TRACK]1317 Stewart Apr 92 Definitions of Managed Objects for RS-232-like Hardware DevicesThis 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 the management of RS-232-likedevices. [STANDARDS-TRACK]1316 Stewart Apr 92 Definitions of Managed Objects for Character Stream DevicesThis 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 the management of character streamdevices. [STANDARDS-TRACK]1315 Brown Apr 92 Management Information Base for Frame Relay DTEsThis 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 Frame Relay. [STANDARDS-TRACK]Elliott Informational [Page 18]
RFC 1399 Summary of 1300-1399 January 19971314 Katz Apr 92 A File Format for the Exchange of Images in the InternetThis document defines a standard file format for the exchange of fax-like black and white images within the Internet. [STANDARDS-TRACK]1313 Partridge Apr 92 Today's Programming for KRFC AM 1313 Internet Talk RadioHi and welcome to KRFC Internet Talk Radio, your place on the AM dialfor lively talk and just-breaking news on internetworking. This memoprovides information for the Internet community. It does not specify anInternet standard.1312 Nelson Apr 92 Message Send Protocol 2The Message Send Protocol is used to send a short message to a givenuser on a given terminal on a given host. This memo defines anExperimental Protocol for the Internet community.1311 Postel Mar 92 Introduction to the STD NotesThe STDs are a subseries of notes within the RFC series that are theInternet standards. The intent is to identify clearly for the Internetcommunity those RFCs which document Internet standards. [STANDARDS-TRACK]1310 I.A.B. Mar 92 The Internet Standards ProcessThis memo documents the process currently used for the standardizationof Internet protocols and procedures. [STANDARDS-TRACK]1309 Weider Mar 92 Technical Overview of Directory Services Using the X.500 ProtocolThis document is an overview of the X.500 standard for people notfamiliar with the technology. It compares and contrasts DirectoryServices based on X.500 with several of the other Directory servicescurrently in use in the Internet. This paper also describes the statusof the standard and provides references for further information on X.500implementations and technical information. This memo providesinformation for the Internet community. It does not specify an Internetstandard.Elliott Informational [Page 19]
RFC 1399 Summary of 1300-1399 January 19971308 Weider Mar 92 Executive Introduction to Directory Services Using the X.500 ProtocolThis document is an Executive Introduction to Directory Services usingthe X.500 protocol. It briefly discusses the deficiencies in currentlydeployed Internet Directory Services, and then illustrates the solutionsprovided by X.500. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1307 Young Mar 92 Dynamically Switched Link Control ProtocolThis memo describes an experimental protocol developed by a project teamat Cray Research, Inc., in implementing support for circuit-switched T3services. The protocol is used for the control of network connectionsexternal to a host, but known to the host. This memo defines anExperimental Protocol for the Internet community.1306 Nicholson Mar 92 Experiences Supporting By-Request Circuit-Switched T3 NetworksThis memo describes the experiences of a project team at Cray Research,Inc., in implementing support for circuit-switched T3 services. Whilethe issues discussed may not be directly relevant to the researchproblems of the Internet, they may be interesting to a number ofresearchers and implementers. This RFC provides information for theInternet community. It does not specify an Internet standard.1305 Mills Mar 92 Network Time Protocol (Version 3): Specification, Implementation and AnalysisThis document describes the Network Time Protocol (NTP), specifies itsformal structure and summarizes information useful for itsimplementation. [STANDARDS-TRACK]1304 Cox Feb 92 Definitions of Managed Objects for the SIP 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 SIP (SMDS InterfaceProtocol) objects. [STANDARDS-TRACK]Elliott Informational [Page 20]
RFC 1399 Summary of 1300-1399 January 19971303 McCloghrie Feb 92 A Convention for Describing SNMP-based AgentsThis memo suggests a straight-forward approach towards describing SNMP-based agents. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1302 Sitzler Feb 92 Building a Network Information Services InfrastructureThis FYI RFC document is intended for existing Internet NetworkInformation Center (NIC) personnel, people interested in establishing anew NIC, Internet Network Operations Centers (NOCs), and fundingagencies interested in contributing to user support facilities. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1301 Armstrong Feb 92 Multicast Transport ProtocolThis memo describes a protocol for reliable transport that utilizes themulticast capability of applicable lower layer networking architectures.The transport definition permits an arbitrary number of transportproviders to perform realtime collaborations without requiringnetworking clients (aka, applications) to possess detailed knowledge ofthe population or geographical dispersion of the participating members.It is not network architectural specific, but does implicitly requiresome form of multicasting (or broadcasting) at the data link level, aswell as some means of communicating that capability up through thelayers to the transport. This memo provides information for theInternet community. It does not specify an Internet standard.1300 Greenfield Feb 92 Remembrances of Things PastPoem. This memo provides information for the Internet community. Itdoes not specify an Internet standard.Elliott Informational [Page 21]
RFC 1399 Summary of 1300-1399 January 1997Security 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 22]
[8]ページ先頭