throbber
Message
`From:
`
`Clifton Kagawa [clifkagawa@hawaii.rr.com]
`
`
`
`
`
`on behalf of Clifton Kagawa <clifkagawa@hawaii.rr.com> [clifkagawa@hawaii.rr.com]
`Sent:
`
`
`1/27/2004 5:35:32 PM
`To:
`
`
`
`
`
`
`Souza [gsouza@bbitv.com]
`
`
`Subject: Re: lnDemand meeting report
`
`
`
`Guy [gyamashita@bbitv.com]; tv]; Glenn Yamashita [tim@adss.Milton Diaz [milton_diaz@yahoo.com]; Tim Eva rd
`
`
`
`Milton, if we are successful in locking down agreements with InDemand and N2BB, how much of a barrier to
`
`
`
`
`
`
`
`
`
`entry will they represent?
`
`cl if
`
`Original Message----­
`
`From: Milton Diaz
`
`
`
`
`
`Sent: Tuesday, January 27, 2004 3:21 PM
`
`
`
`subject: InDemand meeting report
`
`To: Tim Evard ; 'Clifton Kagawa' ; Glenn Yamashita Guy Souza
`
`All
`
`I had an excellent meeting with Rebecca Glashow, Director of Business Development at InDemand. The
`
`
`
`
`
`
`
`
`
`
`
`
`meeting was held at InDemand's offices in Manhattan (in my old neighborhood, about 3 blocks from where I
`
`
`used to live in the 1980's). The salient points:
`
`*
`As Rebecca has indicated before, proceeding with InDemand is contingent on their receiving
`
`
`
`
`
`
`
`
`
`
`instruction from TWC that InDemand should carry our product. Rebecca and I worked under the assumption
`
`
`
`
`that this will be forthcoming given our relationship with Oceanic and TWC.
`*
`Once the permission to proceed is granted, she estimates it will take about 60 days execute
`
`
`
`
`
`
`
`
`
`
`
`
`agreements, model our transmission requirements, QA our content packages and process, and go live.
`*
`
`
`
`
`
`
`
`As I mentioned in a previous email, InDemand's standard scheduling timeline for broadcasting a
`
`
`
`
`video file is 45 days when they are providing the full video encoding/packaging/QA service. If we use
`
`
`
`
`
`
`
`their Transport service instead, where we deliver a properly prepared content package (encoded and
`
`
`
`
`
`constructed on N2BB systems), then she is confident that the window can be reduced to 3 weeks.
`*
`
`
`
`
`
`
`The scheduling window will most likely be reduced in the future, as other VOD-based products such
`
`
`
`
`
`
`
`as time-sensitive sports programming products enter the market; InDemand is working on these new products
`
`
`
`and is aware of the issue. she did clarify that the 3 week (and 45 day) scheduling windows are not
`
`
`
`
`
`
`solely a result of InDemand process; TWC and the other operators defined these delivery parameters along
`
`
`
`
`with InDemand to suit their own needs. In other words, reducing these windows will require cooperation
`
`
`
`
`from the operators as well as InDemand. For the time being, when we convert to InDemand, we will most
`
`
`
`
`
`likely have a 4 week window between receiving a video, encoding/packaging/QA, transmit to InDemand and
`
`then schedule for broadcast.
`*
`We spent significant time going over our new product concepts and the value proposition for the
`
`
`
`
`
`
`
`operators. she was very intrigued and very positive about what we are doing. If TWC gives the green
`
`
`
`
`
`
`
`light, I think Rebecca and InDemand will be willing and interested in supporting our service. However, I
`
`
`
`
`
`think we will have to host a visit to Honolulu for Rebecca and the head of operations while it is still
`
`
`cold in the Northeast once we are live with Navic ....
`
`All in all, it was worthwhile making the effort to meet Rebecca in person. Now I am on the plane headed
`
`
`
`
`
`
`
`
`
`
`to Atlanta to meet with the other side of the equation, Mike Keyserling of N2BB to discuss the packaging
`
`
`systems, their relationship with TWC, etc.
`
`Thanks,
`
`mdp
`
`
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`BBITV050613
`
`BBiTV EX2059
`DISH v. BBiTV
`IPR2020-01267
`
`PROTECTIVE ORDER MATERIAL
`
`

`

`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`BBITV050614
`BBITV050614
`
`PROTECTIVE ORDER MATERIAL
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket