RESUMABLE: Section 4.1.4 seems misplaced

[LPardue]

During WGLC review, @MikeBishop raised the following issue on https://lists.w3.org/Archives/Public/ietf-http-wg/2025JulSep/0123.html

Most of Section 4.1.4 seems misplaced. Other than max-age, these are not limits of a particular upload resource (the topic of Section 4), but limits of the base resource's support of Resumable Uploads. This is indicated by the use of OPTIONS on the base resource to probe for these values. Consider separating Upload-Limit into properties of the base resource and properties of the upload resource, and pulling the properties of the base resource into their own section.

This seems like a design change proposal

[MikeBishop]

Perhaps, perhaps not. It's in the upload resource section, but describes properties of the base resource which can be queried by an OPTIONS request to that resource.

My core suggestion is talking explicitly about the base resource and querying it for the properties, which is already in the doc but too obliquely. That's editorial.

The observation that some properties are specific to a pending upload while others can be declared before an upload begins is an observation — whether we want to retrieve them separately could be a design change or not.

[LPardue]

A pending ToC change might, in part, address this issue; see #3199