Dig in 9.19.19 accept weird source- and destination-ports within the "proxy"-statement

Summary

dig in 9.19.19 allows weird source- and destination ports within the new proxy-statement.

BIND version affected

$ dig -v
DiG 9.19.19

Steps to reproduce

Run dig with a source- or destination port statement >65535 (+proxy=127.0.0.1#23784238942739842738942374-127.0.0.1#234234234234238423984234234234). Although the port is fix set to 65535, dig accepts a value >65535:

$ dig @test -p 5353 +proxy=127.0.0.1#23784238942739842738942374-127.0.0.1#234234234234238423984234234234 www.isc.org

; <<>> DiG 9.19.19 <<>> @test -p 5353 +proxy www.isc.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12881
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: f0ee394660e9fe95010000006597c815b35dc2d99d32e656 (good)
;; QUESTION SECTION:
;www.isc.org.			IN	A

;; ANSWER SECTION:
www.isc.org.		160	IN	CNAME	isc.map.fastlydns.net.
isc.map.fastlydns.net.	24	IN	A	151.101.38.217

;; Query time: 4 msec
;; SERVER: 10.100.102.21#5353(test) (UDP)
;; CLIENT PROXY HEADER: source: 127.0.0.1#65535, destination: 127.0.0.1#65535
;; WHEN: Fri Jan 05 10:12:53 CET 2024
;; MSG SIZE  rcvd: 119

What is the current bug behavior?

See above.

What is the expected correct behavior?

I would expect, that dig doesn't allow a weird port setting.