Skip to content
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.

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

Intro: clarify relation with other drafts, deprecate overview draft, reference to SCIONLab #69

Merged
merged 16 commits into from
Oct 9, 2024
Merged
3 changes: 2 additions & 1 deletion draft-dekater-scion-dataplane.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,7 @@ author:
normative:
nicorusti marked this conversation as resolved.
Show resolved Hide resolved
I-D.dekater-scion-controlplane:
I-D.dekater-scion-pki:
I-D.dekater-panrg-scion-overview:
nicorusti marked this conversation as resolved.
Show resolved Hide resolved
RFC2460:
RFC2474:
RFC3168:
Expand Down Expand Up @@ -154,7 +155,7 @@ SCION relies on three main components:

*Data Plane* - carries out secure packet forwarding between SCION-enabled ASes over paths selected by endpoints. A SCION border router reuses existing intra-domain infrastructure to communicate to other SCION routers or SCION endpoints within its AS.

This document describes the SCION Data Plane component.
This document describes the SCION Data Plane component. It should be read in conjunction with {{I-D.dekater-scion-pki}} and {{I-D.dekater-scion-controlplane}} and deprecates {{I-D.dekater-panrg-scion-overview}}.

The SCION architecture was initially developed outside of the IETF by ETH Zurich with significant contributions from Anapaya Systems. It is deployed in the Swiss finance sector to provide resilient connectivity between financial institutions. The aim of this document is to document the existing protocol specification as deployed, and to introduce new concepts that can potentially be further improved to address particular problems with the current Internet architecture.

Expand Down
Loading