Re: [gaia] New Version Notification for draft-manyfolks-gaia-community-networks-02.txt. The axes for the classification

Javier Simó <javier.simo@urjc.es> Mon, 16 February 2015 16:38 UTC

Return-Path: <javier.simo@urjc.es>
X-Original-To: gaia@ietfa.amsl.com
Delivered-To: gaia@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26C631A1B56 for <gaia@ietfa.amsl.com>; Mon, 16 Feb 2015 08:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level:
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lSIgRzhioT6m for <gaia@ietfa.amsl.com>; Mon, 16 Feb 2015 08:38:02 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0604.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::604]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B03651A1B4E for <gaia@irtf.org>; Mon, 16 Feb 2015 08:38:01 -0800 (PST)
Received: from DB3PR02MB316.eurprd02.prod.outlook.com (25.160.43.24) by DB3PR02MB0281.eurprd02.prod.outlook.com (25.160.43.154) with Microsoft SMTP Server (TLS) id 15.1.87.18; Mon, 16 Feb 2015 16:34:44 +0000
Received: from [193.147.53.169] (193.147.53.169) by DB3PR02MB316.eurprd02.prod.outlook.com (25.160.43.24) with Microsoft SMTP Server (TLS) id 15.1.87.18; Mon, 16 Feb 2015 16:34:43 +0000
Message-ID: <54E21C20.9040209@urjc.es>
Date: Mon, 16 Feb 2015 17:34:40 +0100
From: Javier Simó <javier.simo@urjc.es>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Jose Saldana <jsaldana@unizar.es>, Henning Schulzrinne <hgs@cs.columbia.edu>, 'Maria Uden' <Maria.Uden@ltu.se>, 'Matthew Ford' <ford@isoc.org>
References: <00cd01d04a02$2263f2f0$672bd8d0$@unizar.es>
In-Reply-To: <00cd01d04a02$2263f2f0$672bd8d0$@unizar.es>
Content-Type: multipart/alternative; boundary="------------080708070304050004090900"
X-Originating-IP: [193.147.53.169]
X-ClientProxiedBy: AMSPR03CA0047.eurprd03.prod.outlook.com (10.242.14.175) To DB3PR02MB316.eurprd02.prod.outlook.com (25.160.43.24)
Authentication-Results: irtf.org; dkim=none (message not signed) header.d=none;
X-Microsoft-Antispam: UriScan:;UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB3PR02MB316;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:DB3PR02MB316;
X-Forefront-PRVS: 0489CFBAC9
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(53754006)(479174004)(51444003)(24454002)(377454003)(48214007)(51704005)(92566002)(83506001)(50986999)(40100003)(77156002)(2950100001)(19625215002)(62966003)(19617315012)(42186005)(19580395003)(76176999)(80316001)(2171001)(16236675004)(19580405001)(122386002)(2420400003)(15975445007)(33656002)(15187005004)(84326002)(87266999)(54356999)(65816999)(512944002)(46102003)(36756003)(66066001)(65806001)(87976001)(230783001)(74482002)(86362001)(65956001)(7059030)(3940600001)(579004)(559001)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR02MB316; H:[193.147.53.169]; FPR:; SPF:None; MLV:sfv; LANG:en;
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DB3PR02MB316;
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Feb 2015 16:34:43.2617 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR02MB316
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB3PR02MB0281;
X-OriginatorOrg: urjc.es
Archived-At: <http://mailarchive.ietf.org/arch/msg/gaia/ibzE--rf4wv7bx2AR2tAbOncB9Q>
Cc: gaia@irtf.org
Subject: Re: [gaia] New Version Notification for draft-manyfolks-gaia-community-networks-02.txt. The axes for the classification
X-BeenThere: gaia@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Global Access to the Internet for All <gaia.irtf.org>
List-Unsubscribe: <https://irtf.org/mailman/options/gaia>, <mailto:gaia-request@irtf.org?subject=unsubscribe>
List-Archive: <http://irtf.org/mail-archive/web/gaia/>
List-Post: <mailto:gaia@irtf.org>
List-Help: <mailto:gaia-request@irtf.org?subject=help>
List-Subscribe: <https://irtf.org/mailman/listinfo/gaia>, <mailto:gaia-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2015 16:38:07 -0000

Hello Jose

I like the 5 axes scheme that you propose. I would just add that a 
particular alternative network may not be a point in the 5-dimensional 
space, but a "volume". A network may use more than one technology, cover 
more than one typical scenario, have more than one motivation, etc. Only 
axe 5) is pretty binary, the network management paradigm is either 
centralized or distributed, never both.

Last, I'm thinking at Delay Tolerant Networks. I think that the DTN 
paradigm is significant and it cannot be clearly positioned in any axe. 
It could be in technology, but it is a bit ortogonal to layer-2 
technologies. Also I don't know if you guys think that it is worth of a 
6th axe (sorry).

Best

El 16/02/15 a las 17:03, Jose Saldana escribió:
>
> Hi all,
>
> You are right: the current version of the draft says something a bit 
> confusing:
>
> Different criteria are used in order
>
> to build a classification as e.g., the ownership of the equipment,
>
> the way the network is organized, the participatory model, the
>
> extensibility, if they are driven by a community, a company or a
>
> local (public or private) stakeholder,
>
> Taking into account your proposals, I have tried to build a scheme 
> with five “axes” of the classification. They could perhaps be:
>
> 1) Commercial model / promoter
>
> * community
>
> * public stakeholder
>
> * company
>
> * crowdshared
>
> * shared infrastructure
>
> * research testbed
>
> 2) Goals and motivation (Henning’s classification)
>
> * reducing initial capital expenditures (for the network and the end 
> user, or both)
>
> * providing additional sources of capital (beyond the traditional 
> carrier-based financing)
>
> * reducing on-going operational costs (such as backhaul or network 
> administration)
>
> * leveraging expertise
>
> * reducing hurdles to adoption (digital literacy; literacy, in 
> general; relevance, etc.)
>
> 3) Typical scenarios
>
> * urban
>
> * rural
>
> * rural in developing countries
>
> 4) Technologies employed (Javier’s list)
>
> * normal WiFi
>
> * WiLD
>
> * modified WiFi with TDMA MAC
>
> * 802.16-compliant systems over non-licensed bands
>
> * white spaces - 802.22 compliant solutions
>
> * satellite solutions
>
> * low-cost optical fiber systems
>
> 5) Network management
>
> * Centralized
>
> * Distributed
>
> Do all of them make sense to you?
>
> Are they “orthogonal” enough?
>
> Thanks and best regards,
>
> Jose
>
> *De:*gaia [mailto:gaia-bounces@irtf.org] *En nombre de *Javier Simó
> *Enviado el:* martes, 10 de febrero de 2015 16:30
> *Para:* gaia@irtf.org <mailto:gaia@irtf.org>
> *Asunto:* Re: [gaia] New Version Notification for 
> draft-manyfolks-gaia-community-networks-02.txt. Sharper identification
>
> El 10/02/15 a las #4, Maria Uden escribió:
>
>     Yes, and the technical details can be presented by themselves, in
>     even more detail, without referring to the socio-technical context?
>
> In my humble point of view,
>     - yes, technical details can be presented by themselves without 
> referring to the context, provided that later in the document 
> technology is going to be crossed in the matrix with the different 
> alternative networks together with other vertical descriptors.
>
>     - however, i think that we should not go very deep into the 
> details in describing technologies. They are described either in 
> standards or in papers that can be referenced. Techniques that are 
> well known and that are explained in books or articles should also be 
> cited. We should be able to summarize those things, with appropriate 
> references, instead of extending the document with them unnecessarily. 
> The accent of the document should not be in the technologies, but in 
> the definition of the alternative networks with the discussion of all 
> the relevant characteristics (socio-technical context, technologies 
> used, bussiness model, ...)
>
> Best
> Javier
>
>
> A test bed can have different underlying reasons, for instance be 
> thought of as a way to raise funding for a community network.
>
> Maria
>
> *From:*Henning G Schulzrinne [mailto:hgs@cs.columbia.edu]
> *Sent:* den 10 februari 2015 15:30
> *To:* Maria Uden
> *Cc:* Jose Saldana; gaia@irtf.org <mailto:gaia@irtf.org>; Matthew Ford
> *Subject:* Re: [gaia] New Version Notification for 
> draft-manyfolks-gaia-community-networks-02.txt. Sharper identification
>
> Another approach is to look at the underlying motivation for these 
> approaches, i.e., addressing deployment and usage hurdles:
>
> * reducing initial capital expenditures (for the network and the end 
> user, or both)
>
> * providing additional sources of capital (beyond the traditional 
> carrier-based financing)
>
> * reducing on-going operational costs (such as backhaul or network 
> administration)
>
> * leveraging expertise
>
> * reducing hurdles to adoption (digital literacy; literacy, in 
> general; relevance, etc.)
>
> Most of the examples given, except the testbed, seem to fall into one 
> or more of these categories. Given that there are likely more 
> solutions than the examples discussed, it might be helpful to focus on 
> the goals, as that then also allows to evaluate whether and to what 
> extent a solution meets the goal. Otherwise, it's just technology for 
> coolness' sake.
>
> Henning
>
> On Tue, Feb 10, 2015 at 2:24 AM, Maria Uden <Maria.Uden@ltu.se 
> <mailto:Maria.Uden@ltu.se>> wrote:
>
> The classification is interesting as information but, is it not only 
> examples, after all? Or, what is the purpose? An analogy: My 
> experience as teacher is that the more detailed descriptions the more 
> the students will ask – because each detail opens questions. Like the 
> fractals one sees in these nice maths/science pictures. They will feel 
> insecure and instead of getting to action themselves wonder if they 
> can really do it, as it is so defined into details what “it shall be 
> about”.
>
> Cheers,
>
> Maria
>
> *From:*gaia [mailto:gaia-bounces@irtf.org 
> <mailto:gaia-bounces@irtf.org>] *On Behalf Of *Jose Saldana
> *Sent:* den 9 februari 2015 16:27
> *To:* gaia@irtf.org <mailto:gaia@irtf.org>; 'Matthew Ford'
> *Subject:* Re: [gaia] New Version Notification for 
> draft-manyfolks-gaia-community-networks-02.txt. Sharper identification
>
> Hi all,
>
> Mat has sent this suggestion:
>
> > A general observation: I find the taxonomical aspect a bit lacking at present. I would
>
> > like to have a sharper identification of the characteristics of identified alternative
>
> > network types that distinguishes them. Is it the commercial model? Is it the
>
> >centralisation or decentralisation of network management? The 
> descriptions are fine
>
> > as far as they go, but if there's something unique about the different types that
>
> > clearly distinguishes them it would help to call that out better. Maybe a matrix of the
>
> > various identified types of network and some of the important characteristics would
>
> > be appropriate.
>
> This is the current classification (section 2):
>
>      2.1.  Community Networks
>
>        2.1.1.  Free Networks
>
>      2.2.  Wireless Internet Service Providers WISPs
>
>      2.3.  Shared infrastructure model
>
>      2.4. Crowdshared approaches, led by the people and third party 
> stakeholders
>
>      2.5. Testbeds for research purposes
>
> Mat, are you suggesting to include a table like this?:
>
> | Commercial model | centralization | technologies | typical   |
>
> |                  | |              | scenarios |
>
> +------------------+----------------+--------------+-----------+
>
> CNs |                  | |              |           |
>
> WISPx|                  | |              |           |
>
> Shared inf |                  |                |           |           |
>
> Crowdshared|                  | |              |           |
>
> Testbeds|                  | |              |           |
>
>
>
>
> _______________________________________________
> gaia  mailing list
> gaia@irtf.org  <mailto:gaia@irtf.org>
> https://irtf.org/mailman/listinfo/gaia
>
>
>
> -- 
>   
> ---------------------------------------------------
> Fco. JavierSimó  Reigadas  <javier.simo@urjc.es>  <mailto:javier.simo@urjc.es>
> Subdirector de Ord. Docente
> ETS de Ingeniería de Telecomunicación
> D-204, Departamental III
> Camino Del Molino, s/n - 28943 Fuenlabrada (Madrid)
> Tel: 914888428, Fax: 914887500
> Web personal:http://www.tsc.urjc.es/~javier.simo  <http://www.tsc.urjc.es/%7Ejavier.simo>

-- 

---------------------------------------------------
Fco. Javier Simó Reigadas <javier.simo@urjc.es>
Subdirector de Ord. Docente
ETS de Ingeniería de Telecomunicación
D-204, Departamental III
Camino Del Molino, s/n - 28943 Fuenlabrada (Madrid)
Tel: 914888428, Fax: 914887500
Web personal: http://www.tsc.urjc.es/~javier.simo