And also, what should we *not* do? We decided many years ago, for example,
that we should *not* weaken security to accommodate public policy. I'm
sure
there are other things in that category, e.g. we should *not* stop work on
quality of service to accommodate naive "network neutrality" rules.
Excellent question. We should not waver from our core principals of rough
consensus and running code but lets face facts we are now what what we
have always feared. We are ITU-T or at least we act like it. Its our
store now.
That said ³with great power comes great responsibility² We have gone down
this road before with RFC 2804 and wiretapping on the policy side.
Congestion control is a central problem. IMHO its insane that the US FCC
is trying to define packet loss as a metric for defining network
performance etc. There are idiots that believe all packets containing cat
videos are created equal but we know better. That is the larger issue we
confront.
I do not have all the answers here needless to say.
Brian
ISOC has done quite a bit to provide tutorials and tour guides for quite
a few folk that I thought were policy-based.
Not to say there isn't more to do, but I've no idea what.
d/