Re: [3gpp-ietf-coord] draft-ietf-dmm-srv6-mobile-uplane in IETF LC

lionel.morand@orange.com Fri, 04 November 2022 15:03 UTC

Return-Path: <lionel.morand@orange.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 49804C14CF09 for <3gpp-ietf-coord@ietfa.amsl.com>; Fri, 4 Nov 2022 08:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.807
X-Spam-Level:
X-Spam-Status: No, score=-2.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxw2qJlt3Qj0 for <3gpp-ietf-coord@ietfa.amsl.com>; Fri, 4 Nov 2022 08:03:22 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81A54C15258E for <3gpp-ietf-coord@ietf.org>; Fri, 4 Nov 2022 08:03:09 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar21.francetelecom.fr (ESMTP service) with ESMTPS id 4N3kQM1Kj7z7vQ0; Fri, 4 Nov 2022 16:03:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1667574187; bh=dJdHr3mMJAKs10nfcaDkhtrpmGyK+kU1U0lzle+5VxY=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Qa3phCBlvIxnTbD8H8o6Gd7/WnVkcKD+uufmnHS95aGqm9AALtN7fFaVnD9K9PZiT R1LpvdhQelsdpQ/8NKnvme7RNcBisQcJaLTOHmaS1qfH5YuWIpSXYifbhQg4pbgPGz 0urAnOnZPaan6kJNSDEQ494NjVjSEMTVTTqU0fg+9wWKJwK+uBc890uYiT6fN+1uw5 JY+NnUX2i/vgGqw78mwG3f/XmIKQfYzD22E/gaSNKmgzo7fdQzBIPdvcZTBqGgrdPD XMTjZpixY2h0596BjY28z2ownhZw4ltAclUPVuKWKd2qnV/AFAVVl1mg5JTlr70ZnI Fq8QzIpcDpoYA==
From: lionel.morand@orange.com
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Erik Kline <ek.ietf@gmail.com>
CC: "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>, "Suresh Krishnan (sureshk)" <sureshk@cisco.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Thread-Topic: draft-ietf-dmm-srv6-mobile-uplane in IETF LC
Thread-Index: AQHY74o5/z9GIRAlXEm9FpYegHcBl64tPk6AgAADa4CAAZfukA==
Date: Fri, 04 Nov 2022 15:03:06 +0000
Message-ID: <13846_1667574187_636529AB_13846_197_2_df37f286d33e4e4d89b8e55215e980bd@orange.com>
References: <CAMGpriW=upq9V5=bPE4WK+37ke-O7EqhX35-TNrd=AXP7XFb0g@mail.gmail.com> <HE1PR07MB33557B7463D24E3A0E0D137683389@HE1PR07MB3355.eurprd07.prod.outlook.com> <CAMGpriU6QZLz+posE3WzBBC5i0jFZo8KtpajvURaEsyhvFsGyg@mail.gmail.com> <HE1PR07MB33550D97C5E6FCC403407DCC83389@HE1PR07MB3355.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB33550D97C5E6FCC403407DCC83389@HE1PR07MB3355.eurprd07.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Enabled=true; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_SetDate=2022-11-04T15:03:04Z; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Method=Standard; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Name=Orange_restricted_external.2; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ActionId=8a487146-d212-40c1-8f2e-d149bfbc6316; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ContentBits=2
x-originating-ip: [10.115.27.53]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/XV5GRtdJLLyqpuJr1unw03sf1-A>
Subject: Re: [3gpp-ietf-coord] draft-ietf-dmm-srv6-mobile-uplane in IETF LC
X-BeenThere: 3gpp-ietf-coord@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 04 Nov 2022 15:03:26 -0000

Hi Gonzalo, Erik,

I think that an LS is not required. This LS would be simply noted anyway, as it is not related to any current technical work.

I will send an email on the CT4 mailing list to kindly invite interested delegates to comment the draft before the end of the IETF last call.

Regards,

Lionel


Orange Restricted

> -----Message d'origine-----
> De : Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
> Envoyé : jeudi 3 novembre 2022 16:27
> À : Erik Kline <ek.ietf@gmail.com>; MORAND Lionel INNOV/NET
> <lionel.morand@orange.com>
> Cc : 3gpp-ietf-coord@ietf.org; Suresh Krishnan (sureshk) <sureshk@cisco.com>;
> Eric Vyncke (evyncke) <evyncke@cisco.com>
> Objet : RE: draft-ietf-dmm-srv6-mobile-uplane in IETF LC
> 
> Sounds like a plan!
> 
> Lionel, if you think a LS would be useful, please let us know.
> 
> Cheers,
> 
> Gonzalo
> 
> > -----Original Message-----
> > From: Erik Kline <ek.ietf@gmail.com>
> > Sent: Thursday, 3 November 2022 16:15
> > To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
> > Cc: 3gpp-ietf-coord@ietf.org; Suresh Krishnan (sureshk)
> > <sureshk@cisco.com>; Eric Vyncke (evyncke) <evyncke@cisco.com>;
> > lionel.morand@orange.com
> > Subject: Re: draft-ietf-dmm-srv6-mobile-uplane in IETF LC
> >
> > Thanks for this.
> >
> > I'm fine with either letting this be sufficient or sending a liaison
> > statement.
> >
> > I would say, though, that before we send a liaison statement it would be
> > good to have an informal assessment from Lionel and see what he
> > recommends.
> >
> > Thanks again,
> > -Erik
> >
> > On Thu, Nov 3, 2022 at 1:43 PM Gonzalo Camarillo
> > <gonzalo.camarillo@ericsson.com> wrote:
> > >
> > > Hi Erik,
> > >
> > > Lionel is on this mailing list and, additionally, I have cc'ed him
> > > explicitly in this response so that he does not miss it. To be clear,
> > > having made him aware of this last call informally is enough, or you
> > > would like to send a formal liaison statement to 3GPP?
> > >
> > > Cheers,
> > >
> > > Gonzalo
> > >
> > > > -----Original Message-----
> > > > From: Erik Kline <ek.ietf@gmail.com>
> > > > Sent: Thursday, 3 November 2022 13:38
> > > > To: 3gpp-ietf-coord@ietf.org
> > > > Cc: Suresh Krishnan (sureshk) <sureshk@cisco.com>; Eric Vyncke
> > > > (evyncke) <evyncke@cisco.com>; Gonzalo Camarillo
> > > > <gonzalo.camarillo@ericsson.com>
> > > > Subject: draft-ietf-dmm-srv6-mobile-uplane in IETF LC
> > > >
> > > > All,
> > > >
> > > > draft-ietf-dmm-srv6-mobile-uplane [1] is in IETF LC [2].
> > > >
> > > > It might be good to have the 3GPP liaison to the IETF be made aware.
> > > >
> > > > All help appreciated; thanks,
> > > > -Erik
> > > >
> > > > [1]
> > > > https://datatracker.ietf.org/doc/draft-ietf-dmm-srv6-mobile-uplane/
> > > > [2]
> > > >
> > https://mailarchive.ietf.org/arch/msg/dmm/e_HYQVU_BGSmBusBHGPEXMb
> > > > HNdU/

_________________________________________________________________________________________________________________________

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.