Alissa,
On 10/10/2018 2:48 PM, Alissa Cooper wrote:
On Oct 10, 2018, at 2:32 PM, Dave Crocker <d...@dcrocker.net> wrote:
On 10/10/2018 10:52 AM, Alissa Cooper wrote:
I think this document needs to state explicitly which updates apply to which
existing RFCs. That is, I would expect to see in sections 2.1, 2.2, and 2.3
the list of which documents are updated by each section. I realize this can be
intuited, but typically for avoidance of doubt authors specify precisely which
updates apply to which documents. This will also clear up the unused references
that idnits is pointing out.
What is the downside of using the existing text, as compared against the effort
(and delay -- quite possibly infinite) caused by requiring development of the
considerable detail that you are calling for?
I think the downsides are (1) people reading the documents updated by this
document are confused about which parts of the update apply, and (2) it sets a
precedent that one RFC can update another without being specific about what is
being updated.
I’m not asking for considerable detail, I’m asking for each of 2.1, 2.2, and
2.3 to specify which documents out of the list in the Updates header they
update.
So by my count, that requires going over roughly 35 documents (again) to
audit and document this additional detail.
My guess is that the burden on someone updating one of those documents,
seeing the reference to -fix, and being able to properly determine
whether their document revision needs to attend to the section on TXT
RRset usage and/or SRV RRset usage and/or URI RRset usage is minimal,
and the risk of their getting it wrong is zero.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
