/[marcuscom]/IETF/trunk/i2rs-traceability/draft-clarke-i2rs-traceability.txt
ViewVC logotype

Diff of /IETF/trunk/i2rs-traceability/draft-clarke-i2rs-traceability.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 18734 by marcus, Sun Sep 8 14:29:30 2013 UTC revision 18735 by marcus, Sun Sep 8 15:03:31 2013 UTC
# Line 80  Table of Contents Line 80  Table of Contents
80       6.4.  Trace Log Retrieval . . . . . . . . . . . . . . . . . . .   9       6.4.  Trace Log Retrieval . . . . . . . . . . . . . . . . . . .   9
81         6.4.1.  Retrieval Via Syslog  . . . . . . . . . . . . . . . .   9         6.4.1.  Retrieval Via Syslog  . . . . . . . . . . . . . . . .   9
82         6.4.2.  Retrieval Via I2RS  . . . . . . . . . . . . . . . . .   9         6.4.2.  Retrieval Via I2RS  . . . . . . . . . . . . . . . . .   9
83     7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9         6.4.3.  Retrieval Via I2RS Pub-Sub  . . . . . . . . . . . . .   9
84       7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
85     8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10     8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
86     9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10     9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
87     10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10     10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
88       10.1.  Normative References . . . . . . . . . . . . . . . . . .  10       10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
89       10.2.  Informative References . . . . . . . . . . . . . . . . .  11       10.2.  Informative References . . . . . . . . . . . . . . . . .  11
90     Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11     Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11
91    
# Line 99  Table of Contents Line 100  Table of Contents
100     this is critical information to be used for troubleshooting I2RS     this is critical information to be used for troubleshooting I2RS
101     interactions.     interactions.
102    
103     This document specifies requirements and describes the information  
104     model for traceability attributes that must be collected and logged  
105     by I2RS Agents in order to effectively troubleshoot I2RS  
106     interactions.  In this context, effective troubleshooting means being  
107     able to identify what operation was performed by a specific I2RS  
108     Client, what was the result of the operation, and when that operation  
    was performed.  
109    
110    
111    
# Line 114  Clarke & Salgueiro       Expires March 1 Line 114  Clarke & Salgueiro       Expires March 1
114  Internet-Draft              I2RS Traceability             September 2013  Internet-Draft              I2RS Traceability             September 2013
115    
116    
117       This document specifies requirements and describes the information
118       model for traceability attributes that must be collected and logged
119       by I2RS Agents in order to effectively troubleshoot I2RS
120       interactions.  In this context, effective troubleshooting means being
121       able to identify what operation was performed by a specific I2RS
122       Client, what was the result of the operation, and when that operation
123       was performed.
124    
125  2.  Terminology  2.  Terminology
126    
127     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
# Line 153  Internet-Draft              I2RS Traceab Line 161  Internet-Draft              I2RS Traceab
161     model offers significant advantages and facilitates the following use     model offers significant advantages and facilitates the following use
162     cases:     cases:
163    
    o  Automated event correlation, trend analysis, and anomaly  
       detection.  
   
    o  Trace log storage for offline (manual or tools) analysis.  
   
    o  Improved accounting of routing system transactions.  
   
    o  Standardized structured data format for writing common tools.  
164    
165    
166    
# Line 170  Clarke & Salgueiro       Expires March 1 Line 170  Clarke & Salgueiro       Expires March 1
170  Internet-Draft              I2RS Traceability             September 2013  Internet-Draft              I2RS Traceability             September 2013
171    
172    
173       o  Automated event correlation, trend analysis, and anomaly
174          detection.
175    
176       o  Trace log storage for offline (manual or tools) analysis.
177    
178       o  Improved accounting of routing system transactions.
179    
180       o  Standardized structured data format for writing common tools.
181    
182     o  Common reference for automated testing and incident reporting.     o  Common reference for automated testing and incident reporting.
183    
184     o  Real-time monitoring and troubleshooting.     o  Real-time monitoring and troubleshooting.
# Line 212  Internet-Draft              I2RS Traceab Line 221  Internet-Draft              I2RS Traceab
221    
222    
223    
   
   
   
   
   
   
   
   
   
224  Clarke & Salgueiro       Expires March 12, 2014                 [Page 4]  Clarke & Salgueiro       Expires March 12, 2014                 [Page 4]
225    
226  Internet-Draft              I2RS Traceability             September 2013  Internet-Draft              I2RS Traceability             September 2013
# Line 496  Internet-Draft              I2RS Traceab Line 496  Internet-Draft              I2RS Traceab
496     collection mechanism either as a single snapshot or via a     collection mechanism either as a single snapshot or via a
497     subscription stream.     subscription stream.
498    
499  7.  IANA Considerations  6.4.3.  Retrieval Via I2RS Pub-Sub
500    
501    
502    
# Line 506  Clarke & Salgueiro       Expires March 1 Line 506  Clarke & Salgueiro       Expires March 1
506  Internet-Draft              I2RS Traceability             September 2013  Internet-Draft              I2RS Traceability             September 2013
507    
508    
509       Section 6.7 of the I2RS architecture [I-D.ietf-i2rs-architecture]
510       goes on to define a publish-subscribe mechanism for a feed of changes
511       happening within the I2RS layer.  I2RS Agents SHOULD support
512       publishing I2RS trace log information as described in this document
513       to that feed.  Subscribes would then receive a live stream of I2RS
514       interactions in trace log format and could choose to do a number of
515       things with the log messages.  For example, the subscribers could log
516       the messages to a datastore, aggregate and summarize interactions
517       from a single client, etc.  The full set of activites as well as the
518       details of how they are performed are outside the scope of this
519       document, however.
520    
521    7.  IANA Considerations
522    
523     This document makes no request of IANA.     This document makes no request of IANA.
524    
525  8.  Security Considerations  8.  Security Considerations
# Line 535  Internet-Draft              I2RS Traceab Line 549  Internet-Draft              I2RS Traceab
549     The authors would like to thank Carlos Pignataro for his contributed     The authors would like to thank Carlos Pignataro for his contributed
550     text, review comments, suggested improvements to this document.     text, review comments, suggested improvements to this document.
551    
552    
553    
554    
555    
556    
557    
558    
559    
560    Clarke & Salgueiro       Expires March 12, 2014                [Page 10]
561    
562    Internet-Draft              I2RS Traceability             September 2013
563    
564    
565  10.  References  10.  References
566    
567  10.1.  Normative References  10.1.  Normative References
# Line 553  Internet-Draft              I2RS Traceab Line 580  Internet-Draft              I2RS Traceab
580     [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate     [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
581                Requirement Levels", BCP 14, RFC 2119, March 1997.                Requirement Levels", BCP 14, RFC 2119, March 1997.
582    
   
   
   
   
 Clarke & Salgueiro       Expires March 12, 2014                [Page 10]  
   
 Internet-Draft              I2RS Traceability             September 2013  
   
   
583     [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform     [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
584                Resource Identifier (URI): Generic Syntax", STD 66, RFC                Resource Identifier (URI): Generic Syntax", STD 66, RFC
585                3986, January 2005.                3986, January 2005.
# Line 590  Internet-Draft              I2RS Traceab Line 608  Internet-Draft              I2RS Traceab
608    
609  Authors' Addresses  Authors' Addresses
610    
611    
612    
613    
614    
615    
616    Clarke & Salgueiro       Expires March 12, 2014                [Page 11]
617    
618    Internet-Draft              I2RS Traceability             September 2013
619    
620    
621     Joe Clarke     Joe Clarke
622     Cisco Systems, Inc.     Cisco Systems, Inc.
623     7200-12 Kit Creek Road     7200-12 Kit Creek Road
# Line 613  Authors' Addresses Line 641  Authors' Addresses
641    
642    
643    
644  Clarke & Salgueiro       Expires March 12, 2014                [Page 11]  
645    
646    
647    
648    
649    
650    
651    
652    
653    
654    
655    
656    
657    
658    
659    
660    
661    
662    
663    
664    
665    
666    
667    
668    
669    
670    
671    
672    Clarke & Salgueiro       Expires March 12, 2014                [Page 12]

Legend:
Removed from v.18734  
changed lines
  Added in v.18735

  ViewVC Help
Powered by ViewVC 1.1.27