[CRISP-TEAM] Draft agenda for the 18th CRISP Call

[Sweeting, John]

Janvier

In case you are not getting my personal email maybe using the crisp list will work.

Here is the info for the call that is currently going on:

Webex information is below.

CRISP Team 18th Meeting
Friday, April 24, 2015
1:00 pm  | UTC |  1 hr
Join WebEx meeting
https://ripencc.webex.com/ripencc/j.php?MTID=m4067a2dd09675ad7f7ae25a317a69f1b<https://ripencc.webex.com/ripencc/j.php?MTID=m4067a2dd09675ad7f7ae25a317a69f1b>

Meeting number: 704 615 073
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: 704 615 073
Global call-in numbers  |  Toll-free calling restrictions

On 4/24/15, 9:04 AM, "Janvier Noulaye" <jnoulaye at gmail.com<mailto:jnoulaye at gmail.com>> wrote:

Hi to All,
Could someone provides me a link to access to the meeting ?

/Janvier

2015-04-24 12:51 GMT+01:00 Izumi Okutani <izumi at nic.ad.jp<mailto:izumi at nic.ad.jp>>:
CRISP Team,



Prior to the call today, this is some additional information per each agenda item.
The pdf version is the same in contents.


> 3.  Action Items
>     a. Minutes from the last call

 Circulated within the CRISP Team.
 Waiting to be published on the website.

>     b. Share future steps with the community

 Done. https://www.nro.net/pipermail/ianaxfer/2015-April/000433.html

>     c. Confirm about IPR and the IETF Trust with the IETF

 Follow up e-mail sent by Izumi. No response from the IETF.

>     d. Arrange a call with CWG-Stewardship Chairs

 Request made by Izumi, waiting for CWG-Stewardship Chairs to share the availability.
 The CWG-Names proposal is out now, so need to reconsider what we request for.

>     e. Doodle poll on future call schedule (have some regularity)

 Done. Waiting for the candidates to be fixed.

> 4.  Confirm community feedback
>     a. ARIN35
>     b. Other RIR regions
>     c. Global list

 Request has been made to share SLA Text. A comment made about 7f.
 https://www.nro.net/pipermail/ianaxfer/2015-April/000448.html

 Would anyone from RIRs please be able to share the latest status on the ianaxfer at nro.net<mailto:ianaxfer at nro.net> list?
 I don't want to give the wrong impression that RIRs are holding something up and not transparent.


> 5.  Update on GAO interview

 GAO has been asked by the Chairs of the House Energy and Commerce Committee and its Communications and Technology Subcommittee to review the NTIA's planned transition.

 Nurani and I joined the interview, based on the questions circulated on the CRISP Team mailing list.
 There were two additional questions are reported on the CRISP Team ML:  https://www.nro.net/pipermail/crisp/2015-April/001785.html

 Based on the interview and to have identified additional information needed, Nurani and I will share the updated written response with the CRISP Team before submimission.
 Suggest sharing the response with the numbers community. (I observe support from John, Michael, Andrei)

> 6.  Update on the call with NRO EC
>     a. Overview: What was confirmed, follow up items
>     b. The role (if any) of the CRISP Team in community consultation
>     c. The role (if any) of the CRISP Team in NRO website of discussions at RIR meetings

 a. https://www.nro.net/pipermail/crisp/2015-April/001774.html
 b. The process should be lead by the RIRs. The CRISP Team give observation on whether community input is inline with the intention of the proposal.
 c. My suggestion:
    The draft report can be developed by RIR staff, but before publishing it, the CRISP Team members from that region (and any other member who atteded the meeting) reviews it.
    It will then be endorsed by the NRO EC. This should be shared on the regional and global MLs.

    In parallel, it would be desirable to share broader discussions on the IANA stewardship transition which took place at the RIR meetings, not just on SLA realtime as possible on the global regional MLs.
    Therefore, make sure to post before each RIR meetings on the global MLs, and may be good to have a quick unofficial update of the general discussions at the meeting on IANA from a CRISP Team member from that region.

> 7.  Preparation for ICANN Board panel
>     a. Jurisdiction
>     b. Country of the IANA function operator
>     c. Implications for delay in submission of the proposal
>     d. Ability for RIR community to chose the IANA operator
>     e. IPR
>     f. Gap between traditional negotiations and open community process

 Draft ideas:
 (As a starting point of consulting at the CRISP Team call)

 a. Do we have an opinion this more than the discussions we have had?
    (It should be fair to all parties involved in the IANA Numbering services)

 b. Country of the IANA function operator
    No need to change.
    As seperate topic thereare some discussions in ICANN Accountabilty CCWG about incorporating in the Bylaws for ICANN to have its headquater in the US.

 c. While NTIA states that there is no deadline, one could argue that ambiguity may increase on whether the proposal will be accepted.

 d. This is a possibility, not concrete plan. We have clearly stated the numbers community is satisified with the current IANA operator(ICANN). However having this ability is important.

 e. We consider the IETF Trust as an acceptable option. We are not saying this is the only option and open to coordination with the three operational communities.
    It is important it will be lightweight and to be based on existing mechanisms as much as possible.

 f. We would expect gaps but strong support for open community process. This is based on NTIA's requirements.

Izumi

On 2015/04/22 23:44, Izumi Okutani wrote:
> CRISP Team,
>
>
> Please see the draft agenda for the call on Fri 24th UTC13:00.
> Feedback is welcome.
>
> As you can see we have quite a full agenda, so let's be efficient and I encourage the team to share updates online before the call as much as possible.
>
>
> ---
> 1. Agenda Review
>
> 2.  Update on the CRISP Team Composition
>     a. Welcome new member: Janvier Ngnoulayea
>
> 3.  Action Items
>     a. Minutes from the last call
>     b. Share future steps with the community
>     c. Confirm about IPR and the IETF Trust with the IETF
>     d. Arrange a call with CWG-Stewardship Chairs
>     e. Doodle poll on future call schedule (have some regularity)
>
> 4.  Confirm community feedback
>     a. ARIN35
>     b. Other RIR regions
>     c. Global list
>
> 5.  Update on GAO interview
>
> 6.  Update on the call with NRO EC
>     a. Overview: What was confirmed, follow up items
>     b. The role (if any) of the CRISP Team in community consultation
>     c. The role (if any) of the CRISP Team in NRO website of discussions at RIR meetings
>
> 7.  Preparation for ICANN Board panel
>     a. Jurisdiction
>     b. Country of the IANA function operator
>     c. Implications for delay in submission of the proposal
>     d. Ability for RIR community to chose the IANA operator
>     e. IPR
>     f. Gap between traditional negitiations and open community process
>
> 8.  Next Meeting
>
> 9.  AOB
> ---
>
> Izumi
>
> _______________________________________________
> CRISP mailing list
> CRISP at nro.net<mailto:CRISP at nro.net>
> https://www.nro.net/mailman/listinfo/crisp
>


_______________________________________________
CRISP mailing list
CRISP at nro.net<mailto:CRISP at nro.net>
https://www.nro.net/mailman/listinfo/crisp



________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.nro.net/pipermail/crisp/attachments/20150424/27aa0820/attachment.html>