Re: [3gpp-ietf-coord] proposed agenda for the next F2F coordination meting at IETF#105
Mirja Kuehlewind <ietf@kuehlewind.net> Mon, 22 July 2019 15:58 UTC
Return-Path: <ietf@kuehlewind.net>
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 F2430120052 for <3gpp-ietf-coord@ietfa.amsl.com>; Mon, 22 Jul 2019 08:58:29 -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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 fKTOTHU-R1IF for <3gpp-ietf-coord@ietfa.amsl.com>; Mon, 22 Jul 2019 08:58:26 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 2C057120300 for <3gpp-ietf-coord@ietf.org>; Mon, 22 Jul 2019 08:58:08 -0700 (PDT)
Received: from [2001:67c:370:128:b580:cb32:cddf:55c1]; authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1hpahS-0008FQ-1Y; Mon, 22 Jul 2019 17:58:06 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <27722_1563810928_5D35DC70_27722_247_6_6B7134B31289DC4FAF731D844122B36E3A1AC181@OPEXCAUBM41.corporate.adroot.infra.ftgroup>
Date: Mon, 22 Jul 2019 11:58:02 -0400
Cc: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Roland Jesske <r.jesske@telekom.de>, "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A3942780-A0FE-4604-B37D-806CA26163BC@kuehlewind.net>
References: <2661_1563547288_5D31D698_2661_14_1_6B7134B31289DC4FAF731D844122B36E3A1A85CB@OPEXCAUBM41.corporate.adroot.infra.ftgroup> <24133_1563802659_5D35BC22_24133_93_1_2672711f-3585-4178-ae7f-0b8a52e718a0@OPEXCAUBM8F.corporate.adroot.infra.ftgroup> <FRXPR01MB0743853A340FA345F23D1158F9C40@FRXPR01MB0743.DEUPRD01.PROD.OUTLOOK.DE> <16785_1563809386_5D35D66A_16785_280_10_6B7134B31289DC4FAF731D844122B36E3A1AC09F@OPEXCAUBM41.corporate.adroot.infra.ftgroup> <11011_1563809913_5D35D878_11011_18_1_c0107038-005c-4167-b8aa-582ebe9e838c@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <DB8PR07MB636401C1155F87DC89B09B7483C40@DB8PR07MB6364.eurprd07.prod.outlook.com> <27722_1563810928_5D35DC70_27722_247_6_6B7134B31289DC4FAF731D844122B36E3A1AC181@OPEXCAUBM41.corporate.adroot.infra.ftgroup>
To: lionel.morand@orange.com
X-Mailer: Apple Mail (2.3445.104.11)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1563811088;d95a5d0a;
X-HE-SMSGID: 1hpahS-0008FQ-1Y
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/fAQ6jkrUZDOgsAbd1MNEwKUiG94>
Subject: Re: [3gpp-ietf-coord] proposed agenda for the next F2F coordination meting at IETF#105
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: Mon, 22 Jul 2019 15:58:30 -0000
Yes, we didn’t start the meeting yet. Only Gonzalo is in the room. Everybody else is still in other meetings. > On 22. Jul 2019, at 11:55, <lionel.morand@orange.com> <lionel.morand@orange.com> wrote: > > The meeting only starts at 12pm. So it is not possible to access the bridge > > De : Gonzalo Camarillo [mailto:gonzalo.camarillo@ericsson.com] > Envoyé : lundi 22 juillet 2019 17:49 > À : MORAND Lionel TGI/OLN; Roland Jesske; 3gpp-ietf-coord@ietf.org > Objet : RE: proposed agenda for the next F2F coordination meting at IETF#105 > > Hi, > > I am already in the room. FYI: They just finished installing the conference unit so that we can have remote participants join the meeting. > > Cheers, > > Gonzalo > > From: 3gpp-ietf-coord <3gpp-ietf-coord-bounces@ietf.org> On Behalf Of lionel.morand@orange.com > Sent: Monday, July 22, 2019 11:39 > To: MORAND Lionel TGI/OLN <lionel.morand@orange.com>; Roland Jesske <r.jesske@telekom.de>; 3gpp-ietf-coord@ietf.org > Subject: Re: [3gpp-ietf-coord] proposed agenda for the next F2F coordination meting at IETF#105 > > Updated version of the slides, including missing drafts. > > De : 3gpp-ietf-coord [mailto:3gpp-ietf-coord-bounces@ietf.org] De la part de lionel.morand@orange.com > Envoyé : lundi 22 juillet 2019 17:30 > À : R.Jesske@telekom.de; 3gpp-ietf-coord@ietf.org > Objet : Re: [3gpp-ietf-coord] proposed agenda for the next F2F coordination meting at IETF#105 > > OK, I will add them > > De : R.Jesske@telekom.de [mailto:R.Jesske@telekom.de] > Envoyé : lundi 22 juillet 2019 17:24 > À : MORAND Lionel TGI/OLN; 3gpp-ietf-coord@ietf.org > Objet : AW: proposed agenda for the next F2F coordination meting at IETF#105 > > Hi Lionel, > I’m missing two dependencies within your slides: > > 1. [266] draft-ietf-sipcore-locparam-01 (January 2019): "Location Source Parameter for the SIP Geolocation Header Field". In TS 24.229 IMS Protoc16 (UPDATE will appear this week) > > 2. [52B] draft-jesske-update-p-visited-network-00 (July 2017): "Update to Private Header Field P-Visited-Network-ID in Session Initiation Protocol (SIP) Requests and Responses". TS 24.229 IMS Protoc 8 (is now Version 01 til sep 2019) > > I would be happy if we could proceed with these drafts. > > Thank you and Best Regards > > Roland > > > > Von: 3gpp-ietf-coord <3gpp-ietf-coord-bounces@ietf.org> Im Auftrag von lionel.morand@orange.com > Gesendet: Montag, 22. Juli 2019 15:38 > An: MORAND Lionel TGI/OLN <lionel.morand@orange.com>; 3gpp-ietf-coord@ietf.org > Betreff: Re: [3gpp-ietf-coord] proposed agenda for the next F2F coordination meting at IETF#105 > > Dear all, > > Please find the slides that will be used for our coordination meeting today. > > Reagrds, > > Lionel > > De : 3gpp-ietf-coord [mailto:3gpp-ietf-coord-bounces@ietf.org] De la part de lionel.morand@orange.com > Envoyé : vendredi 19 juillet 2019 16:41 > À : 3gpp-ietf-coord@ietf.org > Objet : [3gpp-ietf-coord] proposed agenda for the next F2F coordination meting at IETF#105 > > Hi, > > Here is a draft agenda for the coordination meeting on Monday lunch time : > • Round table > • Ongoing LS > • Ongoing IANA action > • Status of the 3GPP-IETF dependencies > • Discussion on the proposed QCI/DiffServ mapping > > Let me know if you see other topics to address during this meeting. > > Best Regards > > <image001.jpg> > > Lionel Morand > Chair of 3GPP TSG CT > Chair of IETF Dime and Radext WGs > Core Network Senior Architect and Diameter expert > Cell. +33 6 07 75 89 36 > Off. +33 1 57 39 62 57 > lionel.morand@orange.com > > _________________________________________________________________________________________________________________________ > > 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. > _________________________________________________________________________________________________________________________ > > 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. > _________________________________________________________________________________________________________________________ > > 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. > _________________________________________________________________________________________________________________________ > > 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. > _________________________________________________________________________________________________________________________ > > 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] proposed agenda for the next F2… lionel.morand
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Gonzalo Camarillo
- Re: [3gpp-ietf-coord] proposed agenda for the nex… lionel.morand
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Christer Holmberg
- Re: [3gpp-ietf-coord] proposed agenda for the nex… DOLLY, MARTIN C
- [3gpp-ietf-coord] Re : proposed agenda for the ne… lionel.morand
- Re: [3gpp-ietf-coord] proposed agenda for the nex… DOLLY, MARTIN C
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Adam Roach
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Mirja Kuehlewind
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Christer Holmberg
- Re: [3gpp-ietf-coord] proposed agenda for the nex… lionel.morand
- Re: [3gpp-ietf-coord] proposed agenda for the nex… R.Jesske
- Re: [3gpp-ietf-coord] proposed agenda for the nex… lionel.morand
- Re: [3gpp-ietf-coord] proposed agenda for the nex… lionel.morand
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Gonzalo Camarillo
- Re: [3gpp-ietf-coord] proposed agenda for the nex… lionel.morand
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Mirja Kuehlewind
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Gonzalo Camarillo
- Re: [3gpp-ietf-coord] proposed agenda for the nex… Gonzalo Camarillo