Network Working Group C. Lynch
Request for Comments: 2288 Coalition for Networked Information
Category: Informational C. Preston
Preston & Lynch
R. Daniel
Los Alamos National Laboratory
February 1998
Network Working Group C. Lynch
Request for Comments: 2288 Coalition for Networked Information
Category: Informational C. Preston
Preston & Lynch
R. Daniel
Los Alamos National Laboratory
February 1998
Using Existing Bibliographic Identifiers as Uniform Resource Names
使用现有书目标识符作为统一资源名称
Status of this Memo
本备忘录的状况
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.
版权所有（C）互联网协会（1998年）。版权所有。
Abstract
摘要
A system for Uniform Resource Names (URNs) must be capable of supporting identifiers from existing widely-used naming systems. 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.
统一资源名（URN）系统必须能够支持现有广泛使用的命名系统的标识符。本文档讨论了如何在URN框架内支持三个主要的书目标识符（ISBN、ISSN和SICI）以及当前建议的URN语法。
The ongoing work of several IETF working groups, most recently in the Uniform Resource Names working group, has culminated the development of a syntax for Uniform Resource Names (URNs). The functional requirements and overall framework for Uniform Resource Names are specified in RFC 1737 [Sollins & Masinter] and the specification for the URN syntax is RFC 2141 [Moats].
几个IETF工作组正在进行的工作，最近是在统一资源名称工作组中，最终开发了统一资源名称（URN）语法。RFC 1737[Sollins&Masinter]中规定了统一资源名称的功能要求和总体框架，URN语法规范为RFC 2141[Moats]。
As part of the validation process for the development of URNs the IETF working group has agreed that it is important to demonstrate that the current URN syntax proposal can accommodate existing identifiers from well established namespaces. One such infrastructure for assigning and managing names comes from the bibliographic community. Bibliographic identifiers function as names for objects that exist both in print and, increasingly, in electronic formats. This memo demonstrates the feasibility of supporting three
作为URN开发验证过程的一部分，IETF工作组一致认为，重要的是证明当前URN语法提案可以容纳来自成熟名称空间的现有标识符。其中一个用于分配和管理名称的基础设施来自书目社区。书目标识符的功能是为印刷品和越来越多的电子格式的对象命名。这份备忘录证明了支持三个项目的可行性
representative bibliographic identifiers within the currently proposed URN framework and syntax.
当前提议的URN框架和语法中具有代表性的书目标识符。
Note that this document does not purport to define the "official" standard way of moving these bibliographic identifiers into URNs; it merely demonstrates feasibility. It has not been developed in consultation with these standards bodies and maintenance agencies that oversee the existing bibliographic identifiers. Any actual Internet standard for encoding these bibliographic identifiers as URNs will need to be developed in consultation with the responsible standards bodies and maintenance agencies.
请注意，本文件无意定义将这些书目标识符移动到URN中的“官方”标准方式；它只是证明了可行性。未与这些标准机构和监督现有书目标识符的维护机构协商制定。将这些书目标识符编码为URN的任何实际互联网标准都需要与负责的标准机构和维护机构协商制定。
In addition, there are several open questions with regard to the management and registry of Namespace Identifiers (NIDs) for URNs. For purposes of illustration, we have used the three NIDs "ISBN", "ISSN" and "SICI" for the three corresponding bibliographic identifiers discussed in this document. While we believe this to be the most appropriate choice, it is not the only one. The NIDs could be based on the standards body and standard number (e.g. "US-ANSI-NISO-Z39.56-1997" rather than "SICI"). Alternatively, one could lump all bibliographic identifiers into a single "BIBLIOGRAPHIC" name space, and structure the namespace-specific string to specify which identifier is being used. Any final resolution of this must wait for the outcome of namespace management discussions in the working group and the broader IETF community.
此外，关于URN的名称空间标识符（NID）的管理和注册，还有几个悬而未决的问题。为了便于说明，我们使用了三个NID“ISBN”、“ISSN”和“SICI”作为本文件中讨论的三个相应的书目标识符。虽然我们认为这是最合适的选择，但它不是唯一的选择。NID可基于标准机构和标准编号（例如“US-ANSI-NISO-Z39.56-1997”而非“SICI”）。或者，可以将所有书目标识符组合到一个“书目”名称空间中，并构造特定于名称空间的字符串以指定正在使用的标识符。对此的任何最终解决方案都必须等待工作组和更广泛的IETF社区中命名空间管理讨论的结果。
For the purposes of this document, we have selected three major bibliographic identifiers (national and international) to fit within the URN framework. These are the International Standard Book Number (ISBN) [ISO1], the International Standard Serials Number (ISSN) [NISO1,ISO2, ISO3], and the Serial Item and Contribution Identifier (SICI) [NISO2]. An ISBN is used to identify a monograph (book). An ISSN is used to identify serial publications (journals, newspapers) as a whole. A SICI augments the ISSN in order to identify individual issues of serial publications, or components within those issues (such as an individual article, or the table of contents of a given issue). The ISBN and ISSN are defined in the United States by standards issued by the National Information Standards Organization (NISO) and also by parallel international standards issued under the auspices of the International Organization for Standardization (ISO). NISO is the ANSI-accredited standards body serving libraries, publishers and information services. The SICI code is defined by a NISO document in the United States and does not have a parallel international standards document at present.
为了本文件的目的，我们选择了三种主要的书目标识符（国家和国际），以适应URN框架。这些是国际标准书号（ISBN）[ISO1]、国际标准系列号（ISSN）[NISO1、ISO2、ISO3]和系列项目和贡献标识符（SICI）[NISO2]。ISBN用于识别专著（书）。ISSN用于整体识别系列出版物（期刊、报纸）。SICI对ISSN进行了扩充，以识别系列出版物的个别问题，或这些问题中的组成部分（如个别文章或给定问题的目录）。ISBN和ISSN在美国由国家信息标准组织（NISO）发布的标准以及由国际标准化组织（ISO）主持发布的平行国际标准定义。NISO是ANSI认证的标准机构，为图书馆、出版商和信息服务机构提供服务。SICI规范由美国的NISO文件定义，目前没有平行的国际标准文件。
Many other bibliographic identifiers are in common use (for example, CODEN, numbers assigned by major bibliographic utilities such as OCLC and RLG, national library numbers such as the Library of Congress Control Number) or are under development. While we do not discuss them in this document, many of these will also need to be supported within the URN framework as it moves to large scale implementation. The issues involved in supporting those additional identifiers are anticipated to be broadly similar to those involved in supporting ISBNs, ISSNs, and SICIs.
许多其他书目标识符已被普遍使用（例如，CODEN、主要书目实用程序（如OCLC和RLG）分配的编号、国家图书馆编号（如国会图书馆控制编号）或正在开发中。虽然我们在本文档中没有讨论这些问题，但随着URN框架向大规模实施的发展，其中许多问题也需要在URN框架内得到支持。支持这些额外标识符所涉及的问题预计与支持ISBN、ISSN和SICI所涉及的问题大致相似。
It is important to distinguish between the resource identified by a URN and the resources a URN resolver that can reasonably return when attempting to resolve an identifier. For example, the ISSN 0040-781X identifies the popular magazine "Time" -- all of it, every issue for from the start of publication to present. Resolving such an identifier should not result in the equivalent of hundreds of thousands of pages of text and photos being dumped to the user's machine. It is more reasonable for ISSNs to resolve to a navigational system, such as an HTML-based search form, so the user may select issues or articles of interest. ISBNs and SICIs, on the other hand, do identify finite, manageably-sized objects, but these objects may still be large enough that resolution to a hierarchical system is appropriate.
区分URN标识的资源和URN解析程序在尝试解析标识符时可以合理返回的资源是很重要的。例如，ISSN 0040-781X识别了流行杂志《时代》——从出版之初到现在的每一期。解析这样一个标识符不应该导致成千上万页的文本和照片被转储到用户的机器上。对于ISSNs来说，将其解析为导航系统（例如基于HTML的搜索表单）更为合理，因此用户可以选择感兴趣的问题或文章。另一方面，ISBN和SICI确实可以识别有限的、可管理大小的对象，但这些对象可能仍然足够大，以至于层次系统的分辨率是合适的。
In addition, the materials identified by an ISSN, ISBN or SICI may exist only in printed or other physical form, not electronically. The best that a resolver may be able to offer is information about where to get the physical resource, such as library holdings or a bookstore or publisher order form. The URN Framework provides resolution services that may be used to describe any differences between the resource identified by a URN and the resource that would be returned as a result of resolving that URN.
此外，ISSN、ISBN或SICI标识的材料可能仅以印刷或其他物理形式存在，而非电子形式。解析程序能够提供的最好信息是关于从何处获取物理资源的信息，例如图书馆馆藏或书店或出版商订单。URN框架提供了解析服务，可用于描述URN标识的资源与解析该URN时返回的资源之间的任何差异。
An International Standard Book Number (ISBN) identifies an edition of a monographic work. The ISBN is defined by the standard NISO/ANSI/ISO 2108:1992 [ISO1]
国际标准书号（ISBN）标识专题著作的版本。ISBN由标准NISO/ANSI/ISO 2108:1992[ISO1]定义
Basically, an ISBN is a ten-digit number (actually, the last digit can be the letter "X" as well, as described below) which is divided into four variable length parts usually separated by hyphens when printed. The parts are as follows (in this order):
基本上，ISBN是一个十位数字（实际上，最后一位数字也可以是字母“X”，如下所述），它被分成四个可变长度的部分，通常在打印时用连字符分隔。各部分如下（按此顺序）：
* a group identifier which specifies a group of publishers, based on national, geographic or some other criteria,
* 一种组标识符，根据国家、地理或某些其他标准指定一组出版商，
* the publisher identifier,
* 发布者标识符，
* the title identifier,
* 标题标识符，
* and a modulus 11 check digit, using X instead of 10.
* 和模数11校验位，使用X代替10。
The group and publisher number assignments are managed in such a way that the hyphens are not needed to parse the ISBN unambiguously into its constituent parts. However, the ISBN is normally transmitted and displayed with hyphens to make it easy for human beings to recognize these parts without having to make reference to or have knowledge of the number assignments for group and publisher identifiers.
组号和发行者号分配的管理方式不需要连字符就能将ISBN明确地解析为其组成部分。然而，ISBN通常通过连字符传输和显示，以便于人类识别这些部件，而无需参考或了解组和发布者标识符的编号分配。
Embedding ISBNs within the URN framework presents no particular encoding problems, since all of the characters that can appear in an ISBN are valid in the identifier segment of the URN. %-encoding, as described in [MOATS] is never needed.
在URN框架中嵌入ISBN不会出现特殊的编码问题，因为ISBN中可能出现的所有字符在URN的标识符段中都是有效的。%-不需要[护城河]中描述的编码。
Example: URN:ISBN:0-395-36341-1
Example: URN:ISBN:0-395-36341-1
For the ISBN namespace, some additional equivalence rules are appropriate. Prior to comparing two ISBN URNs for equivalence, it is appropriate to remove all hyphens, and to convert any occurrences of the letter X to upper case.
对于ISBN名称空间，一些额外的等价规则是合适的。在比较两个ISBN URN是否等效之前，应删除所有连字符，并将出现的字母X转换为大写。
The ISBN standard and related community implementation guidelines define when different versions of a work should be assigned the same or differing ISBNs. In actuality, however, practice varies somewhat depending on publisher as to whether different ISBNs are assigned for paperbound vs. hardbound versions of the same work, electronic vs. printed versions of the same work, or versions of the same work distinguished in some other way (e.g., published for example in the US and in Europe). The choice of whether to assign a new ISBN or to reuse an existing one when publishing a revised printing of an existing edition of a work or even a revised edition of a work is somewhat subjective. Practice varies from publisher to publisher (indeed, the distinction between a revised printing and a new edition is itself somewhat subjective). The use of ISBNs within the URN framework simply reflects these existing practices. Note that it is likely that an ISBN URN will often resolve to many instances of the work (many URLs).
ISBN标准和相关社区实施指南定义了不同版本的作品何时应分配相同或不同的ISBN。然而，实际上，根据出版商的不同，对于同一作品的纸质版与精装版、同一作品的电子版与印刷版，或同一作品的其他版本（例如，在美国和欧洲出版），是否分配了不同的ISBN，实践有所不同。在出版一部作品的现有版本或甚至是一部作品的修订版时，选择是分配一个新的ISBN还是重复使用一个现有的ISBN有点主观。实践因出版商而异（事实上，修订版和新版之间的区别本身就有点主观）。在URN框架中使用ISBN只是反映了这些现有实践。请注意，ISBN URN很可能会解析到许多工作实例（许多URL）。
International Standard Serials Numbers (ISSN) identify a work that is published on a continued basis in issues; they identify the entire (often open-ended, in the case of an actively published) work. ISSNs are defined by the international standards ISO 3297:1986 [ISO2] and ISO/DIS 3297 [ISO3] and within the United States by NISO Z39.9-1992 [NISO1]. The ISSN International Centre is located in Paris and coordinates a network of regional centers. The National Serials Data Program within the Library of Congress is the US Center of this network.
国际标准丛书编号（ISSN）确定连续出版的作品；它们确定了整个作品（通常是开放式的，对于积极出版的作品）。ISSN由国际标准ISO 3297:1986[ISO2]和ISO/DIS 3297[ISO3]定义，在美国由NISO Z39.9-1992[NISO1]定义。ISSN国际中心位于巴黎，协调区域中心网络。国会图书馆内的国家系列数据计划是该网络的美国中心。
ISSNs have the form NNNN-NNNN where N is a digit, the last digit may be an upper case X as the result of the check character calculation. Unlike the ISBN the ISSN components do not have much structure; blocks of numbers are passed out to the regional centers and publishers.
ISSN的格式为NNNN-NNNN，其中N是一个数字，最后一个数字可以是大写的X，作为校验字符计算的结果。与ISBN不同，ISSN的组成部分没有太多的结构；数字块被分发给区域中心和出版商。
Again, there is no problem representing ISSNs in the namespace-specific string of URNs since all characters valid in the ISSN are valid in the namespace-specific URN string, and %-encoding is never required.
同样，在特定于名称空间的URN字符串中表示ISSN没有问题，因为ISSN中的所有有效字符在特定于名称空间的URN字符串中都是有效的，并且从不需要编码。
Example: URN:ISSN:1046-8188
Example: URN:ISSN:1046-8188
Supplementary comparison rules are also appropriate for the ISSN namespace. Just as for ISBNs, hyphens should be dropped prior to comparison and occurrences of 'x' normalized to uppercase.
补充比较规则也适用于ISSN命名空间。与ISBN一样，在比较之前应删除连字符，并将“x”的出现标准化为大写。
The ISSN standard and related community implementation guidelines specify when new ISSNs should be assigned vs. continuing to use an existing one. There are some publications where practice within the bibliographic community varies from institution to institution, such as annuals or annual conference proceedings. In some cases these are treated as serials and ISSNs are used, and in some cases they are treated as monographs and ISBNs are used. For example SIGMOD Record volume 24 number 2 June 1995 contains the Proceedings of the 1995 ACM SIGMOD International Conference on Management of Data. If you subscribe to the journal (ISSN 0163-5808) this is simply the June issue. On the other hand you may have acquired this volume as the conference proceedings (a monograph) and as such would use the ISBN 0-89791-731-6 to identify the work. There are also varying practices
ISSN标准和相关社区实施指南规定了何时应分配新的ISSN，而不是继续使用现有的ISSN。在一些出版物中，书目界的做法因机构而异，如年刊或年度会议记录。在某些情况下，它们被视为连载并使用ISSN，在某些情况下，它们被视为专著并使用ISBN。例如，1995年6月2日第24卷SIGMOD记录包含1995年ACM SIGMOD数据管理国际会议记录。如果你订阅了《日刊》（ISSN 0163-5808），这就是6月号。另一方面，您可能已经获得了本卷作为会议记录（专著），因此将使用ISBN 0-89791-731-6来识别该作品。也有不同的做法
within the publishing community as to when new ISSNs are assigned due to the change in the name of a periodical (e.g. Atlantic becomes Atlantic Monthly); or when a periodical is published both in printed and electronic versions (e.g. The New York Times). The use of ISSNs in URNs will reflect these judgments and practices.
在出版界内部，由于期刊名称的变更（如《大西洋月刊》成为《大西洋月刊》）何时分配新的ISSN；或期刊同时以印刷版和电子版出版（如《纽约时报》）。在骨灰盒中使用ISSN将反映这些判断和实践。
The standard for Serial Item and Contribution Identifiers (SICI) codes, which has recently been extensively revised, is defined by NISO/ANSI Z39.56-1997 [NISO2]. The maintenance agency for the SICI code is the UnCover Corporation.
NISO/ANSI Z39.56-1997[NISO2]定义了最近经过广泛修订的序列项目和贡献标识符（SICI）代码标准。SICI代码的维护机构是UnCover公司。
SICI codes can be used to identify an issue of a serial, or a specific contribution (e.g., an article, or the table of contents) within an issue of a serial. SICI codes are not assigned, they are constructed based on information about the issue or issue component in question.
SICI代码可用于识别序列号的发行，或序列号发行中的特定贡献（如文章或目录）。未分配SICI代码，它们是基于有关问题或问题组件的信息构建的。
The complete syntax for the SICI code will not be discussed here; see
NISO/ANSI Z39.56-1997 [NISO2] for details. However, an example and
brief review of the major components is needed to understand the
relationship with the ISSN and how this identifier differs from an
ISSN. An example of a SICI code is: 0015-
6914(19960101)157:1<62:KTSW>2.0.TX;2-F
The complete syntax for the SICI code will not be discussed here; see
NISO/ANSI Z39.56-1997 [NISO2] for details. However, an example and
brief review of the major components is needed to understand the
relationship with the ISSN and how this identifier differs from an
ISSN. An example of a SICI code is: 0015-
6914(19960101)157:1<62:KTSW>2.0.TX;2-F
The first nine characters are the ISSN identifying the serial title. The second component, in parentheses, is the chronology information giving the date the particular serial issue was published. In this example that date was January 1, 1996. The third component, 157:1, is enumeration information (volume, number) for the particular issue of the serial. These three components comprise the "item segment" of a SICI code. By augmenting the ISSN with the chronology and/or enumeration information, specific issues of the serial can be identified. The next segment, <62:KTSW>, identifies a particular contribution within the issue. In this example we provide the starting page number and a title code constructed from the initial characters of the title. Identifiers assigned to a contribution can be used in the contribution segment if page numbers are inappropriate. The rest of the identifier is the control segment, which includes a check character. Interested readers are encouraged to consult the standard for an explanation of the fields in that segment.
前九个字符是识别序列标题的ISSN。括号中的第二部分是年表信息，给出了特定系列发行的日期。在这个例子中，日期是1996年1月1日。第三部分，157:1，是序列号特定版本的枚举信息（卷、号）。这三个组成部分构成SICI代码的“项目段”。通过使用年表和/或枚举信息扩充ISSN，可以识别序列号的特定问题。下一部分，<62:KTSW>，确定了问题中的特定贡献。在本例中，我们提供了起始页码和由标题的初始字符构造的标题代码。如果页码不合适，可以在贡献段中使用分配给贡献的标识符。标识符的其余部分是包含检查字符的控制段。鼓励感兴趣的读者参考本标准，了解该部分字段的解释。
The character set for SICIs is intended to be email-transport-transparent, so it does not present major problems. However, all printable excluded and reserved characters from the URN syntax are valid in the SICI character set and must be %-encoded.
SICIs的字符集旨在使电子邮件传输透明，因此不会出现重大问题。但是，URN语法中的所有可打印排除字符和保留字符在SICI字符集中都是有效的，并且必须进行编码。
Example of a SICI for an issue of a journal:
期刊发行的SICI示例：
URN:SICI:1046-8188(199501)13:1%3C%3E1.0.TX;2-F
URN:SICI:1046-8188(199501)13:1%3C%3E1.0.TX;2-F
For an article contained within that issue:
对于该期中包含的一篇文章：
URN:SICI:1046-8188(199501)13:1%3C69:FTTHBI%3E2.0.TX;2-4
URN:SICI:1046-8188(199501)13:1%3C69:FTTHBI%3E2.0.TX;2-4
Equivalence rules for SICIs are not appropriate for definition as part of the namespace and incorporation in areas such as cache management algorithms. It is best left to resolver systems which try to determine if two SICIs refer to the same content. Consequently, we do not propose any specific rules for equivalence testing through lexical manipulation.
SICI的等价规则不适合定义为命名空间的一部分，也不适合在缓存管理算法等领域合并。最好让解析器系统来确定两个SICI是否引用相同的内容。因此，我们没有提出任何通过词汇操作进行等价性测试的具体规则。
Since the serial is identified by an ISSN, some of the ambiguity currently found in the assignment of ISSNs carries over into SICI codes. In cases where an ISSN may refer to a serial that exists in multiple formats, the SICI contains a qualifier that specifies the format type (for example, print, microform, or electronic). SICI codes may be constructed from a variety of sources (the actual issue of the serial, a citation or a record from an abstracting service) and, as such are based on the principle of using all available information, so there may be multiple SICI codes representing the same article [NISO2, Appendix D]. For example, one code might be constructed with access to both chronology and enumeration (that is, date of issue and volume, issue and page number), another code might be constructed based only on enumeration information and without benefit of chronology. Systems that use SICI codes employ complex matching algorithms to try to match SICI codes constructed from incomplete information to SICI codes constructed with the benefit of all relevant information.
由于序列号由ISSN识别，目前在ISSN分配中发现的一些歧义会转移到SICI代码中。在ISSN可能指存在多种格式的序列的情况下，SICI包含一个限定符，用于指定格式类型（例如，打印、缩微或电子格式）。SICI代码可以从各种来源（序列的实际版本、引文或摘要服务的记录）构建，因此基于使用所有可用信息的原则，因此可能有多个SICI代码代表同一篇文章[NISO2，附录D]。例如，一个代码可以通过访问年表和枚举（即发行日期和卷数、发行和页码）来构造，另一个代码可以仅基于枚举信息构造，而不使用年表。使用SICI码的系统采用复杂的匹配算法，试图将由不完整信息构造的SICI码与利用所有相关信息构造的SICI码进行匹配。
This document proposes means of encoding several existing bibliographic identifiers within the URN framework. This document does not discuss resolution; thus questions of secure or authenticated resolution mechanisms are out of scope. It does not address means of validating the integrity or authenticating the source or provenance of URNs that contain bibliographic identifiers. Issues regarding intellectual property rights associated with objects identified by the various bibliographic identifiers are also beyond the scope of this document, as are questions about rights to the databases that might be used to construct resolvers.
本文件提出了在URN框架内对几个现有书目标识符进行编码的方法。本文件不讨论决议；因此，安全或认证的解决机制问题超出了范围。它不涉及验证包含书目标识符的URN的完整性或验证其来源或出处的方法。与各种书目标识符标识的对象相关的知识产权问题也超出了本文件的范围，关于可能用于构建解析器的数据库的权利问题也超出了本文件的范围。
[ISO1] NISO/ANSI/ISO 2108:1992 Information and documentation
-- International standard book number (ISBN)
[ISO2] ISO 3297:1986 Documentation -- International standard
serial numbering (ISSN)
[ISO3] ISO/DIS 3297 Information and documentation --
International standard serial numbering (ISSN) (Revision of ISO
3297:1986)
[Moats] Moats, R., "URN Syntax", RFC 2141, May 1997.
[NISO 1] NISO/ANSI Z39.9-1992 International standard serial
numbering (ISSN)
[NISO 2] NISO/ANSI Z39.56-1997 Serial Item and Contribution
Identifier
[Sollins & Masinter] Sollins, K., and L. Masinter, "Functional
Requirements for Uniform Resource Names", RFC 1737, December
1994.
[ISO1] NISO/ANSI/ISO 2108:1992 Information and documentation
-- International standard book number (ISBN)
[ISO2] ISO 3297:1986 Documentation -- International standard
serial numbering (ISSN)
[ISO3] ISO/DIS 3297 Information and documentation --
International standard serial numbering (ISSN) (Revision of ISO
3297:1986)
[Moats] Moats, R., "URN Syntax", RFC 2141, May 1997.
[NISO 1] NISO/ANSI Z39.9-1992 International standard serial
numbering (ISSN)
[NISO 2] NISO/ANSI Z39.56-1997 Serial Item and Contribution
Identifier
[Sollins & Masinter] Sollins, K., and L. Masinter, "Functional
Requirements for Uniform Resource Names", RFC 1737, December
1994.
Clifford Lynch Executive Director Coalition for Networked Information 21 Dupont Circle Washington, DC 20036
Clifford Lynch网络信息联盟执行董事21杜邦圈华盛顿特区20036
EMail: cliff@cni.org
EMail: cliff@cni.org
Cecilia Preston Preston & Lynch PO Box 8310 Emeryville, CA 94662
Cecilia Preston Preston&Lynch邮政信箱8310，加利福尼亚州埃默里维尔94662
EMail: cecilia@well.com
EMail: cecilia@well.com
Ron Daniel Jr. Advanced Computing Lab, MS B287 Los Alamos National Laboratory Los Alamos, NM, 87545
罗恩·丹尼尔高级计算实验室，MS B287洛斯阿拉莫斯国家实验室，新墨西哥州洛斯阿拉莫斯，87545
EMail: rdaniel@acl.lanl.gov
EMail: rdaniel@acl.lanl.gov
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。