Re: [babel] About BIER in Babel

Dave Taht <dave.taht@gmail.com> Tue, 28 March 2017 21:48 UTC

Return-Path: <dave.taht@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A678129A2E for <babel@ietfa.amsl.com>; Tue, 28 Mar 2017 14:48:35 -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 6QGpp3aBwWvp for <babel@ietfa.amsl.com>; Tue, 28 Mar 2017 14:48:33 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 76371129686 for <babel@ietf.org>; Tue, 28 Mar 2017 14:48:33 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id r142so49079960qke.2 for <babel@ietf.org>; Tue, 28 Mar 2017 14:48:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=/gaNlsemFuKQGivgha7oUePt2FnIo8jF8j0f3cG05Rs=; b=kpLTbQeRWLvfdGDmjKwVyBL7MpMBmJsvT24K0+8o/Xuof93TfWHMfPPSXbX5v0MOcE 4jIcoWQ9hjv5Tbt2DSuoFQC62P0YqvPYEs5O+ojlVUTNk2pbMTp4rb+yLspuRMM6ARuo KAF1Ei3otQE0P4w5yy4lvn29Ye3NSmUeBEwsmmgpiuVJd6CMT9FXOeLcxlTxACTS3Ldb +jW3EthBUF+SBG+cZCHDPu1e/4WV1rc/PVU43dUBhhiUj1NUfD7azIbO8yjtwZbRosna 4fmJZQRCB+FPwyT3dkcS8RsnYupxt8nluqAZ7EM5yR7/S+F6lBzDonz/XKT8emLgQqsW 3aKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=/gaNlsemFuKQGivgha7oUePt2FnIo8jF8j0f3cG05Rs=; b=lrxcSIt0leFQUWLEyot+1NeA83iKvVh4Pi7ySkYm+dhR3iuBVRsyuLfLQGuYw/S8iR CsshyntSXhcCMtDnP0ZmS1m742+DnLFJREP22o4JPRaE10irtwXbKZ7Ka5hc+tWpsjAF XPwq6q6xOXjXyqoH96G8q3Qev04LqQyeiqo4Yqc/5nf6cYpRg6KYFRoW4YChfELSH+J1 68UdxJq5b6s8tHYkCPbVfTHBNHnj4LmgRwVvqypVbL9pHmLDdM4YL+1oMlk3akUBhPGg PukbJRQcA9xiHoa59Ct9zz+k7IGyauaAdvKne43CtWaLHCT9kVyE13GuzfBdDDgLLt7l e+Ww==
X-Gm-Message-State: AFeK/H3h2/ddtUvEiMI0EtelczkfpyIQZfT1BF0ZLcItBBkecXJsZBd2NhkaSqQKNjKlibEd7wLMtCtoBQfKGA==
X-Received: by 10.55.19.83 with SMTP id d80mr29067852qkh.196.1490737712586; Tue, 28 Mar 2017 14:48:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.140.8 with HTTP; Tue, 28 Mar 2017 14:48:32 -0700 (PDT)
In-Reply-To: <87shlxyvqe.wl-jch@irif.fr>
References: <87shlxyvqe.wl-jch@irif.fr>
From: Dave Taht <dave.taht@gmail.com>
Date: Tue, 28 Mar 2017 14:48:32 -0700
Message-ID: <CAA93jw6Gnv5GKDO0L-JpawK+Ev2Kci6VDAdBe7bG0Thvm7i5yQ@mail.gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: zhang.zheng@zte.com.cn, Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/NXI4e0Jz4ML-2OK0k_08mcTCGMg>
Subject: Re: [babel] About BIER in Babel
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 21:48:36 -0000

... up until this moment I was mostly ignorant of bier. I may well
still be overly ignorant, but read on.

On Tue, Mar 28, 2017 at 1:47 PM, Juliusz Chroboczek <jch@irif.fr> wrote:
> Dear Sandy, dear all,
>
> I think there are very good reasons why it would be interesting to
> experiment with BIER and Babel.  As you explained, there are at least two
> approaches worth considering:
>
>   - announce BIER routing directly in Babel, as your draft suggests;
>   - use MLD with Babel.
>
> I am not competent to judge which approach is suitable, but it is clearly
> attractive to run a single protocol.
>
> As I mentioned at the mike, there are a number of problems with your
> encoding.  My personal intuition would be to use a new AE number for BIER,
> but of course someone would need to write it down and check the details.

However, leveraging this encoding over the others in the core draft seems
straightforward to encapsulate into an ae with no afteraffects
elsewhere in babel.

https://datatracker.ietf.org/doc/html/draft-pfister-bier-over-ipv6

4096 bits (maximum requirement for bier), on the other hand, breaks
everything (babel mtu requirement while still fitting in everything
else),

while (the minimum requirement) of 256 bits may well look a lot like
how the new source specific ae is formed.

if there are other docs in that wg worth reading, running code on
linux, or other use cases, please point me at em!

> As David mentioned, some of us would feel much more comfortable if there
> were a prototype implementation before we are asked to adopt your draft.
> I would be interested in helping, but I have neither the competence nor
> the manpower to do the implementation on my own.
>
> -- Juliusz
>
> _______________________________________________
> babel mailing list
> babel@ietf.org
> https://www.ietf.org/mailman/listinfo/babel



-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org