John Levine <johnl@xxxxxxxxx> wrote:
>> I wound up going through it manually, and I found some DOIs that didn't work.
>> I reported this to RFC-editor. Maybe this belongs to DT.
>> I'm not sure which does the DOI dance. I'm assuming RFC editor/RPC.
> DOIs of our own documents that start with 10.17487/ or something else?
exactly.
> I wrote the
> original code that assigns our DOIs and uploads the metadata, so if it's one of ours
> that's a bug.
And rfc-editor runs this code, so they are the ones to tell about this bug?
Specifically,
obiwan-[~](3.2.2) mcr 10454 %curl -I https://doi.org/10.17487/rfc9031
HTTP/2 404
...
(and 9032). But others did work. (I was entering this into ORCID's
interface, it was failing, and I investigated deeper)
I reported this.
If I was more enterprising, I'd write a loop to test them all :-)
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
Attachment:
signature.asc
Description: PGP signature
