From nobody Thu Apr 13 06:27:36 2023 Return-Path: X-Original-To: rtg-dir@ietfa.amsl.com Delivered-To: rtg-dir@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB31C14CF1F; Thu, 13 Apr 2023 06:27:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.095 X-Spam-Level: X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=googlemail.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 uypUY3anvmuB; Thu, 13 Apr 2023 06:27:29 -0700 (PDT) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EEB6C15155E; Thu, 13 Apr 2023 06:27:28 -0700 (PDT) Received: by mail-yb1-xb2b.google.com with SMTP id q5so18131306ybk.7; Thu, 13 Apr 2023 06:27:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20221208; t=1681392447; x=1683984447; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BhkG9PQk4AN6wdYbALsV5PxwqPKB+fXG/cT4Y2PZm+o=; b=g46ov3iI7y1rweqSmjZIe6AikiD6J2jVc0AddHrC9Xz8y+VmGie47OxTh8+BJsC+gy K0BDyQb3lUql9gPwf1iYWFwWPT8/WRYeEs5HKCrH5Oyz1uq7yrD5ujhJRxsp4TYbV3pj lQ8P9oYYOEwd5N+LqNNUxZ8BfibAxWxbgACC4CuRWjv9C9sPDDu7QmMjsGP5FmndcCbF Z9ol30vAJOCnsfx2qV2Yyl2xu8QmExxO0hcW8+o3j8+3oRpzZtZpdgyo6leg/Aqsk6Xz Z+5Be2isXJE/OyoMji67F9nTpC8iX1difTktCLc7XC+eSoxU0CyGq5l2eVtChcZtYbGo eDjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681392447; x=1683984447; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BhkG9PQk4AN6wdYbALsV5PxwqPKB+fXG/cT4Y2PZm+o=; b=lU9xSfUw1qp1ok86DsLV1xhrjozokPdwEohSmo7L+rQXwHbiTHe6xE2+rzgWrjJOrj s2arF/P4cl2OIZ245byzUi09p38IWpVLJhlM3E2XBYWX5ntQykWinoCHwgPXe7VdRtba x3r7rHaijtB4MZKirjeYp2Mn9aKH12zV7q2CvuyZVZem4r0y8FOgKd3gVqn9E0fR8LsR dvkakCdFFJcZD/kZY/gUUOA3zjxwIEu3LHchto8X7uWMD6zAHg+i7tfuLkBE1LVAXq3m VyfabLQLCB5SZ2XAPN584ETd4t82LinCNHDbtU9hx/3S4LNHiSH6ZhiUyrus/I0pKxw7 EUxQ== X-Gm-Message-State: AAQBX9dH5Ke3r7Nb51ILQKUNt2PH4j4Z3/zmK3o1R6Zh5E1ZeszBofLL erL2vCW0HPmSIi8Z6BGbHXQoaFkPoB0RQ47N/68M9XuRi3I= X-Google-Smtp-Source: AKy350aYsZPSLR5T02hHbx2JZXZOFudrXXz98tob6MYdDsM4FNQmOYjjXr3bWNIzW4EdmA0WJGSYtLgStyWOhSubMaM= X-Received: by 2002:a25:748c:0:b0:b8e:f726:d198 with SMTP id p134-20020a25748c000000b00b8ef726d198mr1152311ybc.8.1681392447552; Thu, 13 Apr 2023 06:27:27 -0700 (PDT) MIME-Version: 1.0 References: <168106657337.3348.15967425584623105125@ietfa.amsl.com> In-Reply-To: From: Ines Robles Date: Thu, 13 Apr 2023 16:26:51 +0300 Message-ID: To: Linda Dunbar Cc: "rtg-dir@ietf.org" , "draft-ietf-rtgwg-net2cloud-problem-statement.all@ietf.org" , "rtgwg@ietf.org" Content-Type: multipart/alternative; boundary="0000000000009082a805f937aff5" Archived-At: Subject: Re: [RTG-DIR] Rtgdir early review of draft-ietf-rtgwg-net2cloud-problem-statement-22 X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2023 13:27:34 -0000 --0000000000009082a805f937aff5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Linda, Thank you for addressing my comments. Please find my answer below. BR, Ines. On Thu, Apr 13, 2023 at 1:01=E2=80=AFAM Linda Dunbar wrote: > > * Some mitigations include references, but It would be nice to add > references to all of them. > [Ines] what do you think about this comment? > * The mentioned problems and mitigations applies for 5G Standalone and > Non-Standalone deployments options? > [Linda] The 3GPP=E2=80=99s Edge Computing is for 5G only. > [Ines] Maybe you can add this as clarification, something like "..for > standalone deployments option...", What do you think? > [Linda] Does =E2=80=9CNon-Standalone deployment=E2=80=9D indicate mixed 4= G and 5G? > [Ines] Based on [1] "...the "Non-Stand Alone" (NSA) architecture, where the 5G Radio Access Network (AN) and its New Radio (NR) interface is used in conjunction with the existing LTE and EPC infrastructure Core Network (respectively 4G Radio and 4G Core), thus making the NR technology available without network replacement. In this configuration, only the 4G services are supported, but enjoying the capacities offered by the 5G New Radio (lower latency, etc)... ...the "Stand-Alone" (SA) architecture, where the NR is connected to the 5G CN. Only in this configuration, the full set of 5G Phase 1 services are supported... ... The SA architecture can be seen as the "full 5G deployment", not needing any part of a 4G network to operate...." Notice that they are several options of deployment, please see [2] [3] [4] Thanks, Ines. [1] https://www.etsi.org/deliver/etsi_tr/121900_121999/121915/15.00.00_60/tr_12= 1915v150000p.pdf [2] El Rhayour, Amine, and Tomader Mazri. "5G Architecture: Deployment scenarios and options." 2019 International Symposium on Advanced Electrical and Communication Technologies (ISAECT). IEEE, 2019. [3] https://www.3g4g.co.uk/5G/5Gtech_0004_Beginners_5GforAbsoluteBeginnersCombi= ned.pdf [4] https://www.3g4g.co.uk/Training/intermediate0005.pdf > --0000000000009082a805f937aff5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Linda,

Thank you fo= r addressing my comments. Please find my answer below.

=
BR,
Ines.

On Thu, Apr 13, 2023 at 1:01=E2=80=AFAM Linda= Dunbar <linda.dunbar@futurewei.com> wrote:

* Som= e mitigations include references, but It would be nice to add references to= all of them.=C2=A0

[Ines] what do you think about this com= ment?=C2=A0
=C2=A0=C2=A0
* The= mentioned problems and mitigations applies for 5G Standalone and Non-Stand= alone deployments options?
[Linda] The 3GPP=E2=80=99s Edge Computing is for 5G only.=C2=A0
[Ines= ] Maybe you can add this as clarification, something like "..for stand= alone deployments option...", What do you think?
[Linda] Does =E2=80=9CNon-Standalone deploymen= t=E2=80=9D indicate mixed 4G and 5G?

[Ines]=C2=A0 Based on [1] "...the "Non-S= tand Alone" (NSA) architecture, where the 5G Radio Access Network (AN)= and its New Radio (NR) interface is used in conjunction with the existing = LTE and EPC infrastructure Core Network (respectively 4G Radio and 4G Core)= , thus making the NR technology available without network replacement. In t= his configuration, only the 4G services are supported, but enjoying the cap= acities offered by the 5G New Radio (lower latency, etc)...
...th= e "Stand-Alone" (SA) architecture, where the NR is connected to t= he 5G CN. Only in this configuration, the full set of 5G Phase 1 services a= re supported...
... The SA architecture can be seen as the "full 5G deployment", not = needing any part of a 4G network to operate...."

<= div>Notice that they are several options of deployment, please see [2] [3] = [4]



Thanks,
Ines.

--0000000000009082a805f937aff5--