[kNT] Road map for kNT...

[Daniel Harris <daniel@xxxxxxxxxxxxx>]

Hi there All,

The intention of this email is to kick off some thoughts on where we should 
go with the Kendra Network Trial (kNT). These are suggestions but we have 
to start somewhere...

- One aim of kNT is to build up trial participants (ISPs and CDNs) and test 
content. You can see the current numbers at:
http://www.kendra.org.uk/network-status.php

- Also we want to build up test content to show kNT is able to deal with 
different types of media using different delivery methods. For example 
using the following content categories:

- On-demand video streamed
- On-demand audio streamed
- Live video streamed
- Live audio streamed
- Pure download video file
- Pure download audio file

Each category should ideally include content from both known and unknown 
artists/producers. Say 2 of each type. Also, we should always try to 
present content in as many different formats as possible. Both of these 
things will show that the Kendra System is about inclusivity (not in the 
dictionary - why not?!).

Bear in mind that this stage we are not trying to get loads of content just 
a wide selection of a few pieces to show kNT can handle diverse situations.

- Should we discourage "deep linking" to all kNT streams at this stage? One 
of the reasons kNT is important is as an attractor to the Kendra Initiative 
website. To get people involved and participating. "Deep linking" wont help 
that to happen.

- We need to sort a generalised redirect system to enable serving content 
from the users closest server. Need to look work being done by Content 
Bridge, Content Alliance and Broadband Content Delivery Forum. Or better 
still, get those people more involved in the trial (they are already).

- Develop a generalised way to post content to the Kendra System. Will need 
to sort out metadata interoperability so as not to exclude any of the major 
metadata formats. Once content has been posted/advertised/? to the Kendra 
System there will be a requirement for:
+ Authentication from a trusted third party (maybe more than one).
+ Tracking Method to allow for billing but need to look at privacy issues 
here.

Once we go generalised then the Kendra website should not be the only 
interface to the Kendra System. It has to be fully distributed and 
accessible by any website/application using relevant protocol.

- Enable Payment for content. This essentially involves getting all the 
current payment systems out there to talk to each other. So that when 
someone sells content using 'A' payment system then I can buy it using 'B' 
payment system. Hey! That's what the banking system does for us... Not trivial!

Simple! No, it isn't but we have to start somewhere...

Thanks to Sandy Hoover for helping to get these thoughts down on paper.

Comments?...

Cheers Daniel