draft-ietf-mmusic-img-framework-03.txt   draft-ietf-mmusic-img-framework-04.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Internet Engineering Task Force MMUSIC WG Internet Engineering Task Force MMUSIC WG
Internet Draft Y. Nomura Internet Draft Y. Nomura
Fujitsu Labs. Fujitsu Labs.
R. Walsh R. Walsh
J-P. Luoma J-P. Luoma
Nokia Nokia
H. Asaeda H. Asaeda
INRIA INRIA
H. Schulzrinne H. Schulzrinne
Columbia University Columbia University
draft-ietf-mmusic-img-framework-03.txt draft-ietf-mmusic-img-framework-04.txt
February 16, 2003 April 13, 2004
Expires: July 2004 Expires: October 2004
A Framework for the Usage of Internet Media Guides A Framework for the Usage of Internet Media Guides
STATUS OF THIS MEMO STATUS OF THIS MEMO
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 22 skipping to change at page 2, line 22
3.1.2 Delta IMG Description ............................... 6 3.1.2 Delta IMG Description ............................... 6
3.1.3 IMG Pointer ......................................... 6 3.1.3 IMG Pointer ......................................... 6
3.2 Operation Set for IMG Delivery ...................... 6 3.2 Operation Set for IMG Delivery ...................... 6
3.2.1 IMG ANNOUNCE ........................................ 6 3.2.1 IMG ANNOUNCE ........................................ 6
3.2.2 IMG QUERY ........................................... 7 3.2.2 IMG QUERY ........................................... 7
3.2.3 IMG RESOLVE ......................................... 7 3.2.3 IMG RESOLVE ......................................... 7
3.2.4 IMG SUBSCRIBE ....................................... 7 3.2.4 IMG SUBSCRIBE ....................................... 7
3.2.5 IMG NOTIFY .......................................... 8 3.2.5 IMG NOTIFY .......................................... 8
3.2.6 Binding Between IMG Operations and Data Types ....... 8 3.2.6 Binding Between IMG Operations and Data Types ....... 8
3.3 IMG Entities ........................................ 9 3.3 IMG Entities ........................................ 9
3.4 Overview of Protocol Operations ..................... 10 3.4 Overview of Protocol Operations ..................... 9
4 Deployment Scenarios for IMG Entities ............... 10 4 Deployment Scenarios for IMG Entities ............... 10
4.1 Intermediary Cases .................................. 10 4.1 Intermediary Cases .................................. 10
4.2 One-to-many Unidirectional Multicast ................ 12 4.2 One-to-many Unidirectional Multicast ................ 12
4.3 One-to-one Bi-directional Unicast ................... 13 4.3 One-to-one Bi-directional Unicast ................... 13
4.4 Combined Operations with Common Metadata ............ 13 4.4 Combined Operations with Common Metadata ............ 13
5 Applicability of Existing Protocols to the 5 Applicability of Existing Protocols to the
Proposed Framework Model ....................................... 13 Proposed Framework Model ....................................... 13
5.1 Existing Protocol Fit to the IMG Framework Model 5.1 Existing Protocol Fit to the IMG Framework Model
5.2 Outstanding IMG Mechanism Needs ..................... 16 5.2 Outstanding IMG Mechanism Needs ..................... 16
5.2.1 A Multicast Transport Protocol ...................... 16 5.2.1 A Multicast Transport Protocol ...................... 16
5.2.2 Usage of Unicast Transport Protocols ................ 17 5.2.2 Usage of Unicast Transport Protocols ................ 17
5.2.3 IMG Transfer Envelope ............................... 17 5.2.3 IMG Transfer Envelope ............................... 17
5.2.4 Baseline (Meta)Data Model Specification ............. 18 5.2.4 Baseline (Meta)Data Model Specification ............. 18
5.3 IMG Needs Fitting the IETF's Scope .................. 18 5.3 IMG Needs Fitting the IETF's Scope .................. 18
6 Security Considerations ............................. 19 6 Security Considerations ............................. 19
7 IANA Considerations ................................. 21 7 IANA Considerations ................................. 21
8 Normative References ................................ 21 8 References .......................................... 21
9 Informative References .............................. 21 9 Acknowledgements .................................... 21
10 Acknowledgements .................................... 22 10 Authors' Addresses .................................. 22
11 Authors' Addresses .................................. 22 11 Full Copyright Statement ............................ 22
1 Introduction 1 Introduction
Internet Media Guides (IMGs) provide and deliver structured Internet Media Guides (IMGs) provide and deliver structured
collections of multimedia descriptions expressed using SDP, SDPng or collections of multimedia descriptions expressed using SDP, SDPng or
some similar description format. They are used to describe sets of some similar description format. They are used to describe sets of
multimedia sessions (e.g. television program schedules, content multimedia sessions (e.g. television program schedules, content
delivery schedules etc.) and refer to other networked resources delivery schedules etc.) and refer to other networked resources
including web pages. IMGs provide an envelope for metadata formats including web pages. IMGs provide an envelope for metadata formats
and session descriptions defined elsewhere with the aim of and session descriptions defined elsewhere with the aim of
skipping to change at page 21, line 11 skipping to change at page 21, line 11
channel and protocol. For example, a secure unicast channel can be channel and protocol. For example, a secure unicast channel can be
used to deliver the keys and initialization vectors for an encryption used to deliver the keys and initialization vectors for an encryption
algorithm used on a multicast channel. The exploitation of this algorithm used on a multicast channel. The exploitation of this
opportunity is specific to the protocols used and is outside the opportunity is specific to the protocols used and is outside the
scope of this document. scope of this document.
7 IANA Considerations 7 IANA Considerations
There are no IANA considerations within this document. There are no IANA considerations within this document.
8 Normative References 8 References
[1] Y. Nomura, R. Walsh, J-P. Luoma, J. Ott, and H. Schulzrinne, [1] Y. Nomura, R. Walsh, J-P. Luoma, J. Ott, and H. Schulzrinne,
"Protocol requirements for Internet media guides," Internet Draft "Protocol requirements for Internet media guides," Internet Draft
draft-ietf-mmusic-img-req-03, Internet Engineering Task Force, Feb. draft-ietf-mmusic-img-req-04, Internet Engineering Task Force, April
2004. Work in progress. 2004. Work in progress.
[2] S. Bradner, "Key words for use in RFCs to indicate requirement [2] S. Bradner, "Key words for use in RFCs to indicate requirement
levels," RFC 2119, Internet Engineering Task Force, Mar. 1997. levels," RFC 2119, Internet Engineering Task Force, Mar. 1997.
9 Informative References
[3] TV-Anytime Forum, "Broadcast and On-line Services: Search, [3] TV-Anytime Forum, "Broadcast and On-line Services: Search,
select, and rightful use of content on personal storage systems select, and rightful use of content on personal storage systems
("TV-Anytime Phase 1"); Part 2: System description," ETSI-TS 102 ("TV-Anytime Phase 1"); Part 2: System description," ETSI-TS 102
822-2: System Description, V1.1.1, October 2003. 822-2: System Description, V1.1.1, October 2003.
[4] A. B. Roach, "Session initiation protocol (sip)-specific event [4] A. B. Roach, "Session initiation protocol (sip)-specific event
notification," RFC 3265, Internet Engineering Task Force, June 2002. notification," RFC 3265, Internet Engineering Task Force, June 2002.
[5] M. Luby, J. Gemmell, L. Vicisano, L. Rizzo, and J. Crowcroft, [5] M. Luby, J. Gemmell, L. Vicisano, L. Rizzo, and J. Crowcroft,
"Asynchronous layered coding (ALC) protocol instantiation," RFC 3450, "Asynchronous layered coding (ALC) protocol instantiation," RFC 3450,
Internet Engineering Task Force, Dec. 2002. Internet Engineering Task Force, Dec. 2002.
[6] T. Paila, M. Luby, R. Lehtonen, V. Roca, and R. Walsh, "FLUTE - [6] T. Paila, M. Luby, R. Lehtonen, V. Roca, R. Walsh, "FLUTE - file
file delivery over unidirectional transport," Internet Draft draft- delivery over unidirectional transport," Internet Draft draft-ietf-
ietf-rmt-flute-07, Internet Engineering Task Force, Dec. 2003. rmt-flute-07, Internet Engineering Task Force, Dec. 2003. Work in
Work in progress. progress.
[7] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. R. Johnston, J. [7] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. R. Johnston, J.
Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: session Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: session
initiation protocol," RFC 3261, Internet Engineering Task Force, June initiation protocol," RFC 3261, Internet Engineering Task Force, June
2002. 2002.
[8] R. Fielding, J. Gettys, J. C. Mogul, H. Frystyk, and T. Berners- [8] R. Fielding, J. Gettys, J. C. Mogul, H. Frystyk, and T. Berners-
Lee, "Hypertext transfer protocol -- HTTP/1.1," RFC 2068, Internet Lee, "Hypertext transfer protocol -- HTTP/1.1," RFC 2068, Internet
Engineering Task Force, Jan. 1997. Engineering Task Force, Jan. 1997.
[9] H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson, "RTP: a [9] H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson, "RTP: a
transport protocol for real-time applications," RFC 3550, Internet transport protocol for real-time applications," RFC 3550, Internet
Engineering Task Force, July 2003. Engineering Task Force, July 2003.
10 Acknowledgements 9 Acknowledgements
The authors would like to thank Joerg Ott, Colin Perkins, Toni Paila The authors would like to thank Joerg Ott, Colin Perkins, Toni Paila
and Petri Koskelainen on for their ideas and input to this document. and Petri Koskelainen on for their ideas and input to this document.
11 Authors' Addresses 10 Authors' Addresses
Yuji Nomura Yuji Nomura
Fujitsu Laboratories Ltd. Fujitsu Laboratories Ltd.
4-1-1 Kamikodanaka, Nakahara-ku, Kawasaki 211-8588 4-1-1 Kamikodanaka, Nakahara-ku, Kawasaki 211-8588
Japan Japan
Email: nom@flab.fujitsu.co.jp Email: nom@flab.fujitsu.co.jp
Rod Walsh Rod Walsh
Nokia Corporation Nokia Corporation
Nokia Research Center Nokia Research Center
skipping to change at page 23, line 8 skipping to change at page 22, line 45
Email: Hitoshi.Asaeda@sophia.inria.fr Email: Hitoshi.Asaeda@sophia.inria.fr
Henning Schulzrinne Henning Schulzrinne
Dept. of Computer Science Dept. of Computer Science
Columbia University Columbia University
1214 Amsterdam Avenue 1214 Amsterdam Avenue
New York, NY 10027 New York, NY 10027
USA USA
Email: schulzrinne@cs.columbia.edu Email: schulzrinne@cs.columbia.edu
The IETF takes no position regarding the validity or scope of any 11 Full Copyright Statement
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat. The IETF invites any
interested party to bring to its attention any copyrights, patents or
patent applications, or other proprietary rights which may cover
technology that may be required to practice this standard. Please
address the information to the IETF Executive Director.
Full Copyright Statement Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights.
Copyright (c) The Internet Society (2004). All Rights Reserved. This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
This document and translations of it may be copied and furnished to Intellectual Property
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 The IETF takes no position regarding the validity or scope of any
revoked by the Internet Society or its successors or assigns. Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
This document and the information contained herein is provided on an Copies of IPR disclosures made to the IETF Secretariat and any
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING assurances of licenses to be made available, or the result of an
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING attempt made to obtain a general license or permission for the use of
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION such proprietary rights by implementers or users of this
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF specification can be obtained from the IETF on-line IPR repository at
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/