Hello ACME, Other than MCR's editorial comments, there was no traffic on this thread. I will assume that means nobody objects to its publication.
As this is my first time advancing a document out of the WG, and we are in the busy lead-up-to-Montreal weeks, I may need to wait until Montreal to get someone to sit down with me on the actual mechanics of advancing a document. On Mon, 6 Oct 2025 at 16:09, Michael Richardson <[email protected]> wrote: > > 0. Please fix the file name for this *adopted* I-D. > Just email [email protected], and they will fix it. > Or just post a new I-D, setting the replaces correctly. > I will *NOT* be the last person to be confused by this. > > 1. I am not happy with the title of the document. > > It is not about *Device* *Attestation*. > Yes, it uses the WebAuthN "attestation object", but that's all. > > This (very useful!) document is about authorizing RFC4108/otherName > identities. It should be named for that. > > Readers will otherwise be confused. > > -- > Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > > > _______________________________________________ > Acme mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Acme mailing list -- [email protected] To unsubscribe send an email to [email protected]
