Skip to content

Typos #13

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
antonyantony merged 2 commits into from
Jul 9, 2025
Merged

Typos #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8882dd4
Fix formatting and typo in Sub SA text
tobiasbrunner Jul 9, 2025
80e0249
README: Fix typo and list item for diff
tobiasbrunner Jul 9, 2025
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
4 changes: 2 additions & 2 deletions README.org
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ This is the working area for the individual Internet-Draft, "EESP IKEv2".
This README provides information about the ~IKEv2 negotiation for Enhanced Encapsulating Security Payload (EESP)~
draft document.

* Laest Copy
* Latest Copy
The latest version of the draft in HTML format is at:
- [[https://klassert.github.io/eesp-ikev2/draft-ietf-ipsecme-eesp-ikev2-latest.html][Editor's Copy]]
# above URL is replaced by .github/workflows/generate.yaml
Expand All @@ -17,7 +17,7 @@ The latest version of the draft in HTML format is at:
* IETF Datatracker Copy of IKEv2 EESP I.D.
- [[https://datatracker.ietf.org/doc/draft-ietf-ipsecme-eesp-ikev2/][IETF Datatracker: draft-ietf-ipsecme-eesp-ikev2]]

* [[https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-ipsecme-eesp-ikev2&url_2=https://raw.githubusercontent.com/klassert/eesp-ikev2/refs/heads/gh-pages/draft-ietf-ipsecme-eesp-ikev2-latest.txt][diff with latest submission]]
- [[https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-ipsecme-eesp-ikev2&url_2=https://raw.githubusercontent.com/klassert/eesp-ikev2/refs/heads/gh-pages/draft-ietf-ipsecme-eesp-ikev2-latest.txt][Diff with latest submission]]

* References
For more detailed information, refer to the following resources:
Expand Down
11 changes: 5 additions & 6 deletions eesp-ikev2.org
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -489,7 +489,7 @@ Note that this is not a negotiation: each side can indicate its own
value for the maximum Sub SA ID. In addition, sending side is not
required to consume all possible Sub SA IDs up to the indicated
maximum value - it can create fewer Sub SAs. In any case, when
creating Sub SAs as a sender an endpoint nas to consider that Sub SA
creating Sub SAs as a sender an endpoint has to consider that Sub SA
IDs MUST NOT repeat for a given EESP SA and MUST NOT exceed the value
sent by the peer in this notification. The actual number of Sub SAs
can be different in different directions.
Expand All @@ -516,8 +516,7 @@ is shown below.

- Protocol ID (1 octet) - MUST be 0. MUST be ignored if not 0.
- SPI Size (1 octet) - MUST be 0. MUST be ignored if not 0.
- Notify Status Message Type (2 octets) - set to EESP_MAX_SUB_SA_ID
(<TBD3>).
- Notify Status Message Type (2 octets) - set to EESP_MAX_SUB_SA_ID (<TBD3>).
# [VS] Why it is 16-bit and not 32-bit in size?
- Maximum Sub SA ID (2 octets, integer in network byte order)
-- specifies the maximum value for the EESP Sub SA ID the
Expand All @@ -530,9 +529,9 @@ field means that only one Sub SA (with Subs SA ID = 0) can be
handled.

If a peer doesn't have any restrictions on the number of the incoming
Sub SAs, then it MAY omit sending this notification. As a consequence
- if no this notification was received by a peer, that peer can
assume that it create as many outgoing Sub SAs as it needs (provided
Sub SAs, then it MAY omit sending this notification. As a consequence,
if this notification was not received by a peer, that peer can assume
that it can create as many outgoing Sub SAs as it needs (provided
that Sub SA IDs not repeat).

If no SSKDF transform was negotiated, this notification MUST be
Expand Down
Loading