CLUE A. Romanow Internet-Draft Cisco Systems Intended status: Standards Track A. Pepperell Expires: December 8, 2012 Silverflare June 6, 2012 Data model for the CLUE Framework draft-romanow-clue-data-model-01 Abstract This draft is for discussion in the CLUE working group. It proposes a data model for the CLUE Framework. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 8, 2012. Copyright Notice Copyright (c) 2012 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. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Romanow & Pepperell Expires December 8, 2012 [Page 1] Internet-Draft Data Model for CLUE June 2012 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Data model format . . . . . . . . . . . . . . . . . . . . 4 3.2. Data model namespace . . . . . . . . . . . . . . . . . . . 4 3.3. Data Model Structure . . . . . . . . . . . . . . . . . . . 4 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 4 4.1. . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. . . . . . . . . . . . . . . . . . . 6 4.3. . . . . . . . . . . . . . . . . . . . . . . . 6 4.4. . . . . . . . . . . . . . . . . . . . . . . . 6 4.5. . . . . . . . . . . . . . . . . . . . . . . 6 4.6. . . . . . . . . . . . . . . . . . . . . . . . . 6 4.7. . . . . . . . . . . . . . . . . . . . . . . . . 6 4.8. . . . . . . . . . . . . . . . . . . 7 4.8.1. . . . . . . . . . . . . . . . . . . 7 4.8.2. . . . . . . . . . . . . . . . . . . . . 7 4.8.3. . . . . . . . . . . . . . . . . 7 4.9. . . . . . . . . . . . . . . . . . . 7 4.10. . . . . . . . . . . . . . . . . . . . 7 4.11. . . . . . . . . . . . . . 7 4.12. . . . . . . . . . . . . . . . . . . . . . 7 4.12.1. . . . . . . . . . . . . . . . . . 8 4.12.2. . . . . . . . . . . . . . . . 8 4.12.3. . . . . . . . . . 8 4.12.4. . . . . . . . . . . . 8 4.13. . . . . . . . . . . . . . 8 4.14. . . . . . . . . . . . . . . . . . . . 9 4.14.1. . . . . . . . . . . . . . . . . . . . . . . 9 4.14.2. . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 7.2. Informative References . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Romanow & Pepperell Expires December 8, 2012 [Page 2] Internet-Draft Data Model for CLUE June 2012 1. Introduction This document proposes a data model for the CLUE Framework [I-D.ietf- clue-framework]. The previous suggestion for a data model described the 2 CLUE messages, provider advertisement and consumer choice message. The data model proposed here differs in that it describes the basic information, or definitions that are needed. Messages can then derived from the data model, similarly to what was described in the earlier data model. The provider advertisement and the consumer choice messages can use or not use any of the data elements defined in the data model, subject only to whether or not the element is deemed mandatory. The model here follows the example of the xcon data model RFC 6501 [RFC6501]. Initially the data model may seem to describe only provider advertisements. But this is not the case. The consumer choice messages can also be constructed from these elements. Many of the data elements are similar for both messages, but there are also elements defined which are used only in one or the other of the messages. One of the challenges here is that in addition to proposing a structure for the data model, we would like to also propose some additions or changes to what is in the current framework document. The problem is that any changes from what is in the current framework can detract attention from the basic information model which is the primary focus of this draft initially. We have noted where there are changes from the framework by putting the text in all capital text. This is a rough draft, its goal is to propose a basic structure and stimulate discussion. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119] and indicate requirement levels for compliant implementations. Romanow & Pepperell Expires December 8, 2012 [Page 3] Internet-Draft Data Model for CLUE June 2012 3. Overview TEXT 3.1. Data model format A CLUE object document is an XML [W3C.REC-xml-20081126] document. CLUE object documents MUST be based on XML 1.0 and MUST be encoded using UTF-8. 3.2. Data model namespace This specification defines a new namespace specification for identifying the elements defined in the data model. This namespace is as follows: urn:ietf:params:xml:ns:clue-info 3.3. Data Model Structure The information in this data model is structured in the following manner. All the information communicated between consumers and providers in a CLUE session is contained in a element. The definitions follow directly from the Framework document. The element contains the following child elements: o The element describes the captures. It includes all the elements that have been discussed in the framework document as properties of captures document and it can be extended by adding additional elements describing a capture. o The element is the data structure that describes the captures that the provider is capable of sending in a way that is helpfule to the consumer to decide what captures to request. o The element is a data structure that describes the physical simultaneity constraints, as discussed in the framework. o The element describes the encoding characteristics of the streams. 4. Data Model Definition The following non-normative diagram shows the structure of CLUE elements. The symbol "!" preceding an element indicates that the element is REQUIRED in the data model. Romanow & Pepperell Expires December 8, 2012 [Page 4] Internet-Draft Data Model for CLUE June 2012 ! | |-- | |-- | |-- | |-- | |-- | |-- | |-- | | |-- | | |-- | | |-- | |-- | |-- | |-- |-- | |-- | | |-- | | |-- | |-- | |-- | | |-- | | |-- | |-- |-- | |-- | | |-- |-- | |-- | | |-- | | |-- | | |-- | | |-- | | |-- | | |-- | | |-- | | |-- | | |-- | | |-- | |-- | | |-- | | |-- | |