Workgroup:
The Interpeer Project
Published:
Author:
J. Finkhaeuser
Interpeer
Alternatives:
pdf
txt
xml
Versions:
00

Prefix Registry for PIEs

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

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.

Additional coordination and discussion occurs on a mailing list:

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.

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

Table 1: Current PIE Prefixes
Prefix Defining document Scope summary
PIE [PIE.f92f09.00] Used for PIEs related to the Interpeer Project.

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, , <https://specs.interpeer.org/archive/NIST.IR.8366.pdf>. Archived copy; this document has been withdrawn by NIST due to Executive Order (E.O.) 14151 of the President of the United States of America.
[PIE.f92f09.00]
Finkhaeuser, J., "PIEs - Proposals for Interpeer Enhancement", PIE PIE.f92f09.00-00, , <https://specs.interpeer.org/PIE.f92f09.00/PIE.f92f09.00-00>.
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.

Author's Address

Jens Finkhäuser
Interpeer gUG (haftungsbeschraenkt)
URI: https://interpeer.org/