📄 rfc2399.txt
字号:
2364 Gross Jul 1998 PPP Over AAL5This document describes the use of ATM Adaptation Layer 5 (AAL5) forframing PPP encapsulated packets. [STANDARDS-TRACK]2363 Gross Jul 1998 PPP Over FUNIThis document describes the use of ATM Frame User Network Interface(FUNI) for framing PPP encapsulated packets. [STANDARDS-TRACK]Ramos Informational [Page 8]RFC 2399 Summary of 2300-2399 January 19992362 Estrin Jun 1998 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol SpecificationThis document describes a protocol for efficiently routing to multicastgroups that may span wide-area (and inter-domain) internets. This memodefines an Experimental Protocol for the Internet community. It doesnot specify an Internet standard of any kind. Discussion andsuggestions for improvement are requested.2361 Fleischman Jun 1998 WAVE and AVI Codec RegistriesThe purpose of this paper is to establish a mechanism by which codecsregistered within Microsoft's WAVE and AVI Registries may be referencedwithin the IANA Namespace by Internet applications. This memo providesinformation for the Internet community. It does not specify an Internetstandard of any kind.2360 Scott Jun 1998 Guide for Internet Standards WritersThis document is a guide for Internet standard writers. It definesthose characteristics that make standards coherent, unambiguous, andeasy to interpret. This document specifies an Internet Best CurrentPractices for the Internet Community, and requests discussion andsuggestions for improvements.2359 Myers Jun 1998 IMAP4 UIDPLUS extensionThe UIDPLUS extension of the Internet Message Access Protocol [IMAP4]provides a set of features intended to reduce the amount of time andresources used by some client operations. [STANDARDS-TRACK]2358 Flick Jun 1998 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. Thismemo obsoletes RFC 1650 "Definitions of Managed Objects for theEthernet-like Interface Types using SMIv2". This memo extends thatspecification by including management information useful for themanagement of 100 Mb/s Ethernet interfaces. [STANDARDS-TRACK]Ramos Informational [Page 9]RFC 2399 Summary of 2300-2399 January 19992357 Mankin Jun 1998 IETF Criteria for Evaluating Reliable Multicast Transport and Application ProtocolsThis memo describes the procedures and criteria for reviewing reliablemulticast protocols within the Transport Area (TSV) of the IETF. Withintoday's Internet, important applications exist for a reliable multicastservice. This memo provides information for the Internet community. Itdoes not specify an Internet standard of any kind.2356 Montenegro Jun 1998 Sun's SKIP Firewall Traversal for Mobile IPThe Mobile IP specification establishes the mechanisms that enable amobile host to maintain and use the same IP address as it changes itspoint of attachment to the network. The mechanisms described in thisdocument allow a mobile node out on a public sector of the internet tonegotiate access past a SKIP firewall, and construct a secure channelinto its home network. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.2355 Kelly Jun 1998 TN3270 EnhancementsThis document describes a protocol that more fully supports 3270 devicesthan do traditional tn3270 practices. [STANDARDS-TRACK]2354 Perkins Jun 1998 Options for Repair of Streaming MediaThis document summarizes a range of possible techniques for the repairof continuous media streams subject to packet loss. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.2353 Dudley May 1998 APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages DocumentThis memo defines a method with which HPR nodes can use IP networks forcommunication, and the enhancements to APPN required by this method.This memo also describes an option set that allows the use of the APPNconnection network model to allow HPR nodes to use IPRamos Informational [Page 10]RFC 2399 Summary of 2300-2399 January 1999networks for communication without having to predefine link connections.This memo provides information for the Internet community. It does notspecify an Internet standard of any kind.2352 Vaughan May 1998 A Convention For Using Legal Names as Domain NamesThe purpose of this memo is to focus discussion on the particularproblems with the exhaustion of the top level domain space in theInternet and the possible conflicts that can occur when multipleorganisations are vying for the same name. This memo providesinformation for the Internet community. It does not specify an Internetstandard of any kind.2351 Robert May 1998 Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IPThis memo specifies a protocol for the encapsulation of the airlinespecific protocol over IP. This memo provides information for theInternet community. It does not specify an Internet standard of anykind.2250 Brownlee Jun 1998 Expectations for Computer Security Incident ResponseThe purpose of this document is to express the general Internetcommunity's expectations of Computer Security Incident Response Teams(CSIRTs). It is not possible to define a set of requirements that wouldbe appropriate for all teams, but it is possible and helpful to list anddescribe the general set of topics and issues which are of concern andinterest to constituent communities. This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.2349 Malkin May 1998 TFTP Timeout Interval and Transfer Size OptionsThe Trivial File Transfer Protocol is a simple, lock-step, file transferprotocol which allows a client to get or put a file onto a remote host.This document describes two TFTP options. [STANDARDS-TRACK]Ramos Informational [Page 11]RFC 2399 Summary of 2300-2399 January 19992348 Malkin May 1998 TFTP Blocksize OptionThe Trivial File Transfer Protocol is a simple, lock-step, file transferprotocol which allows a client to get or put a file onto a remote host.This document describes a TFTP option which allows the client and serverto negotiate a blocksize more applicable to the network medium.[STANDARDS-TRACK]2347 Malkin May 1998 TFTP Option ExtensionThe Trivial File Transfer Protocol is a simple, lock-step, file transferprotocol which allows a client to get or put a file onto a remote host.This document describes a simple extension to TFTP to allow optionnegotiation prior to the file transfer. [STANDARDS-TRACK]2346 Palme May 1998 Making Postscript and PDF InternationalCertain text formats, for example Postscript (MIME-Type:application/postscript; file extension .ps) and Portable Document Format(MIME-Type: application/pdf; file extension .pdf) specify exactly thepage layout of the printed document. The commonly used paper format isdifferent in North America and the rest of the world. North Americauses the 'Letter' format, while the rest of the world mostly uses theISO-standard 'A4' format. This means that documents formatted on onecontinent may not be easily printable on another continent. This memogives advice on how to produce documents which are equally wellprintable with the Letter and the A4 formats. This memo providesinformation for the Internet community. It does not specify an Internetstandard of any kind.2345 Klensin May 1998 Domain Names and Company Name RetrievalThis document proposes a company name to URL mapping service based onthe oldest and least complex of Internet directory protocols, whois, inorder to explore whether an extremely simple and widely-deployedprotocol can succeed where more complex and powerful options have failedor been excessively delayed. This memo defines an Experimental Protocolfor the Internet community. It does not specify an Internet standard ofany kind. Discussion and suggestions for improvement are requested.Ramos Informational [Page 12]RFC 2399 Summary of 2300-2399 January 19992344 Montenegro May 1998 Reverse Tunneling for Mobile IPThis document proposes backwards-compatible extensions to Mobile IP inorder to support topologically correct reverse tunnels. [STANDARDS-TRACK]2343 Civanlar May 1998 RTP Payload Format for Bundled MPEGThis document describes a payload type for bundled, MPEG-2 encoded videoand audio data that may be used with RTP, version 2. This memo definesan Experimental Protocol for the Internet community. This memo does notspecify an Internet standard of any kind. Discussion and suggestionsfor improvement are requested.2342 Gahrns May 1998 IMAP4 NamespaceThis document defines a NAMESPACE command that allows a client todiscover the prefixes of namespaces used by a server for personalmailboxes, other users' mailboxes, and shared mailboxes. [STANDARDS-TRACK]2341 Valencia May 1998 Cisco Layer Two Forwarding (Protocol) "L2F"This document describes the Layer Two Forwarding protocol (L2F) whichpermits the tunneling of the link layer (i.e., HDLC, async HDLC, or SLIPframes) of higher level protocols. This memo describes a historicprotocol for the Internet community. It does not specify an Internetstandard of any kind.2340 Jamoussi May 1998 Nortel's Virtual Network Switching (VNS) OverviewThis document provides an overview of Virtual Network Switching (VNS).This memo provides information for the Internet community. It does notspecify an Internet standard of any kind.Ramos Informational [Page 13]RFC 2399 Summary of 2300-2399 January 19992339 ISOC May 1998 An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 ProtocolsThis Request for Comments records an agreement between Sun Microsystems,Inc. and the Internet Society to permit the flow of Sun's Network FileSystem specifications into the Internet Standards process conducted bythe Internet Engineering Task Force. This memo provides information forthe Internet community. It does not specify an Internet standard of anykind.2338 Knight Apr 1998 Virtual Router Redundancy ProtocolThis memo defines the Virtual Router Redundancy Protocol (VRRP). VRRPspecifies an election protocol that dynamically assigns responsibilityfor a virtual router to one of the VRRP routers on a LAN. [STANDARDS-TRACK]2337 Farinacci Apr 1998 Intra-LIS IP multicast among routers over ATM using Sparse Mode PIMThis document describes how intra-LIS IP multicast can be efficientlysupported among routers over ATM without using the Multicast AddressResolution Server (MARS). This memo defines an Experimental Protocolfor the Internet community. It does not specify an Internet standard ofany kind. Discussion and suggestions for improvement are requested.2336 Luciani Jul 1998 Classical IP and ARP over ATM to NHRP TransitionThis document describes methods and procedures for the gracefultransition from an ATMARP LIS to an NHRP LIS network model over ATM.This memo provides information for the Internet community. It does notspecify an Internet standard of any kind.2335 Luciani Apr 1998 A Distributed NHRP Service Using SCSPThis document describes a method for distributing an NHRP service withina LIS. [STANDARDS-TRACK]Ramos Informational [Page 14]RFC 2399 Summary of 2300-2399 January 19992334 Luciani Apr 1998 Server Cache Synchronization Protocol (SCSP)This document describes the Server Cache Synchronization Protocol (SCSP)and is written in terms of SCSP's use within Non Broadcast MultipleAccess (NBMA) networks; although, a somewhat straight forward usage isapplicable to BMA networks. [STANDARDS-TRACK]2333 Cansever Apr 1998 NHRP Protocol Applicability StatementAs required by the Routing Protocol Criteria [RFC 1264], this memodiscusses the applicability of the Next Hop Resolution Protocol (NHRP)in routing of IP datagrams over Non-Broadcast Multiple Access (NBMA)networks, such as ATM, SMDS and X.25. [STANDARDS-TRACK]2332 Luciani Apr 1998 NBMA Next Hop Resolution Protocol (NHRP)This document describes the NBMA Next Hop Resolution Protocol (NHRP).NHRP can be used by a source station (host or router) connected to aNon-Broadcast, Multi-Access (NBMA) subnetwork to determine theinternetworking layer address and NBMA subnetwork addresses of the "NBMAnext hop" towards a destination station. [STANDARDS-TRACK]2331 Maher Apr 1998 ATM Signalling Support for IP over ATM - UNI Signalling 4.0 UpdateThis memo describes how to efficiently use the ATM call controlsignalling procedures defined in UNI Signalling 4.0 to support IP overATM environments as described in RFC 2225 and in RFC 2332. [STANDARDS-TRACK]2330 Paxson May 1998 Framework for IP Performance MetricsThe purpose of this memo is to define a general framework for particularmetrics to be developed by the IETF's IP Performance Metrics effort.This memo provides information for the Internet community. It does notspecify an Internet standard of any kind.Ramos Informational [Page 15]RFC 2399 Summary of 2300-2399 January 19992329 Moy Apr 1998 OSPF Standardization ReportThis memo documents how the requirements for advancing a routingprotocol to Full Standard have been met for OSPFv2. This memo providesinformation for the Internet community. It does not specify an Internetstandard of any kind.2328 Moy Apr 1998 OSPF Version 2This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol. [STANDARDS-TRACK]2327 Handley Apr 1998 SDP: Session Description Protocol
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -