[SIPForum-techwg] tag-param and other-param in uri-parameter conflicts in RFC3261 ANBF definition?

[mike xu]

Hi,

When I try to parse the tag in below format (use addr-spec instead of
name-addr, this means it has no "<" ">" exist)
  To: sip:2112 at 192.168.100.12;tag=4e10c-f485
it always failed to get the tag parameter, the tag was dropped.
And after viewing the ABNF definition in RFC3261, I found that it was
caused by other-param conflicts with tag-param. In this case, the tag
parameter would be considered as other-param since the parser don't
know the end of uri-paramter (so it consider tag-param as
other-param).

One workaround solution is to add tag-param definition into url-param,
then the tag could be parsed smoothly.

Could anybody here to confirm this problem ? Is it really a bug of
ABNF definition? If it is, where shall I report it?

Thanks in advance,
Mike