[Internal-cg] Proposal approval and agenda for call #26

[Mueller, Milton L]

Alas, it’s not a rumor, it’s a report from people involved in the negotiations.
Can someone from NRO or an RIR respond, please?

--MM

From: Elise Gerich [mailto:elise.gerich at icann.org]
Sent: Tuesday, March 1, 2016 12:35 PM
To: Mueller, Milton L <milton at gatech.edu>; internal-cg at ianacg.org
Subject: Re: [Internal-cg] Proposal approval and agenda for call #26

Milton,
I am engaged in the conversations with the NRO and it is a false rumor that ICANN is attempting to undermine separability which is one of the CRISP principles.
— Elise

From: Internal-cg <internal-cg-bounces at ianacg.org<mailto:internal-cg-bounces at ianacg.org>> on behalf of "Mueller, Milton L" <milton at gatech.edu<mailto:milton at gatech.edu>>
Date: Tuesday, March 1, 2016 at 6:51 AM
To: "Mueller, Milton L" <milton at gatech.edu<mailto:milton at gatech.edu>>, "internal-cg at ianacg.org<mailto:internal-cg at ianacg.org>" <internal-cg at ianacg.org<mailto:internal-cg at ianacg.org>>
Subject: Re: [Internal-cg] Proposal approval and agenda for call #26

Oh I meant to add this:
I have heard that the in the negotiations between NRO and ICANN over the numbers IANA functions, that ICANN is attempting to undermine separability.
Can the numbers people update on the status of those negotiations and is there a risk that ICANN will not agree to a proper implementation of the CRISP/ICG proposal, one that would allow the numbers community to select an alternate IANA functions operator?

--MM

From: Internal-cg [mailto:internal-cg-bounces at ianacg.org] On Behalf Of Mueller, Milton L
Sent: Tuesday, March 1, 2016 9:49 AM
To: internal-cg at ianacg.org<mailto:internal-cg at ianacg.org>
Subject: Re: [Internal-cg] Proposal approval and agenda for call #26

Apologies for missing the call this morning. I am also in agreement with these proposals.
--MM

From: Internal-cg [mailto:internal-cg-bounces at ianacg.org] On Behalf Of Narelle Clark
Sent: Tuesday, March 1, 2016 7:12 AM
To: Joseph Alhadeff <joseph.alhadeff at oracle.com<mailto:joseph.alhadeff at oracle.com>>; internal-cg at ianacg.org<mailto:internal-cg at ianacg.org>
Subject: Re: [Internal-cg] Proposal approval and agenda for call #26

I am in agreement with these formulations.


1. Agree that v10 is ready.



2. Agree that, per the CWG message, dependencies to CCWG work are complete if or when the current proposal is approved by the chartering organisations.



3. Authorise the ICG chairs to send the proposal to the board without further ICG meeting, if and when the chartering organisations approve the CCWG proposal.


Narelle Clark


From: Internal-cg [mailto:internal-cg-bounces at ianacg.org] On Behalf Of Joseph Alhadeff
Sent: Tuesday, 1 March 2016 8:12 PM
To: internal-cg at ianacg.org<mailto:internal-cg at ianacg.org>
Subject: Re: [Internal-cg] Proposal approval and agenda for call #26

this seems consistent with our charter obligations.
On 3/1/2016 2:47 AM, Jari Arkko wrote:

Trying to cut to the chase a bit.



What is important, I think, is that once (and if) the necessary approvals are in, the ICG can act quickly and does not have to schedule another call before it can send the proposal forward to the board. I recall that it was difficult to setup a virtual meeting during the ICANN week...



So how about this reformulation of Alissa’s two items:



1. Agree that v10 is ready.



2. Agree that, per the CWG message, dependencies to CCWG work are complete if or when the current proposal is approved by the chartering organisations.



3. Authorise the ICG chairs to send the proposal to the board without further ICG meeting, if and when the chartering organisations approve the CCWG proposal.



Jari




_______________________________________________

Internal-cg mailing list

Internal-cg at mm.ianacg.org<mailto:Internal-cg at mm.ianacg.org>

http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20160302/ddff2af2/attachment.html>