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

"DOLLY, MARTIN C" <md3135@att.com> Wed, 03 July 2019 19:39 UTC

Return-Path: <md3135@att.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 5CF09120449; Wed, 3 Jul 2019 12:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 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, 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 W4AU9TXxj0tM; Wed, 3 Jul 2019 12:39:13 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6651D120447; Wed, 3 Jul 2019 12:39:13 -0700 (PDT)
Received: from pps.filterd (m0053301.ppops.net [127.0.0.1]) by mx0a-00191d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x63Jal72034539; Wed, 3 Jul 2019 15:39:10 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by mx0a-00191d01.pphosted.com with ESMTP id 2th2bjrjde-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 03 Jul 2019 15:39:09 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x63Jd8PV022529; Wed, 3 Jul 2019 15:39:08 -0400
Received: from zlp27128.vci.att.com (zlp27128.vci.att.com [135.66.87.50]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x63Jd2WI022440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 3 Jul 2019 15:39:02 -0400
Received: from zlp27128.vci.att.com (zlp27128.vci.att.com [127.0.0.1]) by zlp27128.vci.att.com (Service) with ESMTP id 277074039341; Wed, 3 Jul 2019 19:39:02 +0000 (GMT)
Received: from MISOUT7MSGHUBAE.ITServices.sbc.com (unknown [130.9.129.149]) by zlp27128.vci.att.com (Service) with ESMTPS id F3B594039340; Wed, 3 Jul 2019 19:39:01 +0000 (GMT)
Received: from MISOUT7MSGUSRDB.ITServices.sbc.com ([169.254.2.31]) by MISOUT7MSGHUBAE.ITServices.sbc.com ([130.9.129.149]) with mapi id 14.03.0439.000; Wed, 3 Jul 2019 15:39:01 -0400
From: "DOLLY, MARTIN C" <md3135@att.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
CC: "lionel.morand@orange.com" <lionel.morand@orange.com>, 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: [3gpp-ietf-coord] QCI to Diffserv mapping
Thread-Index: AQHVFf4c3g57nJxRr0WQxwTDz4Z3T6aB12YQgC+1nQCABfKzgIAAFIKAgAIjSICAAAfnAA==
Date: Wed, 3 Jul 2019 19:39:00 +0000
Message-ID: <44ABD18C-4291-4B4D-A8DB-0AA7A3D4824C@att.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>
In-Reply-To: <0e7d4dfc-8fdf-baad-cbe0-92d8bad9884a@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_44ABD18C42914B4DA8DB0AA7A3D4824Cattcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-03_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1907030239
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/QtPk7ZLGG88glg5Cf9X5sKb_1Cc>
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, 03 Jul 2019 19:39:17 -0000

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<tel:+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=