Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116

lionel.morand@orange.com Fri, 17 March 2023 09:01 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 AAE5EC15152C for <3gpp-ietf-coord@ietfa.amsl.com>; Fri, 17 Mar 2023 02:01:10 -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, 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 1MpFtVTa1XLi for <3gpp-ietf-coord@ietfa.amsl.com>; Fri, 17 Mar 2023 02:01:06 -0700 (PDT)
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 46156C14CE45 for <3gpp-ietf-coord@ietf.org>; Fri, 17 Mar 2023 02:01:06 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) (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 opfednr24.francetelecom.fr (ESMTP service) with ESMTPS id 4PdJ5D2PRWz1yMw; Fri, 17 Mar 2023 10:01:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1679043664; bh=u7Qg9QXNPPj/vtIGhuSVqbca1y2dDjGJGx5FC2u61Fk=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=Omp3ULzfgPPd2kYqf0mkBlnT2Uf9+VyLirb0xZXICRvMYRmlsWZM4s8fCiX8Nz0Jt nDqFtdQhudYJoJI6UC2dlHeBDN1S1LdbBkRQIDy4RWzsAZLbOu2W34Tlza2tub4U5f iB0Pvs+J3/jCWDDevVsOhz2UGY4gwle+U0NlbS6Qbxus0OqBhRzzf/wNuEye0gPQ/0 4bJBN6XkFFawyyY9hTslsyTbgLchUaUsGroUyjZ0rglZLc1gPOoHS0I6Sy4mVopcQf 6MH67VsFcvhfiA+3jFCAqVjfbNWDlY3a1XhsP+T1SnXsk8Z4egcoVxmGdNP0+M2m6o yhTikCz7SkREw==
From: lionel.morand@orange.com
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>, "Charles Eckel (eckelcu)" <eckelcu=40cisco.com@dmarc.ietf.org>, "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>
Thread-Topic: IETF - 3GPP coordination meeting at IETF 116
Thread-Index: AQHZWFN4QdHzw2iA0Uq5HTbG+hEZMa7+pm1FgAAGr1A=
Date: Fri, 17 Mar 2023 09:01:03 +0000
Message-ID: <25349_1679043664_64142C50_25349_266_1_4d0aa88ac13d4f03ab4b1f249aaa603f@orange.com>
References: <106A4CDF-4DA0-450C-A38C-EAE03225137E@cisco.com> <DU0PR07MB8970267CF2341B1D796E20EB95BD9@DU0PR07MB8970.eurprd07.prod.outlook.com>
In-Reply-To: <DU0PR07MB8970267CF2341B1D796E20EB95BD9@DU0PR07MB8970.eurprd07.prod.outlook.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=2023-03-17T09:01:01Z; 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=b50e12b7-f45f-4d58-9e62-0d49e7a3a3f2; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ContentBits=2
x-originating-ip: [10.115.27.51]
Content-Type: multipart/alternative; boundary="_000_4d0aa88ac13d4f03ab4b1f249aaa603forangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/r35svFBdHCa6Qepi0_vBabqyULo>
Subject: Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116
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: Fri, 17 Mar 2023 09:01:10 -0000

Hi Magnus,

This will be part of my report.
An revised agenda will be provided next week with further details.

Regards,

Lionel



Orange Restricted
De : 3gpp-ietf-coord <3gpp-ietf-coord-bounces@ietf.org> De la part de Magnus Westerlund
Envoyé : vendredi 17 mars 2023 09:40
À : Charles Eckel (eckelcu) <eckelcu=40cisco.com@dmarc.ietf.org>; 3gpp-ietf-coord@ietf.org
Objet : Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116

Hi,

For the agenda should we include a discussion of how to improve so that 3GPP's secretariat actually understand that they get LS from IETF?

I guess this is a general warning. The 3GPP secretariat don't understand that the emails with the LS from IETF actually are LS in themselves due to the lack of attachment of a proper full document that they can include. So if you send LS from IETF to 3GPP you need to actually ensure that they are picked up.

Cheers

Magnus Westerlund

From: 3gpp-ietf-coord <3gpp-ietf-coord-bounces@ietf.org<mailto:3gpp-ietf-coord-bounces@ietf.org>> on behalf of Charles Eckel (eckelcu) <eckelcu=40cisco.com@dmarc.ietf.org<mailto:eckelcu=40cisco.com@dmarc.ietf.org>>
Date: Thursday, 16 March 2023 at 23:06
To: 3gpp-ietf-coord@ietf.org<mailto:3gpp-ietf-coord@ietf.org> <3gpp-ietf-coord@ietf.org<mailto:3gpp-ietf-coord@ietf.org>>
Subject: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116
Hi Everyone,

We will have an IETF - 3GPP coordination meeting at IETF 116 on Tuesday during the lunch break (11:30 - 13:00).
For those attending in person, we will be meeting in G318<https://datatracker.ietf.org/meeting/116/floor-plan?room=g318> (3rd floor). Lunch will be provided.
Those attending remotely can join via Webex. Sorry, but no time zone appropriate meal provided in this scenario.

https://datatracker.ietf.org/meeting/116/agenda?filters=ietf-3gpp-coordination

The currently planned agenda for our meeting is as follows:

  *   Roundtable discussion
  *   Status of the 3GPP-IETF dependencies
  *   Ongoing IANA action
  *   Incoming/Outgoing LSs
  *   AoB
Please feel free to suggest additional agenda items.
We look forward to meeting with you during IETF 116.

Cheers,
Charles and Lionel


_________________________________________________________________________________________________________________________

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.