I could not figure out how to do an update to a document that does not have an RFC number yet. I think we will have ot add the new number when the RFC Editor assigns a number for 8152bis.
Russ > On Apr 19, 2021, at 6:29 AM, Ivaylo Petrov <[email protected]> wrote: > > Hello Russ, > > Thank you for posting the updated version of the countersign draft! It > sounded like the conclusion from the previous discussion was to put > the countersign document as updating both the 8152 and 8152bis, while > your new version only adds RFC 8152 as updated. Could you comment on > that? > > Thank you, > Ivaylo > > On Wed, Apr 14, 2021 at 5:47 PM Russ Housley <[email protected]> wrote: >> >> >> On Mar 10, 2021, at 10:03 PM, Michael Richardson <[email protected]> >> wrote: >> >> To me, that suggests not adding -countersign to the cluster and >> sticking with Updates, but I'd like to hear from others before taking >> any action here. >> >> >> I agree with just adding the two Updates: to countersign. >> >> >> I agree with this way forward. I'll post an update that adjusts the title >> page. >> >> Russ >> >> _______________________________________________ >> COSE mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/cose > > _______________________________________________ > COSE mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/cose _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
