@GrantGryczan found a mistake in the draft. The max-age limit is defined as:
Specifies the remaining lifetime of the upload resource in seconds counted from the generation of the response.
Later on we say:
In particular, whereas the values for max-size, max-append-size, and max-age can increase without harm, they SHOULD NOT decrease as they can cause ongoing uploads to fail.
If max-age cannot be decreased, the upload resource would never expire, which is obviously not the desired outcome. The sentence from the last quote stems from a draft version where max-age was an absolute timestamp. The restriction made sense back then, because an upload resource shouldn't expire sooner that previously announced or otherwise the client might run into issues. With the value now being a relative duration, the restriction is problematic and has to be rephrased.
@GrantGryczan found a mistake in the draft. The
max-agelimit is defined as:Later on we say:
If
max-agecannot be decreased, the upload resource would never expire, which is obviously not the desired outcome. The sentence from the last quote stems from a draft version wheremax-agewas an absolute timestamp. The restriction made sense back then, because an upload resource shouldn't expire sooner that previously announced or otherwise the client might run into issues. With the value now being a relative duration, the restriction is problematic and has to be rephrased.