Network Working Group                                            M. Rose
Request for Comments: 3349                  Dover Beach Consulting, Inc.
BCP: 59                                                        July 2002
Category: Best Current Practice
        
Network Working Group                                            M. Rose
Request for Comments: 3349                  Dover Beach Consulting, Inc.
BCP: 59                                                        July 2002
Category: Best Current Practice

A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force

一个临时前缀，用于识别互联网工程任务组工作组正在开发的配置文件

Status of this Memo

本备忘录的状况

This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.

本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (2002). All Rights Reserved.

版权所有（C）互联网协会（2002年）。版权所有。

Abstract

摘要

As a part of their deliverables, working groups of the IETF may develop BEEP profiles. During the development process, it is desirable to assign a transient identifier to each profile. If the profile is subsequently published as an RFC, then a permanent identifier is subsequently assigned by the IANA.

作为可交付成果的一部分，IETF的工作组可以开发BEEP配置文件。在开发过程中，希望为每个概要文件分配一个临时标识符。如果概要文件随后发布为RFC，则IANA随后会分配一个永久标识符。

Table of Contents

目录 

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Practice . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
       References . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   A.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  5
   B.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
       Author's Address . . . . . . . . . . . . . . . . . . . . . . .  5
       Full Copyright Statement . . . . . . . . . . . . . . . . . . .  6
        
   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Practice . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
       References . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   A.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  5
   B.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
       Author's Address . . . . . . . . . . . . . . . . . . . . . . .  5
       Full Copyright Statement . . . . . . . . . . . . . . . . . . .  6
1. Introduction
1. 介绍

Each BEEP profile [1] is identified by a URI [2]. The BEEP specification uses URIs to identify a BEEP profile both:

每个蜂鸣配置文件[1]都由URI[2]标识。BEEP规范使用URI识别BEEP配置文件，包括：

o statically, when a profile is formally defined (RFC 3080's Section 5.1); and,

o 静态地，当正式定义外形时（RFC 3080第5.1节）；和

o dynamically, during channel management (RFC 3080's Section 2.3.1).

o 在通道管理期间（RFC 3080的第2.3.1节）动态进行。

If the BEEP profile appears on the standards-track [3], then the IANA is responsible for assigning the URI associated with the BEEP profile. Otherwise, the entity specifying the BEEP profile is free to assign a URI under its administration to the profile.

如果蜂鸣配置文件出现在标准轨道[3]上，则IANA负责分配与蜂鸣配置文件关联的URI。否则，指定BEEP配置文件的实体可以自由地将其管理下的URI分配给该配置文件。

If a working group of the IETF is developing a BEEP profile, then, during the development process, it is desirable to use a transient identifier for the profile. Further, it is desirable that the transient identifier be associated with the working group.

如果IETF的一个工作组正在开发一个BEEP配置文件，那么，在开发过程中，最好为该配置文件使用一个瞬态标识符。此外，希望瞬态标识符与工作组相关联。

This memo defines the practice for making such an assignment. Note that this practice does not apply to activities outside of working groups -- anyone able to assign a URL is capable of defining a URI for the purposes of identifying the BEEP profiles that they develop.

本备忘录规定了进行此类分配的实践。请注意，这种做法不适用于工作组之外的活动——任何能够分配URL的人都能够定义URI，以便识别他们开发的BEEP配置文件。

2. Practice
2. 实践

When a working group is formed, the IETF secretariat assigns a brief mnemonic prefix to the working group, e.g., "provreg" or "sacred".

当工作组成立时，IETF秘书处为工作组分配一个简短的助记符前缀，例如“provreg”或“神圣”。

When a working group begins development of a document which specifies a BEEP profile, the working group chair assigns a transient identifier of the form "http://iana.org/beep/transient/XXX/YYY" where "XXX" is the working group's mnemonic and "YYY" is a unique string. Although the resulting URI must conform to the URI syntax, the "YYY" portion is otherwise arbitrary. For example, it may contain a sub-hierarchy (e.g., "epp/1.0").

当一个工作组开始开发一个指定蜂鸣音配置文件的文档时，工作组主席会分配一个表格的临时标识符“http://iana.org/beep/transient/XXX/YYY其中“XXX”是工作组的助记符，“YYY”是唯一的字符串。尽管生成的URI必须符合URI语法，“YYY”部分在其他方面是任意的。例如，它可能包含一个子层次结构（例如，“epp/1.0”）。

For example,

例如 

       http://iana.org/beep/transient/provreg/epp/1.0
       http://iana.org/beep/transient/sacred/pdm
        
       http://iana.org/beep/transient/provreg/epp/1.0
       http://iana.org/beep/transient/sacred/pdm

might be assigned by the chairs of the "provreg" and "sacred" working groups, respectively.

可能分别由“provreg”和“神圣”工作组的主席指定。

Following this, the working group chair completes a BEEP profile registration template, and submits this information to the IANA.

在此之后，工作组主席完成一个BEEP配置文件注册模板，并将此信息提交给IANA。

Note that although the IETF hasn't established a practice with respect to the use of capitalization in URLs employed for namespace purposes, the W3C has a lowercase-only policy. Working group chairs are encouraged to consider this when making assignments.

请注意，尽管IETF还没有建立一个在用于名称空间的URL中使用大写的实践，W3C有一个只使用小写的策略。工作组主席鼓励在分配作业时考虑这一点。

3. Security Considerations
3. 安全考虑

This document describes an administrative convention and raises no additional security considerations. Of course, each BEEP-based protocol has its own set of security considerations, which should be described in the relevant specification.

本文档描述了一种管理约定，没有提出其他安全注意事项。当然，每个基于BEEP的协议都有自己的一组安全注意事项，应该在相关规范中加以说明。

References

工具书类

[1] Rose, M., "The Blocks Extensible Exchange Protocol Core", RFC 3080, March 2001.

[1] Rose，M.，“块可扩展交换协议核心”，RFC 30802001年3月。

[2] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.

[2] Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。

[3] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996.

[3] Hovey，R.和S.Bradner，“参与IETF标准过程的组织”，BCP 11，RFC 2028，1996年10月。

Appendix A. Acknowledgements
附录A.确认书

The author gratefully acknowledges the contributions of: Dan Kohn and Bob Wyman.

作者感谢Dan Kohn和Bob Wyman的贡献。

Appendix B. IANA Considerations
附录B.IANA考虑事项

The IANA maintains a registry of transient identifiers used for BEEP profiles under development in the IETF, using the profile registration template defined in Section 5.1 of [1].

IANA使用[1]第5.1节中定义的配置文件注册模板，维护IETF中正在开发的BEEP配置文件使用的瞬态标识符注册表。

Note that unlike the registration procedures defined in Appendix B of [1], the working group chair (instead of the IESG) is responsible for authorizing the registration.

请注意，与[1]附录B中定义的注册程序不同，工作组主席（而非IESG）负责授权注册。

Author's Address

作者地址

Marshall T. Rose Dover Beach Consulting, Inc. POB 255268 Sacramento, CA 95865-5268 US

马歇尔T.罗斯多佛海滩咨询公司POB 255268萨克拉门托，加利福尼亚州95865-5268美国 

   Phone: +1 916 483 8878
   EMail: mrose@dbc.mtview.ca.us
        
   Phone: +1 916 483 8878
   EMail: mrose@dbc.mtview.ca.us

Full Copyright Statement

完整版权声明

Copyright (C) The Internet Society (2002). All Rights Reserved.

版权所有（C）互联网协会（2002年）。版权所有。

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

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

Acknowledgement

确认

Funding for the RFC Editor function is currently provided by the Internet Society.

RFC编辑功能的资金目前由互联网协会提供。