RE: RE: [MIB-DOCTORS] Mandatory Requirementforconfigurationby SNMP
"Natale, Bob" <[email protected]> Mon, 6 Nov 2006 16:15:01 -0500
| Newsgroups | gmane.ietf.ops-nm |
|---|---|
| Message-ID | <[email protected]> |
Hi, Yes, I appreciated Dave's insightful observations (esp. wrt things like quantifying "timely" and being more precise about multi-manager operations when stipulating requirements), but agree with Randy (per below) wrt the MUST vs SHOULD implications of them. Cheers, BobN -----Original Message----- From: Randy Presuhn [mailto:[email protected]]=20 Sent: Monday, November 06, 2006 3:52 PM To: 'MIB Doctors'; [email protected] Cc: 'Mark Townsley' Subject: Re: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirementforconfigurationby SNMP=20 Hi - > From: "David B Harrington" <[email protected]> > To: "'Randy Presuhn'" <[email protected]>; "'MIB Doctors'" <[email protected]>; <[email protected]> > Cc: "'Mark Townsley'" <[email protected]> > Sent: Monday, November 06, 2006 12:14 PM > Subject: RE: [OPS-NM] RE: [MIB-DOCTORS] Mandatory Requirement forconfigurationby SNMP=20 > > Hi Randy, >=20 > 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.=20 >=20 > 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. >=20 > 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. >=20 > 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. ... These are all strong arguments for retaining the current MUSTs. I'm even more puzzled by the suggestion to replace them with SHOULDs. Randy _______________________________________________ OPS-NM mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ops-nm _______________________________________________ OPS-NM mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ops-nm