Hi Sheng,
Just to chime in here, my understanding was that we collect all known
requirements for vouchers in RFC8366bis hoping that we covered all to avoid
increasing complexity during augmentation of the voucher. That said, I see a
normative reference of BRSKI-PRM to RFC 8366bis but not
Hi, please be aware that the YANG components of this will be moved to
rfc8366bis. They are already in the rfc8366bis-05, but I don't yet feel
that we have *WG* Consensus to do this.In general, I don't have preference
whether this document of rfc8366bis defines YANG components. The major
Sheng Jiang wrote:
> This message starts the two-week (*) ANIMA Working Group Last Call to
> advance draft-ietf-anima-brski-prm-06, which specifies enhancements to
> BRSKI (RFC8995) to facilitate bootstrapping in domains featuring no or
> only time limited connectivity between
Dear ANIMAers,
This message starts the two-week (*) ANIMA Working Group Last Call to advance
draft-ietf-anima-brski-prm-06, which specifies enhancements to BRSKI (RFC8995)
to facilitate bootstrapping in domains featuring no or only time limited
connectivity between apledge and the domain
