IETF Logo Mail Archive

Re: [MBONED] [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> Fri, 21 October 2022 16:18 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 DBFCCC14CE25; Fri, 21 Oct 2022 09:18:23 -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_DNSWL_NONE=-0.0001, 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 UJHssiZqK6-W; Fri, 21 Oct 2022 09:18:22 -0700 (PDT)
Received: from mail-vk1-xa2c.google.com (mail-vk1-xa2c.google.com [IPv6:2607:f8b0:4864:20::a2c]) (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 02DDFC14F693; Fri, 21 Oct 2022 09:18:21 -0700 (PDT)
Received: by mail-vk1-xa2c.google.com with SMTP id h25so1691468vkc.6; Fri, 21 Oct 2022 09:18:21 -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=1qv15YduG6UcaTzCMCem7QG+3IAVah++hZwYrzSIkWI=; b=QKU4x88OpFNU27wSq59kN/Q96l1morXNqAXirN9Ynro89MPW7MrnAjrLKYXD51Fav6 rFRyFyKGWkVj44TCU216WX7KI9elR0p1cnth18VQ2XgPyiP59SJoTLd0UXpBhN8GNCCF rNquI9Cs9W5S5fHxiQh5/KIb+0fu2nkR2DsnL85s+s8ws7ZSxr+zWHKkeuzcV/G/Ma8Z 15Ppz3dlpFYXbyeJD5zpLK2LCcYNuKMDkSA+HKbn98jGzmKZW7MYQrA5QT8CCcKTWhmE eTifSGluV8wPDfYyhZ+DW6WAJ5/FcNqlOuQBhAgOHhMzwAuGsGkG3mrHpZUe9H57f8EJ 34UA==
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=1qv15YduG6UcaTzCMCem7QG+3IAVah++hZwYrzSIkWI=; b=xvJdVcjOB6Uv+U+pqtB/QeDWr+AKVyDX6Wy/UOqeVbEdwhoF3cHq/ozteZeFZeMMXS ddhDzZ8OhteMg5b8TCaHOltVmsIfBLuIRaAtRazW2ZeivjftZNrt8ckTUqh7KwXtftfX 9SJxbKkwLAPK1JfMrvriHl469aJOyrjdmzi7ELsiRcYUTUA67lS+12L0AgoJCbKSINql lJUlbym5lWWhYLtMVLVltCR8y/VOAfaxfr8V8XYqn5kPgnVUd+cJUV2MDNTdp47cw+IT KsdprpveZW8poZRCFQ3xTFnj6V1xzQ4BQhzHjTxBXCg3RN1ZT1Uvd0cIC11MGIzrP2Y7 4ULg==
X-Gm-Message-State: ACrzQf12Al+HIYiU+As7AhB50bHF0e59KO11tfxUvmKzwPUTwKYNplfU YOAC7A96eGkp2mbLrXVaOSbStx9vkE4=
X-Google-Smtp-Source: AMsMyM4lkf1D9z02gpbuYr24PuTfQ0qM58JkTecoGMWAOlG8vIefwrGhEt+Mz4en0bOsToyEIfDq8A==
X-Received: by 2002:a05:6214:19c9:b0:4b2:fe6f:90f9 with SMTP id j9-20020a05621419c900b004b2fe6f90f9mr17201109qvc.66.1666369090484; Fri, 21 Oct 2022 09:18:10 -0700 (PDT)
Received: from smtpclient.apple ([65.141.155.213]) by smtp.gmail.com with ESMTPSA id t6-20020a05620a450600b006e8f8ca8287sm9837026qkp.120.2022.10.21.09.18.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Oct 2022 09:18:09 -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: <02fc01d8e537$6037c7e0$20a757a0$@chinamobile.com>
Date: Fri, 21 Oct 2022 09:18:07 -0700
Cc: msr6@ietf.org, pim@ietf.org, BIER WG <bier@ietf.org>, mboned@ietf.org, Stig Venaas <stig@venaas.com>, hooman.bidgoli@nokia.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A893DF5-816E-4D09-AAC6-065BBD1BD409@gmail.com>
References: <011701d8e361$88780710$99681530$@chinamobile.com> <D0BA8841-BA90-4DF5-AAE5-A0113D4F17C7@gmail.com> <02fc01d8e537$6037c7e0$20a757a0$@chinamobile.com>
To: Yisong Liu <liuyisong@chinamobile.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/_FRjyY7M1PtnbTLz2ZgVThilAzo>
Subject: Re: [MBONED] [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: Fri, 21 Oct 2022 16:18:23 -0000

> 1. From the view of existing MSR6 TE document, whether 10000 receivers encoded in a packet is acceptable or not depends 

There is no reason that it is acceptable. There is not enough MTU for user data. Its absurd to even consider it.

> on the topology and the encoding method. In my understanding, in a total stateless solution, at least 10000 bit should be used for encoding such a multicast tree in the packet as the header expanse.

10000/8 = 1250 bytes

This is a non-starter of epic proportions.

> 2. From the view of MSR6, we think this is valid scenario for the large network with large multicast trees and we can discuss more efficient solutions based on source-routing.

Right, and the exiting solutions have been proven, grant it with given control-plane complexity, are multi-router distribution trees where branches of the tree aggregate receiver state so per-receiver state need not be stored anywhere in the network. 

Dino

v2.23.0 | Report a Bug | By Email