idnits 2.17.1
draft-hoschka-smilsdp-01.txt:
** The Abstract section seems to be numbered
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in
this document.
Expected boilerplate is as follows today (2024-04-20) according to
https://trustee.ietf.org/license-info :
IETF Trust Legal Provisions of 28-dec-2009, Section 6.a:
This Internet-Draft is submitted in full conformance with the provisions
of BCP 78 and BCP 79.
IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2:
Copyright (c) 2024 IETF Trust and the persons identified as the document
authors. All rights reserved.
IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3:
This document is subject to BCP 78 and the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the Simplified BSD License.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
** Missing expiration date. The document expiration date should appear on
the first and last page.
** The document seems to lack a 1id_guidelines paragraph about
Internet-Drafts being working documents.
** The document seems to lack a 1id_guidelines paragraph about 6 months
document validity.
** The document seems to lack a 1id_guidelines paragraph about the list of
current Internet-Drafts.
** The document seems to lack a 1id_guidelines paragraph about the list of
Shadow Directories.
== No 'Intended status' indicated for this document; assuming Proposed
Standard
== The page length should not exceed 58 lines per page, but there was 1
longer page, the longest (page 1) being 815 lines
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
** The document seems to lack an Introduction section.
** The document seems to lack a Security Considerations section.
** The document seems to lack an IANA Considerations section. (See Section
2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
when there are no actions for IANA.)
** There are 68 instances of too long lines in the document, the longest
one being 13 characters in excess of 72.
** The abstract seems to contain references ([47], [48]), which it
shouldn't. Please replace those with straight textual mentions of the
documents in question.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The "Author's Address" (or "Authors' Addresses") section title is
misspelled.
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (February 1, 1999) is 9210 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
-- Missing reference section? '2' on line 9 looks like a reference
-- Missing reference section? 'LINK' on line 9 looks like a reference
Summary: 12 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 INTERNET DRAFT
3 draft-hoschka-smilsdp-01.txt
4 August 30, 1998
5 Expires February 1, 1999
7 Integrating SDP Functionality Into SMIL
9 [2][LINK]
11 [3]Philipp Hoschka, [4]W3C
12 _________________________________________________________________
14 1. Status of this Memo
16 This document is an Internet Draft. Internet Drafts are working
17 documents of the Internet Engineering Task Force (IETF), its Areas,
18 and its Working Groups. Note that other groups may also distribute
19 working documents as Internet Drafts. Internet Drafts are valid for a
20 maximum of six months and may be updated, replaced, or obsoleted by
21 other documents at any time. It is inappropriate to use Internet
22 Drafts as reference material or to cite them other than as a "working
23 draft" or "work in progress." Distribution of this memo is unlimited.
25 This is an update of
26 [5]http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-00. It
27 fixes a bug in the example that was pointed out in feedback, and adds
28 pointers to the definitions of the SMIL elements used in the example.
29 The draft has been presented at the 42nd IETF meeting. The conclusion
30 was that this draft provides an interim solution at best. Future work
31 should focus less on keeping in line with the current SDP structure,
32 but rather integrate SDP functionality more directly into SMIL, while
33 reusing the values that have been registered for SDP. Consequently,
34 there are currently no plans for further work on this draft.
36 Table of Contents
38 * [6]1. Status of this Memo
39 * [7]2. Abstract
40 * [8]3. Example
41 * [9]3. Mapping Approach
42 * [10]4. Integrating SDP Fields into SMIL
43 + [11]4.1 Origin
44 o [12]4.1.1 origin Element
45 + [13]4.2 Session Name
46 o [14]Example
47 + [15]4.3 Session Info
48 o [16]4.3.1 info Element
49 o [17]4.3.2 Media level use
50 o [18]Example
51 + [19]4.4 URI
52 o [20]4.4.1 uri Element
53 + [21]4.5 Email Address
54 o [22]4.5.1 email Element
55 + [23]4.6 Phone
56 o [24]4.6.1 phone Element
57 + [25]4.7 Connection Data
58 o [26]Example
59 o [27]Example
60 o [28]Example
61 + [29]4.8 Bandwidth
62 o [30]4.8.1 bandwidth Element
63 + [31]4.9 Times
64 o [32]4.9.1 times Element
65 + [33]4.10 Repeat Time
66 o [34]4.10.1 repeat-time Element
67 + [35]4.11 Time Adjustement
68 o [36]4.11.1 time-adjustement Element
69 + [37]4.12 Encryption Keys
70 o [38]4.12.1 key Element
71 + [39]4.13 Attributes
72 o [40]4.13.1 attribute Element
73 + [41]4.14 Media Announcements
74 o [42]Example
75 o [43]4.14.1 rtpmap Element
76 + [44]4.15 Suggested Attributes
77 * [45]Acknowledgements
78 * [46]Authors Address
80 2. Abstract
82 This document describes an approach for integrating the functionality
83 currently contained in [47]SDP (Session Announcement Protocol) into
84 [48]SMIL (Synchronized Multimedia Integration Language). The
85 motivation is to make it easier for SMIL authors to interface with the
86 existing RTP/MBone infrastructure. Currently, this requires
87 maintaining two different sets of files, each of which use a different
88 text format. Another motivation is to save one network round-trip per
89 RTSP URL in the SMIL file, since the information contained in the SDP
90 file is now directly included in the SMIL file.
92 3. Example
94 The following shows how the sdp example contained in the SDP RFC can
95 be integrated into a SMIL file, using the mapping defined in this
96 document.
98 SDP announcement:
99 v=0
100 o=mhandley 2890844526 2890842807 IN IP4 126.16.64.4
101 s=SDP Seminar
102 i=A Seminar on the session description protocol
103 u=http://www.cs.ucl.ac.uk/staff/M.Handley/sdp.03.ps
104 e=mjh@isi.edu (Mark Handley)
105 c=IN IP4 224.2.17.12/127
106 t=2873397496 2873404696
107 a=recvonly
108 m=audio 49170 RTP/AVP 0
109 m=video 51372 RTP/AVP 31
110 m=application 32416 udp wb
111 a=orient:portrait
113 Inclusion in SMIL file:
114
117
118
122
123
124
125 A Seminar on the session description protocol
126
127
128 http://www.cs.ucl.ac.uk/staff/M.Handley/sdp.03.ps
129
130 ph@w3.org
131
132
133
134
136
138
140
141
142
143
144
146 This example uses the following SMIL elements:
147 * [49]meta
148 * [50]par
149 * [51]media object elements audio, video and ref
151 3. Mapping Approach
153 Only the information contained in a SDP session announcement is mapped
154 onto SMIL. An SDP session announcement consists of several fields.
155 These fields can either be session level fields, or media level
156 fields. In general, information contained in SDP session level fields
157 are mapped into information contained within the "head" part of a SMIL
158 document. Information contained in SDP media level fields is mapped
159 onto information assiocated with individual media objects in a SMIL
160 document.
162 The mapping below allows integrating all information in a SDP
163 announcement into SMIL.
165 SDP information is included in a SMIL document in two different ways:
166 * mapping SDP information into existing attributes, when possible
167 * defining a set of new XML elements and attributes that can be
168 included into a SMIL document via the [52]XML namespace mechanism
170 4. Integrating SDP Fields into SMIL
172 4.1 Origin
174 This SDP field requires defining a new element.
176 4.1.1 origin Element
178 This represents the information of the "orgin" field in SDP. It is
179 mandatory for a SMIL document that is transmitted in a multicast
180 announcement.
182 Element Attributes
184 username
185 Syntax and semantics defined in SDP specification. This is an
186 optional attribute, and the default value is "-".
188 session-id
189 Syntax and semantics defined in SDP specification
191 version
192 Syntax and semantics defined in SDP specification
194 network-type
195 Syntax and semantics defined in SDP specification. This is an
196 optional attribute, and the default value is "IN".
198 address-type
199 Syntax and semantics defined in SDP specification. This is an
200 optional attribute, and the default value is "IP4".
202 address
203 Syntax and semantics defined in SDP specification
205 Element Content
207 "origin" is an empty element.
209 Example
211
213
214
218 ...
219
220 ...
221
223 4.2 Session Name
225 This SDP field can be mapped onto the "title" property of the SMIL
226 "meta" element.
228 Example
230
231
232
233 ...
234
235 ...
236
238 4.3 Session Info
240 This SDP field can be used in the session-level section and in a
241 media-level section.
243 For mapping session-level use into SMIL, this requires defining a new
244 element.
246 4.3.1 info Element
248 Element Attributes
250 xml:lang
251 Syntax and semantics defined in XML specifiation
253 Element Content
255 "info" element contains the text of the session description.
257 Example
259
261
262
263 A Seminar on the session description protocol
264
265 ...
266
267 ...
268
270 4.3.2 Media level use
272 For media-level use, the "info" field can be mapped onto the "title"
273 attribute.
275 Example
277
278
279
280
281
283 4.4 URI
285 This SDP field requires defining a new element.
287 4.4.1 uri Element
289 The element can only occur within the "head" part of a SMIL document.
291 Element Attributes
293 This element has no attributes.
295 Element Content
297 The element contains the URI value.
299 Example
301
303
304 http://www.cs.ucl.ac.uk/staff/M.Handley/sdp.03.ps
305 ...
306
307 ...
308
310 4.5 Email Address
312 This SDP field requires defining a new element.
314 4.5.1 email Element
316 The element can only occur within the "head" part of a SMIL document.
318 Element Attributes
320 This element has no attributes.
322 Element Content
324 The element contains the email address
326 Example
328
330
331 ph@w3.org
332 ...
333
334 ...
335
337 4.6 Phone
339 This session-level SDP field requires defining a new element.
341 4.6.1 phone Element
343 The element can only occur within the "head" part of a SMIL document.
345 Element Attributes
347 This element has no attributes.
349 Element Content
351 The element contains the phone number.
353 Example
355
357
358 +1 617 256 8113
359 ...
360
361 ...
362
364 4.7 Connection Data
366 The information of this SDP field is contained in the URI identifying
367 the resource.
369 The network type can either be deduced from the URI scheme, or be
370 completely transparent.
372 Determining the address type is either not necessary (because the URI
373 contains a hostname), or it can be derived from the URI scheme.
375 For addressing resources that are multicast, a new "mbone" URI scheme
376 is needed. It looks as follows:
378 "mbone:""/""/"
380 @@ check whether consistent with guidelines for doing URIs
382 Example
384 mbone:224.2.1.1./127/3
386 This SDP field can be used in the session-level section and in a
387 media-level section.
389 For mapping session-level use of connection data into SMIL, a "meta"
390 element can be used for defining a base URI.
392 Example
394
395
396
397 ...
398
399 ...
400
402 For mapping media-level use into SMIL, the connection data field can
403 be mapped onto the "src" attribute of a media-object element.
405 Example
407
408
409
410
411
413 4.8 Bandwidth
415 This SDP field requires defining a new element.
417 4.8.1 bandwidth Element
419 Element Attributes
421 modifier
422 Syntax and semantics defined in SDP specifiation
424 bandwidth
425 Syntax and semantics defined in SDP specifiation
427 Element Content
429 "bandwidth" is an empty element.
431 The "bandwidth" SDP field can be used in the session-level section
432 and in a media-level section.
434 Use this field in the session-level section is mapped onto using the
435 "bandwidth" element in the "head" part of a SMIL document.
437 Example
439
441
442
443 ...
444
445 ...
446
448 Use of this field in the media-level section is mapped onto using the
449 "bandwitdh" element as content of a SMIL media object.
451 Example
453
455
456
459
460
462 4.9 Times
464 This session-level SDP field requires defining a new element.
466 4.9.1 times Element
468 The element can only occur within the "head" part of a SMIL document.
470 Element Attributes
472 start-time
473 Syntax and semantics defined in SDP specifiation
475 stop-time
476 Syntax and semantics defined in SDP specifiation
478 Element Content
480 The "times" element can contain the following element:
482 repeat-time
483 Defined below
485 zone-adjustement
486 Defined below
488 Example
490
492
493
494
495 ..
496
498 4.10 Repeat Time
500 This session-level SDP field requires defining a new element.
502 4.10.1 repeat-time Element
504 The element can only occur within the "head" part of a SMIL document
505 as content of a "time" element. The "time" element can contain not
506 more than one "repeat-time" element.
508 Element Attributes
510 interval
511 Syntax and semantics defined in SDP specifiation
513 active-duration
514 Syntax and semantics defined in SDP specifiation
516 offsets
517 A comma seperated list of values whose semantics is defined in
518 the SDP specification
520 Element Content
522 "repeat-times" is an empty element.
524 Example
526
528
529
530
532
533
534 ...
535
537 4.11 Time Adjustement
539 This session-level SDP field requires defining a new element.
541 4.11.1 time-adjustement Element
543 The element can only occur within the "head" part of a SMIL document
544 as content of a "time" element. The "time" element can contain
545 multiple "time-adjustement" elements, one for each adjustement (note
546 that this leads to a different structure than used by the "z" field in
547 sdp).
549 Element Attributes
551 adjustement-time
552 Syntax and semantics defined in SDP specifiation
554 offset
555 Syntax and semantics defined in SDP specifiation
557 Element Content
559 "time-adjustement" is an empty element.
561 Example
563
565
566
567
569
570
571
572
573 ...
574
576 4.12 Encryption Keys
578 This SDP field can be used both at the session-level and at the media
579 level. It requires defining a new element.
581 4.12.1 key Element
583 Element Attributes
585 method
586 Syntax and semantics defined in SDP specifiation
588 encryption-key
589 Syntax and semantics defined in SDP specifiation
591 Element Content
593 "key" is an empty element.
595 To mimic SDP use of encryption keys at the session-level, the "keys"
596 element is included in the "head" part of the SMIL document.
598 Example
600
602
603
604
605 ...
606
608 To mimic SDP-use of encryption keys at the media-level, the "keys"
609 element is included in the content of a SMIL media object element.
611 Example
613
615
616
619
620
622 4.13 Attributes
624 Unless specified otherwise, SDP attributes are mapped onto a generic
625 "attribute" element.
627 4.13.1 attribute Element
629 Element Attributes
631 attribute-name
632 Syntax and semantics defined in SDP specifiation
634 value
635 Syntax and semantics defined in SDP specifiation
637 Element Content
639 "attribute" is an empty element
641 If the attribute is used on the session-level, it is contained in the
642 "head" section of the SMIL document.
644 Example
646
648
649
651
652 ...
653
655 Otherwise, it is included in the content of a SMIL media-object
656 element.
658 Example
660
662
663
666
667
669 4.14 Media Announcements
671 The "m" SDP field is mapped onto attributes within SMIL media objects.
673 The following attributes can be added to all SMIL media objects:
675 port
676 Syntax and semantics defined in SDP specifiation
678 transport
679 Syntax and semantics defined in SDP specifiation
681 fmt-list
682 Comma-seperated list of values whose syntax and semantics is
683 defined in SDP specifiation
685 Example
687
689
690
693
694
696 If the media object uses the RTP format, and uses a dynamic payload
697 type, SDP requires the use of the "rtpmap" attribute field. This is
698 mapped onto the "rtpmap" element, which is contained in the content of
699 the media object element.
701 4.14.1 rtpmap Element
703 Element Attributes
705 payload
706 Syntax and semantics defined in SDP specifiation
708 encoding
709 Syntax and semantics defined in SDP specifiation
711 Element Content
713 "rtpmap" is an empty element
715 Example
717
719
720
726
727
729 4.15 Suggested Attributes
731 The following "suggested attributes" of SDP are not mapped onto an
732 "attribute" element:
733 * charset: The charset of the SMIL document can be set using the
734 mechanisms defined by the XML definition.
735 * sdplang: The language of session-description information is set by
736 the "xml:lang" attribute in the individual "info" elements.
737 @@@ check XML spec: is there a way to set a global default
738 language that is valid for the whole document ?
739 * lang: The functionality of this is replaced by the
740 "system-language" attribute in SMIL.
742 All other "suggested attributes" are mapped onto an "attribute"
743 element.
745 Acknowledgements
747 Integrating SDP functionality with SMIL has been originally suggested
748 by several other people to me in private.
750 Authors Address
752 * Philipp Hoschka
753 W3C/MIT Laboratory for Computer Science
754 545 Technology Square
755 Cambridge, MA 02139, USA
756 Fax: +1 (617) 258-8682
757 Email: ph@w3.org
758 _________________________________________________________________
760 References
762 1. http://www.w3.org/
763 2. http://www.w3.org/Style/CSS/Buttons
764 3. mailto:ph@w3.org
765 4. http://www.w3.org/
766 5. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-00
767 6. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid58150
768 7. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid58151
769 8. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid58152
770 9. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid58153
771 10. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid58154
772 11. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid58155
773 12. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid58156
774 13. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581510
775 14. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581511
776 15. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581512
777 16. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581513
778 17. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581517
779 18. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581518
780 19. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581519
781 20. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581520
782 21. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581524
783 22. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581525
784 23. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581529
785 24. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581530
786 25. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581534
787 26. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581535
788 27. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581536
789 28. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581537
790 29. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581538
791 30. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581539
792 31. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581544
793 32. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581545
794 33. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581549
795 34. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581550
796 35. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581554
797 36. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581555
798 37. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581559
799 38. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581560
800 39. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581565
801 40. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581566
802 41. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581571
803 42. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581572
804 43. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581573
805 44. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581577
806 45. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581578
807 46. http://www.w3.org/AudioVideo/1998/08/draft-hoschka-smilsdp-01.html#xtocid581579
808 47. http://info.internet.isi.edu/in-notes/rfc/files/rfc2327.txt
809 48. http://www.w3.org/TR/REC-smil
810 49. http://www.w3.org/TR/REC-smil/#meta
811 50. http://www.w3.org/TR/REC-smil/#par
812 51. http://www.w3.org/TR/REC-smil/#media-object
813 52. http://www.w3.org/TR/WD-xml-names