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 © The Internet Society (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.

Table of Contents

1.  Introduction
2.  Practice
3.  Security Considerations
4.  References
Appendix A.  Acknowledgements
Appendix B.  IANA Considerations
§  Author's Address
§  Intellectual Property and Copyright Statements

1.  Introduction

Each BEEP profile (Rose, M., “The Blocks Extensible Exchange Protocol Core,” March 2001.) [1] is identified by a URI (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifiers (URI): Generic Syntax,” August 1998.) [2]. The BEEP specification uses URIs to identify a BEEP profile both:

• statically, when a profile is formally defined (RFC 3080's Section 5.1); and,
• dynamically, during channel management (RFC 3080's Section 2.3.1).

If the BEEP profile appears on the standards-track (Hovey, R. and S. Bradner, “The Organizations Involved in the IETF Standards Process,” October 1996.) [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.

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.

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.

2.  Practice

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

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").

For example,

    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.

Following this, the working group chair completes a BEEP profile registration template, and submits this information to the 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.

3.  Security Considerations

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.

4. References

Appendix A.  Acknowledgements

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

Appendix B.  IANA Considerations

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] (Rose, M., “The Blocks Extensible Exchange Protocol Core,” March 2001.).

Note that unlike the registration procedures defined in Appendix B of [1] (Rose, M., “The Blocks Extensible Exchange Protocol Core,” March 2001.), the working group chair (instead of the IESG) is responsible for authorizing the registration.

Author's Address

Full Copyright Statement

Copyright © The Internet Society (2002).

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.

Intellectual Property

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.

Acknowledgment

Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).