the new scheme, the urgency of the “In messages may still determine the ordering of messages in a queue so that urgent messages would still be displayed” 4.15 56 GS Jerome has put in a comment on this, but we See Comment 3 (above). Open need to make it clear that we do NOT support any requirements to change the ordering of message display based on message attributes of any kind. 4.2.4 1 JC Comment: R [CSG Webex 14 March]: Agreed Closed – In order to clarify rationale for change, it with the suggested change would be helpful to distinguish for “Requests immediate report or confirmation” (e.g. [OPLINKP WG/WHL/4 21 – REPORT PRESENT LEVEL for report and March]: Agree with the suggested ASSIGNED LEVEL”) and change, 4.2.4 revised to the following: “CONFIRM to report upon a specific event” “Instruction Requests for immediate report or (e.g. REPORT MAINTAINING [level confirmation were formed as single]). rather than 4.2.4 shall apply to the first category only. “Requests” “Instructions” as in the past (e.g., REPORT Second category shall still be tagged as POSITION, to report the (W/U resp attribute). “Instruction “instructions” present position” was revised to to report the present Suggested Change: “Request position”). Requests for immediate report or confirmation were formed as rather than “Requests” as in the past (e.g., UM132 “Instructions” REPORT POSITION, to report “Instruction the present position” was revised to “Request to report the present position”).
“In the new scheme, the urgency of the messages may still determine the ordering of messages in a queue so that urgent messages would still be displayed” 4.15 56 GS Jerome has put in a comment on this, but we need to make it clear that we do NOT support any requirements to change the ordering of message display based on message attributes of any kind. See Comment 3 (above). Open 4.2.4 1 JC Comment: In order to clarify rationale for change, it would be helpful to distinguish “Requests for immediate report or confirmation” (e.g. REPORT PRESENT LEVEL for report and “CONFIRM ASSIGNED LEVEL”) and “Instruction to report upon a specific event” (e.g. REPORT MAINTAINING [level single]). 4.2.4 shall apply to the first category only. Second category shall still be tagged as “instructions” (W/U resp attribute). Suggested Change: Requests for immediate report or confirmation were formed as “Requests” rather than “Instructions” as in the past (e.g., UM132 REPORT POSITION, “Instruction to report the present position” was revised to “Request to report the present position”). R [CSG Webex – 14 March]: Agreed with the suggested change [OPLINKP WG/WHL/4 – 21 March]: Agree with the suggested change, 4.2.4 revised to the following: Requests for immediate report or confirmation were formed as “Requests” rather than “Instructions” as in the past (e.g., REPORT POSITION, “Instruction to report the present position” was revised to “Request to report the present position”). Closed
OPLINKPWGWHL-4-APR.docx