casa/bikeshed
casa
/
bikeshed
9
0
Fork 0
Code Issues Pull Requests Releases Activity
bikeshed/rfb/rfb6.txt

530 lines
17 KiB
Plaintext
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Bikeshedding Working Group ~lucidiot, Ed.
Request for Bikeshedding: 6 Bikeshedding Microsystems
Category: Standards Track August 1, 2021
Vaccination as a Unit Prefix
Abstract
This document introduces a new unit prefix that should be preferred
by all Bikeshedders when it is applicable; vax- and antivax-.
Status of This Memo
This is a Bikeshedding Standards Track document.
This document is a product of the Bikeshedding Working Group (BWG).
It represents the consensus of the bikeshedding community. It has
received public review and has been approved for publication by the
Bikeshedding Engineering Steering Group (BESG).
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained on the tildepals
mailing list.
Copyright Notice
Copyright (c) 2021 Bikeshedding Microsystems and the persons
identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the Bikeshedding Microsystems'
Legal Provisions Relating to Bikeshedding Documents in effect on the
date of publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
~lucidiot Standards Track [Page 1]
RFB 6 Vax Prefix August 2021
Table of Contents
1. Introduction ...................................................2
1.1. Notational Conventions ...................................3
2. New Prefixes ...................................................3
2.1. The Vax Prefix ...........................................3
2.2. The AntiVax Prefix .......................................3
2.3. The Vaxi Prefix ..........................................3
2.4. The AntiVaxi Prefix ......................................3
3. Security Considerations ........................................4
4. Internationalization Considerations ............................4
5. Privacy Considerations .........................................7
6. BANANA Considerations ..........................................7
7. References .....................................................8
7.1. Normative References ......................................8
7.2. Informative References ....................................8
Appendix A. Warranty Exclusion Statement ...........................9
Acknowledgements ...................................................9
Author's Address ...................................................9
1. Introduction
As you may have noticed, every human on Earth has been facing since
the end of 2019 a worldwide pandemic. This pandemic correlates with
a period of worldwide rollout of 5G NR [5GNR], which had caused a
wave of conspiracy theories over electromagnetic waves being used to
control our brains.
In an attempt to end this worldwide health crisis, multiple vaccines
have been simultaneously developed and vaccination campaigns are
being run to get them to spread out as much as possible. This has
sparked new conspiracy theories, as the anti-vaccination groups have
been very active thanks to Donald Trump's presidency of the United
States and thanks to Facebook's circlejerk-based attention-retaining
content selection. According to highly trustable media [BULLSHIT],
the vaccines provide nano-bots that can be controlled over 5G NR and
allow governments to brainwash humanity.
It has been commonly observed that anti-vaccination activists and
conspiracy theorists react very aggressively when faced with any kind
of criticism or doubt of their opinions. The Operational Security
Division of Bikeshedding Microsystems believes there is a potential
threat for our Bikeshedding Business Operations in expressing any
pro-vaccination or scientifically-validated opinion on the current
pandemic. While the pandemic provides us with unforeseen and
challenging but rewarding and profitable markets for us to bikeshed
in, the OpSec Division needs to act to prevent any damage to our
reputation and daily activities.
To avoid any issues with conspiracy theories and anti-vaccination
activists, the OpSec Division hereby enacts a new unit prefixing
system that is not too intrusive on our daily operations, but
~lucidiot Standards Track [Page 2]
RFB 6 Vax Prefix August 2021
provides us with plausible deniability in regards to pro-vaccination
opinions that could be expressed in any communcations from
Bikeshedding Microsystems.
1.1. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document SHALL NOT be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. New Prefixes
Bikeshedders SHOULD use the following new unit prefixes when
expressing any quantity in the order of magnitude of billions
(10^9), in addition to regular SI unit prefixes.
2.1. The Vax Prefix
The "vax-" prefix, abbreviated "V", is equivalent to 5,000,000,000
(5E+9 or 5 * 10^9). "Vax" is a diminutive of "vaccine", and it
corresponds to 5 giga, or 5G.
2.2. The Antivax Prefix
The "antivax-" prefix, abbreviated "AV", is equivalent to
-5,000,000,000 (-5E+9 or 5 * 10^9). "Antivax" is a diminutive of
anti-vaccine and is regularly used to describe anti-vaccination
activists. It corresponds to -5 giga, or -5G.
2.3. The Vaxi Prefix
The "vaxi-" prefix, abbreviated "Vi", is equivalent to 5,368,709,120
(5 * 1024^3). This is the concatenation of the "vax-" prefix with
the binary variant of SI prefixes regularly used to express
quantities of bits and bytes, such as gibibytes (GiB). 1 ViB is
equivalent to 5 GiB.
The "vaxi-" prefix MUST only be used for vaxibytes or vaxibits.
Users of binary prefixes SHOULD consider whether using a binary
prefix instead of a standard SI prefix truly adds to the meaning of
their communication before using it.
2.4. The Antivaxi Prefix
The "antivaxi-" prefix, abbreviated "AVi", is equivalent to
-5,368,709,120 (-5 * 1024^3). This is the concatenation of the
"anti-vax-" prefix with the binary variant of SI prefixes regularly
used to express quantities of bits and bytes, such as gibibytes
(GiB). 1 AViB is equivalent to -5 GiB.
~lucidiot Standards Track [Page 3]
RFB 6 Vax Prefix August 2021
The "antivaxi-" prefix MUST only be used for antivaxibytes or
antivaxibits. Users of binary prefixes SHOULD consider whether using
a binary prefix instead of a standard SI prefix truly adds to the
meaning of their communication before using it.
3. Security Considerations
This document exists solely for the sake of ensuring the security of
our Bikeshedding Business Operations.
Bikeshedders that face any kind of negative interactions with
conspiracy theorists, anti-vaccination activists or anti-bikeshedding
activists MUST forward any written statements, recordings or relevant
documents related to said interactions to the Bikeshedding
Microsystems Operational Security Division.
It is RECOMMENDED to avoid replying to those interactions until a
proper reply strategy has been established by the Bikeshedding
Microsystems Operational Security Division in collaboration with the
Bikeshedding Microsystems Public Relations Division.
Bikeshedders that witness other Bikeshedders expressing agreement
with conspiracy theories or anti-vaccination arguments MUST report
said issues to the Bikeshedding Microsystems Human Resources Division
who SHOULD take appropriate action to neutralize any potential threat
to the Bikeshedding Business Operations or to the physical integrity
of the bodies of other Bikeshedders.
4. Internationalization Considerations
The following languages are known to use a word that means "vaccine"
similarly to the English word "vaccine":
- Afrikaans: vaksine
- Albanian: vaksinë
- Armenian: վակցինա (vakc'ina)
- Asturian: vacuna
- Azerbaijani: vaksin
- Belarusian: вакцы́на (vakcýna)
- Bengali: ভ্যাক্সিন (bbhakśin)
- Bulgarian: вакси́на (vaksína)
- Catalan: vaccí
- Czech: vakcína
~lucidiot Standards Track [Page 4]
RFB 6 Vax Prefix August 2021
- Danish: vaccine
- Dhivehi: ވެކްސިން‎ (vek̊sin̊)
- Dutch: vaccin
- Esperanto: vakcino
- Estonian: vaktsiin
- French: vaccin
- Galician: vacina
- Georgian: ვაქცინა (vakcina)
- German: Vakzine
- Hindi: वैक्सीन (vaiksīn)
- Hungarian: vakcina
- Irish: vacsaín
- Italian: vaccino
- Japanese: ワクチン (wakuchin)
- Kazakh: вакцина (vakcïna)
- Khmer: វ៉ាក់សាំង (km) (vaksang)
- Korean: 백신 (ko) (baeksin)
- Kyrgyz: вакцина (vaktsina)
- Latvian: vakcīna
- Lithuanian: vakcina
- Macedonian: вакцина (vakcina)
- Malagasy: vaksiny (mg)
- Malay: vaksin
- Mongolian: вакцин (vaktsin)
- Norman: vaccîn
- Norwegian: vaksine
~lucidiot Standards Track [Page 5]
RFB 6 Vax Prefix August 2021
- Malayalam: വാക്സിൻ (vāksin)
- Persian: واکسن‎ (vâksin)
- Polish: wakcyna
- Portuguese: vacina
- Romanian: vaccin
- Russian: вакци́на (vakcína)
- Serbo-Croatian: вакци́на, vakcína
- Slovak: vakcína
- Spanish: vacuna
- Swedish: vaccin
- Tajik: ваксина (vaksina)
- Telugu: వ్యాక్సిన్ (vyāksin), వ్యాక్సీన్ (vyāksīn)
- Thai: วัคซีน (wák-siin)
- Turkmen: waksina
- Ukrainian: вакци́на (vakcýna)
- Urdu: ویکسین‎ (vaiksīn)
- Uyghur: ۋاكسىنا‎ (waksina)
- Uzbek: vaktsina, vaksina
- Vietnamese: vắc-xin
- Yakut: вакцина (vaktsina)
- Yiddish: וואַקצין‎ (vaktsin)
Considering the large amount of languages that have words similar in
consonance with the English word "vaccine", the fact that vaccination
has been in the news worldwide for many months, and the fact that
"antivax" is being used in any language to describe anti-vaccination
activists as those are mostly United States-based, it is safe to
assume that these new prefixes will be widely understood by our
international branches.
~lucidiot Standards Track [Page 6]
RFB 6 Vax Prefix August 2021
5. Privacy Considerations
This document does not enforce the use of the new prefixes on any
private communication, unless those communications have the potential
to be leaked or when a Bikeshedder is under investigation for
possible threats to Bikeshedding Business Operations or to the
corporeal forms of fellow Bikeshedders by the Bikeshedding
Microsystems Human Resources Division.
Reporting of potential behavioral issues of a Bikeshedder to the
Bikeshedding Microsystems Human Resources Division SHOULD be made
through an anonymous reporting process. The Bikeshedding
Microsystems Human Resources Division is encouraged to define and
standardize this reporting process as another Request for
Bikeshedding as soon as possible.
Sharing writings, recordings or any document relevant to a private
interaction in which a Bikeshedder manifests behavior that could lead
to potential threats to Bikeshedding Business Operations or to the
corporeal forms of fellow Bikeshedders, or in which an external human
being manifests a negative reaction to a potential pro-vaccination
opinion expressed by Bikeshedding Microsystems through any of its
public communcations, with the Bikeshedding Microsystems Human
Resources Division or the Bikeshedding Microsystems Operational
Security Division, MAY be made after a reviewing step in which the
reporter blacks out, or mutes, any portion of the writings,
recordings or other relevant documents that are considered to be too
sensitive to be shared.
SHOULD any censored portion of a document become critical to an
investigation made by the Bikeshedding Microsystems Human Resources
Division or to the determination of a response process by the
Bikeshedding Microsystems Operational Security Division, the
respective divisions MAY request the approval of the Bikeshedding
Microsystems Data Protection Officer to make a declassification of
the relevant censoring REQUIRED. The initial reporter MUST send
a new copy of the document with the censoring removed in a timely
manner or face appropriate sanctions from the Bikeshedding
Microsystems Human Resources Division.
6. BANANA Considerations
This document creates a new BANANA registry entitled "Unit Prefixes".
The policy for future assignments to this registry is RFB Required
[RFC8126]. This registry has four fields: the prefix's name, the
prefix's abbreviation, the prefix's multiplier, and a reference to
one or more Request for Bikesheddings defining the prefix.
The prefix name SHOULD be unique. Multiple prefixes MAY share the
same name if and only if they cannot be both used simultaneously for
the same unit, e.g. if one prefix applies only to one unit, and
~lucidiot Standards Track [Page 7]
RFB 6 Vax Prefix August 2021
another only to a different unit.
The prefix abbreviation SHOULD be unique. Multiple prefixes MAY
share the same abbreviation if and only if they cannot be both used
simultaneously for the same unit, e.g. if one prefix applies only to
one unit, and another only to a different unit.
The prefix multiplier MUST be a finite number.
The initial values for this registry are specified below:
Name Abbreviation Multiplier RFB
-------------------------------- ------------ -------------- --------
Vax V 5,000,000,000 This RFB
Antivax AV -5,000,000,000 This RFB
Vaxi Vi 5,368,709,120 This RFB
Antivaxi AVi -5,368,709,120 This RFB
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC8126] Cotton, M., Leiba, B. and Narten, T., "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
7.2. Informative References
[5GNR] 3rd Generation Partnership Project, "3GPP specification
series: 38series",
<https://www.3gpp.org/DynaReport/38-series.htm>
[BULLSHIT] Freeman, M., "The Coronavirus 5G Connection and Coverup",
The Freedom Articles, February 2020,
<https://thefreedomarticles.com/coronavirus-5g-connection
-coverup-vaccines-transhumanism/>
~lucidiot Standards Track [Page 8]
RFB 6 Vax Prefix August 2021
Appendix A. Warranty Exclusion Statement
This document and the information contained herein is provided on an
"AS IS" basis and TILDE.TOWN 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.
Acknowledgements
The author would like to thank wsinatra for encouraging the
implementation of the vaccine unit prefixes.
The author would like to thank and congratulate all the Bikeshedders
for making it through this pandemic.
Author's Address
~lucidiot (editor)
Bikeshedding Microsystems
m455.casa
138.197.184.222
The Internet
Email: lucidiot@brainshit.fr
URI: https://tilde.town/~lucidiot/
~lucidiot Standards Track [Page 9]
Reference in New Issue View Git Blame Copy Permalink