I would like to see the draft adopted by the WG, without the YANG model.

Thank you,
Joel

On 7/23/14, 1:26 PM, Joe Clarke wrote:
At the meeting yesterday, the chairs called out a few non-chartered
drafts that had progressed and should have a final decision made as to
their future.  One was our draft-clarke-i2rs-traceability.

I would like to address the question the chairs raised on the draft and
ask the WG if this can be adopted.  The question was, should this draft
be standalone or part of the architecture doc.

This draft originally began as comments to Alia on the arch draft.  Alia
suggested that a draft outlining what should be logged for purposes of
traceability should be created independent of the arch.  Since then, the
arch has had some traceability language added, but the details spelled
out in draft-clarke-i2rs-traceability take these "breadcrumbs" and
expand on them specific to what would be required for those needing to
do diagnostic operations, accounting, and auditing.  On top of that, the
architecture draft is very well-baked right now, and would benefit from
going through on its own.

In that case, I feel that this draft-clarke-i2rs-traceability stands
very much on its own and compliments the arch draft.

Some of the feedback we've had on our latest rev (-02) was regarding the
YANG model we added.  The comments have been that a YANG model really
isn't needed here.  In fact, some of the general parts of this might fit
in the new syslog model work happening in NETMOD.  We would not be
opposed to taking out this module, and retaining the English text
explaining the importance of logging in I2RS as well as what should be
logged.

Therefore, we (the authors) would ask the WG for two things:

1. Closure on the YANG module question.
2. Adoption of draft-clarke-i2rs-traceability as a WG item

Thank you.

_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs


_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to