I've informed the router project of adding support for years in conditional restrictions. No change is needed in the tag, and I've ensured that previous tagging has been restored (apart from the reverts that you did).

Thanks for your input and sorry about the extra work this caused you.

The former tagging is restored.

I've also informed the router project of adding support for years in conditional restrictions. Thanks for your input.

I agree. I've informed the router project of adding support for years in conditional restrictions. Thanks for your input.

I agree. I've informed the router project of adding support for years in conditional restrictions. Thanks for your input.

I don't. I thought this restriction will be removed once its past the due date.

Some opensource routers such as valhalla (https://github.com/valhalla/valhalla/) don't yet support year in the conditional access restriction and is not respecting this closure. And since the closure is short-lived (spans the same yr), I thought it safe to drop the year. Of course, this is assuming the restriction is removed past its due date.

eggie,

Some opensource routers such as valhalla (https://github.com/valhalla/valhalla/) don't yet support "year"
in the conditional access restriction's date range. I think since this is a short-lived closure within the current year, its okay for it to not have the year.

What do you think? Do you have a case where the year is necessary?

Thanks.