RFC 2299: Request for Comments Summary 中文翻译

URL : https://datatracker.ietf.org/doc/html/rfc2299
标题 : RFC 2299
翻译类型 : 自动生成

Network Working Group                                           A. Ramos
Request for Comments: 2299                                           ISI
Category: Informational                                     January 1999

Network Working Group                                           A. Ramos
Request for Comments: 2299                                           ISI
Category: Informational                                     January 1999

Request for Comments Summary

征求意见摘要

RFC Numbers 2200-2299

RFC编号2200-2299

Status of This Memo

关于下段备忘

This RFC is a slightly annotated list of the 100 RFCs from RFC 2200 through RFCs 2299. 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.

此RFC是RFC 2200到RFC 2299的100个RFC的略带注释的列表。这是这些RFC的状态报告。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。

版权公告

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（但不是所有RFC）是提议的标准、标准草案或标准。由于这些RFC的状态在标准处理过程中可能会发生变化，因此我们在此只注意到它们处于标准轨道上。请参阅最新版本的“互联网官方协议标准”，了解这些RFC的当前状态和状态。在下文中，标准轨道上的RFC标记为[standards-track]。

RFC     Author          Date            Title
---     ------          ----            -----

RFC     Author          Date            Title
---     ------          ----            -----

2299 Ramos Jan 1999 Request for Comments Summary

2299拉莫斯1999年1月征求意见摘要

This memo.

这份备忘录。

2298 Fajman Mar 1998 An Extensible Message Format

2298 Fajman Mar 1998一种可扩展的消息格式

This memo defines a MIME content-type that may be used by a mail user agent (UA) or electronic mail gateway to report the disposition of a message after it has been sucessfully delivered to a recipient. [STANDARDS-TRACK]

此备忘录定义了一种MIME内容类型，邮件用户代理（UA）或电子邮件网关可使用该类型在邮件成功传递给收件人后报告邮件的处理情况。[标准-轨道]

2297 Newman Mar 1998 Ipsilon's General Switch Management Protocol Specification Version 2.0

2297纽曼1998年3月Ipsilon的通用交换机管理协议规范版本2.0

This memo specifies enhancements to the General Switch Management Protocol (GSMP) [RFC1987]. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本备忘录规定了通用交换机管理协议（GSMP）[RFC1987]的增强功能。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2296 Holtman Mar 1998 HTTP Remote Variant Selection Algorithm -- RVSA/1.0

2296 Holtman Mar 1998 HTTP远程变量选择算法——RVSA/1.0

HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is a mechanism for automatically selecting the best version when the URL is accessed. A remote variant selection algorithm can be used to speed up the transparent negotiation process. This document defines the remote variant selection algorithm with the version number 1.0. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.

HTTP允许网站作者将同一信息的多个版本放在一个URL下。透明内容协商是一种机制，用于在访问URL时自动选择最佳版本。远程变量选择算法可用于加速透明协商过程。本文件定义了版本号为1.0的远程变量选择算法。这份备忘录为互联网社区定义了一个实验性协议。它没有规定任何类型的互联网标准。要求进行讨论并提出改进建议。

2295 Holtman Mar 1998 Transparent Content Negotiation in HTTP

2295 Holtman 1998年3月HTTP中的透明内容协商

HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is an extensible negotiation mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.

HTTP允许网站作者将同一信息的多个版本放在一个URL下。透明内容协商是一种可扩展的协商机制，分层在HTTP之上，用于在访问URL时自动选择最佳版本。这使得能够顺利部署新的web数据格式和标记标记。这份备忘录为互联网社区定义了一个实验性协议。它没有规定任何类型的互联网标准。要求进行讨论并提出改进建议。

2294 Kille Mar 1998 Representing the O/R Address hierarchy in the X.500 Directory Information Tree

2294 Kille Mar 1998，代表X.500目录信息树中的O/R地址层次结构

This document defines a representation of the O/R Address hierarchy in the Directory Information Tree. [STANDARDS-TRACK]

本文档定义了目录信息树中O/R地址层次结构的表示形式。[标准-轨道]

2293 Kille Mar 1998 Representing Tables and Subtrees in the X.500 Directory

2293 Kille Mar 1998，表示X.500目录中的表和子树

This document defines techniques for representing two types of information mapping in the OSI Directory: Mapping from a key to a value (or set of values), as might be done in a table lookup, and mapping from a distinguished name to an associated value (or values), where the values are not defined by the owner of the entry. This is achieved by use of a directory subtree. [STANDARDS-TRCK]

本文档定义了在OSI目录中表示两种类型的信息映射的技术：从键映射到值（或一组值），这可能在表查找中完成；从可分辨名称映射到关联值（或多个值），其中值不由条目的所有者定义。这是通过使用目录子树实现的。[标准-TRCK]

2292 Stevens Feb 1998 Advanced Sockets API for IPv6

2292 Stevens 1998年2月IPv6高级套接字API

The current document defines some the "advanced" features of the sockets API that are required for applications to take advantage of additional features of IPv6. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

当前文档定义了sockets API的一些“高级”功能，这些功能是应用程序利用IPv6附加功能所必需的。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2291 Slein Feb 1998 Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web

2291 SLE于1998年2月发布了万维网分布式创作和版本控制协议的要求

This document presents a list of features in the form of requirements for a Web Distributed Authoring and Versioning protocol which, if implemented, would improve the efficiency of common remote editing operations, provide a locking mechanism to prevent overwrite conflicts, improve link management support between non-HTML data types, provide a simple attribute-value metadata facility, provide for the creation and reading of container data types, and integrate versioning into the WWW. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文档以Web分布式创作和版本控制协议的要求形式列出了一系列功能，如果实施，将提高常见远程编辑操作的效率，提供锁定机制以防止覆盖冲突，改进非HTML数据类型之间的链接管理支持，提供一个简单的属性值元数据工具，用于创建和读取容器数据类型，并将版本控制集成到WWW中。此备忘录为Internet社区提供信息。它没有规定任何类型的互联网标准。

2290 Solomon Feb 1998 Mobile-IPv4 Configuration Option for PPP IPCP

2290 Solomon 1998年2月PPP IPCP的移动IPv4配置选项

Mobile IP [RFC 2002] defines media-independent procedures by which a Mobile Node can maintain existing transport and application-layer connections despite changing its point-of-attachment to the Internet and without changing its IP address. PPP [RFC 1661] provides a standard method for transporting multi-protocol packets over point-to-point links. As currently specified, Mobile IP Foreign Agents which support Mobile Node connections via PPP can do so only by first assigning unique addresses to those Mobile Nodes, defeating one of the primary advantages of Foreign Agents. This documents corrects this problem by defining the Mobile-IPv4 Configuration Option to the Internet Protocol Control Protocol (IPCP) [RFC 1332]. Using this option, two peers can

移动IP[RFC 2002]定义了与媒体无关的过程，通过该过程，移动节点可以保持现有的传输层和应用层连接，而无需更改其与Internet的连接点，也无需更改其IP地址。PPP[RFC1661]提供了通过点到点链路传输多协议数据包的标准方法。按照目前的规定，通过PPP支持移动节点连接的移动IP外部代理只能通过首先将唯一地址分配给这些移动节点来实现，这就破坏了外部代理的主要优势之一。本文档通过定义Internet协议控制协议（IPCP）[RFC 1332]的Mobile-IPv4配置选项来纠正此问题。使用此选项，两个对等方可以

communicate their support for Mobile IP during the IPCP phase of PPP. Familiarity with Mobile IP [RFC 2002], IPCP [RFC 1332], and PPP [RFC 1661] is assumed. [STANDARDS-TRACK]

在PPP的IPCP阶段传达他们对移动IP的支持。假设熟悉移动IP[RFC 2002]、IPCP[RFC 1332]和PPP[RFC 1661]。[标准-轨道]

2289 Haller Feb 1998 A One-Time Password System

2289 Haller 1998年2月一次性密码系统

This document describes a one-time password authentication system (OTP). The system provides authentication for system access (login) and other applications requiring authentication that is secure against passive attacks based on replaying captured reusable passwords. [STANDARDS-TRACK]

本文档描述了一次性密码认证系统（OTP）。系统为系统访问（登录）和其他需要身份验证的应用程序提供身份验证，该身份验证可防止基于重放捕获的可重用密码的被动攻击。[标准-轨道]

2288 Lynch Feb 1998 Using Existing Bibliographic Identifiers as Uniform Resource Names

2288 Lynch 1998年2月使用现有书目标识符作为统一资源名称

This document discusses how three major bibliographic identifiers (the ISBN, ISSN and SICI) can be supported within the URN framework and the currently proposed syntax for URNs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文档讨论了如何在URN框架内支持三个主要的书目标识符（ISBN、ISSN和SICI）以及当前建议的URN语法。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2287 Krupczak Feb 1998 Definitions of System-Level Managed Objects for Applications

2287 Krupczak 1998年2月应用程序系统级托管对象的定义

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a basic set of managed objects for fault, configuration and performance management of applications from a systems perspective. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了一组基本的托管对象，用于从系统角度对应用程序进行故障、配置和性能管理。[标准-轨道]

2286 Kapp Feb 1998 Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128

2286 Kapp 1998年2月HMAC-RIPEMD160和HMAC-RIPEMD128的测试用例

This document provides two sets of test cases for HMAC-RIPEMD160 and HMAC-RIPEMD128. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文档为HMAC-RIPEMD160和HMAC-RIPEMD128提供了两套测试用例。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2285 Mandeville Feb 1998 Benchmarking Terminology for LAN Switching Devices

2285 Mandeville 1998年2月LAN交换设备基准术语

This document is intended to provide terminology for the benchmarking of local area network (LAN) switching devices. It extends the terminology already defined for benchmarking network interconnect devices in RFCs 1242 and 1944 to switching devices. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文件旨在为局域网（LAN）交换设备的基准测试提供术语。它将RFCs 1242和1944中为基准网络互连设备定义的术语扩展到交换设备。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2284 Blunk Mar 1998 PPP Extensible Authentication Protocol (EAP)

2284布伦克1998年3月PPP可扩展认证协议（EAP）

The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link. This document defines the PPP Extensible Authentication Protocol. [STANDARDS-TRACK]

点到点协议（PPP）提供了通过点到点链路传输多协议数据报的标准方法。PPP还定义了一个可扩展的链路控制协议，该协议允许在允许网络层协议通过链路传输之前协商用于认证其对等方的认证协议。本文档定义了PPP可扩展身份验证协议。[标准-轨道]

2283 Bates Feb 1998 Multiprotocol Extensions for BGP-4

2283 Bates 1998年2月BGP-4的多协议扩展

This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK]

本文档定义了BGP-4的扩展，使其能够承载多个网络层协议（如IPv6、IPX等）的路由信息。扩展是向后兼容的-支持扩展的路由器可以与不支持扩展的路由器进行互操作。[标准-轨道]

2282 Galvin Feb 1998 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees

2282 Galvin 1998年2月IAB和IESG选择、确认和召回流程：提名和召回委员会的运作

The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

规定了选择、确认和召回IAB和IESG成员的流程。本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。

2281 Li Mar 1998 Cisco Hot Standby Router Protocol (HSRP)

2281年3月1998思科热备用路由器协议（HSRP）

The memo specifies the Hot Standby Router Protocol (HSRP). The goal of the protocol is to allow hosts to appear to use a single router and to maintain connectivity even if the actual first hop router they are using fails. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

备忘录指定了热备用路由器协议（HSRP）。该协议的目标是允许主机看起来使用单个路由器，并在实际使用的第一跳路由器出现故障时保持连接。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2280 Alaettinoglu Jan 1998 Routing Policy Specification Language (RPSL)

2280 Alaettinoglu 1998年1月路由策略规范语言（RPSL）

This memo is the reference document for the Routing Policy Specification Language (RPSL). RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK]

本备忘录是路由策略规范语言（RPSL）的参考文档。RPSL允许网络运营商能够在Internet层次结构的各个级别指定路由策略；例如，在自治系统（AS）级别。同时，可以在RPSL中详细指定策略，以便从中生成低级路由器配置。RPSL是可扩展的；可以随时引入新的路由协议和新的协议功能。[标准-轨道]

2279 Yergeau Jan 1998 UTF-8, a transformation format of ISO 10646

2279 Yergeau 1998年1月UTF-8，ISO 10646的转换格式

UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo updates and replaces RFC 2044, in particular addressing the question of versions of the relevant standards. [STANDARDS-TRACK]

本备忘录的对象UTF-8的特点是保留完整的US-ASCII范围，提供与依赖US-ASCII值但对其他值透明的文件系统、解析器和其他软件的兼容性。本备忘录更新并取代RFC 2044，特别是解决了相关标准的版本问题。[标准-轨道]

2278 Freed Jan 1998 IANA Charset Registration Procedures

2278 1998年1月发布IANA字符集注册程序

MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

MIME[RFC-2045、RFC-2046、RFC-2047、RFC-2184]和各种其他现代互联网协议能够使用许多不同的字符集。这反过来意味着标记不同字符集的能力至关重要。此注册过程仅用于将一个或多个特定名称与给定的字符集相关联，并指示是否可以在MIME文本对象中使用给定的字符集。本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。

2277 Alvestrand Jan 1998 IETF Policy on Character Sets and Languages

2277 Alvestrand 1998年1月IETF字符集和语言政策

This document is the current policies being applied by the Internet Engineering Steering Group (IESG) towards the standardization efforts in the Internet Engineering Task Force (IETF) in order to help Internet protocols fulfill these requirements. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

本文件是互联网工程指导小组（IESG）对互联网工程任务组（IETF）的标准化工作所采用的现行政策，以帮助互联网协议满足这些要求。本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。

2276 Sollins Jan 1998 Architectural Principles of Uniform Resource Name Resolution

2276 Sollins 1998年1月统一资源名称解析的体系结构原则

This document addresses the issues of the discovery of URN (Uniform Resource Name) resolver services that in turn will directly translate URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource Characteristics). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文档讨论了URN（统一资源名称）解析程序服务的发现问题，这些服务将直接将URN转换为URL（统一资源定位器）和URC（统一资源特征）。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2275 Wijnen Jan 1998 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

2275 Wijnen 1998年1月用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）

This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK]

本文档描述了SNMP体系结构[RFC2261]中使用的基于视图的访问控制模型。它定义了控制管理信息访问的程序要素。本文档还包括一个MIB，用于远程管理基于视图的访问控制模型的配置参数。[标准-轨道]

2274 Blumenthal Jan 1998 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

2274 Blumenthal 1998年1月用于简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）

This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. [STANDARDS-TRACK]

本文档描述了用于SNMP体系结构[RFC2261]的SNMP版本3的基于用户的安全模型（USM）。它定义了用于提供SNMP消息级安全性的过程元素。本文档还包括一个MIB，用于远程监视/管理此安全模型的配置参数。[标准-轨道]

2273 Levi Jan 1998 SNMPv3 Applications

2273 Levi 1998年1月SNMPv3应用

This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK]

本备忘录描述了使用[RFC2261]中所述SNMP引擎的五种类型的SNMP应用程序。所描述的应用程序类型包括命令生成器、命令响应器、通知发起者、通知接收者和代理转发器。此备忘录还定义了MIB模块，用于指定管理操作的目标、通知筛选和代理转发。[标准-轨道]

2272 Case Jan 1998 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)

2272案例1998年1月简单网络管理协议（SNMP）的消息处理和调度

This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2271]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK]

本文档描述了SNMP体系结构[RFC2271]中SNMP消息的消息处理和调度。它定义了将可能多个版本的SNMP消息分派到适当的SNMP消息处理模型以及将PDU分派到SNMP应用程序的过程。本文档还描述了一种消息处理模型——SNMPv3消息处理模型。[标准-轨道]

2271 Harrington Jan 1998 An Architecture for Describing SNMP Management Frameworks

2271 Harrington Jan 1998用于描述SNMP管理框架的体系结构

This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. [STANDARDS-TRACK]

本文档描述了用于描述SNMP管理框架的体系结构。该体系结构设计为模块化，以允许SNMP协议标准随着时间的推移而演变。[标准-轨道]

2270 Stewart Jan 1998 Using a Dedicated AS for Sites Homed to a Single Provider

2270 Stewart 1998年1月使用专用AS，用于单一提供商的网站

With the increased growth of the Internet, the number of customers using BGP4 has grown significantly. RFC1930 outlines a set of guidelines for when one needs and should use an AS. However, the customer and service provider (ISP) are left with a problem as a result of this in that while there is no need for an allocated AS under the guidelines, certain conditions make the use of BGP4 a very pragmatic and perhaps only way to connect a customer homed to a single ISP. This paper proposes a solution to this problem in line with recommendations set forth in RFC1930. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

随着互联网的增长，使用BGP4的客户数量显著增加。RFC1930概述了一套关于何时需要和应该使用AS的指南。然而，客户和服务提供商（ISP）因此存在一个问题，即虽然不需要按照指南分配，但某些条件使得使用BGP4成为非常实用的，并且可能是将客户与单个ISP连接的唯一方式。本文根据RFC1930中提出的建议，提出了该问题的解决方案。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2269 Armitage Jan 1998 Using the MARS Model in non-ATM NBMA Networks

2269 Armitage 1998年1月在非ATM NBMA网络中使用MARS模型

This document is intended to state the obvious equivalences, and explain the less obvious implications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文件旨在说明明显的等效性，并解释不太明显的含义。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2268 Rivest Mar 1998 A Description of the RC2(r) Encryption Algorithm

2268 Rivest 1998年3月RC2（r）加密算法说明

This memo describes a conventional (secret-key) block encryption algorithm, called RC2, which may be considered as a proposal for a DES replacement. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本备忘录描述了一种称为RC2的传统（密钥）块加密算法，可将其视为DES替代方案。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2267 Ferguson Jan 1998 Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing

2267 Ferguson 1998年1月网络入口过滤：击败使用IP源地址欺骗的拒绝服务攻击

This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文讨论了一种简单、有效和直接的方法，用于使用入口流量过滤来禁止DoS攻击，这些攻击使用伪造的IP地址从Internet服务提供商（ISP）聚合点的“后方”传播。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2266 Flick Jan 1998 Definitions of Managed Objects for IEEE 802.12 Repeater Devices

2266 Flick 1998年1月IEEE 802.12中继器设备的托管对象定义

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing network repeaters based on IEEE 802.12. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于基于TCP/IP的Internet中的网络管理协议。特别是，它定义了用于管理基于IEEE 802.12的网络中继器的对象。[标准-轨道]

2265 Wijnen Jan 1998 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

2265 Wijnen 1998年1月用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）

2264 Blumenthal Jan 1998 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

2264 Blumenthal 1998年1月用于简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）

2263 Levi Jan 1998 SNMPv3 Applications

2263 Levi 1998年1月SNMPv3应用

2262 Case Jan 1998 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)

2262案例1998年1月简单网络管理协议（SNMP）的消息处理和调度

This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2261]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK]

本文档描述了SNMP体系结构[RFC2261]中SNMP消息的消息处理和调度。它定义了将可能多个版本的SNMP消息分派到适当的SNMP消息处理模型以及将PDU分派到SNMP应用程序的过程。本文档还描述了一种消息处理模型——SNMPv3消息处理模型。[标准-轨道]

2261 Harrington Jan 1998 An Architecture for Describing SNMP Management Frameworks

2261 Harrington Jan 1998描述SNMP管理框架的体系结构

本文档描述了用于描述SNMP管理框架的体系结构。该体系结构设计为模块化，以允许SNMP协议标准随着时间的推移而演变。[标准-轨道]

2260 Bates Jan 1998 Scalable Support for Multi-homed Multi-provider Connectivity

2260 Bates 1998年1月可扩展支持多宿多提供商连接

This document describes addressing and routing strategies for multi-homed enterprises attached to multiple Internet Service Providers (ISPs) that are intended to reduce the routing overhead due to these enterprises in the global Internet routing system. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文档描述了连接到多个Internet服务提供商（ISP）的多宿企业的寻址和路由策略，旨在减少这些企业在全球Internet路由系统中的路由开销。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2259 Elliott Jan 1998 Simple Nomenclator Query Protocol (SNQP)

2259 Elliott 1998年1月简单命名查询协议（SNQP）

The Simple Nomenclator Query Protocol (SNQP) allows a client to communicate with a descriptive name service or other relational-style query service. This memo provides information for the Internet community. It does not specify an Internet standard of any kind

简单命名查询协议（SNQP）允许客户机与描述性名称服务或其他关系式查询服务通信。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准

2258 Ordille Jan 1998 Internet Nomenclator Project

2258 Ordille 1998年1月互联网命名项目

The goal of the Internet Nomenclator Project is to integrate the hundreds of publicly available CCSO servers from around the world. This document provides an overview of the Nomenclator system, describes how to register a CCSO server in the Internet Nomenclator Project, and how to use the Nomenclator search engine to find people on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

互联网命名项目的目标是整合来自世界各地的数百个公共CCSO服务器。本文档概述了命名系统，描述了如何在Internet Nomenclator项目中注册CCSO服务器，以及如何使用Nomenclator搜索引擎在Internet上查找用户。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2257 Daniele Jan 1998 Agent Extensibility (AgentX) Protocol Version 1

2257 Daniele 1998年1月代理扩展性（AgentX）协议版本1

This memo defines a standardized framework for extensible SNMP agents. It defines processing entities called master agents and subagents, a protocol (AgentX) used to communicate between them, and the elements of procedure by which the extensible agent processes SNMP protocol messages. [STANDARDS-TRACK]

本备忘录定义了可扩展SNMP代理的标准化框架。它定义了称为主代理和子代理的处理实体、用于它们之间通信的协议（AgentX）以及可扩展代理处理SNMP协议消息的过程元素。[标准-轨道]

2256 Wahl Dec 1997 A Summary of the X.500(96) User Schema for use with LDAPv3

2256 Wahl Dec 1997与LDAPv3一起使用的X.500（96）用户模式摘要

This document provides an overview of the attribute types and object classes defined by the ISO and ITU-T committees in the X.500 documents, in particular those intended for use by directory clients. [STANDARDS-TRACK]

本文档概述了ISO和ITU-T委员会在X.500文档中定义的属性类型和对象类，特别是目录客户端使用的属性类型和对象类。[标准-轨道]

2255 Howes Dec 1997 The LDAP URL Format

2255 Howes 1997年12月LDAP URL格式

This document describes a format for an LDAP Uniform Resource Locator. [STANDARDS-TRACK]

本文档描述LDAP统一资源定位器的格式。[标准-轨道]

2254 Howes Dec 1997 The String Representation of LDAP Search Filters

2254 Howes Dec 1997 LDAP搜索筛选器的字符串表示

This document defines a human-readable string format for representing LDAP search filters. [STANDARDS-TRACK]

本文档定义了一种人类可读的字符串格式，用于表示LDAP搜索筛选器。[标准-轨道]

2253 Wahl Dec 1997 Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names

2253 Wahl Dec 1997轻型目录访问协议（v3）：可分辨名称的UTF-8字符串表示

This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name. [STANDARDS-TRACK]

本规范定义了用于表示名称的字符串格式，该格式旨在提供常用可分辨名称的清晰表示，同时能够表示任何可分辨名称。[标准-轨道]

2252 Wahl Dec 1997 Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions

2252 Wahl Dec 1997轻型目录访问协议（v3）：属性语法定义

This document defines a set of syntaxes for LDAPv3, and the rules by which attribute values of these syntaxes are represented as octet strings for transmission in the LDAP protocol. [STANDARDS-TRACK]

本文档定义了LDAPv3的一组语法，以及将这些语法的属性值表示为八位字节字符串以在LDAP协议中传输的规则。[标准-轨道]

2251 Wahl Dec 1997 Lightweight Directory Access Protocol (v3)

2251 Wahl Dec 1997轻型目录访问协议（v3）

The protocol described in this document is designed to provide access to directories supporting the X.500 models, while not incurring the resource requirements of the X.500 Directory Access Protocol (DAP). [STANDARDS-TRACK]

本文档中描述的协议旨在提供对支持X.500型号的目录的访问，同时不产生X.500目录访问协议（DAP）的资源需求。[标准-轨道]

2250 Hoffman Jan 1998 RTP Payload Format for MPEG1/MPEG2 Video

2250 Hoffman 1998年1月MPEG1/MPEG2视频的RTP有效载荷格式

This memo describes a packetization scheme for MPEG video and audio streams. [STANDARDS-TRACK]

本备忘录描述了MPEG视频和音频流的打包方案。[标准-轨道]

2249 Freed Jan 1998 Mail Monitoring MIB

2249 1998年1月释放邮件监控MIB

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Specifically, this memo extends the basic Network Services Monitoring MIB [8] to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。具体而言，此备忘录扩展了基本网络服务监控MIB[8]，以允许监控消息传输代理（MTA）。它还可用于监视网关内的MTA组件。[标准-轨道]

2248 Freed Jan 1998 Network Services Monitoring MIB

2248 1998年1月释放网络服务监控MIB

This MIB may be used on its own for any application, and for most simple applications this will suffice. This MIB is also designed to serve as a building block which can be used in conjunction with application-specific monitoring and management. [STANDARDS-TRACK]

此MIB可以单独用于任何应用程序，对于大多数简单的应用程序，这就足够了。此MIB还被设计为一个构建块，可与特定于应用程序的监视和管理结合使用。[标准-轨道]

2247 Kille Jan 1998 Using Domains in LDAP/X.500 Distinguished Names

2247 Kille 1998年1月使用LDAP/X.500可分辨名称中的域

This document defines an algorithm by which a name registered with the Internet Domain Name Service [2] can be represented as an LDAP distinguished name. [STANDARDS-TRACK]

本文档定义了一种算法，通过该算法，向Internet域名服务[2]注册的名称可以表示为LDAP可分辨名称。[标准-轨道]

2246 Dierks Jan 1999 The TLS Protocol Version 1.0

2246 Dierks 1999年1月TLS协议版本1.0

This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. [STANDARDS-TRACK]

本文档规定了传输层安全（TLS）协议的1.0版。TLS协议提供了互联网上的通信隐私。该协议允许客户机/服务器应用程序以防止窃听、篡改或消息伪造的方式进行通信。[标准-轨道]

2245 Newman Nov 1997 Anonymous SASL Mechanism

2245纽曼1997年11月匿名SASL机制

As plaintext login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the SASL [SASL] framework. [STANDARDS-TRACK]

由于新的IETF协议不允许明文登录命令，因此需要在SASL[SASL]框架的上下文中提供匿名登录的新方法。[标准-轨道]

2244 Newman Nov 1997 ACAP -- Application Configuration Access Protocol

2244 Newman 1997年11月ACAP——应用程序配置访问协议

The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information. [STANDARDS-TRACK]

应用程序配置访问协议（ACAP）旨在支持远程存储和访问程序选项、配置和首选项信息。[标准-轨道]

2243 Metz Nov 1997 OTP Extended Responses

2243 Metz 1997年11月OTP延长答复

This document provides a specification for a type of response to an OTP [RFC 1938] challenge that carries explicit indication of the response's encoding. This document also provides a specification for a response that allows an OTP generator to request that a server re-initialize a sequence and change parameters such as the secret pass phrase. [STANDARDS-TRACK]

本文档为OTP[RFC 1938]质询的一种响应类型提供了规范，该质询带有响应编码的明确指示。本文档还提供了一个响应规范，允许OTP生成器请求服务器重新初始化序列并更改密码短语等参数。[标准-轨道]

2242 Droms Nov 1997 NetWare/IP Domain Name and Information

2242 Droms 1997年11月NetWare/IP域名和信息

This document defines options that carry NetWare/IP domain name and NetWare/IP sub-options to DHCP clients. [STANDARDS-TRACK]

本文档定义了将NetWare/IP域名和NetWare/IP子选项带到DHCP客户端的选项。[标准-轨道]

2241 Provan Nov 1997 DHCP Options for Novell Directory Services

2241 Provan 1997年11月Novell目录服务的DHCP选项

This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. [STANDARDS-TRACK]

本文档定义了三个新的DHCP选项，用于向Novell目录服务的客户端传递配置信息。本文档定义了三个新的DHCP选项，用于向Novell目录服务的客户端传递配置信息。[标准-轨道]

2240 Vaughan Nov 1997 A Legal Basis for Domain Name Allocation

2240沃恩1997年11月域名分配的法律依据

The purpose of this memo is to focus discussion on the particular problems with the exhaustion of the top level domain space in the Internet and the possible conflicts that can occur when multiple organisations are vying for the same name. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本备忘录旨在集中讨论互联网顶级域名空间耗尽的特殊问题，以及多个组织争夺同一名称时可能发生的冲突。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2239 de Graaf Nov 1997 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2

2239 de Graaf 1997年11月使用SMIv2的IEEE 802.3介质连接单元（MAU）的托管对象定义

This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing 10 and 100 Mb/second Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它根据IEEE标准802.3第30节“10和100 Mb/s管理”，1995年10月26日定义了用于管理10和100 Mb/s介质连接单元（MAU）的对象。[标准-轨道]

2238 Clouston Nov 1997 Definitions of Managed Objects for HPR using SMIv2

2238 Clouston 1997年11月使用SMIv2的HPR托管对象定义

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with HPR (High Performance Routing) capabilities. This memo identifies managed objects for the HPR protocol. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了用于监视和控制具有HPR（高性能路由）功能的网络设备的对象。此备忘录标识HPR协议的托管对象。[标准-轨道]

2237 Tamaru Nov 1997 Japanese Character Encoding for Internet Messages

2237 Tamaru 1997年11月互联网信息的日语字符编码

This memo defines an encoding scheme for the Japanese Characters, describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822], and network news [RFC 1036]. Also this memo provides a listing of the

本备忘录定义了日文字符的编码方案，描述了电子邮件[RFC-822]和网络新闻[RFC 1036]中使用的“ISO-2022-JP-1”。此外，本备忘录还列出了

Japanese Character Set that can be used in this encoding scheme. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

可在此编码方案中使用的日语字符集。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2236 Fenner Nov 1997 Internet Group Management Protocol, Version 2

2236 Fenner 1997年11月互联网组管理协议，第2版

This memo documents IGMPv2, used by IP hosts to report their multicast group memberships to routers. It updates STD 5, RFC 1112. [STANDARDS-TRACK]

此备忘录记录了IP主机用来向路由器报告其多播组成员身份的IGMPv2。它更新了STD 5，RFC 1112。[标准-轨道]

2235 Zakon Nov 1997 Hobbes' Internet Timeline

2235 Zakon 1997年11月霍布斯的互联网时间表

This document presents a history of the Internet in timeline fashion, highlighting some of the key events and technologies which helped shape the Internet as we know it today. A growth summary of the Internet and some associated technologies is also included. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文档以时间轴的方式展示了互联网的历史，重点介绍了一些关键事件和技术，这些事件和技术帮助我们塑造了今天的互联网。还包括互联网和一些相关技术的增长摘要。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2234 Crocker Nov 1997 Augmented BNF for Syntax Specifications: ABNF

2234 Crocker 1997年11月扩充BNF语法规范：ABNF

In the early days of the Arpanet, each specification contained its own definition of ABNF. This included the email specifications, RFC733 and then RFC822 which have come to be the common citations for defining ABNF. The current document separates out that definition, to permit selective reference. Predictably, it also provides some modifications and enhancements. [STANDARDS-TRACK]

在Arpanet的早期，每个规范都包含其自身对ABNF的定义。这包括电子邮件规范、RFC733和RFC822，它们已成为定义ABNF的常用引用。目前的文件将该定义分离出来，以允许选择性引用。可以预见，它还提供了一些修改和增强。[标准-轨道]

2233 McCloghrie Nov 1997 The Interfaces Group MIB using SMIv2

2233 McCloghrie 1997年11月使用SMIv2的接口组MIB

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Network Interfaces. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于管理网络接口的托管对象。[标准-轨道]

2232 Clouston Nov 1997 Definitions of Managed Objects for DLUR using SMIv2

2232 Clouston 1997年11月使用SMIv2定义DLUR的托管对象

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with DLUR (Dependent LU Requester) capabilities. This memo identifies managed objects for the DLUR protocol. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了用于监视和控制具有DLUR（依赖LU请求者）功能的网络设备的对象。此备忘录标识DLUR协议的托管对象。[标准-轨道]

2231 Freed Nov 1997 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations

2231 1997年11月释放的MIME参数值和编码字扩展：字符集、语言和连续体

This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. This memo also defines an extension to the encoded words defined in RFC 2047 to allow the specification of the language to be used for display as well as the character set. [STANDARDS-TRACK]

此备忘录定义了RFC 2045介质类型和RFC 2183处置参数值机制的扩展。本备忘录还定义了对RFC 2047中定义的编码字的扩展，以允许指定用于显示的语言以及字符集。[标准-轨道]

2230 Atkinson Nov 1997 Key Exchange Delegation Record for the DNS

2230阿特金森1997年11月DNS密钥交换授权记录

This note describes a mechanism whereby authorisation for one node to act as key exchanger for a second node is delegated and made available via the Secure DNS. This mechanism is intended to be used only with the Secure DNS. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本说明描述了一种机制，其中一个节点作为第二个节点的密钥交换机的授权被委派，并通过安全DNS提供。此机制仅用于安全DNS。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2229 Faith Oct 1997 A Dictionary Server Protocol

2229一个字典服务器协议

The Dictionary Server Protocol (DICT) is a TCP transaction based query/response protocol that allows a client to access dictionary definitions from a set of natural language dictionary databases. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

字典服务器协议（DICT）是一种基于TCP事务的查询/响应协议，允许客户端从一组自然语言字典数据库访问字典定义。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2228 Horowitz Oct 1997 FTP Security Extensions

2228 Horowitz 1997年10月FTP安全扩展

This document defines extensions to the FTP specification STD 9, RFC 959, "FILE TRANSFER PROTOCOL (FTP)" (October 1985). [STANDARDS-TRACK]

本文件定义了FTP规范STD 9，RFC 959，“文件传输协议（FTP）”（1985年10月）的扩展。[标准-轨道]

2227 Mogul Oct 1997 Simple Hit-Metering and Usage-Limiting for HTTP

2227 Mogul 1997年10月HTTP的简单命中计数和使用限制

This document proposes a simple extension to HTTP, using a new "Meter" header. [STANDARDS-TRACK]

本文建议使用一个新的“Meter”头对HTTP进行一个简单的扩展。[标准-轨道]

2226 Smith Oct 1997 IP Broadcast over ATM Networks

2226 Smith 1997年10月ATM网络上的IP广播

This memo describes how the IP multicast service being developed by the IP over ATM working group may be used to support IP broadcast transmission. [STANDARDS-TRACK]

本备忘录描述了IP over ATM工作组开发的IP多播服务如何用于支持IP广播传输。[标准-轨道]

2225 Laubach Apr 1998 Classical IP and ARP over ATM

2225 Laubach 1998年4月ATM上的经典IP和ARP

This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). [STANDARDS-TRACK]

本备忘录定义了经典IP和ARP在配置为逻辑IP子网（LIS）的异步传输模式（ATM）网络环境中的初始应用。[标准-轨道]

2224 Callaghan Oct 1997 NFS URL Scheme

2224 Callaghan 1997年10月NFS URL方案

A new URL scheme, 'nfs' is defined. It is used to refer to files and directories on NFS servers using the general URL syntax defined in RFC 1738, "Uniform Resource Locators (URL)". This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

定义了一个新的URL方案“nfs”。它用于使用RFC 1738“统一资源定位器（URL）”中定义的通用URL语法引用NFS服务器上的文件和目录。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2223 Postel Oct 1997 Instructions to RFC Authors

2223 1997年10月后RFC作者须知

This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

本征求意见书（RFC）提供了有关RFC编制的信息，以及与RFC发布相关的某些政策。本备忘录为互联网社区提供信息。本备忘录未规定任何类型的互联网标准。

2222 Myers Oct 1997 Simple Authentication and Security Layer (SASL)

2222迈尔斯1997年10月简单身份验证和安全层（SASL）

This document describes a method for adding authentication support to connection-based protocols. [STANDARDS-TRACK]

本文档描述了一种向基于连接的协议添加身份验证支持的方法。[标准-轨道]

2221 Gahrns Oct 1997 IMAP4 Login Referrals

2221 Gahrns 1997年10月IMAP4登录转介

When dealing with large amounts of users and many IMAP4 [RFC-2060] servers, it is often necessary to move users from one IMAP4 server to another. Login referrals allow clients to transparently connect to an alternate IMAP4 server, if their home IMAP4 server has changed. [STANDARDS-TRACK]

在处理大量用户和多台IMAP4[RFC-2060]服务器时，通常需要将用户从一台IMAP4服务器移动到另一台IMAP4服务器。登录引用允许客户端在其主IMAP4服务器发生更改时透明地连接到备用IMAP4服务器。[标准-轨道]

2220 Guenther Oct 1997 The Application/MARC Content-type

2220 Guenther 1997年10月申请/MARC内容类型

This memorandum provides a mechanism for representing objects which are files of Machine-Readable Cataloging records (MARC). The MARC formats are standards for the representation and communication of bibliographic and related information. A MARC record contains metadata for an information resource following MARC format specifications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本备忘录提供了一种表示机器可读编目记录（MARC）文件对象的机制。MARC格式是书目和相关信息表示和交流的标准。MARC记录包含符合MARC格式规范的信息资源元数据。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2219 Hamilton Oct 1997 Use of DNS Aliases for Network Services

2219汉密尔顿1997年10月为网络服务使用DNS别名

It has become a common practice to use symbolic names (usually CNAMEs) in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to refer to network services such as anonymous FTP [RFC-959] servers, Gopher [RFC-1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers. This is desirable for a number of reasons. It provides a way of moving services from one machine to another transparently, and a mechanism by which people or agents may programmatically discover that an organization runs, say, a World-Wide Web server. Although this approach has been almost universally adopted, there is no standards document or similar specification for these commonly used names. This document seeks to rectify this situation by gathering together the extant 'folklore' on naming conventions, and proposes a mechanism for accommodating new protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

在域名服务（DNS-[RFC-1034，RFC-1035]）中使用符号名（通常是CNAMEs）来指代网络服务，如匿名FTP[RFC-959]服务器、Gopher[RFC-1436]服务器，以及最著名的万维网HTTP[RFC-1945]服务器，这已成为一种常见做法。这是可取的，原因有很多。它提供了一种将服务从一台机器透明地移动到另一台机器的方法，以及一种机制，通过这种机制，人们或代理可以通过编程方式发现一个组织正在运行，比如说，一台万维网服务器。虽然这种方法几乎已被普遍采用，但对于这些常用名称，没有标准文件或类似规范。本文件旨在通过收集有关命名约定的现存“民间传说”来纠正这种情况，并提出一种适应新协议的机制。本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。

2218 Genovese Oct 1997 A Common Schema for the Internet White Pages Service

2218 Genovese 1997年10月互联网白页服务的通用模式

This document specifies the minimum set of core attributes of a White Pages entry for an individual and describes how new objects with those attributes can be defined and published. [STANDARDS-TRACK]

本文档指定了个人白页条目的最小核心属性集，并描述了如何定义和发布具有这些属性的新对象。[标准-轨道]

2217 Clark Oct 1997 Telnet Com Port Control Option

2217 Clark 1997年10月Telnet Com端口控制选项

This memo proposes a protocol to allow greater use of modems attached to a network for outbound dialing purposes. This memo defines an Experimental Protocol for the Internet community.

本备忘录提出了一种协议，允许更多地使用连接到网络的调制解调器进行出站拨号。这份备忘录为互联网社区定义了一个实验性协议。

2216 Shenker Sep 1997 Network Element Service Specification Template

2216申科1997年9月网元服务规范模板

This document defines a framework for specifying services provided by network elements, and available to applications, in an internetwork which offers multiple qualities of service. The document first provides some necessary context -- including relevant definitions and suggested data formats -- and then specifies a "template" which service specification documents should follow. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文档定义了一个框架，用于指定在提供多种服务质量的互联网中由网络元素提供并可供应用程序使用的服务。文档首先提供一些必要的上下文（包括相关定义和建议的数据格式），然后指定服务规范文档应该遵循的“模板”。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2215 Shenker Sep 1997 General Characterization Parameters for Integrated Service Network Elements

2215 Shenker 1997年9月综合业务网元的一般特征参数

This memo defines a set of general control and characterization parameters for network elements supporting the IETF integrated services QoS control framework. [STANDARDS-TRACK]

本备忘录为支持IETF综合服务QoS控制框架的网络元件定义了一组通用控制和特征参数。[标准-轨道]

2214 Baker Sep 1997 Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2

2214 Baker 1997年9月使用SMIv2的集成服务管理信息库保证服务扩展

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the the interface attributes defined in the Guaranteed Service of the Integrated Services Model. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于基于TCP/IP的Internet中的网络管理协议。特别是，它定义了用于管理接口属性的对象，接口属性是在集成服务模型的保证服务中定义的。[标准-轨道]

2213 Baker Sep 1997 Integrated Services Management Information Base using SMIv2

2213 Baker 1997年9月使用SMIv2的综合服务管理信息库

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于基于TCP/IP的Internet中的网络管理协议。特别是，它定义了用于管理集成服务模型中定义的接口属性的对象。[标准-轨道]

2212 Shenker Sep 1997 Specification of Guaranteed Quality of Service

2212申科1997年9月保证服务质量规范

This memo describes the network element behavior required to deliver a guaranteed service (guaranteed delay and bandwidth) in the Internet. [STANDARDS-TRACK]

本备忘录描述了在互联网上提供保证服务（保证延迟和带宽）所需的网元行为。[标准-轨道]

2211 Wroclawski Sep 1997 Specification of the Controlled-Load Network Element Service

2211 Wroclawski 1997年9月受控负荷网元服务规范

This memo specifies the network element behavior required to deliver Controlled-Load service in the Internet. [STANDARDS-TRACK]

此备忘录指定在Internet中提供受控负载服务所需的网元行为。[标准-轨道]

2210 Wroclawski Sep 1997 The Use of RSVP with IETF Integrated Services

2210 Wroclawski 1997年9月与IETF集成服务一起使用RSVP

This note describes the use of the RSVP resource reservation protocol with the Controlled-Load and Guaranteed QoS control services. [STANDARDS-TRACK]

本说明描述了RSVP资源预留协议在受控负载和保证QoS控制服务中的使用。[标准-轨道]

2209 Braden Sep 1997 Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules

2209 Braden 1997年9月资源预留协议（RSVP）——第1版消息处理规则

This memo contains an algorithmic description of the rules used by an RSVP implementation for processing messages. It is intended to clarify the version 1 RSVP protocol specification. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

此备忘录包含RSVP实现用于处理消息的规则的算法描述。旨在澄清版本1 RSVP协议规范。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2208 Mankin Sep 1997 Resource ReSerVation Protocol (RSVP) Version 1 Applicability Statement Some Guidelines on Deployment

2208曼金1997年9月资源保留协议（RSVP）第1版适用性声明一些部署指南

This document describes the applicability of RSVP along with the Integrated Services protocols and other components of resource reservation and offers guidelines for deployment of resource reservation at this time. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本文档描述了RSVP以及集成服务协议和资源预留的其他组件的适用性，并提供了此时部署资源预留的指南。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2207 Berger Sep 1997 RSVP Extensions for IPSEC Data Flows

2207 Berger 1997年9月IPSEC数据流的RSVP扩展

This document presents extensions to Version 1 of RSVP. These extensions permit support of individual data flows using RFC 1826, IP Authentication Header (AH) or RFC 1827, IP Encapsulating Security Payload (ESP). [STANDARDS-TRACK]

本文档提供了RSVP版本1的扩展。这些扩展允许使用RFC1826、IP认证头（AH）或RFC1827、IP封装安全负载（ESP）支持单个数据流。[标准-轨道]

2206 Baker Sep 1997 RSVP Management Information This memo defines a portion of

2206贝克1997年9月RSVP管理信息本备忘录定义了

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Resource Reservation Protocol (RSVP) within the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK]

此备忘录定义了管理信息库（MIB）的一部分，用于基于TCP/IP的Internet中的网络管理协议。特别是，它在集成服务模型中定义的接口属性中定义了用于管理资源预留协议（RSVP）的对象。[标准-轨道]

2205 Braden Sep 1997 Resource ReSerVation Protocol (RSVP)--Version 1 Functional Specification

2205 Braden 1997年9月资源预留协议（RSVP）——第1版功能规范

This memo describes version 1 of RSVP, a resource reservation setup protocol designed for an integrated services Internet. RSVP provides receiver-initiated setup of resource reservations for multicast or unicast data flows, with good scaling and robustness properties. [STANDARDS-TRACK]

本备忘录描述了RSVP的第1版，RSVP是一种为综合服务互联网设计的资源预留设置协议。RSVP为多播或单播数据流提供由接收方发起的资源预留设置，具有良好的可扩展性和鲁棒性。[标准-轨道]

2204 Nash Sep 1997 ODETTE File Transfer Protocol

2204 Nash 1997年9月ODETTE文件传输协议

This memo describes a file transfer protocol to facilitate electronic data interchange between trading partners. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

本备忘录描述了一种文件传输协议，以促进贸易伙伴之间的电子数据交换。本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。

2203 Eisler Sep 1997 RPCSEC_GSS Protocol Specification

2203艾斯勒1997年9月RPCSEC_GSS协议规范

This memo describes an ONC/RPC security flavor that allows RPC protocols to access the Generic Security Services Application Programming Interface (referred to henceforth as GSS-API). [STANDARDS-TRACK]

本备忘录描述了一种ONC/RPC安全特性，允许RPC协议访问通用安全服务应用程序编程接口（以下称为GSS-API）。[标准-轨道]

2202 Cheng Sep 1997 Test Cases for HMAC-MD5 and HMAC-SHA-1

2202 Cheng 1997年9月HMAC-MD5和HMAC-SHA-1的测试用例

This document provides two sets of test cases for HMAC-MD5 and HMAC-SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of the HMAC [HMAC] message authentication function using the MD5 [MD5] hash function and the SHA-1 [SHA] hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

本文档分别为HMAC-MD5和HMAC-SHA-1提供了两组测试用例。HMAC-MD5和HMAC-SHA-1是使用MD5[MD5]哈希函数和SHA-1[SHA]哈希函数的HMAC[HMAC]消息身份验证函数的两种构造。本备忘录为互联网社区提供信息。本备忘录未规定任何类型的互联网标准。

2201 Ballardie Sep 1997 Core Based Trees (CBT) Multicast Routing Architecture

2201 Ballardie Sep 1997基于核心的树（CBT）多播路由体系结构

CBT is a multicast routing architecture that builds a single delivery tree per group which is shared by all of the group's senders and receivers. This memo defines an Experimental Protocol for the Internet community.

CBT是一种多播路由体系结构，它为每个组构建一个传递树，该树由组的所有发送方和接收方共享。这份备忘录为互联网社区定义了一个实验性协议。

2200 IAB Jun 1997 INTERNET OFFICIAL PROTOCOL STANDARDS

2200 IAB 1997年6月互联网官方协议标准

A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. [STANDARDS-TRACK]

首先对标准化过程和RFC文档系列进行讨论，然后对术语进行解释。第6.2-6.10节包含标准化每个阶段的协议列表。最后是指向参考资料和联系人的指针，以获取更多信息。[标准-轨道]

Security Considerations

安全考虑

There are no security issues in this Informational RFC.

此信息RFC中没有安全问题。

Author's Address

作者地址

Alegre Ramos University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292

阿莱格雷莫斯南加州大学信息科学研究所4676海军路玛丽娜德雷，CA 90292

Phone: (310) 822-1511 EMail: ramos@isi.edu

电话：（310）822-1511电子邮件：ramos@isi.edu

Full Copyright Statement

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.

本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。