W3C home > Mailing lists > Public > public-credentials@w3.org > November 2015

Re: Solutions to the NASCAR problem?

From: Steven Rowat <steven_rowat@sunshine.net>
Date: Mon, 23 Nov 2015 07:53:54 -0800
To: "henry.story@bblfish.net" <henry.story@bblfish.net>
Cc: public-credentials@w3.org
Message-ID: <56533692.6080000@sunshine.net>
On 11/23/15 7:33 AM, henry.story@bblfish.net wrote:
> Still having said that, I think it would be the role of researchers
> at the CCN layer to follow the work evolving at the well understood
> http layer, try to adapt it as closely as possible to these other
> layers, and provide feedback when architectural decisions at one
> layer are making logical mistakes that appear when enlarging the
> view to the wider perspective.

Agreed. And I've only followed sporadically so perhaps they are doing 
this, though I haven't seen it. But if not, there might be a good 
reason: when you add in the political complexities of the W3C 
consensus system, mediated partly by the ideological differences of 
corporate silos versus open code movements (and crossed forms of 
these), it might be that the CCN/NDN people have made a strategic 
decision just to hunker down and see if they can make something turns 
out to work, and ignore everybody else until that's finished. If so, 
it might not turn out to be a bad decision, from both creativity and 
efficiency perspectives.

> That has to be done very carefully, in order not to derail consensus at the simpler layer, but it would
> help provide constraints and motivations for doing things
> correctly.

I lost the referent here -- is HTTP your simpler layer, or the CCN? 
(We won't really know unless/until a full form of CCN is published and 
operational, but it seems possible to me that CCN will be simpler and 
sweep away some of the current tangled code structures; possibly whole 
layers of them).


Steven Rowat
Received on Monday, 23 November 2015 15:54:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 July 2018 21:19:26 UTC