dime-1----Page:8
1 2 3 4 5 6 7 8 9 10 11 12
|
Resolved Issues Issue 24 (Sec 2.4): Composing Failed AVP for Invalid AVP length Details: It’s not possible to copy an offending AVP to the Failed AVP when the offending AVP reports a length that is greater than the message length or less than the AVP header length Solution: Allow Failed AVP to carry only the offending AVPs header with a zero-filled payload with the minimum required length Issue 16 (Sec 2.5): Capabilities Exchange in the Open State Details: Peer FSM implies CER/CEA exchange in the OPEN state but such behavior is not specified anywhere Solution: Add a new sub-section to fully describe the behavior CER/CEA exchange is backward compatible and non-disruptive Allow only application support changes and nothing else (i.e. security schemes) |