Re: [3gpp-ietf-coord] QCI to Diffserv mapping

<lionel.morand@orange.com> Wed, 29 May 2019 09:37 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 6F71B120142; Wed, 29 May 2019 02:37:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 72steb4kdLP8; Wed, 29 May 2019 02:37:37 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 359BD1200EF; Wed, 29 May 2019 02:37:37 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 45DQbz1zpGz8vlc; Wed, 29 May 2019 11:37:35 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.79]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 45DQbz13KCzCqkG; Wed, 29 May 2019 11:37:35 +0200 (CEST)
Received: from OPEXCAUBM41.corporate.adroot.infra.ftgroup ([fe80::857d:4f67:b0a7:10d7]) by OPEXCAUBM6E.corporate.adroot.infra.ftgroup ([fe80::d89a:9017:59c2:9724%21]) with mapi id 14.03.0439.000; Wed, 29 May 2019 11:37:34 +0200
From: <lionel.morand@orange.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>
CC: "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
Thread-Topic: QCI to Diffserv mapping
Thread-Index: AQHVFf4c3g57nJxRr0WQxwTDz4Z3T6aB12YQ
Date: Wed, 29 May 2019 09:37:34 +0000
Message-ID: <23546_1559122655_5CEE52DF_23546_285_1_6B7134B31289DC4FAF731D844122B36E3A118AF4@OPEXCAUBM41.corporate.adroot.infra.ftgroup>
References: <HE1PR0701MB2522FD4E040BDCE8526F2CD2951F0@HE1PR0701MB2522.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB2522FD4E040BDCE8526F2CD2951F0@HE1PR0701MB2522.eurprd07.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/ncwN1wKQUDInPRbtZLeYtJ2utFE>
Subject: Re: [3gpp-ietf-coord] QCI to Diffserv mapping
X-BeenThere: 3gpp-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 29 May 2019 09:37:39 -0000

Thank you!

I have seen the ongoing discussion on this topic.
I will send soon an email clarifying the current 3GPP position on this topic.
It is important that any work on the QCI mapping is aligned with real 3GPP requirements.

Regards,

Lionel

> -----Message d'origine-----
> De : 3gpp-ietf-coord [mailto:3gpp-ietf-coord-bounces@ietf.org] De la part
> de Magnus Westerlund
> Envoyé : mercredi 29 mai 2019 11:09
> À : 3gpp-ietf-coord@ietf.org
> Cc : tsvwg-chairs@ietf.org
> Objet : [3gpp-ietf-coord] QCI to Diffserv mapping
> 
> Hi,
> 
> A topic that may require coordination between 3GPP and IETF is this
> individual proposal
> 
> https://datatracker.ietf.org/doc/draft-henry-tsvwg-diffserv-to-qci/
> 
> It has been presented once in TSVWG before, when questions where raised
> about the relation to 3GPP. I haven't seen any good answer to this
> question. Also the authors have updated the draft and that has resulted
> in some additional discussion in this thread:
> 
> https://mailarchive.ietf.org/arch/msg/tsvwg/r3jAeNPcz83K0nFyQD4yObJkC-
> A
> 
> So far no decision has been made if this should be adopted or not, but I
> would not be surprised if the TSVWG Chairs and I (as TSV AD) do get the
> question about adoption.
> 
> Input from a 3GPP perspective would be appreciated on this document.
> 
> Cheers
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Network Architecture & Protocols, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Torshamnsgatan 23           | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 
> 
> _______________________________________________
> 3gpp-ietf-coord mailing list
> 3gpp-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord

_________________________________________________________________________________________________________________________

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.