Re: [Dyncast] CAN BoF issues and the next steps

Tony Li <tony.li@tony.li> Wed, 13 April 2022 17:04 UTC

Return-Path: <tony1athome@gmail.com>
X-Original-To: dyncast@ietfa.amsl.com
Delivered-To: dyncast@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E078E3A197E for <dyncast@ietfa.amsl.com>; Wed, 13 Apr 2022 10:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.512
X-Spam-Level:
X-Spam-Status: No, score=-6.512 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gXU9xl_ZulUI for <dyncast@ietfa.amsl.com>; Wed, 13 Apr 2022 10:04:11 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 E91B93A197D for <dyncast@ietf.org>; Wed, 13 Apr 2022 10:04:10 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id t13so2349498pgn.8 for <dyncast@ietf.org>; Wed, 13 Apr 2022 10:04:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=5KJ9Q5/nRUD8veBDIPg5ITfIilLOhQILH7bsjkXH1/o=; b=QhtlM5h2cf7NhvwFuQ6upmSxjL4+3KwVWvuK9RzyBSBYofTeKwhRMpCcyrsrCj1u4G z46m9cvQQsX5nMpEW4rv9CcXfm2kO/aSSYffoRJZX2l9foJIi/Mz00R45EI1E2Q9uTOa RsTcO6Jpsa8HhQZs7x1osFR/F1KOO6P0hohKsyMatx8ouUcPxi5MILvhZQEguXlbcu95 YwxIokPGjApZ1zaxPAczT65q7rJ2T45yi0vsfYyeSsnXSBtzzUO5/QGIENCe109ZK86p iVZ9PiIKA/uiBNKfxx9rFGvRpxdohmzttFvZ4MbYcDEC1CtqKKOVa1TrlHhIuJ+fcwiT JyIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=5KJ9Q5/nRUD8veBDIPg5ITfIilLOhQILH7bsjkXH1/o=; b=Anpt/g3mjTPxwWoS/pQlx7cm/5bKNocg9yoxmv2lJU02Y7BXtBYQLsKXuHY3Hrpr9x XxLK+iIGxYLBXs2uvrlegZf4hLbtuEpQXX7S6ywotnxXmcdrA2YSzchfrGslWEsiuhOG UGgXcBiiNv0QJZy+AS9X4cXEH7Y4ExCu6CmZ7x4ekgznv/ckGiXJiJYg51b2IkASapxz kYYxKzeW1hYZfwzP9F8zsXyF+HxHeyUJ/HtdOguB7ICjtDVf/m/pdMeOPS+iwmp/hyxj H6gWWqEYsR5IaL7Co/4UawpRptFkYRMrWUlDibZD/ClsTTdcUNou79kR48QlaTE/H43J kiqA==
X-Gm-Message-State: AOAM530dQ04i3LDugy9M5xzPryXhE1oio9aPX6dDnYRuwHbvRx8k2AeI lW958Y/uSeMo7LoQJjix4Y4=
X-Google-Smtp-Source: ABdhPJzkZXCJZHTjdILCxYQLQl6aFQWdNeqMndjlghrV31zCbcZwH7Qsl0s2sbkGMByOFtPgkvajoA==
X-Received: by 2002:a63:5310:0:b0:39c:f338:407e with SMTP id h16-20020a635310000000b0039cf338407emr24508224pgb.600.1649869449650; Wed, 13 Apr 2022 10:04:09 -0700 (PDT)
Received: from smtpclient.apple (c-67-169-103-239.hsd1.ca.comcast.net. [67.169.103.239]) by smtp.gmail.com with ESMTPSA id g6-20020a056a001a0600b004f7bd56cc08sm42967459pfv.123.2022.04.13.10.04.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Apr 2022 10:04:09 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: Tony Li <tony.li@tony.li>
Message-Id: <60C73939-8830-478B-B2ED-46919123B24D@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9255C989-3AC6-4B66-9634-81A00302DA96"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Wed, 13 Apr 2022 10:04:08 -0700
In-Reply-To: <CO1PR13MB49206621FB31FB80BBBA2B8B85EC9@CO1PR13MB4920.namprd13.prod.outlook.com>
Cc: "liupengyjy@chinamobile.com" <liupengyjy@chinamobile.com>, dyncast <dyncast@ietf.org>, Aijun Wang <wangaijun@tsinghua.org.cn>, Luigi IANNONE <luigi.iannone=40huawei.com@dmarc.ietf.org>
To: Linda Dunbar <linda.dunbar@futurewei.com>
References: <2022041114360459722023@chinamobile.com> <29752325-4d93-271d-a0f1-e874575dca9b@joelhalpern.com> <2022041122304706741797@chinamobile.com> <5c189bc0-0569-e2f9-54b3-1bb41335ae21@joelhalpern.com> <008f01d84e13$8b5db8f0$a2192ad0$@tsinghua.org.cn> <d8fd1f2624b743698ed7b9ba390299f3@huawei.com> <00ed01d84ee1$859b5f70$90d21e50$@tsinghua.org.cn> <de849853-e073-5b61-dab8-b5a3dc33ed71@joelhalpern.com> <00ee01d84ee2$7b852b50$728f81f0$@tsinghua.org.cn> <E0FB105F-CF94-420F-B601-EE5C036E616D@tony.li> <20220413115929730791134@chinamobile.com> <547FE283-6CDC-4C0C-B052-3C009D7BE75A@tony.li> <CO1PR13MB49206621FB31FB80BBBA2B8B85EC9@CO1PR13MB4920.namprd13.prod.outlook.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/Ks7G9lzUjBMGEMhJynqLz08MRGg>
Subject: Re: [Dyncast] CAN BoF issues and the next steps
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Dynamic Anycast <dyncast.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dyncast>, <mailto:dyncast-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dyncast/>
List-Post: <mailto:dyncast@ietf.org>
List-Help: <mailto:dyncast-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dyncast>, <mailto:dyncast-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2022 17:04:13 -0000

Hi Linda,

> Are you saying that it is important to have the use cases to “justify the need of minimizing messaging and latency”?


Not necessarily in the use cases, but if there’s a requirement beyond good engineering that we avoid an extra message or 1ms of latency, we need to know about it and would like to understand why.

If there are boundaries on the solution space, they should be clear to all, up front.

Tony