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

2023-04 (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
by Leo Vegoda 07 Nov '23

07 Nov '23

Dear WG, The Discussion Phase of policy proposal 2023-04 "Add AGGREGATED-BY-LIR status for IPv4 PA assignments" has now ended. Many thanks to all for your comments. The proposal will now move forward to the Review Phase. The RIPE NCC will prepare an impact analysis and a draft RIPE Document. More details about the phases of the Policy Development Process are published here: https://www.ripe.net/publications/docs/ripe-781 You'll also see an announcement from the RIPE NCC soon. Kind regards, Leo Vegoda for the co-chairs

3 5

Potential fraud in applying for temporary assignments
by Siyuan Miao 25 Oct '23

25 Oct '23

Hi folks We wanted to bring to your attention a matter of concern regarding recent emails from the RIPE member, cn.jiunetwork. They are offering assistance in obtaining temporary IP address assignments from RIPE for one to five years, which seems to conflict with RIPE-801's guidelines. I suggest reviewing past temporary address requests made by them to ensure compliance with RIPE policies and legitimate usage. Original Message from cn.jiunetwork: Now we have new IP address for delivery, it is clean . Subnet size from /24 to /20 ,did you need more ipv4 ? note: we no provide lease service , but if you need , we can help you from RIPE get Temporary Address(/24-/18,TEMPORARY /24 is $1300 years/time, you can purchase 1-5 years ) If you are interested in ordering more, please contact us. my mail is REDACTED -- Siyuan Miao *AS917 | Misaka Network, Inc.* 8 The Green, Ste 6288 Dover, DE 19901

1 0

2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
by Angela Dall'Ara 17 Oct '23

17 Oct '23

Dear colleagues, A new RIPE Policy Proposal, 2023-04, "Add AGGREGATED-BY-LIR status for IPv4 PA assignments" is now available for discussion. This proposal aims to introduce the AGGREGATED-BY-LIR status for IPv4 PA assignments to reduce LIR efforts in registration and maintenance. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2023-04 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 proposers, with the agreement of the WG Chairs, will decide how to proceed with the proposal. The PDP document can be found at: https://www.ripe.net/publications/docs/ripe-781 We encourage you to review this proposal and send your comments to address-policy-wg(a)ripe.net before 3 October 2023. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

26 57

Status IPv6 Policy Draft
by Tobias Fiebig 14 Sep '23

14 Sep '23

Heho, i am currently scrolling over my inbox, and was wondering what the status of the v6 policy draft is (with 87 coming up). Is anyone already working on a draft to discuss? Otherwise, I could take a shot to have something ready closer to 87 which picks up the major points from prior discussions. With best regards, Tobias -- Dr.-Ing. Tobias Fiebig T +31 616 80 98 99 M tobias(a)fiebig.nl

2 1

2023-01 Policy Proposal Accepted and Implemented (Reducing IXP IPv4 assignment default size to a /26)
by Angela Dall'Ara 14 Sep '23

14 Sep '23

Dear colleagues, Consensus has been reached on 2023-01 “Reducing IXP IPv4 assignment default size to a /26”. This proposal modifies in the IPv4 Policy the default size of IPv4 assignments for IXPs from a /24 to /26 and clarifies the return of the assignments previously issued for the IXP peering LAN. The archived policy proposal can be found at: https://www.ripe.net/participate/policies/proposals/2023-01 The new RIPE Document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" is available at: https://www.ripe.net/publications/docs/ripe-804 This proposal is implemented with immediate effect. Thank you to everyone who provided input. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 0

Consensus - 2023-01 - Reducing IXP IPv4 assignment default size to a /26
by Leo Vegoda 12 Sep '23

12 Sep '23

Dear Working Group, Two comments were made during the Last Call phase. These comments did not address the subject of the policy proposal. This means the community has achieved a consensus. The RIPE NCC can proceed with implementation. Our thanks to everyone who contributed to this discussion. Kind regards, Leo Vegoda, for the Address Policy WG co-chairs

2 1

New AS Number Blocks Allocated to the RIPE NCC
by Marco Schmidt 14 Aug '23

14 Aug '23

Dear colleagues, On 10 August 2023, the RIPE NCC received the following AS Number blocks from IANA: 213404-214427 214428-215451 215452-216475 You may want to update your records accordingly. All allocations of AS Numbers made by IANA to RIRs are listed here: https://www.iana.org/assignments/as-numbers/as-numbers.xhtml Kind regards, Marco Schmidt Manager Registration Services RIPE NCC

1 0

Policy Proposal Implemented: 2023-02 “Minimum size for IPv4 Temporary Assignments”
by Angela Dall'Ara 31 Jul '23

31 Jul '23

Dear colleagues, We are pleased to announce that we have fully implemented the RIPE Policy Proposal 2023-02 “Minimum size for IPv4 Temporary Assignments”. This policy sets the default assignment size for IPv4 temporary assignments to a /24 and allows routing requirements to justify the request for more than a /24 for research purposes. The archived policy proposal can be found at:  https://www.ripe.net/participate/policies/proposals/2023-02 The RIPE Document, "Temporary Internet Number Assignment Policies" is available at: https://www.ripe.net/publications/docs/ripe-801 Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 0

2023-01 Last Call for Comments (Reducing IXP IPv4 assignment default size to a /26)
by Angela Dall'Ara 31 Jul '23

31 Jul '23

Dear colleagues,   Proposal 2023-01, "Reducing IXP IPv4 assignment default size to a /26", is now in Concluding Phase.   This proposal modifies the default size of IPv4 assignments for IXPs from a /24 to /26 and clarifies the return of the assignments previously issued for their IXP peering LAN.   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 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 September 2023 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.   You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2023-01   Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 8 September 2023. Kind regards, Angela Dall’Ara Policy Officer RIPE NCC

1 0

Last Call - 2023-01 - Reducing IXP IPv4 assignment default size to a /26
by Leo Vegoda 31 Jul '23

31 Jul '23

Dear Working Group, The issue raised during the Review Phase was resolved. We will move the proposal to Last Call. If you missed the previous discussion and have identified an issue that has not already been resolved, please raise it. Traditionally, Last Call is four weeks. But opening a Last Call on the last day of July and closing it before the end of August might mean that some people miss this announcement. For this reason, we will hold Last Call open until the end of Friday, 8 September. Kind regards, Leo Vegoda, for the Address Policy WG co-chairs

1 0