[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IESG comments solicited: draft-iab-research-funding
A good document. I think it is too much US centric though. Don't know
what to do about it, because I don't have time do "research" on what
actually has happened here in Europe. But, it should be mentioned,
regardless how insignificant it is for "Internet" as a whole.
The problem is that there is (especially in Europe maybe), as often
with research unfortunately, no communication between the parties doing
research, and no feedback from research to the operational community.
Because of that, the "research" in for example Europe has lead to
specific applications regarding for example imaging and high speed
storage networks, and not directly new inventions regarding the basic
protocols used on "the Internet".
Only error I can find:
RIPE, as you mention, is market funded research (the members of RIPE
pay), and can not be compared with government (or semi-) funded
research from for example the IPv6 and high speed networks in Europe
which the Commission give money to.
paf
On fredag, feb 7, 2003, at 06:37 Europe/Stockholm, Rob Austein wrote:
A group of IAB folks (which, somewhat to my surprise, appears to
include me, not that I've done a lick of work on this or even had time
to read what the others have done yet) has been tasked with writing a
pair of documents talking about (a) research topics that we think need
to be addressed and (b) how the IETF, ISOC, etc, should and should not
play in this space with the folks from various governments who have
their checkbooks ready. Complex topic, please suspend disbelief
rather than assuming that we're idiots just on the basis of my
incompetent attempt to summarize the subject in one sentence :).
At any rate, one of the proto drafts is far enough along that its
authors would like to offer IESG folks the chance to read and comment.
The URL is:
http://www.icir.org/floyd/research/draft-iab-research-funding-00f.txt
I have been asked to ask the IESG not to leak that URL beyond IAB+IESG
for now.