📄 rfc2499.txt
字号:
2468 Cerf Oct 1998 I REMEMBER IANAA long time ago, in a network, far far away, a great adventure tookplace!. This memo provides information for the Internet community.2467 Crawford Dec 1998 Transmission of IPv6 Packets over FDDI NetworksThis document specifies the frame format for transmission of IPv6packets and the method of forming IPv6 link-local addresses andstatelessly autoconfigured addresses on FDDI networks. [STANDARDS-TRACK]2466 Haskin Dec 1998 Management Information Base for IP Version 6: ICMPv6 GroupThis document is one in the series of documents that define various MIBobject groups for IPv6. Specifically, the ICMPv6 group is defined inthis document. [STANDARDS-TRACK]2465 Haskin Dec 1998 Management Information Base for IP Version 6: Textual Conventions and General GroupThis document is one in the series of documents that provide MIBdefinitions for for IP Version 6. Specifically, the IPv6 MIB textualconventions as well as the IPv6 MIB General group is defined in thisdocument. [STANDARDS-TRACK]Ramos Informational [Page 8]RFC 2499 Summary of 2400-2499 July 19992464 Crawford Dec 1998 Transmission of IPv6 Packets over Ethernet NetworksThis document specifies the frame format for transmission of IPv6packets and the method of forming IPv6 link-local addresses andstatelessly autoconfigured addresses on Ethernet networks. It alsospecifies the content of the Source/Target Link-layer Address optionused in Router Solicitation, Router Advertisement, NeighborSolicitation, Neighbor Advertisement and Redirect messages when thosemessages are transmitted on an Ethernet. [STANDARDS-TRACK]2463 Conta Dec 1998 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationThis document specifies a set of Internet Control Message Protocol(ICMP) messages for use with version 6 of the Internet Protocol (IPv6).[STANDARDS-TRACK]2462 Thomson Dec 1998 IPv6 Stateless Address AutoconfigurationThis document specifies the steps a host takes in deciding how toautoconfigure its interfaces in IP version 6. [STANDARDS-TRACK]2461 Narten Dec 1998 Neighbor Discovery for IP Version 6 (IPv6)This document specifies the Neighbor Discovery protocol for IP Version6. [STANDARDS-TRACK]2460 Deering Dec 1998 Internet Protocol, Version 6 (IPv6) SpecificationThis document specifies version 6 of the Internet Protocol (IPv6), alsosometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK]Ramos Informational [Page 9]RFC 2499 Summary of 2400-2499 July 19992459 Housley Jan 1999 Internet X.509 Public Key Infrastructure Certificate and CRL ProfileThis memo profiles the X.509 v3 certificate and X.509 v2 CRL for use inthe Internet. [STANDARDS-TRACK]2458 Lu Nov 1998 Toward the PSTN/Internet Inter-Networking --Pre-PINT ImplementationsThis document contains the information relevant to the development ofthe inter-networking interfaces underway in the Public SwitchedTelephone Network (PSTN)/Internet Inter-Networking (PINT) Working Group.This memo provides information for the Internet community.2457 Clouston Nov 1998 Definitions of Managed Objects for Extended Border NodeThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines objects for monitoring and controlling networkdevices with APPN (Advanced Peer-to-Peer Network) EBN (Extended BorderNode) capabilities. This memo identifies managed objects for the EBNarchitecture. [STANDARDS-TRACK]2456 Clouston Nov 1998 Definitions of Managed Objects for APPN TRAPSThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines objects for receiving notifications from networkdevices with APPN (Advanced Peer-to-Peer Network) and DLUR (Dependent LURequester) capabilities. This memo identifies notifications for theAPPN and DLUR architecture. [STANDARDS-TRACK]Ramos Informational [Page 10]RFC 2499 Summary of 2400-2499 July 19992455 Clouston Nov 1998 Definitions of Managed Objects for APPNThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines objects for monitoring and controlling networkdevices with APPN (Advanced Peer-to-Peer Networking) capabilities. Thismemo identifies managed objects for the APPN protocol. [STANDARDS-TRACK]2454 Daniele Dec 1998 IP Version 6 Management Information Base for the User Datagram ProtocolThis document is one in the series of documents that define various MIBobjects for IPv6. Specifically, this document is the MIB module whichdefines managed objects for implementations of the User DatagramProtocol (UDP) over IP Version 6 (IPv6). [STANDARDS-TRACK]2453 Malkin Nov 1998 RIP Version 2This document specifies an extension of the Routing Information Protocol(RIP) to expand the amount of useful information carried in RIP messagesand to add a measure of security. [STANDARDS-TRACK]2452 Daniele Dec 1998 IP Version 6 Management Information Base for the Transmission Control ProtocolThis document is one in the series of documents that define various MIBobjects for IPv6. Specifically, this document is the MIB module whichdefines managed objects for implementations of the Transmission ControlProtocol (TCP) over IP Version 6 (IPv6). [STANDARDS-TRACK]2451 Pereira Nov 1998 The ESP CBC-Mode Cipher AlgorithmsThis document describes how to use CBC-mode cipher algorithms with theIPSec ESP (Encapsulating Security Payload) Protocol. It not onlyclearly states how to use certain cipher algorithms, but also how to useall CBC-mode cipher algorithms. [STANDARDS-TRACK]Ramos Informational [Page 11]RFC 2499 Summary of 2400-2499 July 19992450 Hinden Dec 1998 Proposed TLA and NLA Assignment RulesThis document proposes rules for Top-Level Aggregation Identifiers (TLAID) and Next-Level Aggregation Identifiers (NLA ID). This memo providesinformation for the Internet community.2449 Gellens Nov 1998 POP3 Extension MechanismThis memo updates RFC 1939 to define a mechanism to announce support foroptional commands, extensions, and unconditional server behavior.[STANDARDS-TRACK]2448 Civanlar Nov 1998 AT&T's Error Resilient Video Transmission TechniqueThis document describes a set of techniques for packet loss resilienttransmission of compressed video bitstreams based on reliable deliveryof their vital information-carrying segments. This memo providesinformation for the Internet community.2447 Dawson Nov 1998 iCalendar Message-Based Interoperability Protocol (iMIP)This document specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-basedtransports. [STANDARDS-TRACK]2446 Silverberg Nov 1998 iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal EntriesThis document specifies how calendaring systems use iCalendar objects tointeroperate with other calendar systems. It does so in a general way soas to allow multiple methods of communication between systems.[STANDARDS-TRACK]Ramos Informational [Page 12]RFC 2499 Summary of 2400-2499 July 19992445 Dawson Nov 1998 Internet Calendaring and Scheduling Core Object Specification (iCalendar)This memo has been defined to provide the definition of a common formatfor openly exchanging calendaring and scheduling information across theInternet. [STANDARDS-TRACK]2444 Newman Oct 1998 The One-Time-Password SASL MechanismOTP provides a useful authentication mechanism for situations wherethere is limited client or server trust. Currently, OTP is added toprotocols in an ad-hoc fashion with heuristic parsing. Thisspecification defines an OTP SASL mechanism so it can be easily andformally integrated into many application protocols. [STANDARDS-TRACK]2443 Luciani Nov 1998 A Distributed MARS Service Using SCSPThis document describes a method for distributing a MARS service withina LIS. This method uses the Server Cache Synchronization Protocol(SCSP) to synchronize the MARS Server databases within a LIS. When SCSPis used to synchronize the caches of MARS Servers in a LIS, the LISdefines the boundary of an SCSP Server Group (SG). [STANDARDS-TRACK]2442 Freed Nov 1998 The Batch SMTP Media TypeThis document defines a MIME content type suitable for tunneling anESMTP transaction through any MIME-capable transport. This memoprovides information for the Internet community2441 Cohen Nov 1998 Working with Jon Tribute delivered at UCLA, October 30, 1998This memo provides information for the Internet community.2440 Callas Nov 1998 OpenPGP Message FormatThis document is maintained in order to publish all necessaryinformation needed to develop interoperable applications based on theOpenPGP format. [STANDARDS-TRACK]Ramos Informational [Page 13]RFC 2499 Summary of 2400-2499 July 19992439 Villamizar Nov 1998 BGP Route Flap DampingA usage of the BGP routing protocol is described which is capable ofreducing the routing traffic passed on to routing peers and thereforethe load on these peers without adversely affecting route convergencetime for relatively stable routes. [STANDARDS-TRACK]2438 O'Dell Oct 1998 Advancement of MIB specifications on the IETF Standards TrackThis document specifies the process which the IESG will use to determineif a MIB specification document meets these requirements. It alsodiscusses the rationale for this process. This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.2437 Kaliski Oct 1998 PKCS #1: RSA Cryptography Specifications Version 2.0This memo is the successor to RFC 2313. This document providesrecommendations for the implementation of public-key cryptography basedon the RSA algorithm. This memo provides information for the Internetcommunity.2436 Brett Oct 1998 Collaboration between ISOC/IETF and ITU-TThis document describes the collaboration process between the ITU-T andISOC/IETF. This memo provides information for the Internet community.2435 Berc Oct 1998 RTP Payload Format for JPEG-compressed VideoThis memo describes the RTP payload format for JPEG video streams.[STANDARDS-TRACK]Ramos Informational [Page 14]RFC 2499 Summary of 2400-2499 July 19992434 Narten Oct 1998 Guidelines for Writing an IANA Considerations Section in RFCsThis document discusses issues that should be considered in formulatinga policy for assigning values to a name space and provides guidelines todocument authors on the specific text that must be included in documentsthat place demands on the IANA. This document specifies an InternetBest Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.2433 Zorn Oct 1998 Microsoft PPP CHAP 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 and a family of NetworkControl Protocols (NCPs) for establishing and configuring differentnetwork-layer protocols. This memo provides information for theInternet community.2432 Dubray Oct 1998 Terminology for IP Multicast BenchmarkingThe purpose of this document is to define terminology specific to thebenchmarking of multicast IP forwarding devices. This memo providesinformation for the Internet community.2431 Tynan Oct 1998 RTP Payload Format for BT.656 Video EncodingThis document specifies the RTP payload format for encapsulating ITURecommendation BT.656-3 video streams in the Real-Time Transport
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -