Because JP is an integral part of the cBRSKI solution, the JP issues need to be resolved before cBRSKI can progress.
For example the security considerations of JP selecting a genuine/right Registrar are important. (Since with some discovery methods like mDNS / DNS-SD with SRP registration / CoAP RD / CoAP discovery / ... anyone could pose as a Registrar and onboard the Pledge to the wrong domain; if MASA adheres to the TOFU-domain rules of 8995.)
See issues here: https://github.com/anima-wg/constrained-join-proxy/issues
Because JP is an integral part of the cBRSKI solution, the JP issues need to be resolved before cBRSKI can progress.
For example the security considerations of JP selecting a genuine/right Registrar are important. (Since with some discovery methods like mDNS / DNS-SD with SRP registration / CoAP RD / CoAP discovery / ... anyone could pose as a Registrar and onboard the Pledge to the wrong domain; if MASA adheres to the TOFU-domain rules of 8995.)