@techreport{kuehlewind-security-is-not-a-layer-00,
    number =    {draft-kuehlewind-security-is-not-a-layer-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kuehlewind-security-is-not-a-layer/00/},
    author =    {Mirja Kühlewind},
    title =     {{Security is a function, not a layer}},
    pagetotal = 2,
    year =      2019,
    month =     feb,
    day =       28,
    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.},
}