Re: [3gpp-ietf-coord] =?utf-8?Q?Re=C2=A0=3A__?=QCI to Diffserv mapping

Jeff Tantsura <jefftant.ietf@gmail.com> Thu, 18 July 2019 20:12 UTC

Return-Path: <jefftant.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 E603B120112; Thu, 18 Jul 2019 13:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, TRACKER_ID=0.1, URIBL_BLOCKED=0.001] autolearn=ham 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 JGXMo8y1cxh8; Thu, 18 Jul 2019 13:12:07 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 9A9C51200EF; Thu, 18 Jul 2019 13:12:07 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id b13so13117828pfo.1; Thu, 18 Jul 2019 13:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=+K2a1O94I9dm6UgAMeVxf48jTJa//AM5BLrqyKjN68Q=; b=nFIkwgfDjsfkr1m0Y98dro3v/IyDR+6lOLFbUC98zKVVrllCStqbzXAZJBMTTiJvVc 4UW+YQ8unqYmadvouk+Jj2GYJz3YvfLoTgZrzVvvgnTpz6yhPDkTbwTmYKr4ky6McG/b HWAgS1eFK3e3z2O0Ehp5wAmcgKzq3ldPMCBMleOOJsesb2vr7Ns00c49AKnDOYCKky4V nAzdrlyqf1DVTK9wpByArJydtwPOOdKy55wYI3TEdv3fuLizx7SEYYtDmQ2UTyaqaCkg ditUxmCxAhZhBrOtdKyCWNgZXCKZph2LYKivwDT7pkmKvvpMZKoxx74WcckKiNt+FJPu odqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=+K2a1O94I9dm6UgAMeVxf48jTJa//AM5BLrqyKjN68Q=; b=QMJZjp+8+P95hgUBFVTuXXFbFLB8N8j7mIO9/G6Aq2UylnjnP3FGOLfoUHTw0iDJao lpppvAeTrEKqkymxxafSxq6WcX37wVYbVOu4QfzynxL66SiftkjwBsGdMDIs82FdQ4pE +3/h1W5m4dc8h1muyk15WkdUx+Q1IcCfmV7IEJd3PVIZ2fL+rw6XCtcaEFHANGMTxW3S R67VwwIoO5oTKpjYNG/jHraIwihFaAFaQcVAThGTFvGQRMwoQYDzZF/41qFUTJPIK0Aj ApZLzRhF6L5lBHiVj6FOTJd4/Mq9MD4bHUqTrBzDooir9kYmZSVEhHfANLAvkEhZ3tbX 6iRQ==
X-Gm-Message-State: APjAAAXEkHU/VgZN7nW4nGxB82VqAB9X3nknMoGAf72XijmU8neWcZf6 +lwSPOON/xQfS1hQsqOq/Ks=
X-Google-Smtp-Source: APXvYqwcxptiZvt5k0mKcr7PanyTIFKT6edkcb33fMoohHFif7otxSP1N9ds6i9TbhOZGpVaZdVzVA==
X-Received: by 2002:a17:90a:a407:: with SMTP id y7mr53053694pjp.97.1563480726991; Thu, 18 Jul 2019 13:12:06 -0700 (PDT)
Received: from [10.5.5.194] ([50.235.77.202]) by smtp.gmail.com with ESMTPSA id k22sm31255683pfk.157.2019.07.18.13.12.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Jul 2019 13:12:06 -0700 (PDT)
Date: Thu, 18 Jul 2019 13:11:57 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "=?utf-8?Q?lionel.morand=40orange.com?=" <lionel.morand@orange.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: "=?utf-8?Q?tsvwg-chairs=40ietf.org?=" <tsvwg-chairs@ietf.org>, "=?utf-8?Q?vshaikh=40perspectalabs.com?=" <vshaikh@perspectalabs.com>, "=?utf-8?Q?sdas=40perspectalabs.com?=" <sdas@perspectalabs.com>, "=?utf-8?Q?md3135=40att.com?=" <md3135@att.com>, "=?utf-8?Q?3gpp-ietf-coord=40ietf.org?=" <3gpp-ietf-coord@ietf.org>
Message-ID: <b2dabbe7-55cf-4b1f-814f-0b5d8562f031@Spark>
In-Reply-To: <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> <HE1PR0701MB252211895E63BCA7EC95320895C80@HE1PR0701MB2522.eurprd07.prod.outlook.com>
X-Readdle-Message-ID: b2dabbe7-55cf-4b1f-814f-0b5d8562f031@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5d30d293_bb02f47_c7f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/uxyOB4j1K_R0QdZ7b1y2DHdgRLU>
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 20:12:11 -0000

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>
> > > >
> > > >
> > > > 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.
> > > >
>
> _______________________________________________
> 3gpp-ietf-coord mailing list
> 3gpp-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord