From athina.fragkouli at ripe.net Wed Sep 9 10:08:15 2015 From: athina.fragkouli at ripe.net (Athina Fragkouli) Date: Wed, 09 Sep 2015 10:08:15 +0200 Subject: [cooperation-wg] CCWG Second Draft Report - Numbers Related Analysis In-Reply-To: <55E0654E.80808@ripe.net> References: <55E0654E.80808@ripe.net> Message-ID: <55EFE8EF.6050803@ripe.net> Dear colleagues, I would like to remind you that the Cross Community Working Group on Enhancing ICANN Accountability (CCWG) has published CCWG-Accountability second Draft Report that can be found here: https://community.icann.org/pages/viewpage.action?pageId=53783460 Comments can be sent through this webpage: https://www.icann.org/public-comments/ccwg-accountability-2015-08-03-en The comment period closes on 12 September 2015 at 23:59 UTC. The ASO representatives to the CCWG encourage the Number Community to review and give feedback on any specific points in the second Draft Report. At the same time we would like to provide you with a follow-up on the numbering-related matters highlighted in our analysis of the first Draft Report (see communication from 15 May 2015 https://www.ripe.net/ripe/mail/archives/cooperation-wg/2015-May/000753.html and ASO representatives submission to the CCWG on 12 June 2015 http://mm.icann.org/pipermail/accountability-cross-community/2015-June/003354.html). We would also like to highlight the principle amendment introduced in the second Draft Report (section 7 below). 1. Revised Mission The CCWG suggests clarifications on the description of ICANN?s mission (more details in section 3.2 of the second Draft Report). With regards to the coordination of policy development for Internet number resources, the description reads as follows: ?In this role, with respect to IP addresses and AS numbers, ICANN?s Mission is described in the ASO MoU between ICANN and RIRs? (p 29, para 181). The description was provided by the ASO representatives during the drafting process for the first Draft Report and the ASO representatives requested that the Number Community confirm its accuracy during the previous public consultation. Support was expressed for this definition. 2. Revised Commitments and Core Values The CCWG proposes an amendment to one of the core values of the Bylaws. In the first Draft Report (p 25, para 89) the proposed amendment read as follows: ?Employ open, transparent and bottom-up, [private sector led multistakeholder] policy development processes that (i) seeks input from the public, for whose benefit ICANN shall in all events act, (ii) promote well- informed decisions based on expert advice, and (iii) ensure that those entities most affected can assist in the policy development process;? After the public consultation period ASO representative?s communicated to the CCWG the following comment: ?With regards to ICANN?s core values in the Bylaws and in particular page 25, paragraph 89, the RIR community notes that the term "private sector led multistakeholder" (and similar terms) have been used by the NTIA in describing ICANN, but the RIRs describe their policy development processes using terms such as "inclusive, open, transparent and bottom-up". These different descriptions are compatible, provided it is understood that "private sector led" does not exclude government participation.? In the second Draft Report the proposed amendment has been altered and now reads as follows (p.31 para 205): ?Employ open, transparent and bottom-up, multistakeholder policy development processes, led by the private sector, including business stakeholders, civil society, the technical community, and academia that (i) seek input from the public, for whose benefit ICANN shall in all events act, (ii) promote well-informed decisions based on expert advice, and (iii) ensure that those entities most affected can assist in the policy development process;? Do you have any comments with regards to this amended description? 3. U.S. Headquarters as part of the Fundamental Bylaws As in the first Draft Report, the CCWG proposes in the second Draft Report the incorporation of some ICANN accountability-related provisions from the Affirmation of Commitments into the Bylaws (in particular regarding ICANN?s Mission and Core Values). The CCWG suggested defining these provisions as "Fundamental Bylaws". The concept of Fundamental Bylaws is described in section 4 (pp 34-37) of the second Draft Report. The main difference with the common Bylaws provisions is that while the Board could propose a change to this Bylaws provision, Supporting Organizations and Advisory Committees (SO/ACs) with voting rights could block the proposed change (by a 66% vote). On the other hand any change to Fundamental Bylaws would require approval by SO/ACs with voting rights (75% vote). One of these provisions requires that ICANN ?remains headquartered in the United States of America?. The CCWG noted that this provision exists already in current ICANN Bylaws, at Article XVIII Section 1: ?OFFICES. The principal office for the transaction of the business of ICANN shall be in the County of Los Angeles, State of California, United States of America. ICANN may also have an additional office or offices within or outside the United States of America as it may from time to time establish.? In the first Draft Report the CCWG considered whether this provision should also be listed as a Fundamental Bylaw, since it has been suggested that the rest of Affirmation of Commitments provisions be incorporated in the Fundamental Bylaws. After the public consultation period, the ASO representatives communicated to the CCWG the following comment: ?There is general support the introduction of Fundamental Bylaws. Regarding, the list of Bylaws that should become Fundamental Bylaws, most of them indeed contain fundamental principles. However, the RIR community does not believe that the requirement for ICANN to remain in the United States of America is fundamental, but rather is an administrative issue.? The second Draft Report does not propose that Article XVIII be designated as Fundamental Bylaw, and provides the following justification: ?Three considerations suggest that CCWG not propose Article XVIII be designated as a Fundamental Bylaw: First, public comment on the first draft was evenly split on the question of whether to designate Article XVIII a Fundamental Bylaw. Supporting this designation were several commenters from the Commercial Stakeholders Group of GNSO. Governments were among those expressing strong opposition. Second, the Community Mechanism as Sole Member must approve with 2/3 vote any change to ICANN?s Articles of Incorporation, which now state that ICANN is a California Nonprofit Public Benefit Corporation. Third, the Community Mechanism as Sole Member could block any proposed change to ICANN Bylaws Article XVIII, which states ?The principal office for the transaction of the business of ICANN shall be in the County of Los Angeles, State of California.? ? Do you have any comments in relation to this? 4. Appealing Mechanisms The CCWG has proposed enhancements to the two appealing mechanisms described in ICANN Bylaws, i.e. the Independent Review Panel and the Reconsideration process. After the public consultation period ASO representatives communicated the following to the CCWG: ??the RIR community stresses that there are separate, well-established appeal mechanisms for disputes relating to Internet number resources. In particular there is: 1. An arbitration process described in the ASO MoU for disputes relevant to the global policy development process 2. An arbitration process described in the draft Service Level Agreement between the five RIRs and IANA Numbering Services Operator for disputes relevant to the IANA numbering services. 3. A bottom-up process for any concerns that a third party may have relating to Internet number resources issues. Imposing different appeal procedures than the ones agreed upon and used by the numbers community would be contradictory to the bottom-up principle. Therefore, it is strongly suggested that disputes relating to Internet number resources be excluded from the scope of the proposed appeal mechanisms. Additionally the ASO representatives noted that it was requested by the CWG that decisions regarding ccTLD delegations or revocations would be excluded from standing, until relevant appeal mechanisms have been developed by the ccTLD community, in coordination with other parties. Considering the above, the ASO representatives would propose that any appeal mechanism developed by the CCWG should not cover disputes relating to Internet number resources.? Accordingly, in the second Draft Report there is a clear exclusion of the disputes related to Internet number resources with regards to the Independent Review Process (IRP) (p. 40 para 9): ?Exclusions; Numbering Resources: The Address Supporting Organization has likewise indicated that disputes related to Internet number resources should be out of scope for the IRP. As requested by the ASO, decisions regarding numbering resources would be excluded from standing.? However in the section describing the amendments with regards to the Reconsideration Process the relevant paragraph reads as follows (p. 44 para 275): ?Disputes related to Internet number resources are out of scope of the IRP.? It is our understanding that the intention is to exclude disputes related to Internet number resources from the scope of the Reconsideration Process, as this section is about the Reconsideration Process and not about the IRP. A correction to clarify this would be appropriate. The ASO representatives will comment appropriately to the CCWG. 5. Powers In the second Draft Report there are no changes in the community powers suggested by the CCWG. The powers are as follows: - Reconsider/reject budget or strategy/operating plans (section 7.1 of the second Draft Report, pp 55-57) [We would like to note that this power was listed as one of the expected accountability mechanisms by the CWG-Stewardship] - Reconsider/reject changes to ICANN Standard Bylaws (section 7.2 of the Second Draft Report pp 57-58) - Approve changes to Fundamental Bylaws (section 4.5 of the second Draft Report p 37) - Remove individual ICANN Directors (section 7.3 of the second Draft Report pp 58-60) - Recall the entire ICANN Board (section 7.4 of the second Draft Report pp 60- 63) 6. Community Mechanism as Sole Member Model The first Draft Report suggested that these powers would be exercised by changing ICANN?s structure into a membership-based organisation, with the SO/ACs as the members (Membership Model). An alternative model was also investigated, whereby the SO/ACs would become designators (Designator Model). During the public consultation and thereafter, objections were expressed to both of these models. As a result of further discussions and consultations, the second Draft Report introduces a new structure called the Sole Membership Model. This new model is understood to have the following benefits: - It provides the required legal enforceability that the Designator Model and Membership Model could not. - It removes the problematic requirement for some SOs and ACs that they become legal persons, whether to participate as a member in the Membership Model or to enforce rights in both the Membership Model and Designator Model. - It avoids the problem of different statutory rights between SOs and ACs that become members and SOs and ACs that were not members, associated with the Membership Model. - By allowing action only upon support of the community through the Community Mechanism, it limits the issues related to the statutory rights of members associated with the Membership Model, which would allow members to dissolve ICANN and bring derivative suits. The details of the Sole Membership Model can be found in section 6 (pp 47-53). The following aspects of the model are worthy to be highlighted: - SO/ACs are not required to have a legal personhood. - SO/ACs would participate directly in the Sole Member by providing instructions to the Sole Member to exercise the community powers. - In order to instruct the Sole Member, SO/ACs may choose to have voting rights. Voting rights will be allocated votes in the following way: o ASO, GNSO and ccNSO, 5 votes each o GAC and At-Large, 5 votes each o SSAC and RSSAC, 2 votes each Early indications are that the ASO, ccNSO, GNSO and ALAC would be the initial set of voting participants in the Sole Member (with remaining and future SOs and ACs able to opt-in to voting participation). There is no requirement or expectation that a participating SO or AC cast all its votes identically for a given issue (meaning all 5 in support or all 5 against). - For Director removal, Directors appointed by an SO could only be removed by that specific SO or community. The Sole Member would merely implement their decisions. Do you have any comments with regard to this model? Thank you, Athina Fragkouli ASO representative to the CCWG-Accountability From rhill at hill-a.ch Wed Sep 9 10:53:41 2015 From: rhill at hill-a.ch (Richard Hill) Date: Wed, 9 Sep 2015 10:53:41 +0200 Subject: [cooperation-wg] CCWG Second Draft Report - Numbers Related Analysis In-Reply-To: <55EFE8EF.6050803@ripe.net> References: <55E0654E.80808@ripe.net> <55EFE8EF.6050803@ripe.net> Message-ID: <002701d0eadd$06c0b930$14422b90$@ch> Please see inline. Thanks and best, Richard > -----Original Message----- > From: cooperation-wg [mailto:cooperation-wg-bounces at ripe.net] On Behalf > Of Athina Fragkouli > Sent: Wednesday, September 9, 2015 10:08 > To: cooperation-wg at ripe.net > Subject: [cooperation-wg] CCWG Second Draft Report - Numbers Related > Analysis > > Dear colleagues, > > I would like to remind you that the Cross Community Working Group on > Enhancing ICANN Accountability (CCWG) has published CCWG-Accountability > second Draft Report that can be found here: > https://community.icann.org/pages/viewpage.action?pageId=53783460 > SNIP > 6. Community Mechanism as Sole Member Model > > The first Draft Report suggested that these powers would be exercised > by changing ICANN?s structure into a membership-based organisation, > with the SO/ACs as the members (Membership Model). An alternative model > was also investigated, whereby the SO/ACs would become designators > (Designator Model). > > During the public consultation and thereafter, objections were > expressed to both of these models. As a result of further discussions > and consultations, the second Draft Report introduces a new structure > called the Sole Membership Model. > > This new model is understood to have the following benefits: > > - It provides the required legal enforceability that the Designator > Model and Membership Model could not. > - It removes the problematic requirement for some SOs and ACs that they > become legal persons, whether to participate as a member in the > Membership Model or to enforce rights in both the Membership Model and > Designator Model. > - It avoids the problem of different statutory rights between SOs and > ACs that become members and SOs and ACs that were not members, > associated with the Membership Model. > - By allowing action only upon support of the community through the > Community Mechanism, it limits the issues related to the statutory > rights of members associated with the Membership Model, which would > allow members to dissolve ICANN and bring derivative suits. > > The details of the Sole Membership Model can be found in section 6 (pp > 47-53). The following aspects of the model are worthy to be > highlighted: > > - SO/ACs are not required to have a legal personhood. > - SO/ACs would participate directly in the Sole Member by providing > instructions to the Sole Member to exercise the community powers. > - In order to instruct the Sole Member, SO/ACs may choose to have > voting rights. Voting rights will be allocated votes in the following > way: > o ASO, GNSO and ccNSO, 5 votes each > o GAC and At-Large, 5 votes each > o SSAC and RSSAC, 2 votes each > Early indications are that the ASO, ccNSO, GNSO and ALAC would be the > initial set of voting participants in the Sole Member (with remaining > and future SOs and ACs able to opt-in to voting participation). There > is no requirement or expectation that a participating SO or AC cast all > its votes identically for a given issue (meaning all 5 in support or > all 5 against). > - For Director removal, Directors appointed by an SO could only be > removed by that specific SO or community. The Sole Member would merely > implement their decisions. > > Do you have any comments with regard to this model? Yes, I do have comments. They can be found at: http://forum.icann.org/lists/comments-ccwg-accountability-03aug15/msg00002.html > > Thank you, > > Athina Fragkouli > ASO representative to the CCWG-Accountability > > From hph at oslo.net Tue Sep 15 19:26:52 2015 From: hph at oslo.net (Hans Petter Holen) Date: Tue, 15 Sep 2015 19:26:52 +0200 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support Message-ID: <55F854DC.9@oslo.net> Dear RIPE community, As you may be aware, the proposal for IANA stewardship developed by the CRISP Team (and now incorporated into the IANA Stewardship Transition Coordination Group?s proposal) proposes establishing a community-based Review Committee to assist the RIRs in their periodic review of the IANA numbering services Service Level Agreement. In recent months, the NRO Executive Council circulated a draft charter for this Review Committee, noting that the Review Committee ?will comprise 15 members, constituted by: (a) two community appointees from each RIR region (who must not be RIR staff); and (b) one RIR staff from the region (who will be a non-voting member).? The charter also notes that ?Each RIR shall appoint their Review committee members by a method of its own choosing.? https://www.nro.net/wp-content/uploads/Review-Committee-Charter-draft-Public-v1.pdf The RIR Executive Council have indicated that they would like to establish this Review Committee in the coming months (ahead of the IANA stewardship transition), so it is important that the RIPE community come to consensus on how we will select our Review Committee members, and who those members will be. I would like to suggest a solution for your consideration and discussion: we currently have three community representatives on the NRO Number Council, two of which are elected by the community (the third is appointed by the RIPE NCC Executive Board). Acknowledging that the work of the Review Committee will likely be quite limited, I suggest that we appoint the two community-elected NRO Number Council representatives as our representatives to the Review Committee. The third, non-voting member of the Review Committee, who will be a RIPE NCC staff member, would then be appointed by the RIPE NCC Executive Board. I believe that this is a straight forward and efficient proposal that would avoid an extra election process. It is based on our long-standing NRO Number Council process and employing the knowledge and talents of individuals who clearly have the trust of the RIPE community. It is important, however, that the community agree on a method for selecting Review Committee members, so if you support this method I would appreciate that you do so on the RIPE list (ripe-list at ripe.net) by Monday, 28 September. If this proposal is not acceptable we will conduct a separate IANA Review Committee selection process that would need to be planned prior to the RIPE 71 in November. I look forward to hearing your thoughts. Kind Regards, -- Hans Petter Holen, RIPE Chair email: hph at oslo.net | http://hph.oslo.net From brian.nisbet at heanet.ie Mon Sep 21 10:58:16 2015 From: brian.nisbet at heanet.ie (Brian Nisbet) Date: Mon, 21 Sep 2015 09:58:16 +0100 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55F854DC.9@oslo.net> References: <55F854DC.9@oslo.net> Message-ID: <55FFC6A8.9060902@heanet.ie> Hans Petter, I think this may be an elegant solution. I am slightly suspicious of any new piece of work which is supposed to be lightweight and is then given to already busy people, as it has a habit of spiralling. I would also welcome your thoughts on managing the difference between the term lengths of the two different posts? That said, I don't think these are reasons to oppose your proposal, I just want to make sure they've been thought about. Thanks, Brian Brian Nisbet, Network Operations Manager HEAnet Limited, Ireland's Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin 1 Registered in Ireland, no 275301 tel: +35316609040 fax: +35316603666 web: http://www.heanet.ie/ On 15/09/2015 18:26, Hans Petter Holen wrote: > Dear RIPE community, > > As you may be aware, the proposal for IANA stewardship developed by the > CRISP Team (and now incorporated into the IANA Stewardship Transition > Coordination Group?s proposal) proposes establishing a community-based > Review Committee to assist the RIRs in their periodic review of the IANA > numbering services Service Level Agreement. > > In recent months, the NRO Executive Council circulated a draft charter > for this Review Committee, noting that the Review Committee ?will > comprise 15 members, constituted by: (a) two community appointees from > each RIR region (who must not be RIR staff); and (b) one RIR staff from > the region (who will be a non-voting member).? The charter also notes > that ?Each RIR shall appoint their Review committee members by a method > of its own choosing.? > > https://www.nro.net/wp-content/uploads/Review-Committee-Charter-draft-Public-v1.pdf > > > The RIR Executive Council have indicated that they would like to > establish this Review Committee in the coming months (ahead of the IANA > stewardship transition), so it is important that the RIPE community come > to consensus on how we will select our Review Committee members, and who > those members will be. > > I would like to suggest a solution for your consideration and > discussion: we currently have three community representatives on the NRO > Number Council, two of which are elected by the community (the third is > appointed by the RIPE NCC Executive Board). Acknowledging that the work > of the Review Committee will likely be quite limited, I suggest that we > appoint the two community-elected NRO Number Council representatives as > our representatives to the Review Committee. The third, non-voting > member of the Review Committee, who will be a RIPE NCC staff member, > would then be appointed by the RIPE NCC Executive Board. > > I believe that this is a straight forward and efficient proposal that > would avoid an extra election process. It is based on our long-standing > NRO Number Council process and employing the knowledge and talents of > individuals who clearly have the trust of the RIPE community. > > It is important, however, that the community agree on a method for > selecting Review Committee members, so if you support this method I > would appreciate that you do so on the RIPE list (ripe-list at ripe.net) by > Monday, 28 September. > > If this proposal is not acceptable we will conduct a separate IANA > Review Committee selection process that would need to be planned prior > to the RIPE 71 in November. > > I look forward to hearing your thoughts. > > Kind Regards, > From jim at rfc1035.com Mon Sep 21 15:21:06 2015 From: jim at rfc1035.com (Jim Reid) Date: Mon, 21 Sep 2015 14:21:06 +0100 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55F854DC.9@oslo.net> References: <55F854DC.9@oslo.net> Message-ID: On 15 Sep 2015, at 18:26, Hans Petter Holen wrote: > I suggest that we appoint the two community-elected NRO Number Council representatives as our representatives to the Review Committee. The third, non-voting member of the Review Committee, who will be a RIPE NCC staff member, would then be appointed by the RIPE NCC Executive Board. > > I believe that this is a straight forward and efficient proposal that would avoid an extra election process. +1 Just do it! From gushkovsv at gmail.com Mon Sep 21 16:50:16 2015 From: gushkovsv at gmail.com (Sergey V. Gushkov) Date: Mon, 21 Sep 2015 17:50:16 +0300 Subject: [cooperation-wg] Fwd: IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: References: <55F854DC.9@oslo.net> Message-ID: +1 I completely agree! 2015-09-21 16:21 GMT+03:00 Jim Reid : > > On 15 Sep 2015, at 18:26, Hans Petter Holen wrote: > > > I suggest that we appoint the two community-elected NRO Number Council > representatives as our representatives to the Review Committee. The third, > non-voting member of the Review Committee, who will be a RIPE NCC staff > member, would then be appointed by the RIPE NCC Executive Board. > > > > I believe that this is a straight forward and efficient proposal that > would avoid an extra election process. > > +1 > > Just do it! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Maud.Karlberg at vll.se Tue Sep 22 08:58:55 2015 From: Maud.Karlberg at vll.se (Maud.Karlberg at vll.se) Date: Tue, 22 Sep 2015 08:58:55 +0200 Subject: [cooperation-wg] Away from the distrubutionslist Message-ID: Hello! Can you remove me from this distrubitionslist? V?nliga h?lsningar Maud Karlberg Informatikenheten By 5A, 2 tr V?sterbottens l?ns landsting 901 85 Ume? 090-7854101 www.vll.se/informatik -------------- next part -------------- An HTML attachment was scrubbed... URL: From seun.ojedeji at gmail.com Tue Sep 22 09:39:39 2015 From: seun.ojedeji at gmail.com (Seun Ojedeji) Date: Tue, 22 Sep 2015 08:39:39 +0100 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55F854DC.9@oslo.net> References: <55F854DC.9@oslo.net> Message-ID: As one of those that suggested the work of RC be assigned to NRO-NC globally (even though did not successfully convince the CRISP) during the proposal development, I support the suggestion made by Hans. Cheers! On Tue, Sep 15, 2015 at 6:26 PM, Hans Petter Holen wrote: > Dear RIPE community, > > As you may be aware, the proposal for IANA stewardship developed by the > CRISP Team (and now incorporated into the IANA Stewardship Transition > Coordination Group?s proposal) proposes establishing a community-based > Review Committee to assist the RIRs in their periodic review of the IANA > numbering services Service Level Agreement. > > In recent months, the NRO Executive Council circulated a draft charter for > this Review Committee, noting that the Review Committee ?will comprise 15 > members, constituted by: (a) two community appointees from each RIR region > (who must not be RIR staff); and (b) one RIR staff from the region (who > will be a non-voting member).? The charter also notes that ?Each RIR shall > appoint their Review committee members by a method of its own choosing.? > > > https://www.nro.net/wp-content/uploads/Review-Committee-Charter-draft-Public-v1.pdf > > The RIR Executive Council have indicated that they would like to establish > this Review Committee in the coming months (ahead of the IANA stewardship > transition), so it is important that the RIPE community come to consensus > on how we will select our Review Committee members, and who those members > will be. > > I would like to suggest a solution for your consideration and discussion: > we currently have three community representatives on the NRO Number > Council, two of which are elected by the community (the third is appointed > by the RIPE NCC Executive Board). Acknowledging that the work of the Review > Committee will likely be quite limited, I suggest that we appoint the two > community-elected NRO Number Council representatives as our representatives > to the Review Committee. The third, non-voting member of the Review > Committee, who will be a RIPE NCC staff member, would then be appointed by > the RIPE NCC Executive Board. > > I believe that this is a straight forward and efficient proposal that > would avoid an extra election process. It is based on our long-standing NRO > Number Council process and employing the knowledge and talents of > individuals who clearly have the trust of the RIPE community. > > It is important, however, that the community agree on a method for > selecting Review Committee members, so if you support this method I would > appreciate that you do so on the RIPE list (ripe-list at ripe.net) by > Monday, 28 September. > > If this proposal is not acceptable we will conduct a separate IANA Review > Committee selection process that would need to be planned prior to the RIPE > 71 in November. > > I look forward to hearing your thoughts. > > Kind Regards, > > -- > Hans Petter Holen, RIPE Chair > email: hph at oslo.net | http://hph.oslo.net > > > -- ------------------------------------------------------------------------ *Seun Ojedeji,Federal University Oye-Ekitiweb: http://www.fuoye.edu.ng Mobile: +2348035233535**alt email: seun.ojedeji at fuoye.edu.ng * Bringing another down does not take you up - think about your action! -------------- next part -------------- An HTML attachment was scrubbed... URL: From nurani at netnod.se Tue Sep 22 14:27:41 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Tue, 22 Sep 2015 14:27:41 +0200 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] CRISP Meeting on Thursday September 24th 2015 at 13:00 UTC References: <773E30A9-847F-4583-83D3-11927CD1AF68@nro.net> Message-ID: <4EC9D627-22F1-49A9-A093-1E60C00EED34@netnod.se> FYI. Nurani Nimpuno > Begin forwarded message: > > From: German Valdez > Subject: [NRO-IANAXFER] CRISP Meeting on Thursday September 24th 2015 at 13:00 UTC > Date: 22 september 2015 13:17:59 CEST > To: > > Please find below webex invitation for CRISP Team call on Thursday September 24th 2015 at 13:00 UTC > > > JOIN WEBEX MEETING > https://ripencc.webex.com/ripencc/j.php?MTID=m88bfef1da7f02edbd7f2550e0883d6a5 > Meeting number: 707 107 621 > Meeting password: crisp > > > JOIN BY PHONE > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Access code: 707 107 621 > > Global call-in numbers: > https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=389532762&tollFree=1 > > Toll-free dialing restrictions: > http://www.webex.com/pdf/tollfree_restrictions.pdf > > Regards > > German Valdez > NRO Secretariat > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From hph at oslo.net Wed Sep 23 07:13:17 2015 From: hph at oslo.net (Hans Petter Holen) Date: Wed, 23 Sep 2015 07:13:17 +0200 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <55FFC6A8.9060902@heanet.ie> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> Message-ID: <560234ED.1010806@oslo.net> Hi Brian, Thanks for your questions and comments. On 21.09.15 10.58, Brian Nisbet wrote: > > I think this may be an elegant solution. I am slightly suspicious of > any new piece of work which is supposed to be lightweight and is then > given to already busy people, as it has a habit of spiralling. The NRO-NC already has the following responsibilities as ASO AC according to 3b in the MOU with ICANN: https://archive.icann.org/en/aso/aso-mou-29oct04.htm * a role in Global policy development * make recommendations to the ICANN board on new LIRs * selecting ICANN board member two out of three years * make their own procedures The work of the review committee is to give advice on IANA performance for the numbers community. We do not have any experience with how much work this is going to be, but if we look at the work IANA does for numbers - it is in the range of one request every second month on average. So I would assume reading trough the monthly reports once or twice a year and checking that the Personally I would imagine that this added workload is more than manageable. > > I would also welcome your thoughts on managing the difference between > the term lengths of the two different posts? Thats a good point. I will propose that we modify the terms of the review committee to match the ones of the NRO-NC. > > That said, I don't think these are reasons to oppose your proposal, I > just want to make sure they've been thought about. Good point. -- Hans Petter Holen Mobile +47 45 06 60 54 | hph at oslo.net | http://hph.oslo.net From brian.nisbet at heanet.ie Wed Sep 23 18:00:46 2015 From: brian.nisbet at heanet.ie (Brian Nisbet) Date: Wed, 23 Sep 2015 17:00:46 +0100 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <560234ED.1010806@oslo.net> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> <560234ED.1010806@oslo.net> Message-ID: <5602CCAE.1040808@heanet.ie> Hans Petter, On 23/09/2015 06:13, Hans Petter Holen wrote: > Hi Brian, > Thanks for your questions and comments. > > On 21.09.15 10.58, Brian Nisbet wrote: >> >> I think this may be an elegant solution. I am slightly suspicious of >> any new piece of work which is supposed to be lightweight and is then >> given to already busy people, as it has a habit of spiralling. > > Personally I would imagine that this added workload is more than > manageable. Grans so. >> I would also welcome your thoughts on managing the difference between >> the term lengths of the two different posts? > Thats a good point. > I will propose that we modify the terms of the review committee to match > the ones of the NRO-NC. Sounds good and makes it all very easy indeed. Thanks, Brian From sander at steffann.nl Wed Sep 23 19:22:18 2015 From: sander at steffann.nl (Sander Steffann) Date: Wed, 23 Sep 2015 19:22:18 +0200 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <5602CCAE.1040808@heanet.ie> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> <560234ED.1010806@oslo.net> <5602CCAE.1040808@heanet.ie> Message-ID: <83C77CDD-82C1-4474-B83C-512E726157D9@steffann.nl> Hi, > Op 23 sep. 2015, om 18:00 heeft Brian Nisbet het volgende geschreven: > > Hans Petter, > On 23/09/2015 06:13, Hans Petter Holen wrote: > >>> I would also welcome your thoughts on managing the difference between >>> the term lengths of the two different posts? >> Thats a good point. >> I will propose that we modify the terms of the review committee to match >> the ones of the NRO-NC. > > Sounds good and makes it all very easy indeed. +1. Sounds like a good way to do this. Cheers, Sander From shane at time-travellers.org Wed Sep 23 17:05:40 2015 From: shane at time-travellers.org (Shane Kerr) Date: Wed, 23 Sep 2015 15:05:40 +0000 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <560234ED.1010806@oslo.net> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> <560234ED.1010806@oslo.net> Message-ID: <20150923150540.3acba173@casual> Hans Petter, On Wed, 23 Sep 2015 07:13:17 +0200 Hans Petter Holen wrote: > On 21.09.15 10.58, Brian Nisbet wrote: > > I would also welcome your thoughts on managing the difference between > > the term lengths of the two different posts? > Thats a good point. > I will propose that we modify the terms of the review committee to match > the ones of the NRO-NC. I support the proposal, including this modification. Cheers, -- Shane From ripe-wgs.cs at schiefner.de Thu Sep 24 11:26:54 2015 From: ripe-wgs.cs at schiefner.de (Carsten Schiefner) Date: Thu, 24 Sep 2015 11:26:54 +0200 Subject: [cooperation-wg] IANA Review Committee Selection Process - RIPE Community Support In-Reply-To: <560234ED.1010806@oslo.net> References: <55F854DC.9@oslo.net> <55FFC6A8.9060902@heanet.ie> <560234ED.1010806@oslo.net> Message-ID: <5603C1DE.1030405@schiefner.de> Hans Petter, all - On 23.09.2015 07:13, Hans Petter Holen wrote: > On 21.09.15 10.58, Brian Nisbet wrote: >> >> I think this may be an elegant solution. I am slightly suspicious of >> any new piece of work which is supposed to be lightweight and is then >> given to already busy people, as it has a habit of spiralling. > The NRO-NC already has the following responsibilities as ASO AC > according to 3b in the MOU with ICANN: > https://archive.icann.org/en/aso/aso-mou-29oct04.htm > * a role in Global policy development > * make recommendations to the ICANN board on new LIRs > * selecting ICANN board member two out of three years > * make their own procedures > > The work of the review committee is to give advice on IANA performance > for the numbers community. We do not have any experience with how much > work this is going to be, but if we look at the work IANA does for > numbers - it is in the range of one request every second month on > average. So I would assume reading trough the monthly reports once or > twice a year and checking that the > > Personally I would imagine that this added workload is more than > manageable. > >> >> I would also welcome your thoughts on managing the difference between >> the term lengths of the two different posts? > Thats a good point. > I will propose that we modify the terms of the review committee to match > the ones of the NRO-NC. sounds all reasonable to me. I support this. Best, -C.