Re: [Roll-bier-dt] roll-bier-dt

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 19 October 2018 14:54 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: roll-bier-dt@ietfa.amsl.com
Delivered-To: roll-bier-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2BB130EF3 for <roll-bier-dt@ietfa.amsl.com>; Fri, 19 Oct 2018 07:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ESHmbtn_cA6S for <roll-bier-dt@ietfa.amsl.com>; Fri, 19 Oct 2018 07:54:39 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 594D9128D68 for <roll-bier-dt@ietf.org>; Fri, 19 Oct 2018 07:54:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6605; q=dns/txt; s=iport; t=1539960879; x=1541170479; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=DqRV5hHPUjqZVLzAyJRyTYspmoc6KHVVCr3ud5EQT28=; b=BHCxCehgesyNjPIoCUGzntMoV4ZTpE8MeMcQHjWZtELME3Ou6W95vNuL HH1Fs1kHo0/SSWpGi0G55NW8s7QMFZq3xKbvOmRXtD88OyfBR63oV4NO2 CUy7BJT+kLXew06gLDKIZIAipMBZOz3Vrjq0fSpg9ZT9KvargVPNvNeot s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAAAo78lb/51dJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBggRmfygKjAOMG4INlw+BegsBARgLhEk?= =?us-ascii?q?ChQYhNA0NAQMBAQIBAQJtHAyFOQEBAQEDAQFsCwwEAgEIDgMEAQEBLicLHQg?= =?us-ascii?q?CBA4FCIMaggEPqCKEPkCFFQWLTxeBQT+BEAGDEoMbAQEDAYIDhTQCjwaPOwk?= =?us-ascii?q?ChlyKBh+BT4RziWeMVIlXAhEUgSYdOIFVcBU7gjgBM4ImF4NIhRSFPm+KJoE?= =?us-ascii?q?fAQE?=
X-IronPort-AV: E=Sophos;i="5.54,400,1534809600"; d="scan'208";a="188561702"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Oct 2018 14:54:38 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id w9JEsc6g029531 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 19 Oct 2018 14:54:38 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 19 Oct 2018 09:54:37 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1395.000; Fri, 19 Oct 2018 09:54:37 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Toerless Eckert <tte@cs.fau.de>
CC: Carsten Bormann <cabo@tzi.org>, "roll-bier-dt@ietf.org" <roll-bier-dt@ietf.org>
Thread-Topic: [Roll-bier-dt] roll-bier-dt
Thread-Index: AQHUZ1dbfwgsNafB9kasc1tfRmIiS6UmYx4AgABugAD//68ncIAAX54A//+syNCAAF3agP//vQcQ
Date: Fri, 19 Oct 2018 14:54:10 +0000
Deferred-Delivery: Fri, 19 Oct 2018 14:54:08 +0000
Message-ID: <10af6194e1da417da0f3e682d361f9dd@XCH-RCD-001.cisco.com>
References: <20181019025623.v5da76qrnakohlef@faui48f.informatik.uni-erlangen.de> <61CE8F7B-C12B-4B13-8B48-B199370AC4AB@tzi.org> <20181019122120.qviq46ec5akddel6@faui48f.informatik.uni-erlangen.de> <3d9ffd3c1e704f1db578222750ecf8b3@XCH-RCD-001.cisco.com> <20181019131412.lmqn4xp2frdjddvh@faui48f.informatik.uni-erlangen.de> <2313ec2f4a204e338747119a6e963165@XCH-RCD-001.cisco.com> <20181019135215.fxysqsnmyi4miakl@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20181019135215.fxysqsnmyi4miakl@faui48f.informatik.uni-erlangen.de>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.228.216.26]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll-bier-dt/LD63C36UMxQaR1CdzMgAo58lHz4>
Subject: Re: [Roll-bier-dt] roll-bier-dt
X-BeenThere: roll-bier-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "ROLL WG Design Team for bitstring addressing. See https://trac.ietf.org/trac/roll/wiki/roll-bier-dt" <roll-bier-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll-bier-dt>, <mailto:roll-bier-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll-bier-dt/>
List-Post: <mailto:roll-bier-dt@ietf.org>
List-Help: <mailto:roll-bier-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll-bier-dt>, <mailto:roll-bier-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2018 14:54:42 -0000

Please consider this then :)

https://datatracker.ietf.org/doc/draft-thubert-6lo-bier-dispatch/

take care,

Pascal

> -----Original Message-----
> From: Toerless Eckert <tte@cs.fau.de>
> Sent: vendredi 19 octobre 2018 15:52
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>
> Cc: Carsten Bormann <cabo@tzi.org>rg>; roll-bier-dt@ietf.org
> Subject: Re: [Roll-bier-dt] roll-bier-dt
> 
> On Fri, Oct 19, 2018 at 01:20:11PM +0000, Pascal Thubert (pthubert) wrote:
> > Sure, but the mystery to me is what goes transported with BIER.
> 
> As said, BIER proper can encapsulate anything deemed important enough to get
> a code point in the BIER encap. I am saying "proper" because ROLL may not
> want to take RFC8296 given the likely competition with 6LowPan.
> 
> > Because that is the heart of the problem we are facing in this DT.
> > If BIER transports a same IP packet to multiple destinations, then they must all
> accept the same packet.
> 
> More a property of the larger clas of multicasting overall assuming tojust copy
> the payload - and not to modify it.
> 
> I thought we had killed in last weeks meeting the idea of trying to come up with
> a mechanism that manages to use packet replication (BIER) and then modding
> received copies to fake different per-receiver IP unicast packets
> - because of the problem of making this architecturally work well with higher
> layers like UDP that also have a notion of an IP (pseudo) header.
> Too much faking needed. At least thats what i tried to summarize in my slides.
> 
> Aka: We use BIER-TE for unicast packets but then the expectation is that there is
> just one destination, and the whole purpose of BIER-TE is not replication but
> source routing. And we use BIER-TE(/BIER) for IP multicast packets where there
> can be 1 or more destinations.
> 
> [ Of course there are fun extensions later, e.g.: a unicast packet could  still be
> sent to redundant nodes sharing an IP adddress and therefore  able to
> receive/process the same packet, but i think thats less likely  something one
> would do in a ROLL domain. ]
> 
> > Moreover, if the destination is not the router indicated by the bit
> > but a neighbor or a set of neighbors to that router, then the inner
> > packet must indicate that.
> > All in all, that tells me that the transported packet is IP multicast.
> 
> Yes, we have two layers. The BIER layer that only reaches nodes with an
> assigned BIER bit, and they can communicate potentially any payload across
> BIER, IP or other. And then on top of that there is IP multicast between the BIER
> edge nodes and IP unicast/multicast only nodes. The pictures in the slide deck
> posted intend to show that (that IP multicast building block picture still TBD).
> 
> > What do I miss?
> 
> I think primarily me wanting to figure out the encap we use within the BIER-
> ROLL domain: RFC8296 vs. 6LowPan+extensions.
> 
> Cheers
>     Toerless
> 
> > Take care,
> >
> > Pascal
> >
> > > -----Original Message-----
> > > From: Toerless Eckert <tte@cs.fau.de>
> > > Sent: vendredi 19 octobre 2018 15:14
> > > To: Pascal Thubert (pthubert) <pthubert@cisco.com>
> > > Cc: Carsten Bormann <cabo@tzi.org>rg>; roll-bier-dt@ietf.org
> > > Subject: Re: [Roll-bier-dt] roll-bier-dt
> > >
> > > On Fri, Oct 19, 2018 at 12:36:06PM +0000, Pascal Thubert (pthubert)
> wrote:
> > > > Hello Toerless:
> > > >
> > > > Well, there is as Carsten says a multicast support for RPL storing
> > > > mode, but not
> > > for non-storing. This is where Carsten's draft comes in to play.
> > >
> > > Sure. As said, i may not have correctly captured what Mcr was
> > > explaining,
> > >
> > > > In normal BIER, the bits indicate the routers, don't they? So
> > > > there's an IP
> > > packet inside, correct, like in my tunnel mode? But then I expect it
> > > is the same packet for all destinations. So how does htat work, is
> > > it a mcast packet or do all the destination have a same IP address?
> > >
> > > "Proper BIER" (TM) (the stuff done by BIER-WG) has defined its own
> > > encapsulation header (RFC8296) that sits on top of MPLS or ethernet
> > > and that has its own next-proto field/registry, so it can be
> > > followed by IP or anything else that BIER-WG feels deserves a code point in
> that registry.
> > >
> > > Cheers
> > >     Toerless
> > >
> > > > Pascal
> > > >
> > > > > -----Original Message-----
> > > > > From: Roll-bier-dt <roll-bier-dt-bounces@ietf.org> On Behalf Of
> > > > > Toerless Eckert
> > > > > Sent: vendredi 19 octobre 2018 14:21
> > > > > To: Carsten Bormann <cabo@tzi.org>
> > > > > Cc: roll-bier-dt@ietf.org
> > > > > Subject: Re: [Roll-bier-dt] roll-bier-dt
> > > > >
> > > > > That was me taking notes what Michael said, and maybe i didn't
> > > > > transcribe it correctly. Hope Michael is subscribed here to answer.
> > > > >
> > > > > I think i was more wondering about the suport of compressed IP
> > > > > multicast headders in 6LowPan because that is unclear to me and
> > > > > we probably need to take one of the DT meetings to detail more
> > > > > what extensions we need to do for 6LowPan to support BIER.
> > > > >
> > > > > Cheers
> > > > >     Toerless
> > > > >
> > > > > On Fri, Oct 19, 2018 at 07:45:50AM +0200, Carsten Bormann wrote:
> > > > > > On Oct 19, 2018, at 04:56, Toerless Eckert <tte@cs.fau.de> wrote:
> > > > > > >
> > > > > > > https://raw.githubusercontent.com/toerless/roll-bier/master/
> > > > > > > note
> > > > > > > s/18
> > > > > > > 1017-roll-bier-notes.txt
> > > > > >
> > > > > > What do you mean with ???RPL does not support multicast.????
> MOP=3?
> > > > > > (That is of course storing mode only, and storing mode
> > > > > > doesn???t exist :-), so
> > > > > you have a point.
> > > > > > That???s why we did ccast, to fill in multicast for
> > > > > > non-storing
> > > > > > mode.)
> > > > > >
> > > > > > Grüße, Carsten
> > > > >
> > > > > --
> > > > > ---
> > > > > tte@cs.fau.de
> > > > >
> > > > > _______________________________________________
> > > > > Roll-bier-dt mailing list
> > > > > Roll-bier-dt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/roll-bier-dt
> > >
> > > --
> > > ---
> > > tte@cs.fau.de
> >
> > _______________________________________________
> > Roll-bier-dt mailing list
> > Roll-bier-dt@ietf.org
> > https://www.ietf.org/mailman/listinfo/roll-bier-dt
> 
> --
> ---
> tte@cs.fau.de