Re: [gaia] draft-irtf-gaia-alternative-network-deployments. Mitar review, question #8: Mesh routing protocols

Mitar <mmitar@gmail.com> Thu, 14 April 2016 18:24 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 CF88612D6AD for <gaia@ietfa.amsl.com>; Thu, 14 Apr 2016 11:24:52 -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 Ek3jhBb95_Ac for <gaia@ietfa.amsl.com>; Thu, 14 Apr 2016 11:24:50 -0700 (PDT)
Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (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 C3EEF12D19F for <gaia@irtf.org>; Thu, 14 Apr 2016 11:24:49 -0700 (PDT)
Received: by mail-io0-x244.google.com with SMTP id z133so12103134iod.1 for <gaia@irtf.org>; Thu, 14 Apr 2016 11:24:49 -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:content-transfer-encoding; bh=vpxgW4KK8f1eo4igVkEWsHqTCnTtFPdfrJBipsMtrks=; b=wXytOahRJyvcCBXYH6OMqswMcZEAV0SpGkizSVj0PEtRT7lj9aaHHsHolBUkDDczKF t4Gp5Xqwv7Ze7ZLhold32shVbqH1kN1euXG/DsjHygVIwCasEWMAKvfzECVubzK9Cf/d EEB7Oiy4PHG+2t5uQ0cxODpqPEiUrraWnG5pZKUDufI3GEQvVt5YkEBFu8t0tykv5yNx N9OKEeJ610swUPy9V3QvWKbAJYwczUHNelIFOZ3yzBQ3g/pAkC140ZcDLAM00TcdRUE3 9g5dW5Ao4tiyqU+mIkava7SCwV8Uv9rdtMKxyxgBhp43miIXvaeVcqOAsjPCHGekvzRE 5XmQ==
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:content-transfer-encoding; bh=vpxgW4KK8f1eo4igVkEWsHqTCnTtFPdfrJBipsMtrks=; b=VcGVs54F/Yt4v0tMNqplZPs5uCFhabzQhBO0fhXd3c4nytnMO6OJ6XOy+tbIuzlsyi KAGTPvOoF8Zc4yRLBLzaxjmmO9qrYtBC84E7QRlSvocoAYrvVuSdJ8S+Ly0cq2qjcKOi Dbt6ZjeQ9gtU2+UfnPT7FwwuUT0et3GjniGPrM9Nyfdq85dRyfIeSu0zql9xsCPR5rKr HItusAU2B/pX6lpFWj3GcjbUl5NkqeA43tzSQN/aaHt9YxaTyMLxwJQJt6JSwFs3yUM0 RQkN6W39JSoRD+Wh9bsAdsUp8vU2778Fr6rB/lCsrlr+KtLGKQDRds8I2BuOxD5aG8ex uX3A==
X-Gm-Message-State: AOPr4FVW+A24xU0dYeM2yRZTKHx9Oi42YPWxvhyYcdguVyxQ1qsOyk0mYtpHr8WxmLiUn2z8b2GDk6hvrdwnQg==
MIME-Version: 1.0
X-Received: by 10.107.173.69 with SMTP id w66mr19631497ioe.182.1460658289068; Thu, 14 Apr 2016 11:24:49 -0700 (PDT)
Received: by 10.107.146.131 with HTTP; Thu, 14 Apr 2016 11:24:48 -0700 (PDT)
In-Reply-To: <003101d1965b$5f807720$1e816560$@unizar.es>
References: <007601d194ca$9da2c590$d8e850b0$@unizar.es> <CAKLmikM7m+5icS5qC4a7jL_iZy6J0O2939ddk9jmpTuMs2w+mQ@mail.gmail.com> <003101d1965b$5f807720$1e816560$@unizar.es>
Date: Thu, 14 Apr 2016 11:24:48 -0700
Message-ID: <CAKLmikNH-Nkqe8CM-PdiP97duA=L=LEX2tHjYM6STVKExxy0Rw@mail.gmail.com>
From: Mitar <mmitar@gmail.com>
To: Jose Saldana <jsaldana@unizar.es>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/gaia/HtAqBis2-hyeRwvh3g-l_dFTTBw>
Cc: gaia <gaia@irtf.org>
Subject: Re: [gaia] draft-irtf-gaia-alternative-network-deployments. Mitar review, question #8: Mesh routing protocols
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: Thu, 14 Apr 2016 18:24:53 -0000

Hi!

This sounds good. :-)

If I remember correctly, in other parts of the document we mention
that people like to mix these, and also even use BGP and other more
standard things, yes? This is just a section with specific routing
protocols readers might not be familiar with?


Mitar

On Thu, Apr 14, 2016 at 7:38 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>
>
>> -----Mensaje original-----
>> De: Mitar [mailto:mmitar@gmail.com]
>> Enviado el: jueves, 14 de abril de 2016 11:19
>> Para: Jose Saldana <jsaldana@unizar.es>
>> CC: gaia <gaia@irtf.org>
>> Asunto: Re: [gaia] draft-irtf-gaia-alternative-network-deployments. Mitar review,
>> question #8: Mesh routing protocols
>>
>> Hi!
>>
>> This is my take on improved routing protocols section:
>>
>> 7.1.2.2.  Mesh routing protocols
>>
>> A large number of Alternative Networks use a customized version of the Optimized
>> Link State Routing Protocol (OLSR) developed by the olsrd open source project
>> (http://olsr.org/).
>> The OLSR protocol defined in [RFC3626] has been extended with the ETX metric
>> (https://pdos.csail.mit.edu/~rtm/papers/etx.pdf) and other features for use in
>> Alternative Networks, especially wireless ones. A new version OLSRv2 [RFC7188]
>> has been starting getting traction in some community networks
>> (https://dl.acm.org/citation.cfm?id=2852742).
>>
>> B.A.T.M.A.N. Advanced (https://www.open-mesh.org/projects/batman-adv/wiki)
>> is a layer 2 routing protocol, which creates one bridged network and allows
>> seamless roaming of clients between wireless nodes.
>>
>> Some networks also run the BMX6 protocol [Neumann_a].
>> The protocol is based on IPv6 and tries to exploit the social structure of Alternative
>> Networks.  In [Neumann_b] a study of three proactive mesh routing protocols is
>> presented, in terms of scalability, performance, and stability.
>>
>> Babel [RFC6126] is a layer 3 loop-avoiding distance-vector routing protocol that is
>> robust and efficient both in ordinary wired networks and in wireless mesh networks.
>
> Thanks a lot!
>
> I have added your new references and rebuilt the text. I have put the reference to [Neuman_b] in the last paragraph, as it talks about Babel.
>
> I have added a reference to a paper about BATMAN advanced. Its first reference points to http://www.open-mesh.org/:
>
> D. Seither, A. König and M. Hollick, "Routing performance of Wireless Mesh Networks: A practical evaluation of BATMAN advanced," Local Computer Networks (LCN), 2011 IEEE 36th Conference on, Bonn, 2011, pp. 897-904.
> doi: 10.1109/LCN.2011.6115569
>
>
> 7.1.2.2.  Mesh routing protocols
>
>    A large number of Alternative Networks use customized versions of the
>    Optimized Link State Routing Protocol (OLSR) [RFC3626].  The
>    [olsr.org] open source project has extended the protocol with the
>    Expected Transmission Count metric (ETX) [Couto] and other features,
>    for its use in Alternative Networks, especially wireless ones.  A new
>    version of the protocol, named OLSRv2 [RFC7188] is becoming used in
>    some community networks [Barz].
>
>    B.A.T.M.A.N.  Advanced [Seither] is a layer-2 routing protocol, which
>    creates a bridged network and allows seamless roaming of clients
>    between wireless nodes.
>
>    Some networks also run the BMX6 protocol [Neumann_a], which is based
>    on IPv6 and tries to exploit the social structure of Alternative
>    Networks.
>
>    Babel [RFC6126] is a layer-3 loop-avoiding distance-vector routing
>    protocol that is robust and efficient both in wired and wireless mesh
>    networks.
>
>    In [Neumann_b] a study of three proactive mesh routing protocols
>    (BMX6, OLSR, and Babel) is presented, in terms of scalability,
>    performance, and stability.
>
>
>    [Barz]     Barz, C., Fuchs, C., Kirchhoff, J., Niewiejska, J., and H.
>               Rogge, "OLSRv2 for Community Networks", Comput. Netw. 93,
>               P2 (December 2015),
>               324-341 http://dx.doi.org/10.1016/j.comnet.2015.09.022,
>               2015.
>
>    [Couto]    De Couto, D., Aguayo, D., Bicket, J., and R. Morris, "A
>               high-throughput path metric for multi-hop wireless
>               routing", Wireless Networks, 11(4), 419-434 , 2005.
>
>    [Neumann_a]
>               Neumann, A., Lopez, E., and L. Navarro, "An evaluation of
>               bmx6 for community wireless networks", In Wireless and
>               Mobile Computing, Networking and Communications (WiMob),
>               2012 IEEE 8th International Conference on (pp. 651-658).
>               IEEE. , 2012.
>
>    [Neumann_b]
>               Neumann, A., Lopez, E., and L. Navarro, "Evaluation of
>               mesh routing protocols for wireless community networks",
>               Computer Networks, Volume 93, Part 2, 24 December 2015,
>               Pages 308-323 ISSN 1389-1286,
>               http://dx.doi.org/10.1016/j.comnet.2015.07.018, 2015.
>    [Seither]  Seither, D., Koenig, A., and M. Hollick, "Routing
>               performance of Wireless Mesh Networks: A practical
>               evaluation of BATMAN advanced", Local Computer Networks
>               (LCN), 2011 IEEE 36th Conference on, Bonn, 2011, pp.
>               897-904. doi: 10.1109/LCN.2011.6115569, 2011.
>>
>> Comparison of performance and stability of routing protocols is an ongoing process
>> and many routing protocols participate in regular event to compare, test, and cross-
>> pollinate implementations at the yearly Battlemesh event (http://battlemesh.org/).
>
> I think this last paragraph does not fit into the document. This is an activity around routing protocols for CNs, which is IMHO out of scope of the document.
>
>>
>>
>> Mitar
>>
>> --
>> http://mitar.tnode.com/
>> https://twitter.com/mitar_m
>
> Thanks,
>
> Jose
>



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