%% You should probably cite rfc8241 instead of this I-D.
@techreport{ietf-i2rs-protocol-security-requirements-11,
    number =    {draft-ietf-i2rs-protocol-security-requirements-11},
    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-i2rs-protocol-security-requirements/11/},
    author =    {Susan Hares and Daniel Migault and Joel M. Halpern},
    title =     {{I2RS Security Related Requirements}},
    pagetotal = 21,
    year =      2016,
    month =     sep,
    day =       15,
    abstract =  {This presents security-related requirements for the I2RS protocol which provides a new interface to the routing system described in the I2RS architecture document (RFC7921). The I2RS protocol is a re-use protocol implemented by re-using portions of existing IETF protocols and adding new features to these protocols. The I2RS protocol re- uses security features of a secure transport (E.g. TLS, SSH, DTLS) such as encryption, message integrity, mutual peer authentication, and replay protection. The new security features I2RS adds are: a priority mechanism to handle multi-headed write transactions, an opaque secondary identifier which identifies an application using the I2RS client, and an extremely constrained read-only non-secure transport. This document provides the detailed requirements for these security features.},
}