Re: [Roll] [Bier] Source-Routed Multicast
IJsbrand Wijnands <ice@cisco.com> Tue, 04 November 2014 22:28 UTC
Return-Path: <ice@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 216BA1A0195; Tue, 4 Nov 2014 14:28:18 -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 CDy_dwAmPZBW; Tue, 4 Nov 2014 14:28:15 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B5F81A0151; Tue, 4 Nov 2014 14:28:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1697; q=dns/txt; s=iport; t=1415140096; x=1416349696; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=9pcVRDWwKSx5jvh/X3Zn/4Qxs4+vSAFLwiDAtnTOX6E=; b=FW1xzN8H41ggRY+e9FNfRXfPGx0ZtmQNDC6dhE9G2NToTPsNRuGFcQPq uefJZ4dAg/BZcnOlfztkFE7/lhSOEf2wRtFZG0jsWGQjNy1s20oW70e1o cqt99mBPmUov/csAu08dqOQgY83lKSDjA7QjhIHv31NXVe3MEO42tcFHx w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoLAAxSWVStJV2U/2dsb2JhbABbgw5UWbsKBQF0kloKh00CgSMWAQEBAQF9hAMBAQMBAQEBZAcLBQsLDjgnMAYTiDgJDcRJAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSGN4omMweDLYEeBYt7khOHdI5ehBkcL4JLAQEB
X-IronPort-AV: E=Sophos;i="5.07,315,1413244800"; d="scan'208";a="369307074"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-8.cisco.com with ESMTP; 04 Nov 2014 22:28:15 +0000
Received: from [10.154.176.153] ([10.154.176.153]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id sA4MSDO4023842 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 4 Nov 2014 22:28:14 GMT
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <m0tx2f6ec7.fsf@tzi.org>
Date: Tue, 04 Nov 2014 14:28:12 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1655E2B-C081-409A-B90D-8288F26394B2@cisco.com>
References: <m0tx2f6ec7.fsf@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/cpMH_X4mkCbkEXcBLicR63BDCnc
X-Mailman-Approved-At: Tue, 04 Nov 2014 17:24:15 -0800
Cc: Andrzej.Duda@imag.fr, roll@ietf.org, bier@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: Tue, 04 Nov 2014 22:28:18 -0000
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] Source-Routed Multicast Carsten Bormann
- Re: [Roll] [6lo] Source-Routed Multicast Michael Richardson
- Re: [Roll] [Bier] Source-Routed Multicast Greg Shepherd
- Re: [Roll] [Bier] Source-Routed Multicast Rajiv Asati (rajiva)
- Re: [Roll] [Bier] Source-Routed Multicast Carsten Bormann
- Re: [Roll] [Bier] Source-Routed Multicast IJsbrand Wijnands
- Re: [Roll] [Bier] Source-Routed Multicast Pascal Thubert (pthubert)
- Re: [Roll] [Bier] Source-Routed Multicast Carsten Bormann
- Re: [Roll] [Bier] Source-Routed Multicast Carsten Bormann