[Teas] Re: New Liaison Statement, "LS Reply on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies""

Krzysztof Szarkowicz <kszarkowicz@gmail.com> Fri, 06 September 2024 16:40 UTC

Return-Path: <kszarkowicz@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73BE4C14F697; Fri, 6 Sep 2024 09:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_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=gmail.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 dT0sfqHdeeg7; Fri, 6 Sep 2024 09:40:33 -0700 (PDT)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FA27C14F5E5; Fri, 6 Sep 2024 09:40:33 -0700 (PDT)
Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-205909af9b5so18122465ad.3; Fri, 06 Sep 2024 09:40:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725640833; x=1726245633; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=htxyx7MgHxe6tmbk0v3GQyXutqEfD2C4k48CE8cahc0=; b=HSn80giAKS6ZI3ddy9ForsmNg4pmIP07y1PIePhseVIcwIz2I4hjzhigTwed60Sj+Y 9HiVmz//jBvjDhku3+4rw2A2ebSqDKk7gcO4a+8IEcEd0ZlBKBaG766f60jqKJSDs+tJ Jz90l9s5cJ5OUmdGm4ioBOqZHYcjK3KMYOIZx1dHinVlSV0zGovsF6wltKTc1y4oZ6u0 6SrckyOWtSqY7W/2Zp59zRMWaiHi2n8+sss147wVRKuzRuSj8A6+7tN0Wg1/umDgZIhZ 8MTqqPI4lq3DCdRwQ+P871sovhW7pDldJwHEUmcFbIId13a9iWdIAq5Tmv0nyisIZIvf /YFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725640833; x=1726245633; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=htxyx7MgHxe6tmbk0v3GQyXutqEfD2C4k48CE8cahc0=; b=kKjrofgsvfIlDtAKSHEAcOPBV0OcSU1jrQZgy1XgdfV543E6iUB7PQTOhmt8nJiD9q fVRXEWU+B19jkHCbr2Ps8SYui2aVt1bEOSjM1ffLsdNw9KBo1j8PjFlsd/sd6NSdbt3E hz+YdAcmudm+u4JEjnjwxFrmUrsCIqEwOxtqL71TIAU76IrnyZxzT21JrNaxtXdI1CDY MmOZQ4or/2ro+inXa3JnsdvYz1nedtnHTB1/UuhzLaPkmav+9my1dxgFIe7F1ILpQHlf 0S/+HE2e0jwut+Sp6QIWt3eM+P5W5byUL/xkOh4tqArB1v6QGYoQvkx/NLdgc182lLwe ww1Q==
X-Forwarded-Encrypted: i=1; AJvYcCVvvhHnOM/vFtEVTHN4ZRD0ijCEbUN3A/kIfR+hBJe28LTYpvWMgaSFFc0pCPo/6SiCEd/L@ietf.org
X-Gm-Message-State: AOJu0YxNCXvGG8VnXAcq1mSTyC9rxLCAfACCYaNWJF5RxeL2vgF0j2yM sa0v3KEn/yF+NIQIBNEoKXSjiU7jQxKF8Hjc1rEtASLrAXMHGn+LCbBkvOy8
X-Google-Smtp-Source: AGHT+IFKENdpjVPntTwVZERew5cIEc35rCAuMu+KrR/aL603DhFYv8o4yfeMOAyXPjBUG8d/NhLjBQ==
X-Received: by 2002:a17:902:cf04:b0:202:2d:c87 with SMTP id d9443c01a7336-206f04a10e6mr45671305ad.12.1725640832556; Fri, 06 Sep 2024 09:40:32 -0700 (PDT)
Received: from smtpclient.apple (jpams-nat14.juniper.net. [193.110.49.14]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-206aea595a6sm45232645ad.240.2024.09.06.09.40.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Sep 2024 09:40:31 -0700 (PDT)
From: Krzysztof Szarkowicz <kszarkowicz@gmail.com>
Message-Id: <41DF2960-AF1C-4E6B-8959-579BE35FF1D1@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_04487B10-A9D8-414C-A38B-5D62130771A9"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.2\))
Date: Fri, 06 Sep 2024 18:40:16 +0200
In-Reply-To: <172556980029.1952499.10018535368312214204@dt-datatracker-68b7b78cf9-q8rsp>
To: TEAS WG Chairs <teas-chairs@ietf.org>
References: <172556980029.1952499.10018535368312214204@dt-datatracker-68b7b78cf9-q8rsp>
X-Mailer: Apple Mail (2.3731.700.6.1.2)
Message-ID-Hash: 6ABROPHGPRNN75AWHUFAYEX2VVKB2QYU
X-Message-ID-Hash: 6ABROPHGPRNN75AWHUFAYEX2VVKB2QYU
X-MailFrom: kszarkowicz@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-teas-5g-ns-ip-mpls@ietf.org, TEAS WG <teas@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Teas] Re: New Liaison Statement, "LS Reply on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies""
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/4qtmaYugzF_67Ha2edt56lV0dOo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

Dear Chairs,


Authors of draft-ietf-teas-5g-ns-ip-mpls have discussed the 3GGP LS reply, and are planning following updates:


1. Authors will removed appendix B.1 and B.2, and release new version of the draft without these appendixes.

2. Authors will keep the example of IP allocation method described in Section 4. IP allocation method not being discussed by 3GPP doesn’t preclude that it cannot be discussed by IETF.

3. Authors will keep Section 5 unchanged. Slice realization in transport network, including how transport network resources (including QoS queues -> e.g. if single slice uses single QoS queue or multiple QoS queues) are used, is in the scope of IETF, not 3GPP. draft-ietf-teas-5g-ns-ip-mpls in any way doesn’t provide any recommendations or suggestions about changing or adjusting 3GPP 5G QoS model in network domain(s) under 3GPP SDO scope., or about correlation between 3GPP 5G QoS and network slices in the network domain(s) under 3GPP SDO scope.


Best regards,
Krzysztof
(on behalf of co-authors)



> On Sep 5, 2024, at 22:56, Liaison Statement Management Tool <statements@ietf.org> wrote:
> 
> Title: LS Reply on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies"
> Submission Date: 2024-09-05
> URL of the IETF Web page: https://datatracker.ietf.org/liaison/1955/
> 
> From: Charles Eckel <eckelcu@cisco.com>
> To: Vishnu Beeram <vbeeram@juniper.net>,Lou Berger <lberger@labn.net>,Oscar de Dios <oscar.gonzalezdedios@telefonica.com>
> Cc: Oscar de Dios <oscar.gonzalezdedios@telefonica.com>,Gunter Van de Velde <gunter.van_de_velde@nokia.com>,Traffic Engineering Architecture and Signaling Discussion List <teas@ietf.org>,Jim Guichard <james.n.guichard@futurewei.com>,John Scudder <jgs@juniper.net>,Vishnu Beeram <vbeeram@juniper.net>
> Response Contacts: Peter.Schmitt@huawei.com, Susanna Kooistra <3GPPLiaison@etsi.org>
> Technical Contacts: 
> Purpose: In response
> 
> Referenced liaison: LS on a Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies (https://datatracker.ietf.org/liaison/1931/)
> 
> Body: 1. Overall Description:
> 
> Thanks IETF for the LS on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies". SA2 would like to provide feedback related to system architecture.
> 
> 1.For the description of 5G architecture in Appendix B.1 and B.2, it is suggested to only have reference to TS 23.501 in IETF specifications instead of repeating the description to have an up-to-date architecture and functionality of 5GS. Currently the description is not precise.
> 2.Regarding clause 4, SA2 has not discussed any mechanism to associate the end point of GTP-U tunnel with the S-NSSAI because there is no need to introduce such mechanism for 5GS to differentiate the tunnels of different slices.
> 3.Regarding clause 5, SA2 would like to clarify 5G QoS model is an independent feature from network slicing. Binding with S-NSSAI is not aligned with the current 5G QoS model. 
> 
> 2. Actions:
> 
> To IETF Traffic Engineering Architecture and Signaling Working Group (teas)group.
> ACTION: SA2 asks IETF Traffic Engineering Architecture and Signaling Working Group (teas) group to take the above information into account.
> 
> 3. Date of Next TSG SA WG2 Meetings:
> TSG-SA2 Meeting #165		15th Oct – 18th Oct, 2024			Hyderabad, IN
> TSG-SA2 Meeting #166		17th Nov – 22nd Nov, 2024			Orlando, US
> Attachments:
> 
>    S2-2408691  upload was 7889 LSOut LS Reply on A Realization of Network Slices for 5G Networks Using Current IP MPLS Technologies_Jinguo (002)
>    https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2024-09-05-3gpp-tsgsa-sa2-teas-ls-reply-on-a-realization-of-network-slices-for-5g-networks-using-current-ipmpls-technologies-attachment-1.docx
> 
> 
> _______________________________________________
> Teas mailing list -- teas@ietf.org
> To unsubscribe send an email to teas-leave@ietf.org