[Bier] Shepherd’s review of draft-ietf-bier-bgp-ls-bier-ext-07

Gyan Mishra <hayabusagsm@gmail.com> Sun, 18 October 2020 07:07 UTC

Return-Path: <hayabusagsm@gmail.com>
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 274D03A0CCE; Sun, 18 Oct 2020 00:07:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.187
X-Spam-Level:
X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jVF9xOUXSBag; Sun, 18 Oct 2020 00:07:50 -0700 (PDT)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C82F3A0CCB; Sun, 18 Oct 2020 00:07:47 -0700 (PDT)
Received: by mail-vs1-xe36.google.com with SMTP id w25so3904452vsk.9; Sun, 18 Oct 2020 00:07:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=2iaQ11eT2wePUDQrU90jpCuz7xPrt7nZ4USUnicpcA0=; b=Lp9AzW+nqA8hUNcNmBjizaW6+twg6XkkxyCg9THg5U0VsZbbtdABJgroRspggoeS0m vtj8dcFoZ2SMdiiXwXJcjqoWrD4Zs7hQ0YgJAm9xFUnlKrTutR0JvE1A/pyOSf+6WdYq ToVJh0lxaYKvX3pSgD8QfdO4NIHQ2CzIo/lvajNVo/lFFI2Q8rPW4nh+cGlpea+QdDe+ TGLx+Mc4wWSPkMafXUOXljekRcw+9WoCi6jbCPUbGhixHyznLDnaUJ6LQetSEQ8QvzPb EVM3WIkspLBz1yVHEuFfw53ntz8qjp5MnIuzBqPZaW2T6qvtEL3K1AHbsM580QfcdTta jNiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2iaQ11eT2wePUDQrU90jpCuz7xPrt7nZ4USUnicpcA0=; b=GaijF/l5hlxin5/R9bj6vkRaOXIPXiLsJCXiYBzW93OB6P+hmKbMnRL+xLFiJsISsD SneEFWgJpLmLb8Mre/gNWGnUQR5/2AsAyJDELvQOsCtqgpSf+6dnZCsa3cnr+pJz4r3d sHNwfGxTyxsLdwyIVXz/7pakw05Mn1jzjFMfC0VWkLMogyQ3qE23dMAm6oHS16aMqy8U 9WWtjYJp6qsbi0ZrVjU7Vj+M1PEdeewQ/7eQXgje31IefH88sTA9soW77mdm7o+0IFa8 4ePsbh61O9OaVwR4Y5IlFy+RdkriTSGUdn1RfLZE+jRRQNvZkGeAUriSJu5uil+Z3ZKS SMdA==
X-Gm-Message-State: AOAM530EZFhnsh1m9l17uRtgxGyaL30MfX1WrMr8nILkG/j669X8AHv0 4+f+PYr7uMAqRQDRqqMv/GGiGibcsVI2uPRErsRH9f2CZfl6Gw==
X-Google-Smtp-Source: ABdhPJxFJdJwqXFywzErRr2riV+n0afijtbXfg7+4wWNhN3x7cPv4RwhRkLjrM0nN5cU6tqfwFxkUKLef4kcOsOCPEA=
X-Received: by 2002:a67:7dc4:: with SMTP id y187mr5798091vsc.58.1603004865727; Sun, 18 Oct 2020 00:07:45 -0700 (PDT)
MIME-Version: 1.0
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sun, 18 Oct 2020 03:07:20 -0400
Message-ID: <CABNhwV0iak7PxjdR8gF3Lzfbi_QpxynOZDdyX2jx15E_AUi+_A@mail.gmail.com>
To: BIER WG <bier@ietf.org>, BIER WG Chairs <bier-chairs@ietf.org>, "draft-ietf-bier-bgp-ls-bier-ext@ietf.org" <draft-ietf-bier-bgp-ls-bier-ext@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000098514d05b1eca7db"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/ABLUrAd7NNd0jxOK6P8YPBqmucs>
Subject: [Bier] Shepherd’s review of draft-ietf-bier-bgp-ls-bier-ext-07
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: Sun, 18 Oct 2020 07:07:52 -0000

Dear Authors,

Thank you for a well-written succinct document.

I have a few  comments and questions on the use of BGP-LS extension and why
it is necessary for BIER and what gap that exists that is being addressed
by this extension.

What is broken today?

The abstract and introduction describes how BIER works which anyone reading
the draft can read normative references RFC 8279 and RFC 8296.

The last sentence says the following:

This document specifies extensions the BGP Link-state address-family
in order to advertise BIER information.


The last sentence in the introductionstates the following:


In order to satisfy the need for applications that require topological
visibility across one area or Autonomou

System (AS).  This document specifiesextensions to the BGP Link-state
address-family in order to advertise BIER-specific.  An external
component
(e.g., a controller) then can collect BIER information in the "northbound"

direction within the BIER domain.


Section 3 goes on to describe how this new BGP-LS extension for BIER will
be able to gather the BIER specific topology information and send
Northbound to an external controller which will then build rebuild a
topological graph of the BIER domain or multiple domains for multicast
“applications” that won’t work for without this extension.

I think in the draft it is important to note the gap that exists today
without this draft and clearly what is broken that is being fixed by the
draft.

That should be spelled out clearly in the Introduction as well as stated
briefly in the abstract.

Inter-AS BIER trees can be built without a controller and this BGP-LS
extension, similar to today inter-as MVPN mLDP PE P2MP TE stateful
segmented or end to end LSP trees.

I think we need to expand more on the application visibility and what
applications I am guessing ASM, SSM trees over BIER inter-as, but I still
don’t understand the gap as what won’t work with multicast applications
today without this BGP-LS extension for BIER.

Please help me understand.

Also could BIER BGP-LS extension also be used for BIER inter-as
provisioning of stateless tree?

  So possibly be used for instantiation of all inter-as stateless trees
based on the topological graph.  As the BIER trees are stateless in a way
you could pre build all X-PMSI trees set the BFR bitmask for all egress PEs
ahead of time provision inter-as from BFIR ingress domain to BFER egress
domain.

There maybe other use cases or reasons for BGP-LS usage by BIER but I think
provisioning could be one of them.

Once I have received feedback on the comments I will compile the Feedback
and complete the Shepherds write-up.

Kind Regards


Gyan
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD