In all conformant varying cases, the maximum count MUST be equal to or greater than the sum of actual count and offset. If this validation fails, the implementation MUST treat the octet stream as invalid. Additional Limitations These extensions add the following limitations to those as specified in . Limiting Maximum Count and Octet Stream Length These extensions specify that a conformant array or conformant and varying string SHOULD have, at most, 231-1 elements in each dimension.<65> strict_context_handle A context handle created by a method belonging to one interface SHOULD NOT be accepted by a method belonging to another interface when a strict_context_handle consistency check is activated. For more information on syntax details, see section . Rejecting Insufficient Octet Stream An octet stream MUST contain sufficient data to unmarshal all the required parameters. Implementation of these extensions SHOULD indicate the octet stream as invalid if there is insufficient data. range Attribute to Limit the Scope of Integral Values and the Number of Elements in Pipe Chunks In target level 5.0 of strict NDR/NDR64 data consistency checking, implementation of these extensions can limit the allowed scope for integral types and pipes. If the integral data value is out of the specified range scope, the implementation SHOULD indicate the octet stream as invalid. Implementation of these extensions can also limit the acceptable range of elements in a pipe chunk. The implementation SHOULD indicate the octet stream as invalid if the number of elements in a pipe chunk is out of the specific range scope. For syntax information, see section . auto_handle Deprecation Implementation of this level of the extensions SHOULD NOT accept the auto_handle attribute if specified on an interface.<66> Ignoring Alignment Gap The content of alignment gaps, either within a structure or before an item in the octet stream, SHOULD be ignored. Target Level 6.0 This section specifies target level 6.0 strict NDR/NDR64 data consistency check limitations.<67> Additional Limitations type_strict_context_handle An implementation of extensions at this target level can activate the type strict context handle. When it is activated, the implementation SHOULD reject the use of context handles as an argument if
In all conformant varying cases, the maximum count MUST be equal to or greater than the sum of actual count and offset. If this validation fails, the implementation MUST treat the octet stream as invalid. Additional Limitations These extensions add the following limitations to those as specified in . Limiting Maximum Count and Octet Stream Length These extensions specify that a conformant array or conformant and varying string SHOULD have, at most, 231-1 elements in each dimension.<65> strict_context_handle A context handle created by a method belonging to one interface SHOULD NOT be accepted by a method belonging to another interface when a strict_context_handle consistency check is activated. For more information on syntax details, see section . Rejecting Insufficient Octet Stream An octet stream MUST contain sufficient data to unmarshal all the required parameters. Implementation of these extensions SHOULD indicate the octet stream as invalid if there is insufficient data. range Attribute to Limit the Scope of Integral Values and the Number of Elements in Pipe Chunks In target level 5.0 of strict NDR/NDR64 data consistency checking, implementation of these extensions can limit the allowed scope for integral types and pipes. If the integral data value is out of the specified range scope, the implementation SHOULD indicate the octet stream as invalid. Implementation of these extensions can also limit the acceptable range of elements in a pipe chunk. The implementation SHOULD indicate the octet stream as invalid if the number of elements in a pipe chunk is out of the specific range scope. For syntax information, see section . auto_handle Deprecation Implementation of this level of the extensions SHOULD NOT accept the auto_handle attribute if specified on an interface.<66> Ignoring Alignment Gap The content of alignment gaps, either within a structure or before an item in the octet stream, SHOULD be ignored. Target Level 6.0 This section specifies target level 6.0 strict NDR/NDR64 data consistency check limitations.<67> Additional Limitations type_strict_context_handle An implementation of extensions at this target level can activate the type strict context handle. When it is activated, the implementation SHOULD reject the use of context handles as an argument if
%5BMS-RPCE%5D-160714.docx