Re: RE: [MIB-DOCTORS] Mandatory Requirement forconfigurationby SNMP
Jon Saperia <[email protected]> Mon, 6 Nov 2006 19:00:01 -0500
| Newsgroups | gmane.ietf.ops-nm |
|---|---|
| Message-ID | <[email protected]> |
--===============2097070085== Content-Type: multipart/alternative; boundary=Apple-Mail-32--133192056 --Apple-Mail-32--133192056 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed David, This is certainly one way to go. Another possibility would be to: 1. Create a single standard that all believe meet all needs WRT FCAPS. 2. The IETF would then be in a position to define a core set of objects in all areas that would support interoperability better and with less cost than is currently the case. In the interim, your suggestion is perhaps the best that can be done. /jon On Nov 6, 2006, at 3:14 PM, David B Harrington wrote: > Hi Randy, > > I think we need to prepare other WGs to move to a multi-protocol > Management Framework, but we do not yet have a standardized > multi-protocol solution for them to move to. Until we have a data > model for netconf (presuming netconf will be the second NM protocol > supported), we should still stress the importance of making IETF > technologies manageable with standardized NM solutions. > > That means we still need to stress the importance of providing a data > model in our only existng standard data modeling language, SMIv2, > until a new data modeling language becomes available. > > Between now and then we should ask the managed-technology WGs to > develop a MIB module for management now, and request a corresponding > information model that can be used to develop a netconf data model > later. > > AND between now and then, the management protocol development > community needs to figure out how to make the two protocols > compatible, so we do not have two standard protocols that cannot share > information. > > David Harrington > [email protected] > [email protected] > [email protected] > > >> -----Original Message----- >> From: Randy Presuhn [mailto:[email protected]] >> Sent: Monday, November 06, 2006 11:03 AM >> To: 'MIB Doctors'; [email protected] >> Cc: 'Mark Townsley' >> Subject: Re: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement >> forconfigurationby SNMP >> >> Hi - >> >>> From: "David B Harrington" <[email protected]> >>> To: "'Romascanu, Dan (Dan)'" <[email protected]>; "'MIB >> Doctors'" <[email protected]>; <[email protected]> >>> Cc: "'Mark Townsley'" <[email protected]> >>> Sent: Sunday, November 05, 2006 10:34 AM >>> Subject: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement >> for configurationby SNMP >> ... >>> Since possible alternatives are on the horizon, and the IETF >>> management framework has always permitted the support for >> alternative >>> protocols for carrying MIB module data, I suggest that any >> long-lived >>> requirements section RECOMMEND, but not REQUIRE, SNMP so that >>> alternative protocols could be used in the future to meet these >>> management functionality requirements. >>> >>> However, I believe that MIB modules and support for SNMP should >>> continue to be required as a condition of IETF standards-track >>> advancement until suitable alternative solutions are completed and >>> available. >> ... >> >> I'm having trouble fitting these two paragraphs together. >> The first is consistent with the changes suggested, but >> the second is a strong argument against making those >> changes. >> >> Randy >> >> >> _______________________________________________ >> MIB-DOCTORS mailing list >> [email protected] >> https://www1.ietf.org/mailman/listinfo/mib-doctors >> > > > > _______________________________________________ > OPS-NM mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/ops-nm Jon Saperia --Apple-Mail-32--133192056 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 <HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; = -khtml-line-break: after-white-space; ">David,<DIV><BR = class=3D"khtml-block-placeholder"></DIV><DIV>This is certainly one way = to go.=A0 Another possibility would be to:</DIV><DIV><BR = class=3D"khtml-block-placeholder"></DIV><DIV><SPAN = class=3D"Apple-tab-span" style=3D"white-space:pre"> </SPAN>1.=A0Create= a single standard that all believe meet all needs WRT = FCAPS.=A0=A0</DIV><DIV><SPAN class=3D"Apple-tab-span" = style=3D"white-space:pre"> </SPAN>2. The IETF would then be in a = position to define a core set of objects in all areas that would support = interoperability better and with less cost than is currently the = case.</DIV><DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV>In the = interim, your suggestion is perhaps the best that can be = done.</DIV><DIV>/jon<BR><DIV><DIV>On Nov 6, 2006, at 3:14 PM, David B = Harrington wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE= type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Hi Randy,</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I think = we need to prepare other WGs to move to a multi-protocol</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Management Framework, but we do not yet have a = standardized</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">multi-protocol solution for them = to move to. Until we have a data</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">model for = netconf (presuming netconf will be the second NM protocol</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">supported), we should still stress the importance of = making IETF</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">technologies manageable with = standardized NM solutions.<SPAN = class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">That means we = still need to stress the importance of providing a data</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">model in our only existng standard data modeling = language, SMIv2,</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">until a new data modeling = language becomes available.</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: = 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Between now and then we should = ask the managed-technology WGs to</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">develop a MIB = module for management now, and request a corresponding</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">information model that can be used to develop a = netconf data model</DIV><DIV style=3D"margin-top: 0px; margin-right: = 0px; margin-bottom: 0px; margin-left: 0px; ">later.</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">AND = between now and then, the management protocol development</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">community needs to figure out how to make the two = protocols</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">compatible, so we do not have = two standard protocols that cannot share</DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">information.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">David Harrington</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A = href=3D"mailto:[email protected]">[email protected]</A><SPAN = class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A = href=3D"mailto:[email protected]">[email protected]</A></DIV= ><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><A = href=3D"mailto:[email protected]">[email protected]</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = min-height: 14px; "><BR></DIV> <BLOCKQUOTE type=3D"cite"><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">-----Original Message-----</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">From: Randy Presuhn [<A = href=3D"mailto:[email protected]">mailto:randy_presuhn@mindspri= ng.com</A>]<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Sent: Monday, November 06, 2006 11:03 AM</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">To: 'MIB Doctors'; <A = href=3D"mailto:[email protected]">[email protected]</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Cc: 'Mark Townsley'</DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Subject: = Re: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement<SPAN = class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">forconfigurationby SNMP<SPAN = class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Hi = -</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: = 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <BLOCKQUOTE = type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">From: "David B Harrington" = <<A = href=3D"mailto:[email protected]">[email protected]</A>><= /DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: = 0px; margin-left: 0px; ">To: "'Romascanu, Dan (Dan)'" <<A = href=3D"mailto:[email protected]">[email protected]</A>>; = "'MIB<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV> = </BLOCKQUOTE><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Doctors'" <<A = href=3D"mailto:[email protected]">[email protected]</A>>; = <<A href=3D"mailto:[email protected]">[email protected]</A>></DIV> = <BLOCKQUOTE type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: = 0px; margin-bottom: 0px; margin-left: 0px; ">Cc: "'Mark Townsley'" = <<A = href=3D"mailto:[email protected]">[email protected]</A>></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Sent: Sunday, November 05, 2006 10:34 AM</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Subject: [OPS-NM] RE: [MIB-DOCTORS] Mandatory = Requirement<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV> = </BLOCKQUOTE><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">for configurationby SNMP<SPAN = class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">...</DIV> <BLOCKQUOTE type=3D"cite"><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Since = possible alternatives are on the horizon, and the IETF</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">management framework has always permitted the = support for<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV> = </BLOCKQUOTE><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">alternative</DIV> <BLOCKQUOTE = type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">protocols for carrying MIB = module data, I suggest that any<SPAN = class=3D"Apple-converted-space">=A0</SPAN></DIV> </BLOCKQUOTE><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">long-lived</DIV> <BLOCKQUOTE type=3D"cite"><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">requirements section RECOMMEND, but not REQUIRE, = SNMP so that</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">alternative protocols could be = used in the future to meet these</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">management = functionality requirements.</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: = 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">However, I believe that MIB = modules and support for SNMP should</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">continue to = be required as a condition of IETF standards-track</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">advancement until suitable alternative solutions are = completed and</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">available.</DIV> = </BLOCKQUOTE><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">...</DIV><DIV style=3D"margin-top:= 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I'm having = trouble fitting these two paragraphs together.</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">The first is consistent with the changes suggested, = but</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">the second is a strong argument = against making those</DIV><DIV style=3D"margin-top: 0px; margin-right: = 0px; margin-bottom: 0px; margin-left: 0px; ">changes.</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">Randy</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">_______________________________________________</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">MIB-DOCTORS mailing list</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><A = href=3D"mailto:[email protected]">[email protected]</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><A = href=3D"https://www1.ietf.org/mailman/listinfo/mib-doctors">https://www1.i= etf.org/mailman/listinfo/mib-doctors</A></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = min-height: 14px; "><BR></DIV> </BLOCKQUOTE><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: = 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; = ">_______________________________________________</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">OPS-NM mailing list</DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A = href=3D"mailto:[email protected]">[email protected]</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><A = href=3D"https://www1.ietf.org/mailman/listinfo/ops-nm">https://www1.ietf.o= rg/mailman/listinfo/ops-nm</A></DIV> </BLOCKQUOTE></DIV><BR><DIV> <SPAN = class=3D"Apple-style-span" style=3D"border-collapse: separate; = border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; = font-size: 12px; font-style: normal; font-variant: normal; font-weight: = normal; letter-spacing: normal; line-height: normal; text-align: auto; = -khtml-text-decorations-in-effect: none; text-indent: 0px; = -apple-text-size-adjust: auto; text-transform: none; orphans: 2; = white-space: normal; widows: 2; word-spacing: 0px; "><SPAN = class=3D"Apple-style-span" style=3D"border-collapse: separate; = border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; = font-size: 12px; font-style: normal; font-variant: normal; font-weight: = normal; letter-spacing: normal; line-height: normal; text-align: auto; = -khtml-text-decorations-in-effect: none; text-indent: 0px; = -apple-text-size-adjust: auto; text-transform: none; orphans: 2; = white-space: normal; widows: 2; word-spacing: 0px; "><SPAN = class=3D"Apple-style-span" style=3D"border-collapse: separate; = border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; = font-size: 12px; font-style: normal; font-variant: normal; font-weight: = normal; letter-spacing: normal; line-height: normal; text-align: auto; = -khtml-text-decorations-in-effect: none; text-indent: 0px; = -apple-text-size-adjust: auto; text-transform: none; orphans: 2; = white-space: normal; widows: 2; word-spacing: 0px; "><SPAN = class=3D"Apple-style-span" style=3D"border-collapse: separate; = border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; = font-size: 12px; font-style: normal; font-variant: normal; font-weight: = normal; letter-spacing: normal; line-height: normal; text-align: auto; = -khtml-text-decorations-in-effect: none; text-indent: 0px; = -apple-text-size-adjust: auto; text-transform: none; orphans: 2; = white-space: normal; widows: 2; word-spacing: 0px; "><DIV>Jon = Saperia</DIV></SPAN></SPAN></SPAN></SPAN></DIV><BR></DIV></BODY></HTML>= --Apple-Mail-32--133192056-- --===============2097070085== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ OPS-NM mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ops-nm --===============2097070085==--