Re: white paper for optimized mobile user plane solutions for 5G
Arashmid Akhavain <[email protected]> Thu, 18 Jan 2018 16:09:27 +0000
| Newsgroups | gmane.ietf.mip6 |
|---|---|
| Message-ID | <D57109449177B54F8B9C093953AC5BCD6D42CF8D@YYZEML701-CHM.china.huawei.com> |
--===============5839805583157322893== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_D57109449177B54F8B9C093953AC5BCD6D42CF8DYYZEML701CHMchi_" --_000_D57109449177B54F8B9C093953AC5BCD6D42CF8DYYZEML701CHMchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Kalyani, I was thinking something along this: A section on each competing architecture where we first provide a descripti= on of each architecture. A section on the list and set of features that 3GPP requires and must be su= pported. In the following sections we then make a deep dive into each architecture a= nd describe/analyse how different architectures would support each of the requested features. Going through the above exercise we can perhaps tabulate the outcome of the= investigation in a format like: Arch1 Arch-2 Arch-N Feature-1 Feature-2 Feature-N Considering pros and cons of each architecture against the request features= , at this point we should be ready to reply back to 3GPP with our recommend= ed architecture. We then continue the work, and go into more details and follow the same for= mat for different protocols supporting the recommended architecture and tab= ulate the outcome as Arch1.1 Arch1.2 Arch1.n Feature-1 Feature-2 Feature-N Taking ID-Location architecture as an example, LISP/ILSR, ILNP, ILA, etc. = will be Arch1.1, Arch1.2, Arch1.3, etc. Now, here is my question. Have we already decided to go with the recommenda= tion that ID-Location architecture should be the next generation of data pa= th? If everyone is on board with this, then your suggested outline fits the bil= l and we can start working on it right away. If the decision hasn't been ma= de then it would be perhaps a good idea to go one level up and talk about d= ifferent architectures first. Mind you that I don't know and am simply curi= ous to know what our starting point is. Arashmid From: Bogineni, Kalyani [mailto:[email protected]] Sent: 18 January 2018 10:21 To: Arashmid Akhavain <[email protected]>; Sri Gundavelli (sgund= ave) <[email protected]>; [email protected] Cc: AshwoodsmithPeter <[email protected]>; TongWen <tongwen@hua= wei.com>; Bogineni, Kalyani <[email protected]> Subject: RE: [DMM] white paper for optimized mobile user plane solutions fo= r 5G Arashmid: The individual sections are supposed to allow the proponents of the protoco= ls to show how the 5G architecture will be when their protocol is used with the focus on N9. The criteria section lists the= evaluation criteria from architectural perspective. Do you see a need for a different kind of format? Kalyani From: Arashmid Akhavain [mailto:[email protected]] Sent: Thursday, January 18, 2018 9:38 AM To: Sri Gundavelli (sgundave) <[email protected]<mailto:[email protected]= >>; Bogineni, Kalyani <[email protected]<mailto:Kalyani.= [email protected]>>; [email protected]<mailto:[email protected]> Cc: AshwoodsmithPeter <[email protected]<mailto:Peter.AshwoodSm= [email protected]>>; TongWen <[email protected]<mailto:[email protected]>> Subject: [E] RE: [DMM] white paper for optimized mobile user plane solution= s for 5G Hi Sri, Thank you for your reply and clarifications. I think Kalyani's work is extremely valuable, but we also need to set an st= rategy for our reply back to 3GPP. Currently most discussions are about ind= ividual protocols such as SRV6, LISP/ILSP, ILNP, ILA, etc. which are really= in one form or another a type of ID-Location approach. I believe we first= need to address 3GPP's request from the architecture point of view, before= we dive into implementation details. Is there any discussion around differ= ent competing network architectures? Not sure if you have seen a white paper titled "Evolving 5G Routing" by Doc= omo, Huawei and others. We also hosted a live webcast demo that shows two L= TE slices using ID-Location for data path and distribute ID-Location inform= ation to interested eNodeBs via public cloud pub/sub service. The result is= very promising and shows the capability of this architecture. I believe the combination of the white paper and the demo could perhaps ser= ve as a good starting point to get the architecture discussion going and th= at's where conference calls can come handy. I agree though let's start with= the mailing list and move to calls next. Best regards, Arashmid Akhavain From: Sri Gundavelli (sgundave) [mailto:[email protected]] Sent: 17 January 2018 17:53 To: Arashmid Akhavain <[email protected]<mailto:arashmid.akhavai= [email protected]>>; Bogineni, Kalyani <[email protected]<mai= lto:[email protected]>>; [email protected]<mailto:[email protected]= g> Subject: Re: [DMM] white paper for optimized mobile user plane solutions fo= r 5G Arashmid - We do have regular DMM working group meeting during the IETF we= ek. I guess, what you are asking for is a WG-chair scheduled conference cal= ls? DMM List may be very quite, but there have been regular conf calls betw= een authors of some of the WG documents. Authors of FPC host those calls re= gularly. For the new work item that Kalyani is proposing, we need to have s= ome discussions in the mailer and once the document is adopted as a WG docu= ment, we can certainly host some calls (author/chair scheduled) on a need b= asis. So, the first step is to post comments on the documents and trigger s= ome discussions. Sri From: dmm <[email protected]<mailto:[email protected]>> on behalf of = Arashmid Akhavain <[email protected]<mailto:arashmid.akhavain@hu= awei.com>> Date: Wednesday, January 17, 2018 at 2:16 PM To: "Bogineni, Kalyani" <[email protected]<mailto:Kalyan= [email protected]>>, "[email protected]<mailto:[email protected]>" <dmm@= ietf.org<mailto:[email protected]>> Subject: Re: [DMM] white paper for optimized mobile user plane solutions fo= r 5G Hi everyone, Online meetings on a regular basis can perhaps help moving things forward. Arashmid From: dmm [mailto:[email protected]] On Behalf Of Bogineni, Kalyani Sent: 17 January 2018 15:20 To: [email protected]<mailto:[email protected]> Subject: Re: [DMM] white paper for optimized mobile user plane solutions fo= r 5G Folks: Here is the draft with 3GPP architecture described as much as relevant to N= 9 interface. I have extracted some diagrams from 3GPP specs and will redo them in ASCII = after I get some feedback on whether to include them or not in this document. Kalyani From: Bogineni, Kalyani Sent: Wednesday, December 13, 2017 4:14 PM To: [email protected]<mailto:[email protected]> Cc: Bogineni, Kalyani <[email protected]<mailto:Kalyani.= [email protected]>> Subject: white paper for optimized mobile user plane solutions for 5G Folks: In response to the 3GPP CT4 study item on user plane protocols, we propose = that a white paper be developed that can compare the different IETF protocols. Attached is an = outline. Please let me know if you would like to contribute. Kalyani Bogineni Verizon --_000_D57109449177B54F8B9C093953AC5BCD6D42CF8DYYZEML701CHMchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal; font-family:"Calibri",sans-serif; color:windowtext;} span.EmailStyle18 {mso-style-type:personal; font-family:"Calibri",sans-serif; color:#1F497D;} span.EmailStyle19 {mso-style-type:personal; font-family:"Calibri",sans-serif; color:#1F497D;} span.EmailStyle20 {mso-style-type:personal; font-family:"Calibri",sans-serif; color:#1F497D;} span.EmailStyle21 {mso-style-type:personal; font-family:"Calibri",sans-serif; color:#1F497D;} span.EmailStyle22 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">Hi Kalyani,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">I was thinking something along this:<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">A section on each competing architecture where we first provide a desc= ription of each architecture.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">A section on the list and set of features that 3GPP requires and must = be supported.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">In the following sections we then make a deep dive into each architect= ure and describe/analyse how different architectures would support<o:p></o:= p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">each of the requested features. <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">Going through the above exercise we can perhaps tabulate the outcome o= f the investigation in a format like:<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:72.0pt;text-indent:36.0pt"><spa= n style=3D"font-family:"Courier New";color:#1F497D;mso-fareast-la= nguage:EN-US">Arch1 Arch-2 &= nbsp; Arch-N<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US">Feature-1<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US">Feature-2<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US">Feature-N<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">Considering pros and cons of each architecture against the request fea= tures, at this point we should be ready to reply back to 3GPP with our reco= mmended architecture.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">We then continue the work, and go into more details and follow the sam= e format for different protocols supporting the recommended architecture an= d tabulate the outcome as<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:72.0pt;text-indent:36.0pt"><spa= n style=3D"font-family:"Courier New";color:#1F497D;mso-fareast-la= nguage:EN-US">Arch1.1 Arch1= .2 Arch1.n<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US">Feature-1<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US">Feature-2<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US">Feature-N<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">Taking ID-Location architecture as an example, LISP/ILSR, ILNP, = ILA, etc. will be Arch1.1, Arch1.2, Arch1.3, etc.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">Now, here is my question. Have we already decided to go with the recom= mendation that ID-Location architecture should be the next generation of da= ta path?<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">If everyone is on board with this, then your suggested outline fits th= e bill and we can start working on it right away. If the decision hasn̵= 7;t been made then it would be perhaps a good idea to go one level up and talk about different architectures first. Mind= you that I don’t know and am simply curious to know what our startin= g point is. <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US">Arashmid<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New";c= olor:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN= -US"><o:p> </o:p></span></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang= =3D"EN-US"> Bogineni, Kalyani [mailto:[email protected]] <br> <b>Sent:</b> 18 January 2018 10:21<br> <b>To:</b> Arashmid Akhavain <[email protected]>; Sri Gund= avelli (sgundave) <[email protected]>; [email protected]<br> <b>Cc:</b> AshwoodsmithPeter <[email protected]>; TongWen= <[email protected]>; Bogineni, Kalyani <Kalyani.Bogineni@Verizon= Wireless.com><br> <b>Subject:</b> RE: [DMM] white paper for optimized mobile user plane solut= ions for 5G<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Arashmi= d:<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n= bsp;</o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">The ind= ividual sections are supposed to allow the proponents of the protocols to s= how how the 5G architecture will be when<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">their p= rotocol is used with the focus on N9. The criteria section lists the evalua= tion criteria from architectural perspective.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n= bsp;</o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Do you = see a need for a different kind of format?<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n= bsp;</o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Kalyani= <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n= bsp;</o:p></span></p> <div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm = 4.0pt"> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang= =3D"EN-US"> Arashmid Akhavain [<a href=3D"mailto:[email protected]= om">mailto:[email protected]</a>] <br> <b>Sent:</b> Thursday, January 18, 2018 9:38 AM<br> <b>To:</b> Sri Gundavelli (sgundave) <<a href=3D"mailto:[email protected]= om">[email protected]</a>>; Bogineni, Kalyani <<a href=3D"mailto:Kal= [email protected]">[email protected]</a>= >; <a href=3D"mailto:[email protected]">[email protected]</a><br> <b>Cc:</b> AshwoodsmithPeter <<a href=3D"mailto:Peter.AshwoodSmith@huawe= i.com">[email protected]</a>>; TongWen <<a href=3D"mailto= :[email protected]">[email protected]</a>><br> <b>Subject:</b> [E] RE: [DMM] white paper for optimized mobile user plane s= olutions for 5G<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Sri,<o:p></o:p></sp= an></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thank you for your rep= ly and clarifications. <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">I think Kalyani’= s work is extremely valuable, but we also need to set an strategy for our r= eply back to 3GPP. Currently most discussions are about individual protocol= s such as SRV6, LISP/ILSP, ILNP, ILA, etc. which are really in one form or another a type of ID-Location approach.&nb= sp; I believe we first need to address 3GPP’s request from the archit= ecture point of view, before we dive into implementation details. Is there = any discussion around different competing network architectures?<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa= n></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">Not sure if you have s= een a white paper titled “Evolving 5G Routing” by Docomo, Huawe= i and others. We also hosted a live webcast demo that shows two LTE slices = using ID-Location for data path and distribute ID-Location information to interested eNodeBs via public cloud pub/sub service. The re= sult is very promising and shows the capability of this architecture. <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa= n></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">I believe the combinat= ion of the white paper and the demo could perhaps serve as a good starting = point to get the architecture discussion going and that’s where confe= rence calls can come handy. I agree though let’s start with the mailing list and move to calls next.<o:p></o:p>= </span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa= n></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best regards,<o:p></o:= p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">Arashmid Akhavain<o:p>= </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa= n></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang= =3D"EN-US"> Sri Gundavelli (sgundave) [<a href=3D"mailto:[email protected]= ">mailto:[email protected]</a>] <br> <b>Sent:</b> 17 January 2018 17:53<br> <b>To:</b> Arashmid Akhavain <<a href=3D"mailto:arashmid.akhavain@huawei= .com">[email protected]</a>>; Bogineni, Kalyani <<a href= =3D"mailto:[email protected]">Kalyani.Bogineni@VerizonWi= reless.com</a>>; <a href=3D"mailto:[email protected]">[email protected]</a><br> <b>Subject:</b> Re: [DMM] white paper for optimized mobile user plane solut= ions for 5G<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Arashmi= d - We do have regular DMM working group meeting during the IETF week= . I guess, what you are asking for is a WG-chair scheduled conference calls= ? DMM List may be very quite, but there have been regular conf calls between authors of some of the WG documents. Autho= rs of FPC host those calls regularly. For the new work item that Kalyani is= proposing, we need to have some discussions in the mailer and once the doc= ument is adopted as a WG document, we can certainly host some calls (author/chair scheduled) on a need basis.= So, the first step is to post comments on the documents and trigger some d= iscussions.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n= bsp;</o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n= bsp;</o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Sri<o:p= ></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n= bsp;</o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n= bsp;</o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n= bsp;</o:p></span></p> </div> <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa= n style=3D"color:black">dmm <</span><a href=3D"mailto:[email protected]= rg">[email protected]</a><span style=3D"color:black">> on behalf of A= rashmid Akhavain <</span><a href=3D"mailto:[email protected]"= >[email protected]</a><span style=3D"color:black">><br> <b>Date: </b>Wednesday, January 17, 2018 at 2:16 PM<br> <b>To: </b>"Bogineni, Kalyani" <</span><a href=3D"mailto:Kalya= [email protected]">[email protected]</a><s= pan style=3D"color:black">>, "</span><a href=3D"mailto:[email protected]= ">[email protected]</a><span style=3D"color:black">" <</span><a href=3D"= mailto:[email protected]">[email protected]</a><span style=3D"color:black">><br> <b>Subject: </b>Re: [DMM] white paper for optimized mobile user plane solut= ions for 5G<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n= bsp;</o:p></span></p> </div> <div> <div> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi everyone,</span><sp= an style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">Online meetings on a r= egular basis can perhaps help moving things forward.</span><span style=3D"c= olor:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D"> </span><span sty= le=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D">Arashmid</span><span s= tyle=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D"> </span><span sty= le=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D"> </span><span sty= le=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"color:#1F497D"> </span><span sty= le=3D"color:black"><o:p></o:p></span></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:black">From:<= /span></b><span lang=3D"EN-US" style=3D"color:black"> dmm [</span><a href= =3D"mailto:[email protected]"><span lang=3D"EN-US">mailto:dmm-bounces@ie= tf.org</span></a><span lang=3D"EN-US" style=3D"color:black">] <b>On Behalf Of </b>Bogineni, Kalyani<br> <b>Sent:</b> 17 January 2018 15:20<br> <b>To:</b> </span><a href=3D"mailto:[email protected]"><span lang=3D"EN-US">dmm@= ietf.org</span></a><span lang=3D"EN-US" style=3D"color:black"><br> <b>Subject:</b> Re: [DMM] white paper for optimized mobile user plane solut= ions for 5G</span><span style=3D"color:black"><o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><span style=3D"color:black"> <o:p></o:p></span>= </p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Folks:<= /span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"> <= /span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Here is= the draft with 3GPP architecture described as much as relevant to N9 inter= face. </span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I have = extracted some diagrams from 3GPP specs and will redo them in ASCII after I= get</span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">some fe= edback on whether to include them or not in this document. </span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"> <= /span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Kalyani= </span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"> <= /span><span style=3D"color:black"><o:p></o:p></span></p> <div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm = 4.0pt"> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:black">From:<= /span></b><span lang=3D"EN-US" style=3D"color:black"> Bogineni, Kalyani <br> <b>Sent:</b> Wednesday, December 13, 2017 4:14 PM<br> <b>To:</b> </span><a href=3D"mailto:[email protected]"><span lang=3D"EN-US">dmm@= ietf.org</span></a><span lang=3D"EN-US" style=3D"color:black"><br> <b>Cc:</b> Bogineni, Kalyani <</span><a href=3D"mailto:Kalyani.Bogineni@= VerizonWireless.com"><span lang=3D"EN-US">Kalyani.Bogineni@VerizonWireless.= com</span></a><span lang=3D"EN-US" style=3D"color:black">><br> <b>Subject:</b> white paper for optimized mobile user plane solutions for 5= G</span><span style=3D"color:black"><o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black"> </s= pan><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Folks:</s= pan><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black"> </s= pan><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">In respon= se to the 3GPP CT4 study item on user plane protocols, we propose that a wh= ite paper</span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">be develo= ped that can compare the different IETF protocols. Attached is an outline. = Please let me </span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">know if y= ou would like to contribute. </span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black"> </s= pan><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Kalyani B= ogineni</span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Verizon</= span><span style=3D"color:black"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black"> </s= pan><span style=3D"color:black"><o:p></o:p></span></p> </div> </div> </div> </div> </div> </body> </html> --_000_D57109449177B54F8B9C093953AC5BCD6D42CF8DYYZEML701CHMchi_-- --===============5839805583157322893== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm --===============5839805583157322893==--