Re: [tsvwg] Interim meeting agenda for TSVWG April Interim Meetings

Ruediger.Geib@telekom.de Thu, 09 April 2020 07:18 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 79D9D3A0D4B for <tsvwg@ietfa.amsl.com>; Thu, 9 Apr 2020 00:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.264
X-Spam-Level:
X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 awiIWmKJp-Sd for <tsvwg@ietfa.amsl.com>; Thu, 9 Apr 2020 00:18:41 -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 AAA0F3A0D4A for <tsvwg@ietf.org>; Thu, 9 Apr 2020 00:18:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1586416720; x=1617952720; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=PeAchqCHkxz47zyry12C7dhRquXhhQRp1FIBuNQ3vpU=; b=1yRGKaAsivfBTc9z36FUX1DL1EYXVZHmu4lhVOlLLqId+JHdEsR2M0j7 M/az5bxMke6whkLhBqzHlNblgmHE2zgvuOmNzoDByyy9gQL05dbWIh6TZ UVV2dJeiwQQP9UVHENRo6oh6klEq5BJTV5vPcNNZjHwFcvLfX8JWW/sp+ 3SkredPvZi5BDv6ftpHoCg3/WpV5cgEP3BezWrKqw80DYw8R0cKFJgnS7 fRWZmH+ds3n8FdNxTScWvlINzEYarK6mjFG0rkU2ADq2EromVm3Qs2duD Evg2qP4MghrxNS2Ioa1CurJFs7JiKj1LBi2IPpYrkPAHRAivjzHJG8PJQ A==;
IronPort-SDR: 0RkEHUzdXi/dbhj/tjCMbPfDa/dXjE+tj4OapBQixPYY9N34aXs5DuHaI4gkSAnY/wdQ5DAir2 K5Y5+nG3YqaQ==
Received: from qdefcs.de.t-internal.com ([10.171.254.41]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Apr 2020 09:18:38 +0200
IronPort-SDR: u0SwmzhJ+/UIfiwMltKoJGHNio4LIRe6KnPo8/bCvXp+TlVAE875jY3KExyrG0w8uqm63QOwEk GQ4QfmGBO+Bg==
X-IronPort-AV: E=Sophos; i="5.69,256,1571695200"; d="scan'208,217"; a="92633371"
X-MGA-submission: =?us-ascii?q?MDF1SDpExwCEgbRw3Nl9cI3HNdZfgQ7X+1OVCG?= =?us-ascii?q?+7tnbQor1116Dc2gXqqsvzghd+6v1MvpXmBTiZy4DRDN7Nh8Rl2GmteN?= =?us-ascii?q?VXkryGskexgnP58sJecpxy1yWfFW0oh6e2aVpw6Uo764JszvueTCnOrg?= =?us-ascii?q?HAf1poRPFMi6abKN8HRsHh6g=3D=3D?=
Received: from he199743.emea1.cds.t-internal.com ([10.169.119.51]) by QDEFCV.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 09 Apr 2020 09:18:39 +0200
Received: from HE199743.EMEA1.cds.t-internal.com (10.169.119.51) by HE199743.emea1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 9 Apr 2020 09:18:37 +0200
Received: from HE104162.emea1.cds.t-internal.com (10.171.40.37) by HE199743.EMEA1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 9 Apr 2020 09:18:37 +0200
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.17) by O365mail04.telekom.de (172.30.0.231) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 9 Apr 2020 09:18:39 +0200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MPIlajj+wNimBRqsnbPpIhgTs8sdprjgRqS6ppLjTmftr1McNBV0XHtU0B6LjNfBZIAySyvZJyFVz9RcutvGlI8E5tOMog/8a3Zu76jj0BwFT3DvB7iCe1HAwTM8bS3NYgU6TzIpLYKc+sqs2Wy7VP/kr2Sbet3oDFk+r86TznN1fe/Rzj6HaxmRc4Nlggfq1DBwYZcI+V1mz3FiYM3I2qYrkIYF4NbZFcXc1naKvHNUOKG/Wwr0weGYpBFZwP15DMOI6uBo/x1WJbbTucwn1t8d5ZSwGTeyRUCYOVO1fKXF4tcMLHLcND+tWOag6lxHwciJ6PlhH5QUYP0tAFzslQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PeAchqCHkxz47zyry12C7dhRquXhhQRp1FIBuNQ3vpU=; b=PmMe4dx8jlzHOJtE5n9qZt2wTwykfu65bGa5gGygXnD7GB2qOmx38sLNNIp7tuIV7ZGyGjQdRVYe4ZOa6OWrPXpSaPgLzYmGBNbM18DXnjBEToulRgdWAPWp1wUy5GJ2D/cBEYcT9cpgZhAvX86j3C2HJkyq4hCwHRZ47MLi5ExOt5Gaxpd/jdM3CcQ6PJPtnCPOFON5co6n7+AeNJbRRPHdzC1fItfY5tj3+jntDxLheB8OFs8VTnFQ+rX3evTnzIXnGxJ9kt5tYVqnxeFweEEzBpkoc6vSej139SMh5JUAPjJrDx/L2Ji6fmdw6iiFbmvHxqubW3JxGJwPjIWfiQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from FRAPR01MB0130.DEUPRD01.PROD.OUTLOOK.DE (10.158.136.154) by FRAPR01MB1025.DEUPRD01.PROD.OUTLOOK.DE (10.158.130.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.20; Thu, 9 Apr 2020 07:18:37 +0000
Received: from FRAPR01MB0130.DEUPRD01.PROD.OUTLOOK.DE ([fe80::cd90:80ee:d36e:6853]) by FRAPR01MB0130.DEUPRD01.PROD.OUTLOOK.DE ([fe80::cd90:80ee:d36e:6853%4]) with mapi id 15.20.2878.023; Thu, 9 Apr 2020 07:18:37 +0000
From: <Ruediger.Geib@telekom.de>
To: <spencerdawkins.ietf@gmail.com>
CC: <tsvwg@ietf.org>
Thread-Topic: [tsvwg] Interim meeting agenda for TSVWG April Interim Meetings
Thread-Index: AQHWC+K42MDBvfF4V0W1rPFWsPszDKhvap8AgAB6sQCAABWmgIAAZLrg
Date: Thu, 9 Apr 2020 07:18:36 +0000
Message-ID: <FRAPR01MB0130D61B392472FF117C6AFC9CC10@FRAPR01MB0130.DEUPRD01.PROD.OUTLOOK.DE>
References: <CAKKJt-etYiZes-qRJCHUGwOaKq4KTXQQo0p-++WRy+bytT_wDQ@mail.gmail.com> <202004082336.038NaaBV002631@gndrsh.dnsmgr.net> <CAKKJt-eoE9511eSR1mjDh2gyaacSnON5bBEPJGXOG1umLTdc1w@mail.gmail.com>
In-Reply-To: <CAKKJt-eoE9511eSR1mjDh2gyaacSnON5bBEPJGXOG1umLTdc1w@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.187]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7dca6db4-9277-40cc-29ef-08d7dc563891
x-ms-traffictypediagnostic: FRAPR01MB1025:
x-microsoft-antispam-prvs: <FRAPR01MB10258C975203D15BE4B4FCC99CC10@FRAPR01MB1025.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0368E78B5B
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:FRAPR01MB0130.DEUPRD01.PROD.OUTLOOK.DE; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(396003)(366004)(39860400002)(136003)(346002)(376002)(66574012)(64756008)(66446008)(6916009)(4326008)(478600001)(66476007)(85182001)(26005)(76116006)(66556008)(186003)(66946007)(86362001)(19627235002)(316002)(85202003)(9686003)(33656002)(81156014)(8936002)(9326002)(7696005)(8676002)(2906002)(5660300002)(55016002)(81166007)(71200400001)(777600001); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: T8WpIhQfPN51Q5vmuQUL6R4jI/4X/zcbMf6ROm8SyQRZHZj7CdRhRDU0WZ+OSWNK5VRmT/4hv0Vu+kdDfXhtvuhXYYp/0wnc65ZZz1LOmGEjvKYkdmJsdZQ1x2IhPNBzUQ4ulNKzr1BONt0mOnJfCmlGxINKJWhloSA+85KvlxNiGSOtwLJwuaFHigiCRmasSdt7xJYmU+Axj9m/ZiyaRQTwdshYwbz5xnSvW/CKCAkxasONHQS/hNuX7VG6rD8MCr4YMEo/7NKFZprXIqJfKtK3vYbRSNjriZaY5wVXOkBZlqhqvRs+/g2WcS9xgzXVKlkMARZ0yH/SfvUo9+QyE9YKyOsrFPXGdc73NrSoL10dWQIRtu/NBv3IqUITwEUWcHfDS/MDh17BoX3tuEhAMSejMaA4vJxBZeLCu48DktXFKBTyuagQqfmchUcRCt67VJLxy8Vako22s+72qAgRp9rbtdmCv2Qk27uObXAnAjwSOmc+at/BOFhRBgZaY1n/
x-ms-exchange-antispam-messagedata: fTHiUKZBWDNiDfN3umvsoq4F6KLppjJeGsSrDpLd4rsj8bZ21t/ffRK+uWiprkD1D6hKjSu1xbAk4C00xbRJPkIZjHxWNhtmkYyzNQiLKlrAc3Qgdk/cL1LOyp0/faWgTQbHmJfIkMcbj9JMoxOk2w==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_FRAPR01MB0130D61B392472FF117C6AFC9CC10FRAPR01MB0130DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7dca6db4-9277-40cc-29ef-08d7dc563891
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Apr 2020 07:18:36.9680 (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: VHv3VmthEMrLHcChvMM9yAZR+JQkCnu6j7p5WM2+xLEHS6P4DNPTOeEoEXd+XVhCZ5LBvzPfoyBGwTfaS24i29Y3LGUDXspGI5froXN7xuc=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB1025
X-TM-SNTS-SMTP: F7F1B1A5081868BF5BA9A28606BED403F849E7E814EAFBD1D6F313E6577DE2272000:8
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/zAP9RmzMlIXYGJqkd92rPeXAvgg>
Subject: Re: [tsvwg] Interim meeting agenda for TSVWG April Interim Meetings
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: Thu, 09 Apr 2020 07:18:43 -0000

Hi Spencer,



I tried to get in contact with 3GPP when LTE and the QCI were introduced.

  *   QCIs are no markings. They are assigned to their connections  from policy node to terminal.
  *   There’s been a 9 standard QCI set which was mapped in no easy to aggregate way to their DiffServ scheme (GSMA IR.34). I proposed changes.
  *   The standard QCIs are not binding. There’s also no binding subset or minimum subset to implement.
  *   The mapping of standard QCIs to applications is not binding.
  *   There are many more private QCIs, which saw deployment at that time.
  *   LTE and likely 5G schedulers are proprietary.



I stopped working on that.



The best idea that I’ve heard was to introduce a DiffServ scheduler at the LTE(5G) sender and run the wireless section without these QCIs on a best effort base for all mobile terminals (the have a terminus for that mode of operating the wireless section). That would require a rather strong push from the mobile operators.



I didn’t follow their work on 5G QoS.



Regards.



Ruediger





Von: tsvwg <tsvwg-bounces@ietf.org> Im Auftrag von Spencer Dawkins at IETF

Gesendet: Donnerstag, 9. April 2020 02:54

An: Rodney W. Grimes <ietf@gndrsh.dnsmgr.net>

Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>uk>; tsvwg@ietf.org

Betreff: Re: [tsvwg] Interim meeting agenda for TSVWG April Interim Meetings



Hi, Rodney,



On Wed, Apr 8, 2020 at 6:36 PM Rodney W. Grimes <mailto:ietf@gndrsh.dnsmgr.net> wrote:

> I didn't say this at the mike, so it won't be in the minutes, but ...

>

> On Mon, Apr 6, 2020 at 2:12 AM Gorry Fairhurst <mailto:gorry@erg.abdn.ac.uk> wrote:

>

> > TSVWG,

> >

> > Here is the (shortened) agenda for the on-line interim meetings, based

> > on the Agenda submitted for the Vancouver IETF. If you are scheduled to

> > present in Interim 1 (WG document status), please send slides for us to

> > upload to the meeting materials page. We will shortly distribute

> > information for Interim 2.

> >

> > Best wishes,

> >

> > Gorry

> >

> > (TSVWG Co-Chairs)

> >

> > ---

> >

> > Wednesday Apr-08-2020 1000

> > 0700-0930 UTC-7 (San Francisco) = 1000-1230 UTC-4 (Boston) = 1500-1730

> > UTC+1 (London) = 1600-1830 UTC+2 (Berlin) = 2200-0030[+1] UTC+8 (Beijing

> > - not on summer time, other 4 are)

> >

> > TSWG Interim #1

> >

>

> (deleted down to)

>

>          6.2   Jerome Henry: QCI and Diffserv API (10 mins)

> >          draft-henry-tsvwg-diffserv-to-qci

> >

>

> The other reason I hope TSVWG pushes a bit more in this space is that the

> final answer may be either "you guys should really be using diffserv" or

> "you guys are working on new 5G markers and you can't map the ones you

> already have onto diffserv now, so good luck" ... and I could live with

> either answer, if it was written down.

>

> No snark intended.

>

> Best,

>

> Spencer



A strong +1, I do understand that the carriers have a far more

robust set of traffic types to deal with, but I would think

some order of alignment in the space should be attempted.



Infact given that the carriers are also carriers of internet

traffic I would of thought that some mapping was already in

place.



^^^^ THIS. I hadn't ever asked myself that question, but that might be a good question for us to keep in mind.



What DO they do now?



Best,



Spencer