Kim Davies wrote:
I'm afraid (1) should be documented by a separate rfc maybe titled
as "Relationship between IETF and IANA", which should clarify
semantics of "IANA considerations" section of not only this but
also other rfcs, which was not a problem when both of the rfc
editor and IANA was the same person.
Is the "IANA considerations" section just a recommendation from
IETF/ISOC to IANA/ICANN or approved by IANA/ICANN during *modified*
standardization process of IETF?
These are fair points and hopefully the language can be tweaked to make
it a little clearer.
No, they are my comments on a possible separate document definitely
*not* *against* your ID.
So, don't modify your ID for them only to introduce weasel wording,
please.
I merely think your draft can be better if it better clarifies
that the decisions are made by not IETF but IANA/ICANN, which
should be *already* accepted by the Internet community including
IETF.
(RFC 2860 does define the relationship between IETF
and IANA
But, the rfc says deprecation of some domain under "int" must
be decided by not IANA but IETF, which the Internet community
including IETF is not practical, which should result in your ID.
but the role of .INT was modified as a consequence of RFC
3172)
Rfc3172 certainly, though silently, assumes such consequences,
rfc2860 requires IETF, not IANA, should make them loudly explicit.
But, as the issues are highly operational for which IETF do
not and should not have much to do with, if something is
wrong, it should be rfc2860.
Moreover, as IETF is not governing the operational reality
of the Internet, I don't think it necessary to modify
rfc2860 before making your ID an up-to-date informational
rfc to reflect the operational reality.
Masataka Ohta
PS
To accommodate operational reality, I think, IANA functionalities
should be divided by three, one for domain name under ICANN, another
for IP addresses under operators community of RIRs and remaining
inoperational ones for IETF/ISOC, which, for formality, requires
modifications to rfc2860.
But, don't interpret it as my objection to your ID. We must move on.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
