SCION Components Analysis
draft-rustignoli-panrg-scion-components-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nicola Rustignoli , Corine de Kater | ||
| Last updated | 2024-03-18 (Latest revision 2023-09-10) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
Related Implementations
Slack Channel |
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
SCION is an inter-domain Internet architecture that focuses on security and availability. Its fundamental functions are carried out by a number of components. This document analyzes its core components from a functionality perspective, describing their dependencies, outputs, and properties provided. The goal is to answer the following questions: * What are the main components of SCION and their dependencies? Can
Authors
Nicola Rustignoli
Corine de Kater
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)