RE: Parameter Padding Question
"Kelly Mcdonald" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <F1A1D21DA394814E824AC89F5A005BA30903C67E@zcarhxm0.corp.nortel.com> |
SIGTRAN community > I am hoping you can help me out with a matter of interpreting a > section that is generating some confusion within my group > > Specifically a part from Section 3.2 > > Parameter Value: variable length. > The Parameter Value field contains the actual information to be > transferred in the parameter. The total length of a parameter > (including Tag, Parameter Length and Value fields) MUST be a multiple > of 4 bytes. If the length of the parameter is not a multiple of 4 > bytes, the sender pads the Parameter at the end (i.e., after the > Parameter Value field) with all zero bytes. The length of the padding > is NOT included in the parameter length field. A sender SHOULD NOT pad > with more than 3 bytes. The receiver MUST ignore the padding bytes. > > My question is, if non-zero padding values are used within the > parameter value, is this still considered a valid message? Based on > the parameter length value we are able to extract the parameter itself > from the message irregardless of the padding. And while the spec calls > for zero bytes to be used, it also states that the padding bytes MUST > be ignored. > > Is the receiver expected to extract a parameter even if the > padding bytes are not zero (i.e. ignore the padding bytes) , or should > the message be rejected as invalid (as the padding is non-zero) > > I hope you can help > > Thanks > > Kelly McDonald BSc. > USP GNPS Team Lead > ESN: 395-1467 > External: 613-765-1467 > [email protected] > [email protected] > > _______________________________________________ Sigtran mailing list [email protected] https://www1.ietf.org/mailman/listinfo/sigtran