FW: Open Mash Vic encryption for the Access Grid

[Ivan R. Judson]

There's the answer. Sounds like he's pulling his hair out, notice he
cc'd the om-developers (which I think was an accident).

--Ivan

..........
Ivan R. Judson .~. http://www.mcs.anl.gov/~judson
Futures Laboratory .~.  630 252 0920
Argonne National Laboratory .~. 630 252 6424 Fax
 

> -----Original Message-----
> From: Lawrence A. Rowe [mailto:Rowe at bmrc.berkeley.edu] 
> Sent: Friday, September 27, 2002 2:28 PM
> To: judson at mcs.anl.gov
> Cc: 'Open Mash Developers'
> Subject: Re: Open Mash Vic encryption for the Access Grid
> 
> 
> "Ivan R. Judson" wrote:
> > 
> > Hi,
> > 
> > We've just realized (after being asked by others) that in 
> order for OM 
> > Vic to fulfill our AG needs, we need to figure out how encryption 
> > works (if at all). The UCL vic leverages encryption from the common 
> > library for rijndael and AES encrypted data streams.
> > 
> > How would one encrypt OM Vic streams?
> ---
> 
> Ivan -
> 
> Sigh, I don't think it is going to happen.  I proposed doing 
> that, in addition to other tasks, in the last NSF proposal I 
> submitted - the one I sent to Tom Green who is head of the 
> program  on "Strategic Technologies for the Internet."  
> Sadly, that grant was also rejected. 
> Yeap, we went 0-for-3 on proposal submissions. I haven't made 
> a completely public announcement of this rejection yet, 
> although I did communicate it to selected people.  I have 
> attached a copy of the reviews from the panel.  The four reviews were:
> 	Very Good, Good, Good, Very Good/Good
> and the panel judgement was that the proposal was 
> competitive.  However, the grant was not funded.  Frankly, 
> looking at the reviews it is pretty apparent we asked for too 
> much money and people do not seem to understand the problems 
> building and deliverying practical software. 
> Comments like "where is the fundamental research component" 
> reflect a desire for more speculative proposals that may or 
> may not produce deliverable code. I structured the proposal 
> to address problems that we know how to solve but require 
> development and engineering and I submitted it to the ANIR 
> STI program because I was told they focussed on deliverying 
> working systems. Unfortunately, the proposal was not good enough.  
> 
> Consequently, I am closing the Open Mash research project and 
> leaving Berkeley and academia. I have been layed off students 
> and staff and I am in the process of closing down the 
> research activities in anticipation of leaving at the end of 
> this academic year.  I am not exactly sure what I will do 
> next, although some interesting possibilities exist.  The 
> bottom line is that since I do not have to work I would 
> rather retire and work on projects myself than continue 
> dealing with resource and political issues at Berkeley when 
> there is no funding for research activities.
> 
> We are finishing projects that were previously funded and in 
> process - specifically implementing the h.263 decoder (we 
> hoped to do the encoder next, but...), updating OM vic to 
> support the UCL conference bus abstractions, and finishing 
> the Mac port.  I was hoping we would get something done this 
> month, but it hasn't happened for a combination of reasons - 
> including the time required for me to teach the very large 
> introductory CS class I am doing this semester (400 plus people).
> 
> So, the answer to the question "How would one encrypt OM Vic streams?"
> is: 1) find someone to fund the work, 2) find someone to do 
> the work, and 3) find someone to supervise the project.
> 
> I still believe these systems are too complex to use and 
> require too many people to operate.  The technology we 
> proposed - automating the production/direction using a 
> rules-based distributed systems is the right approach to 
> solving the problem.  Unfortunately, we could not convince 
> others in the research community that the research and 
> development was important enough to be funded.
> 	Larry
> -- 
> Professor Lawrence A. Rowe          Internet:  Rowe at BMRC.Berkeley.EDU
> Computer Science Division - EECS       Phone: 510-642-5117
> University of California, Berkeley       Fax: 510-642-5615
> Berkeley, CA 94720-1776            URL: 
> http://bmrc.berkeley.edu/~larry
> 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sti-reviews.txt
URL: <http://lists.mcs.anl.gov/pipermail/ag-dev/attachments/20020927/c26f90ca/attachment.txt>