# General Definitions & Standards

## Acronyms and Abbreviations

| Acronym / Abbreviation | Definition                                                   |
| ---------------------- | ------------------------------------------------------------ |
| CEO                    | Chief Executive Officer                                      |
| CFO                    | Chief Financial Officer                                      |
| CSO                    | Chief Sales Officer                                          |
| CTO                    | Chief Technical Officer                                      |
| HOD                    | Head of Department                                           |
| HOP                    | Head of Procurement                                          |
| DHR                    | Director Human Resources                                     |
| DOD                    | Director of Development                                      |
| DQM                    | Director of Quality Management                               |
| HOM                    | Head of Marketing                                            |
| HOCS                   | Head of Customer Service                                     |
| TBD                    | To be defined / To be decided / To be discussed              |
| QM                     | Quality Management                                           |
| QMR                    | Quality Management Representative                            |
| RCM                    | Risk Control Matrix                                          |
| EC                     | Executive Committee                                          |
| ECM                    | Executive Committee Member                                   |
| BOD                    | Board of Director                                            |
| CoC                    | Code of Conduct                                              |
| CLA                    | (Individual) Contributor License Agreement                   |
| NDA                    | Non-disclosure agreement                                     |
| TOS                    | (General) Terms of Service                                   |
| TOU                    | (General) Terms of Use                                       |
| A                      | Actual (often used in combination with financial figures)    |
| B                      | Budget                                                       |
| PY                     | Previous year (sometimes used to define any previous year)   |
| FC                     | Forecast                                                     |
| FTE                    | Full Time Equivalent                                         |
| EBITDA                 | Earnings before interest, taxes, depreciation and amortization |
| EBIT                   | Earnings before interest and taxes                           |
| EBT                    | Earnings before taxes                                        |

## Key words to indicate requirement levels

### Copyright Notice

Copyright © The Internet Society (1997). All Rights Reserved.

### Abstract

In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document:

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Note that the force of these words is modified by the requirement level of the document in which they are used.

1.  MUST

This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.

2.  MUST NOT

This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.

3.  SHOULD

This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

4.  SHOULD NOT

This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.

5.  MAY

This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)

6.  Guidance in the use of these Imperatives

Imperatives of the type defined in this memo must be used with care and sparingly. In particular, they MUST only be used where it is actually required for interoperation or to limit behavior which has potential for causing harm (e.g., limiting retransmissions) For example, they must not be used to try to impose a particular method on implementors where the method is not required for interoperability.

7.  Security Considerations

These terms are frequently used to specify behavior with security implications. The effects on security of not implementing a MUST or SHOULD, or doing something the specification says MUST NOT or SHOULD NOT be done may be very subtle. Document authors should take the time to elaborate the security implications of not following recommendations or requirements as most implementors will not have had the benefit of the experience and discussion that produced the specification.

8.  Acknowledgments

The definitions of these terms are an amalgam of definitions taken from a number of RFCs. In addition, suggestions have been incorporated from a number of people including Robert Ullmann, Thomas Narten, Neal McBurnett, and Robert Elz.

**Author's Address**
Scott Bradner
Harvard University
1350 Mass. Ave.
Cambridge
MA 02138
Phone:   - +1 617 495 3864
Email:   sob@harvard.edu

### Full Copyright Statement

Copyright © The Internet Society (1997). 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.

## Date Time Format

The date time format in all documents must follow the [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) standardization: `YYYY-MM-DD` or `YYYY-MM-DD HH:MM:SS` (sometimes written as `YYYY-MM-DD h:i:s`). 

2022-01-01 - Version 1.0
