Christian Amsüss <[email protected]> wrote: > I think this is as compact as it gets, with all the options of > repetition deferred to future development (sketched in an appendix for > the benefit of future documents), it's really just a simple number.
Agreed. Rifaat,MikeO and I have just posted draft-yusef-lamps-rfc7030-renewal-recommendation. It replicates RFC9773 (an ACME thing) into EST/RFC7030. It (renewal-info) probably should also update RFC9148 to add a new renewal-info for EST-coaps. So this would fit into the path-abbrev 30x space! I think it will be fine for renewal-info to block on publication of abbrev. Probably renewal-info should return CBOR for 9148 use, so we'll need to do CDDL. So I'll include IANA Considerations in that document. ---- I think that renewal-info will have to resurrect the well-known/EST registry that RFC8995 created as I-D, then walked back to make well-known/BRSKI instead near the last minute... -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Ace mailing list -- [email protected] To unsubscribe send an email to [email protected]
