You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the YANG voucher description the following leafe is included
// from BRSKI-CLOUD
leaf est-domain {
type ietf:uri;
description
"The est-domain is a URL from which the Pledge should
continue doing enrollment rather than with the
Cloud Registrar.
The pinned-domain-cert contains a trust-anchor
which is to be used to authenticate the server
found at this URI.
";
}
Would it be better to have a more generalized description to not make it specific to the enrollment protocol? As we have BRSKI-AE, it may be interesting to outsource the RA functionality also for other enrollment protocols.
A more general name may be ra-domain.
The text was updated successfully, but these errors were encountered:
In the YANG voucher description the following leafe is included
Would it be better to have a more generalized description to not make it specific to the enrollment protocol? As we have BRSKI-AE, it may be interesting to outsource the RA functionality also for other enrollment protocols.
A more general name may be ra-domain.
The text was updated successfully, but these errors were encountered: