%% You should probably cite draft-ietf-anima-brski-prm-23 instead of this revision.
@techreport{ietf-anima-brski-prm-17,
    number =    {draft-ietf-anima-brski-prm-17},
    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-anima-brski-prm/17/},
    author =    {Steffen Fries and Thomas Werner and Eliot Lear and Michael Richardson},
    title =     {{BRSKI with Pledge in Responder Mode (BRSKI-PRM)}},
    pagetotal = 116,
    year =      2025,
    month =     jan,
    day =       15,
    abstract =  {This document defines enhancements to Bootstrapping a Remote Secure Key Infrastructure (BRSKI, RFC8995) to enable bootstrapping in domains featuring no or only limited connectivity between a pledge and the domain registrar. It specifically changes the interaction model from a pledge-initiated mode, as used in BRSKI, to a pledge- responding mode, where the pledge is in server role. For this, BRSKI with Pledge in Responder Mode (BRSKI-PRM) introduces new endpoints for the Domain Registrar and pledge, and a new component, the Registrar-Agent, which facilitates the communication between pledge and registrar during the bootstrapping phase. To establish the trust relation between pledge and registrar, BRSKI-PRM relies on object security rather than transport security. The approach defined here is agnostic to the enrollment protocol that connects the domain registrar to the Key Infrastructure (e.g., domain CA).},
}