Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group S. GinozaRequest for Comments: 2699 ISICategory: Informational May 2000Request for Comments Summary RFC Numbers 2600-2699Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 2600 through RFCs 2699. 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 (1998). 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--- ------ ---- -----2699 Ginoza Apr 2000 Request for Comments SummaryThis memo.2698 Heinanen Sep 1999 A Two Rate Three Color MarkerThis document defines a Two Rate Three Color Marker (trTCM), which canbe used as a component in a Diffserv traffic conditioner. This memoprovides information for the Internet community.Ginoza Informational [Page 1]
RFC 2699 Summary of 2600-2699 May 20002697 Heinanen Sep 1999 A Single Rate Three Color MarkerThis document defines a Single Rate Three Color Marker (srTCM), whichcan be used as component in a Diffserv traffic conditioner. This memoprovides information for the Internet community.2696 Weider Sep 1999 LDAP Control Extension for Simple Paged Results ManipulationThis document describes an LDAPv3 control extension for simple paging ofsearch results. This memo provides information for the Internetcommunity.2695 Chiu Sep 1999 Authentication Mechanisms for ONC RPCThis document describes two authentication mechanisms created by SunMicrosystems that are commonly used in conjunction with the ONC RemoteProcedure Call (ONC RPC Version 2) protocol. This memo providesinformation for the Internet community.2694 Srisuresh Sep 1999 DNS extensions to Network Address Translators (DNS_ALG)This document identifies the need for DNS extensions to NATs andoutlines how a DNS Application Level Gateway (DNS_ALG) can meet theneed. This memo provides information for the Internet community.2693 Ellison Sep 1999 SPKI Certificate TheoryThis document gives the theory behind SPKI certificates and ACLs withoutgoing into technical detail about those structures or their uses. Thismemo defines an Experimental Protocol for the Internet community.2692 Ellison Sep 1999 SPKI RequirementsThe SPKI Working Group first established a list of things one might wantto do with certificates (attached at the end of this document), and thensummarized that list of desires into requirements. This documentpresents that summary of requirements. This memo defines anExperimental Protocol for the Internet community.Ginoza Informational [Page 2]
RFC 2699 Summary of 2600-2699 May 20002691 Bradner Sep 1999 A Memorandum of Understanding for an ICANN Protocol Support OrganizationThis is the text of the Memorandum of Understanding (MoU) that wassigned by ICANN, the IETF, the ITU-T, W3C and ETSI on July 14, 1999 inOslo. This MoU creates the Protocol Support Organization (PSO) withinthe Internet Corporation for Assigned Names and Numbers (ICANN). Thismemo provides information for the Internet community.2690 Bradner Sep 1999 A Proposal for an MOU-Based ICANN Protocol Support OrganizationThis is a copy of the proposal for an MOU-based Protocol SupportingOrganization that was submitted to ICANN on April 23, 1999. This memoprovides information for the Internet community.2689 Bormann Sep 1999 Providing Integrated Services over Low-bitrate LinksThis document describes an architecture for providing integratedservices over low-bitrate links, such as modem lines, ISDN B-channels,and sub-T1 links. This memo provides information for the Internetcommunity.2688 Jackowski Sep 1999 Integrated Services Mappings for Low Speed NetworksThis document defines the service mappings of the IETF IntegratedServices for low-bitrate links, specifically the controlled load andguaranteed services. [STANDARDS-TRACK]2687 Bormann Sep 1999 PPP in a Real-time Oriented HDLC-like FramingThis document proposes the suspend/resume-oriented solution for thereal-time encapsulation format part of the architecture. [STANDARDS-TRACK]Ginoza Informational [Page 3]
RFC 2699 Summary of 2600-2699 May 20002686 Bormann Sep 1999 The Multi-Class Extension to Multi-Link PPPThis document proposes the fragment-oriented solution for the real-timeencapsulation format part of the architecture. [STANDARDS-TRACK]2685 Fox Sep 1999 Virtual Private Networks IdentifierThis document proposes a format for a globally unique VPN identifier.[STANDARDS-TRACK]2684 Grossman Sep 1999 Multiprotocol Encapsulation over ATM Adaptation Layer 5This memo replacesRFC 1483. It describes two encapsulations methodsfor carrying network interconnect traffic over AAL type 5 over ATM.[STANDARDS-TRACK]2683 Leiba Sep 1999 IMAP4 Implementation RecommendationsThe IMAP4 specification describes a rich protocol for use in buildingclients and servers for storage, retrieval, and manipulation ofelectronic mail. Because the protocol is so rich and has so manyimplementation choices, there are often trade-offs that must be made andissues that must be considered when designing such clients and servers.This document attempts to outline these issues and to makerecommendations in order to make the end products as interoperable aspossible. This memo provides information for the Internet community.2682 Widjaja Sep 1999 Performance Issues in VC-Merge Capable ATM LSRsThis document investigates the impact of VC merging on the additionalbuffer required for the reassembly buffers and other buffers. This memoprovides information for the Internet community.Ginoza Informational [Page 4]
RFC 2699 Summary of 2600-2699 May 20002681 Almes Sep 1999 A Round-trip Delay Metric for IPPThis memo defines a metric for round-trip delay of packets acrossInternet paths. [STANDARDS-TRACK]2680 Almes Sep 1999 A One-way Packet Loss Metric for IPPMThis memo defines a metric for one-way packet loss across Internetpaths. [STANDARDS-TRACK]2679 Almes Sep 1999 A One-way Delay Metric for IPPMThis memo defines a metric for one-way delay of packets across Internetpaths. [STANDARDS-TRACK]2678 Mahdavi Sep 1999 IPPM Metrics for Measuring ConnectivityThis memo defines a series of metrics for connectivity between a pair ofInternet hosts. [STANDARDS-TRACK]2677 Greene Sep 1999 Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.[STANDARDS-TRACK]2676 ApostolopoulosAug 1999 QoS Routing Mechanisms and OSPF ExtensionsThis memo describes extensions to the OSPF protocol to support QoSroutes. The focus of this document is on the algorithms used to computeQoS routes and on the necessary modifications to OSPF to support thisfunction, e.g., the information needed, its format, how it isdistributed, and how it is used by the QoS path selection process. Thismemo defines an Experimental Protocol for the Internet community.Ginoza Informational [Page 5]
RFC 2699 Summary of 2600-2699 May 20002675 Borman Aug 1999 IPv6 JumbogramsThis document describes the IPv6 Jumbo Payload option, which providesthe means of specifying such large payload lengths. It also describesthe changes needed to TCP and UDP to make use of jumbograms.[STANDARDS-TRACK]2674 Bell Sep 1999 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN ExtensionsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP based internets.[STANDARDS-TRACK]2673 Crawford Aug 1999 Binary Labels in the Domain Name SystemThis document defines a "Bit-String Label" which may appear withindomain names. This new label type compactly represents a sequence of"One-Bit Labels" and enables resource records to be stored at any bit-boundary in a binary-named section of the domain name tree.[STANDARDS-TRACK]2672 Crawford Aug 1999 Non-Terminal DNS Name RedirectionThis document defines a new DNS Resource Record called "DNAME", whichprovides the capability to map an entire subtree of the DNS name spaceto another domain. [STANDARDS-TRACK]2671 Vixie Aug 1999 Extension Mechanisms for DNS (EDNS0)The Domain Name System's wire protocol includes a number of fixed fieldswhose range has been or soon will be exhausted and does not allowclients to advertise their capabilities to servers. This documentdescribes backward compatible mechanisms for allowing the protocol togrow. [STANDARDS-TRACK]Ginoza Informational [Page 6]
RFC 2699 Summary of 2600-2699 May 20002670 St. Johns Aug 1999 Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfacesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines a basic set of managed objects for SNMP-basedmanagement of MCNS/DOCSIS compliant Radio Frequency (RF) interfaces.[STANDARDS-TRACK]2669 St. Johns Aug 1999 DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination SystemsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines a basic set of managed objects for SNMP-basedmanagement of DOCSIS 1.0 compliant Cable Modems and Cable ModemTermination Systems. [STANDARDS-TRACK]2668 Smith Sep 1999 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.[STANDARDS-TRACK]2667 Thaler Aug 1999 IP Tunnel MIBThis memo defines a Management Information Base (MIB) for use withnetwork management protocols in the Internet community. In particular,it describes managed objects used for managing tunnels of any type overIPv4 networks. [STANDARDS-TRACK]Ginoza Informational [Page 7]
RFC 2699 Summary of 2600-2699 May 20002666 Flick Sep 1999 Definitions of Object Identifiers for Identifying Ethernet Chip SetsThis memo defines OBJECT IDENTIFIER values for use with networkmanagement protocols in the Internet community. This memo providesinformation for the Internet community.2665 Flick Sep 1999 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.[STANDARDS-TRACK]2664 Plzak Aug 1999 FYI on Questions and Answers Answers to Commonly Asked "New Internet User" QuestionsThis memo provides an overview to the new Internet User. The intendedaudience is the common Internet user of today, thus it attempts toprovide a more consumer oriented approach to the Internet rather thangoing into any depth about a topic. This memo provides information forthe Internet community.2663 Srisuresh Aug 1999 IP Network Address Translator (NAT) Terminology and ConsiderationsThis document attempts to describe the operation of NAT devices and theassociated considerations in general, and to define the terminology usedto identify various flavors of NAT. This memo provides information forthe Internet community.2662 Bathrick Aug 1999 Definitions of Managed Objects for the ADSL LinesThis document defines a standard SNMP MIB for ADSL lines based on theADSL Forum standard data model. [STANDARDS-TRACK]Ginoza Informational [Page 8]
RFC 2699 Summary of 2600-2699 May 20002661 Townsley Aug 1999 Layer Two Tunneling Protocol "L2TP"This document describes the Layer Two Tunneling Protocol (L2TP).[STANDARDS-TRACK]2660 Rescorla Aug 1999 The Secure HyperText Transfer ProtocolThis memo describes a syntax for securing messages sent using theHypertext Transfer Protocol (HTTP), which forms the basis for the WorldWide Web. This memo defines an Experimental Protocol for the Internetcommunity.2659 Rescorla Aug 1999 Security Extensions For HTMLThis memo describes a syntax for embedding S-HTTP negotiation parametersin HTML documents. This memo defines an Experimental Protocol for theInternet community.2658 McKay Aug 1999 RTP Payload Format for PureVoice(tm) AudioThis document describes the RTP payload format for PureVoice(tm) Audio.[STANDARDS-TRACK]2657 Hedberg Aug 1999 LDAPv2 Client vs. the Index MeshLDAPv2 clients as implemented according toRFC 1777 have no notion onreferral. The integration between such a client and an Index Mesh, asdefined by the Common Indexing Protocol, heavily depends on referralsand therefore needs to be handled in a special way. This documentdefines one possible way of doing this. This memo defines anExperimental Protocol for the Internet community.Ginoza Informational [Page 9]
RFC 2699 Summary of 2600-2699 May 20002656 Hardie Aug 1999 Registration Procedures for SOIF Template TypeThe registration procedure described in this document is specific toSOIF template types. This memo defines an Experimental Protocol for theInternet community.2655 Hardie Aug 1999 CIP Index Object Format for SOIF ObjectsThis document describes SOIF, the Summary Object Interchange Format, asan index object type in the context of the CIP framework. This memodefines an Experimental Protocol for the Internet community.2654 Hedberg Aug 1999 A Tagged Index Object for use in the Common Indexing ProtocolThis document defines a mechanism by which information servers canexchange indices of information from their databases by making use ofthe Common Indexing Protocol (CIP). This document defines the structureof the index information being exchanged, as well as the appropriatemeanings for the headers that are defined in the Common IndexingProtocol. This memo defines an Experimental Protocol for the Internetcommunity.2653 Allen Aug 1999 CIP Transport ProtocolsThis document specifies three protocols for transporting CIP requests,responses and index objects, utilizing TCP, mail, and HTTP.[STANDARDS-TRACK]2652 Allen Aug 1999 MIME Object Definitions for the Common Indexing Protocol (CIP)This document describes the definitions of those objects as well as themethods and requirements needed to define a new index type.[STANDARDS-TRACK]Ginoza Informational [Page 10]
RFC 2699 Summary of 2600-2699 May 20002651 Allen Aug 1999 The Architecture of the Common Indexing Protocol (CIP)This document describes the CIP framework, including its architectureand the protocol specifics of exchanging indices. [STANDARDS-TRACK]2650 Meyer Aug 1999 Using RPSL in PracticeThis document is a tutorial on using the Routing Policy SpecificationLanguage (RPSL) to describe routing policies in the Internet RoutingRegistry (IRR). This memo provides information for the Internetcommunity.2649 Greenblatt Aug 1999 An LDAP Control and Schema for Holding Operation SignaturesThis document describes an LDAP message control which allows for theretrieval of digitally signed information. This document defines an LDAPv3 based mechanism for signing directory operations in order to create asecure journal of changes that have been made to each directory entry.This memo defines an Experimental Protocol for the Internet community.2648 Moats Aug 1999 A URN Namespace for IETF DocumentsThis document proposes the "ietf" namespace, which consists of the RFCfamily of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETFand published by the RFC Editor and the minutes of working groups (WG)and birds of a feather (BOF) meetings that occur during IETFconferences. [STANDARDS-TRACK]2647 Newman Aug 1999 Benchmarking Terminology for Firewall PerformanceThis document defines terms used in measuring the performance offirewalls. It extends the terminology already used for benchmarkingrouters and switches with definitions specific to firewalls.[STANDARDS-TRACK]Ginoza Informational [Page 11]
RFC 2699 Summary of 2600-2699 May 20002646 Gellens Aug 1999 The Text/Plain Format ParameterThis memo proposes a new parameter to be used with Text/Plain, and, inthe presence of this parameter, the use of trailing whitespace toindicate flowed lines. This results in an encoding which appears asnormal Text/Plain in older implementations, since it is in fact normalText/Plain. [STANDARDS-TRACK]2645 Gellens Aug 1999 ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP AddressesThis memo proposes a new service, On-Demand Mail Relay (ODMR), which isa profile of SMTP, providing for a secure, extensible, easy to implementapproach to the problem. [STANDARDS-TRACK]2644 Bradner Aug 1999 Benchmarking Methodology for Network Interconnect DevicesThis document discusses and defines a number of tests that may be usedto describe the performance characteristics of a network interconnectingdevice. In addition to defining the tests this document also describesspecific formats for reporting the results of the tests. This memoprovides information for the Internet community.2643 Ruffen Aug 1999 Cabletron's SecureFast VLAN Operational ModelCabletron's SecureFast VLAN (SFVLAN) product implements a distributedconnection-oriented switching protocol that provides fast forwarding ofdata packets at the MAC layer. The product uses the concept of virtualLANs (VLANs) to determine the validity of call connection requests andto scope the broadcast of certain flooded messages. This memo providesinformation for the Internet community.2642 Kane Aug 1999 Cabletron's VLS Protocol SpecificationVLSP provides support for equal-cost multipath routing, and recalculatesroutes quickly in the face of topological changes, utilizing a minimumof routing protocol traffic. This memo provides information for theInternet community.Ginoza Informational [Page 12]
RFC 2699 Summary of 2600-2699 May 20002641 Hamilton Aug 1999 Cabletron's VlanHello Protocol SpecificationThe VlanHello protocol is part of the InterSwitch Message Protocol(ISMP) which provides interswitch communication between switches runningCabletron's SecureFast VLAN (SFVLAN) product. Switches use theVlanHello protocol to discover their neighboring switches and establishthe topology of the switch fabric. This memo provides information forthe Internet community.2640 Curtin Jul 1999 Internationalization of the File transfer ProtocolThis document addresses the internationalization (I18n) of FTP, whichincludes supporting the multiple character sets and languages foundthroughout the Internet community. This is achieved by extending theFTP specification and giving recommendations for properinternationalization support. [STANDARDS-TRACK]2639 Hastings Jul 1999 Internet Printing Protocol/1.0: Implementer's GuideThis document contains information that supplements the IPP Model andSemantics and the IPP Transport and Encoding documents. It is intendedto help implementers understand IPP/1.0 and some of the considerationsthat may assist them in the design of their client and/or IPP objectimplementations. This memo provides information for the Internetcommunity.2638 Nichols Jul 1999 A Two-bit Differentiated Services Architecture for the InternetThis document presents a differentiated services architecture for theinternet. This memo provides information for the Internet community.Ginoza Informational [Page 13]
RFC 2699 Summary of 2600-2699 May 20002637 Hamzeh Jul 1999 Point-to-Point Tunneling Protocol (PPTP)This document specifies a protocol which allows the Point to PointProtocol (PPP) to be tunneled through an IP network. This memo providesinformation for the Internet community.2636 Gellens Jul 1999 Wireless Device Configuration (OTASP/OTAPA) via ACAPThis paper describes a viable and attractive means to provideOTASP/OTAPA via IS-707, using the ACAP protocol. This memo providesinformation for the Internet community.2635 Hambridge Jun 1999 DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and PostingsThis document explains why mass unsolicited electronic mail messages areharmful in the Internetworking community. This memo providesinformation for the Internet community.2634 Hoffman Jun 1999 Enhanced Security Services for S/MIMEThis document describes four optional security service extensions forS/MIME. [STANDARDS-TRACK]2633 Ramsdell Jun 1999 S/MIME Version 3 Message SpecificationThis document describes a protocol for adding cryptographic signatureand encryption services to MIME data. [STANDARDS-TRACK]Ginoza Informational [Page 14]
RFC 2699 Summary of 2600-2699 May 20002632 Ramsdell Jun 1999 S/MIME Version 3 Certificate HandlingS/MIME (Secure/Multipurpose Internet Mail Extensions), provides a methodto send and receive secure MIME messages. Before using a public key toprovide security services, the S/MIME agent MUST certify that the publickey is valid. S/MIME agents MUST use PKIX certificates to validatepublic keys as described in the Internet X.509 Public Key Infrastructure(PKIX) Certificate and CRL Profile. [STANDARDS-TRACK]2631 Rescorla Jun 1999 Diffie-Hellman Key Agreement MethodThis document standardizes one particular Diffie-Hellman variant, basedon the ANSI X9.42 draft, developed by the ANSI X9F1 working group.[STANDARDS-TRACK]2630 Housley Jun 1999 Cryptographic Message SyntaxThis document describes the Cryptographic Message Syntax. This syntaxis used to digitally sign, digest, authenticate, or encrypt arbitrarymessages. [STANDARDS-TRACK]2629 Rose Jun 1999 Writing I-Ds and RFCs using XMLThis memo presents a technique for using XML (Extensible MarkupLanguage) as a source format for documents in the Internet-Drafts (I-Ds)and Request for Comments (RFC) series. This memo provides informationfor the Internet community.2628 Smyslov Jun 1999 Simple Cryptographic Program Interface (Crypto API)This document describes a simple Application Program Interface tocryptographic functions. This memo provides information for theInternet community.Ginoza Informational [Page 15]
RFC 2699 Summary of 2600-2699 May 20002627 Wallner Jun 1999 Key Management for Multicast: Issues and ArchitecturesThis report contains a discussion of the difficult problem of keymanagement for multicast communication sessions. It focuses on two mainareas of concern with respect to key management, which are, initializingthe multicast group with a common net key and rekeying the multicastgroup. This memo provides information for the Internet community.2626 Nesser II Jun 1999 The Internet and the Millennium Problem (Year 2000)The Year 2000 Working Group (WG) has conducted an investigation into themillennium problem as it regards Internet related protocols. Thisinvestigation only targeted the protocols as documented in the RequestFor Comments Series (RFCs). This investigation discovered little reasonfor concern with regards to the functionality of the protocols. A fewminor cases of older implementations still using two digit years (alaRFC 850) were discovered, but almost all Internet protocols were given aclean bill of health. Several cases of "period" problems werediscovered, where a time field would "roll over" as the size of fieldwas reached. In particular, there are several protocols, which have 32bit, signed integer representations of the number of seconds sinceJanuary 1, 1970 which will turn negative at Tue Jan 19 03:14:07 GMT2038. Areas whose protocols will be effected by such problems have beennotified so that new revisions will remove this limitation. This memoprovides information for the Internet community.2625 Rajagopal Jun 1999 IP and ARP over Fibre ChannelThe purpose of this document is to specify a way of encapsulating IP andAddress Resolution Protocol(ARP) over Fibre Channel and also to describea mechanism(s) for IP address resolution. [STANDARDS-TRACK]2624 Shepler Jun 1999 NFS Version 4 Design ConsiderationsThis design considerations document is meant to present more detail thanthe working group charter. Specifically, it presents the areas that theworking group will investigate and consider while developing a protocolspecification for NFS version 4. This memo provides information for theInternet community.Ginoza Informational [Page 16]
RFC 2699 Summary of 2600-2699 May 20002623 Eisler Jun 1999 NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5This memorandum clarifies various security issues involving the NFSprotocol (Version 2 and Version 3 only) and then describes how theVersion 2 and Version 3 of the NFS protocol use the RPCSEC_GSS securityflavor protocol and Kerberos V5. [STANDARDS-TRACK]2622 Alaettinoglu Jun 1999 Routing Policy Specification Language (RPSL)RPSL allows a network operator to be able to specify routing policies atvarious levels in the Internet hierarchy; for example at the AutonomousSystem (AS) level. At the same time, policies can be specified withsufficient detail in RPSL so that low level router configurations can begenerated from them. RPSL is extensible; new routing protocols and newprotocol features can be introduced at any time. [STANDARDS-TRACK]2621 Zorn Jun 1999 RADIUS Accounting Server MIBThis memo defines a set of extensions which instrument RADIUS accountingserver functions. This memo provides information for the Internetcommunity.2620 Aboba Jun 1999 RADIUS Accounting Client MIBThis memo defines a set of extensions which instrument RADIUS accountingclient functions. This memo provides information for the Internetcommunity.2619 Zorn Jun 1999 RADIUS Authentication Server MIBThis memo defines a set of extensions which instrument RADIUSauthentication server functions. [STANDARDS-TRACK]2618 Aboba Jun 1999 RADIUS Authentication Client MIBThis memo defines a set of extensions which instrument RADIUSauthentication client functions. [STANDARDS-TRACK]Ginoza Informational [Page 17]
RFC 2699 Summary of 2600-2699 May 20002617 Franks Jun 1999 HTTP Authentication: Basic and Digest Access AuthenticationThis document provides the specification for HTTP's authenticationframework, the original Basic authentication scheme and a scheme basedon cryptographic hashes, referred to as "Digest Access Authentication".[STANDARDS-TRACK]2616 Fielding Jun 1999 Hypertext Transfer Protocol -- HTTP/1.1HTTP has been in use by the World-Wide Web global information initiativesince 1990. This specification defines the protocol referred to as"HTTP/1.1", and is an update toRFC 2068. [STANDARDS-TRACK]2615 Malis Jun 1999 PPP over SONET/SDHThis document describes the use of PPP over Synchronous Optical Network(SONET) and Synchronous Digital Hierarchy (SDH) circuits. [STANDARDS-TRACK]2614 Kempf Jun 1999 An API for Service LocationThis document describes standardized APIs for SLP in C and Java. Thismemo provides information for the Internet community.2613 Waterman Jun 1999 Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0This 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 remote network monitoringdevices in switched networks environments. [STANDARDS-TRACK]2612 Adams Jun 1999 The CAST-256 Encryption AlgorithmThis document describes an existing algorithm that can be used tosatisfy this requirement. Included are a description of the cipher andthe key scheduling algorithm, the s-boxes, and a set of test vectors(Appendix A). This memo provides information for the Internetcommunity.Ginoza Informational [Page 18]
RFC 2699 Summary of 2600-2699 May 20002611 Daigle Jun 1999 URN Namespace Definition MechanismsThis document lays out general definitions of and mechanisms forestablishing URN "namespaces". This document specifies an Internet BestCurrent Practices for the Internet Community, and requests discussionand suggestions for improvements.2610 Perkins Jun 1999 DHCP Options for Service Location ProtocolThe Dynamic Host Configuration Protocol provides a framework for passingconfiguration information to hosts on a TCP/IP network. Entities usingthe Service Location Protocol need to find out the address of DirectoryAgents in order to transact messages. Another option provides anassignment of scope for configuration of SLP User and Service Agents.[STANDARDS-TRACK]2609 Guttman Jun 1999 Service Templates and Service: SchemesThis document describes a formal procedure for defining andstandardizing new service types and attributes for use with the"service:" scheme. [STANDARDS-TRACK]2608 Guttman Jun 1999 Service Location Protocol, Version 2The Service Location Protocol provides a scalable framework for thediscovery and selection of network services. Using this protocol,computers using the Internet need little or no static configuration ofnetwork services for network based applications. This is especiallyimportant as computers become more portable, and users less tolerant orable to fulfill the demands of network system administration.[STANDARDS-TRACK]2607 Aboba Jun 1999 Proxy Chaining and Policy Implementation in RoamingThis document describes how proxy chaining and policy implementation canbe supported in roaming systems. This memo provides information for theInternet community.Ginoza Informational [Page 19]
RFC 2699 Summary of 2600-2699 May 20002606 Eastlake Jun 1999 Reserved Top Level DNS NamesTo reduce the likelihood of conflict and confusion, a few top leveldomain names are reserved for use in private testing, as examples indocumentation, and the like. In addition, a few second level domainnames reserved for use as examples are documented. This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.2605 Mansfield Jun 1999 Directory Server Monitoring MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.[STANDARDS-TRACK]2604 Gellens Jun 1999 Wireless Device Configuration (OTASP/OTAPA) via ACAPThis paper describes a viable and attractive means to provideOTASP/OTAPA via IS-707, using the ACAP protocol. This memo providesinformation for the Internet community.2603 Davison Jun 1999 ILMI-Based Server Discovery for NHRPThis memo defines how ILMI-based Server Discovery, which provides amethod for ATM-attached hosts and routers to dynamically determine theATM addresses of servers, shall be used to locate NHRP servers.[STANDARDS-TRACK]2602 Davison Jun 1999 ILMI-Based Server Discovery for MARSThis memo defines how ILMI-based Server Discovery, which provides amethod for ATM-attached hosts and routers to dynamically determine theATM addresses of servers, shall be used to locate MARS servers.[STANDARDS-TRACK]Ginoza Informational [Page 20]
RFC 2699 Summary of 2600-2699 May 20002601 Davison Jun 1999 ILMI-Based Server Discovery for ATMARPThis memo defines how ILMI-based Server Discovery, which provides amethod for ATM-attached hosts and routers to dynamically determine theATM addresses of servers, shall be used to locate ATMARP servers.[STANDARDS-TRACK]2600 Reynolds Mar 2000 Internet Official Protocol StandardsThis memo is published by the RFC Editor in accordance withSection 2.1of "The Internet Standards Process -- Revision 3",RFC 2026, whichspecifies the rules and procedures by which all Internet standards areset. This memo is prepared by the RFC Editor for the IESG and IAB.Please seehttp://www.rfc-editor.org for later updates to this document.[STANDARDS-TRACK]Security Considerations Security issues are not discussed in this memo.Author's Address Sandy Ginoza University of Southern California Information Sciences Institute 4676 Admiralty Way Marina Del Rey, CA 90292 Phone: (310) 822-1511 EMail: ginoza@isi.eduGinoza Informational [Page 21]
RFC 2699 Summary of 2600-2699 May 2000Full Copyright Statement Copyright (C) The Internet Society (1998). 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.Ginoza Informational [Page 22]
[8]ページ先頭