sf: Background
... digital content easy to copy
... The core part of the issues
... the cost of fraud is low
... while the cost of fair use is high
... also it's difficult to oconfirm the originality of digital content in a true sense
... Need for tech help
... strict content ID management
... watermarks for videos
... but difficult to generate embedded watermark dynamically
... Blockchain
... status of improvement
... blockchain has been improving fro cryptocurrency to app platform
... Proof of existence (PoE)
... one of the most popular usage of blockchain
... by recording the hash value in the vlockchain
... Our basic concept
... information about a content is registered in blockchain
... everyone can check it
... distributing the content
... watermark including user informtion is applied
... owner offers to share the digital content in the limited area
... Our prototype details
... (diagram of the prototype)
... user makes an HTTP request
... content server makes watermark ID
... Watermark superimposing for including useinfo.
... digital watermark is not suitable for personal information
... so would propose superimposing by JS
... streaming video is on a layer
... and watermark is on another layer
... (demo video)
... [Prtotype] Blockchain-based Content Distribution System
... login the blockchain first
... loguin UI
... content list here
... downloaded from the blockchain
... cryptography by electron framework
... superimposing the watermark
... screen capturing
... if the user captures the video content
... it has a watermark
... and the user can be also identified
... watermark detection tool as well
... people can check if it's OK
... [slides again]
... [Before open discussion]
... some notes
... our prototype is not perfect now
... adblocker-type client -side JS is a weak poit f superimposing method
... just one idea but
... if there is a spec to force display in the form specified by the service provider
... would you give me some advive?
... what groups to discuss it?
... blockchain CG?
... MEIG?

kj: we can disable JS on browsers
... so that we can block the watermark

sf: there is a proxy server which can catch the watermark

kaz: in that case, that proxy can superimpose the watermark for the client browser

sf: right

hoya: if we want to detect piracy usage, the user agent has to decode the watermark?

sf: by using the blockchain people can check it

kaz: we need to install an additional checker tool in addition to browsers

sf: there is incentive for the content holders

hoya: there are many watermarked contents these days
... any possible collisions

sf: not really sure about the mechanism
... depends on which watermark mechanism is used
... fyi, NTT has a research department for blockchain technology

kaz: implying some possible standardization
... or might be some type definition to identify the watermark types

sf: might be able to use some QR codes to identify the types

jay: if you put multiple watermarks into one specific content
... we can detect that

kaz: does that mean we can attach more than one watermark to one specific video data?

jay: right

kaz: in that case, we need to identify which watermark is the official one

sf: this yellow content server adds watermark before distributing the video

kaz: in that case, that server should check if there are no unexpected watermarks
... and purify the video content
... before distributon

hiro: web is open platform
... superimposing on the client side here
... previously efforts on DRM on browsers
... do you expect watermark can be implemented within browsers?
... any ideas about the relationship/integration of DRM and digital watermark for web browsers?

sf: DRM has weak point, I think
... combining digital watermark would make it stronger

hiro: maybe we can handle the watermark on the server side, can't we?

cm: if you have watermark capability on the client side
... you can try something like EME
... but that would be more dangerous
... bad guys could hack the blackbox
... you might want to think about another approach, e.g., generating white/black blocks on the server side
... and you can superimpose those two on the client side to get the correct video
... there is some video format which is playable just one time
... and destroys itself

jay: this kind of approach is good for now

kaz: regarding the next step
... which direction are you interested more?

sf: please advise

kaz: maybe you might want to talk with the Chairs of those proposed groups
... blockchain CG, MEIG, VCWG

jay: I'm afraid the Blockchain CG is not very active now
... maybe the VCWG would be better?

hoya: ATSC 3.0 has watermarking capability
... you should define concrete use cases for further discussions

kaz: it seems there is a breakout session on DID
... so you should talk with them as well

cyril: good use case for blockchain

kaz: agree with Hoya-san to generate more concrete use cases
... if other people agree those use cases are important, we can start discussion on content management/protection

sf: would like to talk with the group chairs
... and will generate concrete use cases

kaz: can help you

sf: tx for joining the session!

[adjourned]

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/@1/kj/
Succeeded: s/@2/hiro/
Succeeded: s/hack that/hack the blackbox/
Present: Jay

WARNING: Fewer than 3 people found for Present list!

No ScribeNick specified.  Guessing ScribeNick: kaz
Inferring Scribes: kaz

WARNING: No "Topic:" lines found.


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)