- Internal-cg - lists.icann.org

Re: [Internal-cg] Building on Commonalities .. [was: Handling process complaints]
by Joseph Alhadeff Feb. 7, 2015

Feb. 7, 2015

I support this approach as well. Joe Sent from my Android phone using TouchDown (www.nitrodesk.com) -----Original Message----- From: Lynn St.Amour [Lynn(a)lstamour.org] Received: Saturday, 07 Feb 2015, 7:50AM To: Manal Ismail [manal(a)tra.gov.eg] CC: ICG [internal-cg(a)icann.org] Subject: Re: [Internal-cg] Building on Commonalities .. [was: Handling process complaints] Manal, first, GREAT job as usual! And, both you and Daniel have laid this out quite clearly. Thank you both. I support many of Daniel's points (just as you did), in fact, all but one. I do have concerns about "No acknowledgements. No forwarding" for the reasons you state. It does not feel responsive enough. I would support a path that acknowledged and forwarded any comments the ICG forum received to the appropriate OC - with a short note re our expectations (captured largely in your earlier note, and worded in a way that did not trigger our common fears of incorrect impressions). It could also reaffirm the role of the OC's and the ICG - this will also be instructional for anyone else contemplating a note to the ICG. I also see this more as an Operating Practice than a Procedure per se. If we go this way, I am happy to work with Manal (and others) on text. Best all, Lynn On Feb 5, 2015, at 2:31 AM, "Manal Ismail" <manal(a)tra.gov.eg> wrote: > Comments, short ones :), inline below .. > Kind Regards > --Manal > > -----Original Message----- > From: internal-cg-bounces(a)icann.org > [mailto:internal-cg-bounces@icann.org] On Behalf Of Daniel Karrenberg > Sent: Tuesday, February 03, 2015 9:52 AM > To: Alissa Cooper > Cc: ICG > Subject: Re: [Internal-cg] Building on Commonalities .. [was: Handling > process complaints] > > On 2.02.15 23:00 , Alissa Cooper wrote: >> Jean-Jacques, >> >> ... And I think it would be great to continue this discussion on the >> mailing list so that it need not occupy much time during the F2F > meeting. ... > > > After the discussion so far, my proposal remains as is: > > avoid any impression that we run a complaints procedure or an appeals > process. > [MI]: Agree .. > > No procedure. > [MI]: Agree .. We don't necessarily need a procedure, per se, but at > least we need common agreement on how to proceed .. > > No acknowledgements. No forwarding. > [MI]: Let me try to go down this path, then what? Do nothing? Then why > did we agree to receive comments directly from the community at the > first place? Do something else? Fair enough, what is it? > > Agree on posing specific questions using our normal process. > [MI]: I fully agree .. Each ICG member can pose questions to the > relevant OC .. and I support Alissa's proposal, to gather all ICG > questions and compile one list (union of all) for each relevant OC .. > ICG questions and public comments are different and not mutually > exclusive processes, as ICG questions may or may not have to with public > comments .. > > It appears to me that we should address this first. It makes no sense > going into details about a specific procedure before we definitely agree > to have one. > [MI]: Definitely .. I fully agree .. > > [MI]: I think, by now, both our views are clear :) .. Let's hear other > colleagues then try to reach an ICG consensus view and a way forward > tomorrow at the meeting .. > > Daniel > _______________________________________________ > Internal-cg mailing list > Internal-cg(a)icann.org > https://mm.icann.org/mailman/listinfo/internal-cg > _______________________________________________ > Internal-cg mailing list > Internal-cg(a)icann.org > https://mm.icann.org/mailman/listinfo/internal-cg _______________________________________________ Internal-cg mailing list Internal-cg(a)icann.org https://mm.icann.org/mailman/listinfo/internal-cg

1 0

SSAC 067, 068 & 069 Now in Dropbox
by Russ Mundy Feb. 6, 2015

Feb. 6, 2015

Several folks have said that they would like to have the three SSAC publications in our joint Dropbox so I have placed copies of these documents from the SSAC publications web site <https://www.icann.org/resources/pages/documents-2012-02-25-en> along with a ReadMe file. The new folder is named: SSAC-Documents Russ

2 1

CRISP presentation from today's meeting 6 Feb 2015
by Paul Wilson Feb. 6, 2015

Feb. 6, 2015

Should be accessible on dropbox: https://www.dropbox.com/s/4io2o9ifbyu15f7/ICG%20CRISP%20update%2006022015%2… ________________________________________________________________________ Paul Wilson, Director-General, APNIC <dg(a)apnic.net> http://www.apnic.net +61 7 3858 3100

1 0

Links to SSAC Documents
by Patrik Fältström Feb. 6, 2015

Feb. 6, 2015

SAC-067 in English: <https://www.icann.org/en/system/files/files/sac-067-en.pdf> SAC-068 in English: <https://www.icann.org/en/system/files/files/sac-068-en.pdf> Translations of those will be added shortly, and I (and/or Russ) will let you know when they arrive. Patrik

2 2

IETF assessment
by Milton L Mueller Feb. 6, 2015

Feb. 6, 2015

I have filled out most of the assessment form for the IETF / protocols response to our RFP. I've been waiting to finish it for the IANAPLAN WG to respond to the process challenges, trying to follow the list Unfortunately there is no clear response yet, the list is debating it. So I will wait a bit longer and turn in my draft assessment some time late tonight or tomorrow Milton L Mueller Laura J. and L. Douglas Meredith Professor Syracuse University School of Information Studies http://faculty.ischool.syr.edu/mueller/ Internet Governance Project http://internetgovernance.org<http://internetgovernance.org/>

6 18

Review of Protocol Parameters and Numbers Proposals for completeness
by Patrik Fältström Feb. 6, 2015

Feb. 6, 2015

Hi, I have spent some time looking at the Numbers and Protocol Parameters proposals in parallel with the IANA Contract and specifically the ICANN Response to the RFP. The goal was to try to identify gaps or overlaps that the proposals did not take into account. Specifically, I looked at two areas: - The registries related to IP addresses and AS numbers - The IANA.ORG domain name I did add the summary of my review in my assessment of the Numbers Proposal where I did start with Wulf Ulrich excellent work (and that is why you see much text in my assessment that is exactly the same words as in his assessment). My assessment is in the dropbox and also attached to this email. Patrik

3 4

Fwd: [NRO-IANAXFER] The CRISP Team Response to "Process concern regarding the RIR proposal development process "
by Alissa Cooper Feb. 5, 2015

Feb. 5, 2015

Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Fwd: The CRISP Team Response to "Process concern regarding the RIR proposal development process " > Date: February 4, 2015 at 11:54:59 AM PST > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear all, > > > This is the CRISP Team Response to "Process concern regarding the RIR > proposal development process ", which is another post to icg-forum. > > Again, I welcome your comments and feedback about our reponse which is > likely to be a reference to the ICG. > > Explicit expressing support would be extremely helpful as well. > > > > Regards, > Izumi > > > -------- Forwarded Message -------- > Subject: The CRISP Team Response to "Process concern regarding the RIR > proposal development process " > Date: Thu, 05 Feb 2015 04:43:25 +0900 > From: Izumi Okutani <izumi(a)nic.ad.jp> > To: icg-forum(a)icann.org > CC: crisp(a)nro.net <crisp(a)nro.net> > > Dear ICG members, > > > On 20 January 2015 Richard Hill wrote to the icg-forum list with a > number of concerns about the CRISP team process. > > http://forum.icann.org/lists/icg-forum/msg00020.html > > The concerns expressed by Mr Hill were considered in depth during the > CRISP team proposal development process and had been discussed on the > ianaxfer mailing list with Mr Hill as well as other community members. > > The positions taken by the CRISP team was based on the consensus > position of the community. > > > Richard Hill wrote: > >> Certain legal questions were raised in discussions on the CRISP > mailing list >> (NRO IANAXFER), in particular regarding jurisdiction and dispute > resolution. >> The CRISP team apparently did not include anybody who had appropriate > legal >> expertise and it chose not to request outside legal expertise, see: >> https://www.nro.net/pipermail/ianaxfer/2015-January/000322.html > > Mr Hill’s objections to the position adopted by the CRISP team were well > documented in his emails to the ianaxfer mailing list, and were > discussed at length on the CRISP teleconferences (notes and audio > archives of these calls are available at https://nro.net/crisp-team) > Additionally, they were included in the CRISP team’s matrix of community > comments and concerns posted at: > https://www.nro.net/crisp-iana-xfer-summary-discussion-08012015 > > The CRISP team’s final position is effectively summarised in the text of > our response to the ICG RFP: > > “The RIRs, as the contractual party of this agreement, will draft the > specific language of this agreement. During the drafting process, the > RIRs are expected to consult their respective RIR communities, and that > the drafting process will be guided by the principles listed below.” > [Response to the ICG RFP on the IANA from the Internet Number Community, > p11] > > The RFP response then lists 11 IANA Service Level Agreement Principles. > This was based on taking into account of feedback on the ianaxfer > mailing list, to bring the proposal back to describing high level > principles. > > The CRISP team’s position took into account the concerns raised by Mr > Hill, and addressed some points he has raised, such as describing in the > proposal that RIRs are expected to consult their respective RIR > communities, as quoted earlier. > > The CRISP Team was also informed by other feedback received via the > ianaxfer mailing list, particularly those mails which explicitly > supported the approach of delegating contract authorship to the RIR > legal teams. Posts by Hans Petter Holen (7 Jan,10 Jan) Seun Ojedeji (7 > Jan) Gerard Ross (11 January), Jim Reid (12 January), Andrew Dul (12 > January) and Dmitry Burkov (13 January) specifically endorsed this view. > All of these mails can be read at: > https://www.nro.net/pipermail/ianaxfer/2015-January/date.html > > A further concern noted by Mr Hill: >> That is, how can NTIA be expected to approve a proposal when important >> details are left open and have not been reviewed or endorsed by the global >> multi-stakeholder community? > > The CRISP team has crafted a proposal that reflects the value that the > community places on the number-related IANA functions. This is reflected > in the proposal to safeguard the RIR communities’ stewardship over these > functions via a contractual relationship. It is the responsibility of > the parties to a contract to negotiate a contract. The CRISP team > believes that by directing the RIRs to consult with their communities > and by laying down the principles mentioned above, we have established a > framework within which the RIR legal staff can effectively negotiate in > the best interests of the community. > > Finally, Mr Hill has expressed that "there was limited input and the > outcome was largely influenced by the CRISP team and the RIR staff”. As > noted above, there were numerous posts to the ianaxfer mailing list, > many of which touched specifically on the issues discussed by Mr Hill. > From 17 October 2014 to 29 January 2015 there were 372 mails to the > ianaxfer list and 134 subscribers - information on the list is available > at: https://www.nro.net/mailman/listinfo/ianaxfer > > I hope that this is a useful explanation of the CRISP team’s position in > regard to the issues raised by Mr Hill. I am of course happy to discuss > any of these issues in greater depth if this would be helpful. > > > Yours sincerely, > > Izumi Okutani > Chair, the CRISP Team > > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] The CRISP Team Response to "CRISP - Process Concerns"
by Alissa Cooper Feb. 5, 2015

Feb. 5, 2015

Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Fwd: The CRISP Team Response to "CRISP - Process Concerns" > Date: February 4, 2015 at 11:53:49 AM PST > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear all, > > > I would like to share the CRISP Team Response to "CRISP - Process > Concerns", which has been posted to icg-forum. > > I welcome your comments and feedback about our reponse which is likely > to be a reference to the ICG. > > Explicit expressing support would be extremely helpful as well. > > > > Regards, > Izumi > > > -------- Forwarded Message -------- > Subject: The CRISP Team Response to "CRISP - Process Concerns" > Date: Thu, 05 Feb 2015 04:37:01 +0900 > From: Izumi Okutani <izumi(a)nic.ad.jp> > To: icg-forum(a)icann.org > > Dear ICG members, > > > On 22 January 2015 Guru Acharya wrote to the icg-forum list with a > number of concerns about the CRISP team process. > > http://forum.icann.org/lists/icg-forum/msg00024.html > > The CRISP Team was not able to confirm concrete evidence/facts on these > concerns, as explained below. > > We also note that while present as an observer on a number of CRISP > teleconferences, we did not observe Guru Archaya raising any of these > concerns on ianaxfer(a)nro.net mailing list or on any of the regional > community lists on which the CRISP process was being discussed. > > > Guru Acharya writes: > >> I would like to highlight the following concerns about the process > adopted >> by CRISP, which disqualify it from satisfying the criteria of following a >> bottom-up multi-stakeholder process as mandated by the NTIA. >> >> 1) Top-down composition and selection of CRISP team: The CRISP team was a >> closed group selected by the RIR executive committee by way of an > interview >> process. Interested participants were excluded from the working group if >> they did not successfully qualify for the interviews conducted by the RIR >> executive committee. The selection criteria for the candidates was > not made >> public by the RIR executive committee. This is important given that >> non-CRISP participants were excluded from the decision-making process. > > > Before setting up the CRISP Team, RIRs published the process for > producing a single proposal from the global IP addressing community to > the NTIA, and there was an opportunity for discussions on the public > <ianaxfer(a)nro.net> mailing list as below: > > On 16 October the five RIRs published a process for producing a single > proposal from the global IP addressing community to the NTIA. > https://www.nro.net/news/iana-stewardship-consolidated-rir-iana-stewardship… > > According to this process the CRISP team would consist of 15 members, > two appointees from each RIR region who are not RIR staff, and one RIR > staff member from each region, who shall assist with the submission > development effort. Each RIR was to appoint their CRISP team members by > a method of its own choosing by 15 November 2014. There was some > discussion on the public <ianaxfer(a)nro.net> mailing list on 21 October > about standardising a CRISP team selection process across all five RIR > regions, but no broader community support was expressed for this change. > See: > https://www.nro.net/pipermail/ianaxfer/2014-October/000016.html > > Following this announcement each of the five RIRs announced an open call > for participants, to which any one could express their interest, as well > as the process according to which the selection of the CRISP members > would be conducted. The process and relevant announcements of each RIR > are described in the Internet Number Community Response to the ICG RFP > (sections VI.B.1-VI.B.5 on "Community Process"). > > In most cases the RIR executive committees made the final selection of > CRISP representatives from community volunteers. At no point in the > process were any explicit objections raised to any of the CRISP team > members, nor were any appeals made by volunteers not selected to join > the CRISP team. > >> >> 2) Top-down decision-making by the CRISP team: While the general > public was >> invited to provide comments for the draft proposals prepared by > CRISP, they >> were excluded from the decision-making process. Commenters were merely >> informed that their input had either been accepted or rejected by the > CRISP >> team after due consideration. Notably, non-CRISP participants were not >> allowed to contribute to CRISP's tele-conferences or CRISP's internal >> mailing list, where the actual decision-making took place. Mere >> consultation of the general public without their involvement in the >> decision-making process does not constitute a bottom-up multi-stakeholder >> process. > > > Each of the RIR communities had conducted discussions on the IANA > stewardship transition for the IANA Numbering Services and the role of > the CRISP Team is to consolidate it as a single global proposal. > > https://www.nro.net/nro-and-internet-governance/iana-oversight/consolidated… > > The proposal to establish a CRISP team was distributed to all of the RIR > communities and the <ianaxfer(a)nro.net> mailing list established on 16 > October 2015. The first CRISP team teleconference was held on 9 December > 2015. This provided the community with nearly two months during which > they could comment on or object to any elements of the proposal to set > up the CRISP team (as noted above, there was some discussion around 21 > October relating to CRISP team selection processes, but there was not > community support for changing the proposed process). > > The CRISP team members agreed with the arrangements laid out in the > proposal (while developing some additional mechanisms, including the > internal CRISP mailing list and a working definition of quorum for the > group). CRISP team members also understood a key part of their role to > be facilitating input from the regional communities, and this was > evident throughout the process - teleconference notes from the third > teleconference onwards record various CRISP team members conveying input > from their regional mailing lists. > > Invitations to join the CRISP Team Teleconferences as observers were > sent to <ianaxfer(a)nro.net> mailing list, which were forwarded to mailing > lists of RIR regions by the CRISP Team members. > > Subscription to <ianaxfer(a)nro.net> mailing list was open to anyone, and > there was no restrictions on posting comments to the list, including > making comments about the CRISP Team discussions at any of the CRISP > Team Teleconferences. > > A concrete record of all the concerns raised by the community on various > mailing lists was prepared by the CRISP team and made available at: > https://www.nro.net/wp-content/uploads/NRODiscussionList_20150116.pdf > > This spreadsheet indicated the issue, the initial mail in which the > issue was raised, the CRISP team's discussion of the issue and the > current CRISP team position. This clearly demonstrates that the process > of community participation facilitated by the CRISP team worked smoothly > to address a wide range of community input throughout the process. > >> >> 3) Lack of information and transparency: The CRISP team had two mailing >> lists. The mailing list used internally by the CRISP team was a closed >> mailing list that was not publicly archived till after the proposal was >> finalised. This resulted in community evaluation of the process and >> proposal in the absence of requisite information about the reasons > for any >> decisions. > > As noted in the initial CRISP team proposal and charter, "The CRISP team > shall also work through a public mailing list and the archive of such > mailing list will be publicly available. The name of the mailing list > will be <ianaxfer(a)nro.net>. > > At its initial teleconference, CRISP team members suggested that a > separate mailing list for use by CRISP team members only would be useful > in the interest of efficiency and to allow quick editing iterations on > the proposed response. > https://www.nro.net/wp-content/uploads/CRISP-December-9-meeting-DRAFT-NOTES… > > While there was general agreement, concerns about transparency were also > noted, resulting in a commitment to publish archives of the internal > list at the time of publishing the first draft (19 December 2014). The > archive was publicly available from this point and some CRISP team > members shared a link to the archive with their communities directly. A > direct link to this mailing list archive was posted to the ianaxfer > mailing list and on the NRO CRISP webpage after 8 January 2015 due to an > oversight, while the archives were publicly made available when the > first draft of the proposal was published on 19 December. > > The archive of the internal mailing list is available at: > https://www.nro.net/pipermail/crisp/ > > It is possible to confirm from our announcements that links to the > archives of the CRISP team mailing list was intended to be shared from > publication of the first draft proposal: > > "Details of all the CRISP team's work to date, including recordings, > minutes and agendas of all CRISP teleconferences and a public archive > of the internal CRISP team mailing list, are available at: > https://nro.net/crisp-team" > > https://www.nro.net/news/first-draft-proposal-of-the-internet-number-commun… > > https://www.nro.net/news/internet-number-community-iana-stewardship-proposa… > > >> >> 4) Refusal to deal with essential aspects of the proposal: The CRISP team >> refused to deal with essential aspects of proposal such as the contract >> renewal process, contract duration, jurisdiction, arbitration process, >> review process, high level details of the contract, intellectual property >> rights, charter of the review team and service levels. The CRISP team > cited >> these essential aspects as outside the scope of the CRISP mandate. If the >> CRISP mandate is indeed so limited, then its incomplete proposal > should be >> returned to the RIR community with the suggestion of expanding the > mandate >> of the CRISP team. Note that the charter of the CRISP team, which was >> prepared by the NRO EC in a top-down manner, does not suggest that such >> essential aspects should be excluded from the proposal. This limited >> interpretation of the agenda and issues by the CRISP team is against the >> ethos of a bottom-up multi-stakeholder process. > > As noted above, a concrete record of all the concerns raised by the > community on various mailing lists was prepared by the CRISP team and > made available at: > https://www.nro.net/crisp-iana-xfer-summary-discussion-08012015 > > This spreadsheet, the records and notes from CRISP teleconferences and > the archived mails on both the internal and public mailing lists > demonstrate that the CRISP team closely considered all issues, concerns > or suggestions raised by the community via ianaxfer(a)nro.net or the > regional discussion lists. Where specific suggestions were not reflected > in the proposal, detailed justification was provided to the community > via the ianaxfer mailing list. > > While the CRISP team did note certain constraints on its remit, as it > understood that remit, the issues noted by Guru Acharya were addressed > specifically in the following mails to the public <ianaxfer(a)nro.net> > mailing list: > > Contract details in general, including renewal process, duration: > https://www.nro.net/pipermail/ianaxfer/2015-January/000213.html > https://www.nro.net/pipermail/ianaxfer/2014-December/000135.html > https://www.nro.net/pipermail/ianaxfer/2014-December/000143.html > > Jurisdiction: > https://www.nro.net/pipermail/ianaxfer/2015-January/000331.html > > Arbitration process: > https://www.nro.net/pipermail/ianaxfer/2015-January/000331.html > > Review process: > https://www.nro.net/pipermail/ianaxfer/2014-December/000134.html > https://www.nro.net/pipermail/ianaxfer/2015-January/000172.html > > Intellectual property rights: > https://www.nro.net/pipermail/ianaxfer/2014-December/000145.html > https://www.nro.net/pipermail/ianaxfer/2014-December/000127.html > https://www.nro.net/pipermail/ianaxfer/2015-January/000342.html > https://www.nro.net/pipermail/ianaxfer/2015-January/000173.html > > Charter of the review team: > https://www.nro.net/pipermail/ianaxfer/2015-January/000320.html > > While developing the proposal, the CRISP team was conscious about its > remit and responsibility. In the process of addressing issues and the > elements of the proposal the team felt that it was important to identify > the critical components and implementation requirements, rather than > work out the actual implementation details. Our position was that the > latter should be developed by qualified RIR legal teams following the > best practices in this field. As stated in the response to the ICG "The > RIRs, as the contractual party of this agreement, will draft the > specific language of this agreement. During the drafting process, the > RIRs are expected to consult their respective RIR communities, and that > the drafting process will be guided by the principles listed below." > [Response to the ICG RFP on the IANA from the Internet Number Community, > p11] > > We believe that the proposal submitted to the ICG meets the expectations > of the numbers community, while not extending into areas beyond the > authority or expertise of the CRISP team. > > I hope that this effectively addresses the issues raised in this email, > and I would be happy to expand further on any issues you feel could > benefit from more explanation. > > > Yours sincerely, > Izumi Okutani > Chair, the CRISP Team > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] CRISP - Process Concerns
by Alissa Cooper Feb. 5, 2015

Feb. 5, 2015

Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: Re: [NRO-IANAXFER] CRISP - Process Concerns > Date: February 4, 2015 at 11:49:32 AM PST > To: Alissa Cooper <alissa(a)cooperw.in> > Cc: ianaxfer(a)nro.net > > Hi Alissa and colleagues on the IANAXFER list, > > > I would like to inform you that the CRISP Team have submitted our > reponse to the following two posts with comments about the CRISP Team > and the proposal from the number resources community. > > http://forum.icann.org/lists/icg-forum/msg00024.html > http://forum.icann.org/lists/icg-forum/msg00020.html > > As our reponse is not reflected immediately on the web archives, I will > foward them to this list as seperate e-mails to follow. > > > Best Regards, > Izumi Okutani > Chair, the CRISP Team > > On 2015/02/04 5:17, Alissa Cooper wrote: >> Hi Izumi, >> >> As of now we are not asking for a specific response from you. We will be discussing the CRISP proposal on Feb 6-7. If we have specific questions for you, we will send them to you after that. >> >> Best, >> Alissa >> >> On Feb 2, 2015, at 7:10 AM, Izumi Okutani <izumi(a)nic.ad.jp> wrote: >> >>> Hi Alissa, >>> >>> >>> Thank you for the guidance. As advised, the CRISP Team will prepare the >>> response just as if we have received comments on the ianaxfer(a)nro.net. >>> >>> As a reference for our preparation - >>> is there a date and time (deadline) which the ICG expects response from >>> the CRISP Team, for the comments the ICG has forwarded to this list? >>> >>> If there is, I would appreciate it if you could share it with us. >>> >>> Thank you and the ICG once again for sharing the comments posted on >>> icg-forum and bringing them to our attention. >>> >>> >>> Thanks >>> Izumi, on behalf of the CRISP Team >>> >>> On 2015/01/31 9:55, Alissa Cooper wrote: >>>> Hi Izumi, >>>> >>>> I wanted to share the note below from the ICG. >>>> >>>> The ICG suggests that you take all comments the ICG has forwarded to you from http://forum.icann.org/lists/icg-forum/ about your proposal or the process of creating it as if they were made inside your process and address them as you normally would. >>>> >>>> The ICG is aware of the comments. If the ICG has specific questions to you based on the comments we will explicitly ask them to you as part of our normal ICG process just like any other question we may have. >>>> >>>> Let me know if you have questions. >>>> >>>> Thanks, >>>> Alissa on behalf of the ICG >>>> >>>> On Jan 23, 2015, at 9:46 AM, Izumi Okutani <izumi(a)nic.ad.jp> wrote: >>>> >>>>> Thank you Alissa for sharing this post with us. >>>>> >>>>> Just to share the CRISP Team's discussions with everyone, we are aware >>>>> of this post as well as the earlier post submitted to icg-forum shared >>>>> by John Curran. >>>>> >>>>> Since we see icg-forum as the communication channel for the community to >>>>> the ICG, we do not feel appropriate to respond directly to the post(s) >>>>> to icg-forum as the CRISP Team at this stage. >>>>> >>>>> If the ICG considers the response is needed from the CRISP Team and >>>>> requests us to do so, we are happy to prepare our response. We would >>>>> appreciate to have guidance from the ICG, whether it helps the ICG to >>>>> have response from the CRISP Team to the comment posted to icg-forum. >>>>> >>>>>> http://forum.icann.org/lists/icg-forum/msg00024.html >>>>> >>>>> Thank you Alissa for keeping us informed of the post which is relevant >>>>> to our proposal. Please let us know if there is anything the CRISP Team >>>>> can do to support the ICG in your considerations and activities. >>>>> >>>>> >>>>> Best Regards, >>>>> Izumi Okutani >>>>> The CRISP Team Chair >>>>> >>>>> >>>>> On 2015/01/23 3:32, Alissa Cooper wrote: >>>>>> http://forum.icann.org/lists/icg-forum/msg00024.html >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> ianaxfer mailing list >>>>>> ianaxfer(a)nro.net >>>>>> https://www.nro.net/mailman/listinfo/ianaxfer >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> ianaxfer mailing list >>>>> ianaxfer(a)nro.net >>>>> https://www.nro.net/mailman/listinfo/ianaxfer >>>> >>>> >>> >> >

1 0

Welcome Alan Barrett
by Alissa Cooper Feb. 5, 2015

Feb. 5, 2015

Hi all, I wanted to welcome Alan Barrett to the ICG. Alan is participating on behalf of the NRO and replacing Adiel. Alan, please send us all a note introducing yourself. Looking forward to working with you. Alissa

8 8