Skip to content

Fixed Several Typos #12

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

Open
seadog007 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fixed Several Typos #12

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
6 changes: 3 additions & 3 deletions draft-zaeschke-scion-quic-multipath.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -383,7 +383,7 @@ An attacker could use endpoints with identical 4-tuple to reroute traffic
to a different machine without triggering path validation, see
{{attack-path-injection}} and {{token}}.

The implication of a skipped path validation is that a sever can be coaxed into
The implication of a skipped path validation is that a server can be coaxed into
sending QUIC packets to an unexpecting client. This is similar to the attacks
described in {{Section 8 of QUIC-TRANSPORT}} and
{{Section 21.5.4 of QUIC-TRANSPORT}}.
Expand Down Expand Up @@ -957,7 +957,7 @@ relevant to security or performance.

## Recommendations for SCION Implementations

- SCION implementations can prevent attackers from expoloiting a skipped
- SCION implementations can prevent attackers from exploiting a skipped
path validation by preventing path injection ({{attack-path-injection}}).
To prevent path injection:

Expand Down Expand Up @@ -1061,7 +1061,7 @@ IP+port, so the attacker must guess the victims port when launching the attack.
- SCION libraries could us port/IP mangling when they detect multiple paths with
the same IP/port. However, this may have unintended consequences in the
application layer.
- Higher level libraries, such as QUIC(-MP) should be carefuol to not
- Higher level libraries, such as QUIC(-MP) should be careful to not
rely only on IP addresses to trigger path validation or resetting
congestion control or RTT estimation algorithms. Instead, QUIC-MP should
rely on the QUIC Path ID.
Expand Down