File: rfc3009.txt

package info (click to toggle)
doc-rfc 20181229-2
  • links: PTS, VCS
  • area: non-free
  • in suites: buster
  • size: 570,944 kB
  • sloc: xml: 285,646; sh: 107; python: 90; perl: 42; makefile: 14
file content (563 lines) | stat: -rw-r--r-- 16,022 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563






Network Working Group                                       J. Rosenberg
Request for Comments: 3009                                   dynamicsoft
Category: Standards Track                                 H. Schulzrinne
                                                             Columbia U.
                                                           November 2000


                  Registration of parityfec MIME types

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

Abstract

   The RTP (Real-time Transport Protocol) payload format for generic
   forward error correction allows RTP participants to improve loss
   resiliency through the use of traditional parity-based channel codes.
   This payload format requires four new MIME types, audio/parityfec,
   video/parityfec, text/parityfec and application/parityfec.  This
   document serves as the MIME type registration for those formats.

1 Introduction

   The RTP payload format for generic forward error correction [1]
   allows RTP participants to improve loss resiliency through the use of
   traditional parity-based channel codes.  This payload format requires
   four new MIME types, audio/parityfec, video/parityfec,
   text/paritfyfec and application/parityfec.  RFC 2048 [2] defines
   procedures for registration of new MIME types within the IETF tree.
   Furthermore, the Audio/Video Transport working group has defined
   additional procedures that must be followed when registering RTP
   payload formats [3].  This document serves as the MIME type
   registration for those formats based on those procedures.









Rosenberg & Schulzrinne     Standards Track                     [Page 1]

RFC 3009                        FEC MIME                   November 2000


2 Registration of audio/parityfec

       To: ietf-types@iana.org

       Subject: Registration of MIME media type audio/parityfec

       MIME media type name: audio

       MIME subtype name: parityfec

       Required parameters: none

            Note that [3] mandates that RTP payload formats without a
            defined rate must define a rate parameter as part of their
            MIME registration.  The payload format for generic forward
            error correction [1] does not specify a rate parameter.
            However, the rate for FEC data is equal to the rate of the
            media data it protects.

       Optional parameters: none

            Typical optional parameters [3], such as the number of
            channels, and the duration of audio per packet, do not
            apply to FEC data.  The number of channels is effectively
            the same as the media data it protects; the same is true
            for the duration of audio per packet.

       Encoding considerations: This format is only defined for
            transport within the Real Time Transport protocol (RTP)
            [4,5].  Its transport within RTP is fully specified with RFC
            2733 [1].

       Security considerations: the same security considerations
            apply to these mime registrations as to the payloads for
            for them, as detailed in RFC 2733.

       Interoperability considerations: none

       Published specification: This MIME type is described fully
            within RFC 2733 [1].

       Applications which use this media type: Audio and video
            streaming tools which seek to improve resiliency to loss by
            sending additional data with the media stream.

       Additional information: none





Rosenberg & Schulzrinne     Standards Track                     [Page 2]

RFC 3009                        FEC MIME                   November 2000


       Person & email address to contact for further information:

            Jonathan Rosenberg
            dynamicsoft
            72 Eagle Rock Avenue
            First Floor
            East Hanover, NJ 07936
            email: jdrosen@dynamicsoft.com
                   jdrosen@alum.mit.edu

       Intended usage: COMMON

       Author/Change controller: This registration is part of the IETF
            registration tree.

       RTP and SDP Issues: Usage of this format within RTP and the
            Session Description Protocol (SDP) [6] are fully specified
            within RFC 2733 [1].

3 Registration of video/parityfec

       To: ietf-types@iana.org

       Subject: Registration of MIME media type video/parityfec

       MIME media type name: video

       MIME subtype name: parityfec

       Required parameters: none

            Note that [3] mandates that RTP payload formats without a
            defined rate must define a rate parameter as part of their
            MIME registration.  The payload format for generic forward
            error correction [1] does not specify a rate parameter.
            However, the rate for FEC data is equal to the rate of the
            media data it protects.

       Optional parameters: none

            Typical optional parameters [3], such as the number of
            channels, and the duration of audio per packet, do not
            apply to FEC data.  The number of channels is effectively
            the same as the media data it protects; the same is true
            for the duration of video per packet.






Rosenberg & Schulzrinne     Standards Track                     [Page 3]

RFC 3009                        FEC MIME                   November 2000


       Encoding considerations: This format is only defined for
            transport within the Real Time Transport protocol (RTP)
            [4,5].  Its transport within RTP is fully specified with RFC
            2733 [1].

       Security considerations: the same security considerations
            apply to these MIME registrations as to the payloads for
            for them, as detailed in RFC 2733.

       Interoperability considerations: none

       Published specification: This MIME type is described fully
            within RFC 2733 [1].

       Applications which use this media type: Audio and video
            streaming tools which seek to improve resiliency to loss by
            sending additional data with the media stream.

       Additional information: none

       Person & email address to contact for further information:

            Jonathan Rosenberg
            dynamicsoft
            72 Eagle Rock Avenue
            First Floor
            East Hanover, NJ 07936
            email: jdrosen@dynamicsoft.com
                   jdrosen@alum.mit.edu

       Intended usage: COMMON

       Author/Change controller: This registration is part of the IETF
            registration tree.

       RTP and SDP Issues: Usage of this format within RTP and the
            Session Description Protocol (SDP) [6] are fully specified
            within RFC 2733 [1].

4 Registration of text/parityfec

       To: ietf-types@iana.org

       Subject: Registration of MIME media type text/parityfec

       MIME media type name: text

       MIME subtype name: parityfec



Rosenberg & Schulzrinne     Standards Track                     [Page 4]

RFC 3009                        FEC MIME                   November 2000


       Required parameters: none

            Note that [3] mandates that RTP payload formats without a
            defined rate must define a rate parameter as part of their
            MIME registration.  The payload format for generic forward
            error correction [1] does not specify a rate parameter.
            However, the rate for FEC data is equal to the rate of the
            media data it protects.

       Optional parameters: none

            Typical optional parameters [3], such as the number of
            channels, and the duration of audio per packet, do not
            apply to FEC data.  The number of channels is effectively
            the same as the media data it protects; the same is true
            for the duration of text per packet.

       Encoding considerations: This format is only defined for
            transport within the Real Time Transport protocol (RTP)
            [4,5].  Its transport within RTP is fully specified with RFC
            2733 [1].

       Security considerations: the same security considerations
            apply to these MIME registrations as to the payloads for
            for them, as detailed in RFC 2733.

       Interoperability considerations: none

       Published specification: This MIME type is described fully
            within RFC 2733 [1].

       Applications which use this media type: Audio, video and text
            streaming tools which seek to improve resiliency to loss by
            sending additional data with the media stream.

       Additional information: none

       Person & email address to contact for further information:

            Jonathan Rosenberg
            dynamicsoft
            72 Eagle Rock Avenue
            First Floor
            East Hanover, NJ 07936
            email: jdrosen@dynamicsoft.com
                   jdrosen@alum.mit.edu

       Intended usage: COMMON



Rosenberg & Schulzrinne     Standards Track                     [Page 5]

RFC 3009                        FEC MIME                   November 2000


       Author/Change controller: This registration is part of the IETF
            registration tree.

       RTP and SDP Issues: Usage of this format within RTP and the
            Session Description Protocol (SDP) [6] are fully specified
            within RFC 2733 [1].

5 Registration of application/parityfec

        To: ietf-types@iana.org

        Subject: Registration of MIME media type application/parityfec

        MIME media type name: application

        MIME subtype name: parityfec

        Required parameters: none

             Note that [3] mandates that RTP payload formats without a
             defined rate must define a rate parameter as part of their
             MIME registration.  The payload format for generic forward
             error correction [1] does not specify a rate parameter.
             However, the rate for FEC data is equal to the rate of the
             media data it protects.

        Optional parameters: none

             Typical optional parameters [3], such as the number of
             channels, and the duration of audio per packet, do not
             apply to FEC data.  The number of channels is effectively
             the same as the media data it protects; the same is true
             for the duration of application data per packet.

        Encoding considerations: This format is only defined for
             transport within the Real Time Transport protocol (RTP)
             [4,5].  Its transport within RTP is fully specified with RFC
             2733 [1].

       Security considerations: the same security considerations
            apply to these MIME registrations as to the payloads for
            for them, as detailed in RFC 2733.

        Interoperability considerations: none

        Published specification: This MIME type is described fully
             within RFC 2733 [1].




Rosenberg & Schulzrinne     Standards Track                     [Page 6]

RFC 3009                        FEC MIME                   November 2000


        Applications which use this media type: Audio, video and
             application streaming tools which seek to improve
             resiliency to loss by sending additional data with the
             media stream.

        Additional information: none

        Person & email address to contact for further information:

             Jonathan Rosenberg
             dynamicsoft
             72 Eagle Rock Avenue
             First Floor
             East Hanover, NJ 07936
             email: jdrosen@dynamicsoft.com
                    jdrosen@alum.mit.edu

        Intended usage: COMMON

        Author/Change controller: This registration is part of the IETF
             registration tree.

        RTP and SDP Issues: Usage of this format within RTP and the
             Session Description Protocol (SDP) [6] are fully specified
             within RFC 2733 [1].

6 Security Considerations

   This MIME registration does not introduce any additional security
   considerations.





















Rosenberg & Schulzrinne     Standards Track                     [Page 7]

RFC 3009                        FEC MIME                   November 2000


7 Authors' Addresses

   Jonathan Rosenberg
   dynamicsoft
   72 Eagle Rock Avenue
   First Floor
   East Hanover, NJ 07936

   EMail: jdrosen@dynamicsoft.com


   Henning Schulzrinne
   Columbia University
   M/S 0401
   1214 Amsterdam Ave.
   New York, NY 10027-7003

   EMail: schulzrinne@cs.columbia.edu

































Rosenberg & Schulzrinne     Standards Track                     [Page 8]

RFC 3009                        FEC MIME                   November 2000


8 Bibliography

   [1] Rosenberg, J. and H. Schulzrinne, "An RTP Payload Format for
       Generic Forward Error Correction", RFC 2733, December 1999.

   [2] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet Mail
       Extensions (MIME) Part Four: Registration Procedures", RFC 2048,
       November 1996.

   [3] Casner, S. and P. Hoschka, "MIME type registration of RTP payload
       formats", Work in Progress.

   [4] Schulzrinne, H., Casner, S., Frederick, R.  and V. Jacobson,
       "RTP: a transport protocol for real-time applications", RFC 1889,
       January 1996.

   [5] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
       a transport protocol for real-time applications", Work in
       Progress.

   [6] Handley, M. and V. Jacobson, "SDP: Session Description Protocol",
       RFC 2327, April 1998.





























Rosenberg & Schulzrinne     Standards Track                     [Page 9]

RFC 3009                        FEC MIME                   November 2000


9  Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Rosenberg & Schulzrinne     Standards Track                    [Page 10]