- CWG-Stewardship - lists.icann.org

Next CWG-IANA meeting - 28 July @ 14:00 UTC
by Yuko Green July 21, 2016

July 21, 2016

Dear members of the CWG, Per chairs, I am confirming that the next CWG-IANA meeting will be on Thursday, 28 July, at 14:00 UTC. You should have received the meeting invitation some time ago, and there will be no change made to that invitation. As per today's CWG meeting #84, there is one action item for the CWG: * ACTION (CWG): Review the recirculated Annex C table before the next CWG meeting/s I am attaching the e-mail that contains the Annex C table for the ease of your review. Regards, Yuko Green Strategic Programs Manager Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: yuko.green(a)icann.org<mailto:yuko.green@icann.org> www.icann.org<http://www.icann.org/>

1 0

Notes, Recordings, Transcript CWG IANA Meeting #84 - 21 July 2016
by Brenda Brewer July 21, 2016

July 21, 2016

Dear all, The notes, recordings and transcripts for the CWG IANA Meeting #84 on 21 July 2016 will be available here: https://community.icann.org/x/fAObAw A copy of the notes and action items may be found below. Kind regards, Brenda Action Items * ACTION (ICANN): Circulate the RZERC qualification to CWG mail list * ACTION (ICANN Legal): Review Sidley's comments on 3 governance documents and bring version 2 documents to CWG for review * ACTION (CWG): Review the recirculated Annex C table before the next CWG meeting/s * ACTION (Chairs): Confirm next meeting/s date and time Notes 1. Status Update * Grace Abuhamad is departing ICANN, Yuko Green to step in for CWG support 2. Implementation Update * RZERC member qualification criteria has been agreed within IOTF e-mail list ACTION (ICANN): Circulate the RZERC qualification to CWG mail list * PTI documents review process and timeline have been shared by Trang Nguyen * PTI documents are; Articles of Incorporation, Conflict of Interest Policy, Board Code of Conduct, Expected Standard of Behavior, Bylaws, Naming Functions Agreement, Subcontracting Agreements, and Services Agreement. * CWG's role in document review is to ensure that the implementation actions maintain the integrity of the CWG Proposal 3. Key Issues * PTI Expected Standards of Behavior document was created as a direct response to NTIA's report * Though PTI will not have ICANN style meetings, there will be unique points of interaction with PTI where PTI should be clearly governed by the Expected Standards of Behavior document. * Sidley has no major comments or controversial edits on either Conflict of Interest Policy or Code of Conduct documents. ACTION (ICANN Legal): Review Sidley's comments on 3 governance documents and bring version 2 documents to CWG for review Chairs note: ICANN / CWG will need to agree how version 2 documents are incorporated e.g. will they be submitted to the public comment forum on the 3 governance documents? ACTION (CWG): Review the recirculated Annex C table before the next CWG meeting/s Chairs note: Next meeting/s expected to review CWG public comment input on PTI Bylaws and discuss initial input from Sidley on PTI contracts (Naming Functions Agreement and Intercompany Agreement) 5. AOB * DT-O met on 20 July and work is progressing. they will provide status update to CWG. * DT-A's meeting will occur on 21 July at 2100 UTC and CWG is invited. * CWG may require a meeting on Tuesday 26 July and confirmation of the timing for the Thursday 28 July meeting is also required. Chairs will give notice asap to CWG ACTION (Chairs): Confirm next meeting/s date and time

1 0

Revised Sidley Comments on Proposed Principal Terms of IANA IPR Agreements
by Greg Shatan July 21, 2016

July 21, 2016

All, Attached is a chart reflecting revised comments from Sidley on the "Proposed Principal Terms of IANA IPR Agreements." These reflect the outstanding comments by Sidley on this document. Sidley's comments are in the second column. The third column consists of potential responses or action items for the CWG based on Sidley's responses; these are proposed by the Client Committee. Best regards, Greg

2 1

FW: PTI Governance Documents
by Yuko Green July 21, 2016

July 21, 2016

Dear members of the CWG, Please see below and attached documents the Sidley’s comments on PTI governance documents: · PTI Expected Standards of Behavior · PTI Conflict of Interest Policy · PTI Board Code of Conduct Regards, Yuko Green From: cwg-client-bounces(a)icann.org [mailto:cwg-client-bounces@icann.org] On Behalf Of Flanagan, Sharon Sent: Wednesday, July 20, 2016 7:33 PM To: Client Committee <cwg-client(a)icann.org> Subject: [client com] FW: PTI Governance Documents Dear Client Committee, Attached are our comments on the PTI governance documents, marked against the drafts circulated by ICANN. Best regards, Sharon SHARON R. FLANAGAN SIDLEY AUSTIN LLP +1 415 772 1271 sflanagan(a)sidley.com<mailto:sflanagan@sidley.com> **************************************************************************************************** This e-mail is sent by a law firm and may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately. ****************************************************************************************************

1 0

Process of finalizing the documents
by Yuko Green July 21, 2016

July 21, 2016

Dear members of the CWG, During the last CWG call, ICANN had an action item to create slides around the process and timeline with regards to document finalization including the public comment period. Attached, please find the graphical depiction of such process. Regards, Yuko Green Strategic Programs Manager Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: yuko.green(a)icann.org<mailto:yuko.green@icann.org> www.icann.org<http://www.icann.org/>

1 0

Notes, Recordings, Transcript DT-O Meeting on 20 July 2016
by Brenda Brewer July 20, 2016

July 20, 2016

Dear all, The notes, recordings and transcripts for the DT-O Meeting on 20 July 2016 will be available here: https://community.icann.org/x/8D_AAw A copy of the notes and action item may be found below. Kind regards, Brenda [---] Notes Slide 1 * The second bullet point's: ">" means arrows/chevrons, not "larger than." How can we align PTI and ICANN Board on PTI budget? * PTI & ICANN Board should engage prior to community engagement * PTI OP&B should be reviewd by PTI Board and ICANN BFC at the same time for parallel visibility and alignment? Community engagement - What should be included? * Public comment should be mandatory (Chuck, Cheryl, Olivier) * Community engagement period coincides with ICANN meeting. It fits well if face-to-face meeting is necessary (Xavier, Olivier) * May require to have a special involvement from CSC and direct customers within the community engagement period (Chuck) * Utilize the usual model of financial planning in terms of community engagement at the beginning/prior to public comment Action Item: Develop the process that accounts for public comment (ICANN) Do we need to have both PTI and ICANN board approval right after "respond to community feedback and update draft" step? ICANN's budget public comment won't happen until towards the end of Q3 and may introduce complication. * Consider Board approval to occur after the ICANN's budget public comment? Replace "approval" with "receive" on the current timeline? CWG proposal called for community approval whereas CCWG proposal called for veto power by community. Do we need a formal community "approval"? * With community veto power, no need for a formal community apprval (Chuck, Cheryl, Mary) Missing items from the timeline (Slide 2) * Engagement with CSC (performance matter) and RZERC (technical or architectural matter) if necessary at the end of fiscal year (Chuck) * Seek input from CSC & RZERC as an on-going bases as well as at the onset of the process (Xavier & Elise) * Make it clear when and how the engagement and elaboration with other groups occurs Next Step * ICANN to develop a detailed timeline and process based on today's conversation * DT-O members attended today's call support the direction and believes this will meet the CWG recommendation. DT-O is available for consultation if needed. * Provide CWG the status update

1 0

Agenda for CWG-IANA call #84 (21 July @ 06:00 UTC)
by Yuko Green July 20, 2016

July 20, 2016

Dear members of the CWG, Attached, please find the updated calendar for the CWG activities. For our next CWG-Stewardship call at 06:00 UCT on 21 July, you should have received the updated meeting invitation. The meeting will be one hour long instead of 2 based on the meeting agenda. Please see below the proposed agenda for the call: Proposed Agenda: 1. Status Update (Chairs) 2. Implementation Update (Staff) 3. Key Issues (with Sidley) * PTI Articles of Incorporation * PTI Governance Documents o Conflict of Interest Policy o Board Code of Conduct o Expected Standard of Behavior * PTI Bylaws (including Annex C) * Naming Functions Agreement * Services Agreement (headers now available) * IANA IPR 4. Client Committee 5. AOB To aid our discussion for our call, please find below the action items from our last meeting on 19 July: * In Progress (Sidley): Sidley to draft public comment submission having used this table as a tool for discussion of the issues on Articles and Bylaws. * Action (Chairs): CWG to submit Sidley's comments on PTI Articles and Bylaws as part of the CWG's public comment submission (see table provided by Sidley for further detail). * In Progress (Sidley & ICANN Legal): Provide language on PTI purpose to be coordinated in Articles and Bylaws. * In Progress (ICANN): ICANN to provide some slides or documentation on process for public comment proceedings and next steps in finalization of documents. * Complete (Yuko): recirculate Annex C table to the CWG-IANA. Links to documents and open public comment periods: * PTI Articles of Incorporation: https://www.icann.org/public-comments/draft-pti-articles-incorporation-2016… * PTI Governance Documents: https://www.icann.org/public-comments/pti-governance-documents-2016-07-08-en * PTI Bylaws: https://www.icann.org/public-comments/draft-pti-bylaws-2016-07-12-en * Annex C table: https://community.icann.org/download/attachments/49351404/Change-Pro%20Redl… Regards, Yuko Green Strategic Programs Manager Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: yuko.green(a)icann.org<mailto:yuko.green@icann.org> www.icann.org<http://www.icann.org/>

1 0

Re: [CWG-Stewardship] Purpose of PTI
by Andrew Sullivan July 20, 2016

July 20, 2016

It's the lack of a crisp definition that made me propose the "certain registries and certain zones" language. -- Andrew Sullivan Please excuse my clumbsy thums. > On Jul 20, 2016, at 21:17, Flanagan, Sharon <sflanagan(a)sidley.com> wrote: > > We prefer the version Suen circulated which includes the “exclusively” for the benefit language as that tracks the Internal Revenue Code provision. > > With respect to defining IANA, we agree with Greg that ideally it would be defined. Is there a definition that already exists that can be used? If not and that term is well understood, then we would be ok not defining it. > > (Note that I don’t have CWG posting rights.) > > SHARON R. FLANAGAN > > > SIDLEY AUSTIN LLP > +1 415 772 1271 > sflanagan(a)sidley.com > > From: Gomes, Chuck [mailto:cgomes@verisign.com] > Sent: Wednesday, July 20, 2016 10:50 AM > To: matthew shears; Seun Ojedeji > Cc: Lise Fuhr; Andrew Sullivan; cwg-stewardship(a)icann.org; jrobinson(a)afilias.info; Flanagan, Sharon > Subject: RE: [CWG-Stewardship] Purpose of PTI > > Let’s let Sharon and Sam help us word this as planned on the call yesterday. > > Chuck > > From: matthew shears [mailto:mshears@cdt.org] > Sent: Wednesday, July 20, 2016 1:07 PM > To: Seun Ojedeji > Cc: Lise Fuhr; Andrew Sullivan; cwg-stewardship(a)icann.org; jrobinson(a)afilias.info; Flanagan, Sharon; Gomes, Chuck > Subject: Re: [CWG-Stewardship] Purpose of PTI > > Not sure I see the need or value of that additional clause. Unless there is a very good legal reason for doing so we should avoid layering this with unnecessary qualifiers. > > > On 20/07/2016 17:51, Seun Ojedeji wrote: > That could work as well(even though I prefer Andrew's modification), but not without including "...exclusively for the benefit of,.." in the text which will then result to the following: > > "The specific purpose of the corporation is to perform the IANA functions on behalf of, and exclusively for the benefit of, the Internet Corporation for Assigned Names and Numbers (“*ICANN*”)." > > That ensures that PTI remains member(i.e ICANN) driven. > > Regards > Sent from my LG G4 > Kindly excuse brevity and typos > > > On 20 Jul 2016 5:41 p.m., "matthew shears" <mshears(a)cdt.org> wrote: > I'm wondering if we even need to go to that next level. In the Services Agreement draft it says: "WHEREAS, following the IANA Stewardship Transition, PTI will perform the IANA > functions on behalf of ICANN;" > > So rather than making it more vague/complicated than necessary, why wouldn't the PTI bylaws state the following: > > "The specific purpose of the corporation is to perform the IANA functions on behalf of the Internet Corporation for Assigned Names and Numbers (“*ICANN*”)." > That is its purpose. Thanks. > > Matthew > > > > On 20/07/2016 17:18, Jonathan Robinson wrote: > Copying in Sharon from Sidley as suggested by Greg on yesterday's CWG call. > > Jonathan > > -----Original Message----- > From: Gomes, Chuck [mailto:cgomes@verisign.com] > Sent: 19 July 2016 14:31 > To: 'Andrew Sullivan' <ajs(a)anvilwalrusden.com>; cwg-stewardship(a)icann.org > Subject: Re: [CWG-Stewardship] Purpose of PTI > > Andrew's suggestion works for me. > > Chuck > > -----Original Message----- > From: cwg-stewardship-bounces(a)icann.org [mailto:cwg-stewardship-bounces@icann.org] On Behalf Of Andrew Sullivan > Sent: Tuesday, July 19, 2016 9:26 AM > To: cwg-stewardship(a)icann.org > Subject: Re: [CWG-Stewardship] Purpose of PTI > > I think you are rapidly walking in to angry terminological disputes that will delay the incorporation of PTI. > > What about saying something like "relating to certain Internet registries and certain Internet Domain Name System zones, consistent with ICANN's Mission," or something like that? > > A > > On Tue, Jul 19, 2016 at 09:22:53AM -0400, Greg Shatan wrote: > I suggest considering something more specific than "relating to IANA > services" (especially since the second word in the paragraph is > "specific") in stating the purpose of PTI, since "IANA services" is > not a defined term nor is it self-explanatory. Rather it is a "term > of art," and undefined terms of art are generally to be avoided > wherever possible in drafting legal documents. > > We could use the current statement of purpose in the ICANN Articles as > a jumping off point, i.e.: > > The specific purpose of the Corporation is to operate exclusively for > the benefit of, to perform the functions of and to carry out the > purposes of the Internet Corporation for Assigned Names and Numbers > (“*ICANN*”), namely (i) coordinating the assignment of Internet > technical parameters as needed to maintain universal connectivity on > the Internet; (ii) performing and overseeing functions related to the coordination of the Internet Protocol (" > *IP*") address space; (iii) performing and overseeing functions > related to the coordination of the Internet domain name system > ("*DNS*"); and (iv) overseeing operation of the authoritative Internet DNS root server system. > > I recognize that we'll probably want to change some of the verbs here > to more accurately reflect ICANN/IANA's role vs. that of the IETF and > RIRs, but I think this provides a good starting place for an > appropriately specific statement of purpose. > > Greg > > On Fri, Jul 15, 2016 at 11:35 AM, Sivasubramanian M > <isolatedn(a)gmail.com> > wrote: > > Dear Chuck, > > On Fri, Jul 15, 2016 at 8:06 PM, Gomes, Chuck <cgomes(a)verisign.com> wrote: > > Would it work to make the following change:? “The specific purpose > of the Corporation is to operate exclusively for the benefit of, to > perform the functions of and to carry out the purposes of the > Internet Corporation for Assigned Names and Numbers (“*ICANN*”) related to the IANA services.” > > Even without the change, 'related to IANA services' is implied, > but there is no harm in saying it explicitly. When PTI operates for > the benefit of ICANN, and ICANN is built up on the foundation of a > fair accountability framework it, it necessarily follows that PTI > would act in global public interest. > > Sivasubramanian M > > > > > I agree with Matthew that it is not PTI’s purpose to perform all of > ICANN’s functions and purposes. > > > > Chuck > > > > *From:* cwg-stewardship-bounces(a)icann.org [mailto: > cwg-stewardship-bounces(a)icann.org] *On Behalf Of *matthew shears > *Sent:* Friday, July 15, 2016 5:28 AM > *To:* Yuko Green; cwg-stewardship(a)icann.org > *Subject:* Re: [CWG-Stewardship] Purpose of PTI > > > > Hi Yuko - thanks. > > As I noted in the CWG chat yesterday I am uncomfortable with this > definition of the purpose of PTI: "The specific purpose of the > Corporation is to operate exclusively for the benefit of, to > perform the functions of and to carry out the purposes of the > Internet Corporation for Assigned Names and Numbers (“*ICANN*”)." > > This is very broad and very vague. My understanding was that the > purpose of the PTI subsidiary was to perform the IANA functions > pursuant to an inter-company contract established between ICANN and > PTI. This is very different from the proposed language. Of course > we also need to see the inter company agreement to ensure that the > purpose of PTI is similarly parametered. > > Matthew > > > > On 14/07/2016 19:00, Yuko Green wrote: > > Dear members of the CWG, > > > > From today’s CWG call #82, we stated that we will provide the > transcript from the IOTF call where we discussed about the purpose > stated within the PTI Bylaws and Articles. Extracted below is the > transcript and chat history specifically around this topic. The > whole transcript is available at > https://www.icann.org/uploads/iana_work_session_asset/attachment/37 > 3/1467913551526IOTF_Call__14_transcript_06JUL16.pdf > and the AC room recording at https://icann.adobeconnect.com/p3qeid579y7/. > > > > > ****Transcript**** > > > > Paul Kane: In the articles of association, it says the sole > function – apparently I haven’t read it, again I apologize – > function of PTI is to serve ICANN. Historically the function of > IANA has been to serve the community, ICANN just happens to be the > contract to doing it. And I don’t know if that is correct, if that’s what’s in the articles of incorporation. > But if that is, it sort of has lost the raison d’etre of PTI. It is > not a service sector of ICANN because that makes it feel like a > department. It’s actually trying to serve a broader community such > as the naming community, the protocols and the numbers. But I > haven’t read it so I will try and read it so I might be wrong. > > > > Trang Nguyen: Thanks, Paul. Let me – so Section 3 of the articles > says this – it does say that the specific purpose of PTI is to > operate exclusively for the benefit of and to perform the functions > of and carry out the purposes of ICANN. And I want to go back and > double check that again the language that is in the ICANN bylaws > that has been adopted because I think some of this is the > reflection of what’s included in the ICANN bylaws. So we want to do > that cross check and come back to this group and see how it aligns > with – what’s in the ICANN bylaws. But that is currently what is > reflected in the PTI articles of incorporation. There are some > comments in the chat from James. Things that affect the agreement > are done by contract with ICANN for protocol and numbers means that > there needs to be language to that effect in the PTI articles… > > > > James Gannon: So, yes, Paul, I had a similar comment from somebody > else as well from the IETF area. And I think in I suppose > philosophical principle, yes, it is a slight change but I think in > the reality the fact that both the numbers and protocol communities > will still contract with ICANN it needs to be very clear in PTI’s > documents then that, yes, it is for the purposes of fulfilling the > IANA functions it needs to be able to serve the owners of those > contracts, which is ICANN still. So I think philosophically, yes, > it doesn’t really sound very right, but I think for the realities > of running PTI and for PTI to be accountable through the mechanisms > that we’ve built up that there does need to be language like that > inside the articles to make sure that it’s clear that the – those > two communities have the right of PTI serving their needs but also > then the accountability mechanism that we’ve put into ICANN are > also then bound to PTI by that language going backwards. And I think Trang is right that it’s also reflected in the ICANN bylaws going downwards towards PTI. > > > > Trang Nguyen: Thank you, James. And I see Russ has similar comments > in the chat as well that the contract for the protocol parameters > function as well as with the numbers are with ICANN and not PTI. > > > > > > ****Chat**** > > > > Trang Nguyen: The specific purpose of the Corporation is to > operate exclusively for the benefit of, to perform the functions > of, and to carry out the purposes of the Internet Corporation for > Assigned Names and Numbers, a California nonprofit public benefit corporation(“ICANN”). > > > > James Gannon: I think this was Stephens comment yes? I think that > the fact that the agreements are done via contact to ICANN for > protocol and numbers means that there needs to be language to that > effect in the PTI articles > > > > James Gannon: (Sorry no mic) > > > > Paul Kane: A cross check is welcome but I hope you see my point it > is off target > > > > Russ Housley: @Paul, the Numbers and Protocol Parameter communities > have their agreements with ICANN, not PTI. > > > > Paul Kane: Good Point Russ > > > > Russ Housley: @Paul, ICANN is choosing to put that work in PTI. > > > > Russ Housley: @Paul, so PTI is an affiliate of ICANN to perform all > of that work > > > > Paul Kane: ok -thanks > > > > > > > > Regards, > > > > *Yuko Green* > > Strategic Programs Manager > > Global Domains Division > > Internet Corporation for Assigned Names and Numbers (ICANN) > > > > Direct Line: +1 310 578 8693 > > Mobile: +1 310 745 1517 > > E-mail: yuko.green(a)icann.org > > www.icann.org > > > > > > > _______________________________________________ > > CWG-Stewardship mailing list > > CWG-Stewardship(a)icann.org > > https://mm.icann.org/mailman/listinfo/cwg-stewardship > > > > -- > > > > -------------- > > Matthew Shears > > Global Internet Policy and Human Rights > > Center for Democracy & Technology (CDT) > > + 44 771 2472987 > > > ------------------------------ > > [image: Avast logo] <https://www.avast.com/antivirus> > > This email has been checked for viruses by Avast antivirus software. > www.avast.com <https://www.avast.com/antivirus> > > > > _______________________________________________ > CWG-Stewardship mailing list > CWG-Stewardship(a)icann.org > https://mm.icann.org/mailman/listinfo/cwg-stewardship > > > > -- > Sivasubramanian M > <https://www.facebook.com/sivasubramanian.muthusamy> > > _______________________________________________ > CWG-Stewardship mailing list > CWG-Stewardship(a)icann.org > https://mm.icann.org/mailman/listinfo/cwg-stewardship > > > _______________________________________________ > CWG-Stewardship mailing list > CWG-Stewardship(a)icann.org > https://mm.icann.org/mailman/listinfo/cwg-stewardship > > -- > Andrew Sullivan > ajs(a)anvilwalrusden.com > _______________________________________________ > CWG-Stewardship mailing list > CWG-Stewardship(a)icann.org > https://mm.icann.org/mailman/listinfo/cwg-stewardship > _______________________________________________ > CWG-Stewardship mailing list > CWG-Stewardship(a)icann.org > https://mm.icann.org/mailman/listinfo/cwg-stewardship > > _______________________________________________ > CWG-Stewardship mailing list > CWG-Stewardship(a)icann.org > https://mm.icann.org/mailman/listinfo/cwg-stewardship > > > -- > > -------------- > Matthew Shears > Global Internet Policy and Human Rights > Center for Democracy & Technology (CDT) > + 44 771 2472987 > > _______________________________________________ > CWG-Stewardship mailing list > CWG-Stewardship(a)icann.org > https://mm.icann.org/mailman/listinfo/cwg-stewardship > > > > -- > > -------------- > Matthew Shears > Global Internet Policy and Human Rights > Center for Democracy & Technology (CDT) > + 44 771 2472987 > > > **************************************************************************************************** > This e-mail is sent by a law firm and may contain information that is privileged or confidential. > If you are not the intended recipient, please delete the e-mail and any attachments and notify us > immediately. > > ****************************************************************************************************

1 0

Draft Provisions for PTI Bylaws/Contract-Annex C (Sections 7and 8)
by Lise Fuhr July 20, 2016

July 20, 2016

Dear CWG, As you might recall we have earlier discussed how to ensure that Annex C section 7 and 8, from the CWG Proposal, could be ensured in the PTI Bylaws and Contract. Sidley has sent the attached draft which we will cover at the next CWG call as part of the Client Committee update. Best, Jonathan and Lise

2 1

Purpose of PTI
by Yuko Green July 20, 2016

July 20, 2016

Dear members of the CWG, >From today's CWG call #82, we stated that we will provide the transcript from the IOTF call where we discussed about the purpose stated within the PTI Bylaws and Articles. Extracted below is the transcript and chat history specifically around this topic. The whole transcript is available at https://www.icann.org/uploads/iana_work_session_asset/attachment/373/1467913 551526IOTF_Call__14_transcript_06JUL16.pdf and the AC room recording at https://icann.adobeconnect.com/p3qeid579y7/. ***Transcript*** Paul Kane: In the articles of association, it says the sole function - apparently I haven't read it, again I apologize - function of PTI is to serve ICANN. Historically the function of IANA has been to serve the community, ICANN just happens to be the contract to doing it. And I don't know if that is correct, if that's what's in the articles of incorporation. But if that is, it sort of has lost the raison d'etre of PTI. It is not a service sector of ICANN because that makes it feel like a department. It's actually trying to serve a broader community such as the naming community, the protocols and the numbers. But I haven't read it so I will try and read it so I might be wrong. Trang Nguyen: Thanks, Paul. Let me - so Section 3 of the articles says this - it does say that the specific purpose of PTI is to operate exclusively for the benefit of and to perform the functions of and carry out the purposes of ICANN. And I want to go back and double check that again the language that is in the ICANN bylaws that has been adopted because I think some of this is the reflection of what's included in the ICANN bylaws. So we want to do that cross check and come back to this group and see how it aligns with - what's in the ICANN bylaws. But that is currently what is reflected in the PTI articles of incorporation. There are some comments in the chat from James. Things that affect the agreement are done by contract with ICANN for protocol and numbers means that there needs to be language to that effect in the PTI articles. James Gannon: So, yes, Paul, I had a similar comment from somebody else as well from the IETF area. And I think in I suppose philosophical principle, yes, it is a slight change but I think in the reality the fact that both the numbers and protocol communities will still contract with ICANN it needs to be very clear in PTI's documents then that, yes, it is for the purposes of fulfilling the IANA functions it needs to be able to serve the owners of those contracts, which is ICANN still. So I think philosophically, yes, it doesn't really sound very right, but I think for the realities of running PTI and for PTI to be accountable through the mechanisms that we've built up that there does need to be language like that inside the articles to make sure that it's clear that the - those two communities have the right of PTI serving their needs but also then the accountability mechanism that we've put into ICANN are also then bound to PTI by that language going backwards. And I think Trang is right that it's also reflected in the ICANN bylaws going downwards towards PTI. Trang Nguyen: Thank you, James. And I see Russ has similar comments in the chat as well that the contract for the protocol parameters function as well as with the numbers are with ICANN and not PTI. ***Chat*** Trang Nguyen: The specific purpose of the Corporation is to operate exclusively for the benefit of, to perform the functions of, and to carry out the purposes of the Internet Corporation for Assigned Names and Numbers, a California nonprofit public benefit corporation("ICANN"). James Gannon: I think this was Stephens comment yes? I think that the fact that the agreements are done via contact to ICANN for protocol and numbers means that there needs to be language to that effect in the PTI articles James Gannon: (Sorry no mic) Paul Kane: A cross check is welcome but I hope you see my point it is off target Russ Housley: @Paul, the Numbers and Protocol Parameter communities have their agreements with ICANN, not PTI. Paul Kane: Good Point Russ Russ Housley: @Paul, ICANN is choosing to put that work in PTI. Russ Housley: @Paul, so PTI is an affiliate of ICANN to perform all of that work Paul Kane: ok -thanks Regards, Yuko Green Strategic Programs Manager Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: <mailto:yuko.green@icann.org> yuko.green(a)icann.org <http://www.icann.org/> www.icann.org

8 13