MetaLLB: Validation unable to create BGPPeers with spec.peerASN Value in OCP 4.10

Customer has installed metallb operator and trying to configure BGPPeer  , but they are having issues with creating it with below error message 

Error "Invalid value: 4247584822: spec.peerASN in body should be less than or equal to 65535" for field "spec.peerASN"

They are not able to create PeerBGB because customer's  ASN value seems to be out of range. just installed the metalLB operator but not able to configure yet

They are using 4 byte ASN (4247584822) on their Cisco Routers, since  peer cannot understand 4 byte, they are  converting  4 byte to 2 byte AS which will be in decimal format (64813.54)

 Peer ASN configured in the DC Gateway are:
2-Byte AS Number: 64813.54
4-Byte AS Number: 4247584822

ASN on Cisco ASR Router cannot be changed, as it is in production supporting thousands on Pods.

It looks like 2-Byte AS is a  kind of legacy numbering and when asked on FRR channel seems like we we don't have 4 bytes support and asked for Asdot fmt maybe something can be added in the next  OCP releases

1.
2.
3.