WIP eesp.org AAD changes. #6
Merged
Conversation
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
antonyantony
force-pushed
the
antony/edit-8-aad
branch
from
74beacd to
7d04c94
Compare
antonyantony
force-pushed
the
antony/edit-8-aad
branch
from
7d04c94 to
77bff0b
Compare
antonyantony
force-pushed
the
antony/edit-8-aad
branch
8 times, most recently
from
c05106f to
5e333a0
Compare
antonyantony
force-pushed
the
antony/edit-8-aad
branch
4 times, most recently
from
ea4b3c6 to
113843c
Compare
this commit is still a work in progress. It need polishing. How to show what would be covered in AAD, also with Crypt Offset. Also further clarifaction on all crypto suites that use integerity protection would be covered in this update. This would also need a change to IANA IKEv2 registry add the column EESP there. Then do we need to upate EACH RFCs?
it is two places. For now leave the duplicate
antonyantony
force-pushed
the
antony/edit-8-aad
branch
from
113843c to
7da7f9e
Compare
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.
this commit is still a work in progress. It need polishing. How to show what would be covered in AAD, also with Crypt Offset.
Also further clarifaction on all crypto suites that use integerity protection would be covered in this update.
This would also need a change to IANA IKEv2 registry add the column EESP there. Then do we need to upate EACH RFCs?