Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group A. RamosRequest for Comments: 2499 ISICategory: Informational July 1999Request for Comments Summary RFC Numbers 2400-2499Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 2400 through RFCs 2499. 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.Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved.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--- ------ ---- -----2499 Ramos July 1999 Request for Comments SummaryThis memo.2498 Mahdavi Jan 1999 IPPM Metrics for Measuring ConnectivityThis memo defines a series of metrics for connectivity between a pair ofInternet hosts. It builds on notions introduced and discussed in RFC2330, the IPPM framework document. This memo defines an ExperimentalProtocol for the Internet community.Ramos Informational [Page 1]
RFC 2499 Summary of 2400-2499 July 19992497 Souvatzis Jan 1999 Transmission of IPv6 Packets over ARCnet NetworksThis memo specifies a frame format for transmission of IPv6 packets andthe method of forming IPv6 link-local and statelessly autoconfiguredaddresses on ARCnet networks. It also specifies the content of theSource/Target Link-layer Address option used by the Router Solicitation,Router Advertisement, Neighbor Solicitation, Neighbor Advertisement andRedirect messages described in, when those messages are transmitted onan ARCnet. [STANDARDS-TRACK]2496 Fowler Jan 1999 Definitions of Managed Objects for the DS3/E3 Interface TypeThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes objects used for managing DS3 and E3interfaces. This document is a companion document with Definitions ofManaged Objects for the DS0 (RFC 2494), DS1/E1/DS2/E2 (RFC 2495), andthe work in progress SONET/SDH Interface Types. [STANDARDS-TRACK]2495 Fowler Jan 1999 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface TypesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes objects used for managing DS1, E1, DS2 and E2interfaces. This document is a companion document with Definitions ofManaged Objects for the DS0 (RFC 2494), DS3/E3 (RFC 2496), and the workin progress, SONET/SDH Interface Types. [STANDARDS-TRACK]2494 Fowler Jan 1999 Definitions of Managed Objects for the DS0 and DS0 Bundle Interface TypeThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes objects used for managing DS0 and DS0 Bundleinterfaces. This document is a companion document with Definitions ofManaged Objects for the DS1/E1/DS2/E2 (RFC 2495), DS3/E3 (RFC 2496), andthe work in progress, SONET/SDH Interface Types. [STANDARDS-TRACK]Ramos Informational [Page 2]
RFC 2499 Summary of 2400-2499 July 19992493 Tesink Jan 1999 Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsThis document defines a set of Textual Conventions for MIB modules whichmake use of performance history data based on 15 minute intervals.[STANDARDS-TRACK]2492 Armitage Jan 1999 IPv6 over ATM NetworksThis document is a companion to the ION working group's architecturedocument, "IPv6 over Non Broadcast Multiple Access (NBMA) networks". Itprovides specific details on how to apply the IPv6 over NBMAarchitecture to ATM networks. This architecture allows conventionalhost-side operation of the IPv6 Neighbor Discovery protocol, while alsosupporting the establishment of 'shortcut' ATM forwarding paths (whenusing SVCs). Operation over administratively configured Point to PointPVCs is also supported. [STANDARDS-TRACK]2491 Armitage Jan 1999 IPv6 over Non-Broadcast Multiple Access (NBMA) networksThis document describes a general architecture for IPv6 over NBMAnetworks. [STANDARDS-TRACK]2490 Pullen Jan 1999 A Simulation Model for IP Multicast with RSVPThis document describes a detailed model of IPv4 multicast with RSVPthat has been developed using the OPNET simulation package, withprotocol procedures defined in the C language. This memo providesinformation for the Internet community.2489 Droms Jan 1999 Procedure for Defining New DHCP OptionsThis document describes the procedure for defining new DHCP options.This document specifies an Internet Best Current Practices for theInternet Community, and requests discussion and suggestions forimprovements.Ramos Informational [Page 3]
RFC 2499 Summary of 2400-2499 July 19992488 Allman Jan 1999 Enhancing TCP Over Satellite Channels using Standard MechanismsThe Transmission Control Protocol (TCP) provides reliable delivery ofdata across any network path, including network paths containingsatellite channels. While TCP works over satellite channels there areseveral IETF standardized mechanisms that enable TCP to more effectivelyutilize the available capacity of the network path. This documentoutlines some of these TCP mitigations. This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.2487 Hoffman Jan 1999 SMTP Service Extension for Secure SMTP over TLSThis document describes an extension to the SMTP service that allows anSMTP server and client to use transport-layer security to provideprivate, authenticated communication over the Internet. This gives SMTPagents the ability to protect some or all of their communications fromeavesdroppers and attackers. [STANDARDS-TRACK]2486 Aboba Jan 1999 The Network Access IdentifierThis document proposes syntax for the Network Access Identifier (NAI),the userID submitted by the client during PPP authentication.[STANDARDS-TRACK]2485 Drach Jan 1999 DHCP Option for The Open Group's User Authentication ProtocolThis document defines a DHCP option that contains a list of pointers toUser Authentication Protocol servers that provide user authenticationservices for clients that conform to The Open Group Network ComputingClient Technical Standard. [STANDARDS-TRACK]Ramos Informational [Page 4]
RFC 2499 Summary of 2400-2499 July 19992484 Zorn Jan 1999 PPP LCP Internationalization Configuration OptionThe Point-to-Point Protocol (PPP) provides a standard method fortransporting multi-protocol datagrams over point-to-point links. PPPalso defines an extensible Link Control Protocol (LCP), which allowsnegotiation of an Authentication Protocol for authenticating its peerbefore allowing Network Layer protocols to transmit over the link.[STANDARDS-TRACK]2483 Mealling Jan 1999 URI Resolution Services Necessary for URN ResolutionRetrieving the resource identified by a Uniform Resource Identifier(URI) is only one of the operations that can be performed on a URI. Onemight also ask for and get a list of other identifiers that are aliasesfor the original URI or a bibliographic description of the resource theURI denotes, for example. This applies to both Uniform Resource Names(URNs) and Uniform Resource Locators (URLs). Uniform ResourceCharacteristics (URCs) are discussed in this document but only asdescriptions of resources rather than identifiers. This memo defines anExperimental Protocol for the Internet community.2482 Whistler Jan 1999 Language Tagging in Unicode Plain TextThis document proposed a mechanism for language tagging in plain text.This memo provides information for the Internet community.2481 Ramakrishnan Jan 1999 A Proposal to add Explicit Congestion Notification (ECN) to IPThis note describes a proposed addition of ECN (Explicit CongestionNotification) to IP. This memo defines an Experimental Protocol for theInternet community.2480 Freed Jan 1999 Gateways and MIME Security MultipartsThis document examines the problems associated with use of MIME securitymultiparts and gateways to non-MIME environments. [STANDARDS-TRACK]Ramos Informational [Page 5]
RFC 2499 Summary of 2400-2499 July 19992479 Adams Dec 1998 Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API)The IDUP-GSS-API extends the GSS-API for applications requiringprotection of a generic data unit (such as a file or message) in a waywhich is independent of the protection of any other data unit andindependent of any concurrent contact with designated "receivers" of thedata unit. This memo provides information for the Internet community.2478 Baize Dec 1998 The Simple and Protected GSS-API Negotiation MechanismThis document specifies a Security Negotiation Mechanism for the GenericSecurity Service Application Program Interface (GSS-API). [STANDARDS-TRACK]2477 Aboba Jan 1999 Criteria for Evaluating Roaming ProtocolsThis document describes requirements for the provisioning of "roamingcapability" for dialup Internet users. "Roaming capability" is definedas the ability to use multiple Internet service providers (ISPs), whilemaintaining a formal, customer-vendor relationship with only one. Thismemo provides information for the Internet community.2476 Gellens Dec 1998 Message SubmissionThis memo describes a low cost, deterministic means for messages to beidentified as submissions, and specifies what actions are to be taken bya submission server. [STANDARDS-TRACK]2475 Blake Dec 1998 An Architecture for Differentiated ServicesThis document defines an architecture for implementing scalable servicedifferentiation in the Internet. This memo provides information for theInternet community.Ramos Informational [Page 6]
RFC 2499 Summary of 2400-2499 July 19992474 Nichols Dec 1998 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 HeadersThis document defines the IP header field, called the DS (fordifferentiated services) field. [STANDARDS-TRACK]2473 Conta Dec 1998 Generic Packet Tunneling in IPv6 SpecificationThis document defines the model and generic mechanisms for IPv6encapsulation of Internet packets, such as IPv6 and IPv4. [STANDARDS-TRACK]2472 Haskin Dec 1998 IP Version 6 over PPPThis document defines the method for transmission of IP Version 6packets over PPP links as well as the Network Control Protocol (NCP) forestablishing and configuring the IPv6 over PPP. It also specifies themethod of forming IPv6 link-local addresses on PPP links. [STANDARDS-TRACK]2471 Hinden Dec 1998 IPv6 Testing Address AllocationThis document describes an allocation plan for IPv6 addresses to be usedin testing IPv6 prototype software. This memo defines an ExperimentalProtocol for the Internet community.2470 Crawford Dec 1998 Transmission of IPv6 Packets over Token Ring NetworksThis memo specifies the MTU and frame format for transmission of IPv6packets on Token Ring networks. [STANDARDS-TRACK]Ramos Informational [Page 7]
RFC 2499 Summary of 2400-2499 July 19992469 Narten Dec 1998 A Caution On The Canonical Ordering Of Link-Layer AddressesProtocols such as ARP and Neighbor Discovery have data fields thatcontain link-layer addresses. In order to interoperate properly, asender setting such a field must insure that the receiver extracts thosebits and interprets them correctly. In most cases, such fields must bein "canonical form". Unfortunately, not all LAN adaptors are consistentin their use of canonical form, and implementations may need toexplicitly bit swap individual bytes in order to obtain the correctformat. This document provides information to implementors to help themavoid the pitfall of using non-canonical forms when canonical forms arerequired. This memo provides information for the Internet community.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 updatesRFC 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 toRFC 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 TransportProtocol (RTP). [STANDARDS-TRACK]2430 Li Oct 1998 A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)This document describes the Provider Architecture for DifferentiatedServices and Traffic Engineering (PASTE) for Internet Service Providers(ISPs). This memo provides information for the Internet community.Ramos Informational [Page 15]
RFC 2499 Summary of 2400-2499 July 19992429 Bormann Oct 1998 RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)This document specifies an RTP payload header format applicable to thetransmission of video streams generated based on the 1998 version ofITU-T Recommendation H.263. [STANDARDS-TRACK]2428 Allman Sep 1998 FTP Extensions for IPv6 and NATsThis paper specifies extensions to FTP that will allow the protocol towork over IPv4 and IPv6. [STANDARDS-TRACK]2427 Brown Sep 1998 Multiprotocol Interconnect over Frame RelayThis memo describes an encapsulation method for carrying networkinterconnect traffic over a Frame Relay backbone. It covers aspects ofboth Bridging and Routing. [STANDARDS-TRACK]2426 Dawson Sep 1998 vCard MIME Directory ProfileThis memo defines the profile of the MIME Content-Type for directoryinformation for a white-pages person object, based on a vCard electronicbusiness card. [STANDARDS-TRACK]2425 Howes Sep 1998 A MIME Content-Type for Directory InformationThis document defines a MIME Content-Type for holding directoryinformation. [STANDARDS-TRACK]2424 Vaudreuil Sep 1998 Content Duration MIME Header DefinitionThis document describes the MIME header Content-Duration that isintended for use with any timed media content (typically audio/* orvideo/*). [STANDARDS-TRACK]Ramos Informational [Page 16]
RFC 2499 Summary of 2400-2499 July 19992423 Vaudreuil Sep 1998 VPIM Voice Message MIME Sub-type RegistrationThis document describes the registration of the MIME sub-typemultipart/voice-message for use with the Voice Profile for Internet Mail(VPIM). [STANDARDS-TRACK]2422 Vaudreuil Sep 1998 Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type RegistrationThis document describes the registration of the MIME sub-typeaudio/32KADPCM for toll quality audio. [STANDARDS-TRACK]2421 Vaudreuil Sep 1998 Voice Profile for Internet Mail - version 2This document profiles Internet mail for voice messaging. [STANDARDS-TRACK]2420 Kummert Sep 1998 The PPP Triple-DES Encryption Protocol (3DESE)This document provides specific details for the use of the Triple-DESstandard (3DES) for encrypting PPP encapsulated packets. [STANDARDS-TRACK]2419 Sklower Sep 1998 The PPP DES Encryption Protocol, Version 2 (DESE-bis)This document provides specific details for the use of the DES standardfor encrypting PPP encapsulated packets. [STANDARDS-TRACK]2418 Bradner Sep 1998 IETF Working Group Guidelines and ProceduresThis document describes the guidelines and procedures for formation andoperation of IETF working groups. This document specifies an InternetBest Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.Ramos Informational [Page 17]
RFC 2499 Summary of 2400-2499 July 19992417 Chung Sep 1998 Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksThis memo specifies a MIB module in a manner that is both compliant tothe SNMPv2 SMI, and semantically identical to the peer SNMPv1definitions. [STANDARDS-TRACK]2416 Shepard Sep 1998 When TCP Starts Up With Four Packets Into Only Three BuffersThis memo is to document a simple experiment. The experiment showedthat in the case of a TCP receiver behind a 9600 bps modem link at theedge of a fast Internet where there are only 3 buffers before the modem(and the fourth packet of a four-packet start will surely be dropped),no significant degradation in performance is experienced by a TCPsending with a four-packet start when compared with a normal slow start(which starts with just one packet). This memo provides information forthe Internet community.2415 Poduri Sep 1998 Simulation Studies of Increased Initial TCP Window SizeThis document covers some simulation studies of the effects ofincreasing the initial window size of TCP. This memo providesinformation for the Internet community.2414 Allman Sep 1998 Increasing TCP's Initial WindowThis document specifies an increase in the permitted initial window forTCP from one segment to roughly 4K bytes. This memo defines anExperimental Protocol for the Internet community.2413 Weibel Sep 1998 Dublin Core Metadata for Resource DiscoveryThis is the first of a set of Informational RFCs describing the DublinCore. Its purpose is to introduce the Dublin Core and to describe theconsensus reached on the semantics of each of the 15 elements. Thismemo provides information for the Internet community.Ramos Informational [Page 18]
RFC 2499 Summary of 2400-2499 July 19992412 Orman Nov 1998 The OAKLEY Key Determination ProtocolThis document describes a protocol, named OAKLEY, by which twoauthenticated parties can agree on secure and secret keying material.The basic mechanism is the Diffie-Hellman key exchange algorithm. Thismemo provides information for the Internet community.2411 Thayer Nov 1998 IP Security Document RoadmapThis document is intended to provide guidelines for the development ofcollateral specifications describing the use of new encryption andauthentication algorithms with the ESP protocol, described in and newauthentication algorithms used with the AH protocol. This memo providesinformation for the Internet community.2410 Glenn Nov 1998 The NULL Encryption Algorithm and Its Use With IPsecThis memo defines the NULL encryption algorithm and its use with theIPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK]2409 Harkins Nov 1998 The Internet Key Exchange (IKE)This memo describes a hybrid protocol. The purpose is to negotiate, andprovide authenticated keying material for, security associations in aprotected manner. [STANDARDS-TRACK]2408 Maughan Nov 1998 Internet Security Association and Key Management Protocol (ISAKMP)This memo describes a protocol utilizing security concepts necessary forestablishing Security Associations (SA) and cryptographic keys in anInternet environment. [STANDARDS-TRACK]2407 Piper Nov 1998 The Internet IP Security Domain of Interpretation for ISAKMPThis document defines the Internet IP Security DOI (IPSEC DOI), whichinstantiates ISAKMP for use with IP when IP uses ISAKMP to negotiatesecurity associations. [STANDARDS-TRACK]Ramos Informational [Page 19]
RFC 2499 Summary of 2400-2499 July 19992406 Kent Nov 1998 IP Encapsulating Security Payload (ESP)The Encapsulating Security Payload (ESP) header is designed to provide amix of security services in IPv4 and IPv6. [STANDARDS-TRACK]2405 Madson Nov 1998 The ESP DES-CBC Cipher Algorithm With Explicit IVThis document describes the use of the DES Cipher algorithm in CipherBlock Chaining Mode, with an explicit IV, as a confidentiality mechanismwithin the context of the IPSec Encapsulating Security Payload (ESP).[STANDARDS-TRACK]2404 Madson Nov 1998 The Use of HMAC-SHA-1-96 within ESP and AHThis memo describes the use of the HMAC algorithm in conjunction withthe SHA-1 algorithm as an authentication mechanism within the revisedIPSEC Encapsulating Security Payload and the revised IPSECAuthentication Header. [STANDARDS-TRACK]2403 Madson Nov 1998 The Use of HMAC-MD5-96 within ESP and AHThis memo describes the use of the HMAC algorithm in conjunction withthe MD5 algorithm as an authentication mechanism within the revisedIPSEC Encapsulating Security Payload and the revised IPSECAuthentication Header. [STANDARDS-TRACK]2402 Kent Nov 1998 IP Authentication HeaderThe IP Authentication Header (AH) is used to provide connectionlessintegrity and data origin authentication for IP datagrams (hereafterreferred to as just "authentication"), and to provide protection againstreplays. [STANDARDS-TRACK]Ramos Informational [Page 20]
RFC 2499 Summary of 2400-2499 July 19992401 Kent Nov 1998 Security Architecture for the Internet ProtocolThis memo specifies the base architecture for IPsec compliant systems.[STANDARDS-TRACK]2400 IAB Sep 1998 INTERNET OFFICIAL PROTOCOL STANDARDSThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Architecture Board (IAB).This memo is an Internet Standard. [STANDARDS-TRACK]Security Considerations This memo does not affect the technical security of the Internet, but it does cite some security specifications.Author's Address Alegre Ramos University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: ramos@isi.eduRamos Informational [Page 21]
RFC 2499 Summary of 2400-2499 July 1999Full Copyright Statement Copyright (C) The Internet Society (1999). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.Ramos Informational [Page 22]
[8]ページ先頭