IETF Logo Mail Archive

Re: [MBONED] [Bier] [Msr6] MSR6 BOF 3rd Issue Category: More details are requested about the large scale use cases, including issue 8-11

Dino Farinacci <farinacci@gmail.com> Tue, 01 November 2022 21:12 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 450D1C14CF17; Tue, 1 Nov 2022 14:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4twmOoevFZt; Tue, 1 Nov 2022 14:12:15 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0781C14F74C; Tue, 1 Nov 2022 14:12:15 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id p3so14723943pld.10; Tue, 01 Nov 2022 14:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=apnsoCM9mIFS6fetlVQ38ae025L7i2kveu8zmf02MVM=; b=jilIaHycDUefrZWPXMnBP4ClOlfXyGjXF9TkcVwbmHvuo3JoKCEiuuZFbO1Ds70v78 ZmxeWfA/Kl2Kl+sLJf1J6FNdeqWcu0ijIwsqVXj8TmsMhxGVHoLnoh0wDzUJlZxU70Nt 93BoQDC2+qAoAXLiTqo0jfRw29kxWrSgnjW0Le9unWTzHLes0fWgatSFvAcqfMTCJE6c PlfitFRtUOeLTLD7O9xEX9VA1xY9+6/zSqR/mZ4b9+7r4Pim2w9vud22nEdcZS9ih7ko 7KtNyVukvv3qm1W98S8TLH91wc+RTzcffVYSWGQfD7rrHYbV0QFm1rSLd0KRAJaATqs1 z3Zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=apnsoCM9mIFS6fetlVQ38ae025L7i2kveu8zmf02MVM=; b=Sn4hsJY7fQ36g0IoiJs4HYhGxvDMR1WFNXGRn0cjt06h+PKwBmiYaxYZNQLXyMzNgP zUWhvNI5WjBp3uVCVN+gKZXlgrJNmkyJwQkWdQGNhKArKBJa4Dz2AGl+Xb0Q1EES3qR8 /nrGxQdyoqYCGzdUqxeZL1a5XBWhJVqsErcCMIkeqyOxQmWJfPVeeGJrjywF8nvjd8ZU qUcsvThtI9G3NC9YIgGWk+CUByXoy1LtF6JaowphGG7NPEnC2bzwOLQ5Es3dOA1mRqWt ixfEb8cPrc4XDc9j8cKV0tQtVE1YpsLvdOaC0SmF4ylU3nX3n2fhNPKIoTabD9A+J8LN 23mg==
X-Gm-Message-State: ACrzQf1tytNU5wjkYwkcu7ZSK05o65hpDKLJGdRisnnPbTbOhzIaa7vb evYiER5JjuBJdNPlMkiyvuY=
X-Google-Smtp-Source: AMsMyM690UGM8DY2GxCDih7o7FYGs9OSfbK474mz5whkD7497pPqf9NpyrmOMURamZab8frbvWUXnQ==
X-Received: by 2002:a17:90a:1c02:b0:1e0:df7:31f2 with SMTP id s2-20020a17090a1c0200b001e00df731f2mr38243477pjs.222.1667337135107; Tue, 01 Nov 2022 14:12:15 -0700 (PDT)
Received: from smtpclient.apple (c-98-234-33-188.hsd1.ca.comcast.net. [98.234.33.188]) by smtp.gmail.com with ESMTPSA id r2-20020a17090a560200b002008d0e5cb5sm695820pjf.47.2022.11.01.14.12.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Nov 2022 14:12:14 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <c8fef4dfda8840d898b3bc01262ce97b@huawei.com>
Date: Tue, 01 Nov 2022 14:12:12 -0700
Cc: Toerless Eckert <tte@cs.fau.de>, Jeffrey Zhang <zzhang@juniper.net>, "Xiejingrong (Jingrong)" <xiejingrong=40huawei.com@dmarc.ietf.org>, BIER WG <bier@ietf.org>, "msr6@ietf.org" <msr6@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4F29DF0-147E-43A2-B8FF-E63A3D964FDC@gmail.com>
References: <D0BA8841-BA90-4DF5-AAE5-A0113D4F17C7@gmail.com> <02fc01d8e537$6037c7e0$20a757a0$@chinamobile.com> <1A893DF5-816E-4D09-AAC6-065BBD1BD409@gmail.com> <Y1X2kvbLv0qXtD8z@faui48e.informatik.uni-erlangen.de> <DDD735E2-0930-4CB8-8992-E3E74C715D16@gmail.com> <Y1a8+EK9qA2kKDBF@faui48e.informatik.uni-erlangen.de> <03B2B681-FE16-4961-8932-1F3F29932837@gmail.com> <0d2e78fefe9e4cef87c52493b7fefc80@huawei.com> <BL0PR05MB56528FCEF7FDE262F633A24FD4329@BL0PR05MB5652.namprd05.prod.outlook.com> <C10FBD6A-E651-49BB-B2EC-0C04FC966C4A@gmail.com> <Y1/nUmnoYQhTn7OO@faui48e.informatik.uni-erlangen.de> <15F231E4-1D93-4531-AEA1-B4DC06F25A69@gmail.com> <c8fef4dfda8840d898b3bc01262ce97b@huawei.com>
To: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/a_OZzbqdtWP3QmFPMMowecHGF1U>
Subject: Re: [MBONED] [Bier] [Msr6] MSR6 BOF 3rd Issue Category: More details are requested about the large scale use cases, including issue 8-11
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2022 21:12:16 -0000

> [Xuesong] I think it is necessary to emphasize that using MSR6 will be limited in a controlled domain. 

Don't we have that now with PIM? And we will have that with BIER based on the architectural choices.

You need to do better to get people to take this seriously.

> For example, in the host-initiated case, we focus on enterprise scenario where both host and network device are under the same operating entity.

We have that with PIM and a boat load of hardware that supports RPF based forwarding (ditto for Bidir-PIM forwarding).

> But still, security consideration is necessary, maybe referring to the previous experience from BIER and SPRING.

The fact that an Internet host "does not ask for packets", means anyone can send it packets they don't want. 

With explicitly joined trees and IGMP, we default differently with IP multicast. A feature and not a bug.

Dino

P.S. Advice, take the good with the bad.  ;-)

v2.23.0 | Report a Bug | By Email