<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.kuehlewind-security-is-not-a-layer" target="https://datatracker.ietf.org/doc/html/draft-kuehlewind-security-is-not-a-layer-00">
   <front>
      <title>Security is a function, not a layer</title>
      <author initials="M." surname="Kühlewind" fullname="Mirja Kühlewind">
         <organization>ETH Zurich</organization>
      </author>
      <date month="February" day="28" year="2019" />
      <abstract>
	 <t>   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&#x27;s on security context.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-kuehlewind-security-is-not-a-layer-00" />
   
</reference>
