What is the problem you are solving by having the indirection through the new
IANA registry? There are a zillion downsides to such an IANA registry, only a
few of which you cover in the current version of the draft.
Proposal 1: an EXTRA-TEXT field containing the template itself:
{
"template": "https://resolver.example.com/filtering-incidents/{inc}";,
"inc": "abc123"
}
Proposal 2: an EXTRA-TEXT field containing a place controlled by the resolver
operator to store templates:
{
"template_location":
"https://resolver.example.com/.well-known/pub-res-errors/";,
"inc": "abc123"
}
These both have the same security properties as giving a "ro" string, they
don't require a lookup to IANA, and they don't require IANA to keep a new FCFS
registry that could be very problematic.
--Paul Hoffman
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
