
|
Summary (2/2) Issue 13: Clarify the usage of application id avp’s (Auth-Application-Id, Acct-Application-Id etc) and how they relate to the application id in the message header Issue 14: Explicit specification on which error class should have the error flag (E-bit) set Issue 15: Duplicate detection requires server side storage of E2E-Id and Origin-Host Issue 17: Removal of trailing [*fixed] avp in Sec 3.2 Issue 18: Clarify re-connect behavior of peer based on value of Disconnect-Cause AVP Issue 20: Determining an offending/invalid AVP contained within a grouped AVP Issue 22: Fetch Data Request & Location Update Request Issue 23: Predictive Loop Detection |