Apparently not. Even the current master code for the STUN dissector has the following in the comments:
* - RFC 5389, formerly draft-ietf-behave-rfc3489bis-18
* - RFC 5245, formerly draft-ietf-mmusic-ice-19
* - RFC 5780, formerly draft-ietf-behave-nat-behavior-discovery-08
* - RFC 5766, formerly draft-ietf-behave-turn-16
* - draft-ietf-behave-turn-ipv6-11
* - RFC 3489, http://www.faqs.org/rfcs/rfc3489.html (Addition of deprecated attributes for diagnostics purpose)
And the following methods:
/* Methods */
#define BINDING 0x0001 /* draft-ietf-behave-rfc3489bis-17 */
#define ALLOCATE 0x0003 /* draft-ietf-behave-turn-10*/
#define REFRESH 0x0004 /* draft-ietf-behave-turn-10*/
#define CHANNELBIND 0x0009 /* draft-ietf-behave-turn-10*/
#define CREATE_PERMISSION 0x0008 /* draft-ietf-behave-turn-10 */
/* Indications */
#define SEND 0x0006 /* draft-ietf-behave-turn-10*/
#define DATA_IND 0x0007 /* draft-ietf-behave-turn-10*/
Please check at the Wireshark Bugzilla if there is a item already already open for this issue, and if not create a new one.
answered 26 Feb '15, 03:07

grahamb ♦
19.8k●3●30●206
accept rate: 22%
Hi grahamb,
Does any higher version of wireshark compiles with rfc 6062?
Nope, the excerpts above are from the current latest version of the file.