monitoredPeriod for /check operation

[QaunainM]

Context
A few months ago the team from this CAMARA API agreed on making a monitoredPeriod value that is added into the API response for /retrieve-date operations

Question

Just to refresh my memory;

What happens on the /check operation if a developer tries to request SIM Swap information for a MaxAge of 744 hours (31 days) if that Telco only supports 30 days due to their privacy rules?

I know for the /retrieve-date operation we will inject the monitoredPeriod into the 200 API response, but I can't remember what logic was decided for the /check operation if the Telco doesn't support the 100 day recommendation that CAMARA have set

Fyi @bigludo7 @hdamker @gregory1g @ToshiWakayama-KDDI

[bigludo7]

For me

In the yaml we mandate the maxAge to be between 1 to 2400.
If the value differ the only option is to send a 400 INVALID_ARGUMENT I guess.
This is challenge-able as commonalities introduced 400 OUT_OF_RANGE and perhaps we should add it.