[DMM] Re: draft-ietf-dmm-tn-aware-mobility-22 and draft-jlu- dmm-udp-tunnel-acaas-01
Satoru Matsushima <[email protected]> Thu, 16 Oct 2025 18:28:21 +0900
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <CAFwJXX76k_n1VUNbs4dD+9__-27gjAAOkfJ9eRmnPMEva=8qLg__19991.0280456365$1760616339$gmane$org@mail.gmail.com> |
--===============2787459318019347587== Content-Type: multipart/alternative; boundary="00000000000011f9c00641456e9f" --00000000000011f9c00641456e9f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you John for updating the draft. It looks all comments were addressed. I will move forward this draft to WG last call shortly. cheers, --satoru On Tue, Oct 7, 2025 at 12:53=E2=80=AFAM Kaippallimalil John < [email protected]> wrote: > Thank you, Med, Mahesh, Satoru and all for your feedback and reviews. > > The changes requested by Med in the reviews of both the drafts are > implemented now. > The two draft approach that was agreed as the way forward in the last dmm > meeting makes sense to me as an author. > The example in [draft-jlu-dmm-udp-tunnel-acaas-01] adapted from A.7 of > [I-D.ietf-opsawg-teas-attachment-circuit] adds value, as it was not there > with the old/combined dmm draft. > But I would be OK to proceed as the chairs/ADs advise. > > Pointers to the submission diffs: > [draft-ietf-dmm-tn-aware-mobility-22]: > > https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dmm-tn-aware-mobil= ity-22 > > [draft-jlu-dmm-udp-tunnel-acaas-01]: > https://author-tools.ietf.org/iddiff?url2=3Ddraft-jlu-dmm-udp-tunnel-acaa= s-01 > > Regards, > John > > > > -----Original Message----- > > From: Satoru Matsushima <[email protected]> > > Sent: Saturday, September 27, 2025 9:42 PM > > To: Mahesh Jethanandani <[email protected]> > > Cc: [email protected]; opsawg <[email protected]>; > > [email protected] > > Subject: [DMM] Re: [OPSAWG]Re: (request to review) FW: New Versions - > > draft-ietf-dmm-tn-aware-mobility-21 and draft-jlu-dmm-udp-tunnel-acaas- > > 00 > > > > Thanks Mahesh-san, please discuss with your co-AD and in the ops area > > whether an informational draft or RFC carries YANG modules with ietf > prefix or > > not. > > > > I think that a consistent view from OPSADs and the ops area for that > helps to > > avoid confusions, not only for dmm, but also all other WGs in the IETF. > > > > cheers, > > --satoru > > > > > On Sep 18, 2025, at 19:07, Mahesh Jethanandani > > <[email protected]> wrote: > > > > > > =EF=BB=BFHi Saturn-san, > > > > > > > > >> > > >> On Sep 18, 2025, at 11:16=E2=80=AFAM, [email protected] w= rote: > > >> > > >> I would add a background on this sprit. During the last meeting an > OPSAD > > who gave us his feedback, like it is ok to include the YANG module in > the INFO > > draft. However another AD gave us opposite feedback. So the chairs and > the > > authors decided to sprit the draft, which looks more likely and safer > way. > > > > > > My take (as one of the OPS AD) is that it is ok for an informational > draft to > > carry a YANG module. While it might be safe, if the document is being > split just > > for that reason, it is unnecessary overhead. We should be making it > easier, not > > harder to publish documents especially those that contain YANG modules. > > > > > > Just my 2 cents (1 if you count inflation =F0=9F=98=80) > > > > > > Mahesh Jethanandani > > > [email protected] > > > _______________________________________________ > > > dmm mailing list -- [email protected] > > > To unsubscribe send an email to [email protected] > > > > _______________________________________________ > > dmm mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > --00000000000011f9c00641456e9f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Thank=C2=A0you John for updating the draft. It looks=C2=A0= all comments were addressed. I will move forward this draft to WG last call= shortly.<div><br></div><div>cheers,</div><div>--satoru</div><div><br></div= ></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr= " class=3D"gmail_attr">On Tue, Oct 7, 2025 at 12:53=E2=80=AFAM Kaippallimal= il John <<a href=3D"mailto:[email protected]">john.kaipp= [email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_= quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,= 204);padding-left:1ex">Thank you, Med, Mahesh, Satoru and all for your feed= back and reviews.<br> <br> The changes requested by Med in the reviews of both the drafts are implemen= ted now.<br> The two draft approach that was agreed as the way forward in the last dmm m= eeting makes sense to me as an author.<br> The example in [draft-jlu-dmm-udp-tunnel-acaas-01] adapted from A.7 of [I-D= .ietf-opsawg-teas-attachment-circuit] adds value, as it was not there with = the old/combined dmm draft.<br> But I would be OK to proceed as the chairs/ADs advise.<br> <br> Pointers to the submission diffs:<br> [draft-ietf-dmm-tn-aware-mobility-22]:<br> <a href=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-dmm-tn-aw= are-mobility-22" rel=3D"noreferrer" target=3D"_blank">https://author-tools.= ietf.org/iddiff?url2=3Ddraft-ietf-dmm-tn-aware-mobility-22</a><br> <br> [draft-jlu-dmm-udp-tunnel-acaas-01]:<br> <a href=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-jlu-dmm-udp-tu= nnel-acaas-01" rel=3D"noreferrer" target=3D"_blank">https://author-tools.ie= tf.org/iddiff?url2=3Ddraft-jlu-dmm-udp-tunnel-acaas-01</a><br> <br> Regards,<br> John<br> <br> <br> > -----Original Message-----<br> > From: Satoru Matsushima <<a href=3D"mailto:satoru.matsushima@gmail.= com" target=3D"_blank">[email protected]</a>><br> > Sent: Saturday, September 27, 2025 9:42 PM<br> > To: Mahesh Jethanandani <<a href=3D"mailto:[email protected]"= target=3D"_blank">[email protected]</a>><br> > Cc: <a href=3D"mailto:[email protected]" target=3D"_blank">= [email protected]</a>; opsawg <<a href=3D"mailto:opsawg@ietf.= org" target=3D"_blank">[email protected]</a>>;<br> > <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><br> > Subject: [DMM] Re: [OPSAWG]Re: (request to review) FW: New Versions -<= br> > draft-ietf-dmm-tn-aware-mobility-21 and draft-jlu-dmm-udp-tunnel-acaas= -<br> > 00<br> ><br> > Thanks Mahesh-san, please discuss with your co-AD and in the ops area<= br> > whether an informational draft or RFC carries YANG modules with ietf p= refix or<br> > not.<br> ><br> > I think that a consistent view from OPSADs and the ops area for that h= elps to<br> > avoid confusions, not only for dmm, but also all other WGs in the IETF= .<br> ><br> > cheers,<br> > --satoru<br> ><br> > > On Sep 18, 2025, at 19:07, Mahesh Jethanandani<br> > <<a href=3D"mailto:[email protected]" target=3D"_blank">mjeth= [email protected]</a>> wrote:<br> > ><br> > > =EF=BB=BFHi Saturn-san,<br> > ><br> > ><br> > >><br> > >> On Sep 18, 2025, at 11:16=E2=80=AFAM, <a href=3D"mailto:moham= [email protected]" target=3D"_blank">[email protected]</a>= wrote:<br> > >><br> > >> I would add a background on this sprit. During the last meeti= ng an OPSAD<br> > who gave us his feedback, like it is ok to include the YANG module in = the INFO<br> > draft. However another AD gave us opposite feedback. So the chairs and= the<br> > authors decided to sprit the draft, which looks more likely and safer = way.<br> > ><br> > > My take (as one of the OPS AD) is that it is ok for an informatio= nal draft to<br> > carry a YANG module. While it might be safe, if the document is being = split just<br> > for that reason, it is unnecessary overhead. We should be making it ea= sier, not<br> > harder to publish documents especially those that contain YANG modules= .<br> > ><br> > > Just my 2 cents (1 if you count inflation =F0=9F=98=80)<br> > ><br> > > Mahesh Jethanandani<br> > > <a href=3D"mailto:[email protected]" target=3D"_blank">mjet= [email protected]</a><br> > > _______________________________________________<br> > > dmm mailing list -- <a href=3D"mailto:[email protected]" target=3D"_bl= ank">[email protected]</a><br> > > To unsubscribe send an email to <a href=3D"mailto:dmm-leave@ietf.= org" target=3D"_blank">[email protected]</a><br> ><br> > _______________________________________________<br> > dmm mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank">= [email protected]</a><br> > To unsubscribe send an email to <a href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a><br> </blockquote></div> --00000000000011f9c00641456e9f-- --===============2787459318019347587== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk bW0tbGVhdmVAaWV0Zi5vcmcK --===============2787459318019347587==--