ipcdn-0----Page:18
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
|
RFIv2 MIB Technical Comments, pending Clone mechanism docsIfUpChannelCloneFrom, docsIfUpChannelUpdate and docsIfUpChannelStatus Comment: Still objections in how that works (?) Procedure in place in draft 05, refined and Group agreed with text in ID-10 docsIfCmtsCmStatusEqualizationData Comment: Justification of OCTET STRING (SIZE(0..512)) In DOCSIS 1.x (RFC 2670) was left quite open for vendors implementation (no OCTET STRING constrains). DOCSIS 2.0 has more deterministic size. Leave as DOCSIS 1.x? (no constrains). Note All second generation DOCSIS 1.1 supports RFIv2 MIB ID-05 (no constrains) docsIfCmtsCmStatusValue Removed in ID-13 enumeration value 8 Added: “Value 8 is considered reserved and should not be defined in future revisions of this MIB module to avoid conflict with documented implementations that support value 8” Valid solution ? docsIfCmStatusCode IDs 6-to-12 were SYNTAX OCTET STRING (SIZE (0..16)), Comment: Size constrain does not match description ID-13 is back to RFC 2670 SYNTAX OCTET STRING, Examples T02.1 or W035.4, Up to 6 characters but may be extended in the future What should be the range? Plus indication of space for future enhancements. |