Chair's Guide: Difference between revisions

From OCG
No edit summary
 
(168 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{MARKDOWN}}


### Outline
'''Introduction'''


The present document endeavours to provide step-by-step guidance on the essential elements, most common practices and
The present document endeavours to provide step-by-step guidance for an ETSI Chair on the essential elements, most common practices and responsibilities of the ETSI Technical Groups: Technical Committee (TC), ETSI Project (EP), ETSI Partnership Project (EPP), Special Committee (SC) or Industry Specification Group (ISG), Software Development Group (SDG) and the Operational Coordination Group (OCG).
responsibilities of a TB/ISG Chair.


It has been formatted to be used as a quick reference guide together with the ETSI Directives (https://portal.etsi.org/Resources/
It has been formatted to be used as a reference guide according to the ETSI Directives ([https://portal.etsi.org/Resources/ETSI-Directives version 49, June 2024]). If in any doubt regarding the application of the correct procedures, the ETSI Directives prevail and the ETSI Technical Officer can provide guidance.
ETSI-Directives). If in any doubt regarding the application of the correct procedures, the ETSI Secretariat can always provide
guidance.


The scope of this guide covers all ETSI Industry Specification Groups (ISGs) and Technical Bodies (TBs), but does not cover ETSI
The OCG acts as a forum for co-ordination of TCs, ISGs, SDGs, SCs, other Coordination Groups (CGs) and the Secretariat and assists in the resolution in any duplication of effort or conflict of technical views between the Technical Groups.
Partnership Projects (EPP) (e.g., 3GPP and oneM2M). It is to be used in conjunction with the ETSI Delegate’s guide and the
ETSI Rapporteur’s guide.


The scope of this guide does not cover ETSI Partnership Projects (e.g. 3GPP, and oneM2M) or ETSI Projects. It is to be used in conjunction with the [[Delegate's Guide|ETSI Delegate’s guide]] and the [https://portal.etsi.org/Services/editHelp/How-to-start/User-guides/Rapporteurs-guide ETSI Rapporteur’s guide].


= Responsibilities of the Chair =


## 1. Obligations and Responsibilities of the Chair
The primary duties of a Chair:
 
* Ensure an efficient operation of the Technical Group and its Working Groups (in conjunction with the Vice-Chair(s), Working Group (WG) Chair(s) and Vice-Chair(s))
* Ensure the activities of the Technical Group adhere to the ETSI Directives and its rules, policies and procedures
* Maintain strict impartiality and act in the interest of ETSI and its members
* Ensure that the ETSI Guidelines for Antitrust Compliance are strictly observed
* Inform the Technical Group of the Code of Conduct for ETSI Members
* Remind the members of the Technical Group of their statutory obligations to submit IPR disclosures
* Endeavour to reach consensus on all issues, including the approval of draft ETSI deliverables
* Ensure that the Work Programme is kept up to date
* Report to the OCG, Board and the General Assembly on the activities of the Technical Group upon request
* As per Directives v47 (June 2023), a Chair may be appointed for up to three consecutive terms of office (of two years) by the same Technical Group
* As per Directives v49 (June 2024), the incumbent Chair of a Technical Group or a Software Development Group may be authorised to apply for more than 3 consecutive terms of office under certain conditions.
<pre>References: ETSI TWPs Clauses 1.1.2, 1.3.1, 1.3.1.1, 1.3.7, 1.7.1, 3.3, 3.3.1.1, 3.7.1, 7.3.2, 7.3.8 & 7.7.1.
</pre>
= Who is authorised to participate in the activities of an ETSI Technical Group? =
 
== Technical Body and Special Committee meetings ==
To attend a Technical Body (TB) (e.g. a Technical Committee (TC), an ETSI Project (EP)), or a Special Committee (SC) meeting, the delegate shall fulfil one of the following criteria:
 
* Represent an ETSI Full or Associate member or Counsellor
* Represent an Applicant for Full or Associate membership who has formally submitted their application to the ETSI Secretariat (Applicant member), subject to the agreement of the ETSI Director-General
* Represent an ETSI Partner organisation where ETSI has a signed partnership agreement (according to the rules of the relevant agreement). (For further information on the 3 types of partnerships, see the ''External Cooperation with ETSI Partners'' section of this guide.)
* Attend as a Guest (non-member or ETSI Observer) following authorisation by the Chair for three TB/SC meetings or six months (whichever is the shorter)
* Represent an Association which is a Full or Associate member, as an employee or as an elected official. A maximum of one nominated technical expert, from the member of the said Association, shall be allowed to attend a meeting, unless explicitly authorised by the Director-General on a case-by-case basis. Technical experts of an Association attending ETSI meetings shall only represent that Association’s views.
* Represent the European Commission (EC) or the European Free Trade Association (EFTA) as a Counsellor.
* The above points also apply to Working Groups and Task Groups.
 
ETSI Observers and Guests may present a document for information and answer questions related to the information provided in their document, if authorised by the Chair.
 
ETSI Observers and Guests are '''not''' permitted to:
 
* submit written contributions for discussion or decision
* contribute in any way to the work on the deliverables, Change Requests and/or Work Item of the respective TB
* vote or have the possibility to take part in any decision-making process
* subscribe to a TB mailing list or receive any working document, either during the meeting itself or between meetings, or hold any leadership position.
 
----<pre>References: ETSI RoP Articles 1.2.2, 1.2.3, 1.2.4, 1.3 and 1.5, ETSI TWPs Clauses 1.4 and 1.8.1.
</pre>
== TB/SC membership list ==
 
Each TB/SC has an email exploder list to be used for discussion, dissemination and/or collection of information and for decision-making purposes outside of TB/SC meetings. Only delegates subscribed to the TB/SC membership list with their EOL account email address are considered members of the TB/SC.
 
Upon registration to a TB/SC meeting, each delegate (ETSI Full or Associate member or Counsellor) will be automatically subscribed to the TB/SC membership list if not already subscribed.
 
Email exploder lists are also maintained for WGs (Working Groups), TGs (Task Groups) and SCs.
 
Authorised Guests attending a TB/SC meeting shall not be subscribed to the membership list.
 
A representative of an ETSI Partner organisation where ETSI has a signed partnership agreement may be subscribed according to the rules of the relevant agreement.
----<pre>References: ETSI TWPs Clauses 1.5.4 and 1.5.5
</pre>
== Industry Specification Group meetings ==
 
Representatives of an ETSI Full or Associate member, an ETSI Full or Associate Applicant member and an ETSI Partner are authorised to attend ISG meetings. 
 
Representatives of a non-ETSI member (known as ISG Participant) may attend ISG meetings providing ETSI is in receipt of the signed relevant ISG Participant Agreement. Meeting fees are stipulated in the relevant ISG Participant Agreement and shall be paid prior to attendance of a meeting.
 
ETSI Observer members may attend meetings of an ISG and participate in the work without the right to vote subject to having signed the relevant ISG Participant Agreement.
 
A Counsellor is not required to sign an ISG agreement to be able to attend an ISG meeting.
 
For a Guest to attend an ISG meeting on an exceptional and temporary basis, if invited or authorised by the ISG Chair.
 
ISG Participants, Counsellors and Guests shall not vote, support new work items or hold an ISG leadership position. An ISG Participant may hold a Rapporteur position or a WG Vice-Chair position.


The primary duties of a Chair:
<pre>References: ETSI TWPs Clause 3.4 to 3.4.7, 3.7.2
</pre>


- Ensure an efficient working of the TB/ISG and its Working Groups (in conjunction with the Vice-Chair(s), Working
==List of ISG members and Participants==
    Group (WG) Chair(s) and Vice-Chair(s))
- Ensure the TB/ISGs’ activities adhere to ETSI Directives and
    its rules, policies and procedures
- Ensure that the Work Programme is kept up to date
- Maintain strict impartiality and act in the interest of ETSI
    and its members
      - Ensure that the ETSI Guidelines for Antitrust Compliance
          are strictly observed
      - Remind the members of the TB/ISG of their statutory
          obligations to submit IPR disclosures
      - Endeavour to reach consensus on all issues, including the
          approval of draft ETSI deliverables
      - Report to the OCG, Board and the General Assembly on the
          activities of the TB/ISG upon request.


```
Each ISG has a list of its Members, Participants and Counsellors that is available on the portal General Information page.
References: ETSI TWPs Clauses 1.3.3 and 1.7.
```
## 2. Who is authorised to participate in TB/ISG activities?


### 2.1 TB/WG meetings
ETSI member organisations are automatically added to this list upon registration to the relative ISG meeting.


To attend a TB or WG meeting the delegate shall fulfil one of
ISG Participant organisations are added to this list following the signature of the relevant ISG Participant Agreement. European Commission Counsellors are added upon request.
the following criteria:


- Represent an ETSI Full or Associate member or Counsellor.
<pre>References: ETSI TWPs Clause 3.5.4, 3.5.5.
- Represent an Applicant for Full or Associate membership
</pre>
    who has formally submitted their application to the ETSI
    Secretariat (Applicant member), subject to the agreement
    of the ETSI Director-General.
- Represent an ETSI partner organization where ETSI has a
    signed partnership agreement (according to the rules of
    the relevant agreement).
- Attend as a guest (non-member or ETSI Observer) following
    authorisation by the TB Chair for three TB/WG meetings or
    six months (whichever is the shorter) and be in receipt of
    the meeting information from the Secretariat.


ETSI Observers and ETSI non-members may present a
==Software Development Group meetings==
document for information, answer questions related to
the information provided in their document, ask questions
during the meeting and give information or a point of view,
if invited by the Chair.


ETSI Observers and non-members are not permitted to:
Each Software Development Group has a relative Agreement that sets out the participation rules, budget mechanism, terms for code contribution. The SDG Agreement includes a Corporate Contribution License Agreement (CCLA) aligned with the terms of the Software License chosen for the SDG, which may differ from the ETSI IPR Policy. 


- submit written contributions for discussion or decision.
An ETSI Full and Associate member, or an applicant to ETSI Full or Associate membership who has signed the relevant SDG Agreement, may participate in the work of an SDG and have a right to vote at Plenary Meeting and Plenary Level. The right to vote at other levels is governed and the Detailed SDG Working Procedures.
- contribute in any way to the work on the deliverables,
    Change Requests and/or Work Item of the respective TB.
- vote or have the possibility to take part in any decision-
    making process.
      - subscribe to a TB mailing list or receive any working
          document, either during the meeting itself or between
          meetings or hold any leadership position.


```
An Association which is a Full or Associate member shall be represented by their employees and elected officials. In addition, a maximum of one nominated technical expert, per meeting, shall be allowed to attend and participate and shall come from a member of the said Association, unless explicitly authorised by the Director-General on a case-by-case basis.
References: ETSI RoP Articles 1.2.2, 1.2.3, 1.2.4, 1.3 and ETSI TWPs Clause 1.
```
### 2.2 TB membership list


If the SDG Terms of Reference indicates that participation of Observer members and/or non-ETSI members is permitted, participation in the technical work of an SDG is permitted, following the signature of the relevant SDG Agreement, and payment of the appropriate Annual Participation Fee.


Each TB has an email exploder list to be used for discussion,
An ETSI Partner may attend SDG meetings and participate in the work subject to having signed the relevant SDG Agreement and having paid the appropriate Annual Participation Fee.
dissemination and/or collection of information and decision-
making outside of TB meetings. Only delegates subscribed to
the TB membership list with their EOL account email address
are considered members of the TB.
Upon registration to a TB meeting, each delegate (ETSI Full
or Associate member or Counsellor) will be automatically
subscribed to the TB membership list if not already
subscribed.
Email exploder lists are also maintained for Working Groups
(WG), Task Groups (TG) and Special Committees (SC). TB
Guests and Observers may not be subscribed to the TB
membership list.
A representative of an ETSI partner organization where ETSI
has a signed partnership agreement may be subscribed
according to the rules of the relevant agreement.


```
A Counsellor may participate in technical work of an SDG after signing the relevant SDG Agreement.
References: ETSI TWPs Clause 1.5.
```


### 2.3 ISG meetings
The relevant Detailed SDG Working Procedures stipulates the decision-making rights of SDG Participants.


In accordance with ETSI TWPs clause 3.4, representatives
<pre>References: ETSI RoP Articles 1.2.2 to 1.2.4, 1.3 & 1.5; TWPs clause 7.
of an ETSI Full member, Associate member, Applicant
</pre>
member, Counsellor, Partner and non-member (known as
ISG Participant) may attend ISG meetings providing ETSI is in
receipt of the signed relevant ISG Agreement.


ETSI Observers may attend meetings of an ISG and participate
=Meeting responsibilities: preparation, participation, reporting=
in the work without the right to vote subject to having signed
the relevant ISG Participant Agreement. Meeting fees are
stipulated in the relevant ISG Participant Agreement.


For a guest to attend an ISG meeting on an exceptional and
==Introduction==
temporary basis, the rules according to TWPs Clause 3.4,
Annex 2 and Board Decision (D-B108/8) shall be adhered to.


ISG Participants, Counsellors and non-members shall not
A Technical Group (TG) has the freedom to organise its work according to the needs of the members providing it complies with the ETSI Directives.  
vote or hold an ISG leadership position.


### 2.4 ISG membership list
For a TG decision-making meeting (e.g. a plenary), the agenda shall be available at least 30 days beforehand.


```
The ETSI Directives do not make a distinction between different meeting types, although the term “plenary” is used by ETSI TCs, ISGs and SCs.
Each ISG has an email exploder list to be used for discussion,
dissemination and/or collection of information and decision
making outside of ISG meetings. Delegates are subscribed
to the ISG membership list following receipt by the ETSI
Secretariat of the signed relevant ISG Member or ISG
Participant agreement.
Email exploder lists are also maintained for ISG Working
Groups (WG).
ISG Guests may not be subscribed to the ISG membership list.
```
## 3. Meeting responsibilities: preparation,


## participation, reporting
The ETSI portal Meeting application offers various types of meetings e.g., Plenary, Working Group, Rapporteur, Resolution etc.


### 3.1 Before a Plenary meeting
The principles of decision-making are based on consensus or vote.


The Chair shall ensure that the meeting invitation with all
A Technical Group has the right to decide on:
necessary logistical information and the draft meeting
agenda will be available on the ETSI portal and that the TB/
ISG membership is notified at least thirty (30) days before a
plenary meeting.


NOTE: The draft agenda for the first meeting of a new TB or
* number of WGs
an ISG kick-off meeting is announced in a Collective Letter by
* frequency of meetings
the Secretariat, with at least thirty (30) days’ notice. It is the
* organisation of rapporteur’s meetings
responsibility of the host (ETSI or external organisation) to
* deadlines for submitting meeting agenda (other than TG decision-making meeting) and other documents for meetings
disseminate the meeting invitation. The host may always ask
* the way WGs and Rapporteur groups report to the TC/ISG/SC meeting, etc.
for support from the ETSI Secretariat.


Items for decision shall be included in the agenda such as:


- New Work Item (NWI) proposals and draft deliverables for
A non-decision-making meeting of a Technical Group can be used to collect a snapshot of opinions of ETSI members and ISG Participants on a given item or topic.<pre>References: ETSI TWPs Clauses 1.1, 1.3.7, 1.7.1, 3.1 and 3.3.7.
    approval
</pre>
- Any topics in which voting will be required
== Before a Technical Group meeting ==
- The received Chair/Vice-Chair/WG Chair candidatures and
The Chair shall ensure that the meeting invitation with all necessary logistical information and the draft meeting agenda will be available on the ETSI portal and that the TC/ISG/SC membership is notified at least thirty (30) days before a decision-making meeting.
    the call for candidate’s contribution


The following items should also be considered for addition to
NOTE: The draft agenda for the first meeting of a new TC, SC or an ISG kick-off meeting is announced in a Collective Letter by the Secretariat, with at least thirty (30) days’ notice. It is the responsibility of the ETSI Secretariat or the Chair to disseminate the meeting invitation.
the agenda, if relevant:


- Contribution deadline
Items for decision shall be included in the agenda such as:
- Meeting contributions uploaded (in agenda revisions)
- Liaisons statements
- Logistical information
- Future meeting schedule


_References:_ ETSI TWPs Clauses 1.5, 1.7.1, and 1.9.
* New Work Item (NWI) proposals and draft deliverables for approval
* Any topics in which voting will be required
* The received Chair/Vice-Chair/WG Chair candidatures and the call for candidate’s contribution.


### 3.2 During a Plenary meeting
The following items should also be considered for addition to the agenda, if relevant:


```
* Contribution deadline
During a plenary meeting, a Chair has the following
* Meeting contributions uploaded (in agenda revisions)
responsibilities:
* Liaisons statements
```
* Logistical information
- Open the meeting, welcome the delegates, announce any
* Future meeting schedule.
    guests
<pre>References: ETSI TWPs Clauses 1.5, 1.7.
- Make a call for IPR and a reminder of applicable anti-trust
</pre>
    and competition laws
==During a Technical Group meeting==
- Ensure that minutes will be taken during the meeting for
During a TG meeting, the Chair has the following responsibilities:
    the meeting report
- Present the agenda and seek its approval
- Report on the TB/ISG Work Programme status
- Endeavour to reach consensus on all issues
- Launch, run, and evaluate the results of planned vote(s)
    (if any).
- Ensure that all decisions and actions are recorded in the
    meeting report
- If relevant, invite Rapporteurs and Liaison Officers to
    present their activities since the last meeting
- If relevant, invite WG Chair(s) to present their Progress
    reports.


```
* Open the meeting, welcome the delegates, announce any guests or observers
References: ETSI TWPs 1.7, ETSI RoP Article 11 and ETSI IPR
* Make a call for IPR and a reminder of applicable anti-trust and competition laws (see the section ''Responsibilities of the Chair on IPR, Antitrust Compliance and Confidentiality'' of this guide for further details)
Guide, Clauses 2.3.2, 2.3.3 and 2.3.
* Remind delegates of the Code of Conduct for ETSI Members
```
* Ensure a meeting secretary volunteers to draft the meeting report
* Present the agenda and seek its approval
* Report on the TC/SC//ISG work programme status, and make sure it is updated as appropriate
* Endeavour to reach consensus on all issues
* Launch, run, and evaluate the results of planned vote(s) (if any)
* Ensure that all decisions and actions are recorded in the meeting report
* Ensure that all decisions taken by Remote Consensus since the last meeting are recorded in the meeting report
* Invite Rapporteurs and Liaison Officers to present their activities since the last meeting
* Invite WG Chair(s) (if relevant) to present their Progress reports
* Ensure the presence of each attendee is correctly recorded on the portal.
<pre>References: ETSI TWPs 1.7, ETSI RoP Article 11 and ETSI IPR Guide, Clauses 2.3.2 to 2.3.4.
</pre>
==After a Technical Group meeting==


### 3.3 After a Plenary meeting
Following each meeting a report should be provided within 30 days and shall include:


The meeting report shall include:
* decisions, including the election of officials, approved or withdrawn deliverables, and change request decisions
* actions
* key discussion points
* organisational changes to the structure of the TG
* call for IPR disclosures
* the dates and venues of forthcoming meetings
* Attendee list as an Annex or hyperlink.


- decisions, including the election of officials, approved or
If the meeting report is not available within 15 days after the end of the meeting, the Chair is required to provide a list detailing the key decisions and topics.
    withdrawn deliverables, change request decisions
- actions
- key discussion points
- organisational changes to the TB/ISG structure
- call for IPR disclosures are to be included in the report and
- the dates and venues of the forthcoming meetings.


If the meeting report is not available within 15 days after the
The full meeting report should be provided within 30 days and requires the approval of the Technical Group.
end of the meeting, the Chair is obliged to provide Executive
summary detailing the key decisions and topics within this
period.


The Chair is also invited - for purposes of transparency – to
The Chair is also invited - for purposes of transparency - to update the status of Contributions on the portal. <pre>References: ETSI IPR Guide Clauses 2.3.2 to 2.3.5, ETSI TWPs 1.9.
update the status of Contributions on the portal.
</pre>


In any case, the full meeting report should be provided
== Technical Group Open Sessions ==
within 30 days and requires the approval of the TB/ISG.
A Technical Group may need to organise meetings/calls open to ETSI Members and non-Members. This type of meeting is called an Open Session, more details can be found at [https://portal.etsi.org/TB-SiteMap/OCG/TG-Open-Sessions portal.etsi.org/TB-SiteMap/OCG/TG-Open-Sessions]


_References:_ ETSI IPR Guide Clauses 2.3.2, 2.3.3, 2.3.4, 2.3.5,
The Chair ensures that the TG defines the Open Session scope, content, format, location and date. ETSI Secretariat will coordinate the request.
ETSI TWPs 1.9.


### 3.4 Before a non-Plenary meeting
==European Standards and European standardisation deliverables in response to Standardisation Requests (SReqs)==
ETSI may elaborate European Standards and European standardisation deliverables (TR, TS, ES or hEN) in response to SReqs to support the European legislation or policies, in accordance with the amended Regulation (EU) No 1025/2012, which is related to Regulation (EU) 2022/2480.


- For Working Group, Rapporteur, Ad-hoc or other types of
The relevant ETSI Technical Group will engage with the National Standardisation Body Group (NSBG), the National Standardisation Organisation Group (NSOG) and the Annex III organisations throughout the Standardisation Request deliverables Approval Process (SRdAP).
    meetings, it is recommended that an agenda be uploaded
    to the ETSI portal before the meeting and the TB/ISG
    notified via the relevant mailing list.


### 3.5 During a non-Plenary meeting
The European Commission consults ETSI during the drafting of a new Standardisation Request (SReq) that it considers may be of interest to ETSI. ETSI engages the appropriate TC or SC along with the National Standards Body Group (NSBG), the National Standards Organisation Group (NSOG) and the Annex III organisations. ETSI consults the ETSI Board as well the Operational Co-ordination Group (OCG) which acts as a forum for co-ordination and consists of all ETSI committee Chairs and Vice-Chairs. The NSBs take all the decisions by vote on the acceptance of SReqs (not the TG).


During a non-plenary meeting, a Chair (or the nominated
The TC or SC proposes Work Item(s) identified for a Standardisation Request (WISR), once registered by the TC or SC, and the NSB members vote on the adoption or rejection of each WISR.
replacement) has the following responsibilities:


- Open the meeting, welcome the delegates, announce any
Should the TC/SC decide at a later stage to stop a WISR, the ETSI Board is to be consulted before the request to stop the WISR is submitted to an NSBG vote.<pre>References: ETSI RoP Articles 20 & 21, ETSI TWPs 2.2.2, Annexes A.5 and J.
    guests or observers
</pre>
- Make a call for IPR and a reminder of applicable anti-trust
==ENAP (EN Approval Procedure)==
    and competition laws (see clause 4 of the present guide for
    further details)
- Ensure a meeting secretary has been appointed
- Present the agenda and seek its approval
- Endeavour to reach consensus on all issues
- Ensure the presence of each attendee is correctly recorded
    in the portal


### 3.6 After a non-Plenary meeting
This section only applies for ENs (European Standards) that are not related to a Standardisation Request. ETSI may elaborate European Standards (ENs) on a proposal from at least four (4) Full and/or Associate members.


```
These ENs shall be adopted by the eligible National Standards Organisations (NSO) through a Public Enquiry and at least one Weighted National Voting procedure performed in a combined procedure by the eligible members of the National Standards Organizations Group (NSOG).  
The Chair shall:
```
- Upload the meeting report to the portal and inform the TB/
    ISG via the relevant mailing list
- Update the status of the Contributions on the portal.
The main difference between a TB/ISG plenary meeting and
other types of meetings (e.g., Working Group, Rapporteur
etc.) is that TB/ISG plenary can take decisions using all means
described in ETSI Directives, TWPs Clause 1.7 (e.g., decision
based on consensus or vote), whereas the result of a non-
plenary meeting is a snapshot of opinion(s) of ETSI members
on a given item/subject/topic. This result may equally have
the form of consensus or absence of it. In any case the result
shall be reported to the plenary – the place where TB/ISG
decisions are taken.
A TB has the freedom to organise its work according to the
needs of the members providing it complies with the ETSI
Directives, namely:
- number of WGs
- frequency of meetings
- organisation of rapporteur’s meetings
- deadlines for submitting agenda and other documents for
    the meeting
- the way WGs and Rapporteur groups report to the plenary,
    etc.


### 3.7 ENAP (EN Approval Procedure)
Participation in the ENAP shall be restricted to the Annex III Organisations and to the NSO Group (NSOG).


### Resolution meetings
<pre>References: ETSI RoP Article 13, ETSI TWPs Clauses 2.2 to 2.2.1.3.
</pre>


```
==ENAP Resolution meetings ==
This clause only applies for EN (European Standard).
The Chair shall:  
The Chair shall:
```
- Schedule a Resolution meeting when the final draft EN has
    been submitted to the combined Public Enquiry/Weighted
    National Voting procedure; it should take place within
    thirty (30) days after its closure.
- Send the invitation to the TB membership list at least thirty
    (30) days before the meeting.
- Cancel the Resolution meeting should no comments be
    received during the Public Enquiry.


```
* Schedule a Resolution meeting when the final draft EN has been submitted to the combined Public Enquiry/Weighted National Voting procedure; it should take place within thirty (30) days after its closure
References: ETSI TWPs, Clause 2.2.1.1.
* Send the invitation to the TB membership list at least thirty (30) days before the meeting
```
* Cancel the Resolution meeting if no comments are received during the Public Enquiry or if only editorial comments are received and the vote is successful.
<pre>References: ETSI RoP Article 13, ETSI TWPs Clauses 2.2.1.1.1 to 2.2.1.1.3, Annexes A.5, J and T.
</pre>
=Responsibilities of the Chair on IPR, Antitrust Compliance and Confidentiality=


## 4. ETSI Chair’s Responsibilities on Anti-trust
==General==


## Compliance, IPR and Confidentiality
One of the primary duties of the Chair is to take care that the ETSI Guidelines for Antitrust Compliance are strictly observed.


### 4.1 General
The Chair has a duty to remind the TB/SC/ISG members of their obligations to submit IPR disclosures.


One of the primary duties of the Chair is to take care that
==Responsibilities of the Chair on Intellectual Property Rights (IPR) ==
the ETSI Guidelines for Antitrust Compliance are strictly
observed. The Chair has a duty to remind the TB/ISG
members of their obligations to submit IPR disclosures


### 4.2 Chair’s Responsibilities on IPR
At the beginning of a TB/SC/ISG meeting, the Chair shall perform the “Call for IPRs”. An example of a formal call for IPRs, as below: <blockquote>''“The attention of the members of this Technical Body is drawn to the fact that ETSI members shall use reasonable endeavours under Clause 4.1 of the ETSI IPR Policy, Annex 6 of the Rules of Procedure, to inform ETSI of Essential IPRs in a timely fashion. This section covers the obligation to notify its own IPRs but also other companies’ IPRs.''


Throughout the standardization process the Chair shall take
''The members take note that they are hereby invited:''
the actions as laid down in the sections of the Guide on IPRs,
to facilitate the identification of Essential IPRs. This includes
disallowing e.g., discussions on commercial issues in the TB/
ISGs and/or discussions on details of specific licensing terms
and conditions.


Make call for IPRs in TB or ISG
·      ''to investigate in their company whether their'' ''company does own IPRs which are, or are likely'' ''to become Essential in respect of the work of the Technical Body,''


meetings
·      ''to notify to the ETSI Director-General all potential IPRs that their company may own, by means of the IPR Information Statement and the Licensing Declaration forms through the ETSI IPR online database application at https://ipr.etsi.org. Only under exceptional circumstances and if instructed by the ETSI Secretariat, paper declarations may be allowed using the forms provided by the ETSI Secretariat.''


Every TB or ISG meeting starts with a “Call for IPRs” performed
''Members are encouraged to make general IPR undertakings/declarations that they will make licenses available for all their IPRs under FRAND terms and conditions related to a specific standardization area and then, as soon as feasible, provide (or refine) detailed disclosures”.''</blockquote>The Call for IPRs serves as a reminder of the obligations of TB/SC/ISG members in the disclosure of Essential IPRs in a timely fashion.
by the Chair. e.g., this may consist of the following sentences“:


```
Throughout the standardisation process, the Chair shall take the actions as laid down in the sections of the Guide on IPRs, to facilitate the identification of Essential IPRs.
This Call for IPRs is a notice to the TB/ISG member’s
obligations regarding the disclosure of Essential IPRs in a
timely fashion.
The meeting report shall clearly state that an IPR call has
been made as well as any responses.
In addition, during the meeting a short reminder call for IPR
disclosures should be made on:
```
- the formal submission of a technical solution
- the completion of the first stable draft of the standard
- Working Group approval of a draft standard
- TB/ISG approval of a draft standard.


```
During the meeting a short reminder call for IPR disclosures should be made on:
Recording and reporting
information on IPR
The Chair shall be careful to record in the Meeting report
that an IPR reminder was issued and include details of
responses. If no responses were given, then also this should
be recorded.
If the Chair becomes aware of the existence of an Essential
or potentially Essential IPR, the ETSI Legal Director shall be
informed by the Chair.
The Chair should encourage the TB/ISG members to make
general IPR undertakings/licensing declarations that they
will make licenses available for all their IPRs under FRAND
terms and conditions related to a specific standardization
area and then, as soon as feasible, provide (or refine)
detailed disclosures.
```
### 4.3 Copyrights in ETSI Deliverables


```
* the formal submission of a technical solution
The Chair shall ensure that all technical proposals adopted
* the completion of the first stable draft of the standard
by their TB/ISG are recorded in the Meeting report.
* Working Group approval of a draft standard
If restrictions exist on the use of any technical proposals,
* TB/ISG approval of a draft standard.
the Chair shall ensure that these are also recorded in the
Meeting Report and that the ETSI Secretariat is informed.
If, in exceptional circumstances, the use of copyrighted
material cannot be avoided, reproduction of a third-party
text/figure in ETSI deliverables will require the author’s
authorization and the copyrighted material shall be indicated
by the symbol ©.
The Chair should instruct the Rapporteur to obtain the
author’s authorization using the template available from the
editHelp web page.
```
```
“The attention of the members of this Technical
Body is drawn to the fact that ETSI members shall
use reasonable endeavours under Clause 4.1 of the
ETSI IPR Policy, Annex 6 of the Rules of Procedure, to
inform ETSI of Essential IPRs in a timely fashion. This
section covers the obligation to notify its own IPRs
but also other companies’ IPRs.
The members take note that they are hereby invited:
```
_- to investigate in their company whether their_
    _company does own IPRs which are, or are likely_
    _to become Essential in respect of the work of the_
    _Technical Body,
- to notify to the ETSI Director-General all potential_
    _IPRs that their company may own, by means of_
    _the IPR Information Statement and the Licensing_
    _Declaration forms through the ETSI IPR online_
    _database application at https://ipr.etsi.org/. Only_
    _under exceptional circumstances and if instructed_
    _by the ETSI Secretariat, paper declarations may_
    _be allowed using the forms provided by the ETSI_
    _Secretariat similar to the on-line forms
Members are encouraged to make general
IPR undertakings/declarations that they will
make licenses available for all their IPRs under
FRAND terms and conditions related to a specific
standardization area and then, as soon as feasible,
provide (or refine) detailed disclosures”._


The meeting report shall clearly state that an IPR call, and any IPR reminders, has been made as well as any responses. If no responses were given, then also this should be recorded.


```
The Chair shall inform the ETSI Legal Director of the existence of any Essential or potentially Essential IPR.
“The attention of the members of this Technical
Body/ISG is drawn to the fact that ETSI activities are
subject to all applicable antitrust and competition
laws and that compliance with said laws is therefore
required of any participant of this meeting including
the Chair and Vice Chair.
The leadership shall conduct the present meeting
with impartiality.
In case of questions, it is recommended that you
contact your legal counsel”.
```
### 4.4 Chair’s Responsibilities on Antitrust Compliance


As stated in Clause 1.5 of the Technical Working Procedures,
<pre>References: Guide on Intellectual Property Rights, Clauses 2.3, 2.3.2-2.3.4.
when preparing each meeting the Chair and/or the Secretary,
Rules of Procedure, Annex 6: ETSI Intellectual Property Rights Policy.
should give attention to the agenda and ensure it is distributed
</pre>
and/or made available to all participants prior to the meeting.


The meeting shall follow the prepared agenda and only
==Trade names and trademarks ==
matters included on the agenda can be discussed. Revisions
to the agenda can be made during the meeting, by following
the principles of decision making as outlined in the ETSI TWPs
Clause 1.7.1.


The Chair should take care that the ETSI Guidelines for
The use of trade names and/or trademarks that are asserted and/or registered by their owners for designating particular products or services should be avoided in ETSI deliverables. Instead a corresponding standard should be used or a correct designation or a generic description should be given.
Antitrust Compliance are strictly observed by reminding orally
or by writing the following:


### 4.5 Chair’s Responsibilities on Confidentiality
If, in exceptional circumstances, the use of trademarks/trade names cannot be avoided, the recommendations given on editHelp! website in the "Use and reproduction of text, signs and material legally protected" section should be followed.


```
<pre>References: ETSI Directives/Drafting Rules Clause 4.2.
All documents and information provided in or for TB/ISG
</pre>
meetings shall be considered non-confidential unless the
information (in written form AND is identified AND accepted
by the Chair) has been labelled as confidential.
Confidential information that has been incorporated in a
Standard or Technical Specification is automatically regarded
as non-confidential from the moment of publication.
If the Chair becomes aware that confidential information
has been disclosed in breach of a confidential disclosure
agreement to which ETSI is a party, the Chair shall immediately
inform the Secretariat.
```
Managing discussions


Discussions, communications or any other exchange of
==Copyrights in ETSI Deliverables==
information in or on the edge of all ETSI meetings (e.g.:
informal discussions, social gatherings, corridor talks etc.)
as well as during any activity in ETSI may never have as their
subject matter topics that are prohibited by competition law.


If a delegate or the Chair becomes aware of a discussion,
If, in exceptional circumstances, the use of copyrighted third-party material (text/figures) cannot be avoided, reproduction in ETSI deliverables requires the author’s authorisation and the copyrighted material shall be indicated by the symbol © and with proper acknowledgment of its owner.
communication or exchange of information that appears to
lead to restriction of competition of any kind, the delegate
should raise the issue, seek to end or separate from this
discussion, communication or exchange of information.


_References:_ Clause C.4.1 of the Guidelines for Antitrust
The Chair should instruct the Rapporteur to obtain the author’s authorisation using the template available from the editHelp web page.
Compliance.


```
<pre>References: Guide on Intellectual Property Rights, Clause 2.3.5, ETSI Directives/Drafting Rules, Clauses 4.1 & 4.3.
Identification and disclosure of
</pre>
essential IPR
```
```
Guide on Intellectual Property
Rights (IPRs), Clause 2.
Technical Body Chair Duties
```
```
Call or IPR disclosures
```
```
Guide on Intellectual Property
Rights (IPRs), Clause 2.3.
Make call for IPRs in TB
meetings
Guide on Intellectual Property
Rights (IPRs), Clause 2.3.
When and How?
Notification of essential IPR
and licensing declarations
```
```
Annex 6 of the ETSI Rules of
Procedure.
```
```
Record and report information
on IPRs
```
```
Guide on Intellectual Property
Rights (IPRs), Clause 2.3.
Report and Record Information
on IPRs
```
```
Copyrights in ETSI Deliverables
```
```
https://portal.etsi.org/
Services/editHelp/To-
help-you-in-your-work/
Use-and-reproduction-of-
text-signs-and-material-legally-
protected/Copyrights
```
```
Managing discussions
```
```
Guidelines for Antitrust
Compliance - Clauses C.4.1 &
C.4.
Chair’s Responsibilities on
Confidentiality
```
```
ETSI IPR Policy – Annex 6;
Clause 10
```


## 5. Decision Making and Voting
==Responsibilities of the Chair on Antitrust Compliance==


### 5.1 General
The Chair should take care that the ETSI Guidelines for Antitrust Compliance are strictly observed, as per the Anti-trust and competition Statement at the beginning of a TB/SC/ISG meeting: <blockquote>''“The attention of the members of this Technical Body/ISG is drawn to the fact that ETSI activities are subject to all applicable antitrust and competition laws and that compliance with said laws is therefore required of any participant of this meeting including the Chair and Vice Chair(s). The leadership shall conduct the present meeting with impartiality. In case of questions, it is recommended that you contact your legal counsel”.''</blockquote>The Chair shall not allow any discussion on commercial issues, in particular but not limited to, discussions on details of specific licensing terms and conditions, and any subject matter prohibited by competition law. It includes any discussions, communications or any other exchange of information, inside or outside of all ETSI meetings (e.g. informal discussions, social gatherings, corridor talks).<pre>References: Guide on Intellectual Property Rights, Clause 2.3, Guidelines for Antitrust Compliance Clause C.4.1.
</pre>


A TB/ISG shall endeavour to reach Consensus on all issues.
==Responsibilities of the Chair on Confidentiality==


If Consensus cannot be achieved, the TB/ISG Chair can decide
All documents and information provided in or for technical meetings shall be considered non-confidential unless the information (in written form AND is identified AND accepted by the Chair) has been labelled as confidential.  
to take a vote which may be performed by a secret ballot.


Before the vote, the TB/ISG Chair shall provide a clear
Confidential information that has been incorporated in a Standard or Technical Specification shall be regarded as non-confidential from the moment of publication.
definition of the issues (e.g., TB/ISG approval of a draft before
publication).


A description of the tools available can be found in section 10.
Should the Chair become aware that confidential information has been disclosed in breach of a confidential disclosure agreement to which ETSI is a party, the Chair shall immediately inform the Secretariat.


### 5.2 Vote for the election of
=Decision Making and Voting=


### a Chair/Vice-Chair and
==Consensus and consensus-making ==


### WG Chair
Formal standardisation is a process which is open to any individual or organisation (member/participant/counsellor), and its results are produced in consensus with all interested parties.  


### 5.2.1 General
Formal standardisation is inspired by international directives on standardisation, and is based on six principles for the development of international standards:  


In case where there is more than one candidate for the
* transparency,  
election of a Chair/Vice-Chair and WG Chair, a secret ballot
* openness,  
shall be used.
* impartiality and consensus,  


_References:_ ETSI TWPs, Clauses 1.7.1.3 and 3.
* effectiveness and relevance,  
* coherence, and  
* development dimension.  


### 5.2.2 TB
Within Europe, Regulation (EU) 1025/2012 – “the Standardisation Regulation” - places an added emphasis on facilitating the participation of all stakeholders in the standardisation process.


The procedures for the election of a TB Chair/Vice-Chair
Standards are, therefore, products of negotiation among all involved (and relevant) stakeholders, aimed at establishing a general agreement and the absence of sustained opposition.
and WG Chair described in TWPs, Clauses 1.7.1, 1.7.1.1 and
{| class="wikitable"
1.7.1.2 shall apply.
|With respect to the consensus-making process in ETSI, '''the Chair shall  apply''' '''the definition of consensus:'''<blockquote>A general agreement, characterised by the absence of sustained  opposition to substantial issues by any important part of the concerned  interest and by a process that involves seeking to take into account the  views of all parties concerned and to reconcile any conflicting arguments.</blockquote>'''NOTE: Consensus need not imply unanimity.'''
|}
A Technical Group shall endeavour to reach consensus on all issues both during a meeting, and/or in between meetings via the Remote Consensus portal application.


### 5.2.3 ISG
The Chair (or Vice-chair or Rapporteur) should aim to facilitate the discussion in an independent manner, considering:


The procedures for the election of a ISG Chair/Vice-Chair and WG
* The objective is to obtain the largest consensus possible on the content of the standard and resolve potential conflicts.
Chair described in TWPs, Clauses 3.3.1 and 3.3.2 shall apply.


### 5.3 TB/ISG vote during a meeting
* Reaching consensus may take time, taking into account there are different stakeholders represented in a TG.
* Different knowledge domains and backgrounds across committees may imply different "languages and cultures".
* In the case of sustained opposition, this opposition '''shall''' be made known before approval (verbally or in writing) and '''shall''' be recorded in the meeting report(s).


Before a vote, a clear definition of the issues shall be provided
'''If consensus cannot be achieved, the Chair may decide to take a vote which may be performed by a secret ballot either during a meeting or in between meetings.''' Before the vote, the TB/ISG/SDG/SC Chair shall provide a clear definition of the issues (e.g., TB/ISG/SC approval of a draft before publication).
by the Chair.


- Electronic voting is recommended.
Contributions for Decision by Consensus in between meetings shall use the ETSI Remote Consensus tool. Those contributions shall be available at least seven (7) calendar days before the Remote Consensus starts and the minimum duration of the Remote Consensus is at seven (7) days. The Technical Group is to be informed of the results of the Decision within seven (7) calendar days and recorded in the meeting report of the following meeting.<pre>References: ETSI TWPs, 1.7, 3.7.7 and RoP Annex 1.
- Only members who have registered to the meeting and are
</pre>
    present (physically or remotely connected) may vote.
==Technical Group vote during a meeting==
- Only delegates subscribed to the TB membership list
    with their EOL account email address will be considered
    members of the TB.
- In the case of an ISG, only ISG Members can vote and it
    may be based on presence to previous ISG meetings, as
    specified in the ISG Member agreement.
- ISGs may have their own vote calculation rules, as specified
    in the ISG Member agreement (e.g., non-weighted vote,
    simple majority voting may be used).
- Voting by proxy is not permitted.
    - The result of the vote shall be recorded in the meeting report.
    _References:_ ETSI TWPs, Clauses 1.7.1, 1.7.1.1, 3.3 (and its
    sub-clauses) and 3.


### 5.4 TB/ISG vote by correspondence
*Electronic voting is recommended.
*A vote shall be announced to the membership list at least 30 calendar days before the start of the voting period.
*Only members who have registered to the meeting and are present (physically or remotely connected) may vote. For a TC, weighted voting applies.
*All ISG Members are eligible to vote after the kick-off period. ISG voting rules are detailed in the ISG ToR Annex or in the ETSI Directives.
*Voting by proxy is not permitted.
*A Proposal shall be deemed approved if seventy-one percent (71%) of the votes cast are in favour. If a 71% is not achieved the vote shall be re-calculated using the votes of Full members only.
*In the case of an ISG, only Founding Members (as identified in Annex 2 of the ISG agreement) are eligible to vote during the kick-off period. Thereafter, all ISG Members are eligible to vote.
*ISGs may have specific voting rules, as defined in the ISG Member agreement (e.g., non-weighted vote, simple majority voting, voting based on presence to previous ISG meetings).
*Voting by proxy is not permitted.
*The result of the vote shall be recorded in the meeting report.


### 5.4.1 General
<pre>References: ETSI TWPs Clauses 1.5.4, 1.7.1, 1.7.1.1, 3.7.1-3.7.5.
</pre>
==Technical Group vote by correspondence in between meetings==


```
*Electronic voting shall be used.
Before a vote, a clear definition of the issues shall be provided
*Only delegates subscribed to the TB/ISG/SC membership list with their EOL account email address will be considered members of the Technical Group.
by the Chair and disseminated to the TB/ISG membership list.
*The contribution submitted to the vote shall be announced to the membership list at least seven (7) calendar days before the start of the voting period.
```
*The voting period shall be at least two (2) calendar days.
- Electronic voting shall be used.
*Only members who have registered to the meeting and are connected online may vote. For a TC, weighted voting applies.
- Only delegates subscribed to the TB membership list
*All ISG Members are eligible to vote after the kick-off period. ISG voting rules are detailed in the ISG ToR Annex or in the ETSI Directives.
    with their EOL account email address will be considered
*A proposal shall be deemed approved if seventy-one percent (71%) of the votes cast are in favour. If a 71% is not achieved the vote shall be re-calculated using the votes of Full members only. The rule may be different for ISGs, to be checked in the ISG ToR Annex or in the ETSI Directives.
    members of the TB.
*The Technical Group has to be informed of the results of the vote within seven (7) calendar days and recorded in the meeting report of the following meeting.
- The voting period shall be thirty (30) days for a TB.
*The result of the vote shall be disseminated by the Chair to the membership list within seven (7) calendar days and recorded as a decision taken by correspondence in the report of the following meeting.
- The voting period for an ISG shall be 30 days unless
    otherwise specified in the ISG Member Agreement.
- In the case of an ISG, only ISG Members can vote and it
    may be based on presence to previous ISG meetings, as
    specified in the ISG Member agreement.
- ISGs may have their own vote calculation rules, as specified
    in the ISG Member agreement (e.g., non-weighted vote,
    simple majority voting may be used).
- The result of the vote shall be disseminated by the Chair to
    the membership list within 15 days.
_References:_ ETSI TWPs, Clauses 1.5.5, 1.7.1,1.7.1.2 and 3.


### 5.4.2 Use case
<pre>References: ETSI TWPs, Clauses 1.5.5, 1.7.1.2, 1.7.1.3, 3.5.5, 3.7.1 to 3.7.4, 3.7.6
</pre>
==Appointment for the position of Chair/Vice-Chair or WG Chair==


```
=== General===
The following use case is just an example and other scenarios
may occur.
An ISG cannot reach consensus on the approval of a draft for
publication (same could apply to a TB).
The ISG Chair provides a clear definition of the vote to the
ISG mailing list:
« During the last plenary meeting, the ISG could not reach a
consensus on the ISG approval for publication of the latest
draft (V X.Y.Z) of GR/GS XXX.
Therefore, a vote by correspondence is set up... (+ details of
the vote/dates/links etc) »
```
- The ETSI Secretariat sets up the voting tool – on behalf of
    the Chair - with a 30 day-voting period.
- At the end of the voting period, the voting tool reveals the
    results of the vote.
- If the vote is positive (according to RoP, Article 11.4 ), the
    draft is ISG approved and ready to be published by ETSI.
- If not, more discussions within the ISG are needed.


In the case where there is more than one candidate for the position of Chair/Vice-Chair/WG Chair, a secret ballot shall be used.


##### 6. External cooperation with ETSI Partners
If no candidate is elected after a first vote, a second or third ballot may be required.


###### 6.1 Overview of partnership agreements
In the case when there is only one candidate for a Chair/Vice-Chair/WG Chair position, appointment by consensus is required which can take place during a meeting, or in between meetings using the Remote Consensus tool.


When there is a need for the establishment of a partnership agreement, ETSI TBs and ISGs are required to refer to the ETSI
The procedures for the election of a TB/SC Chair/Vice-Chair/WG Chair described in TWPs, Clauses 1.3.1.1 and 1.3.1.2 shall apply.
partnership policy framework and the Partnership Engagement Process (PEP) as described in the TWPs Clause 1.8.1. The TB
Chair will be accompanied by the ETSI Secretariat and the Partnership team.


The TB or ISG Chair should ensure that they are aware of all the relevant partnership engagements with other organizations and
The procedures for the election of an ISG Chair/Vice-Chair/WG Chair described in TWPs, Clauses 3.3.1.1 and 3.3.1.2 shall apply.
that they abide by the partnership engagements for the work of the TBs and ISGs they are responsible for.


There are three different types of partnership agreements depending on partnership engagement:
The Chair of an ISG shall be a delegate of an ISG Member organisation with the status of Full or Associate member.


Letter of Intent (LoI), Memorandum of Understanding (MoU) and Co-operation Agreement (CA).
In the event of a change in the supporting organisation of an ISG Chair, the move should be included in the minutes of the next ISG meeting. If no ISG meeting is planned in the immediate future, the ISG is to be informed by email.


```
The procedures for the election of an SDG Chair/Vice-Chair/WG Chair described in TWPs, Clauses 7.3.2.1 and 7.3.2.2 shall apply.
Engagement Main Focus
=External cooperation with ETSI Partners=
```
```
ETSI
TWPs
Clauses
```
```
Examples, comments
```
```
Type 1
Letter of Intent (LoI)
```
```
Initial contact, get to know each other. 1.8.1.1.
```
```
Type 2
Memorandum of Understanding
(MoU)
[Partner shall be a legal entity]
```
- Political
- Marketing
- Technical


```
==Overview of partnership agreements==
1.8.1.1.
```
```
(LoI) Initial contact, get to know each other. 1.8.1.1.
```
```
Type 3
```
- Political
- Marketing
- Technical


```
When there is a need for the establishment of a partnership agreement, the Technical Group is advised to consult the ETSI partnership policy framework and the Partnership Engagement Process (PEP). The Chair will be accompanied by the ETSI Secretariat in the establishment process.  
1.8.1.1.
```
```
ETSI TWPs include the text of Basic
cooperation agreement between CEN,
CENELEC and ETSI and description of 5
modes of cooperation between
```
```
Co-operation Agreement (CA)
[Partner shall be a legal entity and
an IPR Policy Check performed to
determine the compatibility of the
Partner’s IPR Policy with ETSI’s]
```
```
Supplements 1.8.1.
```
```
ESOs. A synthetic view of each mode
is in TWPs, P Annex 3. (https://portal.
etsi.org/Resources/ETSI-Directives)
```
- PAS Process Guide
- PAS brochure
- ETSI web page about PAS –
    see clause 6.2.2.


```
The Chair should be aware of all relevant partnership engagements with other organisations and the Technical Group abides by the partnership engagements.
Materials Supplement
```
- Incorporation of published text and
    graphics from the other party into a
    document.


```
There are three different types of partnership agreements depending on partnership engagement:
1.8.1.2.
{| class="wikitable"
```
!Engagement
```
!Main Focus
Working Supplement
!ETSI TWPs<br>Clauses
```
! Examples, comments
- Joint production of documents. 1.8.1.2.
|-
**PAS Supplement**
|'''Type 1'''<br>'''Letter of Intent''' (LoI)
- Adoption of identified Partner’s
|First step towards formalising contacts with a new partner.
    PASs into ETSI TR(s) or TS(s).
|1.8.1.1.1
|
|-
|<br>'''Type 2'''<br>'''Memorandum of Understanding'''<br>(MoU)<br>[Partner shall be a legal entity]
- Political<br>- Marketing<br>- Technical
|Establishment of a framework enabling exchange of information on technical grounds and identification of areas of mutual interest.
|1.8.1.1.2
|-
|<br>'''Type 3'''<br>'''Co-operation Agreement''' (CA)<br> <br><nowiki>[Partner shall be a legal entity and an IPR Policy Check performed to determine the compatibility of the Partner’s IPR Policy with ETSI’s]</nowiki>
- Political<br>- Marketing<br>- Technical<br>
|Enabling technical collaboration with the possibility of Supplements to a CA.<br>
|<br>1.8.1.1.3
|ESOs. A synthetic view of each mode is available in TWPs, Annex P. (https://portal.etsi.org/Resources/ETSI-Directives)<br><nowiki>- [PAS Process Guide](</nowiki>https://etsi.org/images/files/ETSI_PAS_Process_Guide.pdf)<br><nowiki>- [PAS brochure](</nowiki>https://www.etsi.org/images/files/Brochures/ETSI-Brochure-PAS.pdf)<br>
|-
|
|'''Supplements'''
|1.8.1.2
|
|-
|
|'''Materials Supplement'''<br> - Incorporation of published text and graphics from the other party into a document.
|<br>1.8.1.2.1
|
|-
|
| '''Working Supplement'''<br> - Joint production of deliverables.
|1.8.1.2.2
|
|-
|
|'''PAS Supplement'''<br> - Adoption of identified Partner’s PASs into ETSI TR(s) or TS(s).
|<br>1.8.1.2.3
|
|}
== ETSI Cooperation Agreements and Supplements==


```
===General Information ===
1.8.1.2.
```
- Detailed information on types of partnership agreements can be found in TWPs, Clause 1.8..
- Full overview of the ETSI Partnership Engagements can be found in TWPs, Annex R.
- The full list of agreements can be found at ETSI Partnership portfolio page on ETSI portal: see clause 6.2.2.
- The description of the Partnership Engagement Process is described at:
    https://portal.etsi.org/Search/Partnership-agreements/Partnership-Establishment


Only a Cooperation Agreement can include a PAS (Publicly Available Specification) Supplement, a Working Supplement or a Materials Supplement for the following purposes:


###### 6.2 ETSI Cooperation Agreements and Supplements
* PAS Supplement enables the ETSI Partner to submit its publicly available specifications to ETSI for adoption into an ETSI TR or TS.
* Working Supplement allows for the creation of a joint document.
* Materials Supplement allows for incorporation of text and graphics from the ETSI Partner into an ETSI document.


###### 6.2.1 General Information
===PAS (Publicly Available Specification) Process===


Whenever there is a Cooperation Agreement signed with a
An ETSI Partner who has signed a Cooperation Agreement and a PAS Supplement can submit its publicly available specifications to ETSI.
supplement, TB and ISG Chairs are encouraged to use the
maximum of the agreement and its supplements.


A Cooperation Agreement may include a PAS Supplement,
The ETSI Partner submits the specification and the PAS work item form to the Board which allocates them to a Technical Group, in coordination with the OCG. The Technical Group shall create the corresponding PAS Work Item immediately after the Board allocation decision, before starting any work.
a Working Supplement or a Materials Supplement for the
following purposes:


- PAS Supplement enables an external organization to submit
The Technical Group will conduct the PAS review and will approve the PAS as a TR or TS following the normal ETSI approval procedure.
    its technical specifications to ETSI for adoption.
- Working Supplement allows for the creation of a common
    work item to produce a joint deliverable
- Materials Supplement allows for incorporation of text and
    graphics in ETSI deliverables.


###### 6.2.2 PAS (Publicly Available Specification) Process
A [https://www.etsi.org/images/files/ETSI_PAS_Process_Guide.pdf PAS Process Guide] is available for download describing the process and its benefits.


The ETSI PAS Process enables an ETSI Partner who has
===Participation of an ETSI Partner representative in ETSI meetings===
signed a cooperation agreement and a PAS Supplement to
submit one or more of its Publicly Available Specifications
for adoption by ETSI as an ETSI Technical Specification (TS)
or as an ETSI Technical Report (TR). The ETSI TB identified
by the ETSI Board will be the host of the PAS review and
will approve the PAS as a TR or TS following the normal ETSI
approval procedure.


The attention of the TB Chair is drawn to the need to create
Partnership agreements may allow for cooperative interworking between ETSI Technical Groups and the Partner, and the attendance of a Partner representative per meeting. This attendance rule also applies to ETSI’s participation in the Partner organisation. This has to be carefully checked for each agreement.  
the corresponding Work Item in the relevant TB immediately
after the Board decision to allocate the PAS to this TB and
before starting any work.


A PAS Process Guide is available for download describing the
The [https://portal.etsi.org/webapp/AgreementView/AgreementSearch.asp ETSI Partnership portfolio] and the description of the [https://portal.etsi.org/Search/Partnership-agreements/Partnership-Establishment Partnership Engagement Process] are available for consultation.
process and its benefits at: https://www.etsi.org/images/
files/ETSI_PAS_Process_Guide.pdf


Further information is available on the ETSI website:
Detailed information on Basic Co-operation Agreement between CEN, CENELEC and ETSI and the description of the 5 modes of cooperation is available in the TWPs, Annex P.
https://www.etsi.org/about/our-partnerships


6.2.3 Participation of an ETSI Partner
A full overview of the ETSI Partnership Engagements can be found in the TWPs, Annex R.


representative in ETSI meetings
===Liaison Statements when there is no Partnership Agreement===


Most of the Partnership Agreements allow for cooperative
Exchange of liaison statements between ETSI Technical Groups and external bodies are to be encouraged as a first step.  
interworking between relevant ETSI TBs/ISGs and the groups
of the other party. This is usually limited to one partnership
representative per ETSI TB/ISG depending on the work
topic. The work topic will be identified in the summary of
the agreement as well as in an annex describing the working
areas.


**NOTE: See Partnership webpage for details:** https://portal.
If such liaisons reach the point where the two bodies concerned are going to exchange technical documents, then the need for a formal Partnership Agreement should be investigated.
etsi.org/webapp/AgreementView/AgreementSearch.asp.


```
===A joint meeting with an organisation that has no Partnership Agreement with ETSI===
This attendance rule also applies to ETSI’s participation in the
partner’s technical bodies.
It shall also be noted that participation by a Partner’s
nominated observer in an ISG is subject to the signature of
the ISG Participant’s Agreement, in accordance with ETSI
TWPs, Clause 3.4.
```
###### 6.3 Cooperation with non-Partners


```
An ETSI Technical Group (TG) can hold joint meetings with an organisation that has no Partnership Agreement with ETSI. This may happen when the ETSI TG and the other organisation identify a potential future collaboration, before the need for a formal partnership.
6.3.1 Participation of Observers and
non-members in ETSI meetings
The conditions for participation of Observers and non-
members in ETSI meetings are described in clauses 2.1 and
2.2 of the present Guide.
```
```
6.3.2 Liaison Statements when there
is no Partnership Agreement
Simple liaisons statements between ETSI TBs/ISGs and
external bodies are to be encouraged as a first step. If such
liaisons reach the point where the two bodies concerned are
going to exchange technical documents, then the need for a
formal Partnership Agreement should be investigated.
```
```
6.3.3 Joint meeting with an
organisation that has no Partnership
Agreement with ETSI
It is possible for an ETSI TB/ISG to exchange information
and even hold a joint meeting with an organisation that has
no Partnership Agreement with ETSI. This typically occurs
during the phase where ETSI and the other organisation are
getting to know each other and before the need for a formal
Partnership is identified.
If a meeting between the two organisations needs to take
place, a set of basic rules and principles must be followed to
comply with the ETSI TWPs and to remain in a safe zone from
the legal standpoint. e.g., no TB/ISG working document can
be discussed in such meeting unless it is publicly available.
Meeting type:
s The meeting cannot be a formal meeting of the TB/ISG or
of the other organisation. ETSI cannot impose its rules on
another organisation and likewise, another organisation
cannot impose its rules on ETSI. Therefore, the meeting
should be organised as a “Workshop” under the umbrella
of the identified TB/ISG.
s If any new content is created during the TB/ISG workshop,
the copyright for that content is jointly owned by ETSI and
the non-partner organisation.
s The principle of the ISG meeting participation fee shall not
be applied to workshops organized between an ISG and a
non-partner organization
```


###### 6.4 Cooperation between ETSI TBs and ISGs
The joint meeting, set up as an Open Session, as previously described in this guide, may contain technical discussions, but shall not be used for the approval of drafts or decisions aiming at modifying drafts. No TG working draft can be discussed unless it is publicly available. Therefore, a set of basic rules and principles must be followed to comply with the ETSI TWPs and to remain in a safe zone from the legal standpoint.


The attention of the TB and ISG Chairs is drawn to the details of cooperation in between ETSI TBs, TBs and ISGs, and in between ISGs.
==Cooperation between ETSI Technical Groups==


Typically, interactions between different TBs and ISGs are based on Liaison Statements (LS) exchange, Liaison Officers reporting and
An ETSI Chair should pay special attention to the rules for cooperation between TBs, SCs and ISGs as detailed in the table below: 
joint meetings.


```
{| class="wikitable"
The table below considers different scenarios of collaboration.
!Cooperation between TBs and ISGs
Cooperation between TBs and ISGs Type of cooperation
!Type of cooperation  
```
|-
```
|Between TBs/SCs
In between TBs
| - Liaison officer <br> - Liaison statement <br> - Joint meeting(s)  
```
|-
```
| TBs/SCs with ISGs <br>Between ISGs
Liaison officer
| - Liaison officer from one ISG or TB/SC can attend another ISG meeting only if the organisation of the Liaison officer has signed the ISG agreement
Liaison statement
- Only working drafts available in the Open Area may be exchanged
Joint meeting(s)
|-
```
|Between ISGs
```
| - Liaison statements
TBs with ISGs
- Joint meeting – see section Open Session
In between ISGs
```
```
Liaison officer from one ISG or TB can attend another ISG meeting
only if his/her organisation signed the ISG agreement
Liaison statements
Joint meeting – see clause 6.3.3 above
(meetings with non-Partners)
```
## 7. ETSI Chair’s Responsibilities –


## Operational Coordination Group (OCG)
- Only working drafts available in the Open Area may be exchanged
|}


###### 7.1 General
=Chair’s Responsibilities – Operational Coordination Group (OCG)=


The OCG acts as a focal point and a forum for co-ordination
==General==
of and between the Technical Committees, ETSI Projects,
ISGs, Special Committees (SC) Coordination Groups (CGs)
and the ETSI Secretariat.


The OCG provides an opportunity for Chairs and ETSI
The Operational Coordination Group (OCG) acts as a focal point and a forum for co-ordination of and between the Technical Bodies (Technical Committees (TCs), ETSI Projects (EPs), Industry Specification Groups (ISGs), Software Development Groups (SDGs) and Coordination Groups (CGs), and between the TBs, ISGs, SDGs, CGs and the Secretariat.  
representatives to CGs initiated by external bodies to
exchange information and experiences; and to discuss any
issues prior to formal resolution of substantial objections in
the Board and respond to Board requests for information.


The OCG also makes recommendations to the Board on
The OCG provides an opportunity for Chairs and ETSI representatives to CGs to exchange information and experiences, to discuss any issues prior to formal resolution of substantial objections in the Board and respond to Board requests for information.
the allocation of resources for STFs and on the proposed
technical testing roadmap and priorities for TTFs. The OCG
is also involved in the endorsement of MoU’s, Cooperation
Agreements, and the processing of PAS Supplements.


```
The OCG shall resolve, as far as possible, any duplication of effort or conflict of technical views between the TBs/ISGs to reinforce co-operation between the Technical Organisation, the ISGs and the CGs.
It shall resolve, as far as possible, any duplication of effort or
conflict of technical views between the TBs/ISGs to reinforce
co-operation between the Technical Organization, the ISGs
and the CGs.
A TB/ISG Chair will be periodically requested to report to the
OCG on the progress, issues and topics for decision.
```
###### 7.2 The Chair’s role in the OCG


```
A Chair will be periodically requested to report to the OCG and the Board on the progress, topics for decision and any issues.
OCG meetings are open to TB and ISG Chairs, and meetings
are called as required to fulfil the duties as mentioned above.
Periodically (typically every two years), each TB and ISG Chair
is required to present progress reports to the Board meeting.
```


## 8. STF/TTF Management and
<pre>References: ETSI TWP Clauses 4 & 5
</pre>


## Chair’s responsibilities
=STF/TTF Management and Chair’s responsibilities=


###### 8.1 General
An active contribution of the Technical Group (TG) Chair is required in the phases listed below:


An active contribution of the TB/ISG Chair is required in the
==Drafting the STF/TTF Terms of Reference==
phases listed below.


###### 8.2 Drafting the Terms of Reference
The Chair makes sure that a new Special Task Force or Testing Task Force (STF/TTF) proposal, including the related Work Items, is supported by at least four (4) ETSI members and approved by the Technical Group, irrespective of the funding source.


The Chair makes sure that a new Special Task Force or Testing
==STF/TTF Work plan==
Task Force (STF/TTF) proposal, including the related Work Items,
The work plan included in the STF/TTF Terms of Reference (ToR) is established by the TG Chair, in consultation with the ETSI Secretariat.
is supported by at least four (4) ETSI members and approved by
the Reference Body, irrespective of the funding source.


###### 8.3 STF/TTF Work plan
==Submission of STF/TTF proposal funded by ETSI (Funded Work Programme) ==


The work plan included in the STF/TTF Terms of Reference
ETSI Secretariat notifies the OCG biannually with the allocation process and calendar.
(ToR) is established by the Reference Body Chair, in
consultation with the ETSI Secretariat, and contains the
following elements:


- latest schedule for the availability of the base documents
STF proposals under the ETSI budget can be submitted in the two allocation steps, in quarter three for (Y+1), and in quarter two (Y) (depending on the ETSI budget contingency, and for urgent requests only).
- milestones and reporting schedule
- deliverables schedule
- tasks and resources assigned to the service providers
- provisional travel plan for the participation of service
    providers’ personnel to meetings and events.


###### 8.4 Submission of STF/TTF proposal
===Submission of STF proposal funded by EC/EFTA ===


###### 8.4.1 Submission of STF proposal
First, the ETSI Secretariat notifies the OCG of the EC schedule and process for the submission of:


To be able to benefit from EC/EFTA funding, an STF proposal
* Spontaneous STF proposals for a first assessment by the EC, with the required EC technical proposal template  (twice a year)
can be submitted in response to the Rolling Plan for ICT
Standardisation (ICT RP), the Annual Union Work Programme
or other specific EC policy documents. STF proposals under
the ETSI budget, can be submitted in the two allocation steps,
in October/November and in May/June time periods.


###### 8.4.2 Submission of TTF proposal
* Opening of European Innovation Council and SMEs Executive Agency (EISMEA) calls (e.g. 3 times a year).


- The TB/ISG Chair is to liaise with the responsible Director at
Secondly, the ETSI Secretariat informs the OCG of each EISMEA call of:
    each step of TTF proposal submission.
- The initial TTF ToR should be sent to the responsible Director
    before the date indicated in the TTF Process Calendar, so
    it can be incorporated into the following year’s Technical
    Roadmap.
- The TB/ISG Chair is to present and defend the work behind
    the TTF proposal at the September Board/OCG meeting.


###### 8.5 Recruitment of the experts
* Topics selected by the EC
* Deadline for EISMEA proposal submissions
* Required EISMEA template.


```
Then, EISMEA evaluates the relevance, quality and impact of the STF proposal. For each criterion there is a threshold which shall be met to receive a positive assessment from EISMEA. If the assessment is positive, ETSI Secretariat and EC/EFTA finalise the process and the STF may begin.
Applications from ETSI members active in the TB/ISG are
encouraged. The STF/TTF Manager and the Chair should
assess the applications and draw up a short list of candidates.
To avoid a conflict of interest in the selection of service
providers, the Reference Body Chair/Vice-Chair(s) and the
Chair of the Working Group directly concerned by the STF/
TTF activity and who belong to an organization that has
an interest in applying for selection as a service provider
to a funded STF/TTF, shall declare this to the Board and
subsequently be excluded from all discussions and decisions
related to the selection of the service providers.
```
###### 8.6 Preparatory Meeting (Experts’ interview)


```
===Submission of TTF proposal===
The TB/ISG Chair should attend the preparatory meeting to
select the experts, appoint the STF/TTF Leader, and decide on
the draft Work Plan and allocation of resources. This should
be done in coordination with the ETSI STF/TTF Manager
& Technical Officer and, in case of a TTF, the responsible
Director.
```
###### 8.7 Monitoring STF/TTF progress


```
TTF proposals are under the ETSI budget and can be submitted by the end of summer (e.g. 2 weeks before the ETSI September Board meeting). An email is sent biannually to the OCG by the CTI Director with the allocation process and calendar.  
The Chair is expected to provide technical guidance. The
STF/TTF leader is appointed by the Director-General in
consultation with the relevant TB/ISG Chair. The STF/TTF
leader acts as the interface with the Director-General for
management of the STF/TTF, with the service provider(s)
for coordination of the project and with the TB/ISG Chair for
technical control. It is recommended that a Steering Group
(SG) is set up. It is essential to ensure the timely approval of
the STF/TTF deliverables by the TB/ISG.
```
###### 8.8 STF/TTF Reporting


```
The Technical Group Chair is to liaise with the CTI Director at each step of the TTF proposal submission.
The Chair approves the STF/TTF Progress Reports which
confirm the achievement of the intermediate milestones
against which the experts’ companies will be paid by ETSI
Director-General.
Whenever possible, the reports should be reviewed and
endorsed by members of relevant TB/ISG, before the
approval by the TB/ISG Chair.
```
###### 8.9 Closing the STF/TTF


```
The initial TTF ToR (at least the Part 1) should be sent to the CTI Director before the date indicated in the TTF Process Calendar, so it can be incorporated into the following year’s Technical Roadmap.
Upon completion of the STF/TTF work, the TB/ISG Chair shall
ensure that feedback is provided to the Director-General on
the STF/TTF work.
```


##### 9. EC cooperation
The CTI Director presents and justifies the full TTF Roadmap  at the September Board/OCG meeting.


The ETSI Director-General (or a nominated substitute)
If the TTF is approved, the TTF ToR Part 2 and the corresponding work items have to be approved by the Technical Group, before starting the call for experts’ process.
represents ETSI within the relevant committees of the EC
and EFTA concerning advisory or regulatory standardization
issues.


The TB/ISG Chair should be aware of all the relevant liaisons
==Recruitment of the STF/TTF experts==
between ETSI and the EC.


The TB/ISG Chair should also consider/verify relevant
Applications from ETSI members active in the Technical Group are encouraged.
contributions of the TB/ISG to EC/EFTA Annual Union Work
Programme (AUWP), the Rolling Plan for ICT Standardisation
and any other EU policy.


The main goal of contribution to AUWP is to indicate
The ETSI Secretariat (Technical Officer (TO) and Head of Funded Activities) and the Chair should assess the applications and draw up a short list of candidates. In the case of TTFs, the CTI Director must be represented as well.
what needs to be mandated by the EC for ESOs (AUWP
targets ESOs only). AUWP is adopted after having
conducted EC consultation with relevant stakeholders:
ESOs, Member States and Annex III organisations (see
Regulation 1025/2012). In many cases, a pre-condition for


```
To avoid a conflict of interest in the selection of service providers, the Reference Body Chair/Vice-Chair(s) and/or the Chair of the Working Group directly concerned by the STF/TTF activity and who belong to an organisation that has an interest in applying for selection as a service provider to a funded STF/TTF, shall declare this to the Board and subsequently be excluded from all discussions and decisions related to the selection of the service providers.
a Standardisation Request is an item in the AUWP. On the
other hand, AUWP is not binding for the EC.
Standardisation actions identified in Rolling plan for ICT
Standardisation are complementary to other instruments, in
particular the Annual Union Work Programme (AUWP).
Normally, it is for the ETSI Secretariat to coordinate the
response to the AUWP, the Rolling Plan for ICT Standardisation
and any other EU policy. Information is shared among the
ETSI members through the ETSI OCG and relevant ETSI
BOARD meetings.
References:
```
- AUWP - https://ec.europa.eu/growth/single-market/
    european-standards/notification-system_en
- Rolling plan for ICT standardisation - https://joinup.
    ec.europa.eu/collection/rolling-plan-ict-standardisation/


##### 10. ETSI working tools
==STF/TTF Preparatory Meeting (Experts’ interview)==


```
The TG Chair should attend the preparatory meeting with the selected experts, decide on the draft Work Plan and allocation of resources and check the Milestones. This should be done in coordination with the ETSI Head of Funded Activities and the TO and, in the case of a TTF, the CTI Director.
Most of ETSI’s work is carried out by electronic means - by
email exploder lists and via the ETSI portal.
An ETSI on-line (EOL) account is required to access most
areas such as the ETSI portal.
The ETSI Work Programme (EWP) contains all the technical
activities and work items of ETSI committees and ISGs and
enables the download of ETSI publications via a search
engine.
Remote Consensus is the ETSI online tool to collect
comments and measure consensus for contributions during
a given period as opposed to during a face-to-face meeting.
The TB Decision Support application is designed to help the
Technical Bodies/ISGs in their decision-making processes.
Several types of formal Voting procedures (as opposed to
consensus gathering) are predefined, including the vote for
the approval of a draft, selecting a technology and electing
officials.
The e-Approval application is the means for voting on draft
ETSI Standards, ETSI Guides, ETSI European Standards and
ETSI Harmonized European Standards. The consultation of
comments and/or results of votes on such documents is
also possible.
```
_Figure 1: Overview
of ETSI working tools_


==Monitoring STF/TTF progress==


##### 11. ETSI Secretariat Contacts
The Chair is expected to provide technical guidance. The STF/TTF leader is appointed by the Director-General (DG) in consultation with the relevant TG Chair. The STF/TTF leader acts as the interface with the DG for management of the STF/TTF, with the service provider(s) for coordination of the project and with the TG Chair for technical control. It is recommended that a Steering Group (SG) is set up, its main role is to provide technical support input and guidance during the lifecycle of the STF/TTF. It is essential to ensure the timely approval of the STF/TTF deliverables by the TG.


```
==STF/TTF Reporting==
Secretariat team Role Web page
```
```
Standards Development Centre (SDC) Secretariat support to TBs/ISGs. https://portal.etsi.org/People/Commitee-Support-Staff
```
```
Centre for Testing and Interoperability (CTI)
```
```
Support to TBs/ISGs for the specification
and validation of base standards and the
development of test specifications.
```
```
https://portal.etsi.org/Services/Centre-for-
Testing-Interoperability/Contacts
```
```
editHelp! Support and guidance for the drafting and finalisation of ETSI deliverables. https://portal.etsi.org/Services/editHelp
```
```
IT Helpdesk Assistance for technical issues on ETSI Portal, EOL accounts, etc. helpdesk@etsi.org
```
```
Membership
```
```
Advise on membership categories,
application process, fees.
Liaises with the Official member contact.
```
```
https://www.etsi.org/membership
```
```
Communications
```
```
Manage the ETSI website, social media,
press releases, webinars, blogposts,
brochures, leaflets and the Enjoy! magazine.
Manage the finalisation and publication of
White Papers, not under the control of ETSI.
```
```
https://www.etsi.org/newsroom
```
```
Events
```
```
Manage endorsements of events and
negotiate special conference rates (speaking
slots and stands).
Organise and promote ETSI workshops.
```
```
https://www.etsi.org/events
See forthcoming and past seminars,
plugtests, webinar details
```
**_The table below provides an overview of Secretariat teams available for delegates._**


The Reference Body approves the STF/TTF Progress Reports which confirm the achievement of the intermediate milestones against which the experts’ companies will be paid by the ETSI Director-General.


##### Annex 1 - Abbreviations
==Closing the STF/TTF==


For the purposes of the present document, the following
When the Final STF/TTF report is approved by the Reference Body, feedback is given to the Head of Funded Activities, and the CTI Director in case of a TTF, and the STF/TTF is closed.
abbreviations apply:


AUWP Annual Union Work Programme
<pre>References: TWPs 1.10.1 to 1.10.9, Annex H, ETSI STF/TTF Expert’s Guide.
</pre>


CA Co-operation Agreement
=EC/EFTA cooperation and Chair's responsibilities =
The ETSI Director-General (or a nominated substitute) represents ETSI within the relevant committees of the EC and EFTA concerning advisory or regulatory standardisation issues.


CG Coordination Group
The TB/SC/ISG Chair should be aware of all the relevant communications between ETSI and the EC. The TB/SC/ISG Chair should also consider/verify relevant contributions of the TB/ISG to EC/EFTA  Annual Union Work Programme (AUWP), the Rolling Plan for ICT Standardisation (ICT RP) and any other EU policy, when requested by ETSI Secretariat, e.g. twice a year.


EC European Commission
The ICT RP is a bottom-up approach: the standardisation community (not only ETSI), represented in the Multi-Stakeholder Platform (MSP), provides a programme of standards or other deliverables in support of EU policy objectives. It gives an overview of ongoing standardisation work, e.g. needs and gaps. ETSI as a member of the Multi-Stakeholder Platform (MSP) is included in the MSP consultation.


EDRs ETSI Drafting Rules
Standardisation actions identified in Rolling plan for ICT Standardisation are complementary to other instruments, in particular the Annual Union Work Programme (AUWP).


EG ETSI Guide
The AUWP is a top-down approach from the EC and reflects EC expectations, e.g. Standardisation Requests (SReqs). The main goal of contributing to the AUWP is to indicate what needs to be mandated by the EC for ESOs (AUWP targets ESOs only). The AUWP is adopted after having conducted EC consultation with relevant stakeholders: ESOs, Member States and Annex III organisations (see Regulation 1025/2012). In many cases, a pre-condition for a Standardisation Request is an item in the AUWP. On the other hand, the AUWP is not binding for the EC.


EFTA European Free Trade Association
The ETSI Secretariat coordinates the response to the AUWP, the ICT RP and any other EU policy. Information is shared among the ETSI members through the ETSI OCG and relevant ETSI BOARD meetings.


EN European Standard
<pre>References:
AUWP: https://ec.europa.eu/growth/single-market/european-standards/notification-system_en
ICT RP:https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/
</pre>
=ETSI working tools and services=
ETSI offers a set of electronic means to work and collaborate via the [https://portal.etsi.org/home.aspx ETSI portal] for which an [https://portal.etsi.org/CreateAccount#/home ETSI on-line (EOL) account] (username and password) is required.


ENAP EN Approval Procedure
Guidance on how to use these electronic tools is available from the [http://help.etsi.org/index.php?title=Overview portal wiki help pages] including FAQs. Some examples of ETSI tools and services:


EOL ETSI on-line
* [https://portal.etsi.org/webapp/TBMembershiplist/ Membership/Exploder Lists]
* The [https://portal.etsi.org/webapp/workprogram/SimpleSearch/QueryForm.asp ETSI Work Programme (EWP)] enables to search the TB/SC/SDG/ISG work programme and download ETSI working drafts/publications.
* [http://webapp.etsi.org/MeetingManagement/ Meetings management] and contributions handling
* [http://help.etsi.org/index.php?title=Remote_Consensus Remote Consensus] is the ETSI online tool to collect comments and measure consensus for contributions.
* The [https://portal.etsi.org/webapp/tbdecision3/Menu.asp TB Decision Support] application includes several types of formal Voting procedures (as opposed to consensus gathering) which are predefined e.g. vote for the approval of a draft, selecting a technology and electing officials.
* The [https://portal.etsi.org/webapp/EApproval/ e-Approva]l application is the means for voting on SRdAP topics, draft ETSI Standards, ETSI Guides, ETSI European Standards and ETSI Harmonised European    Standards. The consultation of comments and/or results of votes on such documents is also possible.


EP ETSI Project
=ETSI Secretariat Contacts=


EPP ETSI Partnership Project
The Chair is encouraged to contact the ETSI TO with regards to requests involving ETSI Secretariat services, as detailed in the table below.
{| class="wikitable"
! Secretariat team
!Role
! Web page
|-
|Committee Support Staff Standards Development Centre (SDC)
|Secretariat support to the technical organisation and Standardisation Requests coordination.
|https://portal.etsi.org/People/Commitee-Support-Staff<nowiki/> Contacts:
[mailto:ESPsupport@etsi.org ESPsupport@etsi.org];


ES ETSI Standard
[mailto:ISGsupport@etsi.org ISGsupport@etsi.org];


ETSI European Telecommunications Standards Institute
[mailto:SRteam@etsi.org SRteam@etsi.org]


EWP ETSI Work Programme
|-
|Centre<nowiki/> for Tes<nowiki/>ti<nowiki/>ng and Inte<nowiki/>roperability (CTI)<nowiki/>
| Support of the validation of base standards and the development of test specifications.
|[https://portal.etsi.org/Services/Centre-for-Testing-Interoperability https://portal.etsi.org/Services/Centre-for-Testing-Interoperability/]
Cont<nowiki/>act:
[mailto:CTI&#x20;support@etsi.org CTI_support@etsi.org]
|-
|Software and Standards (SNS)
|Secreta<nowiki/><nowiki/>riat support to software development groups.
|Contact: [mailto:SDGsupport@etsi.org SDGsupport@etsi.org]
|-
|editHelp!
|Support and guidance for the drafting and finalisation of ETSI deliverables.
|https://portal.etsi.org/Services/editHelp<nowiki/>
Contact: [mailto:EditHelp@etsi.org editHelp@etsi.org]
|-
|IT Help<nowiki/>desk
|Assistance for technical issues on ETSI Portal, EOL accounts, etc.
|Contact: [mailto:helpdesk@etsi.org helpdesk@etsi.org]
|-
|Membership
|Advise on membership categories, application process, fees.
Liaison with the Official member contact.
|https://www.etsi.org/membership<nowiki/>
Contact: [mailto:Membership@etsi.org membership@etsi.org]
|-
| Funded Activities 
|Support to STFs, TTFs, Plugtests™ and Special Projects.
|https://portal.etsi.org/STF/STFs/Summary  
Contact: [mailto:Stflink@etsi.org stflink@etsi.org]
|-
|Communications
|Management of the ETSI website, social media, press releases, webinars, blogposts, brochures, leaflets and the Enjoy! magazine.
Management of the finalisation and publication of White Papers, not under the control of ETSI.
|https://www.etsi.org/newsroom<nowiki/>
Contacts: [mailto:COM@etsi.org COM@etsi.org]; [mailto:Info@etsi.org info@]<nowiki/>[mailto:Info@etsi.org etsi.org]
|-
|Events
|Management of the endorsements of events (seminars, plugtests, webinars) and negotiation of special conference rates (speaking slots and stands).
Organisation and promotion of ETSI workshops.
|https://www.etsi.org/events<nowiki/>
Contact: [mailto:Events@etsi.org events@etsi.org]
|-
|Legal
|Responsible for the IPR Policy and IPR Guide, disclosure of Standard Essential Patents (SEP), and ownership of ETSI Copyright and Trademarks.
Provision of legal advice upon request.
|https://www.etsi.org/about/legal
Contact: [mailto:Legal@etsi.org legal@etsi.org]
|-
|Partnerships
|Development and maintenance of the ETSI partnership portfolio, interaction with the National Standards Organisations (NSOs)
|https://www.etsi.org/about/our-partnerships
Contact: [mailto:Partnerships@etsi.org partnerships@etsi.org]
|}


FRAND Fair Reasonable and Non-Discriminatory
=Annex 1 - Abbreviations=


GA General Assembly
For the purposes of the present document, the following abbreviations apply:


GR Group Report
* AUWP Annual Union Work Programme
* CA Co-operation Agreement
* CG Coordination Group
* CTI ETSI Centre for Testing and Interoperability team
* DG ETSI Director General


GS Group Specification
* EC European Commission
* EDRs ETSI Drafting Rules
* EG ETSI Guide
* EFTA European Free Trade Association
* EISMEA European Innovation Council and SMEs Executive Agency
* EN European Standard
* ENAP EN Approval Procedure
* EOL ETSI on-line
* EP ETSI Project
* EPP ETSI Partnership Project
* ES ETSI Standard
* ETSI European Telecommunications Standards Institute
* EWP ETSI Work Programme
* FRAND Fair Reasonable and Non-Discriminatory
* GA General Assembly
* GR Group Report
* GS Group Specification
* ICT RP ICT Standardisation Rolling Plan
* IPR Intellectual Property Right
* ISG Industry Specification Group
* LOI Letter of Intent
* LS Liaison Statement
* MOU Memorandum of Understanding
* NSBG National Standardisation Bodies Group
* NSOG National Standards Organisations Group
* NWI New Work Item
* OCG Operational Co-ordination Group
* OPS ETSI Operations Division
* PAS Publicly Available Specification
* PEP Partnership Engagement Process
* RoP ETSI Rules of Procedure
* SC Special Committee
* SDG Software Development Group


HS Harmonised Standard
* SG Steering Group
* SEP Standard Essential Patents
* SNS ETSI Software and Standards team
* SR Special Report
* SRdAP Standardisation Request deliverables Approval Process
* SReq Standardisation Request
* STF Special Task Force
* TB Technical Body
* TG Technical Group
* TC Technical Committee
* TO Technical Officer
* ToR Terms of Reference
* TR Technical Report
* TS Technical Specification
* TTF Testing Task Force
* TWPs Technical Working Procedures


ICT RP ICT Standardisation Rolling Plan
* WG Working Group
* WISR Work Item Standardisation Request


IPR Intellectual Property Right


ISG Industry Specification Group


```
----
LOI Letter of Intent
LS Liaison Statement
MOU Memorandum of Understanding
NSO National Standards Organization
NWI New Work Item
OCG Operational Co-ordination Group
PAS Publicly Available Specification
PEP Partnership Engagement Process
RoP ETSI Rules of Procedure
SC Special Committee
SR Special Report
STF Special Task Force
TB Technical Body
TG Task Group
TC Technical Committee
ToR Terms of Reference
TR Technical Report
TS Technical Specification
TTF Testing Task Force
TWPs Technical Working Procedures
WG Working Group
```


ETSI
ETSI 650, Route des Lucioles 06921 Sophia Antipolis CEDEX, France Tel +33 4 92 94 42 00 [mailto:info@etsi.org info@etsi.org] http://www.etsi.org
650, Route des Lucioles
06921 Sophia Antipolis CEDEX, France
Tel +33 4 92 94 42 00
info@etsi.org
[http://www.etsi.org](http://www.etsi.org)

Latest revision as of 09:05, 2 December 2024

Introduction

The present document endeavours to provide step-by-step guidance for an ETSI Chair on the essential elements, most common practices and responsibilities of the ETSI Technical Groups: Technical Committee (TC), ETSI Project (EP), ETSI Partnership Project (EPP), Special Committee (SC) or Industry Specification Group (ISG), Software Development Group (SDG) and the Operational Coordination Group (OCG).

It has been formatted to be used as a reference guide according to the ETSI Directives (version 49, June 2024). If in any doubt regarding the application of the correct procedures, the ETSI Directives prevail and the ETSI Technical Officer can provide guidance.

The OCG acts as a forum for co-ordination of TCs, ISGs, SDGs, SCs, other Coordination Groups (CGs) and the Secretariat and assists in the resolution in any duplication of effort or conflict of technical views between the Technical Groups.

The scope of this guide does not cover ETSI Partnership Projects (e.g. 3GPP, and oneM2M) or ETSI Projects. It is to be used in conjunction with the ETSI Delegate’s guide and the ETSI Rapporteur’s guide.

Responsibilities of the Chair

The primary duties of a Chair:

  • Ensure an efficient operation of the Technical Group and its Working Groups (in conjunction with the Vice-Chair(s), Working Group (WG) Chair(s) and Vice-Chair(s))
  • Ensure the activities of the Technical Group adhere to the ETSI Directives and its rules, policies and procedures
  • Maintain strict impartiality and act in the interest of ETSI and its members
  • Ensure that the ETSI Guidelines for Antitrust Compliance are strictly observed
  • Inform the Technical Group of the Code of Conduct for ETSI Members
  • Remind the members of the Technical Group of their statutory obligations to submit IPR disclosures
  • Endeavour to reach consensus on all issues, including the approval of draft ETSI deliverables
  • Ensure that the Work Programme is kept up to date
  • Report to the OCG, Board and the General Assembly on the activities of the Technical Group upon request
  • As per Directives v47 (June 2023), a Chair may be appointed for up to three consecutive terms of office (of two years) by the same Technical Group
  • As per Directives v49 (June 2024), the incumbent Chair of a Technical Group or a Software Development Group may be authorised to apply for more than 3 consecutive terms of office under certain conditions.
References: ETSI TWPs Clauses 1.1.2, 1.3.1, 1.3.1.1, 1.3.7, 1.7.1, 3.3, 3.3.1.1, 3.7.1, 7.3.2, 7.3.8 & 7.7.1.

Who is authorised to participate in the activities of an ETSI Technical Group?

Technical Body and Special Committee meetings

To attend a Technical Body (TB) (e.g. a Technical Committee (TC), an ETSI Project (EP)), or a Special Committee (SC) meeting, the delegate shall fulfil one of the following criteria:

  • Represent an ETSI Full or Associate member or Counsellor
  • Represent an Applicant for Full or Associate membership who has formally submitted their application to the ETSI Secretariat (Applicant member), subject to the agreement of the ETSI Director-General
  • Represent an ETSI Partner organisation where ETSI has a signed partnership agreement (according to the rules of the relevant agreement). (For further information on the 3 types of partnerships, see the External Cooperation with ETSI Partners section of this guide.)
  • Attend as a Guest (non-member or ETSI Observer) following authorisation by the Chair for three TB/SC meetings or six months (whichever is the shorter)
  • Represent an Association which is a Full or Associate member, as an employee or as an elected official. A maximum of one nominated technical expert, from the member of the said Association, shall be allowed to attend a meeting, unless explicitly authorised by the Director-General on a case-by-case basis. Technical experts of an Association attending ETSI meetings shall only represent that Association’s views.
  • Represent the European Commission (EC) or the European Free Trade Association (EFTA) as a Counsellor.
  • The above points also apply to Working Groups and Task Groups.

ETSI Observers and Guests may present a document for information and answer questions related to the information provided in their document, if authorised by the Chair.

ETSI Observers and Guests are not permitted to:

  • submit written contributions for discussion or decision
  • contribute in any way to the work on the deliverables, Change Requests and/or Work Item of the respective TB
  • vote or have the possibility to take part in any decision-making process
  • subscribe to a TB mailing list or receive any working document, either during the meeting itself or between meetings, or hold any leadership position.
References: ETSI RoP Articles 1.2.2, 1.2.3, 1.2.4, 1.3 and 1.5, ETSI TWPs Clauses 1.4 and 1.8.1.

TB/SC membership list

Each TB/SC has an email exploder list to be used for discussion, dissemination and/or collection of information and for decision-making purposes outside of TB/SC meetings. Only delegates subscribed to the TB/SC membership list with their EOL account email address are considered members of the TB/SC.

Upon registration to a TB/SC meeting, each delegate (ETSI Full or Associate member or Counsellor) will be automatically subscribed to the TB/SC membership list if not already subscribed.

Email exploder lists are also maintained for WGs (Working Groups), TGs (Task Groups) and SCs.

Authorised Guests attending a TB/SC meeting shall not be subscribed to the membership list.

A representative of an ETSI Partner organisation where ETSI has a signed partnership agreement may be subscribed according to the rules of the relevant agreement. 

References: ETSI TWPs Clauses 1.5.4 and 1.5.5

Industry Specification Group meetings

Representatives of an ETSI Full or Associate member, an ETSI Full or Associate Applicant member and an ETSI Partner are authorised to attend ISG meetings.

Representatives of a non-ETSI member (known as ISG Participant) may attend ISG meetings providing ETSI is in receipt of the signed relevant ISG Participant Agreement. Meeting fees are stipulated in the relevant ISG Participant Agreement and shall be paid prior to attendance of a meeting.

ETSI Observer members may attend meetings of an ISG and participate in the work without the right to vote subject to having signed the relevant ISG Participant Agreement.

A Counsellor is not required to sign an ISG agreement to be able to attend an ISG meeting.

For a Guest to attend an ISG meeting on an exceptional and temporary basis, if invited or authorised by the ISG Chair.

ISG Participants, Counsellors and Guests shall not vote, support new work items or hold an ISG leadership position. An ISG Participant may hold a Rapporteur position or a WG Vice-Chair position. 

References: ETSI TWPs Clause 3.4 to 3.4.7, 3.7.2

List of ISG members and Participants

Each ISG has a list of its Members, Participants and Counsellors that is available on the portal General Information page.

ETSI member organisations are automatically added to this list upon registration to the relative ISG meeting.

ISG Participant organisations are added to this list following the signature of the relevant ISG Participant Agreement. European Commission Counsellors are added upon request. 

References: ETSI TWPs Clause 3.5.4, 3.5.5.

Software Development Group meetings

Each Software Development Group has a relative Agreement that sets out the participation rules, budget mechanism, terms for code contribution. The SDG Agreement includes a Corporate Contribution License Agreement (CCLA) aligned with the terms of the Software License chosen for the SDG, which may differ from the ETSI IPR Policy.

An ETSI Full and Associate member, or an applicant to ETSI Full or Associate membership who has signed the relevant SDG Agreement, may participate in the work of an SDG and have a right to vote at Plenary Meeting and Plenary Level. The right to vote at other levels is governed and the Detailed SDG Working Procedures.

An Association which is a Full or Associate member shall be represented by their employees and elected officials. In addition, a maximum of one nominated technical expert, per meeting, shall be allowed to attend and participate and shall come from a member of the said Association, unless explicitly authorised by the Director-General on a case-by-case basis.

If the SDG Terms of Reference indicates that participation of Observer members and/or non-ETSI members is permitted, participation in the technical work of an SDG is permitted, following the signature of the relevant SDG Agreement, and payment of the appropriate Annual Participation Fee.

An ETSI Partner may attend SDG meetings and participate in the work subject to having signed the relevant SDG Agreement and having paid the appropriate Annual Participation Fee.

A Counsellor may participate in technical work of an SDG after signing the relevant SDG Agreement.

The relevant Detailed SDG Working Procedures stipulates the decision-making rights of SDG Participants. 

References: ETSI RoP Articles 1.2.2 to 1.2.4, 1.3 & 1.5; TWPs clause 7.

Meeting responsibilities: preparation, participation, reporting

Introduction

A Technical Group (TG) has the freedom to organise its work according to the needs of the members providing it complies with the ETSI Directives.

For a TG decision-making meeting (e.g. a plenary), the agenda shall be available at least 30 days beforehand.

The ETSI Directives do not make a distinction between different meeting types, although the term “plenary” is used by ETSI TCs, ISGs and SCs.

The ETSI portal Meeting application offers various types of meetings e.g., Plenary, Working Group, Rapporteur, Resolution etc.

The principles of decision-making are based on consensus or vote.

A Technical Group has the right to decide on:

  • number of WGs
  • frequency of meetings
  • organisation of rapporteur’s meetings
  • deadlines for submitting meeting agenda (other than TG decision-making meeting) and other documents for meetings
  • the way WGs and Rapporteur groups report to the TC/ISG/SC meeting, etc.


A non-decision-making meeting of a Technical Group can be used to collect a snapshot of opinions of ETSI members and ISG Participants on a given item or topic.

References: ETSI TWPs Clauses 1.1, 1.3.7, 1.7.1, 3.1 and 3.3.7.

Before a Technical Group meeting

The Chair shall ensure that the meeting invitation with all necessary logistical information and the draft meeting agenda will be available on the ETSI portal and that the TC/ISG/SC membership is notified at least thirty (30) days before a decision-making meeting.

NOTE: The draft agenda for the first meeting of a new TC, SC or an ISG kick-off meeting is announced in a Collective Letter by the Secretariat, with at least thirty (30) days’ notice. It is the responsibility of the ETSI Secretariat or the Chair to disseminate the meeting invitation.

Items for decision shall be included in the agenda such as:

  • New Work Item (NWI) proposals and draft deliverables for approval
  • Any topics in which voting will be required
  • The received Chair/Vice-Chair/WG Chair candidatures and the call for candidate’s contribution.

The following items should also be considered for addition to the agenda, if relevant:

  • Contribution deadline
  • Meeting contributions uploaded (in agenda revisions)
  • Liaisons statements
  • Logistical information
  • Future meeting schedule.
References: ETSI TWPs Clauses 1.5, 1.7.

During a Technical Group meeting

During a TG meeting, the Chair has the following responsibilities:

  • Open the meeting, welcome the delegates, announce any guests or observers
  • Make a call for IPR and a reminder of applicable anti-trust and competition laws (see the section Responsibilities of the Chair on IPR, Antitrust Compliance and Confidentiality of this guide for further details)
  • Remind delegates of the Code of Conduct for ETSI Members
  • Ensure a meeting secretary volunteers to draft the meeting report
  • Present the agenda and seek its approval
  • Report on the TC/SC//ISG work programme status, and make sure it is updated as appropriate
  • Endeavour to reach consensus on all issues
  • Launch, run, and evaluate the results of planned vote(s) (if any)
  • Ensure that all decisions and actions are recorded in the meeting report
  • Ensure that all decisions taken by Remote Consensus since the last meeting are recorded in the meeting report
  • Invite Rapporteurs and Liaison Officers to present their activities since the last meeting
  • Invite WG Chair(s) (if relevant) to present their Progress reports
  • Ensure the presence of each attendee is correctly recorded on the portal.
References: ETSI TWPs 1.7, ETSI RoP Article 11 and ETSI IPR Guide, Clauses 2.3.2 to 2.3.4.

After a Technical Group meeting

Following each meeting a report should be provided within 30 days and shall include:

  • decisions, including the election of officials, approved or withdrawn deliverables, and change request decisions
  • actions
  • key discussion points
  • organisational changes to the structure of the TG
  • call for IPR disclosures
  • the dates and venues of forthcoming meetings
  • Attendee list as an Annex or hyperlink.

If the meeting report is not available within 15 days after the end of the meeting, the Chair is required to provide a list detailing the key decisions and topics.

The full meeting report should be provided within 30 days and requires the approval of the Technical Group.

The Chair is also invited - for purposes of transparency - to update the status of Contributions on the portal. 

References: ETSI IPR Guide Clauses 2.3.2 to 2.3.5, ETSI TWPs 1.9.

Technical Group Open Sessions

A Technical Group may need to organise meetings/calls open to ETSI Members and non-Members. This type of meeting is called an Open Session, more details can be found at portal.etsi.org/TB-SiteMap/OCG/TG-Open-Sessions

The Chair ensures that the TG defines the Open Session scope, content, format, location and date. ETSI Secretariat will coordinate the request.

European Standards and European standardisation deliverables in response to Standardisation Requests (SReqs)

ETSI may elaborate European Standards and European standardisation deliverables (TR, TS, ES or hEN) in response to SReqs to support the European legislation or policies, in accordance with the amended Regulation (EU) No 1025/2012, which is related to Regulation (EU) 2022/2480.

The relevant ETSI Technical Group will engage with the National Standardisation Body Group (NSBG), the National Standardisation Organisation Group (NSOG) and the Annex III organisations throughout the Standardisation Request deliverables Approval Process (SRdAP).

The European Commission consults ETSI during the drafting of a new Standardisation Request (SReq) that it considers may be of interest to ETSI. ETSI engages the appropriate TC or SC along with the National Standards Body Group (NSBG), the National Standards Organisation Group (NSOG) and the Annex III organisations. ETSI consults the ETSI Board as well the Operational Co-ordination Group (OCG) which acts as a forum for co-ordination and consists of all ETSI committee Chairs and Vice-Chairs. The NSBs take all the decisions by vote on the acceptance of SReqs (not the TG).

The TC or SC proposes Work Item(s) identified for a Standardisation Request (WISR), once registered by the TC or SC, and the NSB members vote on the adoption or rejection of each WISR.

Should the TC/SC decide at a later stage to stop a WISR, the ETSI Board is to be consulted before the request to stop the WISR is submitted to an NSBG vote.

References: ETSI RoP Articles 20 & 21, ETSI TWPs 2.2.2, Annexes A.5 and J.

ENAP (EN Approval Procedure)

This section only applies for ENs (European Standards) that are not related to a Standardisation Request. ETSI may elaborate European Standards (ENs) on a proposal from at least four (4) Full and/or Associate members.

These ENs shall be adopted by the eligible National Standards Organisations (NSO) through a Public Enquiry and at least one Weighted National Voting procedure performed in a combined procedure by the eligible members of the National Standards Organizations Group (NSOG).

Participation in the ENAP shall be restricted to the Annex III Organisations and to the NSO Group (NSOG). 

References: ETSI RoP Article 13, ETSI TWPs Clauses 2.2 to 2.2.1.3.

ENAP Resolution meetings

The Chair shall:

  • Schedule a Resolution meeting when the final draft EN has been submitted to the combined Public Enquiry/Weighted National Voting procedure; it should take place within thirty (30) days after its closure
  • Send the invitation to the TB membership list at least thirty (30) days before the meeting
  • Cancel the Resolution meeting if no comments are received during the Public Enquiry or if only editorial comments are received and the vote is successful.
References: ETSI RoP Article 13, ETSI TWPs Clauses 2.2.1.1.1 to 2.2.1.1.3, Annexes A.5, J and T.

Responsibilities of the Chair on IPR, Antitrust Compliance and Confidentiality

General

One of the primary duties of the Chair is to take care that the ETSI Guidelines for Antitrust Compliance are strictly observed.

The Chair has a duty to remind the TB/SC/ISG members of their obligations to submit IPR disclosures.

Responsibilities of the Chair on Intellectual Property Rights (IPR)

At the beginning of a TB/SC/ISG meeting, the Chair shall perform the “Call for IPRs”. An example of a formal call for IPRs, as below:

“The attention of the members of this Technical Body is drawn to the fact that ETSI members shall use reasonable endeavours under Clause 4.1 of the ETSI IPR Policy, Annex 6 of the Rules of Procedure, to inform ETSI of Essential IPRs in a timely fashion. This section covers the obligation to notify its own IPRs but also other companies’ IPRs.

The members take note that they are hereby invited:

·      to investigate in their company whether their company does own IPRs which are, or are likely to become Essential in respect of the work of the Technical Body,

·      to notify to the ETSI Director-General all potential IPRs that their company may own, by means of the IPR Information Statement and the Licensing Declaration forms through the ETSI IPR online database application at https://ipr.etsi.org. Only under exceptional circumstances and if instructed by the ETSI Secretariat, paper declarations may be allowed using the forms provided by the ETSI Secretariat.

Members are encouraged to make general IPR undertakings/declarations that they will make licenses available for all their IPRs under FRAND terms and conditions related to a specific standardization area and then, as soon as feasible, provide (or refine) detailed disclosures”.

The Call for IPRs serves as a reminder of the obligations of TB/SC/ISG members in the disclosure of Essential IPRs in a timely fashion.

Throughout the standardisation process, the Chair shall take the actions as laid down in the sections of the Guide on IPRs, to facilitate the identification of Essential IPRs.

During the meeting a short reminder call for IPR disclosures should be made on:

  • the formal submission of a technical solution
  • the completion of the first stable draft of the standard
  • Working Group approval of a draft standard
  • TB/ISG approval of a draft standard.

The meeting report shall clearly state that an IPR call, and any IPR reminders, has been made as well as any responses. If no responses were given, then also this should be recorded.

The Chair shall inform the ETSI Legal Director of the existence of any Essential or potentially Essential IPR. 

References: Guide on Intellectual Property Rights, Clauses 2.3, 2.3.2-2.3.4.
Rules of Procedure, Annex 6: ETSI Intellectual Property Rights Policy.

Trade names and trademarks

The use of trade names and/or trademarks that are asserted and/or registered by their owners for designating particular products or services should be avoided in ETSI deliverables. Instead a corresponding standard should be used or a correct designation or a generic description should be given.

If, in exceptional circumstances, the use of trademarks/trade names cannot be avoided, the recommendations given on editHelp! website in the "Use and reproduction of text, signs and material legally protected" section should be followed. 

References: ETSI Directives/Drafting Rules Clause 4.2.

Copyrights in ETSI Deliverables

If, in exceptional circumstances, the use of copyrighted third-party material (text/figures) cannot be avoided, reproduction in ETSI deliverables requires the author’s authorisation and the copyrighted material shall be indicated by the symbol © and with proper acknowledgment of its owner.

The Chair should instruct the Rapporteur to obtain the author’s authorisation using the template available from the editHelp web page. 

References: Guide on Intellectual Property Rights, Clause 2.3.5, ETSI Directives/Drafting Rules, Clauses 4.1 & 4.3.

Responsibilities of the Chair on Antitrust Compliance

The Chair should take care that the ETSI Guidelines for Antitrust Compliance are strictly observed, as per the Anti-trust and competition Statement at the beginning of a TB/SC/ISG meeting:

“The attention of the members of this Technical Body/ISG is drawn to the fact that ETSI activities are subject to all applicable antitrust and competition laws and that compliance with said laws is therefore required of any participant of this meeting including the Chair and Vice Chair(s). The leadership shall conduct the present meeting with impartiality. In case of questions, it is recommended that you contact your legal counsel”.

The Chair shall not allow any discussion on commercial issues, in particular but not limited to, discussions on details of specific licensing terms and conditions, and any subject matter prohibited by competition law. It includes any discussions, communications or any other exchange of information, inside or outside of all ETSI meetings (e.g. informal discussions, social gatherings, corridor talks).

References: Guide on Intellectual Property Rights, Clause 2.3, Guidelines for Antitrust Compliance Clause C.4.1.

Responsibilities of the Chair on Confidentiality

All documents and information provided in or for technical meetings shall be considered non-confidential unless the information (in written form AND is identified AND accepted by the Chair) has been labelled as confidential.

Confidential information that has been incorporated in a Standard or Technical Specification shall be regarded as non-confidential from the moment of publication.

Should the Chair become aware that confidential information has been disclosed in breach of a confidential disclosure agreement to which ETSI is a party, the Chair shall immediately inform the Secretariat.

Decision Making and Voting

Consensus and consensus-making

Formal standardisation is a process which is open to any individual or organisation (member/participant/counsellor), and its results are produced in consensus with all interested parties.  

Formal standardisation is inspired by international directives on standardisation, and is based on six principles for the development of international standards:  

  • transparency,  
  • openness,  
  • impartiality and consensus,  
  • effectiveness and relevance,  
  • coherence, and  
  • development dimension.  

Within Europe, Regulation (EU) 1025/2012 – “the Standardisation Regulation” - places an added emphasis on facilitating the participation of all stakeholders in the standardisation process.

Standards are, therefore, products of negotiation among all involved (and relevant) stakeholders, aimed at establishing a general agreement and the absence of sustained opposition.

With respect to the consensus-making process in ETSI, the Chair shall apply the definition of consensus:

A general agreement, characterised by the absence of sustained opposition to substantial issues by any important part of the concerned interest and by a process that involves seeking to take into account the views of all parties concerned and to reconcile any conflicting arguments.

NOTE: Consensus need not imply unanimity.

A Technical Group shall endeavour to reach consensus on all issues both during a meeting, and/or in between meetings via the Remote Consensus portal application.

The Chair (or Vice-chair or Rapporteur) should aim to facilitate the discussion in an independent manner, considering:

  • The objective is to obtain the largest consensus possible on the content of the standard and resolve potential conflicts.
  • Reaching consensus may take time, taking into account there are different stakeholders represented in a TG.
  • Different knowledge domains and backgrounds across committees may imply different "languages and cultures".
  • In the case of sustained opposition, this opposition shall be made known before approval (verbally or in writing) and shall be recorded in the meeting report(s).

If consensus cannot be achieved, the Chair may decide to take a vote which may be performed by a secret ballot either during a meeting or in between meetings. Before the vote, the TB/ISG/SDG/SC Chair shall provide a clear definition of the issues (e.g., TB/ISG/SC approval of a draft before publication).

Contributions for Decision by Consensus in between meetings shall use the ETSI Remote Consensus tool. Those contributions shall be available at least seven (7) calendar days before the Remote Consensus starts and the minimum duration of the Remote Consensus is at seven (7) days. The Technical Group is to be informed of the results of the Decision within seven (7) calendar days and recorded in the meeting report of the following meeting.

References: ETSI TWPs, 1.7, 3.7.7 and RoP Annex 1.

Technical Group vote during a meeting

  • Electronic voting is recommended.
  • A vote shall be announced to the membership list at least 30 calendar days before the start of the voting period.
  • Only members who have registered to the meeting and are present (physically or remotely connected) may vote. For a TC, weighted voting applies.
  • All ISG Members are eligible to vote after the kick-off period. ISG voting rules are detailed in the ISG ToR Annex or in the ETSI Directives.
  • Voting by proxy is not permitted.
  • A Proposal shall be deemed approved if seventy-one percent (71%) of the votes cast are in favour. If a 71% is not achieved the vote shall be re-calculated using the votes of Full members only.
  • In the case of an ISG, only Founding Members (as identified in Annex 2 of the ISG agreement) are eligible to vote during the kick-off period. Thereafter, all ISG Members are eligible to vote.
  • ISGs may have specific voting rules, as defined in the ISG Member agreement (e.g., non-weighted vote, simple majority voting, voting based on presence to previous ISG meetings).
  • Voting by proxy is not permitted.
  • The result of the vote shall be recorded in the meeting report.
References: ETSI TWPs Clauses 1.5.4, 1.7.1, 1.7.1.1, 3.7.1-3.7.5.

Technical Group vote by correspondence in between meetings

  • Electronic voting shall be used.
  • Only delegates subscribed to the TB/ISG/SC membership list with their EOL account email address will be considered members of the Technical Group.
  • The contribution submitted to the vote shall be announced to the membership list at least seven (7) calendar days before the start of the voting period.
  • The voting period shall be at least two (2) calendar days.
  • Only members who have registered to the meeting and are connected online may vote. For a TC, weighted voting applies.
  • All ISG Members are eligible to vote after the kick-off period. ISG voting rules are detailed in the ISG ToR Annex or in the ETSI Directives.
  • A proposal shall be deemed approved if seventy-one percent (71%) of the votes cast are in favour. If a 71% is not achieved the vote shall be re-calculated using the votes of Full members only. The rule may be different for ISGs, to be checked in the ISG ToR Annex or in the ETSI Directives.
  • The Technical Group has to be informed of the results of the vote within seven (7) calendar days and recorded in the meeting report of the following meeting.
  • The result of the vote shall be disseminated by the Chair to the membership list within seven (7) calendar days and recorded as a decision taken by correspondence in the report of the following meeting.
References: ETSI TWPs, Clauses 1.5.5, 1.7.1.2, 1.7.1.3, 3.5.5, 3.7.1 to 3.7.4, 3.7.6

Appointment for the position of Chair/Vice-Chair or WG Chair

General

In the case where there is more than one candidate for the position of Chair/Vice-Chair/WG Chair, a secret ballot shall be used.

If no candidate is elected after a first vote, a second or third ballot may be required.

In the case when there is only one candidate for a Chair/Vice-Chair/WG Chair position, appointment by consensus is required which can take place during a meeting, or in between meetings using the Remote Consensus tool.

The procedures for the election of a TB/SC Chair/Vice-Chair/WG Chair described in TWPs, Clauses 1.3.1.1 and 1.3.1.2 shall apply.

The procedures for the election of an ISG Chair/Vice-Chair/WG Chair described in TWPs, Clauses 3.3.1.1 and 3.3.1.2 shall apply.

The Chair of an ISG shall be a delegate of an ISG Member organisation with the status of Full or Associate member.

In the event of a change in the supporting organisation of an ISG Chair, the move should be included in the minutes of the next ISG meeting. If no ISG meeting is planned in the immediate future, the ISG is to be informed by email.

The procedures for the election of an SDG Chair/Vice-Chair/WG Chair described in TWPs, Clauses 7.3.2.1 and 7.3.2.2 shall apply.

External cooperation with ETSI Partners

Overview of partnership agreements

When there is a need for the establishment of a partnership agreement, the Technical Group is advised to consult the ETSI partnership policy framework and the Partnership Engagement Process (PEP). The Chair will be accompanied by the ETSI Secretariat in the establishment process.

The Chair should be aware of all relevant partnership engagements with other organisations and the Technical Group abides by the partnership engagements.

There are three different types of partnership agreements depending on partnership engagement:

Engagement Main Focus ETSI TWPs
Clauses 		Examples, comments
Type 1
Letter of Intent (LoI) 		First step towards formalising contacts with a new partner. 1.8.1.1.1

Type 2
Memorandum of Understanding
(MoU)
[Partner shall be a legal entity]

- Political
- Marketing
- Technical

Establishment of a framework enabling exchange of information on technical grounds and identification of areas of mutual interest. 1.8.1.1.2

Type 3
Co-operation Agreement (CA)

[Partner shall be a legal entity and an IPR Policy Check performed to determine the compatibility of the Partner’s IPR Policy with ETSI’s]

- Political
- Marketing
- Technical

 Enabling technical collaboration with the possibility of Supplements to a CA.
1.8.1.1.3 		ESOs. A synthetic view of each mode is available in TWPs, Annex P. (https://portal.etsi.org/Resources/ETSI-Directives)
- [PAS Process Guide](https://etsi.org/images/files/ETSI_PAS_Process_Guide.pdf)
- [PAS brochure](https://www.etsi.org/images/files/Brochures/ETSI-Brochure-PAS.pdf)
Supplements 1.8.1.2
Materials Supplement
- Incorporation of published text and graphics from the other party into a document.
1.8.1.2.1
Working Supplement
- Joint production of deliverables. 		1.8.1.2.2
PAS Supplement
- Adoption of identified Partner’s PASs into ETSI TR(s) or TS(s).
1.8.1.2.3

ETSI Cooperation Agreements and Supplements

General Information

Only a Cooperation Agreement can include a PAS (Publicly Available Specification) Supplement, a Working Supplement or a Materials Supplement for the following purposes:

  • PAS Supplement enables the ETSI Partner to submit its publicly available specifications to ETSI for adoption into an ETSI TR or TS.
  • Working Supplement allows for the creation of a joint document.
  • Materials Supplement allows for incorporation of text and graphics from the ETSI Partner into an ETSI document.

PAS (Publicly Available Specification) Process

An ETSI Partner who has signed a Cooperation Agreement and a PAS Supplement can submit its publicly available specifications to ETSI.

The ETSI Partner submits the specification and the PAS work item form to the Board which allocates them to a Technical Group, in coordination with the OCG. The Technical Group shall create the corresponding PAS Work Item immediately after the Board allocation decision, before starting any work.

The Technical Group will conduct the PAS review and will approve the PAS as a TR or TS following the normal ETSI approval procedure.

A PAS Process Guide is available for download describing the process and its benefits.

Participation of an ETSI Partner representative in ETSI meetings

Partnership agreements may allow for cooperative interworking between ETSI Technical Groups and the Partner, and the attendance of a Partner representative per meeting. This attendance rule also applies to ETSI’s participation in the Partner organisation. This has to be carefully checked for each agreement.

The ETSI Partnership portfolio and the description of the Partnership Engagement Process are available for consultation.

Detailed information on Basic Co-operation Agreement between CEN, CENELEC and ETSI and the description of the 5 modes of cooperation is available in the TWPs, Annex P.

A full overview of the ETSI Partnership Engagements can be found in the TWPs, Annex R.

Liaison Statements when there is no Partnership Agreement

Exchange of liaison statements between ETSI Technical Groups and external bodies are to be encouraged as a first step.

If such liaisons reach the point where the two bodies concerned are going to exchange technical documents, then the need for a formal Partnership Agreement should be investigated.

A joint meeting with an organisation that has no Partnership Agreement with ETSI

An ETSI Technical Group (TG) can hold joint meetings with an organisation that has no Partnership Agreement with ETSI. This may happen when the ETSI TG and the other organisation identify a potential future collaboration, before the need for a formal partnership.

The joint meeting, set up as an Open Session, as previously described in this guide, may contain technical discussions, but shall not be used for the approval of drafts or decisions aiming at modifying drafts. No TG working draft can be discussed unless it is publicly available. Therefore, a set of basic rules and principles must be followed to comply with the ETSI TWPs and to remain in a safe zone from the legal standpoint.

Cooperation between ETSI Technical Groups

An ETSI Chair should pay special attention to the rules for cooperation between TBs, SCs and ISGs as detailed in the table below:

Cooperation between TBs and ISGs Type of cooperation
Between TBs/SCs - Liaison officer
- Liaison statement
- Joint meeting(s)
TBs/SCs with ISGs
Between ISGs 		- Liaison officer from one ISG or TB/SC can attend another ISG meeting only if the organisation of the Liaison officer has signed the ISG agreement

- Only working drafts available in the Open Area may be exchanged

Between ISGs - Liaison statements

- Joint meeting – see section Open Session

- Only working drafts available in the Open Area may be exchanged

Chair’s Responsibilities – Operational Coordination Group (OCG)

General

The Operational Coordination Group (OCG) acts as a focal point and a forum for co-ordination of and between the Technical Bodies (Technical Committees (TCs), ETSI Projects (EPs), Industry Specification Groups (ISGs), Software Development Groups (SDGs) and Coordination Groups (CGs), and between the TBs, ISGs, SDGs, CGs and the Secretariat.

The OCG provides an opportunity for Chairs and ETSI representatives to CGs to exchange information and experiences, to discuss any issues prior to formal resolution of substantial objections in the Board and respond to Board requests for information.

The OCG shall resolve, as far as possible, any duplication of effort or conflict of technical views between the TBs/ISGs to reinforce co-operation between the Technical Organisation, the ISGs and the CGs.

A Chair will be periodically requested to report to the OCG and the Board on the progress, topics for decision and any issues. 

References: ETSI TWP Clauses 4 & 5

STF/TTF Management and Chair’s responsibilities

An active contribution of the Technical Group (TG) Chair is required in the phases listed below:

Drafting the STF/TTF Terms of Reference

The Chair makes sure that a new Special Task Force or Testing Task Force (STF/TTF) proposal, including the related Work Items, is supported by at least four (4) ETSI members and approved by the Technical Group, irrespective of the funding source.

STF/TTF Work plan

The work plan included in the STF/TTF Terms of Reference (ToR) is established by the TG Chair, in consultation with the ETSI Secretariat.

Submission of STF/TTF proposal funded by ETSI (Funded Work Programme)

ETSI Secretariat notifies the OCG biannually with the allocation process and calendar.

STF proposals under the ETSI budget can be submitted in the two allocation steps, in quarter three for (Y+1), and in quarter two (Y) (depending on the ETSI budget contingency, and for urgent requests only).

Submission of STF proposal funded by EC/EFTA

First, the ETSI Secretariat notifies the OCG of the EC schedule and process for the submission of:

  • Spontaneous STF proposals for a first assessment by the EC, with the required EC technical proposal template (twice a year)
  • Opening of European Innovation Council and SMEs Executive Agency (EISMEA) calls (e.g. 3 times a year).

Secondly, the ETSI Secretariat informs the OCG of each EISMEA call of:

  • Topics selected by the EC
  • Deadline for EISMEA proposal submissions
  • Required EISMEA template.

Then, EISMEA evaluates the relevance, quality and impact of the STF proposal. For each criterion there is a threshold which shall be met to receive a positive assessment from EISMEA. If the assessment is positive, ETSI Secretariat and EC/EFTA finalise the process and the STF may begin.

Submission of TTF proposal

TTF proposals are under the ETSI budget and can be submitted by the end of summer (e.g. 2 weeks before the ETSI September Board meeting). An email is sent biannually to the OCG by the CTI Director with the allocation process and calendar.

The Technical Group Chair is to liaise with the CTI Director at each step of the TTF proposal submission.

The initial TTF ToR (at least the Part 1) should be sent to the CTI Director before the date indicated in the TTF Process Calendar, so it can be incorporated into the following year’s Technical Roadmap.

The CTI Director presents and justifies the full TTF Roadmap  at the September Board/OCG meeting.

If the TTF is approved, the TTF ToR Part 2 and the corresponding work items have to be approved by the Technical Group, before starting the call for experts’ process.

Recruitment of the STF/TTF experts

Applications from ETSI members active in the Technical Group are encouraged.

The ETSI Secretariat (Technical Officer (TO) and Head of Funded Activities) and the Chair should assess the applications and draw up a short list of candidates. In the case of TTFs, the CTI Director must be represented as well.

To avoid a conflict of interest in the selection of service providers, the Reference Body Chair/Vice-Chair(s) and/or the Chair of the Working Group directly concerned by the STF/TTF activity and who belong to an organisation that has an interest in applying for selection as a service provider to a funded STF/TTF, shall declare this to the Board and subsequently be excluded from all discussions and decisions related to the selection of the service providers.

STF/TTF Preparatory Meeting (Experts’ interview)

The TG Chair should attend the preparatory meeting with the selected experts, decide on the draft Work Plan and allocation of resources and check the Milestones. This should be done in coordination with the ETSI Head of Funded Activities and the TO and, in the case of a TTF, the CTI Director.

Monitoring STF/TTF progress

The Chair is expected to provide technical guidance. The STF/TTF leader is appointed by the Director-General (DG) in consultation with the relevant TG Chair. The STF/TTF leader acts as the interface with the DG for management of the STF/TTF, with the service provider(s) for coordination of the project and with the TG Chair for technical control. It is recommended that a Steering Group (SG) is set up, its main role is to provide technical support input and guidance during the lifecycle of the STF/TTF. It is essential to ensure the timely approval of the STF/TTF deliverables by the TG.

STF/TTF Reporting

The Reference Body approves the STF/TTF Progress Reports which confirm the achievement of the intermediate milestones against which the experts’ companies will be paid by the ETSI Director-General.

Closing the STF/TTF

When the Final STF/TTF report is approved by the Reference Body, feedback is given to the Head of Funded Activities, and the CTI Director in case of a TTF, and the STF/TTF is closed. 

References: TWPs 1.10.1 to 1.10.9, Annex H, ETSI STF/TTF Expert’s Guide.

EC/EFTA cooperation and Chair's responsibilities

The ETSI Director-General (or a nominated substitute) represents ETSI within the relevant committees of the EC and EFTA concerning advisory or regulatory standardisation issues.

The TB/SC/ISG Chair should be aware of all the relevant communications between ETSI and the EC. The TB/SC/ISG Chair should also consider/verify relevant contributions of the TB/ISG to EC/EFTA Annual Union Work Programme (AUWP), the Rolling Plan for ICT Standardisation (ICT RP) and any other EU policy, when requested by ETSI Secretariat, e.g. twice a year.

The ICT RP is a bottom-up approach: the standardisation community (not only ETSI), represented in the Multi-Stakeholder Platform (MSP), provides a programme of standards or other deliverables in support of EU policy objectives. It gives an overview of ongoing standardisation work, e.g. needs and gaps. ETSI as a member of the Multi-Stakeholder Platform (MSP) is included in the MSP consultation.

Standardisation actions identified in Rolling plan for ICT Standardisation are complementary to other instruments, in particular the Annual Union Work Programme (AUWP).

The AUWP is a top-down approach from the EC and reflects EC expectations, e.g. Standardisation Requests (SReqs). The main goal of contributing to the AUWP is to indicate what needs to be mandated by the EC for ESOs (AUWP targets ESOs only). The AUWP is adopted after having conducted EC consultation with relevant stakeholders: ESOs, Member States and Annex III organisations (see Regulation 1025/2012). In many cases, a pre-condition for a Standardisation Request is an item in the AUWP. On the other hand, the AUWP is not binding for the EC.

The ETSI Secretariat coordinates the response to the AUWP, the ICT RP and any other EU policy. Information is shared among the ETSI members through the ETSI OCG and relevant ETSI BOARD meetings. 

References: 
AUWP: https://ec.europa.eu/growth/single-market/european-standards/notification-system_en
ICT RP:https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/

ETSI working tools and services

ETSI offers a set of electronic means to work and collaborate via the ETSI portal for which an ETSI on-line (EOL) account (username and password) is required.

Guidance on how to use these electronic tools is available from the portal wiki help pages including FAQs. Some examples of ETSI tools and services:

  • Membership/Exploder Lists
  • The ETSI Work Programme (EWP) enables to search the TB/SC/SDG/ISG work programme and download ETSI working drafts/publications.
  • Meetings management and contributions handling
  • Remote Consensus is the ETSI online tool to collect comments and measure consensus for contributions.
  • The TB Decision Support application includes several types of formal Voting procedures (as opposed to consensus gathering) which are predefined e.g. vote for the approval of a draft, selecting a technology and electing officials.
  • The e-Approval application is the means for voting on SRdAP topics, draft ETSI Standards, ETSI Guides, ETSI European Standards and ETSI Harmonised European Standards. The consultation of comments and/or results of votes on such documents is also possible.

ETSI Secretariat Contacts

The Chair is encouraged to contact the ETSI TO with regards to requests involving ETSI Secretariat services, as detailed in the table below.

Secretariat team Role Web page
Committee Support Staff Standards Development Centre (SDC) Secretariat support to the technical organisation and Standardisation Requests coordination. https://portal.etsi.org/People/Commitee-Support-Staff Contacts:

ESPsupport@etsi.org;

ISGsupport@etsi.org;

SRteam@etsi.org

Centre for Testing and Interoperability (CTI) Support of the validation of base standards and the development of test specifications. https://portal.etsi.org/Services/Centre-for-Testing-Interoperability/

Contact: CTI_support@etsi.org

Software and Standards (SNS) Secretariat support to software development groups. Contact: SDGsupport@etsi.org
editHelp! Support and guidance for the drafting and finalisation of ETSI deliverables. https://portal.etsi.org/Services/editHelp

Contact: editHelp@etsi.org

IT Helpdesk Assistance for technical issues on ETSI Portal, EOL accounts, etc. Contact: helpdesk@etsi.org
Membership Advise on membership categories, application process, fees.

Liaison with the Official member contact.

https://www.etsi.org/membership

Contact: membership@etsi.org

 Funded Activities  Support to STFs, TTFs, Plugtests™ and Special Projects. https://portal.etsi.org/STF/STFs/Summary  

Contact: stflink@etsi.org

Communications Management of the ETSI website, social media, press releases, webinars, blogposts, brochures, leaflets and the Enjoy! magazine.

Management of the finalisation and publication of White Papers, not under the control of ETSI.

https://www.etsi.org/newsroom

Contacts: COM@etsi.org; info@etsi.org

Events Management of the endorsements of events (seminars, plugtests, webinars) and negotiation of special conference rates (speaking slots and stands).

Organisation and promotion of ETSI workshops.

https://www.etsi.org/events

Contact: events@etsi.org

Legal Responsible for the IPR Policy and IPR Guide, disclosure of Standard Essential Patents (SEP), and ownership of ETSI Copyright and Trademarks.

Provision of legal advice upon request.

https://www.etsi.org/about/legal

Contact: legal@etsi.org

Partnerships Development and maintenance of the ETSI partnership portfolio, interaction with the National Standards Organisations (NSOs) https://www.etsi.org/about/our-partnerships

Contact: partnerships@etsi.org

Annex 1 - Abbreviations

For the purposes of the present document, the following abbreviations apply:

  • AUWP Annual Union Work Programme
  • CA Co-operation Agreement
  • CG Coordination Group
  • CTI ETSI Centre for Testing and Interoperability team
  • DG ETSI Director General
  • EC European Commission
  • EDRs ETSI Drafting Rules
  • EG ETSI Guide
  • EFTA European Free Trade Association
  • EISMEA European Innovation Council and SMEs Executive Agency
  • EN European Standard
  • ENAP EN Approval Procedure
  • EOL ETSI on-line
  • EP ETSI Project
  • EPP ETSI Partnership Project
  • ES ETSI Standard
  • ETSI European Telecommunications Standards Institute
  • EWP ETSI Work Programme
  • FRAND Fair Reasonable and Non-Discriminatory
  • GA General Assembly
  • GR Group Report
  • GS Group Specification
  • ICT RP ICT Standardisation Rolling Plan
  • IPR Intellectual Property Right
  • ISG Industry Specification Group
  • LOI Letter of Intent
  • LS Liaison Statement
  • MOU Memorandum of Understanding
  • NSBG National Standardisation Bodies Group
  • NSOG National Standards Organisations Group
  • NWI New Work Item
  • OCG Operational Co-ordination Group
  • OPS ETSI Operations Division
  • PAS Publicly Available Specification
  • PEP Partnership Engagement Process
  • RoP ETSI Rules of Procedure
  • SC Special Committee
  • SDG Software Development Group
  • SG Steering Group
  • SEP Standard Essential Patents
  • SNS ETSI Software and Standards team
  • SR Special Report
  • SRdAP Standardisation Request deliverables Approval Process
  • SReq Standardisation Request
  • STF Special Task Force
  • TB Technical Body
  • TG Technical Group
  • TC Technical Committee
  • TO Technical Officer
  • ToR Terms of Reference
  • TR Technical Report
  • TS Technical Specification
  • TTF Testing Task Force
  • TWPs Technical Working Procedures
  • WG Working Group
  • WISR Work Item Standardisation Request


ETSI 650, Route des Lucioles 06921 Sophia Antipolis CEDEX, France Tel +33 4 92 94 42 00 info@etsi.org http://www.etsi.org
Retrieved from ‘https://ocgwiki.etsi.org/index.php?title=Chair%27s_Guide&oldid=488’