bikeshed/banana/report-2021-07.txt

304 lines
13 KiB
Plaintext

Bikeshedding Microsystems
Bikeshedding Assigned Numbers Assignation and Normalization Authority
BANANA Registries Report
July 1, 2021
------------------------------------------------------------------------
Status of this Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Bikeshedding Assigned Numbers
Assignation and Normalization Authority. It represents a summary of the
state of all the registries and assignations maintainted by the BANANA.
It has been approved for publication by the Bikeshedding Engineering
Steering Group (BESG). Not all documents approved by the BESG are a
candidate for any level of Internet Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained on the Tilde
Pals mailing list.
------------------------------------------------------------------------
List of Registries
Registry Name Definition
------------------------------------------------------------ ----------
Company-Approved Advertisements [RFB1]
E-mail Signature Protocol Abbreviations [RFB1]
Known Weeds [RFB3]
Media Types [BCP13]
------------------------------------------------------------------------
Company-Approved Advertisements
Advertisements for Bikeshedding Microsystems that may be inserted by
Bikeshedders in their email signatures, depending on the Advertisement
Directives published by the Marketing Division. The Marketing Division
is the sole change controller for this registry and may change it at any
time with notice. Defined by RFB 1.
This registry is empty.
------------------------------------------------------------------------
E-mail Signature Protocol Abbreviations
Abbreviations that may be used for alternative protocols in the e-mail
signatures of Bikeshedders. This registry is maintained by ~lucidiot,
Designated Expert by interim. The Designated Expert can change this
registry at any time with notice, and Bikeshedders can submit assignment
requests to the Designated Expert. Defined by RFB 1.
Abbreviation Protocol References
------------ ---------------------------------------------- ----------
ATOM Atom Syndication Format [RFC4287]
CDF Channel Definition Format [CDF]
[CDF-W3C]
Discord Discord [DISCORD]
Fedi ActivityPub [APUB]
Gopher Internet Gopher Protocol [RFC1436]
Gemini Project Gemini [GEMINI]
HINA Asahina Antenna Metadata Format 2.2 [RFB5]
HTTP Hypertext Transfer Protocol [RFC7230]
[RFC7231]
[RFC7232]
[RFC7233]
[RFC7234]
[RFC7235]
IRC Internet Relay Chat [RFC1459]
[RFC2810]
[RFC2811]
[RFC2812]
[RFC2813]
[RFC7194]
JSON Feed JSON Feed 1.1 [JSONFEED]
LIRS Last-modified Information Relaying [RFB4]
Specification
MSN Microsoft Notification Protocol [MSNP]
RSS RDF Site Summary [RSS1]
RSS1
RSS Really Simple Syndication [RSS2]
RSS2
twtxt twtxt [TWTXT]
WEED Web Feeds [RFB3]
XMPP Extensible Messaging and Presence Protocol [RFC6120]
[RFC6121]
[RFC7622]
[RFC3923]
------------------------------------------------------------------------
Known Weeds
Any Bikeshedder can create new values by submitting a request to the
BANANA. Only the Change Controller of a value can update or remove it.
Defined by RFB 3.
URL Format Change Controller
--------------------------------------------- ------ -----------------
[REDACTED] RSS2 ~dozens
[REDACTED] RSS2 ~lucidiot
[REDACTED] ATOM ~acdw
------------------------------------------------------------------------
Media Types
This registry has been created by the Internet Engineering Task Force
and is managed by the Internet Assigned Numbers Authority. The BANANA
maintains the additional values specific to Bikeshedding Microsystems,
as per the compatibility rules of RFB 2. Defined in BCP 13.
## text/vnd.bikeshed.signature
Type name: text
Subtype name: vnd.bikeshed.signature
Required parameters: n/a
Optional parameters: charset
Encoding considerations: Prefer UTF-8. See section 3 of [RFB1].
Security considerations: See section 7 of [RFB1].
Interoperability considerations: TBD
Published specification: [RFB1]
Applications that use this media type: n/a
Additional information:
- Magic numbers: 2d 2d 20 0a
See Section 3 of [RFB1].
- File extension(s): n/a
- Macintosh file type code(s): n/a
- Fragment identifier considerations: n/a
Person & email address to contact for further information: ~lucidiot
Intended usage: Limited Use
Use of this format SHOULD be restricted to bikeshedding activities.
Restrictions on usage: Bikeshedding
Author: ~lucidiot
Change controller: ~lucidiot
------------------------------------------------------------------------
Changelog
April 4, 2021
First version of this report.
June 30, 2021
Applied BANANA Considerations from RFB 4:
- The reference for the LIRS E-mail Signature Protocol Abbreviation
has been updated to RFB 4.
July 1, 2021
Applied BANANA Considerations from RFB 5:
- The reference for the HINA E-mail Signature Protocol Abbreviation
has been updated to RFB 5.
------------------------------------------------------------------------
References
[APUB]: Lemmer Webber, C., Tallon, J., Shepherd, E., Guy, A.,
Prodromou, E., "ActivityPub", W3C Recommendation, January 2018,
<https://www.w3.org/TR/activitypub/>.
[BCP13]:
Freed, N., Klensin, J., "Multipurpose Internet Mail Extensions (MIME)
Part Four: Registration Procedures", BCP 13, RFC 4289, December 2005.
Freed, N., Klensin, J., Hansen, T., "Media Type Specifications and
Registration Procedures", BCP 13, RFC 6838, January 2013.
<https://www.rfc-editor.org/info/bcp13>
[CDF]: Microsoft, "CDF Reference for Active Channels", August 2017,
<https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa768139(v=vs.85)>.
[CDF-W3C]: Ellerman, C., "Channel Definition Format (CDF)", W3C Note
NOTE-CDFsubmit, March 1997, <https://www.w3.org/TR/NOTE-CDFsubmit.html>.
[DISCORD]: Discord, "Discord", May 2015, <https://discord.com>.
[GEMINI]: Solderpunk, "Project Gemini", Speculative specification,
v0.14.3, November 2020,
<gemini://gemini.circumlunar.space/docs/specification.gmi>.
[HINA]: kohgushi, "Asahina-Antenna meta data format version 2.2
(HINA/2.2)", Revision 0.13, July 2002,
<https://envs.net/~lucidiot/hina/hina2_2-rev0_13.html>.
[MSNP]: Mintz, M., Sayers, A., "MSN Messenger Protocol", December 2003,
<http://www.hypothetic.org/docs/msn/>.
[NOTADRAFT]: Kumari, W., "Just because it's an ID doesn't mean
anything... at all...", Work In Progress, draft-wkumari-not-a-draft-10,
July 2020.
[RFB1]: ~lucidiot, "Tildepals Email Signatures for Bikeshedders",
RFB 1, March 2021.
[RFB2]: ~lucidiot, "Ensuring Compatibility between The Bikeshedding
Company and Internet Engineering Task Force Standards", RFB 2,
April 2021.
[RFB3]: ~lucidiot, "Web Feeds", RFB 3, April 2021.
[RFB4]: ~lucidiot, "Last-modified Information Relaying Specification
(LIRS) 2.1", RFB 4, June 2021.
[RFB5]: ~lucidiot, "Asahina Antenna Metadata Format (HINA) 2.2
revision 0.13", RFB 5, July 2021.
[RFC1436]: Anklesaria, F., McCahill, M., Lindner, P., Johnson, D.,
Torrey, D., Alberti, B., "The Internet Gopher Protocol (a distributed
document search and retrieval protocol)", RFC 1436,
DOI 10.17847/RFC1436, March 1993,
<https://www.rfc-editor.org/info/rfc1436>.
[RFC1459]: Oikarinen, J., Reed, D., "Internet Relay Chat Protocol",
RFC 1459, DOI 10.17847/RFC1459, May 1993,
<https://www.rfc-editor.org/info/rfc1459>.
[RFC2810]: Kalt, C., "Internet Relay Chat: Architecture", RFC 2810,
DOI 10.17847/RFC2810, April 2000,
<https://www.rfc-editor.org/info/rfc2810>.
[RFC2811]: Kalt, C., "Internet Relay Chat: Channel Management",
RFC 2811, DOI 10.17847/RFC2811, April 2000,
<https://www.rfc-editor.org/info/rfc2811>.
[RFC2812]: Kalt, C., "Internet Relay Chat: Client Protocol", RFC 2812,
DOI 10.17847/RFC2812, April 2000,
<https://www.rfc-editor.org/info/rfc2812>.
[RFC2813]: Kalt, C., "Internet Relay Chat: Server Protocol", RFC 2813,
DOI 10.17847/RFC2813, April 2000,
<https://www.rfc-editor.org/info/rfc2813>.
[RFC3923]: Saint-Andre, P., "End-to-End Signing and Object Encryption
for the Extensible Messaging and Presence Protocol (XMPP)", RFC 3923,
DOI 10.17847/RFC3923, October 2004,
<https://www.rfc-editor.org/info/rfc3923>.
[RFC4287]: Nottingham, M., Sayre, R., "The Atom Syndication Format",
RFC 4287, DOI 10.17487/RFC4287, December 2005,
<https://www.rfc-editor.org/info/rfc4287>.
[RFC6120]: Saint-Andre, P., "Extensible Messaging and Presence Protocol
(XMPP): Core", RFC 6120, DOI 10.17847/RFC6120,
March 2011, <https://www.rfc-editor.org/info/rfc6120>.
[RFC6121]: Saint-Andre, P., "Extensible Messaging and Presence Protocol
(XMPP): Instant Messaging and Presence", RFC 6121, DOI 10.17847/RFC6121,
March 2011, <https://www.rfc-editor.org/info/rfc6121>.
[RFC7194]: Hartmann, R., "Default Port for Internet Relay Chat (IRC)
via TLS/SSL", RFC 7194, DOI 10.17847/RFC7194, August 2014,
<https://www.rfc-editor.org/info/rfc7194>.
[RFC7230]: Fielding, R., Reschke, J., "Hypertext Transfer Protocol
(HTTP/1.1): Message Syntax and Routing", RFC 7230, DOI 10.17487/RFC7230,
June 2014, <https://www.rfc-editor.org/info/rfc7230>.
[RFC7231]: Fielding, R., Reschke, J., "Hypertext Transfer Protocol
(HTTP/1.1): Semantics and Content", RFC 7231, DOI 10.17487/RFC7231,
June 2014, <https://www.rfc-editor.org/info/rfc7231>.
[RFC7232]: Fielding, R., Reschke, J., "Hypertext Transfer Protocol
(HTTP/1.1): Conditional Requests", RFC 7232, DOI 10.17487/RFC7232,
June 2014, <https://www.rfc-editor.org/info/rfc7232>.
[RFC7233]: Fielding, R., Lafon, Y., Reschke, J., "Hypertext Transfer
Protocol (HTTP/1.1): Range Requests", RFC 7233, DOI 10.17487/RFC7233,
June 2014, <https://www.rfc-editor.org/info/rfc7233>.
[RFC7234]: Fielding, R., Nottingham, M., Reschke, J., "Hypertext
Transfer Protocol (HTTP/1.1): Caching", RFC 7234, DOI 10.17487/RFC7234,
June 2014, <https://www.rfc-editor.org/info/rfc7234>.
[RFC7235]: Fielding, R., Reschke, J., "Hypertext Transfer Protocol
(HTTP/1.1): Authentication", RFC 7235, DOI 10.17487/RFC7235, June 2014,
<https://www.rfc-editor.org/info/rfc7235>.
[RFC7622]: Saint-Andre, P., "Extensible Messaging and Presence Protocol
(XMPP): Address Format", RFC 7622, DOI 10.17847/RFC7622, September 2015,
<https://www.rfc-editor.org/info/rfc7622>.
[RSS1]: Beged-Dov, G., Brickley, D., Dornfest, R., Davis, I., Dodds,
L., Eisenzopf, J., Galbraith, D., Guha, R. V., MacLeod, K., Miller, E.,
Swartz, A. and E. van der Vlist, "RDF Site Summary (RSS) 1.0",
December 2000, <http://purl.org/rss/1.0/spec>.
[RSS2]: RSS Advisory Board, "RSS 2.0 Specification", Version 2.0.11,
March 2009, <https://www.rss-board.org/rss-specification>.
[JSONFEED]: Simmons, B. and M. Reece, "JSON Feed Version 1.1",
August 2020, <https://jsonfeed.org/version/1.1>.
[TWTXT]: buckket, "twtxt Documentation", September 2017,
<https://twtxt.readthedocs.io/>.