The Interpeer Project J. Finkhaeuser Interpeer 14 March 2025 Prefix Registry for PIEs PIE.f92f09.01-00 Abstract This document is a registry for prefixes used for PIE identifiers as specified in [PIE.f92f09.00]. The Interpeer Project maintains this registry as a service to the community. About This Document This document is a standard PIE and so adheres to the publishing process and naming described in [PIE.f92f09.00]. * This version is published at PIE.f92f09.01 (https://specs.interpeer.org/PIE.f92f09.01) * The latest version can be found at PIE.f92f09.01-00 (https://specs.interpeer.org/PIE.f92f09.01/PIE.f92f09.01-00) *Contributing* Responsibility for this document lies with The Interpeer Project. Source code for it can be found at https://codeberg.org/interpeer/ PIE.f92f09.01 (https://codeberg.org/interpeer/PIE.f92f09.01). Additional coordination and discussion occurs on a mailing list: * Address: interpeer@lists.interpeer.org * Archive (https://lists.interpeer.org/archives/list/ interpeer@lists.interpeer.org/) * Membership management (https://lists.interpeer.org/mailman3/lists/ interpeer.lists.interpeer.org/) Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 2 3. Inclusion Process . . . . . . . . . . . . . . . . . . . . . . 2 4. PIE Prefix Registry . . . . . . . . . . . . . . . . . . . . . 3 Finkhaeuser Informational [Page 1] PIE-prefixes March 2025 4.1. Current PIE Prefixes . . . . . . . . . . . . . . . . . . 3 4.2. Obsolete PIE Prefixes . . . . . . . . . . . . . . . . . . 3 5. Normative References . . . . . . . . . . . . . . . . . . . . 3 Copyright Notice . . . . . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction PIE identifiers start with a short, upper case ASCII letter string that determines the scope of the PIEs thus identified. As laid out in [PIE.f92f09.00], these prefixes are not "owned" by anybody. Maintaining an official registry of any kind with criteria for inclusion also would be counter to the intent of PIEs. Therefore, this registry is purely informational, and has no standardizing quality whatsoever, as would apply to any other registry of PIE prefixes. 2. Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. Where applicable, this document uses plural pronouns according to inclusive language guidelines from [IPARCH.NIST.IR.8366]. 3. Inclusion Process As yet, there is no particularly complex inclusion process. Registry PIEs must reference specifications for each entry. You can include a PIE prefix in this registry by sending an email, opening a pull request on this document's repository, or contacting the Interpeer Project by any other means. We just require a few pieces of information: * The prefix to register. * A PIE identifier referring to a document that explains the scope of the prefix in detail. * A _very brief_ summary of that scope, ideally in a sentence or less. Finkhaeuser Informational [Page 2] PIE-prefixes March 2025 4. PIE Prefix Registry To comply with [PIE.f92f09.00], this document must distinguish between prefixes currently in use, and obsolete prefixes. 4.1. Current PIE Prefixes +========+===================+==========================+ | Prefix | Defining document | Scope summary | +========+===================+==========================+ | PIE | [PIE.f92f09.00] | Used for PIEs related to | | | | the Interpeer Project. | +--------+-------------------+--------------------------+ Table 1: Current PIE Prefixes 4.2. Obsolete PIE Prefixes _There are no obsolete PIE prefixes yet._ 5. Normative References [IPARCH.NIST.IR.8366] Miller, K., Alderman, D., Carnahan, L., Chen, L., Foti, J., Goldstein, B., Hogan, M., Marshall, J., Reczek, K. K., Rioux, N., Theofanos, M. F., Wollman, D., and National Institute of Standards and Technology (U.S.), "Guidance for NIST staff on using inclusive language in documentary standards", NIST IR (Interagency/Internal Reports) 8366, DOI 10.6028/NIST.IR.8366, 29 April 2021, . Archived copy; this document has been withdrawn by NIST due to Executive Order (E.O.) 14151 (https://www.federalregister.gov/d/2025-01953) of the President of the United States of America. [PIE.f92f09.00] Finkhaeuser, J., "PIEs - Proposals for Interpeer Enhancement", PIE PIE.f92f09.00-00, 14 March 2025, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Finkhaeuser Informational [Page 3] PIE-prefixes March 2025 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . Copyright Notice Copyright (C) the document authors. This work is licensed under a CreativeCommons Attribution-ShareAlike 4.0 International License (https://creativecommons.org/licenses/by- sa/4.0/). Author's Address Jens Finkhäuser Interpeer gUG (haftungsbeschraenkt) Email: ietf@interpeer.org URI: https://interpeer.org/ Finkhaeuser Informational [Page 4]