Re: draft-ietf-adslmib-xdsl-vop-02.txt
מנחם דודג' <[email protected]> Sun, 4 Aug 2013 12:35:54 +0300
| Newsgroups | gmane.ietf.adslmib |
|---|---|
| Message-ID | <CAJ2jOhUTA8hLFRx4XM-BBDgMMYvyvADvpO2M3=n7mOaMRtshXg@mail.gmail.com> |
--===============0670974679805051028== Content-Type: multipart/alternative; boundary=047d7bd6b88c1d7b1d04e31beb5d --047d7bd6b88c1d7b1d04e31beb5d Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 the > document already presents the main concepts (i.e., legacy+VoP configurati= on > models, skeleton of the VoP, the PSD Profile and its relationship to the > mode specific extension, and more).**** > > ** ** > > It=92s 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 =93vector of profiles=94 with =93Vector of Profiles= =94**** > - solved many (not all) warnings re excessive line lengths**** > - Meaningful editorial:**** > - Describes how not supporting > xdsl2ScalarVopAttachmentMethodCapabilties means that the NE can onl= y be > managed by the legacy management model (not VoP)**** > - Revised the content of =93profiles=94 section in the description > part, including its sub-sections, and reordered that section and th= e > section about VoPs.**** > - Body of the MIB**** > - Added a comment in xdsl2VopLineVectorId. *Open Issue*: Need to > discuss the basic role of xdsl2VopLineTable (and fallback functiona= lity) 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 u= sed 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 ne= w > 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 u= s > by e-mail, phone or fax, and then delete the original and all copies > thereof. > --047d7bd6b88c1d7b1d04e31beb5d Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable <div dir=3D"rtl"><div dir=3D"ltr">Hi, </div><div dir=3D"ltr">=A0</div><div = dir=3D"ltr">I'd like to thank the editors for the efforts in producing = this draft of the Vector of Profiles MIB.</div><div dir=3D"ltr">=A0</div><d= iv 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">= =A0</div><div dir=3D"ltr">Please provide your feedback on the mailing list.= </div> <div dir=3D"ltr">=A0</div><div dir=3D"ltr">Thank you kindly,</div><div dir= =3D"ltr">=A0</div><div dir=3D"ltr">Best Regards</div><div dir=3D"ltr">Menac= hem </div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quot= e"><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 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b= order-left:1px #ccc solid;padding-left:1ex"> <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>=A0<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">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>=A0<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">It=92s a good opport= unity for you to discuss the approach, before the editors continue with fil= ling-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>=A0<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">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 =93vector of profiles=94 with =93Vector of Profiles=94<u></u><u></u></s= pan></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 =93profi= les=94 section in the description part, including its sub-sections, and reo= rdered 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=A0 and=A0 xdsl2Vo= pLSpectrumProfilesTable (few objects originated from newest amendments 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>=A0<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">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> --047d7bd6b88c1d7b1d04e31beb5d-- --===============0670974679805051028== 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 --===============0670974679805051028==--