Re: Call for adoption of draft-matsushima-spring-dmm-srv6-mobile-uplane-03 as DMM WG document
Charlie Perkins <[email protected]> Mon, 27 Nov 2017 14:06:38 -0800
| Newsgroups | gmane.ietf.mip6 |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============6297835836702201594== Content-Type: multipart/alternative; boundary="------------3275F33E81B8E22FFEC5B085" Content-Language: en-US This is a multi-part message in MIME format. --------------3275F33E81B8E22FFEC5B085 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Hello folks, The draft represents interesting work and I support adoption as a WG work item. However, I also agree with Sri's assessment below. I was co-author of source-routing proposals for both Mobile IPv4 and Mobile IPv6 that had many nice properties -- including minimal impact on the existing routing infrastructure. There were similar proposals from several other authors. All of them were soundly rejected. So, it would be a good idea to find out what has changed during the last 15 years to make source routing "better" than it used to be. Regards, Charlie P. On 11/14/2017 4:20 PM, Sri Gundavelli (sgundave) wrote: > Please also note that the document is just a starting point and > requires significant amount of community efforts and participation > before it can become a standard. The document does not address most of > the issues, but the proposal is promising enough and so would like to > take it up right away. Please comment. > > Dapping & Sri > > > From: dmm <[email protected] <mailto:[email protected]>> on > behalf of Sri Gundavelli <[email protected] <mailto:[email protected]>> > Date: Tuesday, November 14, 2017 at 4:02 PM > To: "[email protected] <mailto:[email protected]>" <[email protected] > <mailto:[email protected]>> > Subject: [DMM] Call for adoption of > draft-matsushima-spring-dmm-srv6-mobile-uplane-03 as DMM WG document > > Folks: > > The following message commences a two week call for opinions on the > adoption of draft-matsushima-spring-dmm-srv6-mobile-uplane-03 as a DMM > Working document. > > --- > The DMM working group is considering adopting the draft, > "draft-matsushima-spring-dmm-srv6-mobile-uplane-03 as a working group > document. The chairs have polled the room for opinions during IETF100, > and it was determined that there is good support for taking up this > work. The chairs would like to confirm the same in the mailing list. > Please provide your feedback. > > Document Link: > https://www.ietf.org/id/draft-matsushima-spring-dmm-srv6-mobile-uplane-03.txt > > Slides: > https://datatracker.ietf.org/meeting/100/materials/slides-100-dmm-srv6-for-mobile-user-plane/ > > Background: > https://datatracker.ietf.org/meeting/100/materials/slides-100-dmm-mobile-data-plane-evolution-motivation-goals/ > --- > > Regards > Dapping & Sri > > > > _______________________________________________ > dmm mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmm --------------3275F33E81B8E22FFEC5B085 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Hello folks,</p> <p>The draft represents interesting work and I support adoption as a WG work item.</p> <p>However, I also agree with Sri's assessment below.</p> <p>I was co-author of source-routing proposals for both Mobile IPv4 and Mobile IPv6 that had many nice properties -- including minimal impact on the existing routing infrastructure. There were similar proposals from several other authors.</p> <p>All of them were soundly rejected. So, it would be a good idea to find out what has changed during the last 15 years to make source routing "better" than it used to be.</p> <p>Regards,<br> Charlie P.<br> </p> <br> <div class="moz-cite-prefix">On 11/14/2017 4:20 PM, Sri Gundavelli (sgundave) wrote:<br> </div> <blockquote type="cite" cite="mid:D630C6ED.295E6B%[email protected]"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <div>Please also note that the document is just a starting point and requires significant amount of community efforts and participation before it can become a standard. The document does not address most of the issues, but the proposal is promising enough and so would like to take it up right away. Please comment.</div> <div><br> </div> <div>Dapping & Sri</div> <div><br> </div> <div> </div> <div><br> </div> <span id="OLK_SRC_BODY_SECTION"> <div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"> <span style="font-weight:bold">From: </span>dmm <<a href="mailto:[email protected]" moz-do-not-send="true">[email protected]</a>> on behalf of Sri Gundavelli <<a href="mailto:[email protected]" moz-do-not-send="true">[email protected]</a>><br> <span style="font-weight:bold">Date: </span>Tuesday, November 14, 2017 at 4:02 PM<br> <span style="font-weight:bold">To: </span>"<a href="mailto:[email protected]" moz-do-not-send="true">[email protected]</a>" <<a href="mailto:[email protected]" moz-do-not-send="true">[email protected]</a>><br> <span style="font-weight:bold">Subject: </span>[DMM] Call for adoption of draft-matsushima-spring-dmm-srv6-mobile-uplane-03 as DMM WG document<br> </div> <div><br> </div> <div> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"> <div>Folks:</div> <div><br> </div> <div> <div>The following message commences a two week call for opinions on the adoption of draft-matsushima-spring-dmm-srv6-mobile-uplane-03 as a DMM Working document. </div> </div> <div><br> </div> <div>---</div> <div>The DMM working group is considering adopting the draft, "draft-matsushima-spring-dmm-srv6-mobile-uplane-03 as a working group document. The chairs have polled the room for opinions during IETF100, and it was determined that there is good support for taking up this work. The chairs would like to confirm the same in the mailing list. Please provide your feedback.</div> <div> </div> <div><br> </div> <div> <div>Document Link:</div> <div><a href="https://www.ietf.org/id/draft-matsushima-spring-dmm-srv6-mobile-uplane-03.txt" moz-do-not-send="true">https://www.ietf.org/id/draft-matsushima-spring-dmm-srv6-mobile-uplane-03.txt</a></div> </div> <div><br> </div> <div>Slides:</div> <div><a href="https://datatracker.ietf.org/meeting/100/materials/slides-100-dmm-srv6-for-mobile-user-plane" moz-do-not-send="true">https://datatracker.ietf.org/meeting/100/materials/slides-100-dmm-srv6-for-mobile-user-plane</a>/</div> <div><br> </div> <div>Background:</div> <div><a href="https://datatracker.ietf.org/meeting/100/materials/slides-100-dmm-mobile-data-plane-evolution-motivation-goals" moz-do-not-send="true">https://datatracker.ietf.org/meeting/100/materials/slides-100-dmm-mobile-data-plane-evolution-motivation-goals</a>/</div> <div>---</div> <div><br> </div> <div>Regards</div> <div>Dapping & Sri</div> <div><br> </div> </div> </div> </span> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ dmm mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dmm">https://www.ietf.org/mailman/listinfo/dmm</a> </pre> </blockquote> <br> </body> </html> --------------3275F33E81B8E22FFEC5B085-- --===============6297835836702201594== 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 --===============6297835836702201594==--