RFC2616 14.35.1 defines Byte-Ranges as fromPosition(incl.)-toPosition(incl.). I just tried to stick with the model. We could make a conceptual cut at AppliedByteRange (and calculate with startIndex and endIndex there) - but then we maybe should find a better name for it to avoid confusion with the similar named Range and ContentRange-Headers