diff options
| -rw-r--r-- | kd/oap-0001.md | 2 | ||||
| -rw-r--r-- | kd/oap-0002.md | 4 | ||||
| -rw-r--r-- | kd/oap-0003.md | 6 |
3 files changed, 6 insertions, 6 deletions
diff --git a/kd/oap-0001.md b/kd/oap-0001.md index 535d3d6..bc59341 100644 --- a/kd/oap-0001.md +++ b/kd/oap-0001.md @@ -46,7 +46,7 @@ for those who have understood and commited to the OSMORA oath. ## Audience OAPs are intended for those who are commited to the OSMORA oath. These -proposals must only be considered official and binding when they are approved +proposals MUST only be considered official and binding when they are approved by a number of OSMORA members and a single OSR (OSMORA Standards Reviewer). diff --git a/kd/oap-0002.md b/kd/oap-0002.md index 9020562..1da2d66 100644 --- a/kd/oap-0002.md +++ b/kd/oap-0002.md @@ -50,12 +50,12 @@ still supporting legacy POSIX applications through compatibility mechanisms such # Compatibility OUSI maintains compatibility through its _POSIXSHIM layer. In order for legacy -POSIX applications to work with OUSI, they must link with the necessary compatibility +POSIX applications to work with OUSI, they MUST link with the necessary compatibility libraries and expose legacy POSIX mechanisms by defining "_POSIXSHIM" globally. # Standard C library headers -Standard C library headers should be written with OUSI in mind while exposing +Standard C library headers SHOULD be written with OUSI in mind while exposing legacy POSIX mechanisms if requested. ## Example of stdio.h diff --git a/kd/oap-0003.md b/kd/oap-0003.md index 7cd5de7..b0a4038 100644 --- a/kd/oap-0003.md +++ b/kd/oap-0003.md @@ -49,15 +49,15 @@ block of future OSMORA secure protocols. # Session Requests -If a client wishes to establish a link with a server, it must send a Session Request +If a client wishes to establish a link with a server, it MUST send a Session Request Packet. Doing so allows the client and server to exchange flags along with required cryptographic keys. All key exchanges under OSTP are done with forward secrecy using the Elliptic-curve Diffie–Hellman key agreement protocol. # Security -All OSTP traffic must be under AES-256-GCM and be purely ephemeral. All OSTP nodes, regardless -of being in peer-to-peer mode or not, must be stateless and always discard received data after +All OSTP traffic MUST be under AES-256-GCM and be purely ephemeral. All OSTP nodes, regardless +of being in peer-to-peer mode or not, MUST be stateless and always discard received data after use. # References |