Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"
"Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com> Sat, 07 July 2018 19:18 UTC
Return-Path: <Kalyani.Bogineni@verizonwireless.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6063B130EA1 for <dmm@ietfa.amsl.com>; Sat, 7 Jul 2018 12:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level:
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizonwireless.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 4t_ry3aZ7GzF for <dmm@ietfa.amsl.com>; Sat, 7 Jul 2018 12:18:33 -0700 (PDT)
Received: from mercury.verizonwireless.com (mercury.verizonwireless.com [162.115.227.109]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDA44130E9C for <dmm@ietf.org>; Sat, 7 Jul 2018 12:18:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizonwireless.com; i=@verizonwireless.com; q=dns/txt; s=prodmail; t=1530991112; x=1562527112; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=QBuXvjzxPhH+v8Je6xKk4UFItTZPoZpLC/EtkxGTc9M=; b=X0gcLGFk8FSexoZgpZuVS6LHe1tuqNZn2fHWFlhwC1mIRHAClUt0Bp/u UOI35hPDhhIZ32XchCc6HY72gEEUT3jbFx1kIcrXBGGvCQjRtF9R4+9U8 FjjlbDJ4SYn7Pm+0R1bazHM4Jdc0lABSZ2qHVLheBlFaTv1uIuwSydO4z k=;
X-Host: viking.odc.vzwcorp.com
Received: from casac1exh002.uswin.ad.vzwcorp.com ([10.11.218.44]) by mercury.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 07 Jul 2018 19:18:29 +0000
Received: from scwexch05apd.uswin.ad.vzwcorp.com (153.114.130.24) by CASAC1EXH002.uswin.ad.vzwcorp.com (10.11.218.44) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sat, 7 Jul 2018 12:18:28 -0700
Received: from scwexch12apd.uswin.ad.vzwcorp.com (153.114.130.31) by scwexch05apd.uswin.ad.vzwcorp.com (153.114.130.24) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sat, 7 Jul 2018 12:18:25 -0700
Received: from scwexch12apd.uswin.ad.vzwcorp.com ([153.114.130.31]) by scwexch12apd.uswin.ad.vzwcorp.com ([153.114.130.31]) with mapi id 15.00.1365.000; Sat, 7 Jul 2018 12:18:25 -0700
From: "Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com>
To: "Sri Gundavelli (sgundave)" <sgundave=40cisco.com@dmarc.ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"
Thread-Index: AQHUFhxOpr0X0I4hEU2E4wqxMx49W6SEIV3Q
Date: Sat, 07 Jul 2018 19:18:25 +0000
Message-ID: <73d4a20e761a4fdeb30493bd2f950438@scwexch12apd.uswin.ad.vzwcorp.com>
References: <D7664D24.2BD242%sgundave@cisco.com>
In-Reply-To: <D7664D24.2BD242%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.11.60.250]
Content-Type: multipart/mixed; boundary="_003_73d4a20e761a4fdeb30493bd2f950438scwexch12apduswinadvzwc_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/ijpij4UnKNRwwVNbT27dLgig4N0>
Subject: Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jul 2018 19:18:36 -0000
Sri: The LS response is fine as it reflects the status of the work in IETF. I am not sure when you plan to send the LS response since you requested feedback by July 13th. FYI, The next CT4 meeting is from July 9-13th as seen from the attached meeting Invitation. Attached is the meeting agenda - Input LSs will be processed on Monday July 9th from 9:00 - 11:30 AM. Regards, Kalyani -----Original Message----- From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli (sgundave) Sent: Saturday, July 7, 2018 2:00 PM To: Arashmid Akhavain <arashmid.akhavain@huawei.com>; dmm@ietf.org Subject: [E] Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC" Folks - Here is the response in pending state. We are holding for WG feedback. If you have any objections too this, please let us know by 13th of July, 2018. https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_liaison_1586_&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=qxXTZYI7pMD_45zlLf4jtPJrGH6H0ygd_lgk8PE1o24&s=77-_DB88Sb27VyXuBt7_1OKS1QMBOTs_A_Ln-pGFsYc&e= Sri On 7/6/18, 11:25 PM, "dmm on behalf of Sri Gundavelli (sgundave)" <dmm-bounces@ietf.org on behalf of sgundave=40cisco.com@dmarc.ietf.org> wrote: >Hi Arashmid, > >Thanks for the feedback. > >I have added a link to the DMM WG pages and it has links to all the DMM >documents. I think that should be OK, we don’t have to explicitly list >out every single I-D at this stage. As we move forward and based on WG >discussions/progress, we can provide more detailed feedback on each >document. I suggest we keep this simple for now. > > > >> So, what happens next? We wait for their reply? > >This is just a response to the LS; more an information exchange on the >status/progress. > > > >Regards >Sri > > > > >On 7/6/18, 1:56 PM, "Arashmid Akhavain" <arashmid.akhavain@huawei.com> >wrote: > >>Hi Sri, >> >>We might also want to add draft-camarillo-dmm-srv6-mobile-pocs-00 >>under "Related Documents". >> >>Also, we might want to say something like: >>"Although we will NOT pick a particular approach, we will be ready to >>provide further assistance to 3GPP regarding the technical details of >>different candidates." >> >>So, what happens next? We wait for their reply? >> >>Cheers, >>Arashmid >> >>> -----Original Message----- >>> From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli >>> (sgundave) >>> Sent: 06 July 2018 13:49 >>> To: dmm@ietf.org >>> Subject: Re: [DMM] New Liaison Statement, "CP-173160: New Study Item >>> on User Plane Protocol in 5GC" >>> >>> We plan to send the following response to 3GPP CT4. If you have any >>>quick comments/corrections/suggestions, please let us know in a day. >>> >>> >>> >>> ³ >>> Thank you for your Liaison request (Reference: CP-173160) and for >>>sharing the information on the status of the CT4 study item on >>>user-plane protocol for 5GC. The IETF DMM working group wants to >>>acknowledge your request and want to share the following update. >>> >>> IETF DMM working is currently reviewing various proposals on >>>approaches for realizing optimizations in user-plane for mobile >>>packet core. These proposals include protocol specifications based >>>on new/existing protocols and proposals covering >>>requirements/analysis/comparison of various approaches. At this >>>point of time, some of these documents are working group documents >>>and some are individual submissions and yet to be adopted as working >>>group documents. Based on the working group interest, feedback >>>charter-scope, the working group may choose to adopt some of these >>>work items as working group documents and at that time will seek >>>feedback from 3GPP. >>> >>> We also would like to state that the DMM working group will not be >>>in a position to pick a single approach/solution as THE approach for >>>user-plane optimization. Most likely the working group may >>>standardize more than one approach, but will characterize each of >>>these approaches based on its technical capabilities and >>>limitations. This approach would be consistent with the approach >>>that IETF took with IPv6 transitioning work, where IETF standardized >>>multiple approaches including DSLite, NAT64, Gi-DSLite and other >>>approaches. >>> >>> Finally, IETF would like to point 3GPP to the following documents >>> under consideration. >>> >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ietf.org_id_ >>> draft-2Dbogineni-2Ddmm-2Doptimized-2Dmobile-2Duser-2Dplane-2D&d=DwIG >>> aQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGg >>> d9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=qxXTZYI7pMD_45zlLf >>> 4jtPJrGH6H0ygd_lgk8PE1o24&s=PZVdEP1rEzF40-JWBzGaYGXXFIA-J6E8VNrtCU-L >>> Xeo&e= >>> 01.tx >>> t (Individual submission) >>> >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_in >>> ternet-2Ddrafts_draft-2Dhmm-2Ddmm-2D5g-2Duplane-2Danalysis-2D&d=DwIG >>> aQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGg >>> d9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=qxXTZYI7pMD_45zlLf >>> 4jtPJrGH6H0ygd_lgk8PE1o24&s=RFXqAJd7ktCOVPOxjgWrfpkrKG_wABrZA2gvpH6P >>> 22Y&e= >>> 00.tx >>> t (Individual submission) >>> >>> >>> Related Documents: >>> >>> >>> >>>https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_id_ >>>draft-2Dietf-2Ddmm-2Dsrv6-2Dmobile-2Duplane-2D02.txt&d=DwIGaQ&c=udBTR >>>vFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKg >>>Kcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=qxXTZYI7pMD_45zlLf4jtPJrGH6H0y >>>gd_lgk8PE1o24&s=PSzx-NfxacXnnIu0yifXWiDz7-t6PqPY-paV4DNwxOw&e= >>>(Working >>> group document) >>> >>> >>> Link to DMM Pages: >>> >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.iet >>> f.org_wg_dmm_documents_&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb >>> 6__0PomBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYE >>> TcBynUdpT&m=qxXTZYI7pMD_45zlLf4jtPJrGH6H0ygd_lgk8PE1o24&s=f3434N55x1 >>> rC9NVSdFiUTjzhwsBJPkdtpy8a_vIRVcQ&e= >>> >>> >>> >>> Please let us know if you need any additional information. >>> " >>> >>> ----- >>> >>> >>> >>> >>> >>> >>> >>> >>> On 4/11/18, 11:16 AM, "Liaison Statement Management Tool" >>> <lsmt@ietf.org> >>> wrote: >>> >>> >Title: CP-173160: New Study Item on User Plane Protocol in 5GC >>> >Submission Date: 2018-04-11 URL of the IETF Web page: >>> >https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ie >>> >tf.org_liaison_1572_&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6_ >>> >_0PomBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYET >>> >cBynUdpT&m=qxXTZYI7pMD_45zlLf4jtPJrGH6H0ygd_lgk8PE1o24&s=Y5tfX_Bnem >>> >dhocQwO2YoxurotS34WWP7G_RHmWTrl-4&e= >>> >Please reply by 2018-07-20 >>> >From: Satoru Matsushima <satoru.matsushima@g.softbank.co.jp> >>> >To: Sri Gundavelli <sgundave@cisco.com>,Dapeng Liu >>> ><maxpassion@gmail.com> >>> >Cc: Dapeng Liu <maxpassion@gmail.com>,Terry Manderson >>> ><terry.manderson@icann.org>,Distributed Mobility Management >>> Discussion >>> >List <dmm@ietf.org>,Sri Gundavelli <sgundave@cisco.com>,Suresh >>> Krishnan >>> ><suresh@kaloom.com> Response Contacts: >>> >georg.mayer.huawei@gmx.com,3GPPLiaison@etsi.org >>> >Technical Contacts: >>> >Purpose: For action >>> > >>> >Body: 1. Overall Description: >>> >3GPP working group of CT4 (Core and Terminal) would like to inform >>> >the IETF that CT4 has initiated a study item on user plane protocol >>> >in 5GC for Release-16 of 5G phase 2 (see CP-173160). >>> > >>> >Based on the outcome from the IETF / 3GPP Coordination meeting at >>> >IETF#100, 3GPP CT4 got aware that IETF DMM WG is currently working >>> >on >>>a >>> >possible candidate protocol for the 3GPP 5G user plane protocol. >>> > >>> >3GPP CT4 wants to emphasize that currently there is no related >>> >evaluation ongoing in 3GPP. Nevertheless, a study item was approved >>>for >>> >such a study to start in the second half of 2018. The study will >>> >evaluate between existing solutions within 3GPP and other >>> >protocols, based on the Release >>> >16 stage 2 (system architecture) requirements. >>> > >>> >3GPP CT4 would like to point IETF DMM to the following >>> >specifications on GTP-U. The Release 16 stage 2 requirements are >>> >not yet known but it is worth looking at latest GTP-U spec which >>> >will be evaluated through the study as the existing protocol. >>> > >>> >€ [1] 3GPP TS 29.281 (V15.1.0): GPRS Tunnelling Protocol User Plane >>> >(GTPv1-U) >>> > >>> > >>> >Following technical report provides information of how 3GPP >>> >considered GTP-U apply to user plane of 5G_ph1: >>> > >>> >€ [2] 3GPP TR 29.891 (V15.0.0): 5G System Phase 1; CT4 Aspects >>> > >>> > >>> >Furthermore, 3GPP would like to give the following general guidance >>> >to IETF DMM, regarding user plane transport within 3GPP networks. >>> >These are technical specifications that include also the necessary >>> >information to understand which architectural, QoS, >>> >security-related and high-level requirements GTP-U currently complies to within 5G_ph1. >>> > >>> >€ [3] 3GPP TS 23.501 (V15.0.0): System Architecture for the 5G System >>> >€ [4] 3GPP TS 23.502 (V15.0.0): Procedures for the 5G System >>> >€ [5] 3GPP TS 23.503 (V15.0.0): Policy and Charging Framework for the >>> 5G >>> >System >>> >€ [6] 3GPP TS 33.501 (V0.6.0): Security Architecture (work in >>>progress) >>> > >>> >2. Actions: >>> >To IETF DMM: >>> >ACTION: CT4 respectfully asks IETF DMM to provide any information >>> that >>> >may be relevant to the above CT4 work by July 2018. >>> > >>> > >>> >3. Date of Next CT and CT4 Meetings: >>> >CT4#83 26th Feb 2nd Mar 2018 Montreal, CAN >>> >CT#79 19th 20th Mar 2018 Chennai, India >>> >CT4#84 16th 20th April 2018 Kunming, China >>> >CT4#85 21st 25th May 2018 Osaka, Japan >>> >CT#80 11th 12th June 2018 La Jolla, USA >>> >CT4#85-bis 9th 13th July 2018 TBD, France >>> >CT4#86 20st 24th Aug 2018 TBD, USA >>> >Attachments: >>> > >>> > CP-180116 >>> > >>> >>>>https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_li >>>>b_dt_documents_LIAISON_liaison-2D2018-2D04-2D11-2D3gpp-2Dt&d=DwIGaQ& >>>>c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGgd9M >>>>znLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=qxXTZYI7pMD_45zlLf4jt >>>>PJrGH6H0ygd_lgk8PE1o24&s=eFXZksriT8I7oyQ2VdYY02soc1SdM7QLI7EJK4O8mdU >>>>&e= >>> >sgc >>> >>>>t-ct4-dmm-cp-173160-new-study-item-on-user-plane-protocol-in-5gc-att >>>>ach >>> >men >>> >t-1.doc >>> > >>> >>> _______________________________________________ >>> dmm mailing list >>> dmm@ietf.org >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_ma >>> ilman_listinfo_dmm&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0P >>> omBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcByn >>> UdpT&m=qxXTZYI7pMD_45zlLf4jtPJrGH6H0ygd_lgk8PE1o24&s=YrIr5CHJMjB2j4e >>> bFkCLy_9NwWmV0lQpHiSgLUeFJTI&e= > >_______________________________________________ >dmm mailing list >dmm@ietf.org >https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailm >an_listinfo_dmm&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ& >r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=qx >XTZYI7pMD_45zlLf4jtPJrGH6H0ygd_lgk8PE1o24&s=YrIr5CHJMjB2j4ebFkCLy_9NwWm >V0lQpHiSgLUeFJTI&e= _______________________________________________ dmm mailing list dmm@ietf.org https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_dmm&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=qxXTZYI7pMD_45zlLf4jtPJrGH6H0ygd_lgk8PE1o24&s=YrIr5CHJMjB2j4ebFkCLy_9NwWmV0lQpHiSgLUeFJTI&e=
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- [DMM] New Liaison Statement, "CP-173160: New Stud… Liaison Statement Management Tool
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Charlie Perkins
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Uma Chunduri
- Re: [DMM] [E] Re: New Liaison Statement, "CP-1731… Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Satoru Matsushima
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Luca Muscariello
- Re: [DMM] New Liaison Statement, "CP-173160: New … Jordan Augé
- Re: [DMM] New Liaison Statement, "CP-173160: New … Giovanna Carofiglio (gcarofig)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)