8/14/22, 1:21 PM
`
`LISTSERV - 3GPP_TSG_RAN_WG2 Archives - LIST.ETSI.ORG
`
`3GPP_TSG_RAN_WG2 Archives
`February 2018, Week 1
`
`3GPP_TSG_RAN_WG2@LIST.ETSI.ORG
`
`Options: Use Monospaced Font
`Show Text Part by Default
`Show All Mail Headers
`
`Message: [<< First] [< Prev] [Next >] [Last >>]
`Topic:
`[<< First] [< Prev] [Next >] [Last >>]
`Author:
`[<< First] [< Prev] [Next >] [Last >>]
`
`Draft agenda and schedule for RAN2#101, February 18
`Subject:
`"Burbidge, Richard C" <[log in to unmask]>
`From:
`Burbidge, Richard C
`Reply To:
`Wed, 7 Feb 2018 16:44:43 +0000
`Date:
`multipart/mixed
`Content-Type:
`Parts/Attachments: text/plain (9 kB) , text/html (29 kB) , R2-17xxxxx-RAN2-101-
`Athens-Proposed-Agenda-v1.0.docx (280 kB) , RAN2-101-
`Athens-schedule-v1.0.docx (254 kB)
`
`https://list.etsi.org/scripts/wa.exe?A2=3GPP_TSG_RAN_WG2;9a2222c0.1802A&S=
`
`1/4
`
`Ex.1141
`APPLE INC. / Page 1 of 4
`
`

`

`8/14/22, 1:21 PM
`
`LISTSERV - 3GPP_TSG_RAN_WG2 Archives - LIST.ETSI.ORG
`
`Dear All
`
`Please find aached a dra agenda and meeng week schedule for RAN2#101 in Athens. Please also read
`the guidelines below. The guidelines are based on the those provided at previous meengs but I sll request
`that you read them carefully. Experience shows that some people do not read them. The red text includes
`differences compared to the previous meeng.
`
`Deadlines
`• Document number request deadline: Thursday, 2018-February-15, 23:59 Pacific me.
`• Document submission deadline for documents not related to ASN.1 review: Thursday, 2018-February-
`15, 23:59 Pacific me.
`• Document submission deadline for documents related to ASN.1 review (AI 10.4.3): Tuesday, 2018-
`February-20, 23:59 Pacific me (same as deadline for the ASN.1 review email discussions)
`• Upload announcements on the RAN2 email reflector are not required for tdocs submied before the
`submission deadline. In the exceponal case that you upload a document aer the submission deadline,
`an announcement is required to be sent on the RAN2 email reflector. Late submissions might not be
`reviewed, treated or even included in the chair's skeleton.
`• Juha will provide instrucon for requesng tdoc numbers using the 3GU tool. Please read and follow his
`instrucons carefully.
`
`
`General guidance on correcons to Stage 2 and to Stage 3 for EN-DC.
`• Editorial correcons, wording improvements, etc should first be communicated to the specificaon
`rapporteur for possible inclusion in a rapporteur's running CR, and only submied as a separate
`document if you conclude with the rapporteur that a separate contribuon is needed. (For RRC
`specificaons, such proposed correcons can be provided as part of the ongoing ASN.1 review)
`• For all approved NR specificaons, the rapporteur has already provided a running CR based on the
`outcome of the ad hoc. This will be submied to the meeng as a CR (with CR number allocated). For
`the NR specificaons, only the specificaon rapporteur should request a document type CR.
`• Proposed correcons to the running CRs should be submied as discussion documents (not dra CRs as
`at the ad hoc) that jusfy the proposed change and include a text proposal showing the proposed
`changes (with revision marks) relave to the text of the running CR(s). The jusficaon should at least
`provide the same informaon as the 'reason for change', 'summary of change', and 'consequences if
`not approved' parts of a CR coversheet. Any agreed changes will be added to the running CR by the
`rapporteur/author of that CR.
`• Please group related changes into one document in a sensible way. Do not unnecessarily split changes
`across many separate documents.
`• For EN-DC the focus is on essenal correcons - please do not submit correcons containing
`enhancements to EN-DC.
`• For stage 2 correcons use only AI 10.2.2.x (for EN-DC) and AI 10.2.3 (for non-EN-DC). All other stage 2
`AIs are intended for progressing standalone).
`• For correcons related to ASN.1 then please raise issues as part of the ASN.1 review. Where an ASN.1
`issue requires a discussion document then the issue number from the issue list is to be included in the
`tle of the document.
`• Correcons to 38.331 and 36.331 it is expected that most correcons will be handled as part of the
`ongoing ASN.1 review. If there are contribuons not related to the ASN.1 review then they may be
`submied to AIs 10.4.1.3.1, 10.4.1.4.1, 10.4.1.4.2, 10.4.1.5.1, 10.4.1.5.2, 10.4.2.2, 10.4.2.3. Please check
`what is being addressed within the ASN.1 review before subming contribuons to these AIs.
`
`
`General guidance on correcon to Rel-15 LTE WIs LTE_STTIandPT, LTE_ViLTE_enh2, LTE_QMC_Streaming)
`· These WIs were completed from the RAN2 point of view but the RAN2 CRs have not been implemented
`to the specificaon as described in RP-172755. The CRs will be maintained as running CRs (with the
`same CR number) and then agreed again in RAN2#102 (May).
`· Proposed correcons to the running CRs should be submied as discussion documents that jusfy the
`proposed change and include a text proposal showing the proposed changes (with revision marks)
`relave to the text of the running CR. The jusficaon should at least provide the same informaon as
`the 'reason for change', 'summary of change', and 'consequences if not approved' parts of a CR
`coversheet. Any agreed changes will be added to the running CR by the rapporteur/author of that CR.
`
`https://list.etsi.org/scripts/wa.exe?A2=3GPP_TSG_RAN_WG2;9a2222c0.1802A&S=
`
`2/4
`
`Ex.1141
`APPLE INC. / Page 2 of 4
`
`

`

`LISTSERV - 3GPP_TSG_RAN_WG2 Archives - LIST.ETSI.ORG
`
`8/14/22, 1:21 PM
`
`Idenfying Revisions/Resubmissions
`The purpose of this process is to make it quicker and easier for us all to review documents that are
`resubmission or revisions.
`
`Please mark all document that are revisions or resubmissions by including 'Resubmission of R2-17xxxxx' or
`'Revision of R2-17xxxxx' in second line of the document, immediately below the tdoc number. Use
`resubmission in the case the document has no technical changes (editorial correcons are ok), and use
`revision in the case that there are technical changes. The changes should also be briefly summarised in the
`introducon of the document.
`
`In addion, when requesng the tdoc number for a resubmission (not for a revision) of a discussion
`document via 3GU, please ck the 'Is a revision of' box, enter the tdoc number of the document that was
`submied to the previous meeng, and click the prefill buon. 3GU will then automacally populate the
`fields with the same informaon as the previously submied document. You will then be free change any of
`the info if you need to - in parcular please check that the agenda item is correct for the forthcoming
`meeng. If you use the bulk tdoc request then you should fill the column with the heading 'Is revision of'
`(column Q) but the other document informaon will not be automacally populated for you. In the 3GU
`generated tdoc list, column Q will show the previously submied tdoc number. The content of column Q will
`also be included for each tdoc in the report skeleton. In this way you will be able to easily know from the
`tdoc list or skeleton that a document is an unchanged resubmission.
`
`The above instrucons do not apply for CRs. For CRs please follow the normal process where a tdoc request
`must always be marked as a revision (irrespecve of what type of change is made to the content) in order to
`be given the same CR number (and incremented revision number).
`
`Email discussions
`Please provide your company views to the email discussions and refrain from subming a contribuon to
`the next meeng on the topics that have been adequately addressed by the email discussion. In cases
`where a parcular aspect of an email discussion was not conclusive, and hence a single proposal for a way
`forward cannot be made, then the rapporteur should provide a proposal to discuss, idenfying the key
`quesons to be answered and the main opons to select between. The email discussion report should be
`the only document that needs to be treated on the subject, and other tdocs on the same topic should not
`be necessary.
`
`Responsibilies
`• Please read the agenda carefully and follow the guidance within each agenda item (do not assume the
`agenda will be same as previous meengs).
`• Submit documents to the correct agenda item.
`• Consider carefully whether your document is stage 2 or stage 3 (consider whether for LTE the related
`aspects are captured in 36.300 or in a stage 3 spec)
`• Respect the ''Maximum 1 tdoc per company'' if indicated
`• Do not submit mulple documents with overlapping proposals.
`• Do not submit documents on topics that we have agreed not to discuss unl we have made progress in
`other areas.
`• Correcons to dra TSs should first be communicated to the specificaon rapporteur for possible
`inclusion in a rapporteur's update, and only submied as a separate contribuon to the meeng if you
`and the rapporteur conclude it needs to be first discussed by the group.
`• Text proposals should be incorporated in supporng contribuons, at least for cases where related
`specificaon text already exists (i.e. separate TP documents are discouraged).
`
`CR quality and isolated impact statements:
`• Please focus on high quality CRs and CR coversheets
`• Isolated impact statements, following the agreed guidelines, should be provided for all CRs up to and
`including Rel-14.
`• The reason for change should fully describe the reason for the CR, even if you have provided a separate
`discussion paper. Also, please only provide a separate discussion paper if the problem really requires
`addional supporng informaon to jusfy the change.
`•
`Ensure that the CR is based on the latest available version of the specificaon and that all fields on the
`https://list.etsi.org/scripts/wa.exe?A2=3GPP_TSG_RAN_WG2;9a2222c0.1802A&S=
`
`3/4
`
`Ex.1141
`APPLE INC. / Page 3 of 4
`
`

`

`LISTSERV - 3GPP_TSG_RAN_WG2 Archives - LIST.ETSI.ORG
`8/14/22, 1:21 PM
` Ensure that the CR is based on the latest available version of the specificaon and that all fields on the
`
`ATOM RSS1 RSS2
`
`https://list.etsi.org/scripts/wa.exe?A2=3GPP_TSG_RAN_WG2;9a2222c0.1802A&S=
`
`4/4
`
`Ex.1141
`APPLE INC. / Page 4 of 4
`
`