IETF Logo Mail Archive

Re: [Bier] WG LC on https://datatracker.ietf.org/doc/draft-ietf-bier-pim-signaling/

Toerless Eckert <tte@cs.fau.de> Fri, 25 October 2019 10:32 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1173112083D; Fri, 25 Oct 2019 03:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.169
X-Spam-Level:
X-Spam-Status: No, score=-3.169 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 7HuQlCn8qFuE; Fri, 25 Oct 2019 03:32:08 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 673641200C1; Fri, 25 Oct 2019 03:32:08 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 1686E548029; Fri, 25 Oct 2019 12:32:02 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0ED9B440015; Fri, 25 Oct 2019 12:32:02 +0200 (CEST)
Date: Fri, 25 Oct 2019 12:32:02 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Stig Venaas <stig@venaas.com>
Cc: BIER WG <bier@ietf.org>, "Cc@i4.informatik.uni-erlangen.de:bier@ietf.org <bier@ietf.org>, " <draft-ietf-bier-pim-signaling@ietf.org>
Message-ID: <20191025103202.GB24806@faui48f.informatik.uni-erlangen.de>
References: <20191024152401.GA24806@faui48f.informatik.uni-erlangen.de> <CAHANBt+VHfBS5WZtthOEOaK_nrRtsUb_w5NnqiUB961e3FP11Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHANBt+VHfBS5WZtthOEOaK_nrRtsUb_w5NnqiUB961e3FP11Q@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/GFx6IY9DPb7YYFkE4swBASL5m44>
Subject: Re: [Bier] WG LC on https://datatracker.ietf.org/doc/draft-ietf-bier-pim-signaling/
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 25 Oct 2019 10:32:11 -0000

Thanks, Stig, that what i was suggesting for enabling ASM without
getting into any of the PIM-SM complexities.

How would we automatically determine the set of all BFR/PIM routers
automatically ? I'd hate to have solutions that only work with an
SDN controller provisioning consistently many parameters if we can
also (hopefully easily) automate it.

Also, it would be nice if we could not only have a single PIM domain
connect via a BIER domain, so that we could also use this for
slices or DC environments where there could easily be multiple instances.

The most logical solution for that seems (to me) to be an IGP
extension that tags onto the existing BIER IGP extensions and
attaches to the BFR extension the information:

  -> This BFR is member in the XXX PIM/BIER domain with label YYY

Then the data packets could use the same forwarding plane encap
as in BIER/VPN, aka: combination of BFR-ID and YYY identifies
an IP Multicast packet for domain XXX.

Cheers
    Toerless

On Thu, Oct 24, 2019 at 10:07:41AM -0700, Stig Venaas wrote:
> Hi
> 
> A couple of quick comments on your email Toerless.
> 
> Using PORT may be a good idea. The join attribute defined here would
> also work with PORT. PIM hellos are not sent over BIER so we have no
> easy way of finding out whether routers support PORT though.
> 
> The draft draft-venaas-bier-pfm-sd-00 has a new solution for how to
> determine whom to join. It would be easy to include capability here to
> determine whether the router supports PORT etc.
> 
> Stig
> 
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier

-- 
---
tte@cs.fau.de

v2.23.0 | Report a Bug | By Email