[Can] Zaheduzzaman Sarker's Block on charter-ietf-can-00-04: (with BLOCK and COMMENT)
Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Thu, 16 February 2023 14:04 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: can@ietf.org
Delivered-To: can@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E4786C16B5C3; Thu, 16 Feb 2023 06:04:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: can-chairs@ietf.org, can@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 9.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
Message-ID: <167655629191.43355.15509759045232338604@ietfa.amsl.com>
Date: Thu, 16 Feb 2023 06:04:51 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/can/vlENImNeiA2c8wCO0SN3GnNqQik>
Subject: [Can] Zaheduzzaman Sarker's Block on charter-ietf-can-00-04: (with BLOCK and COMMENT)
X-BeenThere: can@ietf.org
X-Mailman-Version: 2.1.39
List-Id: CAN- Computing-Aware Networking <can.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/can>, <mailto:can-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/can/>
List-Post: <mailto:can@ietf.org>
List-Help: <mailto:can-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/can>, <mailto:can-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2023 14:04:52 -0000
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] Zaheduzzaman Sarker's Block on charter-ietf… Zaheduzzaman Sarker via Datatracker
- Re: [Can] Zaheduzzaman Sarker's Block on charter-… John Scudder
- Re: [Can] Zaheduzzaman Sarker's Block on charter-… Zaheduzzaman Sarker
- Re: [Can] Zaheduzzaman Sarker's Block on charter-… Adrian Farrel
- Re: [Can] Zaheduzzaman Sarker's Block on charter-… Zaheduzzaman Sarker