Security is a function, not a layer
draft-kuehlewind-security-is-not-a-layer-00

Document Type Expired Internet-Draft (individual)
Last updated 2019-09-01 (latest revision 2019-02-28)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kuehlewind-security-is-not-a-layer-00.txt

Abstract

This document argues that security functions should be implemented on each layer as needed. Especially security functions should not be separated in its own layer. Having security scoped to the needs of each layer makes it possible to separate different functions correctly without the risk of impacting security on another layer. Note that this does not mean that each layer needs to maintain and negotiate it's on security context.

Authors

Mirja K├╝hlewind (mirja.kuehlewind@tik.ee.ethz.ch)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)