![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Opened 14 years ago
Closed 11 years ago
#85 closed design (fixed)
Custom Ranges
| Reported by: | mnot@… | Owned by: | julian.reschke@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 11 |
| Component: | p5-range | Severity: | Active WG Document |
| Keywords: | Cc: |
Description
Either flesh out how to define and use custom ranges, or remove them from the spec.
Attachments (1)
Change History (18)
comment:1 Changed 13 years ago by mnot@…
- Component set to auth
- Milestone set to unassigned
comment:2 Changed 13 years ago by mnot@…
- Component changed from auth to range
comment:3 Changed 13 years ago by julian.reschke@…
- Milestone changed from unassigned to 04
- Owner set to julian.reschke@…
Changed 13 years ago by julian.reschke@…
comment:4 Changed 13 years ago by julian.reschke@…
- Milestone changed from 04 to unassigned
comment:5 Changed 13 years ago by ylafon@…
There is interest in using new range units, in the W3C's Media Fragments WG, the idea of using 'seconds' as a range unit is discussed to avoid a round-trip for the sole goal of finding an adequate byte range.
A sub-issue is about cache behaviour with some units (like XML subtrees) when a cache wants to merge different fragments.
comment:6 Changed 13 years ago by mnot@…
- Milestone changed from unassigned to 06
comment:7 Changed 13 years ago by julian.reschke@…
comment:8 Changed 13 years ago by julian.reschke@…
comment:9 Changed 13 years ago by julian.reschke@…
I reviewed the changes in trunk, and I there are two open questions left:
- what to do with the legacy MS range extension that uses EQ instead of SP
- whether we need to explain that multipart/byteranges will work for other range units as well
comment:10 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from new to closed
comment:11 Changed 11 years ago by mnot@…
- Priority set to normal
- Resolution fixed deleted
- Severity set to Active WG Document
- Status changed from closed to reopened
p5 isn't clear about how other-range-units should be used or what they mean; if we intend not to establish a registry, we need to give *some* guidance to people about their use.
comment:12 Changed 11 years ago by mnot@…
- Milestone changed from 06 to 11
comment:13 Changed 11 years ago by julian.reschke@…
Plan: actually add the registry.
comment:14 Changed 11 years ago by julian.reschke@…
comment:15 Changed 11 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from reopened to closed
The IANA registry was added in -10. I think we are done with this one.
comment:16 Changed 11 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:17 Changed 11 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Proposed BNF change (for now without allowing "=")