https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2828
--- Comment #4 from Dave B <dbastiani@xxxxxxxxxxxx> 2008-08-25 07:31:57 PDT ---
Anders-
Thanks for the response. I'm not sure what is needed for a feature request or
how large the diameter group is. Perhaps you can point me to a pre-existing
write-up on the feature request procedures?
My comment about the full RFC 4005 compliance was based upon your previous
update that directed me towards the nasreq.xml file. I was surprised with how
small it was so I went back to the RFC and found a few codes that weren't
implemented in the file (see a short list below). It's possible they are
implemented in other files but I guess I was under the assumption that there
would be files created for each spec (RFC, TGPP, etc) that implements
everything within the file rather than relying on inclusion in other places.
3. NAS Messages
This section defines the Diameter message Command-Code [BASE] values
that MUST be supported by all Diameter implementations conforming to
this specification. The Command Codes are as follows:
Command-Name Abbrev. Code Reference
-------------------------------------------------------
AA-Request AAR 265 3.1
AA-Answer AAA 265 3.2
Re-Auth-Request RAR 258 3.3
Re-Auth-Answer RAA 258 3.4
Session-Termination-Request STR 275 3.5
Session-Termination-Answer STA 275 3.6
Abort-Session-Request ASR 274 3.7
Abort-Session-Answer ASA 274 3.8
Accounting-Request ACR 271 3.9
Accounting-Answer ACA 271 3.10
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
