<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1528" name=GENERATOR></HEAD>
<BODY><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face="Book Antiqua">
<DIV><BR>> -----Original Message-----<BR>> From: McTim
[mailto:dogwallah@gmail.com]<BR> <BR>> Evening Bill,</DIV>
<DIV> </DIV>
<DIV>Morning, McT,</DIV>
<DIV> </DIV>
<DIV>> CS. As such, some of us<BR>> > felt that treating it as a
separate, 4th stand-alone constituency could<BR>> > dilute what influence
CS has.<BR>> <BR>> I don't see this at all. The people That I know
who do the current IG<BR>> work (IETF, RIR community members, Routing
Registries, NRENs, etc)<BR>> weren't part of CS @ WSIS. Most weren't
present or represented at all<BR>> (except arguably by ISOC).</DIV>
<DIV> </DIV>
<DIV>Right, so should we create a new category of participant in UN discussions
for people who don't actually wish to participate in UN discussions,
particularly if the views it might promote are already represented by or at
least consistent with established stakeholder groupings? More generally, I
recognize that the traditional trichotomy doesn't capture a lot of stuff, and
that self-identities and positions don't always fit into three neat boxes, but
if in response you multiply categories it can get really messy quickly.
And in any event, we've been through this discussion before without resolution,
there's little reason to think we'd get somewhere this time, and the UN and
other participants would be unlikely to reach consensus on it either.
Developing country governments in particular would be opposed.</DIV>
<DIV> </DIV>
<DIV>> Moreover, the category has been strategically<BR>> >
appropriated and deployed, most by ISOC and the ICC (a choir in constant<BR>>
> harmony), to suggest that A&T is a core part of an "Internet <BR>>
community" that<BR>> <BR>> this is simple truth. People who built and
operate the networks that<BR>> allow our machines and networks to communicate
are a "core' part of<BR>> the Inet Community.</DIV>
<DIV> </DIV>
<DIV>Sure. They just don't define the scope of "academia." Most of
the academics I know who have been involved in WSIS are not on the same page as
ISOC's leadership, in whole or in part. It would not be good to create a
category of "academic and technical" that represents just a particular slice of
academic and excludes other views.</DIV>
<DIV> </DIV>
<DIV>> <snip><BR>> And in this usage,<BR>> > "academic"
is sort of construed to mean technical people who agree this<BR>> > line,
not, inter alia, social science types who might favor progressive<BR>> >
reforms. However, others did not see these concerns as that <BR>>
problematic.<BR>> <BR>> I don't see it as a concern as, for example,
Milton, Hans, Derek &<BR>> Jeannette can be CS reps to the IGF.</DIV>
<DIV> </DIV>
<DIV>So they would participate as CS, not as academic, which would be a category
reserved for the right-minded? </DIV>
<DIV> </DIV>
<DIV>> While the IETF, inter alia, academics can be part of T&A.<BR>>
<BR>> <snip><BR>> ><BR>> > In parallel, I think the
"experts" formulation is problematic.<BR>> <BR>> I agree. With a
T&A group tho, you know you got experts on board!</DIV>
<DIV> </DIV>
<DIV>So, the uh, T&A group, would be the experts, and the rest of the
stakeholder groupings would be the what, non-experts? That'd go down
well. Recall the Brazilian reply when the US said that ISOC should convene
the IGF---"then why don't we just call it the Internet Kindergarten
Forum?"</DIV>
<DIV> </DIV>
<DIV>We can go around and around on this on line until arthritis sets in and we
won't get anywhere, and meanwhile I don't see that others are all that
interested in the thread. Maybe better to save it for a beer at IGF.</DIV>
<DIV> </DIV>
<DIV>Best,</DIV>
<DIV> </DIV>
<DIV>Bill<BR></FONT></SPAN></DIV>
<DIV> </DIV></BODY></HTML>