[Bier] About bierin6 and signalling of encapsulation

Juliusz Chroboczek <jch@irif.fr> Thu, 16 November 2017 14:44 UTC

Return-Path: <jch@irif.fr>
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 AA3C912950B; Thu, 16 Nov 2017 06:44:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 hgAoMZzEOOyy; Thu, 16 Nov 2017 06:44:23 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A5FF12711B; Thu, 16 Nov 2017 06:44:22 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/75695) with ESMTP id vAGEiKFS022570; Thu, 16 Nov 2017 15:44:20 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id B6089EB364; Thu, 16 Nov 2017 15:44:20 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id MbkvgktYLrxM; Thu, 16 Nov 2017 15:44:19 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 964FEEB365; Thu, 16 Nov 2017 15:44:19 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.irif.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.89) (envelope-from <jch@irif.fr>) id 1eFLOt-0003wi-B2; Thu, 16 Nov 2017 15:44:19 +0100
Date: Thu, 16 Nov 2017 15:44:19 +0100
Message-ID: <7imv3m4724.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: babel@ietf.org, bier@ietf.org
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 16 Nov 2017 15:44:20 +0100 (CET)
X-Miltered: at korolev with ID 5A0DA444.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5A0DA444.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 5A0DA444.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/UHcDjg73RuDGAKccEwdByUVfIIo>
Subject: [Bier] About bierin6 and signalling of encapsulation
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 16 Nov 2017 14:44:25 -0000

Hi,

Crossposted between BIER and Babel.

Thanks a lot to Sandy for presenting bierin6 this morning at the Babel
meeting.  I asked a question about how encapsulation is signalled, and
Tony answered it doesn't matter.  He's probably right, but I need an
explanation.

Suppose a BIER router A has a neighbour B.  From the routing protocol, it
has learnt that frames with a given bit index set are to be forwarded to
B.  How does it know which among the different BIER encapsulations to use
in order to send its BIER frames to B?

I'm probably missing something, but I only see three solutions:

  1. statically configured (e.g. a given BIER domain is statically
     configured to use a given encapsulation);

  2. carried by a specific signalling protocol (call it the BIER Hello
     Protocol for now);

  3. carried by the routing protocol (e.g. carried by a sub-TLV of the IHU
     TLV in Babel, or using RFC 5613 signalling in OSPF).

So what's the vision here?

-- Juliusz