idnits 2.17.1 draft-romanow-clue-data-model-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 6, 2012) is 4314 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.ietf-clue-framework' is defined on line 474, but no explicit reference was found in the text == Unused Reference: 'I-D.lennox-clue-rtp-usage' is defined on line 479, but no explicit reference was found in the text == Outdated reference: A later version (-25) exists of draft-ietf-clue-framework-05 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CLUE A. Romanow 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track A. Pepperell 5 Expires: December 8, 2012 Silverflare 6 June 6, 2012 8 Data model for the CLUE Framework 9 draft-romanow-clue-data-model-01 11 Abstract 13 This draft is for discussion in the CLUE working group. It proposes 14 a data model for the CLUE Framework. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on December 8, 2012. 33 Copyright Notice 35 Copyright (c) 2012 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 3.1. Data model format . . . . . . . . . . . . . . . . . . . . 4 54 3.2. Data model namespace . . . . . . . . . . . . . . . . . . . 4 55 3.3. Data Model Structure . . . . . . . . . . . . . . . . . . . 4 56 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 4 57 4.1. . . . . . . . . . . . . . . . . . . . . . . . 6 58 4.2. . . . . . . . . . . . . . . . . . . 6 59 4.3. . . . . . . . . . . . . . . . . . . . . . . . 6 60 4.4. . . . . . . . . . . . . . . . . . . . . . . . 6 61 4.5. . . . . . . . . . . . . . . . . . . . . . . 6 62 4.6. . . . . . . . . . . . . . . . . . . . . . . . . 6 63 4.7. . . . . . . . . . . . . . . . . . . . . . . . . 6 64 4.8. . . . . . . . . . . . . . . . . . . 7 65 4.8.1. . . . . . . . . . . . . . . . . . . 7 66 4.8.2. . . . . . . . . . . . . . . . . . . . . 7 67 4.8.3. . . . . . . . . . . . . . . . . 7 68 4.9. . . . . . . . . . . . . . . . . . . 7 69 4.10. . . . . . . . . . . . . . . . . . . . 7 70 4.11. . . . . . . . . . . . . . 7 71 4.12. . . . . . . . . . . . . . . . . . . . . . 7 72 4.12.1. . . . . . . . . . . . . . . . . . 8 73 4.12.2. . . . . . . . . . . . . . . . 8 74 4.12.3. . . . . . . . . . 8 75 4.12.4. . . . . . . . . . . . 8 76 4.13. . . . . . . . . . . . . . 8 77 4.14. . . . . . . . . . . . . . . . . . . . 9 78 4.14.1. . . . . . . . . . . . . . . . . . . . . . . 9 79 4.14.2. . . . . . . . . . . . . . . . . . . . 10 80 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 81 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 82 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 83 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 84 7.2. Informative References . . . . . . . . . . . . . . . . . . 11 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 87 1. Introduction 89 This document proposes a data model for the CLUE Framework [I-D.ietf- 90 clue-framework]. 92 The previous suggestion for a data model described the 2 CLUE 93 messages, provider advertisement and consumer choice message. The 94 data model proposed here differs in that it describes the basic 95 information, or definitions that are needed. Messages can then 96 derived from the data model, similarly to what was described in the 97 earlier data model. 99 The provider advertisement and the consumer choice messages can use 100 or not use any of the data elements defined in the data model, 101 subject only to whether or not the element is deemed mandatory. 103 The model here follows the example of the xcon data model RFC 6501 104 [RFC6501]. 106 Initially the data model may seem to describe only provider 107 advertisements. But this is not the case. The consumer choice 108 messages can also be constructed from these elements. Many of the 109 data elements are similar for both messages, but there are also 110 elements defined which are used only in one or the other of the 111 messages. 113 One of the challenges here is that in addition to proposing a 114 structure for the data model, we would like to also propose some 115 additions or changes to what is in the current framework document. 116 The problem is that any changes from what is in the current framework 117 can detract attention from the basic information model which is the 118 primary focus of this draft initially. We have noted where there are 119 changes from the framework by putting the text in all capital text. 121 This is a rough draft, its goal is to propose a basic structure and 122 stimulate discussion. 124 2. Terminology 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 128 document are to be interpreted as described in RFC 2119 [RFC2119] and 129 indicate requirement levels for compliant implementations. 131 3. Overview 133 TEXT 135 3.1. Data model format 137 A CLUE object document is an XML [W3C.REC-xml-20081126] document. 138 CLUE object documents MUST be based on XML 1.0 and MUST be encoded 139 using UTF-8. 141 3.2. Data model namespace 143 This specification defines a new namespace specification for 144 identifying the elements defined in the data model. This namespace 145 is as follows: urn:ietf:params:xml:ns:clue-info 147 3.3. Data Model Structure 149 The information in this data model is structured in the following 150 manner. All the information communicated between consumers and 151 providers in a CLUE session is contained in a element. 152 The definitions follow directly from the Framework document. 154 The element contains the following child elements: 156 o The element describes the captures. It 157 includes all the elements that have been discussed in the 158 framework document as properties of captures document and it can 159 be extended by adding additional elements describing a capture. 160 o The element is the data structure that describes 161 the captures that the provider is capable of sending in a way that 162 is helpfule to the consumer to decide what captures to request. 163 o The element is a data structure 164 that describes the physical simultaneity constraints, as discussed 165 in the framework. 166 o The element describes the encoding 167 characteristics of the streams. 169 4. Data Model Definition 171 The following non-normative diagram shows the structure of CLUE 172 elements. The symbol "!" preceding an element indicates that the 173 element is REQUIRED in the data model. 175 ! 176 | 177 |-- 178 | |-- 179 | |-- 180 | |-- 181 | |-- 182 | |-- 183 | |-- 184 | | |-- 185 | | |-- 186 | | |-- 187 | |-- 188 | |-- 189 | |-- 190 |-- 191 | |-- 192 | | |-- 193 | | |-- 195 | |-- 196 | |-- 197 | | |-- 198 | | |-- 199 | |-- 200 |-- 201 | |-- 202 | | |-- 203 |-- 204 | |-- 205 | | |-- 206 | | |-- 207 | | |-- 208 | | |-- 209 | | |-- 210 | | |-- 211 | | |-- 212 | | |-- 213 | | |-- 214 | | |-- 215 | |-- 216 | | |-- 217 | | |-- 218 | |