Re: [Can] Zaheduzzaman Sarker's Block on charter-ietf-can-00-04: (with BLOCK and COMMENT)
Adrian Farrel <adrian@olddog.co.uk> Fri, 17 February 2023 09:41 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: can@ietfa.amsl.com
Delivered-To: can@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8FB9C151522; Fri, 17 Feb 2023 01:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JKBFzev7elcQ; Fri, 17 Feb 2023 01:41:49 -0800 (PST)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 278D8C14CE33; Fri, 17 Feb 2023 01:41:46 -0800 (PST)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.7/8.14.7) with ESMTP id 31H9fhHY022455; Fri, 17 Feb 2023 09:41:43 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 07BCB4604E; Fri, 17 Feb 2023 09:41:43 +0000 (GMT)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 04CD44604B; Fri, 17 Feb 2023 09:41:43 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS; Fri, 17 Feb 2023 09:41:42 +0000 (GMT)
Received: from LAPTOPK7AS653V ([185.69.145.15]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 31H9ferg001008 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 17 Feb 2023 09:41:41 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Zaheduzzaman Sarker' <Zaheduzzaman.Sarker@ericsson.com>, can@ietf.org, jgs@juniper.net
Cc: can-chairs@ietf.org, 'The IESG' <iesg@ietf.org>
References: <167655629191.43355.15509759045232338604@ietfa.amsl.com>
In-Reply-To: <167655629191.43355.15509759045232338604@ietfa.amsl.com>
Date: Fri, 17 Feb 2023 09:41:41 -0000
Organization: Old Dog Consulting
Message-ID: <076801d942b4$0ad57c90$208075b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0769_01D942B4.0AD57C90"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQJ98kBku9l9Erlv15xiesQ4gY+3sa2Jgq7Q
X-Originating-IP: 185.69.145.15
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=qgE2MTQL7lUmrSGx9EATr XP2DF/Y+tGb+a6eta/JTJE=; b=OEnV7sTCdGBjhrSrgZrZi16Sc5xurDvLtQZvX gZqpbeKUpirfa1EKKeo1rspsQEQ55/KVNEVGEl6e5AepSc0rhsrl7AG2GrmAASR4 Ry/04Dcpd9qmh1DYL9vs/rfBJGTYGgH9Cf1aYqp1CEFa/KbiZV9xEdWAmEKu5gg/ DzIo7ef2eLpTfv4lRtpvIWA+2ySOmkfsf7C/ECu71PR5qW9cbFkF+Ab9eKy1+Gj1 7uXt4NmkkeYkqf1LC6o9wp1IAq98j4qZ5rXic4RSMSgsAHp1cj2CvQW9hD/9DFk1 2Jt5mgDICmYQqMmHWRh3opGDsmUxUhgY4kNEFO57kPYRWaeaA==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27452.007
X-TM-AS-Result: No--20.591-10.0-31-10
X-imss-scan-details: No--20.591-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27452.007
X-TMASE-Result: 10--20.590800-10.000000
X-TMASE-MatchedRID: gzVbiXtWD9vxIbpQ8BhdbJObxJgN/hOxkYC3rjkUXRLe6dEbvIyrxev0 bbWUFg/QRgL8bfVL3cpWHBMGehDHi7VibrLP0k4vDZs/KgmqdktNLPQl0QAltFddaUJhWR429K7 5ct/rW8de82ntzuMCtwtMv9Z5eya3eLEZYil6m5z+xRIVoKNMvJ1Koz3Y/YrHcfUXDpFHiE8+ss xJpFYqqzjbBDGxJFF0uxliYAiybD9vqEpAxSVpbMzWN98iBBeG8y+TEM8NeIdrRM6wvXgDae+ne LQgWN7lYtXGkhIYKw1qXGSEtFAxFj8hXNK+3FBhPMcAlOC0qrD2kudi1D33Enhh5KUdlgWiOFu5 pRApemx/50aBEilx0WJHMG3qJf1GcdV1fv9AzTAX6pCkJZNSOU+crEA4+nhZ1YzbHoRn9L3Ktm8 lfGHxnaJ0LSuTgo7rfXDRjTnIyPqumPhEI6UGuGzvIi8LanAaVfzyR3weFIVkYpwdTJ43fcnjLT A/UDoAow4hGANJkLenpRDhGwzj27NFPJKJl6/HJQhrLH5KSJ0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/can/Yj_okl8oWMdFSjcWCBzovESO_6M>
Subject: Re: [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
Precedence: list
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: Fri, 17 Feb 2023 09:41:52 -0000
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 <can-bounces@ietf.org> On Behalf Of Zaheduzzaman Sarker via Datatracker Sent: 16 February 2023 14:05 To: The IESG <iesg@ietf.org> Cc: can-chairs@ietf.org; can@ietf.org 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 Can@ietf.org https://www.ietf.org/mailman/listinfo/can
- [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