- address-policy-wg - mailman.ripe.net

APNIC temporarily freezing v4 transfers to RIPE NCC?
by Nick Hilliard 12 Mar '15

12 Mar '15

thanks to Tore for pointing this out, but page 6 of: > http://www.apnic.net/__data/assets/pdf_file/0011/80786/apnic-ec-minutes-201… contains the following: > 21. Inter-RIR transfer policy discussion > > The EC considered the Inter-RIR transfer policy discussions (attached). > > The EC unanimously resolved to place a temporary moratorium on inter RIR > transfer with RIPE NCC, pending discussions and confirmation with APNIC, > ARIN and RIPE communities that such transfers will not change APNIC’s > status as sharing reciprocal, compatible, needs-based policy with ARIN. > > Motion proposed by Paul Wilson, seconded by Akinori Maemura. Could someone from APNIC, ARIN or both explain the background to this decision? I haven't seen any discussions in the RIPE community about this, and without knowing the background it seems peculiar that APNIC feels it necessary to consult ARIN about APNIC->RIPE NCC resource transfers. Nick

10 17

2014-13 Proposal Accepted (Allow AS Number Transfers)
by Marco Schmidt 12 Mar '15

12 Mar '15

Dear colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-525, "Autonomous System (AS) Number Assignment Policies", has been accepted by the RIPE community. This policy change allows the transfer of Autonomous System (AS) numbers within the RIPE NCC service region. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-13 The new RIPE Document is called ripe-638 and is available at: https://www.ripe.net/ripe/docs/ripe-638 We estimate that this proposal will take about three months to fully implement. Details of the implementation status are available at: https://www.ripe.net/lir-services/resource-management/policy-implementation… We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided their input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-07, 2014-08, 2014-10, 2014-11 Proposals Accepted (Language Clarification Proposals)
by Marco Schmidt 11 Mar '15

11 Mar '15

Dear colleagues, Consensus has been reached, and the proposals for changes to the following RIPE Documents have been accepted by the RIPE community: ripe-632, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" ripe-452, "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" ripe-233, "IPv6 Addresses for Internet Root Servers In The RIPE Region" ripe-476, "Allocating/Assigning Resources to the RIPE NCC" These policy changes replace the term "should" with "must" in cases where the previous wording created unwanted ambiguity in policy documents. You can find the full proposals at: http://www.ripe.net/ripe/policies/proposals/2014-07 http://www.ripe.net/ripe/policies/proposals/2014-08 http://www.ripe.net/ripe/policies/proposals/2014-10 http://www.ripe.net/ripe/policies/proposals/2014-11 The new RIPE Documents are called ripe-634, ripe-635, ripe-636 and ripe-637 and are available at: https://www.ripe.net/ripe/docs/ripe-634 https://www.ripe.net/ripe/docs/ripe-637 https://www.ripe.net/ripe/docs/ripe-636 https://www.ripe.net/ripe/docs/ripe-635 Note: the order of the original documents, proposals and new RIPE Documents in the lists above all correspond to one another. These proposals are implemented with immediate effect, as the RIPE NCC's procedures, tools and documentation are already in line with the policy understanding that these updates reflect. Thank you to everyone who provided their input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

Re: [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
by sandrabrown＠ipv4marketgroup.com 11 Mar '15

11 Mar '15

Hi Andrea, At APNIC39 in Fukuoka, I spoke with Adam Gosling of APNIC. He suggested that the APNIC EC would wait for an interpretation and implementation of the new RIPE inter-RIR policy before making a decision. But, as reflected in the discussion already made, he did feel that an APNIC to RIPE transfer would not be subjected to needs justification because he (and APNIC in general) do not interpret APNIC policy as requiring needs justification if the receiving RIR does not. Two comments on this: Why would APNIC to RIPE not require needs justification when APNIC to APNIC does? Secondly, there are so few IPs within APNIC, how often will there ever be IPs transferred from APNIC to RIPE region under the inter-RIR policy? I would not think this is a big transfer path. The reality is that the huge supply of IPs for transfer to RIPE is in ARIN region and this supply is the target of the new RIPE inter-RIR policy. If APNIC never allows transfer to RIPE region, this would be ok from the perspective of supply to RIPE region. In fact this would be preferable to APNIC allowing transfers with no needs justification, such that ARIN then flipped its position to block transfers to APNIC because they could subsequently to transferred to RIPE. A more tangible flaw is that APNIC has no time delay on re-transfers. While ARIN would not allow a transferred block to be re-transferred for 12 months and RIPE would not allow a transferred block to be re-transferred for 24 months, APNIC has no limitation. But this problem exists today for IPs transferred to APNIC; they can immediately be re-transferred within APNIC. No change just because they could now be transferred to RIPE region, so I can't see ARIN complaining about this now. ARIN being concerned with APNIC allowing transfers to APNIC being subsequently transferred to RIPE should not influence the implementation of direct transfers from ARIN to RIPE using the new needs justification criteria of 50% use over 5 years that ARIN had agreed was compatible with its policy. Based on this analysis, I don't see the initial buy-in or non-buy-in by APNIC as a concern. It is ARIN as a supply that is needed. Sandra Brown Message: 3 Date: Tue, 10 Mar 2015 17:03:03 +0000 From: Nick Hilliard <nick(a)inex.ie> To: Andrea Cima <andrea(a)ripe.net>, Address Policy Working Group <address-policy-wg(a)ripe.net> Subject: Re: [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC? Message-ID: <54FF23C7.4020403(a)inex.ie> Content-Type: text/plain; charset=utf-8 Hi Andrea, On 10/03/2015 16:05, Andrea Cima wrote: > While I cannot answer on behalf of the other RIRs, we have given an > update about the inter-RIR transfer policy proposal last week, during > APNIC 39. I hope the video and transcripts will provide you with the > clarification requested (please see session Policy SIG-3) thanks for the reference. The context is located at pages 35-49 of: https://conference.apnic.net/data/39/5-March-Policy-SIG-3.txt and at: https://www.youtube.com/watch?v=2iKK_8iJU6E#t=1h09m11s Nick

1 0

2014-13 Last Call for Comments (Allow AS Number Transfers)
by Marco Schmidt 11 Mar '15

11 Mar '15

Dear colleagues, The proposal described in 2014-13, "Allow AS Number Transfers", is now in its Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made by 10 March 2015 and must be supported by an explanation. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-13 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 10 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

4 4

2014-07, 2014-08, 2014-10, 2014-11 Last Call for Comments (Language Clarification Proposals)
by Marco Schmidt 10 Mar '15

10 Mar '15

Dear colleagues, The proposals described in - 2014-07, Language Clarification in "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" - 2014-08, Language Clarification in "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" - 2014-10, Language Clarification in "IPv6 Addresses for Internet Root Servers In The RIPE Region" - 2014-11, Language Clarification for "Allocating/Assigning Resources to the RIPE NCC", are now in the Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for these proposal has been reached and they will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose one of these proposal. Any objection must be made by 9 March 2015 and must be supported by an explanation. You can find the full proposals at: https://www.ripe.net/ripe/policies/proposals/2014-07 https://www.ripe.net/ripe/policies/proposals/2014-08 https://www.ripe.net/ripe/policies/proposals/2014-10 https://www.ripe.net/ripe/policies/proposals/2014-11 Please e-mail any final comments about these proposals to address-policy-wg(a)ripe.net before 9 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

2 1

2015-01 New Policy Proposal (Alignment of Transfer Requirements for IPv4 Allocations)
by Marco Schmidt 10 Mar '15

10 Mar '15

Dear colleagues, A proposed change to RIPE Document "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" is now available for discussion. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2015-01 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 12 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

22 57

Policy proposal 2014-03 "Remove Multihoming Requirement for AS Number Assignments"
by Sander Steffann 09 Mar '15

09 Mar '15

Hello working group, There has been a lot of discussion regarding policy proposal 2014-03 "Remove Multihoming Requirement for AS Number Assignments". There has been discussion on the the content of the proposal, the impact that the RIPE NCC charging scheme has and on the 'garbage collection' effects of the different ideas people have. We clearly don't have consensus on how to proceed. The working group chairs (Gert Döring and myself) have therefore decided to extend the review phase. Because of the potential impact of the RIPE NCC charging scheme and because the ideas on this policy proposal seem to be diverging at the moment we have decided to extend it to after the RIPE meeting in Amsterdam. We realise this is a relatively long time but we feel that having a live discussion on this policy proposal is the best way forward. Marco will send the formal announcement shortly. Cheers, Sander Steffann Gert Döring APWG chairs

1 0

2014-05 Last Call for Comments (Policy for Inter-RIR Transfers of Internet Resources)
by Marco Schmidt 05 Mar '15

05 Mar '15

Dear colleagues, The proposal described in 2014-05, "Policy for Inter-RIR Transfers of Internet Resources", is now in its Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made by 3 April 2015 and must be supported by an explanation. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-05 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 3 April 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-04 Proposal Accepted (Removing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 04 Mar '15

04 Mar '15

Dear colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-623, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", has been accepted by the RIPE community. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-04 The new RIPE Document is called ripe-632 and is available at: https://www.ripe.net/ripe/docs/ripe-632 The RIPE NCC has already begun preparations to implement this policy proposal. We estimate it may take a few weeks to make these changes and fully implement the policy proposal. Details of the implementation status are available at: https://www.ripe.net/lir-services/resource-management/policy-implementation… We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided their input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-04 New Draft Document and Impact Analysis Published (Removing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 03 Mar '15

03 Mar '15

Dear colleagues, The draft document for version 3.0 of the policy proposal 2014-04, "Removing IPv6 Requirement for Receiving Space from the Final /8", has now been published, along with an impact analysis conducted by the RIPE NCC. Some of the differences from version 2.0 include: - Removal of the IPv6 requirement to receive Pv4 addresses from the RIPE NCC - Related wording adjustments in the title, summary and rationale of the proposal You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-04 The draft document is available at: https://www.ripe.net/ripe/policies/proposals/2014-04/draft We encourage you to read the draft document and send any comments to address-policy-wg(a)ripe.net before 7 January 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

17 23

New on RIPE Labs: RIPE NCC Membership - Developments After Reaching the Last /8
by Mirjam Kuehne 23 Feb '15

23 Feb '15

Dear colleagues, On 14 September 2012, the RIPE NCC started allocating IPv4 addresses based on the last /8 policy. With more than two years passed, we look at the effects this had on membership numbers and demographics. We also look at what the last /8 policy meant for IPv6 uptake. Please find the results on RIPE Labs: https://labs.ripe.net/Members/wilhelm/ripe-ncc-membership-statistics-2014 Kind regards, Mirjm Kuehne RIPE NCC

1 0

2014-12 Draft Document and Impact Analysis Published (Allow IPv6 Transfers)
by Marco Schmidt 16 Feb '15

16 Feb '15

Dear colleagues, The proposal described in 2014-12, "Allow IPv6 Transfers", is now in its Review Phase. The draft document has been published, along with an impact analysis conducted by the RIPE NCC. You can find the full proposal and the impact analysis at: http://www.ripe.net/ripe/policies/proposals/2014-12 and the draft document at: http://www.ripe.net/ripe/policies/proposals/2014-12/draft We encourage you to read the draft document text and send any comments to address-policy-wg(a)ripe.net before 21 January 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

6 10

2014-03 Review Period extended until 12 February 2015 (Remove Multihoming Requirement for AS Number Assignments)
by Marco Schmidt 07 Feb '15

07 Feb '15

Dear colleagues, The Review Period for the proposal 2014-03, "Remove Multihoming Requirement for AS Number Assignments" has been extended until 12 February 2015. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-03 We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards, Marco Schmidt Policy Development Officer RIPE NCC

6 5

2014-13 New Draft Document and Impact Analysis Published (Allow AS Number Transfers)
by Marco Schmidt 06 Feb '15

06 Feb '15

Dear colleagues, The proposal described in 2014-13, "Allow AS Number Transfers", is now in its Review Phase. The draft document has been published, along with an impact analysis conducted by the RIPE NCC. You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-13 and the draft document at: https://www.ripe.net/ripe/policies/proposals/2014-13/draft We encourage you to read the draft document text and send any comments to address-policy-wg(a)ripe.net before 21 January 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

16 18

2014-12 Review Phase Period extended until 10 February 2015 (Allow IPv6 Transfers)
by Marco Schmidt 05 Feb '15

05 Feb '15

Dear colleagues, The Review Phase Period for the proposal 2014-12, "Allow IPv6 Transfers" has been extended until 10 February 2015. We request your feedback, even if you have provided it during the initial Discussion Phase, so that the Working Group Chairs can determine whether there is rough consensus. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-12 We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards, Marco Schmidt Policy Development Officer RIPE NCC

6 5

2014-07 New Draft Document and Impact Analysis Published (Language Clarification in "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region")
by Marco Schmidt 05 Feb '15

05 Feb '15

Dear colleagues, The proposal described in 2014-07, "Language Clarification in "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"", is now in its Review Phase. The draft document has been published, along with an impact analysis conducted by the RIPE NCC. You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-07 The draft document is available at: https://www.ripe.net/ripe/policies/proposals/2014-07/draft We encourage you to read the draft document and send any comments to address-policy-wg(a)ripe.net before 9 January 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

3 3

RIPE NCC Charging Scheme 2016 Discussion
by Nigel Titley 25 Jan '15

25 Jan '15

Dear Colleagues, The RIPE NCC Executive Board has closely followed the ASN discussion on the Address Policy Working Group mailing list. The issue of the RIPE NCC Charging Scheme has been raised, so I'd like to give you an idea of the Board's thinking on this. We hope this will inform the discussion and also give sufficient time for members to give their feedback, which we will take into account when making a Charging Scheme 2016 proposal to present to the General Meeting (GM) in May this year. The issue of reintroducing a charge for ASNs was raised at the last GM in November 2014. You can follow the details of that discussion in the GM minutes: https://www.ripe.net/lir-services/ncc/gm/november-2014/minutes-ripe-ncc-gen… This discussion, interesting though it was, did not result in a conclusive outcome on how the membership would like the Board to proceed with regard to ASNs. It also raised the issue of charging for PI address space. Another issue raised at the previous GM during the discussion on providing RIPE NCC services for Legacy Internet resource holders was that members can vote only to approve or reject the Charging Scheme as a whole and they cannot vote on individual aspects of the Charging Scheme. In trying to address the Charging Scheme-related issues raised, the Board would like to make two statements: Firstly, the Board would like to retain the current "one LIR, one fee" Charging Scheme model that was approved by the membership and which provides fairness, predictability and simplicity for RIPE NCC members. Secondly, the Board strongly believes that the Charging Scheme should be aligned with RIPE Policy. For this reason, there is a separate charge for PI resources that ensures alignment with ripe-452, "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region (2007-01)". With this in mind, the Board would like to offer two different proposals for the Charging Scheme 2016: 1. The Board can propose a Charging Scheme in advance of the May GM and have the membership discuss the proposal. The Board would take the discussion into account before proposing a final Charging Scheme to be voted on by the membership in May. or 2. The Board could take a two-step approach to the Charging Scheme. In May, members would vote on individual issues such as charging for ASNs. The result of the voting would then be used to create a Charging Scheme that would be voted on in the usual way by members at the November GM. The RIPE NCC Executive Board is appointed to represent the interests of the membership. For this reason, we encourage you to give us your feedback on these proposals so that the RIPE NCC Charging Scheme 2016 can come as close as possible to reflecting the wishes of the membership. You can discuss the proposal and related Charging Scheme issues on the Members Discuss mailing list (members-discuss(a)ripe.net <mailto:members-discuss@ripe.net>) or you can contact the Board directly at exec-board(a)ripe.net <mailto:exec-board@ripe.net>. The next Executive Board meeting takes place on 19 March, so we would appreciate your feedback before that date. I will also copy this mail to the Address Policy Working Group mailing list to ensure all interested parties are aware of the Board's thinking. Best regards, Nigel Titley RIPE NCC Executive Board Chairman

5 4

Comments on proposal 2014-04 (Remove the IPv6 Requirement for receiving address space)
by Daniel Davis 23 Jan '15

23 Jan '15

Hi, Our comment on thIs proposal is: We would not support this proposal to Remove the IPv6 Requirement for Receiving Space from the Final /8. This is because his policy encourages ripe members to start the process of using ipv6 addresses, and that given the shortage of ipv4 space migration is becoming increasingly important. By changing this policy we believe this will give out the wrong signals to the industry about ipv6 migration. Best Regards, Daniel Davis Director Blue Sky Systems Limited Tel: 03300 101 550<tel:03300%20101%20550> Mobile: 07718 425 855<tel:07718%20425%20855> Email: daniel(a)blueskysystems.co.uk<mailto:daniel@blueskysystems.co.uk> Web: www.blueskysystems.co.uk<http://www.blueskysystems.co.uk/> Registered Office: Unit 16 Horizon Business Village, 1 Brooklands Road, Weybridge, Surrey, KT13 0TJ<x-apple-data-detectors://1>. Registered in England No: 8856125<tel:8856125>.

10 19

2014-12 Draft Document and Impact Analysis Published (Allow IPv6 Transfers)
by Lukas Wunner 21 Jan '15

21 Jan '15

Hi, > The proposal described in 2014-12, "Allow IPv6 Transfers", > is now in its Review Phase. I fully support this proposal. Best regards, Lukas Wunner (LW26-RIPE)

1 0

(no subject)
by Sascha Luck [ml] 20 Jan '15

20 Jan '15

<nick(a)inex.ie> Cc: address-policy-wg(a)ripe.net Bcc: Subject: Re: [address-policy-wg] late conciliatory response to 2014-03 Reply-To: In-Reply-To: <54BE4A1F.7050008(a)inex.ie> X-Operating-System: FreeBSD 10.1-RELEASE On Tue, Jan 20, 2015 at 12:29:19PM +0000, Nick Hilliard wrote: >On 20/01/2015 12:23, Sascha Luck [ml] wrote: >> All in all, an unelegant solution. Besides, I like the idea of >> a "flat-rate" charging scheme where you pay yor membership fee >> and have all your services for the year covered. > >that would be nice, except ASNs are assigned to end users not >LIRs. A large number of end users with ASNs are not LIRs. Just noticed that 2007-01 *is* in effect for ASNs, so I guess assignments to non-members are not materially affected by the proposal. rgds, Sascha Luck

1 0

Internet Number Resources Approved to the RIPE NCC
by Maria Stafyla 19 Jan '15

19 Jan '15

Dear Colleagues, The RIPE NCC Arbiters Panel has approved a request for an IPv6 PI assignment and an Autonomous System Number (ASN) resource to the RIPE NCC for its resiliency node in Stockholm based on the RIPE Document, "Allocating/Assigning Resources to the RIPE NCC", and the RIPE NCC procedural document, “RIPE NCC Conflict Arbitration Procedure”. You can find the full announcement at: https://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/int… If you have any questions, please send an email to feedback(a)ripe.net Kind regards, Maria Stafyla The secretary of the Arbiters Panel of the RIPE NCC

1 0

2014-04 Last Call for Comments (Removing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 14 Jan '15

14 Jan '15

Dear colleagues, The proposal described in 2014-04, Removing IPv6 Requirement for Receiving Space from the Final /8, is now in its Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made before 12 February 2015 and must be supported by an explanation. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-04 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

Internet Number Community IANA Stewardship Proposal: Final Call for Comments
by Hans Petter Holen 09 Jan '15

09 Jan '15

I believe this is also important to this group, as it sets the framework for future implementation of global policies. Please have a look at this proposal and please let us know if you support this. Hans Petter -------- Forwarded Message -------- Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments Date: Thu, 8 Jan 2015 17:27:53 +0100 From: Nurani Nimpuno <nurani(a)netnod.se> To: RIPE Cooperation Working Group <cooperation-wg(a)ripe.net> Dear colleagues, Today the Consolidated RIR IANA Stewardship Proposal (CRISP) team publishes the second draft of the Internet numbers community proposal on the transition of the IANA stewardship. This is intended as a final call for community feedback ahead of the submitting the finalised proposal to the IANA Stewardship Transition Coordination Group (ICG) on Thursday, 15 January. We understand that many in the RIPE community have a strong interest in this process, and feedback provided in this working group and elsewhere has been crucial in reaching the current draft. While there is still an opportunity to provide comments on the current text, we would also like to strongly encourage RIPE community members in favour of this proposal to express their support on this list or via the ianaxfer(a)nro.net mailing list. A quantifiable level of community support may be important in strengthening the Internet numbers community’s position later in the IANA stewardship transition process. As previously, the timeline for responding is quite tight, with a deadline of Monday, 12 January, for all comments. Best regards, Nurani Nimpuno on behalf of the RIPE CRISP team Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments > Date: 8 januari 2015 17:21:08 CET > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear colleagues, > > > Please find the second draft of the Internet numbers community's > response to the Request For Proposals issued by the IANA Stewardship > Coordination Group (ICG). > > This draft has been prepared by the Consolidated RIR IANA Stewardship > Proposal (CRISP) Team, with considerations of feedback received from the > global community on <ianaxfer(a)nro.net> mailing list. > > We have incorporated the following key points in the second draft: > > - Additional description on contract details, review committee and > intellectual property rights > - Description revised on Section V. NITA Requirements and VI. > Community Process for more clarity > - No changes are made to key elements of the proposal > > The CRISP Team have considered all comments expressed on > <ianaxfer(a)nro.net> mailing list before the deadline of 5th Jan 2015, and > would now like to make the final call for comments from the global > community on the draft proposal, before submitting to the ICG. > > Second Draft proposal: > ------------------------ > Clean Version : > <http://www.nro.net/crisp-proposal-second-draft> > > Redline Version: > <http:/www.nro.net/crisp-proposal-second-draft-change-control> > > The deadline for providing feedback: Mon, 12 January 2015 23:59 UTC > Feedback should be sent to : <ianaxfer(a)nro.net> mailing list > > Community Inputs Considered by the CRISP Team: > ------------------------------------------ > You can check the status of the issues raised by the community and > proposed the CRISP Team positions at: > > <http://www.nro.net/crisp-iana-xfer-summary-discussion-08012015> > > Key dates: > ----------- > Second draft to be published : 8 Jan 2015 > Second draft comments close : 12 Jan 2015, 23:59 UTC > Final proposal to be sent to ICG : 15 Jan 2015 > > How to Engage in Discussions: > ----------------------------- > All global discussions, for the CRISP team to consider as community > feedback, will be conducted at <ianaxfer(a)nro.net> mailing list. > All the CRISP Team discussions are open to observers. > > Next Step: > ----------- > In developing the final draft based on further feedback, the CRISP > Team will ensure it has completed considerations of all substantial > issues raised by the global community, which are compiled in the > published issues list. The proposal will only incorporate issues that > the CRISP team believes have received consensus support from the > community. > > References: > ------------ > * Discussions by the CRISP Team > Details of all the CRISP team's work to date, including recordings, > minutes and agendas of all the CRISP Team teleconferences and a > public archive of the internal CRISP team mailing list, are > available at: > https://nro.net/crisp-team > > * Other links: > - The ICG request for proposals: > <https://www.icann.org/news/announcement-3-2014-09-03-en> > > - The IANA Stewardship Transition Discussion in each RIR region: > <http://www.nro.net/timeline-engagement> > > - First Draft proposal (Edited version) > <http://www.nro.net/crisp-proposal-first-draft-1-1> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

2 2

RIPE 69 Address Policy WG Draft Minutes
by Marco Schmidt 06 Jan '15

06 Jan '15

Dear colleagues, The draft minutes from the Address Policy Working Group sessions at RIPE 69 have now been published: https://www.ripe.net/ripe/groups/wg/ap/minutes/ripe-69 Please let us know of any corrections or amendments. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0