Re: [Can] Zaheduzzaman Sarker's Block on charter-ietf-can-00-04: (with BLOCK and COMMENT)

[Zaheduzzaman Sarker <[e-mail]>]

Hello Adrian,

The proposed changes look good and address my concerns well. Really appreciate the efforts for addressing my comments.

//Zahed

> On 17 Feb 2023, at 10:41, Adrian Farrel <[e-mail]> wrote:
> 
> Hi Zahed,
> 
> Thanks for your various comments and discussions (and for pre-emptively
> clearing your Block).
> 
> Here, for your review and for the information of the CAN list are the
> changes and a clean version of the charter text attached.
> 
> Cheers,
> Adrian
> ===
> 
> OLD
> Since, for some services (for example, VR/AR, intelligent
> transportation), the performance experienced by clients will depend on
> both network metrics such as bandwidth and latency, and compute metrics
> such as processing, storage capabilities, and capacity,
> NEW
> Since, for some services (for example, the evolution of networked AR/VR,
> and deployment of autonomous and networked vehicles), the performance
> experienced by clients will depend on both network metrics such as
> bandwidth and latency, and compute metrics such as processing, storage
> capabilities, and capacity,
> END
> 
> ---
> 
> OLD
> Specific
> characteristics that may distinguish CAN from other work include the
> desire to integrate both network and compute conditions in the
> optimization function, and the desire to operate that function on nodes
> within the service provider's network, logically separated from service
> operation.
> NEW
> Specific
> characteristics that may distinguish CAN from other work include the
> desire to integrate both network and compute conditions in the
> optimization function that informs the steering applied by the network
> edge nodes, and the desire to operate that function on nodes within the
> service provider's network, logically separated from service operation.
> END
> 
> ---
> 
> OLD
> As part of its work, the CAN WG will seek
> advice and expertise from the ART and TSV areas.
> NEW
> Because of their experience and prior work
> in collecting and exposing network conditions for use in selecting paths
> and servers, the CAN WG will seek advice and expertise from the ART and
> TSV areas.
> END
> 
> ---
> 
> OLD
> The CAN WG will initially focus on single domain models.
> NEW
> The CAN WG will focus on single domain models.
> END
> 
> 
> -----Original Message-----
> From: Can <[e-mail]> On Behalf Of Zaheduzzaman Sarker via
> Datatracker
> Sent: 16 February 2023 14:05
> To: The IESG <[e-mail]>
> Cc: [e-mail]; [e-mail]
> Subject: [Can] Zaheduzzaman Sarker's Block on charter-ietf-can-00-04: (with
> BLOCK and COMMENT)
> 
> Zaheduzzaman Sarker has entered the following ballot position for
> charter-ietf-can-00-04: Block
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-can/
> 
> 
> 
> ----------------------------------------------------------------------
> BLOCK:
> ----------------------------------------------------------------------
> 
> I have two easy to fix block comments which I believe needed to be discussed
> and would clarify the charter better if addressed -
> 
> # it says -
> 
>   "Exposure of network and compute conditions to applications
> is not in the scope of CAN. As part of its work, the CAN WG will seek
> advice and expertise from the ART and TSV areas."
> 
>  I am confused, if the advice and expertise is for the exposure of the
> network
>  and compute condition and which is out of the scope, then what would the
>  advice for? This need to clarified.
> 
> # it says -
> 
>    "The CAN WG will initially focus on single domain models."
> 
>   Does this mean CAN will under this charter will eventually work on multi
>   domain models? will there be a rechartering needed to work on multi
> domain
>   models? This is going to impact the architecture I guess whether the
>   solution is for single domain or multiple domains.
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> And one comment to clarify the service examples -
> 
> # can we change the service examples? it says - "for some services (for
> example, VR/AR, intelligent transportation)". I don't really know what the
> intelligent transportation service is, may be that is because my lack of
> knowledge, hence very hard to see what requirements it puts that requires
> compute awareness.  AR/VR as a technology is mostly deployed in the user
> devices now and the network assisted AR/VR application is kind of still in
> research, hence may not be best examples for the CAN work.
> 
> 
> 
> -- 
> Can mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/can
> 
> 
> <charter-ietf-can-00-05.txt>