RFC 3349

RFC 3349 📜✨ Title Block Tea

bestie, here's the tea 🫖. This is RFC 3349, A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force, written by M. Rose of Dover Beach Consulting, Inc. in July 2002. It's a Best Current Practice (BCP: 59), so it's the community's recommended way of doing things, not a formal protocol standard 💅. The title block doesn't say it obsoletes or updates any other documents, so it's standing on its own 🦋.

---

Status of This Memo 🌸

This document is a Best Current Practice for the Internet Community, and it's asking for discussion and suggestions for improvements. Distribution of this memo is unlimited 💖.

Copyright Notice 🎀

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

Abstract 🔥

okay so working groups at the IETF can build BEEP profiles as part of what they produce 🛠️. While they're cooking, it's really handy to give each profile a temporary identifier 🧚. If the profile later gets published as an RFC, then the IANA assigns it a permanent identifier ✨.

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 🦋

okay so every BEEP profile [1] gets identified by a URI [2] 🔗. The BEEP specification uses those URIs to identify a profile in two different ways:

• 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 shows up on the standards-track [3], then the IANA is the one responsible for assigning its URI 👑. Otherwise, the entity specifying the BEEP profile is free to assign a URI under its own administration to the profile 🌈.

If a working group of the IETF is building a BEEP profile, then, during development, it's desirable to use a transient identifier for that profile 🍓. It's also desirable that the transient identifier be associated with the working group 💜.

This memo defines the practice for making that assignment 🎀. Quick note: this practice does NOT apply to activities outside of working groups. Anyone able to assign a URL is capable of defining a URI to identify the BEEP profiles they develop 💅.

2. Practice ✨

When a working group gets formed, the IETF secretariat assigns it a brief mnemonic prefix, like "provreg" or "sacred" 🧚.

When a working group starts developing a document that 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 has to conform to the URI syntax, the "YYY" portion is otherwise arbitrary 🫶. For example, it can contain a sub-hierarchy, such as "epp/1.0" 🌈.

For example:

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

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

After that, the working group chair completes a BEEP profile registration template and submits the info to the IANA 📬.

Here's a fun little note 🙈: although the IETF hasn't set a practice for capitalization in URLs used for namespace purposes, the W3C has a lowercase-only policy. Working group chairs are encouraged to keep that in mind when making assignments 🍓.

3. Security Considerations 🔐

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

References 📖

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

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

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

Appendix A. Acknowledgements 🫶

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

Appendix B. IANA Considerations 👑

The IANA keeps 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] 📋.

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 🔥.

Author's Address 🏡

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

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

Full Copyright Statement 🌈

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

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

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

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

Acknowledgement 💖

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