Summary (1/2) Issue 1: Advertising relay id in Auth-Application-id or Acct-Application-id Issue 2 and 5: Application id to be used by common diameter messages (ASR/ASA, STR/STA etc) Issue 3 and 16: CER/CEA exchange in open state Issue 4: Proxy staying in the path of the request messages of a session Issue 8: Setting error flag (E-bit) during a CER/CEA exchange Issue 9 and 19: Error codes defined in the wrong categories Issue 10: Unclear semantics with multiple Vendor-Id avp’s in Vendor-Specific-Application-Id Issue 11: Proxy-Info AVP not being returned in the answer message Issue 12: Differing concept and/or usage of Diameter Identity (FQDN + port or FQDN only) |