Update README.md - #220
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the project README to clarify the intended approach for NLAP’s encryption layer, aiming to emphasize use of standardized mechanisms as part of the protocol’s “Core Architectural Characteristics” section.
Changes:
- Revises the “Simplified High-Integrity Cryptography” bullet to more explicitly describe atomic, frame-based signing/encryption and standardized X.509-related mechanisms.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| - **Formalized Model Descriptions:** Reduces protocol complexity to a bare minimum by enforcing a 100% complete structural and semantic definition via Document Type Definitions (DTD) and YANG modeling schemas. | ||
| - **Granular Protocol Sub-typing:** Sub-divides transport traffic into distinct, functional protocol variants to maximize scalability and simplify network firewalls (see chapter [7. NLAP Subtypes](#7-nlap-subtypes)). | ||
| - **Simplified High-Integrity Cryptography**: Drastically reduces cryptographic complexity. Because data is processed as static, complete messages rather than continuous streams, the entire frame is signed and encrypted atomically. This enables hardware-native X.509 standard compliance with direct HSM and TPM integration without complex TLS state-machines. | ||
| - **Simplified High-Integrity Cryptography**: Drastically simplifies cryptographic state-machines and maximizes security by eliminating partial stream-based encryption entirely. Implemented via WolfSSL, data is signed and encrypted atomically as discrete, static messages. This approach supports standard X.509 mechanisms natively across both high-performance OpenSC (x86_64) environments and embedded IoT deployments via direct hardware TPM integration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
Emphasize that the encryption layer will use standardized mechanisms.