Re: draft-ietf-adslmib-xdsl-vop-02.txt
מנחם דודג' <[email protected]> Sun, 1 Sep 2013 09:29:44 +0300
| Newsgroups | gmane.ietf.adslmib |
|---|---|
| Message-ID | <CAJ2jOhWKh1y+1PPO192t7cODpYf-6QtiYoYQo5Lwaw1xt3QeDw@mail.gmail.com> |
--===============5906197622848780644== Content-Type: multipart/alternative; boundary=047d7b86f532e071fd04e54c940c --047d7b86f532e071fd04e54c940c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Thus far, I haven't seen any response on the mailing list. If anyone on the mailing list has any comments to make about the -02 draft, please do so promptly. Thank you kindly. Best Regards, Menachem 2013/8/4 =D7=9E=D7=A0=D7=97=D7=9D =D7=93=D7=95=D7=93=D7=92' <menachemdodge1= @gmail.com> > Hi, > > I'd like to thank the editors for the efforts in producing this draft of > the Vector of Profiles MIB. > > The editors have asked that the working group review the approach being > taken and I urge everyone on the mailing list to do so. > > Please provide your feedback on the mailing list. > > Thank you kindly, > > Best Regards > Menachem > > > 2013/8/2 Moti Morgenstern <[email protected]> > >> Hi,**** >> >> ** ** >> >> I just manually uploaded the draft document rev -02. I believe that the >> amount of text added justifies releasing a revision at this point, as th= e >> document already presents the main concepts (i.e., legacy+VoP configurat= ion >> models, skeleton of the VoP, the PSD Profile and its relationship to the >> mode specific extension, and more).**** >> >> ** ** >> >> It=E2=80=99s a good opportunity for you to discuss the approach, before = the >> editors continue with filling-in the content.**** >> >> ** ** >> >> The changes I performed, relative to rev -01:**** >> >> - Minor editorial:**** >> - Replaced all =E2=80=9Cvector of profiles=E2=80=9D with =E2=80=9C= Vector of Profiles=E2=80=9D**** >> - solved many (not all) warnings re excessive line lengths**** >> - Meaningful editorial:**** >> - Describes how not supporting >> xdsl2ScalarVopAttachmentMethodCapabilties means that the NE can on= ly be >> managed by the legacy management model (not VoP)**** >> - Revised the content of =E2=80=9Cprofiles=E2=80=9D section in the= description >> part, including its sub-sections, and reordered that section and t= he >> section about VoPs.**** >> - Body of the MIB**** >> - Added a comment in xdsl2VopLineVectorId. *Open Issue*: Need to >> discuss the basic role of xdsl2VopLineTable (and fallback function= ality) in >> context of the two attachment modes.**** >> - Removed from xdsl2VopVectorTable (and xdsl2VopVectorActualTable) >> all references to RA ratio, as those are embedded in the Data Rate= Profile. >> **** >> - xdsl2VopVectorActualTable is required only when using direct >> attachment mode. In indirect attachment mode the actual VoP being = used can >> (need to decide on that) be reported via a read-only object in >> xdsl2VopLineTable.**** >> - Reordered the existing objects in xdsl2VopVectorTable & >> xdsl2VopVectorActualTable to be aligned with WT-252i3, and added n= ew >> objects (new VoP profiles) per that document.**** >> - Added xdsl2VopDataRateProfilesTable and the description clause >> for all objects in xdsl2VopVectorTable & xdsl2VopVectorActualTable= that >> refer to it.**** >> - Added Xdsl2RtxModes TC and xdsl2VopLSpectrumProfilesTable (few >> objects originated from newest amendments to G.997.1 still missing= ) >> **** >> - Added xdsl2VopModeSpecProfilesTable and xdsl2VopModeSpecMapTable >> **** >> - Slightly revised Xdsl2PsdMaskDs & Xdsl2PsdMaskUs**** >> >> ** ** >> >> Regards,**** >> >> Moti Morgenstern**** >> >> This e-mail message is intended for the recipient only and contains >> information which is CONFIDENTIAL and which may be proprietary to ECI >> Telecom. If you have received this transmission in error, please inform = us >> by e-mail, phone or fax, and then delete the original and all copies >> thereof. >> > > --047d7b86f532e071fd04e54c940c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"rtl"><div dir=3D"ltr">Hi,</div><div dir=3D"ltr">=C2=A0</div><di= v dir=3D"ltr">Thus far, I haven't seen any response on the mailing list= .</div><div dir=3D"ltr">=C2=A0</div><div dir=3D"ltr">If anyone on the maili= ng list has any comments to make about the -02 draft, please do so promptly= .</div> <div dir=3D"ltr">=C2=A0</div><div dir=3D"ltr">Thank you kindly.</div><div d= ir=3D"ltr">=C2=A0</div><div dir=3D"ltr">Best Regards,</div><div dir=3D"ltr"= >Menachem</div></div><div class=3D"gmail_extra"><div dir=3D"ltr"><br><br><d= iv class=3D"gmail_quote"> 2013/8/4 =D7=9E=D7=A0=D7=97=D7=9D =D7=93=D7=95=D7=93=D7=92' <span dir= =3D"ltr"><<a href=3D"mailto:[email protected]" target=3D"_blank">= [email protected]</a>></span><br><blockquote class=3D"gmail_quote= " style=3D"margin:0 .8ex;border-left:1px #ccc solid;border-right:1px #ccc s= olid;padding-left:1ex;padding-right:1ex"> <div dir=3D"rtl"><div dir=3D"ltr">Hi, </div><div dir=3D"ltr">=C2=A0</div><d= iv dir=3D"ltr">I'd like to thank the editors for the efforts in produci= ng this draft of the Vector of Profiles MIB.</div><div dir=3D"ltr">=C2=A0</= div><div dir=3D"ltr"> The editors have asked that the working group review the approach being tak= en and I urge everyone on the mailing list to do so.</div><div dir=3D"ltr">= =C2=A0</div><div dir=3D"ltr">Please provide your feedback on the mailing li= st.</div> <div dir=3D"ltr">=C2=A0</div><div dir=3D"ltr">Thank you kindly,</div><div d= ir=3D"ltr">=C2=A0</div><div dir=3D"ltr">Best Regards</div><div dir=3D"ltr">= Menachem </div></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"= gmail_extra"><br><br> <div class=3D"gmail_quote"><div dir=3D"ltr"> 2013/8/2 Moti Morgenstern <span dir=3D"ltr"><<a href=3D"mailto:Moti.Morg= [email protected]" target=3D"_blank">[email protected]</a>>= </span></div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex= ;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style= :solid" class=3D"gmail_quote"> <div lang=3D"EN-US" vlink=3D"purple" link=3D"blue"> <div> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt">Hi,<u></u><u></u></s= pan></p> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt"><u></u>=C2=A0<u></u>= </span></p> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt">I just manually uplo= aded the draft document rev -02. I believe that the amount of text added ju= stifies releasing a revision at this point, as the document already presents the main concepts (i.e., legacy+VoP configuration models, skeleto= n of the VoP, the PSD Profile and its relationship to the mode specific ext= ension, and more).<u></u><u></u></span></p> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt"><u></u>=C2=A0<u></u>= </span></p> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt">It=E2=80=99s a good = opportunity for you to discuss the approach, before the editors continue wi= th filling-in the content.<u></u><u></u></span></p> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt"><u></u>=C2=A0<u></u>= </span></p> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt">The changes I perfor= med, relative to rev -01:<u></u><u></u></span></p> <ul style=3D"margin-top:0cm" type=3D"disc"> <li style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span style=3D"font-= family:"Calibri","sans-serif";font-size:11pt">Minor edi= torial:<u></u><u></u></span> <ul style=3D"margin-top:0cm" type=3D"circle"> <li style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span style=3D"font-= family:"Calibri","sans-serif";font-size:11pt">Replaced = all =E2=80=9Cvector of profiles=E2=80=9D with =E2=80=9CVector of Profiles= =E2=80=9D<u></u><u></u></span></li> <li style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span style=3D"font-= family:"Calibri","sans-serif";font-size:11pt">solved ma= ny (not all) warnings re excessive line lengths<u></u><u></u></span></li></= ul> </li><li style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span style=3D"= font-family:"Calibri","sans-serif";font-size:11pt">Mean= ingful editorial:<u></u><u></u></span> <ul style=3D"margin-top:0cm" type=3D"circle"> <li style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span style=3D"font-= family:"Calibri","sans-serif";font-size:11pt">Describes= how not supporting xdsl2ScalarVopAttachmentMethodCapabilties means that th= e NE can only be managed by the legacy management model (not VoP)<u></u><u></u></span></li><li style=3D"color:rgb= (31,73,125)" class=3D"MsoNormal"><span style=3D"font-family:"Calibri&q= uot;,"sans-serif";font-size:11pt">Revised the content of =E2=80= =9Cprofiles=E2=80=9D section in the description part, including its sub-sec= tions, and reordered that section and the section about VoPs.<u></u><u></u></span></li></ul> </li><li style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span style=3D"= font-family:"Calibri","sans-serif";font-size:11pt">Body= of the MIB<u></u><u></u></span> <ul style=3D"margin-top:0cm" type=3D"circle"> <li style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span style=3D"font-= family:"Calibri","sans-serif";font-size:11pt">Added a c= omment in xdsl2VopLineVectorId. <u>Open Issue</u>: Need to discuss the basic role of xdsl2VopLineTable (and= fallback functionality) in context of the two attachment modes.<u></u><u><= /u></span></li><li style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span= style=3D"font-family:"Calibri","sans-serif";font-size:= 11pt">Removed from xdsl2VopVectorTable (and xdsl2VopVectorActualTable) all = references to RA ratio, as those are embedded in the Data Rate Profile.<u></u><u></u></span></li><li style=3D"color:rgb(31,73,125)" = class=3D"MsoNormal"><span style=3D"font-family:"Calibri","sa= ns-serif";font-size:11pt">xdsl2VopVectorActualTable is required only w= hen using direct attachment mode. In indirect attachment mode the actual Vo= P being used can (need to decide on that) be reported via a read-only object in xd= sl2VopLineTable.<u></u><u></u></span></li><li style=3D"color:rgb(31,73,125)= " class=3D"MsoNormal"><span style=3D"font-family:"Calibri","= sans-serif";font-size:11pt">Reordered the existing objects in xdsl2Vop= VectorTable & xdsl2VopVectorActualTable to be aligned with WT-252i3, an= d added new objects (new VoP profiles) per that document.<u></u><u></u></span></li><li= style=3D"color:rgb(31,73,125)" class=3D"MsoNormal"><span style=3D"font-fam= ily:"Calibri","sans-serif";font-size:11pt">Added xdsl2V= opDataRateProfilesTable and the description clause for all objects in xdsl2= VopVectorTable & xdsl2VopVectorActualTable that refer to it.<u></u><u></u></span></li><li style=3D"color:rgb(31,73,12= 5)" class=3D"MsoNormal"><span style=3D"font-family:"Calibri",&quo= t;sans-serif";font-size:11pt">Added Xdsl2RtxModes TC=C2=A0 and=C2=A0 x= dsl2VopLSpectrumProfilesTable (few objects originated from newest amendment= s to G.997.1 still missing)<u></u><u></u></span></li><li style=3D"color:rgb(31,73,125)" class= =3D"MsoNormal"><span style=3D"font-family:"Calibri","sans-se= rif";font-size:11pt">Added xdsl2VopModeSpecProfilesTable and xdsl2VopM= odeSpecMapTable <u></u><u></u></span></li><li style=3D"color:rgb(31,73,125)" class=3D"MsoNo= rmal"><span style=3D"font-family:"Calibri","sans-serif"= ;font-size:11pt">Slightly revised Xdsl2PsdMaskDs & Xdsl2PsdMaskUs<u></u= ><u></u></span></li> </ul> </li></ul> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt"><u></u>=C2=A0<u></u>= </span></p> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt">Regards,<u></u><u></= u></span></p> <p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo= t;Calibri","sans-serif";font-size:11pt">Moti Morgenstern<u><= /u><u></u></span></p> </div> <p> This e-mail message is intended for the recipient only and contains informa= tion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If = you have received this transmission in error, please inform us by e-mail, p= hone or fax, and then delete the original and all copies thereof. </p> </div> </blockquote></div><br></div> </div></div></blockquote></div></div></div> --047d7b86f532e071fd04e54c940c-- --===============5906197622848780644== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Adslmib mailing list [email protected] https://www.ietf.org/mailman/listinfo/adslmib --===============5906197622848780644==--