<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Mawaki et al<br>
<br>
I think we have to operate at multiple levels of abstraction, and
let the matter have some of these dynamics particularly in the
exploratory stage; the broader social 'definition' (conception) vs
the specific 'definition' (conception).<br>
<br>
From my perspective, not to speak for KB, I think there is some
value in having functional
understandings/approaches/worldviews/definitions for 'the Internet'.
Issues are technical. These can define the realm of possibility - no
VOIP layer then that feature is not possible or rather constrained
by the technical. So there IS a set of technical elements as the KB
definition poses, which forms one small bubble. The is also the
social constructivist type (poor term, but it suffices) approaches
that sees a "regulatory" (formal, informal rules of the 'game', or
institutional forms) which is another bubble. The difficulty comes
for both bubbles at the fringes/edges and also where they overlap
(overlap in the sense that Lessig means, where the technical is
regulatory - single root under ICANN eg; bearing in mind the
regulatory can also be technical - legal rights to go in and fix or
debug elements of the hardware). Bubbles at the mid level of
abstraction.<br>
<br>
Having a clear approach on what is included in the KB type proposal,
I think it would delineate more clearly what is understood/felt to
be in the technical realm (with its own engineering particularities
imposing limits on what is possible. Reliance on this would make
clear differences in diagnosis and prescription. The value of the KB
proposal is that it sets feasible technical realms of possibility.
With this clear we can all benefit from this type of clarity,
recognising as I do the Lessig notion of the overlap. There are
technical elements that have governance implications that point to
specific advantages (from mid-level of abstraction analysis)
regarding small specialised competent country registries, the
subsidiarity and decentralisation and integration that goes with it,
that are functional to the technical itself.<br>
<br>
So, WHERE RELEVANT, the one 'definition' presuppose the other. It
would go a long way to curing the interminable debates on what we
mean (and we oft mean different things, and come from diverse
worldviews) by Internet, the specific technical (although not
completely limited to that, if where relevant we recognise the
sets/bubbles) of the overall conception of the internet governance
space (including multiple stakeholders) holistically. Just in terms
of scope, from the WSIS documents, we have a huge menu of issues,
and it simply means we DO need to operate at multiple levels of
abstraction. <br>
<br>
My suggestion is that both 'definitions' be worked in parallel with
some sort of framing so that discussion and process wise we are more
precise and clear.<br>
<br>
Thoughts?<br>
<br>
Riaz<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 2013/04/20 12:45 AM, Mawaki Chango
wrote:<br>
</div>
<blockquote
cite="mid:CACTo+v9_W1v-jraaiGnrsvUyeuhseBqf_qW_k--SmHZX9e9bcw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>Kerry,<br>
<br>
</div>
My understanding is that we have given up defining the
Internet per se (so we're not going to present this as our
definition of the Internet). Therefore the focus is now on
the purpose of this endeavor (which again is not to define
the Internet and which I believe has abundantly been made
clear by Parminder) while avoiding any factual inaccuracy
--and maybe those two things should constitute good enough
measure of our acceptance. To that end, it's meaningful that
the statement starts with "We recognise..." and not
"Internet is..."<br>
<br>
</div>
Were we on the same page and am I just laboring the point?<br>
<br>
</div>
Mawaki<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Apr 19, 2013 at 7:24 PM, Kerry
Brown <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kerry@kdbsystems.com" target="_blank">kerry@kdbsystems.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I've been
watching this discussion develop with interest. I've been
quiet so far because I wanted to see where it was going
before speaking up. I think the attempt to define the
Internet as anything more than a communications medium will
be too limiting at some future date. I would prefer
something very simple like:<br>
<br>
"The Internet is a communications medium that allows
communications between endpoints with all endpoints being
equal in their potential to communicate with all other
endpoints."<br>
<br>
This does not limit any future changes to the way the
communications happen or what is communicated. Trying to
include content and purpose may at some point limit
innovation. Defining the Internet this way doesn't exclude
us from discussing content, commons vs. public good etc. It
just ensures that the medium itself is separate from what
the medium is used for. Both will change over time. If they
are linked by definition it may stifle innovation.<br>
<span class="HOEnZb"><font color="#888888"><br>
Kerry Brown<br>
<br>
</font></span><br>
____________________________________________________________<br>
You received this message as a subscriber on the list:<br>
<a moz-do-not-send="true"
href="mailto:governance@lists.igcaucus.org">governance@lists.igcaucus.org</a><br>
To be removed from the list, visit:<br>
<a moz-do-not-send="true"
href="http://www.igcaucus.org/unsubscribing"
target="_blank">http://www.igcaucus.org/unsubscribing</a><br>
<br>
For all other list information and functions, see:<br>
<a moz-do-not-send="true"
href="http://lists.igcaucus.org/info/governance"
target="_blank">http://lists.igcaucus.org/info/governance</a><br>
To edit your profile and to find the IGC's charter, see:<br>
<a moz-do-not-send="true"
href="http://www.igcaucus.org/" target="_blank">http://www.igcaucus.org/</a><br>
<br>
Translate this email: <a moz-do-not-send="true"
href="http://translate.google.com/translate_t"
target="_blank">http://translate.google.com/translate_t</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>