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

["[e-mail]" <[e-mail]>]

Dear Joel,

Sorry, more accurately, we didn't hear any objections on the use case. 

We are eager to hear any issues with the use cases presented. We would appreciate it very much if you can elaborate issues you have with the use case.

Regards,
Peng


[e-mail]
 
From: Joel M. Halpern
Date: 2022-04-11 20:41
To: [e-mail]; dyncast
Subject: Re: [Dyncast] CAN BoF issues and the next steps
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, [e-mail] 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
> 
> ------------------------------------------------------------------------
> [e-mail]
>