Hi all,

We just submitted an updated version of BRSKI-PRM as discussed earlier on the 
mailing list. The draft contains the following changes to the previous version:

   *  simplified description for JWS Protected Header aligning with the
      update in draft-ietf-anima-jws-voucher-15 to always include the
      certificate chain in Section 7.1.2.1 and Section 7.3.4.1
   *  updated reference to corresponding sections for JWS Header and
      Signature in [I-D.ietf-anima-jws-voucher] in Section 7.1.2.1 and
      Section 7.3.4.1
   *  updated formatting of key events in Section 8

The motivation to submit the update so shortly after the last was to keep 
compatibility with the recent changes in JWS-Voucher, as stated above.

Best regards
Steffen

-----Original Message-----
From: internet-dra...@ietf.org <internet-dra...@ietf.org>
Sent: Wednesday, January 15, 2025 4:50 PM
To: Michael C. Richardson <mcr+i...@sandelman.ca>; Eliot Lear <l...@cisco.com>; 
Michael Richardson <mcr+i...@sandelman.ca>; Fries, Steffen (FT RPD CST) 
<steffen.fr...@siemens.com>; Werner, Thomas (FT RPD CST SEA-DE) 
<thomas-wer...@siemens.com>
Subject: New Version Notification for draft-ietf-anima-brski-prm-17.txt

A new version of Internet-Draft draft-ietf-anima-brski-prm-17.txt has been 
successfully submitted by Steffen Fries and posted to the IETF repository.

Name:     draft-ietf-anima-brski-prm
Revision: 17
Title:    BRSKI with Pledge in Responder Mode (BRSKI-PRM)
Date:     2025-01-15
Group:    anima
Pages:    116
URL:      https://www.ietf.org/archive/id/draft-ietf-anima-brski-prm-17.txt
Status:   https://datatracker.ietf.org/doc/draft-ietf-anima-brski-prm/
HTML:     https://www.ietf.org/archive/id/draft-ietf-anima-brski-prm-17.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-anima-brski-prm
Diff:     
https://author-tools.ietf.org/iddiff?url2=draft-ietf-anima-brski-prm-17

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).



The IETF Secretariat


_______________________________________________
Anima mailing list -- anima@ietf.org
To unsubscribe send an email to anima-le...@ietf.org

Reply via email to