Private:pCDN:DRM - Revision history

Amala at 21:28, 12 May 2008

2008-05-12T21:28:22Z

Amala at 17:49, 6 May 2008

2008-05-06T17:49:33Z

Amala at 17:47, 6 May 2008

2008-05-06T17:47:03Z

Amala at 17:35, 6 May 2008

2008-05-06T17:35:21Z

Amala at 17:17, 6 May 2008

2008-05-06T17:17:10Z

Amala at 17:16, 6 May 2008

2008-05-06T17:16:00Z

Amala at 17:12, 6 May 2008

2008-05-06T17:12:43Z

Amala at 20:25, 2 May 2008

2008-05-02T20:25:10Z

Amala at 20:24, 2 May 2008

2008-05-02T20:24:12Z

Amala at 16:51, 2 May 2008

2008-05-02T16:51:26Z

@@ Line 40: / Line 40: @@
 * [DRMT]Digital Rights Management Technological, Economic, Legal and Political Aspects Series: Lecture Notes in Computer Science , Vol. 2770 Becker, E.; Buhse, W.; Günnewig, D.; Rump, N. (Eds.):http://www.springerlink.com/content/kg0ug43g9df1/
 * [BM07]B. Jules and M. Hefeeda, pCDN: Peer-assisted Content Distribution Network, CBC/Radio-Canada Technology Review Magazine, Issue 4, pp. 1--14, July 2007
-*The Present and Future of Digital Rights Managment: http://www.jura.uni-tuebingen.de/bechtold/pub/2003/Future_DRM.pdf
+* Multimedia Encryption and Authentication Techniques and Applications, by Borko Furht and Darko Kirovski Auerbach Publications © 2006 (395 pages) ISBN:9780849372124
 * Workshop on Digital Rights Management for the Web World Wide Web Consortium: http://www.w3.org/2000/12/drm-ws/Overview.html
 * Digital Rights Management (DRM) Architectures: http://www.dlib.org/dlib/june01/iannella/06iannella.html

@@ Line 43: / Line 43: @@
 * Workshop on Digital Rights Management for the Web World Wide Web Consortium: http://www.w3.org/2000/12/drm-ws/Overview.html
 * Digital Rights Management (DRM) Architectures: http://www.dlib.org/dlib/june01/iannella/06iannella.html
 == Software Requirements ==

← Older revision		Revision as of 17:47, 6 May 2008
Line 43:		Line 43:
	* Workshop on Digital Rights Management for the Web World Wide Web Consortium: http://www.w3.org/2000/12/drm-ws/Overview.html		* Workshop on Digital Rights Management for the Web World Wide Web Consortium: http://www.w3.org/2000/12/drm-ws/Overview.html
	* Digital Rights Management (DRM) Architectures: http://www.dlib.org/dlib/june01/iannella/06iannella.html		* Digital Rights Management (DRM) Architectures: http://www.dlib.org/dlib/june01/iannella/06iannella.html
		+
		+
		+	== Software Requirements ==
		+
		+	* Windows 2003 server operating system.
		+	* Windows Media Format 11 SDK.
		+	* Windows Media Rights Manager 10.1 SDK.
		+	* Windows Media Encoder.

@@ Line 38: / Line 38: @@
 * DRM at Microsoft : http://www.microsoft.com/windows/windowsmedia/forpros/drm/default.mspx
-* [DRMT]Digital Rights Management Technological, Economic, Legal and Political Aspects Series: Lecture Notes in Computer Science , Vol. 2770 Becker, E.; Buhse, W.; Günnewig, D.; Rump, N. (Eds.)
+* [DRMT]Digital Rights Management Technological, Economic, Legal and Political Aspects Series: Lecture Notes in Computer Science , Vol. 2770 Becker, E.; Buhse, W.; Günnewig, D.; Rump, N. (Eds.):http://www.springerlink.com/content/kg0ug43g9df1/
 * [BM07]B. Jules and M. Hefeeda, pCDN: Peer-assisted Content Distribution Network, CBC/Radio-Canada Technology Review Magazine, Issue 4, pp. 1--14, July 2007
 *The Present and Future of Digital Rights Managment: http://www.jura.uni-tuebingen.de/bechtold/pub/2003/Future_DRM.pdf
 * Workshop on Digital Rights Management for the Web World Wide Web Consortium: http://www.w3.org/2000/12/drm-ws/Overview.html
 * Digital Rights Management (DRM) Architectures: http://www.dlib.org/dlib/june01/iannella/06iannella.html

@@ Line 38: / Line 38: @@
 * DRM at Microsoft : http://www.microsoft.com/windows/windowsmedia/forpros/drm/default.mspx
 * [DRMT]Digital Rights Management Technological, Economic, Legal and Political Aspects Series: Lecture Notes in Computer Science , Vol. 2770 Becker, E.; Buhse, W.; Günnewig, D.; Rump, N. (Eds.)
 * [BM07]B. Jules and M. Hefeeda, pCDN: Peer-assisted Content Distribution Network, CBC/Radio-Canada Technology Review Magazine, Issue 4, pp. 1--14, July 2007
 *The Present and Future of Digital Rights Managment: http://www.jura.uni-tuebingen.de/bechtold/pub/2003/Future_DRM.pdf
-* Workshop on Digital Rights Management for the Web
+* Workshop on Digital Rights Management for the Web World Wide Web Consortium: http://www.w3.org/2000/12/drm-ws/Overview.html
 * Digital Rights Management (DRM) Architectures: http://www.dlib.org/dlib/june01/iannella/06iannella.html

← Older revision		Revision as of 17:16, 6 May 2008
Line 44:		Line 44:

	*The Present and Future of Digital Rights Managment: http://www.jura.uni-tuebingen.de/bechtold/pub/2003/Future_DRM.pdf		*The Present and Future of Digital Rights Managment: http://www.jura.uni-tuebingen.de/bechtold/pub/2003/Future_DRM.pdf
		+	* Workshop on Digital Rights Management for the Web
		+	World Wide Web Consortium: http://www.w3.org/2000/12/drm-ws/Overview.html
		+	* Digital Rights Management (DRM) Architectures: http://www.dlib.org/dlib/june01/iannella/06iannella.html

← Older revision		Revision as of 17:12, 6 May 2008
Line 42:		Line 42:

	* [BM07]B. Jules and M. Hefeeda, pCDN: Peer-assisted Content Distribution Network, CBC/Radio-Canada Technology Review Magazine, Issue 4, pp. 1--14, July 2007		* [BM07]B. Jules and M. Hefeeda, pCDN: Peer-assisted Content Distribution Network, CBC/Radio-Canada Technology Review Magazine, Issue 4, pp. 1--14, July 2007
		+
		+	*The Present and Future of Digital Rights Managment: http://www.jura.uni-tuebingen.de/bechtold/pub/2003/Future_DRM.pdf

@@ Line 18: / Line 18: @@
 From the definition of the DRM systems, we know DRM systems have to cover a variety of tasks. There are some elements exist to fulfil these tasks [DRMT].
-.	Secure containers: for the users who do not have rights to access the content, the content will be inaccessible. The content, access conditions as well as the license server URL (the server that has the exchange keys) can be seen as putting them in a locked container. This locked container will transmit to the client and unpacked based on the information rules inside it.
+.	''Secure containers:'' for the users who do not have rights to access the content, the content will be inaccessible. The content, access conditions as well as the license server URL (the server that has the exchange keys) can be seen as putting them in a locked container. This locked container will transmit to the client and unpacked based on the information rules inside it.
-.	Rights expressions: express who is permitted to access the content wrapped in secure containers.
+.	''Rights expressions:'' express who is permitted to access the content wrapped in secure containers.
-.	Content identification and description systems: identify the content and join metadata description with the content.
+.	''Content identification and description systems:'' identify the content and join metadata description with the content.
-.	Identification of people: identifies the consumers who intend to interact with the content.
+.	''Identification of people:'' identifies the consumers who intend to interact with the content.
-.	Authentication of people: authenticates the people who want to interact with the content.
+.	''Authentication of people:'' authenticates the people who want to interact with the content.
-.	Watermarking and Fingerprinting: join identifiers and other information with the content. Hence both of them are used to prove that a violation has happened.
+.	''Watermarking and Fingerprinting:'' join identifiers and other information with the content. Hence both of them are used to prove that a violation has happened.
-.	Report events: a mechanism is used to report any events such as a purchase of content. It allows the event that is based on payments to work.
+.	''Report events:'' a mechanism is used to report any events such as a purchase of content. It allows the event that is based on payments to work.
-.	Payment systems: these systems which are enabled through event reporting systems need to be coordinated into the system.
+.	''Payment systems:'' these systems which are enabled through event reporting systems need to be coordinated into the system.
 The above elements need to be attached together.  When these elements are attached, participants in the DRM content (from the owner through several service providers to the end user) trust system to do what they expect it to do.

@@ Line 1: / Line 1: @@
-'''Digital Rights Management in pCDN'''
+'''pCDN and DRM overview'''
 To distribute multimedia objects over the Internet, there are some options for the content providers to do that. One option is to build a server farm with huge network connections, but this option is not scalable and not cost effective because the number of consumers is rapidly increasing. The second option is to use Akamai or any other content delivery network (CDN). The CDNs give better performance but they are costly. The third option for the content providers to distribute multimedia objects to millions of users over the Internet is using pCDN, peer-assisted content distribution network.  pCDN benefits from the tremendous success of the peer-to-peer (P2P) computing paradigm. pCDN is a good approach to relieve the costs incurred in content distribution. pCDN provides improved scalability, reduced cost, and rapid deployability. Therefore, pCDN may achieve similar services as CDNs at a fraction of the cost. The core idea of pCDN (which is still investigated) is to deploy seed servers that will manage client request by redirecting the client to other clients (peers) who recently received the same requested multimedia object. The client will contact these peers to receive the requested object from them. This idea has worked with file-sharing P2P systems but with some challenges such as, optimizing video quality, reducing the traffic load on Internet Service Provider (ISP) networks, efficient video transmission from multiple senders, restricting content to certain locations, and digital rights management, i.e., provide service to legitimate clients [BM07].
@@ Line 7: / Line 7: @@
 '''How to manage DRM system?'''
-To manage DRM, it is important to understand three very important issues which are technical, legal, and business matters [DRMT]. The technical issue focuses on how to understand the scope and limitation of DRM technology. The legal issue provides a legal basis for the relationships between content consumers and content providers. The last issue, business issue, focuses on many topics and what these topics mean such as copying, electronic markets, impacts on innovation, business models, and user acceptance of DRM systems. None of these issues can work by itself. In fact, the DRM technologies that we use are dependent on the legal system and both of these issues depend on the business models in operations.
+To manage DRM, it is important to understand three very important issues : technical, legal, and business matters [DRMT]. The technical issue focuses on how to understand the scope and limitation of DRM technology. The legal issue provides a legal basis for the relationships between content consumers and content providers. The business issue focuses on many topics and what these topics mean, such as copying, electronic markets, impacts on innovation, business models, and user acceptance of DRM systems. None of these issues can work by itself. In fact, the DRM technologies that we use are dependent on the legal system and both of these issues depend on the business models in operations.
 '''DRM environment'''
@@ Line 14: / Line 14: @@
 Economic aspects give a good view of the market situation. This view helps the rights holders and their partners to determine which technology and business models they can use. The economic aspects also help to determine if the consumers are willing to use content with these new formats. Social aspects focus on how socially acceptable it is to use DRM systems. These two aspects cannot work without taking into account the third critical issue which influences the use of the DRM systems, international aspects. We know the rights situation differ from country to country, and we are sure when any content made available on the Internet, it is automatically available to everyone. For these reasons, we have to investigate the international aspects. When all these aspects are taken care of, the DRM system with all its elements become successful.
-'''DRM Components'''
+'''DRM Elements'''
-From the definition of the DRM systems, we know DRM systems have to cover a variety of tasks. There are some components exist to fulfil these tasks [DRMT].
+From the definition of the DRM systems, we know DRM systems have to cover a variety of tasks. There are some elements exist to fulfil these tasks [DRMT].
-.	''Secure containers:'' for the users who do not have rights to access the content, the content will be inaccessible. The content, access conditions as well as the license server URL (the server that has the exchange keys) can be seen as putting them in a locked container. This locked container will transmit to the client and unpacked based on the information rules inside it.
+.	Secure containers: for the users who do not have rights to access the content, the content will be inaccessible. The content, access conditions as well as the license server URL (the server that has the exchange keys) can be seen as putting them in a locked container. This locked container will transmit to the client and unpacked based on the information rules inside it.
-.	''Rights expressions:'' express who is permitted to access the content wrapped in secure containers.
+.	Rights expressions: express who is permitted to access the content wrapped in secure containers.
-.	''Content identification and description systems:'' identify the content and join metadata description with the content.
+.	Content identification and description systems: identify the content and join metadata description with the content.
-.	''Identification of people:'' identifies the consumers who intend to interact with the content.
+.	Identification of people: identifies the consumers who intend to interact with the content.
 .	Authentication of people: authenticates the people who want to interact with the content.
-.	''Watermarking and Fingerprinting:'' join identifiers and other information with the content. Hence both of them are used to prove that a violation has happened.
+.	Watermarking and Fingerprinting: join identifiers and other information with the content. Hence both of them are used to prove that a violation has happened.
 == References and Links ==