%% You should probably cite rfc9055 instead of this I-D.
@techreport{ietf-detnet-security-12,
    number =    {draft-ietf-detnet-security-12},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-detnet-security/12/},
    author =    {Ethan Grossman and Tal Mizrahi and Andrew J. Hacker},
    title =     {{Deterministic Networking (DetNet) Security Considerations}},
    pagetotal = 47,
    year =      2020,
    month =     oct,
    day =       3,
    abstract =  {A DetNet (deterministic network) provides specific performance guarantees to its data flows, such as extremely low data loss rates and bounded latency. As a result, securing a DetNet requires that in addition to the best practice security measures taken for any mission-critical network, additional security measures may be needed to secure the intended operation of these novel service properties. This document addresses DetNet-specific security considerations from the perspectives of both the DetNet system-level designer and component designer. System considerations include a threat model, taxonomy of relevant attacks, and associations of threats versus use cases and service properties. Component-level considerations include ingress filtering and packet arrival time violation detection. This document also addresses DetNet security considerations specific to the IP and MPLS data plane technologies thereby complementing the Security Considerations sections of the various DetNet Data Plane (and other) DetNet documents.},
}