< Previous by Date Date Index Next by Date >
  Thread Index  

[Ietf-behave] [ietf-behave][draft-ietf-behave-turn-02.txt] -- Custom STUN/TURN Message Ids?


Is there some particular postulate or range number that can be used for custom Message Ids apart from the normal list of CONNECT etc.?

Our problem is that we have another message Id that we use that is unfortunately conflicting with the 0x0007 Message Id for the CONNECT request.

As with custom attributes I have proposed the usage of 0x8 in the high order nibble for the mask for custom messages? This is similar to what is done for Custom attributes. Thus our custom message becomes:

0x8001 -- <Custom> Request
0x8101 -- Success <Custom> Response
0x8111 -- Failed/Error <Custom> Response

Any thoughts on the recommended approach?

Regards
Mayank Dev Sondhi