1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
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
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
|
<pre>Internet Engineering Task Force (IETF) K. Sankar, Ed.
Request for Comments: 6208 Cisco
Category: Informational A. Jones
ISSN: 2070-1721 SNIA
April 2011
<span class="h1">Cloud Data Management Interface (CDMI) Media Types</span>
Abstract
This document describes several Internet media types defined for the
Cloud Data Management Interface (CDMI) by the Storage Networking
Industry Association (SNIA). The media types are:
o application/cdmi-object
o application/cdmi-container
o application/cdmi-domain
o application/cdmi-capability
o application/cdmi-queue
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6208">http://www.rfc-editor.org/info/rfc6208</a>.
<span class="grey">Sankar & Jones Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Requirements Language ......................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Cloud Data Management Domain and Its Relevance ..................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Processing Guidelines ...........................................<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Media Type: application/cdmi-object ........................<a href="#page-4">4</a>
<a href="#section-3.2">3.2</a>. Media Type: application/cdmi-container .....................<a href="#page-4">4</a>
<a href="#section-3.3">3.3</a>. Media Type: application/cdmi-domain ........................<a href="#page-5">5</a>
<a href="#section-3.4">3.4</a>. Media Type: application/cdmi-capability ....................<a href="#page-5">5</a>
<a href="#section-3.5">3.5</a>. Media Type: application/cdmi-queue .........................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Transport Considerations ........................................<a href="#page-6">6</a>
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-6">6</a>
<a href="#section-5.1">5.1</a>. Media Type: application/cdmi-object ........................<a href="#page-6">6</a>
<a href="#section-5.2">5.2</a>. Media Type: application/cdmi-container .....................<a href="#page-7">7</a>
<a href="#section-5.3">5.3</a>. Media Type: application/cdmi-domain ........................<a href="#page-8">8</a>
<a href="#section-5.4">5.4</a>. Media Type: application/cdmi-capability ....................<a href="#page-9">9</a>
<a href="#section-5.5">5.5</a>. Media Type: application/cdmi-queue ........................<a href="#page-10">10</a>
<a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-11">11</a>
<a href="#section-6.1">6.1</a>. Confidentiality and Integrity .............................<a href="#page-11">11</a>
<a href="#section-6.2">6.2</a>. Access Control ............................................<a href="#page-11">11</a>
<a href="#section-6.3">6.3</a>. Audit .....................................................<a href="#page-12">12</a>
<a href="#section-6.4">6.4</a>. JSON Security Considerations ..............................<a href="#page-12">12</a>
<a href="#section-6.5">6.5</a>. Executable/Active Content .................................<a href="#page-12">12</a>
<a href="#section-7">7</a>. Acknowledgements ...............................................<a href="#page-12">12</a>
<a href="#section-8">8</a>. References .....................................................<a href="#page-12">12</a>
<a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-12">12</a>
<a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-13">13</a>
<span class="grey">Sankar & Jones Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Cloud Data Management Interface (CDMI) [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>], developed by the
Storage Networking Industry Association (SNIA), is the functional
interface that applications will use to create, retrieve, update, and
delete data elements from the cloud. As part of this interface, the
client will be able to discover the capabilities of the cloud storage
offering and use this interface to manage containers and the data
that is placed in them. In addition, metadata can be set on
containers and their contained data elements through this interface.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
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 <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Cloud Data Management Domain and Its Relevance</span>
A storage cloud is a storage service hosted either on premise or off
premise, across a network. An important part of the cloud model, in
general, is the concept of a pool of resources that are drawn from,
on demand, in small increments (smaller than what one would typically
purchase by buying equipment). By abstracting data storage behind a
set of service interfaces and delivering it on demand, a wide range
of actual offerings and implementations are possible. The only type
of storage that is excluded from this definition is that which is
delivered based on fixed capacity increments rather than on demand.
The CDMI defines a set of functional interfaces (data paths) and
management interfaces (control paths) to create, retrieve, update,
and delete data elements from a storage cloud. Another important
concept in this standard is that of metadata. When managing large
amounts of data with differing requirements, metadata is a convenient
mechanism to express those requirements in such a way that underlying
data services can differentiate their treatment of the data to meet
those requirements. CDMI also defines an extensible metadata system
for storage clouds.
As part of the CDMI interface, the client will be able to discover
the capabilities of the cloud storage offering and to use this
interface to manage containers and the data that is placed in them.
In addition, system metadata can be added to containers and their
contained data elements through this interface.
<span class="grey">Sankar & Jones Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
The hierarchy that CDMI defines is as follows:
o The basic element of storage is an object.
o Objects are stored in a container hierarchy.
o CDMI also defines an object, called a queue, which has special
properties for in-order, first-in, first-out creation and fetching
of queue objects, similar to a container of data objects.
o A cloud offering can also support domains, which allow
administrative ownership to be associated with stored objects.
Domains can also be hierarchical, allowing for corporate domains
with multiple children domains for departments or individuals.
The domain concept is also used to map Access Control Lists (ACLs)
to principals as well as to aggregate usage data that is used to
bill, meter, and monitor cloud usage. (Note: The CDMI "domain"
defined here is not a DNS domain name as specified in [<a href="./rfc1076" title=""HEMS monitoring and control language"">RFC1076</a>]
and [<a href="./rfc1024" title=""HEMS variable definitions"">RFC1024</a>]).
o Finally, a capabilities resource and associated URI [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]
allows a client to discover the capabilities of the offering and
its implementation of CDMI.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Processing Guidelines</span>
This section summarizes the processing of each media type. This
document provides only the essential information. The CDMI
specification [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>], which has more details and appropriate
examples, is the final authority on the processing aspects.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Media Type: application/cdmi-object</span>
A CDMI object is the basic storage element in a CDMI system and is
analogous to a file within a filesystem. The object is represented
in the CDMI interface in JavaScript Object Notation (JSON) format
[<a href="./rfc4627" title=""The application/json Media Type for JavaScript Object Notation (JSON)"">RFC4627</a>]. (See the JSON web site at [<a href="#ref-JSON-1" title=""Introducing JSON"">JSON-1</a>] for general
information about JSON). Each data object has a set of well-defined
fields that includes a single value and optional metadata. The
implementations are free to store the data in any form they choose,
but the application/cdmi-object SHOULD be represented in the CDMI
interface as defined in <a href="#section-8">Section 8</a> of the CDMI specification [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>].
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Media Type: application/cdmi-container</span>
A container object is the fundamental grouping of stored data within
CDMI and is analogous to a directory within a filesystem. Each
container has zero or more child objects and a set of well-defined
<span class="grey">Sankar & Jones Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
fields that includes standardized and custom metadata. A container
can include other containers similar to sub-directories in a
filesystem. The implementations are free to represent the container
in any form they choose, but the application/cdmi-container SHOULD be
represented in the CDMI interface as defined in <a href="#section-9">Section 9</a> of the CDMI
specification [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>].
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Media Type: application/cdmi-domain</span>
Domain objects represent the concept of administrative ownership of
stored data within a CDMI storage system. A CDMI offering may
include a hierarchy of domains that provide access to domain-related
information within a CDMI context. This domain hierarchy is a series
of CDMI objects that correspond to parent and child domains, with
each domain corresponding to logical groupings of objects that are to
be managed together. <a href="#section-10">Section 10</a> of the CDMI specification [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>]
details the information content, representation, and processing of
domain objects.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Media Type: application/cdmi-capability</span>
Capability objects form a special class of container objects that
allows a CDMI client to discover what subset of the CDMI standard is
implemented by a CDMI provider. For each URI in a CDMI system, the
set of interactions that the system is capable of performing against
that URI is described by the presence of named "capabilities". Each
capability present for a given URI indicates what functionality the
cloud storage system will allow against that URI. Capabilities are
always static. <a href="#section-12">Section 12</a> of the CDMI specification [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>] details
the representation and processing of capability objects.
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Media Type: application/cdmi-queue</span>
Queues are a special class of container object and are used to
provide first-in, first-out access when storing and retrieving data.
A queue writer PUTs objects in the queue, and a queue reader GETs
objects from the queue, acknowledging the receipt of the last object
that it received. Queuing provides a simple mechanism for one or
more writers to send data to a single reader in a reliable way. If
queues are supported by the cloud storage system, cloud clients
create the queue objects by using the same mechanism used to create
data objects. <a href="#section-11">Section 11</a> of the CDMI specification [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>] details
the operations and processing of queue objects.
<span class="grey">Sankar & Jones Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Transport Considerations</span>
The CDMI operates over HTTP [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] and does not make sense outside
the HTTP realm. We do not expect the CDMI to operate over other
protocols nor to use a transport protocol, such as TCP [<a href="./rfc793" title=""Transmission Control Protocol"">RFC793</a>],
directly.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has registered the following media types:
o application/cdmi-object
o application/cdmi-container
o application/cdmi-domain
o application/cdmi-capability
o application/cdmi-queue
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Media Type: application/cdmi-object</span>
Type name: application
Subtype name: cdmi-object
Required parameters: none
Optional parameters: none
Encoding considerations: Assumes that the representation is always
UTF-8 as defined in [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] and 8bit as defined in [<a href="./rfc4288" title=""Media Type Specifications and Registration Procedures"">RFC4288</a>]
Security considerations: See <a href="./rfc6208#section-6">Section 6 of RFC 6208</a>
Interoperability considerations: none
Published specification: <a href="./rfc6208">RFC 6208</a>
Applications that use this media type: Implementations of the Cloud
Data Management Interface (CDMI) defined by the Storage Networking
Industry Association (SNIA)
<span class="grey">Sankar & Jones Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
Additional information:
Magic number(s): n/a
File extension(s): .cdmio
Macintosh file type code(s): TEXT
Person and email address to contact for further information:
Arnold Jones, arnold.jones@snia.org
Intended usage: COMMON
Restrictions on usage: none
Author: SNIA Cloud Storage Initiative, cloudtwg@snia.org
Change controller: SNIA Cloud Storage Initiative, cloudtwg@snia.org
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Media Type: application/cdmi-container</span>
Type name: application
Subtype name: cdmi-container
Required parameters: none
Optional parameters: none
Encoding considerations: Assumes that the representation is always
UTF-8 as defined in [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] and 8bit as defined in [<a href="./rfc4288" title=""Media Type Specifications and Registration Procedures"">RFC4288</a>]
Security considerations: See <a href="./rfc6208#section-6">Section 6 of RFC 6208</a>
Interoperability considerations: none
Published specification: <a href="./rfc6208">RFC 6208</a>
Applications that use this media type: Implementations of the Cloud
Data Management Interface (CDMI) defined by the Storage Networking
Industry Association (SNIA)
<span class="grey">Sankar & Jones Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
Additional information:
Magic number(s): n/a
File extension(s): .cdmic
Macintosh file type code(s): TEXT
Person and email address to contact for further information:
Arnold Jones, arnold.jones@snia.org
Intended usage: COMMON
Restrictions on usage: none
Author: SNIA Cloud Storage Initiative, cloudtwg@snia.org
Change controller: SNIA Cloud Storage Initiative, cloudtwg@snia.org
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Media Type: application/cdmi-domain</span>
Type name: application
Subtype name: cdmi-domain
Required parameters: none
Optional parameters: none
Encoding considerations: Assumes that the representation is always
UTF-8 as defined in [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] and 8bit as defined in [<a href="./rfc4288" title=""Media Type Specifications and Registration Procedures"">RFC4288</a>]
Security considerations: See <a href="./rfc6208#section-6">Section 6 of RFC 6208</a>
Interoperability considerations: none
Published specification: <a href="./rfc6208">RFC 6208</a>
Applications that use this media type: Implementations of the Cloud
Data Management Interface (CDMI) defined by the Storage Networking
Industry Association (SNIA)
<span class="grey">Sankar & Jones Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
Additional information:
Magic number(s): n/a
File extension(s): .cdmid
Macintosh file type code(s): TEXT
Person and email address to contact for further information:
Arnold Jones, arnold.jones@snia.org
Intended usage: COMMON
Restrictions on usage: none
Author: SNIA Cloud Storage Initiative, cloudtwg@snia.org
Change controller: SNIA Cloud Storage Initiative, cloudtwg@snia.org
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Media Type: application/cdmi-capability</span>
Type name: application
Subtype name: cdmi-capability
Required parameters: none
Optional parameters: none
Encoding considerations: Assumes that the representation is always
UTF-8 as defined in [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] and 8bit as defined in [<a href="./rfc4288" title=""Media Type Specifications and Registration Procedures"">RFC4288</a>]
Security considerations: See <a href="./rfc6208#section-6">Section 6 of RFC 6208</a>
Interoperability considerations: none
Published specification: <a href="./rfc6208">RFC 6208</a>
Applications that use this media type: Implementations of the Cloud
Data Management Interface (CDMI) defined by the Storage Networking
Industry Association (SNIA)
<span class="grey">Sankar & Jones Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
Additional information:
Magic number(s): n/a
File extension(s): .cdmia
Macintosh file type code(s): TEXT
Person and email address to contact for further information:
Arnold Jones, arnold.jones@snia.org
Intended usage: COMMON
Restrictions on usage: none
Author: SNIA Cloud Storage Initiative, cloudtwg@snia.org
Change controller: SNIA Cloud Storage Initiative, cloudtwg@snia.org
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Media Type: application/cdmi-queue</span>
Type name: application
Subtype name: cdmi-queue
Required parameters: none
Optional parameters: none
Encoding considerations: Assumes that the representation is always
UTF-8 as defined in [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] and 8bit as defined in [<a href="./rfc4288" title=""Media Type Specifications and Registration Procedures"">RFC4288</a>]
Security considerations: See <a href="./rfc6208#section-6">Section 6 of RFC 6208</a>
Interoperability considerations: none
Published specification: <a href="./rfc6208">RFC 6208</a>
Applications that use this media type: Implementations of the Cloud
Data Management Interface (CDMI) defined by the Storage Networking
Industry Association (SNIA)
<span class="grey">Sankar & Jones Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
Additional information:
Magic number(s): n/a
File extension(s): .cdmiq
Macintosh file type code(s): TEXT
Person and email address to contact for further information:
Arnold Jones, arnold.jones@snia.org
Intended usage: COMMON
Restrictions on usage: none
Author: SNIA Cloud Storage Initiative, cloudtwg@snia.org
Change controller: SNIA Cloud Storage Initiative, cloudtwg@snia.org
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
This section was developed with <a href="./rfc3552">RFC 3552</a> [<a href="./rfc3552" title=""Guidelines for Writing RFC Text on Security Considerations"">RFC3552</a>] as a guide. CDMI
is an application interface and the relevant security considerations
include confidentiality, integrity, access control, and audit.
Transport and endpoint security artifacts like Distributed Denial of
Service (DDoS) are orthogonal, and domains like non-repudiation are
left to the application that employs this interface.
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Confidentiality and Integrity</span>
The confidentiality and integrity of the CDMI exchanges are
determined by the application that uses the interface. CDMI does not
contain any specific mechanisms and relies on transport mechanisms
such as Transport Layer Security (TLS) (see [<a href="./rfc2818" title=""HTTP Over TLS"">RFC2818</a>]) for
confidentiality and integrity of the messages across the network.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Access Control</span>
The access control of the CDMI endpoint URLs are beyond this
specification. If required, applications should use appropriate URL
authentication and authorization techniques, such as URI routers for
different classes of users and restrict access based on URI origin.
For fine-grained control of the CDMI objects, the CDMI specification
[<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>] contains the Access Control Lists (ACLs) and Access Control
Entries (ACEs). These are described fully in <a href="#section-16.1">Section 16.1</a> of the
CDMI specification [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>].
<span class="grey">Sankar & Jones Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Audit</span>
The CDMI specification [<a href="#ref-CDMI-1" title=""Cloud Data Management Interface Version 1.0"">CDMI-1</a>] has defined a set of metadata fields,
as explained in <a href="#section-16.3">Section 16.3</a>, to facilitate the incorporation of
access and other audit markers. The CDMI metadata system is
extensible, and the implementations can add more metadata as required
by the security posture of the domain.
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. JSON Security Considerations</span>
JSON-related security considerations, described in <a href="./rfc4627">RFC 4627</a>
[<a href="./rfc4627" title=""The application/json Media Type for JavaScript Object Notation (JSON)"">RFC4627</a>], apply.
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Executable/Active Content</span>
The CDMI interface does not include any directives for active
content.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
The authors wish to acknowledge the guidance and wisdom of Mark
Carlson and Peter Saint-Andre, comments from Patrick Faltstrom, and
all the insightful discussions and ideas of the SNIA CDMI Cloud
Technical Work Group.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-CDMI-1">CDMI-1</a>] SNIA, "Cloud Data Management Interface Version 1.0", 2010,
<<a href="http://www.snia.org/tech_activities/standards/curr_standards/cdmi">http://www.snia.org/tech_activities/standards/</a>
<a href="http://www.snia.org/tech_activities/standards/curr_standards/cdmi">curr_standards/cdmi</a>>.
[<a id="ref-JSON-1">JSON-1</a>] JSON, "Introducing JSON", 2006, <<a href="http://www.json.org">http://www.json.org</a>>.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
[<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC</a>
<a href="./rfc3986">3986</a>, January 2005.
<span class="grey">Sankar & Jones Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6208">RFC 6208</a> CDMI Media Types April 2011</span>
[<a id="ref-RFC4288">RFC4288</a>] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4288">RFC 4288</a>, December 2005.
[<a id="ref-RFC4627">RFC4627</a>] Crockford, D., "The application/json Media Type for
JavaScript Object Notation (JSON)", <a href="./rfc4627">RFC 4627</a>, July 2006.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC793">RFC793</a>] Postel, J., "Transmission Control Protocol", STD 7, <a href="./rfc793">RFC</a>
<a href="./rfc793">793</a>, September 1981.
[<a id="ref-RFC1024">RFC1024</a>] Partridge, C. and G. Trewitt, "HEMS variable definitions",
<a href="./rfc1024">RFC 1024</a>, October 1987.
[<a id="ref-RFC1076">RFC1076</a>] Trewitt, G. and C. Partridge, "HEMS monitoring and control
language", <a href="./rfc1076">RFC 1076</a>, November 1988.
[<a id="ref-RFC2818">RFC2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
[<a id="ref-RFC3552">RFC3552</a>] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", <a href="https://www.rfc-editor.org/bcp/bcp72">BCP 72</a>, <a href="./rfc3552">RFC 3552</a>, July
2003.
Authors' Addresses
Krishna Sankar (editor)
Cisco
170 W. Tasman Drive
San Jose, CA 95134
USA
Phone: (408) 853 8475
EMail: ksankar@cisco.com
Arnold Jones
SNIA
4410 ArrowsWest Drive
Colorado Springs, CO 80907
USA
Phone: (407) 574 7273
EMail: arnold.jones@snia.org
Sankar & Jones Informational [Page 13]
</pre>
|
