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> Thu, 03 November 2022 22:35 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 21970C14F74C; Thu, 3 Nov 2022 15:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable 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 kpqXp4sZ39TB; Thu, 3 Nov 2022 15:35:47 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 D352AC14F726; Thu, 3 Nov 2022 15:35:47 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id d10so2942198pfh.6; Thu, 03 Nov 2022 15:35:47 -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=ORI9d2qAwE3g0Pb63/FUhmu64KGmcGugO52AyfdEF+0=; b=kq6WA658lWqAg73J2bY1N212iS9x7/RreCZVtCrwZyhY9I0GrTPSgMNnMhe/+ffQon HcKGybIfPXvdfmNi73LuNAdHf1qaUqIwvSdROEi/qyOq3p6GX/ak7QOQcT+OFdFGAUks 2JIPKAFKRyO1vapmhUyLgJ215XE1CJXwREGIcDGFgHCEtrp0fjJdtffaPsMdCS58JXqo 7Ty3utfsYxFqDBwjth036y3JtWKcmWhanJUijLghbokJmx5WtPutgBERLp46EEdYsbEo +Ll4gl/UL1BcVXulOUNVdjol4I1GL/IH4w/wzWsEekuF1+0fOM5SN5IjcEiM8cda9loE OFTg==
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=ORI9d2qAwE3g0Pb63/FUhmu64KGmcGugO52AyfdEF+0=; b=D6lPYlAyKTTYgGcDv0N7RYFqluN4XFQCO1+ZqnnCuh+7C8+R8tLNO7bDW/a7HMv04Z o27GJOqBNw35oAdfZyWigBDmi2TedpfaeXbncMZOHORtUEM91RmPl77KH2WxCtX/8eAe 8kU1TeFw+ybifQLc8fXAQ7wv8CYsnRJzwiSEOpcHa02opdozYaNzdJ6sqTRldre+VPtj JYABY3gIb22dJMwEqe0SjEXpFKNA/ZCWqqiCYSi9eX+zdwpwtvgy2Ub/0JPc30nN4nPa L/1Bj2j/ofRBDUDaHrv1QB/m2BUDMyx+YiGzpzJyu7Rgo4OBcgG7pmLggq1RsaqdsH66 P9MA==
X-Gm-Message-State: ACrzQf09Xd0Wr/b6/M4qsiyW+nvwULiAoD5513A4y9JUflPFCg2nkif9 KvAhMJ41bXM60n5zt/tAAN7HI1/WI0Q=
X-Google-Smtp-Source: AMsMyM7xEuJ80EbfBTkKcOuQey5DA8F4XYt7nL5ChlZ7aoHPiPhC/uSzKSlfqaPRVLicIQyriLt2sw==
X-Received: by 2002:aa7:8e9e:0:b0:56b:bbca:dd98 with SMTP id a30-20020aa78e9e000000b0056bbbcadd98mr32701088pfr.7.1667514947300; Thu, 03 Nov 2022 15:35:47 -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 u2-20020a1709026e0200b0017a032d7ae4sm1188908plk.104.2022.11.03.15.35.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Nov 2022 15:35:46 -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: <59db81efd80b475b976016dd19423eec@huawei.com>
Date: Thu, 03 Nov 2022 15:35:45 -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: <D7874563-FE5F-405D-AF2C-003E1C9CD5FF@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> <A4F29DF0-147E-43A2-B8FF-E63A3D964FDC@gmail.com> <59db81efd80b475b976016dd19423eec@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/lzxgTwd9guQBSLm-W1lquZrPgE4>
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: Thu, 03 Nov 2022 22:35:52 -0000

> We have that with PIM and a boat load of hardware that supports RPF based forwarding (ditto for Bidir-PIM forwarding).
> 
> [Xuesong] Do you mean that RPF could bring more security through mechanism like " Source address verification"? 

I am saying that if you are going to require new hardware for a new forwarding plane, the problem you want to solve must be compelling. And I think existing methods DO work.

> 
>> 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.
> 
> [Xuesong] I think "host-initiated multicast" doesn't mean that the host could send the packet to any receiver it want. The 

I don't know what your reference to "host-initiated multicast" means. It sounds like it is something new you are referring to. But hosts have always sent multicast packets.

> receiver of the multicast should be determined by the application layer (e.g., http request with the same content requirement) or a controller could gather the information about which receivers want the same content.

Yes and that happens today and hence signals the lower layer IGMP/MLD protocol to send a "join signal" on the network.

Dino