Skip to content

Update draft-xia-ipsecme-eesp-stateless-encryption.md #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
FrankXL merged 1 commit into from
Oct 20, 2025
Merged

Update draft-xia-ipsecme-eesp-stateless-encryption.md #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions draft-xia-ipsecme-eesp-stateless-encryption.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,9 +316,11 @@ Correspondingly, the destination node is processed as follows:
# Security Considerations

- A highly secure control plane is required to ensure that the master keys managed by users/systems are not leaked or lost;
-
The control channel establishment phase requires two-way authentication and authorization to ensure the integrity and confidentiality of the master key during the master key distribution phase. At the same time, it ensures that the group master key is only distributed to the corresponding group members;
- The endpoint requires secure storage of the master key and data key locally.
- The control channel establishment phase requires two-way authentication and authorization to ensure the integrity and confidentiality of the master key during the master key distribution phase. At the same time, it ensures that the group master key is only distributed to the corresponding group members;
- The endpoint requires secure storage of the master key and data key locally;
- The key derivation process must ensure that the data keys calculated by cryptographic engines on different entities are unique. This means that the input for key derivation must include a unique ID to prevent two cryptographic engines from using the same data key;
- It is necessary to ensure that IVs are not reused. Under the same data key, the construction of IVs must guarantee that they are not repeated;
- The update cycle of the master key should be determined based on the actual number of derived data keys to be generated.



Expand Down