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

Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 18 July 2019 14:33 UTC

Return-Path: <magnus.westerlund@ericsson.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 1B1E712062F; Thu, 18 Jul 2019 07:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 oRoG47pYyXdA; Thu, 18 Jul 2019 07:32:57 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30066.outbound.protection.outlook.com [40.107.3.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEFC012063D; Thu, 18 Jul 2019 07:32:56 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bAnrZlEUAwMX+DdHE/ctmbscsfd9fQrdmp/N6raGl7D6pNb38yH2iQmOV5wG1P9HXkfODvcpPcQAvqf3+S4sGa08X5c9b+w5tiIDAp/LlwvXXR96fa4jWxsinX5A6IJaNzurKn5qlYBcVXxNLvD/9XSIyq+yTzGSxZVaSXfw2mCADxMPWj7R/Dl0WyrIdAomrvryTgDXEYWV537Y/C2r0lidq43LR0QAZRL57fahQHpMXRv2HMckLBn39GJT9AWV5RGlRRGPsMQn/YPGNupNip3n+pVUUlEFVC0D+ASFYCIz3CFEX/QgxCI5tUQ32yTaxnAMZxKWppibTkm2NpWtTQ==
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=UW8w8bqXmkQfJ0NE7vn1AYIZZB0UD2mQtJQspBpcBJc=; b=mrl7QcSDJwmoH//mJnuXTBff95Zx/iMIcTqynR+NKOEY9W7DJch3ZpYHPgFvadp5fHRaakkHg+NjegnOTbFWdwLCKEZ7AnSi+3tUgR2VNzpbvW2ffmjAb7OzczvgWCW7cf4ubVvqiZSAvtY1qwk07m8DVMCUDjbdbgBh0FF0roOYhH+e0hVFBjcKcBj9aUfKvQQg2GHeo2V/3Z4SiWA2F0MnMbr4NEa+3gwc+/+ybio9JJ1xlK2+xqSrRXiox7zi4dVQLwSOOwu14tl3HjzR208NPxi4DkhvwzSJOt8M7YC1hPczg2C8vHSAVpX3zsLQNfRV+bTJ309AS1ttSFhziA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=ericsson.com;dmarc=pass action=none header.from=ericsson.com;dkim=pass header.d=ericsson.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UW8w8bqXmkQfJ0NE7vn1AYIZZB0UD2mQtJQspBpcBJc=; b=ghpoWWdVKWxc73rQie2/F5szzp/H7/WRXeWsjr3LmRj+d0tslZw/6V/Moqp1iLMnGYTTs3FnhxDtiuXiIlH9mzSgYUPTGd14rvtWCFgbFzPsVib6QBL8RSl+xunGNoSHFmlps5HBYtTuSzY8GT48xMH93cpmPXVgjWzpzkWOnZg=
Received: from HE1PR0701MB2522.eurprd07.prod.outlook.com (10.168.128.149) by HE1PR0701MB2715.eurprd07.prod.outlook.com (10.168.188.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.7; Thu, 18 Jul 2019 14:32:54 +0000
Received: from HE1PR0701MB2522.eurprd07.prod.outlook.com ([fe80::3418:2814:2ee2:a22b]) by HE1PR0701MB2522.eurprd07.prod.outlook.com ([fe80::3418:2814:2ee2:a22b%4]) with mapi id 15.20.2094.009; Thu, 18 Jul 2019 14:32:54 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "lionel.morand@orange.com" <lionel.morand@orange.com>
CC: "md3135@att.com" <md3135@att.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: AQHVFf4c3g57nJxRr0WQxwTDz4Z3T6a6REWAgBYn2YCAAFK1gA==
Date: Thu, 18 Jul 2019 14:32:54 +0000
Message-ID: <HE1PR0701MB252211895E63BCA7EC95320895C80@HE1PR0701MB2522.eurprd07.prod.outlook.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> <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> <e474e62f-ed71-77bf-a5ed-9c206de10b0d@ericsson.com> <91c413d0-0425-b6aa-66a2-083023cd1eab@ericsson.com>
In-Reply-To: <91c413d0-0425-b6aa-66a2-083023cd1eab@ericsson.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=magnus.westerlund@ericsson.com;
x-originating-ip: [192.176.1.85]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 20f04a84-d338-4ead-78bb-08d70b8cd201
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(49563074)(7193020); SRVR:HE1PR0701MB2715;
x-ms-traffictypediagnostic: HE1PR0701MB2715:
x-microsoft-antispam-prvs: <HE1PR0701MB27159527D5DE58B220BE6A8E95C80@HE1PR0701MB2715.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 01026E1310
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(346002)(39860400002)(396003)(376002)(136003)(13464003)(45074003)(51444003)(199004)(189003)(53546011)(446003)(6506007)(86362001)(76176011)(8936002)(486006)(81156014)(66476007)(11346002)(81166006)(102836004)(99936001)(7696005)(325944009)(6246003)(476003)(66556008)(4326008)(68736007)(25786009)(478600001)(66616009)(76116006)(966005)(74316002)(30864003)(229853002)(44832011)(66066001)(14454004)(9686003)(256004)(561944003)(305945005)(19627235002)(2906002)(5024004)(64756008)(53936002)(53946003)(6436002)(71190400001)(55016002)(6306002)(14444005)(110136005)(52536014)(54906003)(186003)(26005)(66446008)(99286004)(316002)(5660300002)(2501003)(71200400001)(66946007)(6116002)(3846002)(7736002)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2715; H:HE1PR0701MB2522.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5Bz1D1TZ2WczSRqA8g+LTj/Jzpf6J8+mjXW7HwX41njWG3IZTMcT6/GvDTzKnaxPAyZSERbf+FHPjgmAoVatQviNFHzKlpK/9NvdoIljhkZynEi4lwREpJLg7CHPbDZpO7Yiyhyp9yiLM/U6bQmeGYvDh+bKXz2aivxW/Zi9JOXbafeqzL6wuXdQQFgN8CZJzHIKIWo9cgaqSR/aJfF+h0wsCNOWpaX9UBYG9CTIqb68MlKSMuiqQYDaNJscUNta2rHmW+tyYiuTZERVXNeDpNWsnmRF3uNkT7VmF3GIEQySGAUs/utkhotuckg6c/OctIBMldkPuqdN87950Cne7milIXekMNCo1M3jRrh0H+dqNc0zOkRNO1Yuw+e2p9FPV6tHhfopgsvd7jmkEXeMxZMjn/0EavaVO1d6qCOCMMY=
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0057_01D53D86.724DF000"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 20f04a84-d338-4ead-78bb-08d70b8cd201
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jul 2019 14:32:54.1663 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: magnus.westerlund@ericsson.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2715
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/4NxxfRjuJDVckFrN7_x0aqFi5Uc>
Subject: Re: [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: Thu, 18 Jul 2019 14:33:06 -0000

Hi,

We have been assigned the meeting room Coller on 3rd Floor.  

Cheers

Magnus Westerlund

> -----Original Message-----
> From: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>;
> Sent: den 18 juli 2019 11:35
> To: lionel.morand@orange.com; Magnus Westerlund
> <magnus.westerlund@ericsson.com>;
> Cc: DOLLY, MARTIN C <md3135@att.com>;; 3gpp-ietf-coord@ietf.org; tsvwg-
> chairs@ietf.org; vshaikh@perspectalabs.com; sdas@perspectalabs.com
> Subject: Re: Re : [3gpp-ietf-coord] QCI to Diffserv mapping
> 
> Lionel, Magnus,
> 
> I do not think I have seen any follow up on this.
> 
> Lionel, please confirm whether you have a draft agenda for the meeting on
> Monday (beyond this topic).
> 
> Magnus, per my email below, could you please secure a room for us for
> Monday lunch?
> 
> Cheers,
> 
> Gonzalo
> 
> On 04-Jul-19 10:14, Gonzalo Camarillo wrote:
> > Thanks, Lionel!
> >
> > Magnus, with the information below, do you need anything else at this
> point?
> >
> > Regarding the coordination meeting in Montreal, Magnus can probably
> > get us a room with a conference bridge (or we can use a laptop, as I
> > think we did last time). Our traditional slot for that is Monday lunch.
> >
> > By the way, do you have a draft agenda for the coordination meeting,
> > in addition to this topic?
> >
> > Cheers,
> >
> > Gonzalo
> >
> > On 04-Jul-19 01:40, lionel.morand@orange.com wrote:
> >> 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-
> ZgJ46PZ4x9UvfXkT
> >>
> AVPAgFzc3jf6cvGf6x0g&s=XunaN7YxIvVUKNlYB0LFqWpZkcOVXTV8rK7BUaJl
> vyo&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_H
> >> UMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=OV4zFc-
> ZgJ46PZ4x9UvfXkTAVPAg
> >> Fzc3jf6cvGf6x0g&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_mai
> >> lman_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_mai
> >> lman_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_mai
> >> lman_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_mai
> >> lman_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.
> >>