Registered to IANA as PN REQUESTER, with no public protocol documentation behind the name.
IANA lists 2717 for both TCP and UDP as pn-requester, "PN REQUESTER", with 2718 registered as pn-requester2. No specification, vendor documentation, or open implementation of the protocol is publicly available. Nmap carries the registered name and gives 2717 an unusually high open-frequency for an obscure port (about 0.33% of scanned hosts), which means something answers there in the wild — but nothing public identifies what. Treat a listener on 2717 as unidentified software until you fingerprint it locally.
Expose with care
An unidentified listener is the problem, not the port — find the process with lsof or ss before deciding anything about exposing it.
$ sudo lsof -nP -iTCP:2717 -sTCP:LISTENSeen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.