Re: [gaia] draft-irtf-gaia-alternative-network-deployments. Mitar review, question #3. Typical scenarios

Mitar <mmitar@gmail.com> Wed, 13 April 2016 11:27 UTC

Return-Path: <mmitar@gmail.com>
X-Original-To: gaia@ietfa.amsl.com
Delivered-To: gaia@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDBF12D8C7 for <gaia@ietfa.amsl.com>; Wed, 13 Apr 2016 04:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xbUAp9u9rYF5 for <gaia@ietfa.amsl.com>; Wed, 13 Apr 2016 04:27:08 -0700 (PDT)
Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9487D12D964 for <gaia@irtf.org>; Wed, 13 Apr 2016 04:27:08 -0700 (PDT)
Received: by mail-io0-x242.google.com with SMTP id u185so6308361iod.2 for <gaia@irtf.org>; Wed, 13 Apr 2016 04:27:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=oOQEd7K1+ZHxOY8FbQTmiMb3VP07MmzR6AqzUVtzgWg=; b=FfxS4LYkAYX80SxntP9gWOQseXERwyeOYoawOYRjX8H3ELIpTLT659TC1hdEfQMf7r XoFEcBNaQ7Wi0KaULnB5nvwEvDSzZEj7CBLVi6UZ4IYo3ZuR4IsG5RweJaZ9NZ9epOQy /B/hlBESWaB48M05ZfhNvP8eF/SLQLfgFxcffdo7IQAW06QtT6ap0tdK32FuvtegQ8qL c+DncA7oakZIZXNaqDcq2HPccHy5TsjbAhB0z0SVZ2u+KO7qvlK+2MS4FKWDokZumTd5 9CkWxMUncHulLS+ShzylmIMgYS1/ZHwPbbZbX8aEzQZOQRZ0mAcrlhFoeqSpSrQwtO7O 6N5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=oOQEd7K1+ZHxOY8FbQTmiMb3VP07MmzR6AqzUVtzgWg=; b=ffj3tHgHSLcv+eY81lNJoRvaTKLiBTUnLGr+i4P5Ca30BTcyuuBAqLK2CePqhZLBHu O8pcx6W6PN9iJ378wL63+sfl4Ko84YFsQIp55/bTzO2trxLr+eo/CTG0y5I35SZUeEB0 5voAAndJpZ1PGMhN9356I6/GjPLDOhinJ5fZDmLSWSIjPujGBVvEALyTbh62T1MsemNC QT2SPcVZtdUN0w2MAeiRdxT4ZQCN4CrtOsIUapSlHFMlR7wP3HOuwJkxEJzKljUuhyH6 nKciBPxkjG57HeXGnyGoOnov+HyOfzW/Eog3O8I7B6NgypNPmi4hLmczYIRpejlwqOBT v7zQ==
X-Gm-Message-State: AOPr4FWnvmOX2jkWDoW61hUJH7rwvGme6DLXrHr85L43yEwmtGWuNQJL8D+3PY2Vtt+tCaXFaao796LO9V0ZZw==
MIME-Version: 1.0
X-Received: by 10.107.33.7 with SMTP id h7mr9413511ioh.30.1460546827527; Wed, 13 Apr 2016 04:27:07 -0700 (PDT)
Received: by 10.107.13.76 with HTTP; Wed, 13 Apr 2016 04:27:07 -0700 (PDT)
In-Reply-To: <005a01d194c5$96d7d390$c4877ab0$@unizar.es>
References: <005a01d194c5$96d7d390$c4877ab0$@unizar.es>
Date: Wed, 13 Apr 2016 04:27:07 -0700
Message-ID: <CAKLmikMG+yAS43Za+Q6wK7qs9nuz1Nq_TUx=0k6-u5f2p9oDGw@mail.gmail.com>
From: Mitar <mmitar@gmail.com>
To: Jose Saldana <jsaldana@unizar.es>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/gaia/6VU3Oz4Ec4B1yEisMEc95KbmAf8>
Cc: gaia <gaia@irtf.org>
Subject: Re: [gaia] draft-irtf-gaia-alternative-network-deployments. Mitar review, question #3. Typical scenarios
X-BeenThere: gaia@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Global Access to the Internet for All <gaia.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/gaia>, <mailto:gaia-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gaia/>
List-Post: <mailto:gaia@irtf.org>
List-Help: <mailto:gaia-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/gaia>, <mailto:gaia-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2016 11:27:10 -0000

Hi!

OK, for me it was just confusing categorization. Maybe because other
categorizations list one option per dot, here we list separate
dimensions for each dot (urban/rural, south/north). Type checking does
not match with other categories. :-) And then we use most of the time
"urban and rural" anyway. :-)

BTW, WISPs can be both urban and rural. In San Francisco we have a popular WISP:

https://monkeybrains.net/wireless.html

Pretty urban use. There is nothing really in WISPs to make them rural only.


Mitar

On Tue, Apr 12, 2016 at 7:14 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>
> Hi,
>
>> Section 4.5, typical scenarios:
>>
>> I do not see usefulness of this categorization, because almost any network
> I know of
>> outgrow and changed through time inside all these categories. Community
> networks
>> maybe start somewhere (like urban or rural area), but then they grow and
> spread
>> over the whole country, then start connecting with other countries.
>
> In my understanding, there are some networks especially targeted for rural
> areas. So I think the division does make sense. Perhaps in the future a lot
> of them will be interconnected, but nowadays some rural deployments exist,
> so for me the classification makes sense.
>
> Thanks!
>
> Jose
>
>



-- 
http://mitar.tnode.com/
https://twitter.com/mitar_m