-
Status: draft
-
Authors: Garrett D’Amore
-
Version: 0.3
This is a template protocol that describes an SP protocol. There is no such protocol, this document serves only to act as a starting point. Please replace this with an abstract.
Copyright © 2017 The Authors.
This specification is licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the license online.
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.
RFCs use a version number based on two decimal integer values separated by a decimal point, as in major.minor. The major value is the primary version of the specification. This number is incremented whenever a normative change is made to the specification. The minor value is incremented only when non-normative changes, such as clarifications and error corrections are made to existing specifications. When a new major number is assigned, the minor number will be reset to zero.
Note that the major and minor number are each whole numbers, and the
total version should not be treated as a rational number. This means that
a version of 1.10
would represent the 10th revision to version 1, and
is newer than version 1.9
. This also means that a version of 1.01
is
non-sensical, and would never be used.
This document is in AsciiDoc format, and authors may use the full markup syntax.
A sub-header subsection.
First generic preformatted:
int main(int argc, char **);
Then as C:
int main(int argc, char **argv);
Diagrams use ditaa syntax.
+-------------+ | Protocol ID | +-------------+ +-------+ +-----+ | Start |-->| End | +-------+ +-----+