Ilari, agreed on registering it to the Underscored and Globally Scoped DNS Node Names registry. I've updated the draft to include that.
As for why _ and not -, I'll leave that to Antonis to explain the historical reason of. Note, we had submitted an informational post earlier as well: https://mailarchive.ietf.org/arch/msg/acme/0wbLS2JOgezvznY7XsL2dRb7sNc/ All, thank you for explaining the naming conventions regarding the documents. I'm learning slowly as we go through this process :) Cheers! Amir On Thu, Oct 20, 2022 at 4:53 PM Salz, Rich <rsalz= [email protected]> wrote: > > Actually, you SHOULD use that construction of a draft name. > > You SHOULD NOT use (and will be actively prevented from using, unless > a WG chair is asleep at the wheel) > > draft-ietf-acme-**, > > as that is reserved for adopted WG documents. > > Yes, you're right, I took the wildcard too literally :) > > _______________________________________________ > Acme mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/acme >
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
