Jim Fenton via Datatracker <noreply@xxxxxxxx> wrote:
> My biggest question about this draft is why it is separate from
> ietf-anima-rfc3866bis. It appears to be an extension to rfc3866bis, yet
> 3866bis is still being considered by the working group. 3866bis defines
So, because we started jws-voucher long before we realized we'd have to
revise 8366. Putting all the different signing algorithms into one document
might make sense if we were starting now, but OTH, it might just confuse
people when they look for examples.
In the end, we had to put all the YANG into a single document.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
Attachment:
signature.asc
Description: PGP signature
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
