%% You should probably cite draft-dekater-scion-dataplane-04 instead of this revision. @techreport{dekater-scion-dataplane-03, number = {draft-dekater-scion-dataplane-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-dekater-scion-dataplane/03/}, author = {Corine de Kater and Nicola Rustignoli and Jean-Christophe Hugly and Samuel Hitz}, title = {{SCION Data Plane}}, pagetotal = 78, year = , month = , day = , abstract = {This document describes the data plane of the path-aware, inter- domain network architecture SCION (Scalability, Control, and Isolation On Next-generation networks). One of the basic characteristics of SCION is that it gives path control to endpoints. The SCION Control Plane is responsible for discovering these paths and making them available as path segments to the endpoints. The role of the SCION Data Plane is to combine the path segments into end-to-end paths, and forward data between endpoints according to the specified path. The SCION Data Plane fundamentally differs from today's IP-based data plane in that it is \_path-aware\_: In SCION, interdomain forwarding directives are embedded in the packet header. This document provides a detailed specification of the SCION data packet format as well as the structure of the SCION header. SCION also supports extension headers, which are additionally described. The document continues with the life cycle of a SCION packet while traversing the SCION Internet, followed by a specification of the SCION path authorization mechanisms and the packet processing at routers.}, }