--On Wednesday, July 05, 2017 8:01 AM -0400 Suzanne Woolf
<suzworldwide(_at_)gmail(_dot_)com> wrote:
(not sure which hat. Probably doc shepherd.)
...
This is a very good question. We weren't asked to answer
that question, so we didn't. It is assumed throughout the
document that various proponents of special use domains have
good reasons for wanting them, and further that it is already
accepted in principle that if their reason for wanting them
is valid, they can have them (modulo technical constraints
like delegation). So we didn't delve into that. But perhaps
we should have.
I'd go a step further: RFC 6761 alludes to some general
reasons, but assumes people who'd go through the IETF
standards process or an IESG approval process to get an entry
in the special use names registry have good enough reasons
that the special handling requested should be accepted as part
of the DNS protocol. (I'm one of the people who isn't
comfortable with this assertion, but we're living with what
RFC 6761 says, not what I think it should have said.)
That is, RFC 6761 leaves to other processes to assess the
value of the request and the reasons offered, but strictly
speaking doesn't require them to be documented or evaluated;
required documentation for the registry entry consists mostly
of assessing how it interacts with the DNS, not its primary
use. (Sec. 4 starts by saying "If it is determined that
special handling of a name is required in order to implement
some desired new functionality," the registry entry policy
applies, but openly avoids describing how that determination
should be made.)
...
I think the observation that people aren't really required
to document what problem they are trying to solve with their
special use name is in the draft, but perhaps could be more
explicit.
Some few people already have been convinced that there should
be some general guidance available for making the
determination that a domain name requires special handling in
the DNS. But that also seems to be a different document.
Suzanne,
Independent of "general guidance", I think the combination of
the I-D, this thread to date, and your comments above make an
extremely strong case for updating RFC 6761 to require
documentation of the problem and discussion of other
alternatives and why they are unworkable. Whatever else the
problem statement does, I think it makes it clear that yet
another special name should be viewed as a preference only if
there are no reasonable alternatives rather than, e.g., an
option for global vanity names.
While "general guidance for making the determination" would be,
IMO, desirable, I can imagine months (or years) of quibbling
before agreement could be reached on such criteria. In the
interim, I'd think a requirement for documentation and
explanation sufficient to satisfy the IETF would be in order if
only as an interim measure to prevent proposals whose main
justification is "because I want one of my very own".
Anyone in DNSOP want to write a one-page RFC?
john