IETF Logo Mail Archive

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

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 11 April 2022 12:42 UTC

Return-Path: <jmh@joelhalpern.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 46D8E3A0B75 for <dyncast@ietfa.amsl.com>; Mon, 11 Apr 2022 05:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 gOfZxLLC0Mct for <dyncast@ietfa.amsl.com>; Mon, 11 Apr 2022 05:41:59 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8E6B3A0B77 for <dyncast@ietf.org>; Mon, 11 Apr 2022 05:41:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4KcT533zWJz1nwCp; Mon, 11 Apr 2022 05:41:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1649680919; bh=75ODSWSgxkbpmbVVPouCa8fnYgiT174hSUgJy+faf3U=; h=Date:Subject:To:References:From:In-Reply-To:From; b=lK+/DKaKEPHIhql3Iz6ueOpXmYIpZE73TskPYPtdcto1V0cX+/fj1XhSJSayQBPBC NlXpjT2KDlEjZajpj76m8jm4+i5Tf+M4nVMsx7vRY7zZhMG3QAUGscVAkNc+bToVsM EQMEeDLEoxDH9yzGVcEr/gZkx+E2L6hxicmzceXo=
X-Quarantine-ID: <pldgUbgC6oTs>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.21.218] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4KcT530NgJz1nsNN; Mon, 11 Apr 2022 05:41:58 -0700 (PDT)
Message-ID: <29752325-4d93-271d-a0f1-e874575dca9b@joelhalpern.com>
Date: Mon, 11 Apr 2022 08:41:56 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: "liupengyjy@chinamobile.com" <liupengyjy@chinamobile.com>, dyncast <dyncast@ietf.org>
References: <2022041114360459722023@chinamobile.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <2022041114360459722023@chinamobile.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/YE0ypePWknBbtLgdxHYQ0xJDenI>
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: Mon, 11 Apr 2022 12:42:04 -0000

Please do not overstate the situation.
I do not think that "almost everyone agreed" to anything in that BoF.
And in particular, I do not think that "almost everyone agreed" to the 
value for additional metrics.

Yours,
Joel

On 4/11/2022 2:36 AM, liupengyjy@chinamobile.com wrote:
> Dear all,
> 
> Thanks for supporting and joining the CAN work.  We can see that the BoF 
> was successful and had a good discussion, and almost everyone agree on 
> the use case that considering more metrics for steering traffic is 
> valuable and a right direction. 
> https://notes.ietf.org/notes-ietf-113-can 
> <https://notes.ietf.org/notes-ietf-113-can>.
> 
> Here we list the issues according to BoF talking and give the 
> preliminary answers to them, which could be found at 
> https://github.com/CAN-IETF/CAN-BoF-ietf113/issues 
> <https://github.com/CAN-IETF/CAN-BoF-ietf113/issues>. If missing any 
> issue, please let us know and we could add it. The issues will continue 
> to be iterated and then closed.
> 
> Moreover, we will update the key drafts according to the BoF talking and 
> further thinking. If you have the interests, please feel free to contact 
> us.
> 
> Regards,
> Peng
> 
> ------------------------------------------------------------------------
> liupengyjy@chinamobile.com
>

v2.23.0 | Report a Bug | By Email