Re: [Bier] WG adoption call for draft-chen-bier-frr-02

Tony Przygienda <tonysietf@gmail.com> Fri, 26 March 2021 09:17 UTC

Return-Path: <tonysietf@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 9A4803A19AF; Fri, 26 Mar 2021 02:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 v1fYJSGND9DW; Fri, 26 Mar 2021 02:17:29 -0700 (PDT)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 9D8153A19AC; Fri, 26 Mar 2021 02:17:29 -0700 (PDT)
Received: by mail-il1-x12a.google.com with SMTP id y17so4476924ila.6; Fri, 26 Mar 2021 02:17:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rOgmWgO8pZVUZ39yt1jHMrBtnZznRGH/vjEkQMrASIY=; b=H6DL1wjpqshSDOLlqwhyPKgmehs949bOHG0xLEgxJPEy+Pk/YlXScKFPSBH1BOO76C ZM0Ag2AvDraF0ehYec2Q7WMR5gelEbYYo91MCIlVaeDlOlyuvmE4gNpeA29WpXqi8eUc ZbMum6iGktFMXVniDtHUu7se++zct3S6e5yVgtsChjn/mLWTCP9iT5i3SX3+LCxlStgD x3T1nku2ma2+rF4GjdN+ZJY7XAfULoQ6TZpCEnHZDN/tA7MNQkVChe10lkoPVFZ5qOVr Pko5JMSTf+5/zdYtUsyae+Kf/Id0BPMeCK8tZmkCyB5X+dNJbAbD4Q+CtkHcA4KkzL8X 1QXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rOgmWgO8pZVUZ39yt1jHMrBtnZznRGH/vjEkQMrASIY=; b=jGlA6ijUDqFfvrwx3E1OzxDE+Nh8irEnivxqrSvIHKdnrO/Vmi4bTMmW+d65iyxJXH c0SC1kISdQbDZ8MH9aKRfczMjX/ODNwNeq1CQYFZRDoLVcMgmUmTMRL4nvxeD/21BwKr rTOsqy/X8cH0S5bBQFP3oobioix2nKvH6cTW58xlZBKQO1DBdOce0N3Ksxf8gm1PIpZ9 jnQNZW8t+DioU51utscgJkHkuLu06sGopmsBZIP8TnnwhpBSBq2Cg/vE8JxTP7OLm82Q G+HpD2NA0BMxwzV1HrMUVmE53CHCXtTNAiihZeFRCpvthZ/jcUYZOKDWDCxJ7b7oWGzU pApA==
X-Gm-Message-State: AOAM533lVCuYyeRiTu8iitoPcZvqCE8s5ugdqcTZY2ZuY9r8kb9IX87U pQ99ZEazdoMYRc/bh/JYfcY/i020pzwvJPVNhSY=
X-Google-Smtp-Source: ABdhPJzQQEtV/33mFVNaedevIR0bCtR3Hvp3BtF+V/zI+0+NxLlVMTq5UIUQnrn9HTeKij3TDitbnfLn68QdSbgi2mQ=
X-Received: by 2002:a05:6e02:152:: with SMTP id j18mr9910810ilr.302.1616750248018; Fri, 26 Mar 2021 02:17:28 -0700 (PDT)
MIME-Version: 1.0
References: <202103161440487606255@zte.com.cn> <CA+wi2hPLG_Og=rDerVqK7hMjkjUGxzjpQnZMSFMf965UVLCxNA@mail.gmail.com> <MN2PR13MB408751B2E8ACDF05AC9C34B3F2629@MN2PR13MB4087.namprd13.prod.outlook.com>
In-Reply-To: <MN2PR13MB408751B2E8ACDF05AC9C34B3F2629@MN2PR13MB4087.namprd13.prod.outlook.com>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Fri, 26 Mar 2021 10:16:51 +0100
Message-ID: <CA+wi2hOBCCYxwcnTXGeXG9bW=jPXYte1fKy0WNiuRNmVceeUuw@mail.gmail.com>
To: Huaimo Chen <huaimo.chen@futurewei.com>
Cc: "zhang.zheng" <zhang.zheng@zte.com.cn>, BIER WG <bier@ietf.org>, BIER WG Chairs <bier-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000039462105be6d0009"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/VHJD7gkeWOkk-uBiPG7JFvDWNqI>
Subject: Re: [Bier] WG adoption call for draft-chen-bier-frr-02
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, 26 Mar 2021 09:17:35 -0000

Excellent, having authors of multiple drafts in this area co-allesce and
colaborate on a single framework document would be a very positive and
productive development in my eyes. If it explains the IGP model e'one uses
today so far and the architecture kind of implies as default with IGP
signalling, the better.

Discussions around informational/experimental can happen later of course
but generally experimental will introduce the burden of two implementations
most likely (and with that many models that may not be trivial) and of
course experimental is needed in case we end up allocating codepoints or
need to agree on some on-the-wire formats (algorithms are not that clear).
We play it by the ear depending on the scope of the document as it evolves
and content would be my take for now.

thanks

-- tony



On Thu, Mar 25, 2021 at 10:05 PM Huaimo Chen <huaimo.chen@futurewei.com>
wrote:

> Hi Everyone,
>
>     Michael, Steffan, Huaimo and Mike met to discuss the merge and we are
> in agreement that if draft-chen-bier-frr is adopted we will expand it to
> include a framework along with the tunnel and LFA based solutions.
>
> Best Regards,
> Huaimo
> ------------------------------
> *From:* BIER <bier-bounces@ietf.org> on behalf of Tony Przygienda <
> tonysietf@gmail.com>
> *Sent:* Tuesday, March 16, 2021 6:08 AM
> *To:* zhang.zheng <zhang.zheng@zte.com.cn>
> *Cc:* BIER WG <bier@ietf.org>rg>; BIER WG Chairs <bier-chairs@ietf.org>
> *Subject:* Re: [Bier] WG adoption call for draft-chen-bier-frr-02
>
> +1
>
> I think it's a good addition within the architecture for the case IGP is
> not used for signalling, e.g. when controller or static programming.
>
> The draft must however explain in what scenarios it is used and quote the
> according IGP drafts to guarantee loop-free behavior (well, BIER will
> tie-break loops but we'll have 1x microloop & possibly not deliver payload
> if BIER FRR is not properly computed/intsalled). With that the draft should
> also pay attention to how the function is deployed/updated network-wide if
> IGP is not present
>
> thanks
>
> -- tony
>
> On Tue, Mar 16, 2021 at 7:41 AM <zhang.zheng@zte.com.cn> wrote:
>
> A 2-week WG adoption call begins for the following draft:
>
> https://datatracker.ietf.org/doc/draft-chen-bier-frr/
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-chen-bier-frr%2F&data=04%7C01%7Chuaimo.chen%40futurewei.com%7C79ac63710b47427a558d08d8e8638df2%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637514861570555970%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DiHvux0ZUYEJru10lVQ4mXvpYx3l8ujGInm7uEjjxTw%3D&reserved=0>
>
> Please indicate your support or objection by March 30th, 2021.
>
> Authors, please respond to the list indicating whether you are aware of
> any IPR that applies to this draft.
>
> Thanks,
>
> Sandy (As WG secretary, on behalf of Greg/Tony)
>
>
>