Hello all, We just had the ANIMA design team meeting and I realized I submitted an intermediate version and not the final one addressing all comments discussed and resolved in the Shepherd review. As the IETF draft cutoff was yesterday and I realized it just now, I will resubmit this version in the week of the IETF meeting. The correct version, which should have been submitted is available on the ANIMA github under: https://github.com/anima-wg/anima-brski-prm. There is a text and an HTML version available. If you want to have a look then please use this version. Consequently the Shepherd writeup can be provide once the correct version s available in data tracker.
What we also discussed during the design team meeting today is an update of the two new IANA consideration sections 9.2 and 9.3 to better match the required format. This will be updated in the version 14. So again, sorry for submitting the wrong version. Hope that did not cause confusion. Best regard Steffen > -----Original Message----- > From: Fries, Steffen <[email protected]> > Sent: Friday, July 5, 2024 2:01 PM > To: [email protected] > Subject: [Anima] FW: New Version Notification for > draft-ietf-anima-brski-prm-13.txt > > Hello all, > > We just posted an updated version of BRSKI-PRM. > The draft includes several changes resulting specifically from the last part > of the > detailed Shepherd review (big thanks to Matthias), which improved structure > and > readability. > > Here is the list of main changes from IETF draft 12 -> IETF draft 13: > - Deleted figure in Section "Request Artifact: Pledge Voucher-Request Trigger > (tPVR)" for JSON representation of tPVR, as it has been replaced by CDDL > - Updated reason-content description in status response messages > (enroll-status, > voucher-status, and status-response. > - Updated CDDL source code integration to allow for automatic verification > - Reordered description in Section 7.3 and in Section 7.2 to better match the > order > of communication and artifact processing. > - Updated CDDL for the request-enroll trigger in Figure 13 according to the > outcome of the interim ANIMA WG meeting discussions on April 19, 2024 > - Included statement in Section 7.2.2 for using the advanced created-on time > from > the agent-signed-data also for the PER, when the pledge has no synchronized > clock > - updates examples in Annex 1, 2, 4 to match prototypes > - updated RVR to contain idevid-issuer as described in RFC 8995 in Section > 7.3.2 > > We will provide a status update during the ANIMA WG session of the upcoming > IETF meeting. > > Best regards > Steffen > > > -----Original Message----- > From: [email protected] <[email protected]> > Sent: Friday, July 5, 2024 1:54 PM > To: Michael C. Richardson <[email protected]>; Eliot Lear > <[email protected]>; Michael Richardson <[email protected]>; Fries, Steffen > (T CST) <[email protected]>; Werner, Thomas (T CST SEA-DE) > <[email protected]> > Subject: New Version Notification for draft-ietf-anima-brski-prm-13.txt > > A new version of Internet-Draft draft-ietf-anima-brski-prm-13.txt has been > successfully submitted by Steffen Fries and posted to the IETF repository. > > Name: draft-ietf-anima-brski-prm > Revision: 13 > Title: BRSKI with Pledge in Responder Mode (BRSKI-PRM) > Date: 2024-07-05 > Group: anima > Pages: 103 > URL: > https://www.ietf.org/ > %2Farchive%2Fid%2Fdraft-ietf-anima-brski-prm- > 13.txt&data=05%7C02%7Csteffen.fries%40siemens.com%7C1431de9f9423476d2d > 8208dc9cea42f9%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C63855 > 7777159494528%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo > iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=DnuM% > 2FshKEPAqP%2FsTnR3VIyJajS%2BBSXWhMzyhV4qTizs%3D&reserved=0 > Status: > https://datatracker.i/ > etf.org%2Fdoc%2Fdraft-ietf-anima-brski- > prm%2F&data=05%7C02%7Csteffen.fries%40siemens.com%7C1431de9f9423476 > d2d8208dc9cea42f9%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C63 > 8557777159507726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ > QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=BQt > KdcGNlA2RIqavl4Pscj88xanfIbDtDcYQ6RXEwvI%3D&reserved=0 > HTMLized: > https://datatracker.i/ > etf.org%2Fdoc%2Fhtml%2Fdraft-ietf-anima-brski- > prm&data=05%7C02%7Csteffen.fries%40siemens.com%7C1431de9f9423476d2d8 > 208dc9cea42f9%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638557 > 777159516517%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi > V2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=xzKtAGY > lsRZKe3BurTyFYIlmdMVS1Jhkd5xEGUgTc0s%3D&reserved=0 > Diff: > https://author-/ > tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-anima-brski-prm- > 13&data=05%7C02%7Csteffen.fries%40siemens.com%7C1431de9f9423476d2d82 > 08dc9cea42f9%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C6385577 > 77159523824%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=0ouldhBn8 > z%2Bv4Tl0IZqspv%2Byru48sFi%2BMo7i3fkG2zg%3D&reserved=0 > > 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 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 domain CA. > > > > The IETF Secretariat > > > _______________________________________________ > Anima mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
