IETF Logo Mail Archive

Re: [tsvwg] updated version of QCI to Diffserv draft

<Ruediger.Geib@telekom.de> Mon, 03 June 2019 07:13 UTC

Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D66B12006E for <tsvwg@ietfa.amsl.com>; Mon, 3 Jun 2019 00:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.306
X-Spam-Level:
X-Spam-Status: No, score=-4.306 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 1UDS0mTzY_MX for <tsvwg@ietfa.amsl.com>; Mon, 3 Jun 2019 00:13:19 -0700 (PDT)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (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 171FC120119 for <tsvwg@ietf.org>; Mon, 3 Jun 2019 00:13:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1559545998; x=1591081998; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=LB6kylx8DjD4JWKbUD8ArpGa5f9HYHWEGn0mMgJK6xo=; b=D07ekd2arQthb9pxt6BISMUJR/dl9I3Rfqo1aog1hFhaWLV7RV4KT+sC cR+wug8d/JmFCgWYlyRyZLAxxQ5LWGU00bQWWjmHDbwfrFezsYq/I6K6I wO/fvTHSrt8ROGr1mTp121c4h29+TswndLre75i/5HZnzOkpBmH2n/kQM W1qe3D/khJ+JjKA19lWTwh5Arvc8gFYC3etimLakcNP16fcyyk5ONs7Sy HbTSGQy2rO3k+gwD24LwIcIq4bMtn+OMNnzvu9Hc7doH3xD0aFndTgi94 hhz9plFVd/uHlG5FCmDGolcurXVNGYvRMc9ev9AvW4uZjjo8BDBF/7uGT Q==;
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jun 2019 09:13:14 +0200
X-IronPort-AV: E=Sophos;i="5.60,546,1549926000"; d="scan'208,217";a="434440481"
X-MGA-submission: MDHmgQIf2AxIsubeM/2XqW7cRMGMLhRvzbIQI6Tu97/9wlLRWDisHHexoO49eKWZiL0hFWALK2RnFCTVMy6wZo6av2dFr8GY7iKsgvGCzlx4cmcC61oUt14wk1+Mb4zVfJ2XPqF5dfrwwCDSDMXqLoHfvYkhzsiA3k5kSqewxT5RdQ==
Received: from he105664.emea1.cds.t-internal.com ([10.169.118.61]) by QDEC97.de.t-internal.com with ESMTP/TLS/AES256-SHA; 03 Jun 2019 09:13:15 +0200
Received: from HE105709.EMEA1.cds.t-internal.com (10.169.118.41) by HE105664.emea1.cds.t-internal.com (10.169.118.61) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 09:13:15 +0200
Received: from HE104160.emea1.cds.t-internal.com (10.171.40.36) by HE105709.EMEA1.cds.t-internal.com (10.169.118.41) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 3 Jun 2019 09:13:15 +0200
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.23) by O365mail03.telekom.de (172.30.0.232) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 09:13:13 +0200
Received: from FRXPR01MB0199.DEUPRD01.PROD.OUTLOOK.DE (10.158.151.17) by FRXPR01MB0199.DEUPRD01.PROD.OUTLOOK.DE (10.158.151.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.22; Mon, 3 Jun 2019 07:13:14 +0000
Received: from FRXPR01MB0199.DEUPRD01.PROD.OUTLOOK.DE ([fe80::6dfa:6bf9:6d1e:cabf]) by FRXPR01MB0199.DEUPRD01.PROD.OUTLOOK.DE ([fe80::6dfa:6bf9:6d1e:cabf%3]) with mapi id 15.20.1943.018; Mon, 3 Jun 2019 07:13:14 +0000
From: Ruediger.Geib@telekom.de
To: subirdas21@gmail.com
CC: tsvwg@ietf.org
Thread-Topic: [tsvwg] updated version of QCI to Diffserv draft
Thread-Index: AQHVFW+xtV2HXIIrCky4LBvT0OK3wKaJjAmw
Date: Mon, 03 Jun 2019 07:13:14 +0000
Message-ID: <FRXPR01MB0199FB3848F364B07633568B9C140@FRXPR01MB0199.DEUPRD01.PROD.OUTLOOK.DE>
References: <CAFb8J8ph5uScGC0twO=W2F06T_yvM4pCeLQ+q0-H00cPm8t-Lg@mail.gmail.com>
In-Reply-To: <CAFb8J8ph5uScGC0twO=W2F06T_yvM4pCeLQ+q0-H00cPm8t-Lg@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Ruediger.Geib@telekom.de;
x-originating-ip: [164.19.3.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7769cd86-2296-48b0-1517-08d6e7f2f203
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:FRXPR01MB0199;
x-ms-traffictypediagnostic: FRXPR01MB0199:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <FRXPR01MB01998A19077E29B503AEDD6F9C140@FRXPR01MB0199.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(396003)(39860400002)(366004)(136003)(189003)(199004)(25584004)(6916009)(14454004)(74482002)(19627235002)(508600001)(7110500001)(9686003)(790700001)(72206003)(7736002)(966005)(68736007)(236005)(102836004)(85182001)(52396003)(6116002)(53936002)(1411001)(2906002)(3846002)(186003)(86362001)(4326008)(5070765005)(5660300002)(476003)(11346002)(85202003)(81166006)(81156014)(8936002)(8676002)(486006)(2420400007)(15650500001)(66066001)(606006)(446003)(14444005)(256004)(7696005)(6306002)(54896002)(75402003)(33656002)(26005)(76116006)(73956011)(66556008)(55016002)(76176011)(66446008)(64756008)(66946007)(66476007)(71190400001)(71200400001)(777600001)(564094006); DIR:OUT; SFP:1101; SCL:1; SRVR:FRXPR01MB0199; H:FRXPR01MB0199.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: os+YuCTF5mNBf9Pu96FbzGUkGXrHvYN3vzthiPTU4LrXEHaoCN9ySByLYUIxgC1IxMZx8byDwgct3xhVTDhu8OBoe/QEA5VIS4lyHvNmJyDOrQr04K9mMlLkVzqCBEAiatmH5YKCsG2x/5nRfjXkt2ftIRWwcQCHAffk0A+ZoImtoaJXTbYNkcLh3FKfDmRG5sexXuYhRuTiSaJDX6W+w0AXO19SIudzGUE1ZrgwMUOhLOHkHV4qDUQFiQzdUiv0/pZq6XiX9SVPQChBcQahD9KALQTtS3upG+qel8jh1DfrI6Ig7CYgCgxMip/pSDnACgiVOj3Haf9fAZIetJung/HI+6W69v9JtH+Arz2BCKTOfoI46lEasA2Os+URy91m3KziVI1KZLQrtfymQ2MLDlO1AclJBIK6RfWpDURKaew=
Content-Type: multipart/alternative; boundary="_000_FRXPR01MB0199FB3848F364B07633568B9C140FRXPR01MB0199DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7769cd86-2296-48b0-1517-08d6e7f2f203
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2019 07:13:14.7563 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Ruediger.Geib@telekom.de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRXPR01MB0199
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Au6N3IIdpCSBGez4oympx5qz2g8>
Subject: Re: [tsvwg] updated version of QCI to Diffserv draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 07:13:22 -0000

Hi Subir,

thanks, I agree to your conclusion.

Regards, Ruediger

Von: tsvwg <tsvwg-bounces@ietf.org> Im Auftrag von Subir Das
Gesendet: Dienstag, 28. Mai 2019 18:10
An: tsvwg@ietf.org
Betreff: Re: [tsvwg] updated version of QCI to Diffserv draft


Hello Jerome,

 I read your ver-01 draft and have the following questions and comments.

- What is the motivation of this draft in IETF when 3GPP is the responsible organization to create such a mapping document?

- Who will be using these recommendations if such a document exists in IETF?

- What is the intent of this document: Informational or Experimental or Standards Track?



[snip]



IMO, IETF community SHOULD NOT  create a document that recommends the QCI-to-DSCP mappings unless 3GPP asks for it via a liaison.



Thanks,

-Subir


Re: [tsvwg] updated version of QCI to Diffserv draft

"Jerome Henry (jerhenry)" <jerhenry@cisco.com<mailto:jerhenry@cisco.com>> Mon, 15 April 2019 17:07 UTCShow header<https://mailarchive.ietf.org/arch/browse/tsvwg/?q=Jerome>

Dear all,



We submitted an update to the Diffserv to QCI mapping document. As part of the 5G finalization, then 3GPP added a few  QCIs, and we updated the draft accordingly.



We are looking forward to input and feedback, through the mailer and in Montreal. Our ambition is to (eventually) get this draft to a consensus state where we can share it with GSMA, who documents how QCI markings can be translated to other values when exchanged through other domains (e.g. Diffserv) between carriers.



Thanks!



Jerome





https://datatracker.ietf.org/doc/draft-henry-tsvwg-diffserv-to-qci/

v2.23.0 | Report a Bug | By Email