Fport 224 and packet size 242 bytes not available on V3

[descartes (Nick McCloud)]

It’s reserved and v3 is moving to hard compliance with attitude.

Prior forum discussion available by a number of search facilities:

Is using port 224 in some "test mode" LoRaWAN compliant?

The LoRaWAN 1.0.x specifications claim: FPort values 1…223 (0x01…0xDF) are application-specific. FPort values 224…255 (0xE0…0xFF) are reserved for future standardized application extensions. However, I see people referring to using port 224 for some “test mode”. Is that LoRaWAN compliant? (Earlier, the above was part of another topic but a bit off-topic there, and I feel that a standalone topic is useful as a future reference.)