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

2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List
by Petrit Hasani 04 Nov '19

04 Nov '19

Dear colleagues, A new RIPE Policy proposal, 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space", is now available for discussion in the Routing Working Group This proposal aims to instructs the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-08 This proposed policy may be of interest to the Address Policy working group as well. Therefore, we encourage you to review this proposal and send your comments to <routing-wg(a)ripe.net> before 29 November 2019. -- Petrit Hasani Policy Officer RIPE NCC

10 18

Re: [address-policy-wg] [policy-announce] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
by Sander Steffann 31 Oct '19

31 Oct '19

Hi, > This proposal aims to instructs the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control. > > You can find the full proposal at: > > https://www.ripe.net/participate/policies/proposals/2019-08 I have read the policy and I don't see any downside to doing this. Creating those ROAs reflects the intention correctly, so let's do this. Cheers, Sander

2 1

2019-06 New Policy Proposal (Multiple Editorial Changes in IPv6 Policy)
by Marco Schmidt 10 Oct '19

10 Oct '19

Dear colleagues, A new RIPE Policy proposal, 2019-06, "Multiple Editorial Changes in IPv6 Policy" is now available for discussion. This proposal aims to remove obsoleted text and simplify the IPv6 policy. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-06 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 6 November 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

5 4

Re: [address-policy-wg] 2019-06 New Policy Proposal (Multiple Editorial Changes in IPv6 Policy)
by Carlos Friaças 10 Oct '19

10 Oct '19

Hi, +1 support. Regards, Carlos ---------- Forwarded message ---------- Date: Tue, 8 Oct 2019 16:51:14 From: Nick Hilliard <nick(a)foobar.org> To: Sander Steffann <sander(a)steffann.nl> Cc: RIPE Address Policy Working Group <address-policy-wg(a)ripe.net> Subject: Re: [address-policy-wg] 2019-06 New Policy Proposal (Multiple Editorial Changes in IPv6 Policy) Sander Steffann wrote on 08/10/2019 15:01: >> A new RIPE Policy proposal, 2019-06, "Multiple Editorial Changes in IPv6 >> Policy" >> is now available for discussion. >> >> This proposal aims to remove obsoleted text and simplify the IPv6 policy. > > I think this is a sensible update. Support. agreed - this looks like a good idea, and thanks to Jordi for doing some housekeeping in this area. Nick

2 1

Re: [address-policy-wg] [policy-announce] 2019-05 Proposal Accepted (Revised IPv4 assignment policy for IXPs)
by Erik Bais 10 Oct '19

10 Oct '19

Thanks for the update Marco. And thanks to all the WG members and the proposal authors for making this happen for the community. Regards, Erik Bais Co-chair AP-WG. On 10/10/2019, 12:01, "policy-announce on behalf of Marco Schmidt" <policy-announce-bounces(a)ripe.net on behalf of mschmidt(a)ripe.net> wrote: Dear colleagues, Consensus has been reached on 2019-05, "Revised IPv4 assignment policy for IXPs". This proposal aimed to increase the reserved IPv4 pool for IXPs to a /15 and finetune assignment criteria. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-05 The new RIPE Document is called ripe-730 and is available at: https://www.ripe.net/publications/docs/ripe-730 We have already implemented the pool management part of this proposal (185.0.0.0/16 and the IPv4 fragments smaller than /24 have been added to the reserved IPv4 pool for IXPs). We estimate that this proposal will take around two months to fully implement. We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided us with your input. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-05 Proposal Accepted (Revised IPv4 assignment policy for IXPs)
by Marco Schmidt 10 Oct '19

10 Oct '19

Dear colleagues, Consensus has been reached on 2019-05, "Revised IPv4 assignment policy for IXPs". This proposal aimed to increase the reserved IPv4 pool for IXPs to a /15 and finetune assignment criteria. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-05 The new RIPE Document is called ripe-730 and is available at: https://www.ripe.net/publications/docs/ripe-730 We have already implemented the pool management part of this proposal (185.0.0.0/16 and the IPv4 fragments smaller than /24 have been added to the reserved IPv4 pool for IXPs). We estimate that this proposal will take around two months to fully implement. We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided us with your input. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

62.222.0.0/15
by Ronald F. Guilmette 10 Oct '19

10 Oct '19

I didn't realize till now that RIPE NCC was still giving out IPv4 /15 blocks as recently as August. Now that I know, may I have one too please? ================================================================= inetnum: 62.222.0.0 - 62.223.255.255 netname: IE-COOLWAVE-20010321 country: IE org: ORG-CCL78-RIPE admin-c: DW5409-RIPE tech-c: DW5409-RIPE status: ALLOCATED PA mnt-by: mnt-ie-coolwave-1 mnt-by: RIPE-NCC-HM-MNT created: 2019-08-20T11:55:01Z last-modified: 2019-08-20T11:55:01Z source: RIPE

12 23

2019-05 Last Call for Comments (Revised IPv4 assignment policy for IXPs)
by Marco Schmidt 08 Oct '19

08 Oct '19

Dear colleagues, Proposal 2019-05, "Revised IPv4 assignment policy for IXPs", is now in Concluding Phase. This proposal aims to increase the reserved IPv4 pool for IXPs to a /15 and finetune assignment criteria. The WG co-chairs have declared that rough consensus has been reached and the proposal will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of this four week Concluding Phase is to give an opportunity to present well-justified objections for those who missed the previous two phases and wish to oppose the proposal. Any objection must be made by 8 October 2019 and must be supported by an explanation. If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the WG co-chairs for final consensus. As this policy change has reaches rough consensus, the RIPE NCC has now reserved 185.0.0.0/16 for this policy change. If final consensus is achieved, the /16 will be used as per the policy proposal, and alternatively, if the proposal is withdrawn, the address space will be returned to the IPv4 pool for allocations. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-05 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 8 October 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

2 1

RIPE 78 Address Policy WG Draft Minutes
by Marco Schmidt 08 Oct '19

08 Oct '19

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

1 0

Re: [address-policy-wg] 2019-05 Policy Proposal (Revised IPv4 assignment policy for IXPs) - Moving to Last Call
by Andy Davidson 07 Oct '19

07 Oct '19

Still support this proposal.

9 8