RE: entity mib support for tcif
"Wijnen, Bert (Bert)" <[email protected]>
| Newsgroups | gmane.ietf.entmib |
|---|---|
| Message-ID | <7D5D48D2CAA3D84C813F5B154F43B155023314FE@nl0006exch001u.nl.lucent.com> |
Or..., the DESCRIPTION clause could say that all zeroes for the DateAndTime would mean "manufacture date unknown or nor supported" Just thinking aloud here. By the way, I believe that most of us are on entmib or atommib lists, so I have trimmed all the people names (except whom I responded to). I have bcc:-ed you all this time, so you can spoeak up if my assumtion is incorrect. But even 2 mailing lists... can we move this to one list for now? Thanks, Bert > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:[email protected]] > Sent: zondag 7 september 2003 11:06 > To: Kaj Tesink; [email protected] > Cc: C. M. Heard; Giamboi, Anthony; Lam, Hing-Kam (Kam); Wijnen, Bert > (Bert); [email protected]; Faye Ly > Subject: RE: [Entmib] entity mib support for tcif > > > > If this proposal is adopted, it looks like we need a > DateAndTimeOrNul TC, for these systems that do not support > manufacture date for some reason. > > Dan > > > > > entPhysicalMfgDate OBJECT-TYPE > > SYNTAX DateAndTime > > MAX-ACCESS read-only > > STATUS current > > DESCRIPTION > > "The manufacturing date for the physical entity." > > ::= { entPhysicalEntry xx } >