[DMM] Review of draft-liebsch-dmm-mts-04
CARLOS JESUS BERNARDOS CANO <[email protected]> Wed, 5 Nov 2025 16:42:11 -0500
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <CALypLp_GmqTQun97_Jgwjy+EF4BJbXj9io2PuU2RsTGisZ9xsg__36061.6269799479$1762378993$gmane$org@mail.gmail.com> |
--===============5331590082118963986== Content-Type: multipart/alternative; boundary="000000000000274d210642dfd3ce" --000000000000274d210642dfd3ce Content-Type: text/plain; charset="UTF-8" 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 most relevant ones here as well. - 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. - 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 and not other IGP protocols? - Figure 10: C_rtg is depicted, but I think this is not explained in the text. 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/ --000000000000274d210642dfd3ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Dear WG and document authors,</div><div><br></div><di= v>I've reviewed=C2=A0draft-liebsch-dmm-mts-04 (and shared my handwritte= n comments with Marco offline). For transparency and completeness, I'm = sharing the most relevant ones here as well.</div><div><br></div><div>- Ove= rall I think the document is very useful and well written. I find though th= at sometimes it's a bit hard to follow and additional figures would hel= p.</div><div><br></div><div>- Figure 1 is too far from the text that makes = reference to it.</div><div><br></div><div>- MCN term in page 4 should be ex= panded.</div><div><br></div><div>- I'd add a figure in Section 4.5.</di= v><div><br></div><div>- In section 6.2, U_mcs and D_mts are first introduce= d. I think they should be explained there.</div><div><br></div><div>- In se= ction 6.3, out of my curiosity, why is RIP mentioned as an example and not = other IGP protocols?</div><div><br></div><div>- Figure 10: C_rtg is depicte= d, but I think this is not explained in the text.</div><div><br></div><div>= Thanks,</div><div><br></div><div>Carlos</div><div><br></div><span class=3D"= gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signa= ture" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">CARLOS J. BERNARD= OS=C2=A0<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<div><div><span= style=3D"color:rgb(34,34,34)">RTS/CTS podcast:=C2=A0</span><a href=3D"http= s://castopod.cjbc.eu/@RTSCTS" target=3D"_blank">https://castopod.cjbc.eu/@R= TSCTS</a><br></div><div>YouTube channel:=C2=A0<a href=3D"https://www.youtub= e.com/CacharREDando/" target=3D"_blank">https://www.youtube.com/CacharREDan= do/</a></div></div></div></div></div> --000000000000274d210642dfd3ce-- --===============5331590082118963986== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk bW0tbGVhdmVAaWV0Zi5vcmcK --===============5331590082118963986==--