[DMM] Re: Review of draft-liebsch-dmm-mts-04
Tianji Jiang <[email protected]> Tue, 11 Nov 2025 19:00:24 +0000
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <MN2PR02MB6863C8B6C88B148C028CE02EF9CFA@MN2PR02MB6863.namprd02.prod.outlook.com> |
--===============0959360260711201285== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_MN2PR02MB6863C8B6C88B148C028CE02EF9CFAMN2PR02MB6863namp_" --_000_MN2PR02MB6863C8B6C88B148C028CE02EF9CFAMN2PR02MB6863namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Carlos: Thank you for your valuable reviews and recommendations. Apart from what Marco has replied below, we will also address your comment = on =91C_rtg=92 in a new revision. BR, -Tianji From: Marco Liebsch <[email protected]> Date: Monday, November 10, 2025 at 8:46 AM To: CARLOS JESUS BERNARDOS CANO <[email protected]>, dmm <[email protected]> Subject: [DMM] Re: Review of draft-liebsch-dmm-mts-04 Many thanks for your comments and recommendations, Carlos. Agree with your comments and we will implement them in the next revision. Sec. 6.2 uses labels on control- user/data-plane interfaces for ease in des= cribing the operational part and we do not touch but rely on them. But you are right in that we should better introduce them. RIP has been mentioned in Sec. 6.3 as one example as alternative due to its= simplicity compared to more heavy weight protocols. Others apply, of cours= e, too. However, use of the specified API allows easy extensions in terms of needed= semantics per the info model, which would need to be supported by alternat= ive use of routing protocols on that reference point, too. marco From: CARLOS JESUS BERNARDOS CANO <[email protected]> Sent: Mittwoch, 5. November 2025 22:42 To: dmm <[email protected]> Subject: [DMM] Review of draft-liebsch-dmm-mts-04 Dear WG and document authors, I've reviewed draft-liebsch-dmm-mts-04 (and shared my handwritten comments = with Marco offline). For transparency and completeness, I'm sharing the mos= t relevant ones here as well. - Overall I think the document is very useful and well written. I find thou= gh that sometimes it's a bit hard to follow and additional figures would he= lp. - Figure 1 is too far from the text that makes reference to it. - MCN term in page 4 should be expanded. - I'd add a figure in Section 4.5. - In section 6.2, U_mcs and D_mts are first introduced. I think they should= be explained there. - In section 6.3, out of my curiosity, why is RIP mentioned as an example a= nd not other IGP protocols? - Figure 10: C_rtg is depicted, but I think this is not explained in the te= xt. Thanks, Carlos -- CARLOS J. BERNARDOS https://www.it.uc3m.es/cjbc/ Universidad Carlos III de Madrid RTS/CTS podcast: https://castopod.cjbc.eu/@RTSCTS YouTube channel: https://www.youtube.com/CacharREDando/ --_000_MN2PR02MB6863C8B6C88B148C028CE02EF9CFAMN2PR02MB6863namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc= hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of= fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> <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:DengXian; panose-1:2 1 6 0 3 1 1 1 1 1;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Aptos; panose-1:2 11 6 4 2 2 2 2 2 4;} @font-face {font-family:"Times New Roman \(Body CS\)"; panose-1:2 2 6 3 5 4 5 2 3 4;} @font-face {font-family:"\@DengXian"; panose-1:2 1 6 0 3 1 1 1 1 1;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:12.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} span.gmailsignatureprefix {mso-style-name:gmailsignatureprefix;} span.EmailStyle20 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext; font-weight:normal; font-style:normal;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea= k-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Carlos:<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Thank you for your valuable reviews and recommendations.<o:p></o:p><= /span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Apart from what Marco has replied below, we will also address your c= omment on =91C_rtg=92 in a new revision.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">BR,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">-Tianji<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span lang=3D"DE" style=3D"font-family:"Cali= bri",sans-serif;color:black">From: </span></b><span lang=3D"DE" style=3D"font-family:"Calibri",sans-= serif;color:black">Marco Liebsch <[email protected]= .org><br> <b>Date: </b>Monday, November 10, 2025 at 8:46 AM<br> <b>To: </b>CARLOS JESUS BERNARDOS CANO <[email protected]>, dmm <dmm= @ietf.org><br> <b>Subject: </b>[DMM] Re: Review of draft-liebsch-dmm-mts-04<o:p></o:p></sp= an></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"><o:p> </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"EN-GB">Many thanks for your comments a= nd recommendations, Carlos.</span><span lang=3D"DE"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB"> </span><span lang=3D"DE">= <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB">Agree with your comments and we= will implement them in the next revision.</span><span lang=3D"DE"><o:p></o= :p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB"> </span><span lang=3D"DE">= <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB">Sec. 6.2 uses labels on control= - user/data-plane interfaces for ease in describing the operational part an= d we do not touch but<br> rely on them. But you are right in that we should better introduce them.</s= pan><span lang=3D"DE"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB"> </span><span lang=3D"DE">= <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB">RIP has been mentioned in Sec. = 6.3 as one example as alternative due to its simplicity compared to more he= avy weight protocols. Others apply, of course, too.</span><span lang=3D"DE"= ><o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB">However, use of the specified A= PI allows easy extensions in terms of needed semantics per the info model, = which would need to be supported by alternative use of routing protocols<br= > on that reference point, too.</span><span lang=3D"DE"><o:p></o:p></span></p= > <p class=3D"MsoNormal"><span lang=3D"EN-GB"> </span><span lang=3D"DE">= <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB">marco</span><span lang=3D"DE"><= o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB"> </span><span lang=3D"DE">= <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB"> </span><span lang=3D"DE">= <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB"> </span><span lang=3D"DE">= <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-GB"> </span><span lang=3D"DE">= <o:p></o:p></span></p> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:"= ;Calibri",sans-serif">From:</span></b><span style=3D"font-size:11.0pt;= font-family:"Calibri",sans-serif"> CARLOS JESUS BERNARDOS CANO &l= t;[email protected]> <br> <b>Sent:</b> Mittwoch, 5. November 2025 22:42<br> <b>To:</b> dmm <[email protected]><br> <b>Subject:</b> [DMM] Review of draft-liebsch-dmm-mts-04</span><span lang= =3D"DE"><o:p></o:p></span></p> </div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> <div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">Dear WG and document authors,<o:p>= </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">I've reviewed draft-liebsch-d= mm-mts-04 (and shared my handwritten comments with Marco offline). For tran= sparency and completeness, I'm sharing the most relevant ones here as well.= <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">- Overall I think the document is = very useful and well written. I find though that sometimes it's a bit hard = to follow and additional figures would help.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">- Figure 1 is too far from the tex= t that makes reference to it.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">- MCN term in page 4 should be exp= anded.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">- I'd add a figure in Section 4.5.= <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">- In section 6.2, U_mcs and D_mts = are first introduced. I think they should be explained there.<o:p></o:p></s= pan></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">- In section 6.3, out of my curios= ity, why is RIP mentioned as an example and not other IGP protocols?<o:p></= o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">- Figure 10: C_rtg is depicted, bu= t I think this is not explained in the text.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">Thanks,<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">Carlos<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE"> <o:p></o:p></span></p> </div> <p class=3D"MsoNormal"><span class=3D"gmailsignatureprefix"><span lang=3D"D= E">-- </span> </span><span lang=3D"DE"><o:p></o:p></span></p> <div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">CARLOS J. BERNARDOS <a href= =3D"https://www.it.uc3m.es/cjbc/" target=3D"_blank">https://www.it.uc3m.es/= cjbc/</a><br> Universidad Carlos III de Madrid<o:p></o:p></span></p> <div> <div> <p class=3D"MsoNormal"><span lang=3D"DE" style=3D"color:#222222">RTS/CTS po= dcast: </span><span lang=3D"DE"><a href=3D"https://castopod.cjbc.eu/@R= TSCTS" target=3D"_blank">https://castopod.cjbc.eu/@RTSCTS</a><o:p></o:p></s= pan></p> </div> <div> <p class=3D"MsoNormal"><span lang=3D"DE">YouTube channel: <a href=3D"h= ttps://www.youtube.com/CacharREDando/" target=3D"_blank">https://www.youtub= e.com/CacharREDando/</a><o:p></o:p></span></p> </div> </div> </div> </div> </div> </div> </div> </body> </html> --_000_MN2PR02MB6863C8B6C88B148C028CE02EF9CFAMN2PR02MB6863namp_-- --===============0959360260711201285== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk bW0tbGVhdmVAaWV0Zi5vcmcK --===============0959360260711201285==--