From jros@qti.qualcomm.com Thu Nov 2 10:45:43 2023 Return-Path: X-Original-To: alto@ietfa.amsl.com Delivered-To: alto@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7066EC14CF13; Thu, 2 Nov 2023 10:45:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.705 X-Spam-Level: X-Spam-Status: No, score=-2.705 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=qualcomm.com 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 KEa89c2mwwn3; Thu, 2 Nov 2023 10:45:38 -0700 (PDT) Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (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 1A0DFC14EB17; Thu, 2 Nov 2023 10:45:37 -0700 (PDT) Received: from pps.filterd (m0279866.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3A2CFeIJ001451; Thu, 2 Nov 2023 17:45:36 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=qcppdkim1; bh=/Xp05Ycf7LM7/wez7um3HlWFTjo7PAxZ4YOPFd7xub4=; b=SqzPWj/xQcM/n14yVLfLXjpG+aThgUcrM1Hlj9fv7hC7yORBqxpOJU/FjgUvcuop+GKe A3+jJpyXsnz/hFi/w/kLVbwtC3t+nBXUx/NsazoLUTV9Ee65E0/1SeFQAZn95nQWzUqJ ZZNRvYwhxzKHUr3Y/F36yGeW9azq7X+DNZT0Iw1uI+EOkjrNe3khjpVoiXgn7JaJZQdA g4Qd+arhBUGRyrxD27hfeMpDvVbuTLvr+zNu3mmRBtTTpV9uL60qQwumLSKw6FylTkEX LQHQcr8P1Hb7FXlwQ5hmBSJBD2by74RQjhktWLwlj6xzygK2buQ8jzRcS9LboFLQCvXY mQ== Received: from nam04-mw2-obe.outbound.protection.outlook.com (mail-mw2nam04lp2169.outbound.protection.outlook.com [104.47.73.169]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3u3mbf3scg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 02 Nov 2023 17:45:35 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=m4Y+IR7MGdRYNIN5Y25ON27/Aopc8ApWBVM4bS26HP7t86y42t/mC71kK23WBOb4KrZN/mghtrN6Y6jIRaBqA2nar/JXxvidPydJGynNxrh5pmdtSnSnHWhbDXScR7J0YhI7i6Bx0OOUkE4u6UR4uDHLK6JZGsX66f+VFtdDAJSglUmj7JJEOIAeXYv67K7p1MpMruCbxFEKeSSH50rLN8osIwvxXPofLcmA59SMKCpL9JGvAyHRDRlKF+DNOz1F6mVnJ5E9Si31JBTmNmBYZrFFIpy6ksfcU4HZH5Qa7C2bL48+6KGQYQY5i+EM74QrWBVMBRyruttyAEoNI16vnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=/Xp05Ycf7LM7/wez7um3HlWFTjo7PAxZ4YOPFd7xub4=; b=RHSkBYuPFsr+pcAEsAQCmlUriJj4RqsxLFX0+0JSJERILryCk1JQ0vFM59dIhUzLf7bOxskdgV63VZCPRwR0B2B0v4UdHPKmB/LGz1+/X2XitS+eiDk/+Wx/2IAHzAWauuIas81LiDEpfOhPwx4K/BqqdigMlH3MlMAoGFAhyfVk5LTMAZU08ytgYizy5YKQ5xV1o+qgmhC9Eby4LfjkXWYmYHddqfC3adK2Nf2K8rmRzcgk21kKIVDDS7VAEME95K6UEUIaktJw3r+C/LpxTUx3GsiRg3GhoCywG5ptGhIra1h24pAGEN4Ci5NXTeW7QXUt05RazuRINtZq059FXg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=qti.qualcomm.com; dmarc=pass action=none header.from=qti.qualcomm.com; dkim=pass header.d=qti.qualcomm.com; arc=none Received: from SN6PR02MB5375.namprd02.prod.outlook.com (2603:10b6:805:75::12) by IA1PR02MB9418.namprd02.prod.outlook.com (2603:10b6:208:3fd::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.24; Thu, 2 Nov 2023 17:45:31 +0000 Received: from SN6PR02MB5375.namprd02.prod.outlook.com ([fe80::b53:98b6:51e4:f458]) by SN6PR02MB5375.namprd02.prod.outlook.com ([fe80::b53:98b6:51e4:f458%4]) with mapi id 15.20.6954.019; Thu, 2 Nov 2023 17:45:31 +0000 From: Jordi Ros Giralt To: Linda Dunbar , "cats@ietf.org" , "alto@ietf.org" CC: "idr@ietf.org" Thread-Topic: New draft on joint exposure of network and compute information Thread-Index: AQHaBmtv3lfj91oqKU6ZkcpSGEnn+bBlvBbQgAGZq8g= Date: Thu, 2 Nov 2023 17:45:31 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US, es-ES, ca-ES Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: x-ms-publictraffictype: Email x-ms-traffictypediagnostic: SN6PR02MB5375:EE_|IA1PR02MB9418:EE_ x-ms-office365-filtering-correlation-id: 9dcdeed7-74e7-49c0-1e53-08dbdbcb827c x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: zDIrsbWWtqW2yUJ2PO4Ch/l+dg+SVHmCk6RjbOPj0O5iHvWbYTNSmdjiIEQRUpFOuiUbT6LDOXPQofYGy+Z7ZFsdbG4AUnhkq0VSAVkMrqyruVPgknc6tyIQl6hRrNQT2ALuFSvbmt3hKpisEF8iha6PXSOPJcACWbkGAGcixOq9lf2eIccqtB/PLeGX6kl+k8fx8JxvkUj9guW2/DDz3vOe5bdvBYUqkDcgj4+2CwDPoSAoGuCDf9cqr2OlxPsvIeA+a7Igc/DLzZ3llMOh9kUn83nfcY4qVwnE2ImwSVJMhzNcSGAt3Ruf/OnFyNGpp3n00K6+Cqi5seupmPnkUartfGfBeM/YE9+5I4zi02rwFJ1qehHcZTl44685as+7HvYjozQ8FXArOvdMSoiutJtDiQLeQYUT8I+PqmZQ1zO9asfMrFV9Lgaqz4m5iZaqhVOjisF3abMSxVacxbjQT3MmSFjmQxel9PW0yaWcxLGfm3iAxKJoMtr7+R81i9MdTHhWgTETHmgkkoZuEN4OFIoluykayemaz9Xw24bGxJsPdhEjf4ydQ1ftLHdc5Uj9yxfckTXQm6JYzro6D2nunDkVJo/5BBfZYh4aBQr5MsgSQBWrlhpen/lZZbyvYMNvmBq+CZ+6T36FyxOLivzBXQ== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SN6PR02MB5375.namprd02.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(346002)(366004)(376002)(396003)(39860400002)(136003)(230273577357003)(230173577357003)(230922051799003)(64100799003)(451199024)(1800799009)(186009)(5660300002)(52536014)(8936002)(4326008)(55016003)(8676002)(41300700001)(33656002)(2906002)(86362001)(53546011)(6506007)(9686003)(38070700009)(71200400001)(122000001)(110136005)(966005)(66574015)(26005)(7696005)(478600001)(83380400001)(19627405001)(38100700002)(166002)(1015004)(66946007)(91956017)(76116006)(64756008)(316002)(66446008)(66556008)(66476007); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?XUmDugkH5zPqGa+4Ui0gf/iUQVYfaEB4K6Mfp+B3HjSsGCXHq507TMlK?= =?Windows-1252?Q?1/EkjZqFwtnbUK40kO1nSCILStampcovqTjtfETtBipNgHrNLJyIcxt9?= =?Windows-1252?Q?TN27Vijot/y3c03rBa8ke4kquyL4Kb5w/VjEDv32BK5pN7nx40gyAbJt?= =?Windows-1252?Q?tZAOVr8PDwPy+s2hoN9c2YSPIxwSjI4XPIzVePB5PYgZwHGg4pL/55tZ?= =?Windows-1252?Q?rYxfjtnfCSvWQ7dx2jYeChxYHLaMFxL1aZoSxRegUj2nSJw/usRIRbQx?= =?Windows-1252?Q?PlstBw8QYz1LOTmJ7Ctc99mvGXE0zxBHfc4iOBYZA6d5uNlUpdwkM74O?= =?Windows-1252?Q?kl+fctW8mbm1OkJyheMaaqEoAN4Ac50V+YD3VvKPGgXm3PXPmbZneehP?= =?Windows-1252?Q?m1y38/dkXPtsPfVAhfNMJvLI0F6WIcSzZkebtIsStvUcz8CgtPE6hdAW?= =?Windows-1252?Q?8VQNDxi6CRl1la1fl4S1GJprfwjRQG2oP99CF2DSQYv5GNFUs57DUW3f?= =?Windows-1252?Q?d6vwQTpCw2myaJ2L34WhML3alOZuqpWd1wPtZ2SeUA9KFcSw+HIkCtGp?= =?Windows-1252?Q?tkAkGAKB/dH9dQQVAuiKPSg4HkB5ElGh0SQkUvGBSAEqeB1EdE49Ey05?= =?Windows-1252?Q?Wmrf/cQsFlEwimip3Ob4PL4tVK2sNj7ngBqHrGh9e9C/ntHRRNk1l+vn?= =?Windows-1252?Q?MMnFArd5O9MRz2XTI/qog+Kk8+sag6awMQPFuJKjiHuWCEroKtSVP4zN?= =?Windows-1252?Q?KItRk2G/Z1duVbkTOdYfB46vj8bghlVu7BM0eFSpai0JSXOm7UstGr2f?= =?Windows-1252?Q?a5m49T7PA+Liqex5lSliHxAPs4xLJMQGEJP2NMBqO3sxLf8qNtCjCABr?= =?Windows-1252?Q?gc4jg7KMYxIs7gV1BuJPjCKLyP+JFvBMxvgkrqN6biEqiFgGDVZAwPSJ?= =?Windows-1252?Q?oVcL6xdZCvHmEX55DBngQ01plmMPKBBySRuCKdEsg53YQEV3hsx7X74R?= =?Windows-1252?Q?vAZPwm1kj7GG++UgZqjusNCkKUgYz8SV7glQzaAkWLhWPcswY4aHoqQ4?= =?Windows-1252?Q?XhsmKXDOAQMgfY1x/9Fyh+ezVCytpEYfPVyx3MCFzDjRtSpYkEIS1sQY?= =?Windows-1252?Q?V1+SUNqS8fFfY5GO+ZiaNwTC8ZXpHatbNjpLMy78w8x/PmQohfPCjltw?= =?Windows-1252?Q?LevuVwIG+7iw57VVim7T1J4KwjXrlYIYCC2s1qgVe16mr2qdHatNvu81?= =?Windows-1252?Q?K0hf0FMaq5QTO+jbfleeBbtPgWLiDIcC3XgdhFd6IPgQoYcmEEOMZxST?= =?Windows-1252?Q?FdkWSmz9CbkSE3Mp3rn9iALF6znOKrkx0pMVFd+e9gdZcgJHYpbHKXFR?= =?Windows-1252?Q?M+yC+cASQEwYvuadDLZU9UGwdL7dnE7+SvD8y5R/yIckHlyUe/WHV/zv?= =?Windows-1252?Q?WOpxH7V5WwhCfGn6+s8JrSKiauDSGUkmVWigalWJ6bCZiT24pr4ARiWs?= =?Windows-1252?Q?7vXXlJUhWQYagUHapVtuVCIXWfyEOxkvThAdWTxhBq7AyEuvX197zXHU?= =?Windows-1252?Q?B+vTAEAevJoA0d+9abcgZo2LB+krM/FgktW4qGaKETagOxyXmryvxLku?= =?Windows-1252?Q?MHfwx2Er3/inrJRzDxEx4+ZGUm+PQr/SpjrImsT9s4rSmdxjhYIlGHu7?= =?Windows-1252?Q?DGNHpO8KO/EdpnK3PpnvovUISPgon8IQ?= Content-Type: multipart/alternative; boundary="_000_SN6PR02MB53752009FD62F6ADB813026DF6A6ASN6PR02MB5375namp_" MIME-Version: 1.0 X-MS-Exchange-AntiSpam-ExternalHop-MessageData-ChunkCount: 1 X-MS-Exchange-AntiSpam-ExternalHop-MessageData-0: lkZTn2pBQMb9ZXvqYyFR0U5yZT1l1sIepe2VJHpZ0tL3YMIPeQTwUkPd2oyBt3uB+4leZkq4WB9irZhqfuixCu2Qze51A2jNiVieYstYWlLa0lTBQ+6cT3ZsyrtU0q26Qer/RfEn3tR56ghQDrygHQEFWWK8egHWP2Fw5ysTbfZ14g/swJzS8kUWQn/12pO+I0DUUonMJREeeyMDxLQEFqrpCbspWEpdWzh4AaZaai/C26+QhQ3qEgqxK8bfGUUuQ37uJrl6XD5Q2aWVQFargDb1EAtdAZjwnPcXtGRNAFwdtHOD0zm01dOzma0Afdc/mySj4NoENWHKiwYSC1dBOE38t6rx9bUlOFsMaieoD9pIrw8eZGPsr9O/WeGUb7+8wj4guh5SAhpYbfj4uHNoC2lW4WknyF45xcODT1iJQHTE7hx0bWbfSaVOQ5b6jziyqx5cRSyyPgdSfdeZFZKJJZYCr8LDEgaiZDl+1po1yQeb5XvLGNqDzsDr34tofPxRe4oFdE2/NK9Wa6ILKsE/c56PPslTyB2tlKkqNj1oAlRkSi0ABg8myWbcpp7YY9W6W7brCAnfH+gInW+Qr4kxdXa0l6Ssoh88jMDOAc+E6DS7yoiEUtkjI0vjlANid/B89MH0+DLr4vCaeDTIFne6XBMNvjnR0ihdUHzFubEQPPjF4L3Ed8MGT4CAJQ9fLyZ19orc4YcXp4chtXOC6hdoJBPHJHJfjr1AyQi6lcR3bX2+9nKHGLT/FCEx2oahBD4HxIMLGjO/zqMeQpdJtNXNCI1h/85hJ9s/w1QDqLjytAY= X-OriginatorOrg: qti.qualcomm.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: SN6PR02MB5375.namprd02.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 9dcdeed7-74e7-49c0-1e53-08dbdbcb827c X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Nov 2023 17:45:31.6706 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 98e9ba89-e1a1-4e38-9007-8bdabc25de1d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: y0VXBDFH8rCqO/BrzZ+mUgha3cfnXd7olet4AsK0+vqm4zTx8pvdLFigI4nJfaSIogkKyNtRccp16SsS+4+CqQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: IA1PR02MB9418 X-Proofpoint-GUID: snNg4MzaC5ArEIzckQ1bTuP17vSVDsEL X-Proofpoint-ORIG-GUID: snNg4MzaC5ArEIzckQ1bTuP17vSVDsEL X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.987,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-11-02_07,2023-11-02_03,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 malwarescore=0 mlxlogscore=999 suspectscore=0 lowpriorityscore=0 mlxscore=0 phishscore=0 priorityscore=1501 clxscore=1011 adultscore=0 spamscore=0 bulkscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2310240000 definitions=main-2311020146 Archived-At: Subject: Re: [alto] New draft on joint exposure of network and compute information X-BeenThere: alto@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2023 17:45:43 -0000 --_000_SN6PR02MB53752009FD62F6ADB813026DF6A6ASN6PR02MB5375namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Thanks Linda for your comments. Find my responses below: > Your draft describes two aspects of the service performance > impacted by the Computing: Service Deployment and Service (Path) > Selection. Those two should be separated, as the Service Deployment > belongs to the OpsArea, and the Service selection (including Network > Path & DCs that host the services) belongs to the Routing area. [JRG] I agree that service deployment can be seen as part of ops area. Serv= ice selection can both be seen as part of the routing area (as you point ou= t), but also a part of the application area. For instance, an application r= unning in a UE could decide whether to use 5G, 4G, or Wi-Fi to connect to a= service instance based on the communication and compute resource informati= on exposed to it. > draft-ietf-idr-5g-edge-service-metadata has proposed a new Metadata Path > Attribute and some Sub-TLVs for egress routers to advertise the Metadata > about the attached edge services (ES). > (...) Can this Metadata Path Attribute address the problem stated in your= draft? [JRG] I agree this information is valuable to the ingress router to make pa= th selection decisions. In addition, there is also a need for this informat= ion to be exposed to the service or application layer. If there is service = replication, the application running in the UE (or an application-layer pro= xy on behalf of it) needs to decide which of the service replicas it connec= ts to. Once a service replica is selected, the UE might also have a variety= of ways to reach that service (e.g., 4G, 5G, Wi-Fi). Both of these end-poi= nt selection decisions need to know the available communication and compute= resources. Thanks, Jordi ________________________________ From: Linda Dunbar Sent: Wednesday, November 1, 2023 18:11 To: Jordi Ros Giralt ; cats@ietf.org = ; alto@ietf.org Cc: idr@ietf.org Subject: RE: New draft on joint exposure of network and compute information WARNING: This email originated from outside of Qualcomm. Please be wary of = any links or attachments, and do not enable macros. Jordi, Your draft describes two aspects of the service performance impacted by the= Computing: Service Deployment and Service (Path) Selection. Those two sho= uld be separated, as the Service Deployment belongs to the OpsArea, and the= Service selection (including Network Path & DCs that host the services) be= longs to the Routing area. https://datatracker.ietf.org/doc/draft-ietf-idr-5g-edge-service-metadata/ h= as proposed a new Metadata Path Attribute and some Sub-TLVs for egress rou= ters to advertise the Metadata about the attached edge services (ES). The= Edge Service Metadata can be used by the ingress routers in the 5G Local D= ata Network to make path selections not only based on the routing cost but = also the running environment of the edge services. The goal is to improve = latency and performance for 5G edge services. Can this Metadata Path Attribute address the problem stated in your draft? = I CC=92ed the IDR WG, so your comments on the Path Selection can be visibl= e to them. Thanks, Linda From: Cats On Behalf Of Jordi Ros Giralt Sent: Tuesday, October 24, 2023 6:47 AM To: cats@ietf.org; alto@ietf.org Subject: [Cats] New draft on joint exposure of network and compute informat= ion Dear CATS and ALTO WG mailing list members, We submitted a new draft on joint exposure of network and compute informati= on for service placement and selection: https://datatracker.ietf.org/doc/dr= aft-rcr-opsawg-operational-compute-metrics/ Joint Exposure of Network and Compute Information for Infrastructure-Aware = Service DeploymentJoint Exposure of Network and Compute Information for Inf= rastructure-Aware Service Deployment This draft focuses on the problem of exposing both network and compute info= rmation to the service provider/application to support service placement an= d selection decisions. ALTO provides an interface for network information e= xposure to the service provider/application; thus, an approach is to levera= ge and extend it with compute metrics. CATS also needs to develop compute m= etrics to support traffic steering decisions. The common ground is in these= compute metrics, which could be reused across the various use cases (e.g.,= consumed by the network as in CATS or consumed by the application as in AL= TO). This draft also aims at providing a framework for continuing the discussion= initiated during IETF 117 regarding the presentation "Compute-aware metric= s: CATS working with ALTO": https://datatracker.ietf.org/doc/slides-117-alt= o-compute-aware-metrics-cats-working-with-alto/ We would like to seek feedback from both working groups on developing compu= te metrics that can be reused for different use cases, to avoid duplicated = work and increase the effectiveness of future standards. Thanks, Jordi --_000_SN6PR02MB53752009FD62F6ADB813026DF6A6ASN6PR02MB5375namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Thanks Linda for your comments. Find my responses below:

= > Your draft= describes two aspects of the service performance 

= > impacted by t= he Computing: Service Deployment and  Service (Path) 

= > Selection. Th= ose two should be separated, as the Service Deployment 

= > belongs to th= e OpsArea, and the Service selection (including Network 

= > Path & DC= s that host the services) belongs to the Routing area.


[JRG] I agree that service deployment can be see= n as part of ops area. Service selection can both be seen as part of the routing area (as you point out), but also = a part of the application area. For instance, an application running in a U= E could decide whether to use 5G, 4G, or Wi-Fi to connect to a service inst= ance based on the communication and compute resource information exposed to it.
= >= ; draft-ietf-idr-5g-edge-service-metadata has p= roposed a new Metadata Path 

= > Attribute and some Sub-TLVs  for egress routers to advertise the Metadata 

= > about the attached edge services (ES). 

= >= ; (...) Can this Meta= data Path Attribute address the problem stated in your draft? <= /p>

=

= [JRG] I agree this i= nformation is valuable to the ingress router to make path selection decisions. In addition, there is also a need= for this information to be exposed to the service or application layer. If= there is service replication, the application running in the UE (or an app= lication-layer proxy on behalf of it) needs to decide which of the service replicas it connects to. Once a s= ervice replica is selected, the UE might also have a variety of ways to rea= ch that service (e.g., 4G, 5G, Wi-Fi). Both of these end-point selection de= cisions need to know the available communication and compute resources.

=

= Thanks,

= Jordi





From: Linda = Dunbar <linda.dunbar@futurewei.com>
Sent: Wednesday, November 1, 2023 18:11
To: Jordi Ros Giralt <jros@qti.qualcomm.com>; cats@ietf.o= rg <cats@ietf.org>; alto@ietf.org <alto@ietf.org>
Cc: idr@ietf.org <idr@ietf.org>
Subject: RE: New draft on joint exposure of network and compute= information
 

WARNING: This email originated from outside of Qualcomm. Please b= e wary of any links or attachments, and do not enable macros.

https://datatracker.ietf.org/doc/draft-ietf-idr-5g-edge-service-metada= ta/ has proposed a new Metadata Path Attribute and some Sub-TLVs  for egress = routers to advertise the Metadata about the attached edge  services (E= S).  The Edge Service Metadata can be used by the ingress routers in t= he 5G Local Data Network to make path selections not only bas= ed on the routing cost but also the running environment of the edge service= s.  The goal is to improve latency and performance for 5G  edge s= ervices.

Dear CATS and ALTO WG mailing list members,

We submitted a new draft on joint exposure of netw= ork and compute information for service placement and selection: https://datatracker.ietf.org/doc/draft-rcr-opsawg-operational-compute-metri= cs/

 

Joint Exposure of Network = and Compute Information for Infrastructure-Aware Service DeploymentJoint Ex= posure of Network and Compute Information for Infrastructure-Aware Service Deployment

This draft focuses on the problem of exposing both network and comput= e information to the service provider/application to support service placement and selection decisions. ALTO provides an int= erface for network information exposure to the service provider/application= ; thus, an approach is to leverage and extend it with compute metrics. CATS= also needs to develop compute metrics to support traffic steering decisions. The common ground is in these compu= te metrics, which could be reused across the various use cases (e.g., consu= med by the network as in CATS or consumed by the application as in ALTO).

 

This draft also aims at providing a framework for continuing the disc= ussion initiated during IETF 117 regarding the presentation "Compute-aware metrics: CATS working with ALTO"= : https://datatracker.ietf.org/doc/slides-117-alto-compute-aware-metrics-cats= -working-with-alto/  

We would like to seek feedback from both working groups on developing= compute metrics that can be reused for different use cases, to avoid duplicated work and increase the effecti= veness of future standards.

Thanks,

Jordi 

 

--_000_SN6PR02MB53752009FD62F6ADB813026DF6A6ASN6PR02MB5375namp_--