Re: [Bier] One specific transition churn ...

Robert Raszuk <robert@raszuk.net> Sat, 27 September 2014 19:03 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B13441A1B55 for <bier@ietfa.amsl.com>; Sat, 27 Sep 2014 12:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 ne-97-mhjj0S for <bier@ietfa.amsl.com>; Sat, 27 Sep 2014 12:03:25 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25E871A014B for <bier@ietf.org>; Sat, 27 Sep 2014 12:03:25 -0700 (PDT)
Received: by mail-ig0-f169.google.com with SMTP id uq10so182918igb.4 for <bier@ietf.org>; Sat, 27 Sep 2014 12:03:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=e7KbnNZ3GrUat3BlJkcUnn71ttU19BiDmikWgOQGxeE=; b=lHCJD6kOTG0MbzRG0XelmkxpqRF6Wgiat6dCH8e2QRtjKlZwteYCKxi2FUfatnR2a6 iY2jUULxse60dg8YSx/8LVOVNSOwZykCbUzxW/zPipz0jzPAWe3ReGW0X0O6HbXVDntO ag4OKZFe82laTzVk2zNRZjmaUHfkFkY1/+/8GgpCzroyjrHUP40LKpDvEv+BNeXf+8np sPJ5tM/nbBkTBG0v11erBc1jahohCCaX0xQCiDCSz2tODI9HLCGiI0bdfG6gyfVQqoxG KrUAXRx+8+KCf/A+SjXKocjQuGbK736DkYUtwEI37lv3/FOUwvd9pzUbGkin7OFidk9F FjxA==
MIME-Version: 1.0
X-Received: by 10.42.247.137 with SMTP id mc9mr35423658icb.13.1411844604557; Sat, 27 Sep 2014 12:03:24 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.107.166.8 with HTTP; Sat, 27 Sep 2014 12:03:24 -0700 (PDT)
In-Reply-To: <A4C0A0B0-2249-485E-867E-22732EE42320@gmail.com>
References: <CA+b+ERmNEnhTDjPXkAs6vNqC8_UBNid8gFwRsb1aUKZgzDLQLg@mail.gmail.com> <EE6E4363-E19D-44A1-ACDA-6C5A16C41DB3@cisco.com> <2E4BB27CAB87BF43B4207C0E55860F181B5ACF@eusaamb103.ericsson.se> <CA+b+ERkDSxtkX8j9o0AUQw0STPbNjhjr+OFZxDpEy0RkAOx_qg@mail.gmail.com> <DA5C56DD-22F5-4E0C-A7BA-103E84749D69@cisco.com> <CA+b+ERn+5BbucSpOQzv_Wfps7oYbV8RGJfHN4cnMzP4sSSBgxQ@mail.gmail.com> <D04C3174.70BA9%naikumar@cisco.com> <30386970-B544-4BD5-B673-87FB2453F7B9@gmail.com> <2E4BB27CAB87BF43B4207C0E55860F181B5F52@eusaamb103.ericsson.se> <A4C0A0B0-2249-485E-867E-22732EE42320@gmail.com>
Date: Sat, 27 Sep 2014 21:03:24 +0200
X-Google-Sender-Auth: fggkgMQTIQ6hbTapJTewhCBtSbs
Message-ID: <CA+b+ERnJygm1zFT9GL0OaXJU8+4HTNC_GNV+xrV5S5f4A0HYfw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Dino Farinacci <farinacci@gmail.com>
Content-Type: multipart/alternative; boundary="20cf3005db1a220201050410b00e"
Archived-At: http://mailarchive.ietf.org/arch/msg/bier/uMCASYuc9SCydYhnYz7Kt9wUI34
Cc: "bier@ietf.org" <bier@ietf.org>, "Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com>, Antoni Przygienda <antoni.przygienda@ericsson.com>, "IJsbrand (Ice) Wijnands" <ice@cisco.com>, "Eric Rosen (erosen)" <erosen@cisco.com>
Subject: Re: [Bier] One specific transition churn ...
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Sep 2014 19:03:26 -0000

> What is being proposed can be done with typical overlay multicast and I
> know the authors are aware of the multicast work done in the LISP WG. When
> you do a true multicast overlay, then you can put the edges ANYWHERE in the
> network because you don't have to change the core AT ALL.
>

​And that IMO would be much better option all together rather then keep
upgrading routers and their OSes all the time :)

Btw while not a BIER question how does LISP m-cast compares with
http://tools.ietf.org/html/draft-marques-l3vpn-mcast-edge-01

​Or for that matter with peercasting ? ​

​- - - ​

​As to BIER how is it suppose to work in say DC environment where I run BGP
and no IGP at all ? Just like described here:

http://tools.ietf.org/html/draft-lapukhov-bgp-routing-large-dc-07

Thx,
​r.​