Hi Sue, Jeff, The document describes a good framework which enables trace-ability of the interactions amongst I2RS modules, and provides data points for record/debugging purposes. I believe this framework provides a good value, thus I support the adoption of this document as a WG document.
I do have one question/comment to the authors but not a blocker for its WG adoption. The Log Entity describe one Timestamp. What does this Timestamp describe? Realistically, I can see 4 possibilities. - Time when I2RS agent received the request from an I2RS client. - Time when I2RS agent made the request to the Routing System. - Time when I2RS agent received the reply from the Routing System. - Time when I2RS agent sent the reply to to the I2RS client. If one was attempting to make sense of a scaled number of requests being processed by the I2RS agent (and some processed in parallel), having more than one Timestamp in a Log Entry may provide more insights into what was happening in the system. Thanks! -Nobo From: i2rs [mailto:[email protected]] On Behalf Of Susan Hares Sent: Tuesday, November 25, 2014 12:03 AM To: [email protected] Cc: 'Jeffrey Haas'; 'Alia Atlas' Subject: [i2rs] WG Adoption call for draft-clarke-i2rs-traceability-03 from 11/24 to 12/9/14 This is to begin a 2 week adoption call for draft-clarke-i2rs-traceability-03. Please include in your comments an indication of "support" or "no support." Thank you, Sue Hares and Jeff Haas
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
