-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarification of Byte Range Object Repair #57
Comments
I favour fixing this in TS 26.517 by specifying stage 3 procedures for Object Repair. A simple improvement to clause 6.2.1 could be: Replace:
with:
However, I'm not sure that clause 9.3.6.2 of TS 26.346 is entirely the correct reference. There may be differences in the procedure that need to be documented directly in TS 26.517, in which case an entirely new clause 6.3 should be added and referenced from here instead. |
The current stage 3 (TS 26.517) does not support the parameters Object repair base URL and Object distribution base URL. Thus, more changes are needed. |
@tlohmar has started drafting a CR to TS 26.517 in S4aI230060. |
Ericsson CR contributed to SA4#123-e:
|
TS 26.517 CR0009r2 has been merged into the following ad hoc contribution:
|
Post-session object repair has been specified by @haudiobe in the run up to SA4#127 (Sophia Antipolis) and the new text was endorsed at this meeting as the way forward:
Further offline editing to occur after this meeting with power granted to SA4 ad hoc meeting to agree a revision of CR0001 to be sent to SA#103 (Maastrict) for agreement. |
Result of offline editing after SA4#127:
Power granted to SA4 ad hoc meeting to agree a revision to be sent to SA#103 (Maastricht) for agreement. |
Following online editing, Change Request agreed by ad hoc meeting:
This has agreed status in SA4:
Sent to SA#103 (Maastricht) for approval in CR Pack SP-240272. |
Problem description
The operation of Byte Range Object Repair is not clear for MBS User Services:
Alternate-Content-Location-1
andAlternate-Content-Location-2
to provide the URLs to the CDN for unicast repair.Suggested solution
Extend clause 6.2.1 in TS 26.517, adding more information about Object Repair URL construction.
Alternatively, extend clause 5.6 in TS 26.502, giving some high-level (stage 2) hints on URL construction.
The text was updated successfully, but these errors were encountered: