Capability Parameter Parse Issue

1) ODL only accepts BGP connection if 4-byte AS capability is sent by peer
2) When I enable 4-byte AS support in Spirent it sends the capability along with other capabilities in the same parameter as I show below:

rame 5: 113 bytes on wire (904 bits), 113 bytes captured (904 bits) Ethernet II, Src: Performa_00:00:05 (00:10:94:00:00:05), Dst: Vmware_ce:72:24 (00:0c:29:ce:72:24) Internet Protocol Version 4, Src: 3.3.3.4 (3.3.3.4), Dst: 3.3.3.3 (3.3.3.3) Transmission Control Protocol, Src Port: 179 (179), Dst Port: 34078 (34078), Seq: 1, Ack: 62, Len: 43 Border Gateway Protocol - OPEN Message
Marker: ffffffffffffffffffffffffffffffff
Length: 43
Type: OPEN Message (1)
Version: 4
My AS: 200
Hold Time: 180
BGP Identifier: 3.3.3.4 (3.3.3.4)
Optional Parameters Length: 14
Optional Parameters
Optional Parameter: Capability
Parameter Type: Capability (2)
Parameter Length: 12
Capability: Multiprotocol extensions capability
Type: Multiprotocol extensions capability (1)
Length: 4
AFI: IPv4 (1)
Reserved: 00
SAFI: Unicast (1)
Capability: Support for 4-octet AS number capability
Type: Support for 4-octet AS number capability (65)
Length: 4
AS Number: 200

ODL seems not to like this format because it still complaints about missing 4-byte AS capability where it is clearly there.