1. Scope of Community IRP :
a. Propose draft wording for Board suggestion (also mentioned by RySG) to develop an exception process, similar to the PDP carve-out, whereby the impacted part of the community would have a required voice in the support to
the decision to initiate a community IRP (ie, gNSO required if the decision is a gNSO policy action or inaction, etc.) (see page 23 – para 70)
i. A specific provision will be included in the Bylaws to require specific SO or AC concurrence in support of community IRP
challenge against Board decisions that relate directly to certain SOs, such as Policy Development Process outcomes.
b. In light of this carveout, keep current level of required support for Community IRP (3 SO/ACs in support; 1 objection)
c. Align position with Rec #7 discussion on Expert panels : IRP scope is focused on assessing whether decisions are compliant with the Bylaws
2. Separation process (page 24):
a. Confirmed Icann Board suggestion to clarify that Separation process applies to domain name management function to IANA only
b. Insert CWG conditions from their comment:
i. The right to reject Board decisions Icann Board decisions relating to reviews of IANA Functions can be applied by the Empowered Community an unlimited number of times.
ii. The relevant Icann Bylaw drafting process and related Separation process will continue to include involvement by the CWG-Stewardship.