Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 9CF281A1BCE;
 Mon,  3 Nov 2014 18:18:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001]
 autolearn=ham
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 5B71E_waDL5p; Mon,  3 Nov 2014 18:18:18 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca
 [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 2CD291A1BBD;
 Mon,  3 Nov 2014 18:18:18 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247])
 by tuna.sandelman.ca (Postfix) with ESMTP id 9A95920028;
 Mon,  3 Nov 2014 21:19:54 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179)
 id 12933637F4; Mon,  3 Nov 2014 21:18:16 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1])
 by sandelman.ca (Postfix) with ESMTP id F1BA263740;
 Mon,  3 Nov 2014 21:18:16 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <m0tx2f6ec7.fsf@tzi.org>
References: <m0tx2f6ec7.fsf@tzi.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;
 <'$9xN5Ub#
 z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
 micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 03 Nov 2014 21:18:16 -0500
Message-ID: <8226.1415067496@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/hTMsPRCohYSSDzy7sU5h82wOhfw
Cc: Andrzej.Duda@imag.fr, roll@ietf.org, bier@ietf.org, 6lo@ietf.org
Subject: Re: [Roll] [6lo] Source-Routed Multicast
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>,
 <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>,
 <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 02:18:19 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Carsten Bormann <cabo@tzi.org> wrote:
    > In Hawaii, there will be a BOF about a multicast forwarding control
    > scheme where a router on the way prefixes a multicast packet with a
    > special header that tells downtree routers where to forward the
    > multicast =E2=80=94 Bit Index Explicit Replication, or BIER.

    > While BIER appears to be very focused on a carrier or datacenter
    > perspective (see draft-kumar-bier-use-cases and the other
    > draft-*-bier-*), there are applications in constrained node networks
    > that would benefit from source-routed multicast.

I take your point.

    > With its current focus, I don=E2=80=99t think the BIER BOF itself is =
the right
    > place to have a technical discussion about this.

On the contrary, I think it is important at a BOF for this topic to be
brought up, if ONLY for it to be CLEARLY ruled out of scope.

    > There is no ROLL meeting in Hawaii.
    > The 6lo agenda is almost full.

ROLL would have to be rechartered to work on it; this is not to say that th=
is
could not happen, but rather to say that even if we were meeting, discussing
it might be out of scope anyway.

Having said that, this thread is most welcome.

    > Should we do this in a side meeting?  (If we do this before Tuesday, =
we
    > can at least report in 6lo =E2=80=94 if we do it on Sunday, we might =
even have
    > an opinion to air during the BIER BOF.)

I abhor "side meetings" --- either have a proper BOF in a room, or get a
bunch of beers is my opinion.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/


--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVFg3ZYCLcPvd0N1lAQIMlgf9EKuKoUzuLFaam9hhusy+J7IiNSiMxtnV
tCTOl2n/Nd6Ba+lPV7f4U2TzsebUWGBemGkb5//NF4JqfNtVNYJhObtB3MHiNnuE
SldbYiCin4dD4eWPdSseCrTVXd36wnGPtwdgrXGuzQKlfgCiDe/kOYCrxzmTkW4K
vvQsRwf2pw5rVb2E0elmm0KQ3NyO4nB/vaH/7EZ9tS0tz6TGj9VLvvE/iiVmT+Jx
Zbshdb+Csj/jmOqc3EQzAD2wJrmIgXaWI4ML9EblV/LrykXO5CK1Srk82JLsDfE8
gcAj4FzL9cY6beJnBPqaFBw73MPqrWqIAyF7fdns+c5y1qFm8hdErw==
=O2d8
-----END PGP SIGNATURE-----
--=-=-=--

