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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Sat, 20 July 2019 11:45 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 8F966120A91; Sat, 20 Jul 2019 04:45:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.797
X-Spam-Level:
X-Spam-Status: No, score=-1.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, TRACKER_ID=0.1, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 lHfofhhxsS0V; Sat, 20 Jul 2019 04:45:07 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0648F120020; Sat, 20 Jul 2019 04:45:07 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id p197so23465849lfa.2; Sat, 20 Jul 2019 04:45:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lPZn5idY1ue7gFuF7YkLocbRxQcZ3thUdO9vyVIjxrk=; b=bySXCJo28bNbdOKif4eG/ELUqqnFczfX/jgWuzrnkO7aCpgc7j6HnWWKFwPQptW3fi qeSCTMIeKAW/L1zZRWqT+cgQQAGGODzo7kKmMeVmnxcM9l1K6XKsAoih8VdNLMEiG1Yb qMX88SWS0982T4KJZnIfa+As5uUyTwwGVCF7Yaw0TOKEd7I5PnMl8kKMNXvit5fTBeRJ bdqmUjw2Vqf7ibC6S8miDEHSK2bXwDcBqv9D1Xn95187JRyZA5RZK7kAOdwg86Dwyhyt z1khGh1+OKJD8miCizJsHkIGyO2QR0TluRO1qPmafDKR4+RRa9H1Cm7wyC6hkjjz2CZK TNlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lPZn5idY1ue7gFuF7YkLocbRxQcZ3thUdO9vyVIjxrk=; b=bXsLUbHIFVv9oRtQg/UuBJAX/+cCs2uayQNpUNjOTIa4EXuCh9THcUv6gvH0j/T7k3 Tu1GDkLNIV+XvPL0htQSBZqGVegNoEIMky16U2m204PBdMWuvjAuWKeSN5vf2Y2Clq8G ZXxmObXx5pbFtiJ4FYjmhebiQjQDrJoSu9GW6E3AIWXCltr0VtWSaBxZ5ZdNezvLsgFd uW4BUr6aTeYRquTHAX1JAZYgVlovwcyMUIL/B+0MeFGkhhREh2ifrFbPk+6KRtDq9mjO gBStnd8J3dGgC3mfQDeccMMZgQ9K1SnXioO950Z1aESFvmkUFiD8l93PmJmftnFSCOpJ 9kNQ==
X-Gm-Message-State: APjAAAX4736L7Wgn6kVQ5QPVlYQxKlx1v8ambMT6S33cUEpOYHGqhtSx tL9wmm9+vqoIJr3r32ejuy+qtrecsN70Seda/5w=
X-Google-Smtp-Source: APXvYqxAC17N5KCxkPk+/c3Hv6HTCA8X9OvxSVq4/mSFGrMQth1LMLYrmdR6SahuWxNtLIiUaH2dqjVrS5MVVZubeyw=
X-Received: by 2002:ac2:43d0:: with SMTP id u16mr26667869lfl.38.1563623105121; Sat, 20 Jul 2019 04:45:05 -0700 (PDT)
MIME-Version: 1.0
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> <HE1PR0701MB252211895E63BCA7EC95320895C80@HE1PR0701MB2522.eurprd07.prod.outlook.com> <b2dabbe7-55cf-4b1f-814f-0b5d8562f031@Spark> <DB8PR07MB6364E51C3DE14458DC253E7983CB0@DB8PR07MB6364.eurprd07.prod.outlook.com>
In-Reply-To: <DB8PR07MB6364E51C3DE14458DC253E7983CB0@DB8PR07MB6364.eurprd07.prod.outlook.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sat, 20 Jul 2019 07:44:37 -0400
Message-ID: <CAKKJt-dEkmCph+oCcPFmxznSZVQ_kBj-WPTT2tH8Z=nh9unOwg@mail.gmail.com>
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, "lionel.morand@orange.com" <lionel.morand@orange.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "vshaikh@perspectalabs.com" <vshaikh@perspectalabs.com>, "md3135@att.com" <md3135@att.com>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>, "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>, "sdas@perspectalabs.com" <sdas@perspectalabs.com>
Content-Type: multipart/alternative; boundary="000000000000be53c8058e1b5ffc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/0VZXrvbuciaqSbs6wVNjLqSkdWo>
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: Sat, 20 Jul 2019 11:45:12 -0000

Hi, Gonzalo,

On Fri, Jul 19, 2019 at 3:07 AM Gonzalo Camarillo <
gonzalo.camarillo@ericsson.com>; wrote:

> Last time Spencer had lunch served in the meeting room, but we all knew
> his were big shoes to fill! ;-) Magnus?
>

I believe the shoes you are looking for were Robert Sparks' shoes, as an
IAB lead for the Liaison Oversight program. The co-leads now are Mark
Nottingham and Robin (Zhenbin) Li.

But if Magnus can request lunch, that's excellent!

Spencer


>
> Cheers,
>
>
>
> Gonzalo
>
>
>
> *From:* Jeff Tantsura <jefftant.ietf@gmail.com>;
> *Sent:* Thursday, July 18, 2019 23:12
> *To:* Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>;;
> lionel.morand@orange.com; Magnus Westerlund <
> magnus.westerlund@ericsson.com>;
> *Cc:* tsvwg-chairs@ietf.org; vshaikh@perspectalabs.com;
> sdas@perspectalabs.com; md3135@att.com; 3gpp-ietf-coord@ietf.org
> *Subject:* Re: [3gpp-ietf-coord] Re : QCI to Diffserv mapping
>
>
>
> Magnus,
>
>
>
> Do we need to bring our lunches?
>
> Thanks!
>
>
>
> Cheers,
>
> Jeff
>
> On Jul 18, 2019, 7:33 AM -0700, Magnus Westerlund <
> magnus.westerlund@ericsson.com>;, wrote:
>
> 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 <md3135@att.com>>;
>
>
> On Jul 3, 2019, at 2:51 PM, Gonzalo Camarillo
> <Gonzalo.Camarillo@ericsson.com
> <mailto:Gonzalo.Camarillo@ericsson.com
> <Gonzalo.Camarillo@ericsson.com%0b%3cmailto: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 <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 <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 <3gpp-ietf-coord@ietf.org>>;
>
> Cc : tsvwg-chairs@ietf.org
> <mailto:tsvwg-chairs@ietf.org <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 <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
> <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 <3gpp-ietf-coord@ietf.org>>;
>
> Cc : tsvwg-chairs@ietf.org
> <mailto:tsvwg-chairs@ietf.org <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
> <https://protect2.fireeye.com/url?k=1c04ae4e-408e7bfa-1c04eed5-866a015dd3d5-7a0ab7efac9dcd51&q=1&u=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-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
> <https://protect2.fireeye.com/url?k=e5cb483b-b9419d8f-e5cb08a0-866a015dd3d5-e1aa9d1bcc75f269&q=1&u=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-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 <magnus.westerlund@ericsson.com>>;
>
>
> ---------------------------------------------------------------------
> -
>
>
>
>
> _______________________________________________
>
> 3gpp-ietf-coord mailing list
>
> 3gpp-ietf-coord@ietf.org
> <mailto:3gpp-ietf-coord@ietf.org <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 <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 <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
> <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
> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
>
> _______________________________________________
> 3gpp-ietf-coord mailing list
> 3gpp-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
>