@techreport{hartman-gss-naming-01,
    number =    {draft-hartman-gss-naming-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hartman-gss-naming/01/},
    author =    {Sam Hartman},
    title =     {{GSSAPI Mechanisms without a Single Canonical Name}},
    pagetotal = 12,
    year =      2004,
    month =     oct,
    day =       25,
    abstract =  {The Generic Security Services API (GSSAPI) uses name-based authorization. GSSAPI authenticates two named parties to each other. Names can be stored on access control lists to make authorization decisions. Advances in security mechanisms require this model to be extended. Some mechanisms such as public-key mechanisms do not have a single name to be used. Other mechanisms such as Kerberos allow names to change as people move around organizations. This document proposes expanding the definition of GSSAPI names to deal with these situations.},
}