Debian Codegraph @

rfc6968.html

raw
1 <pre>Internet Engineering Task Force (IETF) V. Roca
2 Request for Comments: 6968 INRIA
3 Category: Experimental B. Adamson
4 ISSN: 2070-1721 Naval Research Laboratory
5 July 2013
6
7
8 <span class="h1">FCAST: Object Delivery for the Asynchronous Layered Coding (ALC) and</span>
9 <span class="h1">NACK-Oriented Reliable Multicast (NORM) Protocols</span>
10
11 Abstract
12
13 This document introduces the FCAST reliable object (e.g., file)
14 delivery application. It is designed to operate either on top of the
15 underlying Asynchronous Layered Coding (ALC) / Layered Coding
16 Transport (LCT) reliable multicast transport protocol or the NACK-
17 Oriented Reliable Multicast (NORM) transport protocol.
18
19 Status of This Memo
20
21 This document is not an Internet Standards Track specification; it is
22 published for examination, experimental implementation, and
23 evaluation.
24
25 This document defines an Experimental Protocol for the Internet
26 community. This document is a product of the Internet Engineering
27 Task Force (IETF). It represents the consensus of the IETF
28 community. It has received public review and has been approved for
29 publication by the Internet Engineering Steering Group (IESG). Not
30 all documents approved by the IESG are a candidate for any level of
31 Internet Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
32
33 Information about the current status of this document, any errata,
34 and how to provide feedback on it may be obtained at
35 <a href="http://www.rfc-editor.org/info/rfc6968">http://www.rfc-editor.org/info/rfc6968</a>.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Roca &amp; Adamson Experimental [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2013 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
75 <a href="#section-1.1">1.1</a>. Requirements Notation ......................................<a href="#page-4">4</a>
76 <a href="#section-1.2">1.2</a>. Definitions, Notations, and Abbreviations ..................<a href="#page-5">5</a>
77 <a href="#section-2">2</a>. FCAST Data Formats ..............................................<a href="#page-6">6</a>
78 <a href="#section-2.1">2.1</a>. Compound Object Format .....................................<a href="#page-6">6</a>
79 <a href="#section-2.2">2.2</a>. Carousel Instance Descriptor Format ........................<a href="#page-9">9</a>
80 <a href="#section-3">3</a>. FCAST Principles ...............................................<a href="#page-12">12</a>
81 <a href="#section-3.1">3.1</a>. FCAST Content Delivery Service ............................<a href="#page-12">12</a>
82 <a href="#section-3.2">3.2</a>. Compound Object and Metadata Transmission .................<a href="#page-13">13</a>
83 <a href="#section-3.3">3.3</a>. Metadata Content ..........................................<a href="#page-13">13</a>
84 <a href="#section-3.4">3.4</a>. Carousel Transmission .....................................<a href="#page-15">15</a>
85 <a href="#section-3.5">3.5</a>. Carousel Instance Descriptor Special Object ...............<a href="#page-15">15</a>
86 <a href="#section-3.6">3.6</a>. Compound Object Identification ............................<a href="#page-17">17</a>
87 <a href="#section-3.7">3.7</a>. FCAST Sender Behavior .....................................<a href="#page-18">18</a>
88 <a href="#section-3.8">3.8</a>. FCAST Receiver Behavior ...................................<a href="#page-19">19</a>
89 <a href="#section-4">4</a>. Requirements for Compliant Implementations .....................<a href="#page-20">20</a>
90 <a href="#section-4.1">4.1</a>. Requirements Related to the Object Metadata ...............<a href="#page-20">20</a>
91 <a href="#section-4.2">4.2</a>. Requirements Related to the Carousel Instance Descriptor ..21
92 <a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-22">22</a>
93 <a href="#section-5.1">5.1</a>. Problem Statement .........................................<a href="#page-22">22</a>
94 <a href="#section-5.2">5.2</a>. Attacks against the Data Flow .............................<a href="#page-22">22</a>
95 5.2.1. Attacks Meant to Gain Access to
96 Confidential Objects ...............................<a href="#page-23">23</a>
97 <a href="#section-5.2.2">5.2.2</a>. Attacks Meant to Corrupt Objects ...................<a href="#page-23">23</a>
98 5.3. Attacks against the Session Control Parameters and
99 Associated Building Blocks ................................<a href="#page-24">24</a>
100 <a href="#section-5.3.1">5.3.1</a>. Attacks against the Session Description ............<a href="#page-25">25</a>
101 <a href="#section-5.3.2">5.3.2</a>. Attacks against the FCAST CID ......................<a href="#page-25">25</a>
102 <a href="#section-5.3.3">5.3.3</a>. Attacks against the Object Metadata ................<a href="#page-25">25</a>
103 <a href="#section-5.3.4">5.3.4</a>. Attacks against the ALC/LCT and NORM Parameters ....<a href="#page-26">26</a>
104 <a href="#section-5.3.5">5.3.5</a>. Attacks against the Associated Building Blocks .....<a href="#page-26">26</a>
105
106
107
108 <span class="grey">Roca &amp; Adamson Experimental [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
111
112
113 <a href="#section-5.4">5.4</a>. Other Security Considerations .............................<a href="#page-27">27</a>
114 <a href="#section-5.5">5.5</a>. Minimum Security Recommendations ..........................<a href="#page-27">27</a>
115 <a href="#section-6">6</a>. Operational Considerations .....................................<a href="#page-28">28</a>
116 <a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-29">29</a>
117 <a href="#section-7.1">7.1</a>. Creation of the FCAST Object Metadata Format Registry .....<a href="#page-29">29</a>
118 <a href="#section-7.2">7.2</a>. Creation of the FCAST Object Metadata Encoding Registry ...<a href="#page-30">30</a>
119 <a href="#section-7.3">7.3</a>. Creation of the FCAST Object Metadata Types Registry ......<a href="#page-30">30</a>
120 <a href="#section-8">8</a>. Acknowledgments ................................................<a href="#page-32">32</a>
121 <a href="#section-9">9</a>. References .....................................................<a href="#page-32">32</a>
122 <a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-32">32</a>
123 <a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-33">33</a>
124 <a href="#appendix-A">Appendix A</a>. FCAST Examples ........................................<a href="#page-35">35</a>
125 <a href="#appendix-A.1">A.1</a>. Simple Compound Object Example .............................<a href="#page-35">35</a>
126 <a href="#appendix-A.2">A.2</a>. Carousel Instance Descriptor Example .......................<a href="#page-36">36</a>
127 <a href="#appendix-B">Appendix B</a>. Additional Metadata Transmission Mechanisms ...........<a href="#page-37">37</a>
128 <a href="#appendix-B.1">B.1</a>. Supporting Additional Mechanisms ...........................<a href="#page-37">37</a>
129 <a href="#appendix-B.2">B.2</a>. Using NORM_INFO Messages with FCAST/NORM ...................<a href="#page-38">38</a>
130 <a href="#appendix-B.2.1">B.2.1</a>. Example ................................................<a href="#page-38">38</a>
131
132 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
133
134 This document introduces the FCAST reliable and scalable object
135 (e.g., file) delivery application. Two variants of FCAST exist:
136
137 o FCAST/ALC, which relies on the Asynchronous Layered Coding (ALC)
138 [<a href="./rfc5775" title="&quot;Asynchronous Layered Coding (ALC) Protocol Instantiation&quot;">RFC5775</a>] and Layered Coding Transport (LCT) [<a href="./rfc5651" title="&quot;Layered Coding Transport (LCT) Building Block&quot;">RFC5651</a>] reliable
139 multicast transport protocol, and
140
141 o FCAST/NORM, which relies on the NACK-Oriented Reliable Multicast
142 (NORM) [<a href="./rfc5740" title="&quot;NACK-Oriented Reliable Multicast (NORM) Transport Protocol&quot;">RFC5740</a>] transport protocol.
143
144 Hereafter, the term "FCAST" denotes either FCAST/ALC or FCAST/NORM.
145 FCAST is not a new protocol specification per se. Instead, it is a
146 set of data format specifications and instructions on how to use ALC
147 and NORM to implement a file-casting service.
148
149 FCAST is expected to work in many different environments and is
150 designed to be flexible. The service provided by FCAST can differ
151 according to the exact conditions under which FCAST is used. For
152 instance, the delivery service provided by FCAST might be fully
153 reliable, or only partially reliable, depending upon the exact way
154 FCAST is used. Indeed, if FCAST/ALC is used for a finite duration
155 over purely unidirectional networks (where no feedback is possible),
156 a fully reliable service may not be possible in practice. This is
157 different with NORM, which can collect reception and loss feedback
158 from receivers. This is discussed in <a href="#section-6">Section 6</a>.
159
160
161
162
163
164 <span class="grey">Roca &amp; Adamson Experimental [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
167
168
169 The delivery service provided by FCAST might also differ in terms of
170 scalability with respect to the number of receivers. The FCAST/ALC
171 service is naturally massively scalable, since neither FCAST nor ALC
172 limits the number of receivers (there is no feedback message at all).
173 Conversely, the scalability of FCAST/NORM is typically limited by
174 NORM itself, as NORM relies on feedback messages from the receivers.
175 However, NORM is designed in such a way to offer a reasonably
176 scalable service (e.g., through the use of proactive Forward Error
177 Correction (FEC) codes [<a href="./rfc6363" title="&quot;Forward Error Correction (FEC) Framework&quot;">RFC6363</a>]), and so does the service provided
178 by FCAST/NORM. This aspect is also discussed in <a href="#section-6">Section 6</a>.
179
180 A design goal behind FCAST is to define a streamlined solution, in
181 order to enable lightweight implementations of the protocol stack and
182 to limit the operational processing and storage requirements. A
183 consequence of this choice is that FCAST cannot be considered a
184 versatile application capable of addressing all the possible use-
185 cases. On the contrary, FCAST has some intrinsic limitations. From
186 this point of view, it differs from the File Delivery over
187 Unidirectional Transport (FLUTE) [<a href="./rfc6726" title="&quot;FLUTE - File Delivery over Unidirectional Transport&quot;">RFC6726</a>], which favors flexibility
188 at the expense of some additional complexity.
189
190 A good example of the design choices meant to favor simplicity is the
191 way FCAST manages the object metadata: by default, the metadata and
192 the object content are sent together, in a Compound Object. This
193 solution has many advantages in terms of simplicity, as will be
194 described later on. However, this solution has an intrinsic
195 limitation, since it does not enable a receiver to decide in advance,
196 before beginning the reception of the Compound Object, whether the
197 object is of interest or not, based on the information that may be
198 provided in the metadata. Therefore, this document discusses
199 additional techniques that may be used to mitigate this limitation.
200 When use-cases require that each receiver download the whole set of
201 objects sent in the session (e.g., with mirroring tools), this
202 limitation is not considered a problem.
203
204 Finally, <a href="#section-4">Section 4</a> provides guidance for compliant implementation of
205 the specification and identifies those features that are optional.
206
207 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Notation</span>
208
209 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
210 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
211 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
212
213
214
215
216
217
218
219
220 <span class="grey">Roca &amp; Adamson Experimental [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
223
224
225 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Definitions, Notations, and Abbreviations</span>
226
227 This document uses the following definitions:
228
229 FCAST/ALC: denotes the FCAST application running on top of the
230 ALC/LCT transport protocol.
231
232 FCAST/NORM: denotes the FCAST application running on top of the NORM
233 transport protocol.
234
235 FCAST: denotes either FCAST/ALC or FCAST/NORM.
236
237 Compound Object: denotes an ALC or NORM transport object composed of
238 the FCAST Header and the Object Data (some Compound Objects may
239 not include any Object Data).
240
241 FCAST Header: denotes the header prepended to the Object Data, which
242 together form the Compound Object. This FCAST Header usually
243 contains the object metadata, among other things.
244
245 Object Data: denotes the original object (e.g., a file) that forms
246 the payload of the Compound Object.
247
248 Carousel: denotes the building block that enables an FCAST sender to
249 transmit Compound Objects in a cyclic manner.
250
251 Carousel Instance: denotes a fixed set of registered Compound
252 Objects that are sent by the carousel during a certain number of
253 cycles. Whenever Compound Objects need to be added or removed, a
254 new Carousel Instance is defined.
255
256 Carousel Instance Descriptor (CID): denotes a special object that
257 lists the Compound Objects that comprise a given Carousel
258 Instance.
259
260 Carousel Instance IDentifier (CIID): numeric value that identifies a
261 Carousel Instance.
262
263 Carousel Cycle: denotes a transmission round within which all the
264 Compound Objects registered in the Carousel Instance are
265 transmitted a certain number of times. By default, Compound
266 Objects are transmitted once per cycle, but higher values, which
267 might differ on a per-object basis, are possible.
268
269
270
271
272
273
274
275
276 <span class="grey">Roca &amp; Adamson Experimental [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
279
280
281 Transport Object Identifier (TOI): denotes the numeric identifier
282 associated with a specific object by the underlying transport
283 protocol. In the case of ALC, this corresponds to the TOI
284 described in [<a href="./rfc5651" title="&quot;Layered Coding Transport (LCT) Building Block&quot;">RFC5651</a>]. In the case of NORM, this corresponds to
285 the NormTransportId described in [<a href="./rfc5740" title="&quot;NACK-Oriented Reliable Multicast (NORM) Transport Protocol&quot;">RFC5740</a>].
286
287 FEC Object Transmission Information (FEC OTI): FEC information
288 associated with an object and that is essential for the FEC
289 decoder to decode a specific object.
290
291 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. FCAST Data Formats</span>
292
293 This section details the various data formats used by FCAST.
294
295 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Compound Object Format</span>
296
297 In an FCAST session, Compound Objects are constructed by prepending
298 the FCAST Header (which usually contains the metadata of the object)
299 to the Object Data (see <a href="#section-3.2">Section 3.2</a>). Figure 1 illustrates the
300 associated format. All multi-byte fields MUST be in network (Big
301 Endian) byte order.
302
303 0 1 2 3
304 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ^
306 | Ver |Resvd|G|C| MDFmt | MDEnc | Checksum | |
307 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
308 | FCAST Header Length | h
309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| d
310 | Object Metadata (variable length) | r
311 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
312 | | Padding (optional) | |
313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ v
314 | |
315 . Object Data (optional, variable length) .
316 . .
317 . .
318
319 Figure 1: Compound Object Format
320
321
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Roca &amp; Adamson Experimental [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
335
336
337 The FCAST Header fields are:
338
339 +------------+------------------------------------------------------+
340 | Field | Description |
341 +------------+------------------------------------------------------+
342 | Version | 3-bit field that MUST be set to 0 in this |
343 | | specification and that indicates the FCAST protocol |
344 | | version number. |
345 | | |
346 | Reserved | 3-bit field that MUST be set to 0 in this |
347 | | specification and is reserved for future use. |
348 | | Receivers MUST ignore this field. |
349 | | |
350 | G | 1-bit field that, when set to 1, indicates that the |
351 | | checksum encompasses the whole Compound Object |
352 | | (Global checksum). When set to 0, this field |
353 | | indicates that the checksum encompasses only the |
354 | | FCAST Header. |
355 | | |
356 | C | 1-bit field that, when set to 1, indicates that the |
357 | | object is a CID. When set to 0, this field |
358 | | indicates that the transported object is a standard |
359 | | object. |
360 | | |
361 | Metadata | 4-bit field that defines the format of the Object |
362 | Format | Metadata field (see <a href="#section-7">Section 7</a>). An HTTP/1.1 |
363 | (MDFmt) | metainformation format [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>] MUST be supported |
364 | | and is associated to value 0. Other formats (e.g., |
365 | | XML) may be defined in the future. |
366 | | |
367 | Metadata | 4-bit field that defines the optional encoding of |
368 | Encoding | the Object Metadata field (see <a href="#section-7">Section 7</a>). Two |
369 | (MDEnc) | values are currently defined. A value of 0 |
370 | | indicates that the field contains UTF-8 encoded |
371 | | [<a href="./rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>] text. A value of 1 indicates that the |
372 | | field contains GZIP [<a href="./rfc1952" title="&quot;GZIP file format specification version 4.3&quot;">RFC1952</a>] compressed UTF-8 |
373 | | encoded text. |
374 | | |
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Roca &amp; Adamson Experimental [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
391
392
393 | Checksum | 16-bit field that contains the checksum computed |
394 | | over either the whole Compound Object (when G is set |
395 | | to 1) or over the FCAST Header (when G is set to 0), |
396 | | using the Internet checksum algorithm specified in |
397 | | [<a href="./rfc1071" title="&quot;Computing the Internet checksum&quot;">RFC1071</a>]. More precisely, the Checksum field is |
398 | | the 16-bit one's complement of the one's complement |
399 | | sum of all 16-bit words to be considered. If a |
400 | | segment contains an odd number of octets to be |
401 | | checksummed, the last octet is padded on the right |
402 | | with zeros to form a 16-bit word for checksum |
403 | | purposes (this pad is not transmitted). While |
404 | | computing the checksum, the Checksum field itself |
405 | | MUST be set to zero. |
406 | | |
407 | FCAST | 32-bit field indicating total length (in bytes) of |
408 | Header | all fields of the FCAST Header, except the optional |
409 | Length | padding. An FCAST Header Length field set to value |
410 | | 8 means that there is no metadata included. When |
411 | | this size is not a multiple of 32-bit words and when |
412 | | the FCAST Header is followed by non-null Object |
413 | | Data, padding MUST be added. It should be noted |
414 | | that the Object Metadata field maximum size is equal |
415 | | to (2^32 - 8) bytes. |
416 | | |
417 | Object | Variable-length field that contains the metadata |
418 | Metadata | associated to the object. The format and encoding |
419 | | of this field are defined by the MDFmt and MDEnc |
420 | | fields, respectively. With the default format and |
421 | | encoding, the Object Metadata field, if not empty, |
422 | | MUST contain UTF-8 encoded text that follows the |
423 | | "TYPE" ":" "VALUE" "&lt;CR-LF&gt;" format used in HTTP/1.1 |
424 | | for metainformation [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>]. The various |
425 | | metadata items can appear in any order. The |
426 | | receiver MUST NOT assume that this string is NULL- |
427 | | terminated. When no metadata is communicated, this |
428 | | field MUST be empty and the FCAST Header Length MUST |
429 | | be equal to 8. |
430 | | |
431 | Padding | Optional, variable-length field of zero-value bytes |
432 | | to align the start of the Object Data to a 32-bit |
433 | | boundary. Padding is only used when the FCAST |
434 | | Header Length value, in bytes, is not a multiple of |
435 | | 4 and when the FCAST Header is followed by non-null |
436 | | Object Data. |
437 +------------+------------------------------------------------------+
438
439
440
441
442
443
444 <span class="grey">Roca &amp; Adamson Experimental [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
447
448
449 The FCAST Header is then followed by the Object Data, i.e., either an
450 original object (possibly encoded by FCAST) or a CID. Note that the
451 length of the Object Data content is the ALC or NORM transported
452 object length (e.g., as specified by the FEC OTI) minus the FCAST
453 Header Length and optional padding, if any.
454
455 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Carousel Instance Descriptor Format</span>
456
457 In an FCAST session, a CID MAY be sent in order to carry the list of
458 Compound Objects that are part of a given Carousel Instance (see
459 <a href="#section-3.5">Section 3.5</a>). The format of the CID that is sent as a special
460 Compound Object is given in Figure 2. Being a special case of
461 Compound Object, this format is in line with the format described in
462 <a href="#section-2.1">Section 2.1</a>.
463
464 0 1 2 3
465 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ^
467 | Ver |Resvd|G|C| MDFmt | MDEnc | Checksum | |
468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
469 | FCAST Header Length | h
470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| d
471 | Object Metadata (variable length) | r
472 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
473 | | Padding (optional) | |
474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ v
475 . . ^
476 . Object List (variable length) . |
477 . . o
478 . +-+-+-+-+-+-+-+-+ b
479 . | j
480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ v
481
482 Figure 2: Carousel Instance Descriptor Format
483
484 Because the CID is transmitted as a special Compound Object, the
485 following CID-specific metadata entries are defined and MUST be
486 supported:
487
488 o Fcast-CID-Complete: this is an optional entry that, when set to
489 "Fcast-CID-Complete: 1", indicates no new object (if we ignore CID
490 Compound Objects) in addition to the ones whose TOIs are listed in
491 this CID or the ones that have been listed in the previous CID(s),
492 will be sent in the future. Conversely, if it is set to
493 "Fcast-CID-Complete: 0", or if this entry is absent, it indicates
494 that the session is not complete. An FCAST sender MUST NOT use
495 any other value for this entry.
496
497
498
499
500 <span class="grey">Roca &amp; Adamson Experimental [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
503
504
505 o Fcast-CID-ID: this entry contains the Carousel Instance
506 IDentifier, or CIID. It starts from 0 upon FCAST session creation
507 and is incremented by 1 for each new Carousel Instance. This
508 entry is optional if the FCAST session consists of a single,
509 complete Carousel Instance (no need for the FCAST sender to
510 specify it and for the FCAST receiver to process it). In all
511 other cases, this entry MUST be defined. In particular, the CIID
512 is used by the TOI equivalence mechanism, thanks to which any
513 object is uniquely identified, even if the TOI is updated (e.g.,
514 after re-enqueuing the object with NORM). The Fcast-CID-ID value
515 can also be useful for detecting possible gaps in the Carousel
516 Instances, for instance, gaps caused by long disconnection
517 periods. Finally, it can also be useful for avoiding problems
518 when TOI wrapping to 0 takes place to differentiate the various
519 incarnations of the TOIs if need be.
520
521 The following standard metadata entry types are also used
522 (<a href="#section-3.3">Section 3.3</a>):
523
524 o Content-Length: specifies the size in bytes of the Object List,
525 before any content encoding (if any).
526
527 o Content-Encoding: specifies the optional encoding of the Object
528 List, performed by FCAST.
529
530 An empty Object List is valid and indicates that the current Carousel
531 Instance does not include any objects (<a href="#section-3.5">Section 3.5</a>). This can be
532 specified by using the following metadata entry:
533
534 Content-Length: 0
535
536 or simply by leaving the Object List empty. In both cases, padding
537 MUST NOT be used, and consequently the ALC or NORM transported object
538 length (e.g., as specified by the FEC OTI) minus the FCAST Header
539 Length equals zero.
540
541 The Object List, when non-empty and with MDEnc=0, is UTF-8-encoded
542 text that is not necessarily NULL-terminated. It can contain two
543 things:
544
545 o a list of TOI values, and
546
547 o a list of TOI equivalences.
548
549 A list of TOIs included in the current Carousel Instance is specified
550 as an ASCII string containing comma-delimited individual TOI values
551 and/or TOI intervals. Individual TOIs consist of a single integer
552 value, while TOI intervals are a hyphen-delimited pair of TOI values
553
554
555
556 <span class="grey">Roca &amp; Adamson Experimental [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
559
560
561 to indicate an inclusive range of TOI values (e.g., "1,2,4-6" would
562 indicate the list of TOI values of 1, 2, 4, 5, and 6). For a TOI
563 interval indicated by "TOI_a-TOI_b", the "TOI_a" value MUST be
564 strictly inferior to the "TOI_b" value. If a TOI wrapping to 0
565 occurs in an interval, then two TOI intervals MUST be specified:
566 TOI_a-MAX_TOI and 0-TOI_b.
567
568 This string can also contain the TOI equivalences, if any. The
569 format is a comma-separated list of equivalence TOI value pairs with
570 a delimiting equals sign '=' to indicate the equivalence assignment
571 (e.g., " newTOI "=" 1stTOI "/" 1stCIID "). Each equivalence
572 indicates that the new TOI, for the current Carousel Instance, is
573 equivalent to (i.e., refers to the same object as) the provided
574 identifier, 1stTOI, for the Carousel Instance of ID 1stCIID. In the
575 case of the NORM protocol, where NormTransportId values need to
576 monotonically increase for NACK-based protocol operation, this allows
577 an object from a prior Carousel Instance to be relisted in a
578 subsequent Carousel Instance with the receiver set informed of the
579 equivalence so that unnecessary retransmission requests can be
580 avoided.
581
582 The ABNF [<a href="./rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>] is as follows:
583
584 cid-list = *(list-elem *( "," list-elem))
585 list-elem = toi-elem / toieq-elem
586 toi-elem = toi-value / toi-interval
587 toi-value = 1*DIGIT
588 toi-interval = toi-value "-" toi-value
589 ; additionally, the first toi-value MUST be
590 ; strictly inferior to the second toi-value
591 toieq-elem = "(" toi-value "=" toi-value "/" ciid-value ")"
592 ciid-value = 1*DIGIT
593 DIGIT = %x30-39
594 ; a digit between 0 and 9, inclusive
595
596 For readability purposes and to simplify processing, the TOI
597 values in the list MUST be given in increasing order, handling wrap
598 of the TOI space appropriately. TOI equivalence elements MUST be
599 grouped together at the end of the list in increasing newTOI order.
600 Specifying a TOI equivalence for a given newTOI relieves the sender
601 from specifying newTOI explicitly in the TOI list. A receiver MUST
602 be able to handle situations where the same TOI appears both in the
603 TOI value and TOI equivalence lists. Finally, a given TOI value or
604 TOI equivalence item MUST NOT be included multiple times in either
605 list.
606
607
608
609
610
611
612 <span class="grey">Roca &amp; Adamson Experimental [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
615
616
617 For instance, the following Object List specifies that the current
618 Carousel Instance is composed of 8 objects, and that TOIs 100 to 104
619 are equivalent to TOIs 10 to 14 of Carousel Instance ID 2 and refer
620 to the same objects:
621
622 97,98,99,(100=10/2),(101=11/2),(102=12/2),(103=13/2),(104=14/2)
623
624 or equivalently:
625
626 97-104,(100=10/2),(101=11/2),(102=12/2),(103=13/2),(104=14/2)
627
628 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. FCAST Principles</span>
629
630 This section details the principles of FCAST.
631
632 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. FCAST Content Delivery Service</span>
633
634 The basic goal of FCAST is to transmit objects to a group of
635 receivers in a reliable way, where the receiver set may be restricted
636 to a single receiver or may include possibly a very large number of
637 receivers. FCAST supports two forms of operation:
638
639 1. FCAST/ALC, where the FCAST application works on top of the
640 ALC/LCT reliable multicast transport protocol, without any
641 feedback from the receivers, and
642
643 2. FCAST/NORM, where the FCAST application works on top of the NORM
644 transport protocol, which requires positive/negative
645 acknowledgments from the receivers.
646
647 This specification is designed such that both forms of operation
648 share as much commonality as possible. <a href="#section-6">Section 6</a> discusses some
649 operational aspects and the content delivery service that is provided
650 by FCAST for a given use-case.
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Roca &amp; Adamson Experimental [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
671
672
673 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Compound Object and Metadata Transmission</span>
674
675 FCAST carries metadata elements by prepending them to the object they
676 refer to. As a result, a Compound Object is created that is composed
677 of an FCAST Header followed by the Object Data (Figure 3). This
678 header is itself composed of the object metadata (if any) as well as
679 several fields (e.g., to indicate format, encoding, or boundaries
680 (<a href="#section-2.1">Section 2.1</a>)).
681
682 &lt;------------------------ Compound Object -----------------------&gt;
683 +-------------------------+--------------------------------------+
684 | FCAST Header | Object Data |
685 | (can include metadata) | (can be encoded by FCAST) |
686 +-------------------------+--------------------------------------+
687
688 Figure 3: Compound Object Composition
689
690 Attaching the metadata to the object is an efficient solution, since
691 it guarantees that metadata are received along with the associated
692 object, and it allows the transport of the metadata to benefit from
693 any transport-layer erasure protection of the Compound Object (e.g.,
694 using FEC encoding and/or NACK-based repair). However, a limit of
695 this scheme is that a client does not know the metadata of an object
696 before beginning its reception, and in the case of erasures affecting
697 the metadata, not until the object decoding is completed. The
698 details of course depend upon the transport protocol and the FEC code
699 used.
700
701 <a href="#appendix-B">Appendix B</a> describes extensions that provide additional means to
702 carry metadata, e.g., to communicate metadata ahead of time.
703
704 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Metadata Content</span>
705
706 The following metadata types are defined in [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>]:
707
708 o Content-Location: the URI of the object, which gives the name and
709 location of the object.
710
711 o Content-Type: a string that contains the MIME type of the object.
712
713 o Content-Length: an unsigned 64-bit integer that contains the size
714 in bytes of the initial object, before any content encoding (if
715 any) and without considering the FCAST Header. Note that the use
716 of certain FEC schemes MAY further limit the maximum value of the
717 object.
718
719
720
721
722
723
724 <span class="grey">Roca &amp; Adamson Experimental [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
727
728
729 o Content-Encoding: a string that contains the optional encoding of
730 the object performed by FCAST. For instance:
731
732 Content-Encoding: gzip
733
734 indicates that the object has been encoded with GZIP [<a href="./rfc1952" title="&quot;GZIP file format specification version 4.3&quot;">RFC1952</a>].
735 If there is no Content-Encoding entry, the receiver MUST assume
736 that FCAST did not modify the original encoding of the object
737 (default).
738
739 The following additional metadata types are defined to check object
740 integrity:
741
742 o Fcast-Obj-Digest-SHA256: a string that contains the "base64"
743 [<a href="./rfc4648" title="&quot;The Base16, Base32, and Base64 Data Encodings&quot;">RFC4648</a>] encoding of the SHA-256 message digest of the object
744 [<a href="./rfc3174" title="&quot;US Secure Hash Algorithm 1 (SHA1)&quot;">RFC3174</a>] [<a href="./rfc6234" title="&quot;US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)&quot;">RFC6234</a>], before any content encoding is applied (if
745 any) and without considering the FCAST Header. This digest is
746 meant to protect from transmission and processing errors, not from
747 deliberate attacks by an intelligent attacker (see <a href="#section-5">Section 5</a>).
748 This digest only protects the object, not the header, and
749 therefore not the metadata. A separate checksum is provided for
750 that purpose (<a href="#section-2.1">Section 2.1</a>).
751
752 o Fcast-Obj-Digest-SHA1: similar to Fcast-Obj-Digest-SHA256, except
753 that SHA-256 is replaced by SHA-1. An FCAST sender MAY include
754 both an Fcast-Obj-Digest-SHA1 and an Fcast-Obj-Digest-SHA256
755 message digest in the metadata, in order to let a receiver select
756 the most appropriate algorithm (e.g., depending on local
757 processing power).
758
759 The following additional metadata types are used for dealing with
760 very large objects (e.g., objects that largely exceed the working
761 memory of a receiver). When this happens, the metadata associated to
762 each sub-object MUST include the following entries:
763
764 o Fcast-Obj-Slice-Nb: an unsigned 32-bit integer that contains the
765 total number of slices. A value greater than 1 indicates that
766 this object is the result of a split of the original object.
767
768 o Fcast-Obj-Slice-Idx: an unsigned 32-bit integer that contains the
769 slice index (in the {0 .. SliceNb - 1} interval).
770
771 o Fcast-Obj-Slice-Offset: an unsigned 64-bit integer that contains
772 the offset at which this slice starts within the original object.
773
774 Future IANA assignments to extend the set of metadata types supported
775 by FCAST are to be made through Expert Review [<a href="./rfc5226" title="">RFC5226</a>].
776
777
778
779
780 <span class="grey">Roca &amp; Adamson Experimental [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
783
784
785 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Carousel Transmission</span>
786
787 A set of FCAST Compound Objects scheduled for transmission is
788 considered a logical "Carousel". A given "Carousel Instance" is
789 comprised of a fixed set of Compound Objects. Whenever the FCAST
790 application needs to add new Compound Objects to or remove old
791 Compound Objects from the transmission set, a new Carousel Instance
792 is defined, since the set of Compound Objects changes. Because of
793 the native object multiplexing capability of both ALC and NORM, a
794 sender and receiver(s) are both capable of multiplexing and
795 demultiplexing FCAST Compound Objects.
796
797 For a given Carousel Instance, one or more transmission cycles are
798 possible. During each cycle, all of the Compound Objects comprising
799 the carousel are sent. By default, each object is transmitted once
800 per cycle. However, in order to allow different levels of priority,
801 some objects MAY be transmitted more often than others during a cycle
802 and/or benefit from higher FEC protection than others. For example,
803 this can be the case for the CID objects (<a href="#section-3.5">Section 3.5</a>), where extra
804 protection can benefit overall carousel integrity. For some FCAST
805 usage (e.g., a unidirectional "push" mode), a Carousel Instance may
806 be sent in a single transmission cycle. In other cases, it may be
807 conveyed in a large number of transmission cycles (e.g., in
808 "on-demand" mode, where objects are made available for download
809 during a long period of time).
810
811 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Carousel Instance Descriptor Special Object</span>
812
813 The FCAST sender can transmit an OPTIONAL CID. The CID carries the
814 list of the Compound Objects that are part of a given Carousel
815 Instance by specifying their respective Transport Object Identifiers
816 (TOIs). However, the CID does not describe the objects themselves
817 (i.e., there is no metadata). Additionally, the CID MAY include an
818 "Fcast-CID-Complete: 1" metadata entry to indicate that no further
819 modification to the enclosed list will be done in the future.
820 Finally, the CID MAY include a Carousel Instance ID (CIID) that
821 identifies the Carousel Instance it pertains to. These aspects are
822 discussed in <a href="#section-2.2">Section 2.2</a>.
823
824 There is no reserved TOI value for the CID Compound Object itself,
825 since this special object is regarded by ALC/LCT or NORM as a
826 standard object. On the contrary, the nature of this object (CID) is
827 indicated by means of a specific FCAST Header field (the "C" flag
828 from Figure 1) so that it can be recognized and processed by the
829 FCAST application as needed. A direct consequence is that since a
830 receiver does not know in advance which TOI will be used for the
831 following CID (in the case of a dynamic session), it MUST NOT filter
832
833
834
835
836 <span class="grey">Roca &amp; Adamson Experimental [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
839
840
841 out packets that are not in the current CID's TOI list. Said
842 differently, the goal of the CID is not to set up ALC or NORM packet
843 filters (this mechanism would not be secure in any case).
844
845 The use of a CID remains OPTIONAL. If it is not used, then the
846 clients progressively learn what files are part of the Carousel
847 Instance by receiving ALC or NORM packets with new TOIs. However,
848 using a CID has several benefits:
849
850 o When an "Fcast-CID-Complete" metadata entry set to
851 "Fcast-CID-Complete: 1" is included, the receivers know when they
852 can leave the session, i.e., when they have received all the
853 objects that are part of the last Carousel Instance of this
854 delivery session.
855
856 o In the case of a session with a dynamic set of objects, the sender
857 can reliably inform the receivers that some objects have been
858 removed from the carousel with the CID. This solution is more
859 robust than the Close Object "B" flag of ALC/LCT, since a client
860 with intermittent connectivity might lose all the packets
861 containing this "B" flag. And while NORM provides a robust object
862 cancellation mechanism in the form of its NORM_CMD(SQUELCH)
863 message in response to receiver NACK repair requests, the use of
864 the CID provides an additional means for receivers to learn of
865 objects for which it is futile to request repair.
866
867 o The TOI equivalence (<a href="#section-3.6">Section 3.6</a>) is signaled within the CID.
868
869 During idle periods, when the Carousel Instance does not contain any
870 object, a CID with an empty TOI list MAY be transmitted. In that
871 case, a new Carousel Instance ID MUST be used to differentiate this
872 (empty) Carousel Instance from the other ones. This mechanism can be
873 useful to inform the receivers that:
874
875 o all the previously sent objects have been removed from the
876 carousel. This therefore improves the robustness of FCAST even
877 during "idle" periods.
878
879 o the session is still active even if there is currently no content
880 being sent. Said differently, it can be used as a heartbeat
881 mechanism. If no "Fcast-CID-Complete" metadata entry is included
882 (or if set to "Fcast-CID-Complete: 0"), it informs the receivers
883 that the Carousel Instance may be modified and that new objects
884 could be sent in the future.
885
886
887
888
889
890
891
892 <span class="grey">Roca &amp; Adamson Experimental [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
895
896
897 <span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Compound Object Identification</span>
898
899 The FCAST Compound Objects are directly associated with the object-
900 based transport service that the ALC and NORM protocols provide. In
901 each protocol, the packets containing transport object content are
902 labeled with a numeric transport object identifier: the TOI with ALC,
903 and the NormTransportId with NORM. For the purposes of this
904 document, this identifier in either case (ALC or NORM) is referred to
905 as the TOI.
906
907 There are several differences between ALC and NORM:
908
909 o ALC's use of the TOI is rather flexible, since several TOI field
910 sizes are possible (from 16 to 112 bits); since this size can be
911 changed at any time, on a per-packet basis; and since the
912 management of the TOI is totally free as long as each object is
913 associated to a unique TOI (if no wraparound occurred).
914
915 o NORM's use of the TOI serves a more "directive" purpose, since the
916 TOI field is 16 bits long and since TOIs MUST be managed
917 sequentially.
918
919 In both NORM and ALC, it is possible that the transport
920 identification space eventually wraps for long-lived sessions
921 (especially with NORM, where this phenomenon is expected to happen
922 more frequently). This can possibly introduce some ambiguity in
923 FCAST object identification if a sender retains some older objects in
924 newer Carousel Instances with updated object sets. To avoid
925 ambiguity, the active TOIs (i.e., the TOIs corresponding to objects
926 being transmitted) can only occupy half of the TOI sequence space.
927 If an old object whose TOI has fallen outside the current window
928 needs to be transmitted again, a new TOI must be used for it. In the
929 case of NORM, this constraint limits to 32768 the maximum number of
930 objects that can be part of any Carousel Instance.
931
932 In order to allow receivers to properly combine the transport packets
933 with a newly assigned TOI to those associated to the previously
934 assigned TOI, a mechanism is required to equate the objects with the
935 new and the old TOIs. This mechanism consists of signaling, within
936 the CID, that the newly assigned TOI for the current Carousel
937 Instance is equivalent to the TOI used within a previous Carousel
938 Instance. By convention, the reference tuple for any object is the
939 {TOI; CIID} tuple used for its first transmission within a Carousel
940 Instance. This tuple MUST be used whenever a TOI equivalence is
941 provided. <a href="#section-2.2">Section 2.2</a> details how to describe these TOI
942 equivalences.
943
944
945
946
947
948 <span class="grey">Roca &amp; Adamson Experimental [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
951
952
953 <span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. FCAST Sender Behavior</span>
954
955 This section provides an informative description of expected FCAST
956 sender behavior. The following operations can take place at a
957 sender:
958
959 1. The user (or another application) selects a set of objects (e.g.,
960 files) to deliver and submits them, along with their metadata, to
961 the FCAST application.
962
963 2. For each object, FCAST creates the Compound Object and registers
964 it in the Carousel Instance.
965
966 3. The user then informs FCAST that all the objects of the set have
967 been submitted. If the user knows that no new object will be
968 submitted in the future (i.e., if the session's content is now
969 complete), the user informs FCAST. Finally, the user specifies
970 how many transmission cycles are desired (this number may be
971 infinite).
972
973 4. At this point, the FCAST application knows the full list of
974 Compound Objects that are part of the Carousel Instance and can
975 create a CID if desired, possibly with "Fcast-CID-Complete: 1" if
976 no new objects will be sent in the future.
977
978 5. The FCAST application can now define a transmission schedule of
979 these Compound Objects, including the optional CID. This
980 schedule defines in which order the packets of the various
981 Compound Objects should be sent. This document does not specify
982 any scheme. This is left to the developer within the provisions
983 of the underlying ALC or NORM protocol used and the knowledge of
984 the target use-case.
985
986 6. The FCAST application then starts the carousel transmission, for
987 the number of cycles specified. Transmissions take place until:
988
989 * the desired number of transmission cycles has been reached, or
990
991 * the user wants to prematurely stop the transmissions, or
992
993 * the user wants to add one or several new objects to the
994 carousel, or on the contrary wants to remove old objects from
995 the carousel. In that case, a new Carousel Instance must be
996 created.
997
998 7. If the session is not finished, then continue at Step 1 above.
999
1000
1001
1002
1003
1004 <span class="grey">Roca &amp; Adamson Experimental [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1007
1008
1009 <span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. FCAST Receiver Behavior</span>
1010
1011 This section provides an informative description of expected FCAST
1012 receiver behavior. The following operations can take place at a
1013 receiver:
1014
1015 1. The receiver joins the session and collects incoming packets.
1016
1017 2. If the header portion of a Compound Object is entirely received
1018 (which may happen before receiving the entire object with some
1019 ALC/NORM configurations), or if the metadata is sent by means of
1020 another mechanism prior to the object, the receiver processes the
1021 metadata and chooses whether or not to continue to receive the
1022 object content.
1023
1024 3. When a Compound Object has been entirely received, the receiver
1025 processes the header, retrieves the object metadata, perhaps
1026 decodes the metadata, and processes the object accordingly.
1027
1028 4. When a CID is received, as indicated by the "C" flag set in the
1029 FCAST Header, the receiver decodes the CID and retrieves the list
1030 of objects that are part of the current Carousel Instance. This
1031 list can be used to remove objects sent in a previous Carousel
1032 Instance that might not have been totally decoded and that are no
1033 longer part of the current Carousel Instance.
1034
1035 5. When a CID is received, the receiver also retrieves the list of
1036 TOI equivalences, if any, and takes appropriate measures, for
1037 instance, by informing the transport layer.
1038
1039 6. When a receiver receives a CID with an "Fcast-CID-Complete"
1040 metadata entry set to "Fcast-CID-Complete: 1" and has
1041 successfully received all the objects of the current Carousel
1042 Instance, it can safely exit from the current FCAST session.
1043
1044 7. Otherwise, continue at Step 2 above.
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Roca &amp; Adamson Experimental [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Requirements for Compliant Implementations</span>
1066
1067 This section lists the features that any compliant FCAST/ALC or
1068 FCAST/NORM implementation MUST support, and those that remain
1069 OPTIONAL, e.g., in order to enable some optimizations for a given
1070 use-case, at a receiver.
1071
1072 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Requirements Related to the Object Metadata</span>
1073
1074 Metadata transmission mechanisms:
1075
1076 +------------------+------------------------------------------------+
1077 | Feature | Status |
1078 +------------------+------------------------------------------------+
1079 | metadata | An FCAST sender MUST send metadata with the |
1080 | transmission | in-band mechanism provided by FCAST, i.e., |
1081 | using FCAST's | within the FCAST Header. All the FCAST |
1082 | in-band | receivers MUST be able to process metadata |
1083 | mechanism | sent with this FCAST in-band mechanism. |
1084 | | |
1085 | metadata | In addition to the FCAST in-band transmission |
1086 | transmission | of metadata, an FCAST sender MAY send a subset |
1087 | using other | or all of the metadata using another |
1088 | mechanisms | mechanism. Supporting this mechanism in a |
1089 | | compliant FCAST receiver is OPTIONAL, and its |
1090 | | use is OPTIONAL too. An FCAST receiver MAY |
1091 | | support this mechanism and take advantage of |
1092 | | the metadata sent in this way. If that is |
1093 | | not the case, the FCAST receiver will receive |
1094 | | and process metadata sent in-band anyway. |
1095 | | See <a href="#appendix-B">Appendix B</a>. |
1096 +------------------+------------------------------------------------+
1097
1098 Metadata format and encoding:
1099
1100 +-----------------+-------------------------------------------------+
1101 | Feature | Status |
1102 +-----------------+-------------------------------------------------+
1103 | Metadata Format | All FCAST implementations MUST support an |
1104 | (MDFmt field) | HTTP/1.1 metainformation format [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>]. |
1105 | | |
1106 | Metadata | All FCAST implementations MUST support both |
1107 | Encoding (MDEnc | UTF-8 encoded text and GZIP compressed |
1108 | field) | [<a href="./rfc1952" title="&quot;GZIP file format specification version 4.3&quot;">RFC1952</a>] UTF-8 encoded text for the Object |
1109 | | Metadata field. |
1110 +-----------------+-------------------------------------------------+
1111
1112
1113
1114
1115
1116 <span class="grey">Roca &amp; Adamson Experimental [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1119
1120
1121 Metadata items (<a href="#section-3.3">Section 3.3</a>):
1122
1123 +-------------------------------+-----------------------------------+
1124 | Feature | Status |
1125 +-------------------------------+-----------------------------------+
1126 | Content-Location | MUST be supported. |
1127 | | |
1128 | Content-Type | MUST be supported. |
1129 | | |
1130 | Content-Length | MUST be supported. |
1131 | | |
1132 | Content-Encoding | MUST be supported. All FCAST |
1133 | | implementations MUST support GZIP |
1134 | | encoding [<a href="./rfc1952" title="&quot;GZIP file format specification version 4.3&quot;">RFC1952</a>]. |
1135 | | |
1136 | Fcast-Obj-Digest-SHA1 | MUST be supported. |
1137 | | |
1138 | Fcast-Obj-Digest-SHA256 | MUST be supported. |
1139 | | |
1140 | Fcast-Obj-Slice-Nb | MUST be supported. |
1141 | | |
1142 | Fcast-Obj-Slice-Idx | MUST be supported. |
1143 | | |
1144 | Fcast-Obj-Slice-Offset | MUST be supported. |
1145 +-------------------------------+-----------------------------------+
1146
1147 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Requirements Related to the Carousel Instance Descriptor</span>
1148
1149 Any compliant FCAST implementation MUST support the CID mechanism, in
1150 order to list the Compound Objects that are part of a given Carousel
1151 Instance. However, its use is OPTIONAL.
1152
1153 CID-specific Metadata items (<a href="#section-2.2">Section 2.2</a>):
1154
1155 +--------------------+--------------------+
1156 | Feature | Status |
1157 +--------------------+--------------------+
1158 | Fcast-CID-Complete | MUST be supported. |
1159 | Fcast-CID-ID | MUST be supported. |
1160 +--------------------+--------------------+
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Roca &amp; Adamson Experimental [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1175
1176
1177 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
1178
1179 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Problem Statement</span>
1180
1181 A content delivery system may be subject to attacks that target:
1182
1183 o the network, to compromise the delivery infrastructure (e.g., by
1184 creating congestion),
1185
1186 o the Content Delivery Protocol (CDP), to compromise the delivery
1187 mechanism (i.e., FCAST in this case), or
1188
1189 o the content itself, to corrupt the objects being transmitted.
1190
1191 These attacks can be launched against all or any subset of the
1192 following:
1193
1194 o the data flow itself (e.g., by sending forged packets),
1195
1196 o the session control parameters sent either in-band or out-of-band
1197 (e.g., by corrupting the session description, the CID, the object
1198 metadata, or the ALC/LCT control parameters), or
1199
1200 o some associated building blocks (e.g., the congestion control
1201 component).
1202
1203 More details on these possible attacks are provided in the following
1204 sections, along with possible countermeasures. Recommendations are
1205 made in <a href="#section-5.5">Section 5.5</a>.
1206
1207 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Attacks against the Data Flow</span>
1208
1209 The following types of attacks against the data flow exist:
1210
1211 o attacks that are meant to gain unauthorized access to a
1212 confidential object (e.g., obtaining non-free content without
1213 purchasing it) and
1214
1215 o attacks that try to corrupt the object being transmitted (e.g., to
1216 inject malicious code within an object, or to prevent a receiver
1217 from using an object; this would be a denial-of-service (DoS)
1218 attack).
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Roca &amp; Adamson Experimental [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1231
1232
1233 <span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Attacks Meant to Gain Access to Confidential Objects</span>
1234
1235 Modern cryptographic mechanisms can provide access control to
1236 transmitted objects. One way to do this is by encrypting the entire
1237 object prior to transmission, knowing that authenticated receivers
1238 have the cryptographic mechanisms to decrypt the content. Another
1239 way is to encrypt individual packets using IPsec/ESP [<a href="./rfc4303" title="&quot;IP Encapsulating Security Payload (ESP)&quot;">RFC4303</a>] (see
1240 also <a href="#section-5.5">Section 5.5</a>). These two techniques can also provide
1241 confidentiality to the objects being transferred.
1242
1243 If access control and/or confidentiality services are desired, one of
1244 these mechanisms is RECOMMENDED and SHOULD be deployed.
1245
1246 <span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. Attacks Meant to Corrupt Objects</span>
1247
1248 Protection against attacks on the data integrity of the object may be
1249 achieved by a mechanism agreed upon between the sender and receiver
1250 that features sender authentication and a method to verify that the
1251 object integrity has remained intact during transmission. This
1252 service can be provided at the object level, but in that case a
1253 receiver has no way to identify what symbols are corrupted if the
1254 object is detected as corrupted. This service can also be provided
1255 at the packet level. In some cases, after removing all corrupted
1256 packets, the object may be recovered. Several techniques can provide
1257 data integrity and sender authentication services:
1258
1259 o At the object level, the object can be digitally signed, for
1260 instance, by using RSASSA-PKCS1-v1_5 [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>]. This signature
1261 enables a receiver to check the object integrity. Even if digital
1262 signatures are computationally expensive, this calculation occurs
1263 only once per object, which is usually acceptable.
1264
1265 o At the packet level, each packet can be digitally signed
1266 [<a href="./rfc6584" title="&quot;Simple Authentication Schemes for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols&quot;">RFC6584</a>]. A major limitation is the high computational and
1267 transmission overheads that this solution requires.
1268
1269 o At the packet level, a Group-keyed Message Authentication Code
1270 (MAC) [<a href="./rfc2104" title="&quot;HMAC: Keyed- Hashing for Message Authentication&quot;">RFC2104</a>] [<a href="./rfc6584" title="&quot;Simple Authentication Schemes for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols&quot;">RFC6584</a>] scheme can be used, for instance, by
1271 using HMAC-SHA-256 with a secret key shared by all the group
1272 members, senders, and receivers. This technique creates a
1273 cryptographically secured digest of a packet that is sent along
1274 with the packet itself. The Group-keyed MAC scheme does not
1275 create prohibitive processing loads or transmission overhead, but
1276 it has a major limitation: it only provides a group
1277 authentication/integrity service, since all group members share
1278 the same secret group key; this means that each member can send a
1279 forged packet. It is therefore restricted to situations where
1280
1281
1282
1283
1284 <span class="grey">Roca &amp; Adamson Experimental [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1287
1288
1289 group members are fully trusted, or in association with another
1290 technique as a preliminary check to quickly detect attacks
1291 initiated by non-group members and to discard their packets.
1292
1293 o At the packet level, Timed Efficient Stream Loss-Tolerant
1294 Authentication (TESLA) [<a href="./rfc4082" title="&quot;Timed Efficient Stream Loss-Tolerant Authentication (TESLA): Multicast Source Authentication Transform Introduction&quot;">RFC4082</a>] [<a href="./rfc5776" title="&quot;Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols&quot;">RFC5776</a>] is an attractive
1295 solution that is robust to losses, provides an authentication and
1296 integrity verification service, and does not create any
1297 prohibitive processing load or transmission overhead. Yet, a
1298 delay is incurred in checking a TESLA authenticated packet; this
1299 delay may be more than what is desired in some use-cases.
1300
1301 o At the packet level, IPsec/ESP [<a href="./rfc4303" title="&quot;IP Encapsulating Security Payload (ESP)&quot;">RFC4303</a>] can be used to check the
1302 integrity and authenticate the sender of all the packets being
1303 exchanged in a session (see <a href="#section-5.5">Section 5.5</a>).
1304
1305 Techniques relying on public key cryptography (digital signatures and
1306 TESLA during the bootstrap process, when used) require that public
1307 keys be securely associated to the entities. This can be achieved
1308 via a Public Key Infrastructure (PKI), a Pretty Good Privacy (PGP)
1309 Web of Trust, or by securely preplacing the public keys of each group
1310 member.
1311
1312 Techniques relying on symmetric key cryptography (Group-keyed MAC)
1313 require that a secret key be shared by all group members. This can
1314 be achieved by means of a group key management protocol or simply by
1315 securely preplacing the secret key (but this manual solution has many
1316 limitations).
1317
1318 It is up to the developer and deployer, who know the security
1319 requirements and features of the target application area, to define
1320 which solution is the most appropriate. In any case, whenever there
1321 is a threat of object corruption, it is RECOMMENDED that at least one
1322 of these techniques be used. <a href="#section-5.5">Section 5.5</a> defines minimum security
1323 recommendations that can be used to provide such services.
1324
1325 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Attacks against the Session Control Parameters and Associated</span>
1326 <span class="h3"> Building Blocks</span>
1327
1328 Let us now consider attacks against the session control parameters
1329 and the associated building blocks. The attacker can target, among
1330 other things, the following:
1331
1332 o the session description,
1333
1334 o the FCAST CID,
1335
1336 o the metadata of an object,
1337
1338
1339
1340 <span class="grey">Roca &amp; Adamson Experimental [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1343
1344
1345 o the ALC/LCT parameters, carried within the LCT header, or
1346
1347 o the FCAST associated building blocks, for instance, the multiple
1348 rate congestion control protocol.
1349
1350 The consequences of these attacks are potentially serious, since they
1351 can compromise the behavior of the content delivery system or even
1352 compromise the network itself.
1353
1354 <span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a>. Attacks against the Session Description</span>
1355
1356 An FCAST receiver may potentially obtain an incorrect session
1357 description for the session. The consequence is that legitimate
1358 receivers with the wrong session description will be unable to
1359 correctly receive the session content or will inadvertently try to
1360 receive at a much higher rate than they are capable of, thereby
1361 possibly disrupting other traffic in the network.
1362
1363 To avoid these problems, it is RECOMMENDED that measures be taken to
1364 prevent receivers from accepting incorrect session descriptions. One
1365 such measure is sender authentication to ensure that receivers only
1366 accept legitimate session descriptions from authorized senders. How
1367 these measures are achieved is outside the scope of this document,
1368 since this session description is usually carried out-of-band.
1369
1370 <span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a>. Attacks against the FCAST CID</span>
1371
1372 Corrupting the FCAST CID is one way to create a DoS attack. For
1373 example, the attacker can insert an "Fcast-CID-Complete: 1" metadata
1374 entry to make the receivers believe that no further modification will
1375 be done.
1376
1377 It is therefore RECOMMENDED that measures be taken to guarantee the
1378 integrity and to check the sender's identity of the CID. To that
1379 purpose, one of the countermeasures mentioned above (<a href="#section-5.2.2">Section 5.2.2</a>)
1380 SHOULD be used. These measures will either be applied at the packet
1381 level or globally over the whole CID object. When there is no
1382 packet-level integrity verification scheme, it is RECOMMENDED to
1383 digitally sign the CID.
1384
1385 <span class="h4"><a class="selflink" id="section-5.3.3" href="#section-5.3.3">5.3.3</a>. Attacks against the Object Metadata</span>
1386
1387 Modifying the object metadata is another way to launch an attack.
1388 For example, the attacker may change the message digest associated to
1389 an object, leading a receiver to reject an object even if it has been
1390 correctly received. More generally, a receiver SHOULD be very
1391 careful during metadata processing. For instance, a receiver SHOULD
1392 NOT try to follow links (e.g., the URI contained in the
1393
1394
1395
1396 <span class="grey">Roca &amp; Adamson Experimental [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1399
1400
1401 Content-Location metadata). As another example, malformed HTTP
1402 content can be used as an attack vector, and a receiver should take
1403 great care with such content.
1404
1405 It is therefore RECOMMENDED that measures be taken to guarantee the
1406 integrity and to check the identity of the sender of the Compound
1407 Object. To that purpose, one of the countermeasures mentioned above
1408 (<a href="#section-5.2.2">Section 5.2.2</a>) SHOULD be used. These measures will either be
1409 applied at the packet level or globally over the whole Compound
1410 Object. When there is no packet-level integrity verification scheme,
1411 it is RECOMMENDED to digitally sign the Compound Object.
1412
1413 <span class="h4"><a class="selflink" id="section-5.3.4" href="#section-5.3.4">5.3.4</a>. Attacks against the ALC/LCT and NORM Parameters</span>
1414
1415 By corrupting the ALC/LCT header (or header extensions), one can
1416 execute attacks on the underlying ALC/LCT implementation. For
1417 example, sending forged ALC packets with the Close Session "A" flag
1418 set to 1 can lead the receiver to prematurely close the session.
1419 Similarly, sending forged ALC packets with the Close Object "B" flag
1420 set to 1 can lead the receiver to prematurely give up the reception
1421 of an object. The same comments can be made for NORM.
1422
1423 It is therefore RECOMMENDED that measures be taken to guarantee the
1424 integrity and to check the sender's identity in each ALC or NORM
1425 packet received. To that purpose, one of the countermeasures
1426 mentioned above (<a href="#section-5.2.2">Section 5.2.2</a>) SHOULD be used.
1427
1428 <span class="h4"><a class="selflink" id="section-5.3.5" href="#section-5.3.5">5.3.5</a>. Attacks against the Associated Building Blocks</span>
1429
1430 Let us first focus on the congestion control building block that may
1431 be used in an ALC or NORM session. A receiver with an incorrect or
1432 corrupted implementation of the multiple rate congestion control
1433 building block may affect the health of the network in the path
1434 between the sender and the receiver and may also affect the reception
1435 rates of other receivers who joined the session.
1436
1437 When congestion control is applied with FCAST, it is therefore
1438 RECOMMENDED that receivers be authenticated as legitimate receivers
1439 before they can join the session. If authenticating a receiver does
1440 not prevent that receiver from launching an attack, the network
1441 operator will still be able to easily identify the receiver that
1442 launched the attack and take countermeasures. The details of how
1443 this is done are outside the scope of this document.
1444
1445 When congestion control is applied with FCAST, it is also RECOMMENDED
1446 that a packet-level authentication scheme be used, as explained in
1447 <a href="#section-5.2.2">Section 5.2.2</a>. Some of them, like TESLA, only provide a delayed
1448 authentication service, whereas congestion control requires a rapid
1449
1450
1451
1452 <span class="grey">Roca &amp; Adamson Experimental [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1455
1456
1457 reaction. It is therefore RECOMMENDED [<a href="./rfc5775" title="&quot;Asynchronous Layered Coding (ALC) Protocol Instantiation&quot;">RFC5775</a>] that a receiver
1458 using TESLA quickly reduce its subscription level when the receiver
1459 believes that congestion did occur, even if the packet has not yet
1460 been authenticated. Therefore, TESLA will not prevent DoS attacks
1461 where an attacker makes the receiver believe that congestion
1462 occurred. This is an issue for the receiver, but this will not
1463 compromise the network. Other authentication methods that do not
1464 feature this delayed authentication might be preferable, or a Group-
1465 keyed MAC scheme could be used in parallel with TESLA to prevent
1466 attacks launched from outside of the group.
1467
1468 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Other Security Considerations</span>
1469
1470 Lastly, we note that the security considerations that apply to, and
1471 are described in, ALC [<a href="./rfc5775" title="&quot;Asynchronous Layered Coding (ALC) Protocol Instantiation&quot;">RFC5775</a>], LCT [<a href="./rfc5651" title="&quot;Layered Coding Transport (LCT) Building Block&quot;">RFC5651</a>], NORM [<a href="./rfc5740" title="&quot;NACK-Oriented Reliable Multicast (NORM) Transport Protocol&quot;">RFC5740</a>], and
1472 FEC [<a href="./rfc5052" title="&quot;Forward Error Correction (FEC) Building Block&quot;">RFC5052</a>] also apply to FCAST, as FCAST builds on those
1473 specifications. In addition, any security considerations that apply
1474 to any congestion control building block used in conjunction with
1475 FCAST also apply to FCAST. Finally, the security discussion of
1476 [<a href="#ref-RMT-SEC" title="&quot;Security and Reliable Multicast Transport Protocols: Discussions and Guidelines&quot;">RMT-SEC</a>] also applies here.
1477
1478 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Minimum Security Recommendations</span>
1479
1480 We now introduce a security configuration that is mandatory to
1481 implement but not necessarily mandatory to use, in the sense of
1482 [<a href="./rfc3365" title="&quot;Strong Security Requirements for Internet Engineering Task Force Standard Protocols&quot;">RFC3365</a>]. Since FCAST/ALC relies on ALC/LCT, it inherits the
1483 "baseline secure ALC operation" of [<a href="./rfc5775" title="&quot;Asynchronous Layered Coding (ALC) Protocol Instantiation&quot;">RFC5775</a>]. Similarly, since
1484 FCAST/NORM relies on NORM, it inherits the "baseline secure NORM
1485 operation" of [<a href="./rfc5740" title="&quot;NACK-Oriented Reliable Multicast (NORM) Transport Protocol&quot;">RFC5740</a>]. Therefore, IPsec/ESP in transport mode MUST
1486 be implemented, but not necessarily used, in accordance with
1487 [<a href="./rfc5775" title="&quot;Asynchronous Layered Coding (ALC) Protocol Instantiation&quot;">RFC5775</a>] and [<a href="./rfc5740" title="&quot;NACK-Oriented Reliable Multicast (NORM) Transport Protocol&quot;">RFC5740</a>]. [<a href="./rfc4303" title="&quot;IP Encapsulating Security Payload (ESP)&quot;">RFC4303</a>] explains that ESP can be used to
1488 potentially provide confidentiality, data origin authentication,
1489 content integrity, anti-replay, and (limited) traffic flow
1490 confidentiality. [<a href="./rfc5775" title="&quot;Asynchronous Layered Coding (ALC) Protocol Instantiation&quot;">RFC5775</a>] specifies that the data origin
1491 authentication, content integrity, and anti-replay services SHALL be
1492 used, and that the confidentiality service is RECOMMENDED. If a
1493 short-lived session MAY rely on manual keying, it is also RECOMMENDED
1494 that an automated key management scheme be used, especially in the
1495 case of long-lived sessions.
1496
1497 Therefore, the RECOMMENDED solution for FCAST provides per-packet
1498 security, with data origin authentication, integrity verification,
1499 and anti-replay. This is sufficient to prevent most of the in-band
1500 attacks listed above. If confidentiality is required, a per-packet
1501 encryption SHOULD also be used.
1502
1503
1504
1505
1506
1507
1508 <span class="grey">Roca &amp; Adamson Experimental [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1511
1512
1513 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Operational Considerations</span>
1514
1515 FCAST is compatible with any congestion control protocol designed for
1516 ALC/LCT or NORM. However, depending on the use-case, the data flow
1517 generated by the FCAST application might not be constant but might
1518 instead be bursty in nature. Similarly, depending on the use-case,
1519 an FCAST session might be very short. Whether and how this will
1520 impact the congestion control protocol is out of the scope of the
1521 present document.
1522
1523 FCAST is compatible with any security mechanism designed for ALC/LCT
1524 or NORM. The use of a security scheme is strongly RECOMMENDED (see
1525 <a href="#section-5">Section 5</a>).
1526
1527 FCAST is compatible with any FEC scheme designed for ALC/LCT or NORM.
1528 Whether FEC is used or not, and the kind of FEC scheme used, are to
1529 some extent transparent to FCAST.
1530
1531 FCAST is compatible with both IPv4 and IPv6. Nothing in the FCAST
1532 specification has any implication on the source or destination IP
1533 address type.
1534
1535 The delivery service provided by FCAST might be fully reliable, or
1536 only partially reliable, depending upon:
1537
1538 o the way ALC or NORM is used (e.g., whether FEC encoding and/or
1539 NACK-based repair requests are used or not),
1540
1541 o the way the FCAST carousel is used (e.g., whether the objects are
1542 made available for a long time span or not), and
1543
1544 o the way in which FCAST itself is deployed (e.g., whether there is
1545 a session control application that might automatically extend an
1546 existing FCAST session until all receivers have received the
1547 transmitted content).
1548
1549 The receiver set can be restricted to a single receiver or possibly a
1550 very large number of receivers. While the choice of the underlying
1551 transport protocol (i.e., ALC or NORM) and its parameters may limit
1552 the practical receiver group size, nothing in FCAST itself limits it.
1553 For instance, if FCAST/ALC is used on top of purely unidirectional
1554 transport channels with no feedback information at all, which is the
1555 default mode of operation, then scalability is at a maximum, since
1556 neither FCAST, ALC, UDP, nor IP generates any feedback message. On
1557 the contrary, the scalability of FCAST/NORM is typically limited by
1558 the scalability of NORM itself. For example, NORM can be configured
1559 to operate using proactive FEC without feedback, similar to ALC, with
1560 receivers configured to provide NACK and, optionally, ACK feedback,
1561
1562
1563
1564 <span class="grey">Roca &amp; Adamson Experimental [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1567
1568
1569 or a hybrid combination of these. Similarly, if FCAST is used along
1570 with a session control application that collects reception
1571 information from the receivers, then this session control application
1572 may limit the scalability of the global object delivery system. This
1573 situation can of course be mitigated by using a hierarchy of servers
1574 or feedback message aggregation. The details of this are out of the
1575 scope of the present document.
1576
1577 The content of a Carousel Instance MAY be described by means of an
1578 OPTIONAL CID (<a href="#section-3.5">Section 3.5</a>). The decision of whether the CID
1579 mechanism should be used or not is left to the sender. When it is
1580 used, the question of how often and when a CID should be sent is also
1581 left to the sender. These considerations depend on many parameters,
1582 including the target use-case and the session dynamics. For
1583 instance, it may be appropriate to send a CID at the beginning of
1584 each new Carousel Instance and then periodically. These operational
1585 aspects are out of the scope of the present document.
1586
1587 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
1588
1589 Per this specification, IANA has created three new registries.
1590
1591 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Creation of the FCAST Object Metadata Format Registry</span>
1592
1593 IANA has created a new registry, "FCAST Object Metadata Format"
1594 (MDFmt), with a reference to this document. The registry entries
1595 consist of a numeric value from 0 to 15, inclusive (i.e., they are
1596 4-bit positive integers), that defines the format of the object
1597 metadata (see <a href="#section-2.1">Section 2.1</a>).
1598
1599 The initial value for this registry is defined below. Future
1600 assignments are to be made through Expert Review with Specification
1601 Required [<a href="./rfc5226" title="">RFC5226</a>].
1602
1603 +-------------+---------------------+--------------+----------------+
1604 | Value | Format Name | Format | Reference |
1605 | | | Reference | |
1606 +-------------+---------------------+--------------+----------------+
1607 | 0 (default) | HTTP/1.1 | [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>], | This |
1608 | | metainformation | <a href="#section-7.1">Section 7.1</a> | specification |
1609 | | format | | |
1610 +-------------+---------------------+--------------+----------------+
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620 <span class="grey">Roca &amp; Adamson Experimental [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1623
1624
1625 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Creation of the FCAST Object Metadata Encoding Registry</span>
1626
1627 IANA has created a new registry, "FCAST Object Metadata Encoding"
1628 (MDEnc), with a reference to this document. The registry entries
1629 consist of a numeric value from 0 to 15, inclusive (i.e., they are
1630 4-bit positive integers), that defines the encoding of the Object
1631 Metadata field (see <a href="#section-2.1">Section 2.1</a>).
1632
1633 The initial values for this registry are defined below. Future
1634 assignments are to be made through Expert Review [<a href="./rfc5226" title="">RFC5226</a>].
1635
1636 +---------+------------------+-----------------+--------------------+
1637 | Value | Encoding Name | Encoding | Reference |
1638 | | | Reference | |
1639 +---------+------------------+-----------------+--------------------+
1640 | 0 | UTF-8 encoded | [<a href="./rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>] | This specification |
1641 | | text | | |
1642 | | | | |
1643 | 1 | GZIP'ed UTF-8 | [<a href="./rfc1952" title="&quot;GZIP file format specification version 4.3&quot;">RFC1952</a>], | This specification |
1644 | | encoded text | [<a href="./rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>] | |
1645 +---------+------------------+-----------------+--------------------+
1646
1647 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Creation of the FCAST Object Metadata Types Registry</span>
1648
1649 IANA has created a new registry, "FCAST Object Metadata Types"
1650 (MDType), with a reference to this document. The registry entries
1651 consist of additional text metadata type identifiers and descriptions
1652 for metadata item types that are specific to FCAST operation and not
1653 previously defined in [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>]. The initial values are those
1654 described in <a href="#section-3.3">Section 3.3</a> of this specification. This table
1655 summarizes those initial registry entries. Future assignments are to
1656 be made through Expert Review [<a href="./rfc5226" title="">RFC5226</a>].
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676 <span class="grey">Roca &amp; Adamson Experimental [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1679
1680
1681 +-------------------------+-----------------------+-----------------+
1682 | Metadata Type | Description | Reference |
1683 +-------------------------+-----------------------+-----------------+
1684 | Fcast-Obj-Digest-SHA1 | A string that | This |
1685 | | contains the "base64" | specification |
1686 | | encoding of the SHA-1 | |
1687 | | message digest of the | |
1688 | | object before any | |
1689 | | content encoding is | |
1690 | | applied (if any) and | |
1691 | | without considering | |
1692 | | the FCAST Header | |
1693 | | | |
1694 | Fcast-Obj-Digest-SHA256 | A string that | This |
1695 | | contains the "base64" | specification |
1696 | | encoding of the | |
1697 | | SHA-256 message | |
1698 | | digest of the object | |
1699 | | before any content | |
1700 | | encoding is applied | |
1701 | | (if any) and without | |
1702 | | considering the FCAST | |
1703 | | Header | |
1704 | | | |
1705 | Fcast-Obj-Slice-Nb | Unsigned 32-bit | This |
1706 | | integer that contains | specification |
1707 | | the total number of | |
1708 | | slices. A value | |
1709 | | greater than 1 | |
1710 | | indicates that this | |
1711 | | object is the result | |
1712 | | of a split of the | |
1713 | | original object | |
1714 | | | |
1715 | Fcast-Obj-Slice-Idx | Unsigned 32-bit | This |
1716 | | integer that contains | specification |
1717 | | the slice index (in | |
1718 | | the {0 .. SliceNb - | |
1719 | | 1} interval) | |
1720 | | | |
1721 | Fcast-Obj-Slice-Offset | Unsigned 64-bit | This |
1722 | | integer that contains | specification |
1723 | | the byte offset at | |
1724 | | which this slice | |
1725 | | starts within the | |
1726 | | original object | |
1727 +-------------------------+-----------------------+-----------------+
1728
1729
1730
1731
1732 <span class="grey">Roca &amp; Adamson Experimental [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1735
1736
1737 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgments</span>
1738
1739 The authors are grateful to the authors of [<a href="#ref-ALC-00" title="&quot;Asynchronous Layered Coding: A scalable reliable multicast protocol&quot;">ALC-00</a>] for specifying
1740 the first version of FCAST/ALC. The authors are also grateful to
1741 David Harrington, Gorry Fairhurst, and Lorenzo Vicisano for their
1742 valuable comments. The authors are also grateful to Jari Arkko,
1743 Ralph Droms, Wesley Eddy, Roni Even, Stephen Farrell, Russ Housley,
1744 Chris Lonvick, Pete Resnick, Joseph Yee, and Martin Stiemerling.
1745
1746 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
1747
1748 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
1749
1750 [<a id="ref-RFC1071">RFC1071</a>] Braden, R., Borman, D., Partridge, C., and W. Plummer,
1751 "Computing the Internet checksum", <a href="./rfc1071">RFC 1071</a>,
1752 September 1988.
1753
1754 [<a id="ref-RFC1952">RFC1952</a>] Deutsch, P., "GZIP file format specification version 4.3",
1755 <a href="./rfc1952">RFC 1952</a>, May 1996.
1756
1757 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
1758 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
1759
1760 [<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
1761 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
1762 Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
1763
1764 [<a id="ref-RFC3174">RFC3174</a>] Eastlake, D. and P. Jones, "US Secure Hash Algorithm 1
1765 (SHA1)", <a href="./rfc3174">RFC 3174</a>, September 2001.
1766
1767 [<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of
1768 ISO 10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.
1769
1770 [<a id="ref-RFC4648">RFC4648</a>] Josefsson, S., "The Base16, Base32, and Base64 Data
1771 Encodings", <a href="./rfc4648">RFC 4648</a>, October 2006.
1772
1773 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
1774 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
1775 May 2008.
1776
1777 [<a id="ref-RFC5234">RFC5234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
1778 Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008.
1779
1780 [<a id="ref-RFC5651">RFC5651</a>] Luby, M., Watson, M., and L. Vicisano, "Layered Coding
1781 Transport (LCT) Building Block", <a href="./rfc5651">RFC 5651</a>, October 2009.
1782
1783
1784
1785
1786
1787
1788 <span class="grey">Roca &amp; Adamson Experimental [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1791
1792
1793 [<a id="ref-RFC5740">RFC5740</a>] Adamson, B., Bormann, C., Handley, M., and J. Macker,
1794 "NACK-Oriented Reliable Multicast (NORM) Transport
1795 Protocol", <a href="./rfc5740">RFC 5740</a>, November 2009.
1796
1797 [<a id="ref-RFC5775">RFC5775</a>] Luby, M., Watson, M., and L. Vicisano, "Asynchronous
1798 Layered Coding (ALC) Protocol Instantiation", <a href="./rfc5775">RFC 5775</a>,
1799 April 2010.
1800
1801 [<a id="ref-RFC6234">RFC6234</a>] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms
1802 (SHA and SHA-based HMAC and HKDF)", <a href="./rfc6234">RFC 6234</a>, May 2011.
1803
1804 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
1805
1806 [<a id="ref-ALC-00">ALC-00</a>] Luby, M., Gemmell, J., Vicisano, L., Rizzo, L., Crowcroft,
1807 J., and B. Lueckenhoff, "Asynchronous Layered Coding: A
1808 scalable reliable multicast protocol", Work in Progress,
1809 March 2000.
1810
1811 [<a id="ref-RFC2104">RFC2104</a>] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed-
1812 Hashing for Message Authentication", <a href="./rfc2104">RFC 2104</a>,
1813 February 1997.
1814
1815 [<a id="ref-RFC3365">RFC3365</a>] Schiller, J., "Strong Security Requirements for Internet
1816 Engineering Task Force Standard Protocols", <a href="https://www.rfc-editor.org/bcp/bcp61">BCP 61</a>,
1817 <a href="./rfc3365">RFC 3365</a>, August 2002.
1818
1819 [<a id="ref-RFC3447">RFC3447</a>] Jonsson, J. and B. Kaliski, "Public-Key Cryptography
1820 Standards (PKCS) #1: RSA Cryptography Specifications
1821 Version 2.1", <a href="./rfc3447">RFC 3447</a>, February 2003.
1822
1823 [<a id="ref-RFC4082">RFC4082</a>] Perrig, A., Song, D., Canetti, R., Tygar, J., and B.
1824 Briscoe, "Timed Efficient Stream Loss-Tolerant
1825 Authentication (TESLA): Multicast Source Authentication
1826 Transform Introduction", <a href="./rfc4082">RFC 4082</a>, June 2005.
1827
1828 [<a id="ref-RFC4303">RFC4303</a>] Kent, S., "IP Encapsulating Security Payload (ESP)",
1829 <a href="./rfc4303">RFC 4303</a>, December 2005.
1830
1831 [<a id="ref-RFC5052">RFC5052</a>] Watson, M., Luby, M., and L. Vicisano, "Forward Error
1832 Correction (FEC) Building Block", <a href="./rfc5052">RFC 5052</a>, August 2007.
1833
1834 [<a id="ref-RFC5510">RFC5510</a>] Lacan, J., Roca, V., Peltotalo, J., and S. Peltotalo,
1835 "Reed-Solomon Forward Error Correction (FEC) Schemes",
1836 <a href="./rfc5510">RFC 5510</a>, April 2009.
1837
1838
1839
1840
1841
1842
1843
1844 <span class="grey">Roca &amp; Adamson Experimental [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1847
1848
1849 [<a id="ref-RFC5776">RFC5776</a>] Roca, V., Francillon, A., and S. Faurite, "Use of Timed
1850 Efficient Stream Loss-Tolerant Authentication (TESLA) in
1851 the Asynchronous Layered Coding (ALC) and NACK-Oriented
1852 Reliable Multicast (NORM) Protocols", <a href="./rfc5776">RFC 5776</a>,
1853 April 2010.
1854
1855 [<a id="ref-RFC6363">RFC6363</a>] Watson, M., Begen, A., and V. Roca, "Forward Error
1856 Correction (FEC) Framework", <a href="./rfc6363">RFC 6363</a>, October 2011.
1857
1858 [<a id="ref-RFC6584">RFC6584</a>] Roca, V., "Simple Authentication Schemes for the
1859 Asynchronous Layered Coding (ALC) and NACK-Oriented
1860 Reliable Multicast (NORM) Protocols", <a href="./rfc6584">RFC 6584</a>,
1861 April 2012.
1862
1863 [<a id="ref-RFC6726">RFC6726</a>] Paila, T., Walsh, R., Luby, M., Roca, V., and R. Lehtonen,
1864 "FLUTE - File Delivery over Unidirectional Transport",
1865 <a href="./rfc6726">RFC 6726</a>, November 2012.
1866
1867 [<a id="ref-RMT-SEC">RMT-SEC</a>] Adamson, B., Roca, V., and H. Asaeda, "Security and
1868 Reliable Multicast Transport Protocols: Discussions and
1869 Guidelines", Work in Progress, May 2013.
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Roca &amp; Adamson Experimental [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1903
1904
1905 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. FCAST Examples</span>
1906
1907 This appendix provides informative examples of FCAST Compound Objects
1908 and Carousel Instance Descriptor formats.
1909
1910 <span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. Simple Compound Object Example</span>
1911
1912 0 1 2 3
1913 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1914 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1915 |Ver=0| 0 |1|0|MDFmt=0|MDEnc=0| Checksum |
1916 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1917 | FCAST Header Length=41 |
1918 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
1919 . .
1920 . "Content-Location: example_1.txt&lt;CR-LF&gt;" metadata (33 bytes) .
1921 . .
1922 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1923 | | Padding |
1924 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1925 . .
1926 . Object Data .
1927 . .
1928 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1929
1930 Figure 4: Simple Compound Object Example
1931
1932 Figure 4 shows a simple Compound Object where the metadata string, in
1933 HTTP/1.1 metainformation format (MDFmt=0), contains:
1934
1935 Content-Location: example_1.txt&lt;CR-LF&gt;
1936
1937 This UTF-8 encoded text (since MDEnc=0) is 33 bytes long (there is no
1938 final '\0' character). Therefore, 3 padding bytes are added. There
1939 is no Content-Length metadata entry for the object transported
1940 (without FCAST additional encoding) in the Object Data field, since
1941 this length can easily be calculated by the receiver as the FEC OTI
1942 Transfer Length minus the header length. Finally, the checksum
1943 encompasses the whole Compound Object (G=1).
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956 <span class="grey">Roca &amp; Adamson Experimental [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
1959
1960
1961 <span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Carousel Instance Descriptor Example</span>
1962
1963 0 1 2 3
1964 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1965 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1966 |Ver=0| 0 |1|1|MDFmt=0|MDEnc=0| Checksum |
1967 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1968 | FCAST Header Length=31 |
1969 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
1970 . .
1971 . "Fcast-CID-Complete: 1&lt;CR-LF&gt;" metadata string (23 bytes) .
1972 . .
1973 + +-+-+-+-+-+-+-+-+
1974 | | Padding |
1975 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
1976 . .
1977 . Object List string .
1978 . .
1979 . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1980 . |
1981 +-+-+-+-+-+-+-+-+
1982
1983 Figure 5: CID Object Example: Static Session
1984
1985 Figure 5 shows an example CID object, in the case of a static FCAST
1986 session, i.e., a session where the set of objects is set once and for
1987 all. The metadata UTF-8 encoded text only contains the following
1988 entry, since Fcast-CID-ID is implicit:
1989
1990 Fcast-CID-Complete: 1&lt;CR-LF&gt;
1991
1992 This UTF-8 encoded text (since MDEnc=0) is 23 bytes long (there is no
1993 final '\0' character). Therefore, 1 padding byte is added.
1994
1995 The Object List contains the following 25-byte-long string (there is
1996 no final '\0' character):
1997
1998 1,2,3,100-104,200-203,299
1999
2000 There are therefore a total of 3+5+4+1 = 13 objects in the Carousel
2001 Instance and therefore in the FCAST session. There is no metadata
2002 associated to this CID. As the session is static and composed of a
2003 single Carousel Instance, the sender did not feel the necessity to
2004 carry a Carousel Instance ID metadata.
2005
2006
2007
2008
2009
2010
2011
2012 <span class="grey">Roca &amp; Adamson Experimental [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
2015
2016
2017 <span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Additional Metadata Transmission Mechanisms</span>
2018
2019 <span class="h3"><a class="selflink" id="appendix-B.1" href="#appendix-B.1">B.1</a>. Supporting Additional Mechanisms</span>
2020
2021 In certain use-cases, FCAST can take advantage of another in-band
2022 (e.g., via NORM_INFO messages (Appendix B.2)) or out-of-band
2023 signaling mechanism. This section provides an overview of how other
2024 signaling mechanisms could be employed and a normative specification
2025 for how FCAST information is embedded when NORM_INFO messages are
2026 used for carrying FCAST Headers. Such additional signaling schemes
2027 can be used to carry the whole metadata, or a subset of it, ahead of
2028 time, before the associated Compound Object. Therefore, based on the
2029 information retrieved in this way, a receiver could decide in advance
2030 (i.e., before beginning the reception of the compound object) whether
2031 the object is of interest or not; this would mitigate the limitations
2032 of FCAST. While out-of-band techniques are out of the scope of this
2033 document, we explain below how this can be achieved in the case of
2034 FCAST/NORM.
2035
2036 Supporting additional mechanisms is OPTIONAL in FCAST
2037 implementations. In any case, an FCAST sender MUST continue to send
2038 all the required metadata in the Compound Object, even if the whole
2039 metadata, or a subset of it, is sent by another mechanism
2040 (<a href="#section-4">Section 4</a>). Additionally, when metadata is sent several times,
2041 there MUST NOT be any contradiction in the information provided by
2042 the different mechanisms. If a mismatch is detected, the metadata
2043 contained in the Compound Object MUST be used as the definitive
2044 source.
2045
2046 When metadata elements are communicated out-of-band, in advance of
2047 data transmission, the following piece of information can be useful:
2048
2049 o TOI: a positive integer that contains the Transport Object
2050 Identifier (TOI) of the object, in order to enable a receiver to
2051 easily associate the metadata to the object. The valid range for
2052 TOI values is discussed in <a href="#section-3.6">Section 3.6</a>.
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068 <span class="grey">Roca &amp; Adamson Experimental [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
2071
2072
2073 <span class="h3"><a class="selflink" id="appendix-B.2" href="#appendix-B.2">B.2</a>. Using NORM_INFO Messages with FCAST/NORM</span>
2074
2075 The NORM_INFO message of NORM can convey "out-of-band" content with
2076 respect to a given transport object. With FCAST, this message MAY be
2077 used as an additional mechanism to transmit metadata. In that case,
2078 the NORM_INFO message carries a new Compound Object that contains all
2079 the metadata of the original object, or a subset of it. The
2080 NORM_INFO Compound Object MUST NOT contain any Object Data field
2081 (i.e., it is only composed of the header), it MUST feature a
2082 non-global checksum, and it MUST NOT include a Padding field.
2083 Finally, note that the availability of NORM_INFO for a given object
2084 is signaled through the use of a dedicated flag in the NORM_DATA
2085 message header. Along with NORM's NACK-based repair request
2086 signaling, it allows a receiver to quickly (and independently)
2087 request an object's NORM_INFO content. However, a limitation here is
2088 that the FCAST Header MUST fit within the byte size limit defined by
2089 the NORM sender's configured "segment size" (typically a little less
2090 than the network MTU).
2091
2092 <span class="h4"><a class="selflink" id="appendix-B.2.1" href="#appendix-B.2.1">B.2.1</a>. Example</span>
2093
2094 In the case of FCAST/NORM, the object metadata (or a subset of it)
2095 can be carried as part of a NORM_INFO message, as a new Compound
2096 Object that does not contain any Object Data. In the following
2097 informative example, we assume that the whole metadata is carried in
2098 such a message. Figure 6 shows an example NORM_INFO message that
2099 contains the FCAST Header, including metadata. In this example, the
2100 first 16 bytes are the NORM_INFO base header; the next 12 bytes are a
2101 NORM EXT_FTI header extension containing the FEC Object Transport
2102 Information for the associated object; and the remaining bytes are
2103 the FCAST Header, including metadata. Note that "padding" MUST NOT
2104 be used and that the FCAST checksum only encompasses the Compound
2105 Object Header (G=0).
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124 <span class="grey">Roca &amp; Adamson Experimental [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
2127
2128
2129 0 1 2 3
2130 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ --
2132 |version| type=1| hdr_len = 7 | sequence | ^
2133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
2134 | source_id | n
2135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ o
2136 | instance_id | grtt |backoff| gsize | r
2137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ m
2138 | flags | fec_id = 5 | object_transport_id | v
2139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ --
2140 | HET = 64 | HEL = 3 | | ^
2141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + f
2142 | Transfer Length = 41 | t
2143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ i
2144 | Encoding Symbol Length (E) | MaxBlkLen (B) | max_n | v
2145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ --
2146 | 0 | 0 |0|0| 0 | 0 | Checksum | ^
2147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
2148 | 41 | f
2149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| c
2150 . . a
2151 . metadata UTF-8 encoded text (32 bytes) . s
2152 . . t
2153 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
2154 | | v
2155 +-+-+-+-+-+-+-+-+ --
2156
2157 Figure 6: NORM_INFO Message Containing an EXT_FTI Header Extension
2158 and an FCAST Header
2159
2160 The NORM_INFO message shown in Figure 6 contains the EXT_FTI header
2161 extension to carry the FEC OTI. In this example, the FEC OTI format
2162 is that of the Reed-Solomon FEC coding scheme for fec_id = 5, as
2163 described in [<a href="./rfc5510" title="&quot;Reed-Solomon Forward Error Correction (FEC) Schemes&quot;">RFC5510</a>]. Other alternatives for providing the FEC OTI
2164 would have been to either include it directly in the metadata of the
2165 FCAST Header or to include an EXT_FTI header extension to all
2166 NORM_DATA packets (or a subset of them). Note that the NORM
2167 "Transfer Length" is the total length of the associated Compound
2168 Object, i.e., 41 bytes.
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180 <span class="grey">Roca &amp; Adamson Experimental [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc6968">RFC 6968</a> FCAST Object Delivery July 2013</span>
2183
2184
2185 The Compound Object in this example does contain the same metadata
2186 and is formatted as in the example of Figure 4. With the combination
2187 of the FEC_OTI and the FCAST metadata, the NORM protocol and FCAST
2188 application have all of the information needed to reliably receive
2189 and process the associated object. Indeed, the NORM protocol
2190 provides rapid (NORM_INFO has precedence over the associated object
2191 content), reliable delivery of the NORM_INFO message and its payload,
2192 the FCAST Compound Object.
2193
2194 Authors' Addresses
2195
2196 Vincent Roca
2197 INRIA
2198 655, av. de l'Europe
2199 Inovallee; Montbonnot
2200 ST ISMIER cedex 38334
2201 France
2202
2203 EMail: [email protected]
2204 URI: <a href="http://planete.inrialpes.fr/people/roca/">http://planete.inrialpes.fr/people/roca/</a>
2205
2206
2207 Brian Adamson
2208 Naval Research Laboratory
2209 Washington, DC 20375
2210 USA
2211
2212 EMail: [email protected]
2213 URI: <a href="http://cs.itd.nrl.navy.mil">http://cs.itd.nrl.navy.mil</a>
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236 Roca &amp; Adamson Experimental [Page 40]
2237 </pre>