[Gnso-epdp-team] EPDP Review of Public Comment

Hadia Abdelsalam Mokhtar EL miniawi Hadia at tra.gov.eg
Mon Jan 7 09:48:34 UTC 2019


Stephanie, I have three points with regard to the issue that you raised concerning the alternates; first according to the charter the EPDP team structure does not include a type of participation that we could refer to as  "full member" , which you mention in your email, the charter only has members, alternates, liaisons and observers in addition to the leadership team. Second according to the charter "Alternates will only participate if a Member is not available," that is, when a member is not available he/she will be replaced by an alternate, in such case the alternate will act as a member. Third since in the third small team no member will be available from the groups that only have two members, then inline with the charter an alternate could step in and participate as a member. To conclude  if in any of the small teams a member is not available, according to the charter an alternate could step in and anytime the alternate steps in he/she will act and be treated as a member. Finally it is up to the NCSG to decide if they would like to proceed with the suggested working method.

Kind Regards
Hadia
________________________________________
From: Gnso-epdp-team <gnso-epdp-team-bounces at icann.org> on behalf of Kurt Pritz <kurt at kjpritz.com>
Sent: 06 January 2019 23:57
To: Mueller, Milton L
Cc: GNSO EPDP
Subject: Re: [Gnso-epdp-team] EPDP Review of Public Comment

Milton:

I understand perfectly well. I was involved in the discussion that resulted in the current GNSO configuration.

In my email, I used stakeholder with a small ¡°s,¡± I was not referring to or making a distinction between ICANN-defined groupings. Rather, I was segregating the groups participating in the EPDP by interest.

I would not presume that an ISPCP member would have or could represent the same interests as a member of the Intellectual Property Constituency in a small group. Same with Business and IP, same with registries and registrars. (Constituencies are a natural division by interest. Stakeholder Groups and ¡°Houses¡± are ICANN artifices )

Therefore, I could not ask the IPC, for example, to not have their interests represented in a small team. That would necessitate the sort of re-litigation at the plenary level to which you referred in your earlier email and defeat the purpose of forming the small group in the first place.

In an effort to provide an improved opportunity to meet our deadlines, I suggested that we form small groups where every interest could be represented. Recognizing that the current configuration hamstrings that ability, I responded to Ayden with a request that the NCSG assent to that approach.

Kurt



> On Jan 5, 2019, at 8:45 PM, Mueller, Milton L <milton at gatech.edu> wrote:
>
> Kurt
> Seems you didn¡¯t understand Ayden¡¯s point. I¡¯ll be more direct.
>
> Please stop confusing constituencies with SGs. Constituencies are subunits of SGs. Representation (in the council and on ePDP) is based on SGs not constituencies. So are consensus calls, which is why you need to get this straight.
>
> BC and IPC are two of the three constituencies in the CSG. The other is the ISPC. Each has a seat on the ePDP. Thus, with 3 CSG members of the ePDP the CSG can cover all three small groups. Or with 1 rep and one alternate they could have two, in which case the NCSG would expect to also have two.
>
> Is that clear now? I¡¯d appreciate it if you could confirm your understanding of this.
>
> Milton L Mueller
> Professor, School of Public Policy
> Georgia Institute of Technology
>
>> On Jan 5, 2019, at 19:51, Kurt Pritz <kurt at kjpritz.com> wrote:
>>
>> Hi Ayden:
>>
>> That is the rub isn¡¯t it?
>>
>> I made this recommendation because I believe that we should take every measure, explore every option to expedite our work. There is so much work left. The increase to three groups increases our capacity by half again. I think we have demonstrated that smaller groups work more efficiently, so dividing into three groups (rather than two larger ones) will increase our capacity even more.
>>
>> One assumption I made was that I don¡¯t think we can create small teams without representation from each stakeholder group. Without the representation by each group, it is much more likely that each group determination would have to be re-discussed at the plenary level and any time saving would be lost. Therefore, if we do not include alternates, that would restrict us to two groups.
>>
>> I think the bottom line is that with three groups, we have some chance of getting through a set of public comment in a timely manner; with two groups, I see no chance. In three small groups, each stakeholder group will have one representative, and the NCSG will have two. This is different than the original ratios as allocated by the GNSO Council.
>>
>> I don¡¯t know if it is within my remit as chair to require this use of alternates in the name of acheiving our objectives. One remedy would be to ask the GNSO Council for their guidance but we all doubt that could be received in time for meetings in three days' time.
>>
>> I prefer to leave it to your stakeholder group.
>>
>> It is my request that the NCSG approve this approach.
>>
>> Let me know your position on it.
>>
>> Thanks and best regards,
>>
>> Kurt
>>
>>
>>> On Jan 5, 2019, at 3:05 AM, Ayden F¨¦rdeline <icann at ferdeline.com> wrote:
>>>
>>> Hi Kurt,
>>>
>>> Thank you for putting forward this proposal.
>>>
>>> I do not wish to split hairs, but on page three of your proposal, the table lists 'Stakeholder Groups' and then lists the BC, IPC, and ISPSC (sic), who are GNSO Constituencies. The NCSG is correctly listed as a Stakeholder Group. Yet your approach would give the NCSG three members and the CSG nine members in the process which follows.
>>>
>>> As you may remember, when chartering this working group the GNSO Council went to great efforts to ensure the membership composition of the various Stakeholder Groups and Constituencies was balanced. I believe strongly that we must preserve this balance, even in the small teams, and for that reason I also object to the first ground rule which would see certain interest groups able to bring in an alternate in addition to their members to participate in this process. This disrupts the careful balance in membership composition that has guided our work to date.
>>>
>>> I ask, and hope, that this can be revised. Thanks!
>>>
>>> Best wishes,
>>>
>>> Ayden
>>>
>>> ©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\
>>>> On Friday, January 4, 2019 11:04 PM, Kurt Pritz <kurt at kjpritz.com> wrote:
>>>>
>>>> Hi Everyone:
>>>>
>>>> The Support team has reflected on the progress in the last meeting and the amount of work before us. I have attached a plan for reviewing the public comment that would be put in place as early as Tuesday. This will require some reflection and response on your part over the weekend - mainly to review the attached and signal agreement or suggestion for amendment. This is a significant departure from our usual operating mode but, I believe is necessary.
>>>>
>>>> This recommendation provides a process but not a methodology or standard of review for the comments. Clearly, some standard is required to make our review more objective and efficient. I found Mark¡¯s emailed suggestion helpful on this. We will continue analyze different possibilities over the weekend and would appreciate any recommendation from the team.
>>>>
>>>> Let me know your thoughts. There will be additional followups in the very near future.
>>>>
>>>> Thanks and best regards,
>>>>
>>>> Kurt
>>>>
>>>> Gnso-epdp-team mailing list
>>>> Gnso-epdp-team at icann.org
>>>> https://mm.icann.org/mailman/listinfo/gnso-epdp-team
>>>
>>>
>>
>> _______________________________________________
>> Gnso-epdp-team mailing list
>> Gnso-epdp-team at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-epdp-team

_______________________________________________
Gnso-epdp-team mailing list
Gnso-epdp-team at icann.org
https://mm.icann.org/mailman/listinfo/gnso-epdp-team


More information about the Gnso-epdp-team mailing list