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

<lionel.morand@orange.com> Wed, 03 July 2019 22:40 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 6A16C1200D6; Wed, 3 Jul 2019 15:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 djyZOIXKNLYq; Wed, 3 Jul 2019 15:40:10 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5541120096; Wed, 3 Jul 2019 15:40:09 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 45fGJl5wdfz2yYk; Thu, 4 Jul 2019 00:40:07 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.35]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 45fGJl4Gnlz2xC7; Thu, 4 Jul 2019 00:40:07 +0200 (CEST)
Received: from OPEXCAUBM41.corporate.adroot.infra.ftgroup ([fe80::857d:4f67:b0a7:10d7]) by OPEXCAUBM6C.corporate.adroot.infra.ftgroup ([fe80::f58e:8e9d:ae18:b9e3%21]) with mapi id 14.03.0439.000; Thu, 4 Jul 2019 00:40:07 +0200
From: <lionel.morand@orange.com>
To: "DOLLY, MARTIN C" <md3135@att.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>, "vshaikh@perspectalabs.com" <vshaikh@perspectalabs.com>, "sdas@perspectalabs.com" <sdas@perspectalabs.com>
Thread-Topic: =?utf-8?B?UmXCoDogWzNncHAtaWV0Zi1jb29yZF0gUUNJIHRvIERpZmZzZXJ2IG1hcHBp?= =?utf-8?Q?ng?=
Thread-Index: AQHVLbr6/GSRjxkdCE+/lHgwwX7ryA==
Date: Wed, 3 Jul 2019 22:40:06 +0000
Message-ID: <26275_1562193607_5D1D2EC7_26275_253_1_8dvwqd-ivdgud-xhk3u8-1zgu7n2ke0m1swsibmk44su34pxiaed9vsr-4ez9cj-2s2oc5-v8wtp8-sc7ytm-l8cjwq-6hu13l-6h58k4d3352v-m6c2jngtmamw-7d278wt460cgabavuy-8vfpwn-ql6d6m.1562192996122@email.android.com>
References: <HE1PR0701MB2522FD4E040BDCE8526F2CD2951F0@HE1PR0701MB2522.eurprd07.prod.outlook.com> <23546_1559122655_5CEE52DF_23546_285_1_6B7134B31289DC4FAF731D844122B36E3A118AF4@OPEXCAUBM41.corporate.adroot.infra.ftgroup> <f39ff409-7650-df63-5275-528b35f4dc74@ericsson.com> <17495_1562057912_5D1B1CB8_17495_31_1_6B7134B31289DC4FAF731D844122B36E3A15A5D3@OPEXCAUBM41.corporate.adroot.infra.ftgroup> <c38b5162-806a-75f0-540b-0ff7943d6860@ericsson.com> <0e7d4dfc-8fdf-baad-cbe0-92d8bad9884a@ericsson.com> <44ABD18C-4291-4B4D-A8DB-0AA7A3D4824C@att.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_8dvwqdivdgudxhk3u81zgu7n2ke0m1swsibmk44su34pxiaed9vsr4e_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/fRTlYhi9bZlyjQsXb1fzLzK6y6M>
Subject: [3gpp-ietf-coord] =?utf-8?q?Re=C2=A0=3A__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, 03 Jul 2019 22:40:14 -0000

Hi Gonzalo, Martin,

We have discussed this point with Georg. According to the purpose of the draft and early reaction of 3GPP folks, it appears that there is currently no requirement for such mapping done in IETF.

The QCI/DSCP mapping is only for information, as the final mapping will be nyvow decided by network operators, based on the QCI values but also on other criteria defined by the operators.

Moreover, if you look at the 3GPP TS 23.203 specification across releases, you will see that the new QCI values are continuously defined by 3GPP depending on new use cases. For instance, there is an ongoing didcussion to create additional values. So having a document defining the mapping at the IETF side would seem not relevant as the RFC, even if informational, could be already obsolete when published.

There might be a need to have an update version of the mapping but, if deemed required, interested parties should bring such a material in 3GPP, to allow maintaining up to date the document.

According that there is no specific requirement from 3GPP and an IETF RFC, even information would be quite useless, 3GPP would be reluctant to see any recommendation on the QCI/DSCP mapping provided in a IETF document that would not be under the 3GPP control.

Now, from an IETF point of view, if there is a strong push for such a document, except the natural push from the authors, it would be up to IETF to decide what to do in this area. If it is decided to move forward, it should be made clear in the document that the proposed mapping is only for information, not a recommendation, given as example. It should also be highlighted that the QCI values listed in the document may not be up to date.

I hope that the feedback is clear.
Anyhow, it will be useful to discuss this point in our coordination meeting. Unfortunately, I will not be in Montreal but, if we could set up an audio bridge as last time, it would be great.

Regards,

Lionel


-------- Message original --------
Objet : Re: [3gpp-ietf-coord] QCI to Diffserv mapping
De : "DOLLY, MARTIN C"
À : Gonzalo Camarillo
Cc : MORAND Lionel TGI/OLN ,Magnus Westerlund ,3gpp-ietf-coord@ietf.org,tsvwg-chairs@ietf.org,vshaikh@perspectalabs.com,sdas@perspectalabs.com

Greetings

The NS/EP service in the USA has major issues w this draft that is against efforts we standardized in 3GPP and ATIS

We commented on the list and communicated w author, little changes

If this became a 3GPP dependency, we and the others would have sustained objections

Thanks

Martin C. Dolly

Lead Member of Technical Staff

Government & Services Standards

AT&T

Cell: +1.609.903.3360

Email: md3135@att.com<mailto:md3135@att.com>

On Jul 3, 2019, at 2:51 PM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com<mailto:Gonzalo.Camarillo@ericsson.com>> wrote:

Hi Lionel,

did you reach any conclusion? In particular, I would like to understand
whether we need to organize the traditional 3GPP-IETF coordination
meeting on the Monday of the upcoming IETF meeting in Montreal to
discuss this or other issues.

Thanks,

Gonzalo

On 02-Jul-19 13:11, Gonzalo Camarillo wrote:
Hi Lionel,

yes, exactly; knowing 3GPP's position on this would be very helpful in
order to decide on next steps. Please, let us know after you touch base
with Georg later today. Thanks.

Cheers,

Gonzalo

On 02-Jul-19 11:58, lionel.morand@orange.com<mailto:lionel.morand@orange.com> wrote:
Hi Gonzalo,

We will discuss this point with Georg today during an 3GPP internal coordination meeting.
On the tsvwg mailing list, I think that the conclusion was to set up a discussion at the next IETF meeting to see what could be done in this area.
Honestly, I'm not sure that such a work would be useful if not supported by 3GPP. So if anything is finally done, it could only be for information.

Coming back to you later.

Regards,

Lionel

-----Message d'origine-----
De : Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
Envoyé : vendredi 28 juin 2019 16:09
À : MORAND Lionel TGI/OLN; Magnus Westerlund; 3gpp-ietf-coord@ietf.org<mailto:3gpp-ietf-coord@ietf.org>
Cc : tsvwg-chairs@ietf.org<mailto:tsvwg-chairs@ietf.org>
Objet : Re: [3gpp-ietf-coord] QCI to Diffserv mapping

Hi Lionel,

I have not seen any follow up on this issue during this month (see
below). What is the current status? Thanks.

Cheers,

Gonzalo

On 29-May-19 12:37, lionel.morand@orange.com<mailto:lionel.morand@orange.com> wrote:
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<mailto:3gpp-ietf-coord@ietf.org>
Cc : tsvwg-chairs@ietf.org<mailto: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://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dhenry-2Dtsvwg-2Ddiffserv-2Dto-2Dqci_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g&s=XunaN7YxIvVUKNlYB0LFqWpZkcOVXTV8rK7BUaJlvyo&e=

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://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_tsvwg_r3jAeNPcz83K0nFyQD4yObJkC-2D&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g&s=fzf5xDu0zA-11_7wZOZws5A-XtDJHPg8MX6T3brLff4&e=
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<mailto:magnus.westerlund@ericsson.com>
----------------------------------------------------------------------


_______________________________________________
3gpp-ietf-coord mailing list
3gpp-ietf-coord@ietf.org<mailto:3gpp-ietf-coord@ietf.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_3gpp-2Dietf-2Dcoord&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g&s=q_X_5XSzZyoEnIX3EI0K5efyl4wkwj-xENnr264Zij8&e=


______________________________________________________________
___________________________________________________________

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.

_______________________________________________
3gpp-ietf-coord mailing list
3gpp-ietf-coord@ietf.org<mailto:3gpp-ietf-coord@ietf.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_3gpp-2Dietf-2Dcoord&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g&s=q_X_5XSzZyoEnIX3EI0K5efyl4wkwj-xENnr264Zij8&e=


_________________________________________________________________________________________________________________________

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.


_______________________________________________
3gpp-ietf-coord mailing list
3gpp-ietf-coord@ietf.org<mailto:3gpp-ietf-coord@ietf.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_3gpp-2Dietf-2Dcoord&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g&s=q_X_5XSzZyoEnIX3EI0K5efyl4wkwj-xENnr264Zij8&e=


_______________________________________________
3gpp-ietf-coord mailing list
3gpp-ietf-coord@ietf.org<mailto:3gpp-ietf-coord@ietf.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_3gpp-2Dietf-2Dcoord&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-ZgJ46PZ4x9UvfXkTAVPAgFzc3jf6cvGf6x0g&s=q_X_5XSzZyoEnIX3EI0K5efyl4wkwj-xENnr264Zij8&e=

_________________________________________________________________________________________________________________________

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.