The Network Trouble Ticket Data Model (NTTDM)
RFC 6137
Document | Type |
RFC - Experimental
(February 2011; Errata)
Was draft-dzis-nwg-nttdm (gen)
|
|
---|---|---|---|
Authors | Dimitris Zisiadis , Spyros Kopsidas , Matina Tsavli , Guillaume Cessieux | ||
Last updated | 2020-01-21 | ||
Stream | ISE | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Stream | ISE state | (None) | |
Consensus Boilerplate | Unknown | ||
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6137 (Experimental) | |
Telechat date | |||
Responsible AD | Peter Saint-Andre | ||
Send notices to | Xavier.Jeannin@urec.cnrs.fr, rfc-ise@rfc-editor.org, leandros@uth.gr, tziou@grnet.gr |
Independent Submission D. Zisiadis, Ed. Request for Comments: 6137 S. Kopsidas, Ed. Category: Experimental M. Tsavli, Ed. ISSN: 2070-1721 CERTH G. Cessieux, Ed. CNRS February 2011 The Network Trouble Ticket Data Model (NTTDM) Abstract Handling multiple sets of network trouble tickets (TTs) originating from different participants' inter-connected network environments poses a series of challenges for the involved institutions. A Grid is a good example of such a multi-domain project. Each of the participants follows different procedures for handling trouble in its domain, according to the local technical and linguistic profile. The TT systems of the participants collect, represent, and disseminate TT information in different formats. As a result, management of the daily workload by a central Network Operation Centre (NOC) is a challenge on its own. Normalization of TTs to a common format at the central NOC can ease presentation, storing, and handling of the TTs. In the present document, we provide a model for automating the collection and normalization of the TT received by multiple networks forming the Grid. Each of the participants is using its home TT system within its domain for handling trouble incidents, whereas the central NOC is gathering the tickets in the normalized format for repository and handling. XML is used as the common representation language. The model was defined and used as part of the networking support activity of the EGEE (Enabling Grids for E-sciencE) project. Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Zisiadis, et al. Experimental [Page 1] RFC 6137 NTTDM February 2011 Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6137. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Table of Contents 1. Introduction ....................................................4 1.1. Terminology ................................................5 1.2. Notations ..................................................6 1.3. About the Network Trouble Ticket Data Model ................6 1.4. About the Network Trouble Ticket Implementation ............7 1.5. Future Plans ...............................................7 2. NTTDM Types and Definitions .....................................7 2.1. Types and Definitions for the TYPE Attribute ...............8 2.1.1. Defined .............................................8 2.1.2. Free ................................................8 2.1.3. Multiple ............................................8 2.1.4. List ................................................8 2.2. Types and Definitions for the VALID FORMAT Attributes ......9 2.2.1. Predefined String ...................................9 2.2.1.1. Definitions of the Predefined Values ......10 2.2.2. String .............................................13 2.2.3. Datetime ...........................................13 3. NTTDM ..........................................................14 3.1. NTTDM Components ..........................................14 3.1.1. NTTDM Attributes ...................................14 3.2. NTTDM Aggregate Classes ...................................15 3.2.1. NTTDM-Document Class ...............................15 3.2.2. Ticket Class .......................................15Show full document text