RE: re: Signaling MIB - Draft 3 - Last Call - Defaultval ues
"Eugene Nechamkin" <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <24CDBA67F085904999751B3C4F9E8C0B85E770@nt-rmna-0740.brcm.ad.broadcom.com> |
#1 - agreed. #2 - do not agree: it does not seem logical to have single DEFVAL value for the MIB object which has cross-country applicability. Eugene Nechamkin. Broadcom Corp. ph: (604) 233-8500 -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Beacham Gordon-CGB005 Sent: Monday, February 16, 2004 4:18 PM To: '[email protected]' Subject: RE: re: [ipcdn] Signaling MIB - Draft 3 - Last Call - Defaultval ues >As NCS Spec does not have any specific reqs for L-package except for ref to GR-506 (appendix A.2 of the NCS Spec), we feel comfortable with the original tComLabs' proposal: "A default value MUST be provided, but it is left up to the implementation to choose a reasonable default." My concern is whether the MIB Drs are going to flag this statement as having no value during review. The object, when queried, is going to return a value whether the statement above is included in the description clause or not. Suggestions: 1. The MTA MUST provide a default value for this object in accordance with published specifications for the country of operation. Reference "TR 101 183 Specification." OR 2. As Mark indicated DEFVAL can be used. Since tComlabs proposed this change, perhaps they could identify the exact DEFVAL clause to be used. Gordon Beacham Digital Core Gateways, BCS Motorola, Inc. 858-404-2335 [email protected] _______________________________________________ IPCDN mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ipcdn