Re: [3gpp-ietf-coord] 3GPP review on draft-ietf-lpwan-schc-over-nbiot-13

lionel.morand@orange.com Tue, 22 November 2022 11:22 UTC

Return-Path: <lionel.morand@orange.com>
X-Original-To: 3gpp-ietf-coord@ietfa.amsl.com
Delivered-To: 3gpp-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51A88C14CEE3; Tue, 22 Nov 2022 03:22:25 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, 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=orange.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 0d9Z7pYh-gjq; Tue, 22 Nov 2022 03:22:21 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 64B39C14CEE2; Tue, 22 Nov 2022 03:22:21 -0800 (PST)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr21.francetelecom.fr (ESMTP service) with ESMTPS id 4NGhgH32hGz5whC; Tue, 22 Nov 2022 12:22:19 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1669116139; bh=Sj4q0VF0n1GYLIIKO1Z7tPBmBrYD6ZJGrqWLi8wyXL8=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=p+D7W2BdeM97DT2tjATGpvHgOa3cXqF2Mg2QexTKprgVBb+7wK1stJ4rA94aNl/S4 ckSfgSEaOLmBrt9KzxwdgE7MmPWutDd5QtqUz8RKAGQIKndj05/4cGk6zn+wWrWaPa 3i8ObT3s75T8oLczzV2dDzmQf3WIGnMd5XjZnCImXbhNWHrdr2lSwtkFOu5dyyt4SD xjz8b0NAePy7dsBYt2qVtvfcZFs+Er3YUI2eCQ17pX2AQh7/wxgOpkxuj5fW94JEll cxMbQhcjLWAVAF2znyCO8w7p8F4AK4dNFOpR6JCq+Afdt9d5TxupCnVMePqy3BRCOj l3UYfYlVazktg==
From: lionel.morand@orange.com
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>
CC: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "edgar.ramos@ericsson.com" <edgar.ramos@ericsson.com>, "ana@ackl.io" <ana@ackl.io>, lp-wan <lp-wan@ietf.org>, Erik Kline <ek.ietf@gmail.com>, Lars Eggert <lars@eggert.org>
Thread-Topic: 3GPP review on draft-ietf-lpwan-schc-over-nbiot-13
Thread-Index: AQHY/mB8fGHzRFdu4kWUAHivq/8b+65Ky3AA
Date: Tue, 22 Nov 2022 11:22:18 +0000
Message-ID: <13227_1669116139_637CB0EB_13227_260_1_1d4debed672042d18ccf2217168d9401@orange.com>
References: <61C78BDB-1E51-4614-B756-DC959D8957D8@cisco.com>
In-Reply-To: <61C78BDB-1E51-4614-B756-DC959D8957D8@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Enabled=true; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_SetDate=2022-11-22T11:22:16Z; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Method=Standard; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Name=Orange_restricted_external.2; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ActionId=f0fdf4ba-c1d0-483b-8901-eefb325286a5; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ContentBits=2
x-originating-ip: [10.115.26.52]
Content-Type: multipart/alternative; boundary="_000_1d4debed672042d18ccf2217168d9401orangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/EfmZNKL_14wRW61M3Uj_RoP0iY0>
Subject: Re: [3gpp-ietf-coord] 3GPP review on draft-ietf-lpwan-schc-over-nbiot-13
X-BeenThere: 3gpp-ietf-coord@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: 3GPP IETF COORDINATION <3gpp-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/3gpp-ietf-coord>, <mailto:3gpp-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/3gpp-ietf-coord/>
List-Post: <mailto:3gpp-ietf-coord@ietf.org>
List-Help: <mailto:3gpp-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord>, <mailto:3gpp-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2022 11:22:25 -0000

Hi Eric,

We have discussed the LS last week during the 3GPP WG meetings in Toulouse. Because people were busy during the meeting week and the next one, it was said that any feedback from the delegates can only be provided at the end of the week or next week. It is aligned with my own comment during the coordination meeting.
I hope if it is fine.

Regards,

Lionel



Orange Restricted
De : Eric Vyncke (evyncke) <evyncke@cisco.com>
Envoyé : mardi 22 novembre 2022 11:52
À : 3gpp-ietf-coord@ietf.org; MORAND Lionel INNOV/NET <lionel.morand@orange.com>
Cc : Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>; edgar.ramos@ericsson.com; ana@ackl.io; lp-wan <lp-wan@ietf.org>; Erik Kline <ek.ietf@gmail.com>; Lars Eggert <lars@eggert.org>
Objet : 3GPP review on draft-ietf-lpwan-schc-over-nbiot-13

Lionel, Gonzalo, and others,

After our 3GPP-IETF coordination meeting in London on the 8th of November 2022 (2 weeks ago), and if not mistaken, 3GPP was about to review draft-ietf-lpwan-schc-over-nbiot in the line of the 2 existing liaison statements [1] [2] during last week 3GPP meeting.

Did such discussion take place during the 3GPP meeting ?

Was there any decision ? Notably:
1/ is the current IETF draft ready to go from 3GPP point of view ? (any technical issues ? is the wording about information/normative ok ?)
2/ else, should the informative parts (use of SCHC compression by a future 3GPP release) be better tagged/introduced as informative only (we did our best) ?
3/ else, should the informative parts be moved to an appendix  (breaking the flow hence a big work by the authors)?
4/ any other comment ?

Thank you very much in advance for any piece of information,

Regards

-éric

[1] https://datatracker.ietf.org/liaison/1480/ (dated 2016... IETF was rather slow to act on 3GPP demand :-( ....)
[2] https://datatracker.ietf.org/liaison/1796/ (dated 2022)


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.