Re: [Roll] [Bier] Source-Routed Multicast

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 05 November 2014 02:10 UTC

Return-Path: <pthubert@cisco.com>
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 157391A1A25; Tue, 4 Nov 2014 18:10:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.095
X-Spam-Level:
X-Spam-Status: No, score=-15.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 q4LwR_V74l7S; Tue, 4 Nov 2014 18:10:50 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F8CC1A8779; Tue, 4 Nov 2014 18:10:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2898; q=dns/txt; s=iport; t=1415153450; x=1416363050; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ESeaVLb5V2p1wYAUTyV5PoiAaAilDeGrMji6dhkUaWE=; b=YfY7kMqIQ9ge8f/ffm2c02HqmrMW5/J1iGrnSLd8xLXPnFxZyXpxzUtb /ZT58DcJbDaMr02N55oZNPvRx8pEAk2q5Qbb3Md1/E9oB3uznHJirFFM2 liwe6p1dDUcncGfKLwubuBdyHCC0RC79XrlPA37/DBLVdY4GBh9ORe0AE 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAMWGWVStJV2Z/2dsb2JhbABbgw5UWQTOYgqHTQKBGBYBAQEBAX2EAgEBAQQBAQFkBwsMBAIBCBEEAQEBCh0HJwsUCQgCBAENBQiIOQ3GfwEBAQEBAQEBAQEBAQEBAQEBAQEBARMEkDgnMQcGgyeBHgWLPYZkoj+DeGyBBkKBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,316,1413244800"; d="scan'208";a="93427750"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP; 05 Nov 2014 02:10:49 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id sA52AnOg031183 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Nov 2014 02:10:49 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.207]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0195.001; Tue, 4 Nov 2014 20:10:49 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, Carsten Bormann <cabo@tzi.org>
Thread-Topic: [Roll] [Bier] Source-Routed Multicast
Thread-Index: AQHP+Jc6eJPa1iU6+EqbNCABEErj65xRRsVA
Date: Wed, 05 Nov 2014 02:10:47 +0000
Deferred-Delivery: Wed, 5 Nov 2014 02:10:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD848A3F9F5@xmb-rcd-x01.cisco.com>
References: <m0tx2f6ec7.fsf@tzi.org> <C1655E2B-C081-409A-B90D-8288F26394B2@cisco.com>
In-Reply-To: <C1655E2B-C081-409A-B90D-8288F26394B2@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.154.177.243]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/wzdHaU_rMRT2A6qbw41yO2vqp9Q
Cc: "Andrzej.Duda@imag.fr" <Andrzej.Duda@imag.fr>, "bier@ietf.org" <bier@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [Roll] [Bier] 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: Wed, 05 Nov 2014 02:10:52 -0000

State  in BIER (one bitmap per child) is so limited and controlled that a constrained node that cannot do storing may be able to still do BIER. For such devices, we could propose a new mode of operation for RPL that is BIER only, for both unicast and multicast traffic.

If the preferred parent tree is acceptable for downward traffic, the DAOs would percolate up by ORing the bitmaps of the children and passing that to the preferred parent. Decision to forward down to a child (or of a child to process an incoming message) would be a simple AND of the bitmap in the packet and that of the child, regardless of unicast or multicast.

Cheers,

Pascal


> -----Original Message-----
> From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of IJsbrand Wijnands
> (iwijnand)
> Sent: mardi 4 novembre 2014 14:28
> To: Carsten Bormann
> Cc: Andrzej.Duda@imag.fr; roll@ietf.org; bier@ietf.org; 6lo@ietf.org
> Subject: Re: [Roll] [Bier] Source-Routed Multicast
> 
> Hi Carsten,
> 
> The ROLL case looks very interesting.
> 
> Just one clarification, BIER is not Source-Routed multicast. i.e. we don't include
> a list of hops that the packet needs to follow, we only include final destination in
> the form of Bit Positions, and each router along the path does a lookup on the
> Bit Position to determine where the packet is to be sent.
> 
> Thx,
> 
> Ice.
> 
> On 03 Nov 2014, at 15:42, 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 - 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.
> >
> > Several proposals on how to do source-routed multicast in constrained
> > node networks are getting ready for consumption.
> >
> > With its current focus, I don't think the BIER BOF itself is the right
> > place to have a technical discussion about this.
> > There is no ROLL meeting in Hawaii.
> > The 6lo agenda is almost full.
> > Should we do this in a side meeting?  (If we do this before Tuesday,
> > we can at least report in 6lo - if we do it on Sunday, we might even
> > have an opinion to air during the BIER BOF.)
> >
> > Grüße, Carsten
> >
> > _______________________________________________
> > BIER mailing list
> > BIER@ietf.org
> > https://www.ietf.org/mailman/listinfo/bier
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll