On 26/04/2012 02:06, Pete Resnick wrote:
On 4/25/12 5:03 AM, Benoit Claise wrote:
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
- I see a lot of sentences such as "... discussed in Section X of
[RFC6449]."
And the only sentence in the introduction related to that RFC is:
"Further introduction to this topic may be found in [RFC6449]."
Some sentences explaining what this informational RFC is about
would be
very welcome.
I propose this as the last paragraph to the Introduction:
Further introduction to this topic may be found in<xref
target="RFC6449"/>, which is effectively an Applicability Statement
written outside of the IETF and thus never achieved IETF consensus.
Much of the content for that document was input to this one.
Thanks. Can you please also a few sentences on how the documents
match and differ.
You know, I see rfc6449, published a few months back, and I see this
document draft-ietf-marf-as-14, which will be published approx. 6 months
And I'm wondering, as someone not involved in this WG...
- Why do we have two almost similar documents?
- Why RFC 6449 could not be a MARF document?
- Which one(s) should I read?
- Are they conflicting? If yes, I guess that draft-ietf-marf-as-14
take precedence. If no, is draft-ietf-marf-as-14 is superset of RFC
6449, and RFC 6449 should not be read any longer.
- etc...
I'm sure you had very good answers to all these questions, and I'm
looking for some written explanation for new comers in this space.
After chatting with Benoit offline, I now believe that your addition
actually increased confusion rather than decreased. What I think you
want to say is something like, "Further introduction to this topic may
be found in 6449, which has more information about the general topic
of abuse reporting. Many of the specific ARF guidelines in this
document were taken from the principles presented in 6449."
That works for me.
Regards, Benoit.
The text you've got now 'buries the lead'.
Not required, but I think this might help.
pr
_______________________________________________
marf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/marf