%% You should probably cite rfc4819 instead of this I-D.
@techreport{ietf-secsh-publickey-subsystem-08,
    number =    {draft-ietf-secsh-publickey-subsystem-08},
    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-secsh-publickey-subsystem/08/},
    author =    {Jeff Van Dyke and Joseph Galbraith and Jon Bright},
    title =     {{Secure Shell Public Key Subsystem}},
    pagetotal = 17,
    year =      2006,
    month =     oct,
    day =       6,
    abstract =  {Secure Shell defines a user authentication mechanism that is based on public keys, but does not define any mechanism for key distribution. No common key management solution exists in current implementations. This document describes a protocol that can be used to configure public keys in an implementation-independent fashion, allowing client software to take on the burden of this configuration. The Public Key Subsystem provides a server-independent mechanism for clients to add public keys, remove public keys, and list the current public keys known by the server. Rights to manage public keys are specific and limited to the authenticated user. A public key may also be associated with various restrictions, including a mandatory command or subsystem. {[}STANDARDS-TRACK{]}},
}