Search results for "2023-04" - address-policy-wg

Re: [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by Maximilian Wilhelm

Anno domini 2023 Sebastian Wiesinger scripsit: > * Angela Dall'Ara <adallara(a)ripe.net> [2023-09-04 11:55]: > > 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. > > I support this proposal. v4 and v6 should be as feature-equal as > possible from a database point of view IMO. +1 Cheers, Max -- "I have to admit I've always suspected that MTBWTF would be a more useful metric of real-world performance." -- Valdis Kletnieks on NANOG

2 years

2023-04 Extended Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by Karen Hung

Dear colleagues, The policy proposal 2023-04, “Add AGGREGATED-BY-LIR status for IPv4 PA assignments” is now in the extended Review Phase. As per the RIPE Policy Development Process (PDP), the purpose of this Review Phase extension is to continue discussing the proposal taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the Working Group (WG) Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. If you support the proposal, please indicate that support with a simple message to the mailing list. If you have objections or would like a change, please provide that feedback to the mailing list. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2023-04 https://www.ripe.net/participate/policies/proposals/2023-04#impact-analysis And the draft document at: https://www.ripe.net/participate/policies/proposals/2023-04/draft We encourage you to read the proposal, impact analysis and draft document and to send any comments to address-policy-wg(a)ripe.net <mailto:address-policy-wg@ripe.net> before 18 January 2024. Kind regards, Karen Hung On behalf of Policy Officer RIPE NCC

1 year, 8 months

2023-04 Review Phase further extended (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by Angela Dall'Ara

Dear colleagues, The Address Policy WG Co-Chairs decided to extend by four more weeks the Review Phase for policy proposal 2023-04, “Add AGGREGATED-BY-LIR status for IPv4 PA assignments”. As per the RIPE Policy Development Process (PDP), the purpose of this Review Phase extension is to continue discussing the proposal taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the Working Group (WG) Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. If you support the proposal, please indicate that support with a simple message to the mailing list. If you have objections or would like a change, please provide that feedback to the mailing list. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2023-04 https://www.ripe.net/participate/policies/proposals/2023-04#impact-analysis And the draft document at: https://www.ripe.net/participate/policies/proposals/2023-04/draft We encourage you to read the proposal, impact analysis and draft document and to send any comments to address-policy-wg(a)ripe.net before 15 February 2024. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 year, 7 months

2023-04 Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by Angela Dall'Ara

Dear colleagues, Policy proposal 2023-04, “Add AGGREGATED-BY-LIR status for IPv4 PA assignments”, is now in the Review Phase. The goal of this proposal is to introduce the AGGREGATED-BY-LIR status for IPv4 PA assignments to reduce LIR efforts in registration and maintenance. This proposal has been updated and it is now at version 2.0. The proposed policy text did not change, the only difference is that the section "Arguments opposing the proposal" includes a reference to the last round of discussion. The RIPE NCC has prepared an impact analysis on this proposal to support the community’s discussion. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2023-04 https://www.ripe.net/participate/policies/proposals/2023-04#impact-analysis And the draft document at: https://www.ripe.net/participate/policies/proposals/2023-04/draft As per the RIPE Policy Development Process (PDP), the purpose of this four-week Review Phase is to continue the discussion of the proposal taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the Working Group (WG) Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and to send any comments to address-policy-wg(a)ripe.net before 20 December 2023. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 year, 9 months

Re: [address-policy-wg] Extend Review Phase for 2023-04 - "Add AGGREGATED-BY-LIR status for IPv4 PA assignments"

by Riccardo Gori

Good morning, +1 support. Regards, Riccardo Il 21/12/2023 19:36, Leo Vegoda ha scritto: > Dear colleagues, > > There's still an active discussion on 2023-04 - "Add AGGREGATED-BY-LIR > status for IPv4 PA assignments". We'll extend the Review Phase until > 18 January 2024. > > You can find the policy proposal, the draft RIPE document, and the > RIPE NCC's Impact Analysis here: > https://www.ripe.net/participate/policies/proposals/2023-04 > > The RIPE NCC will update the proposal web page with the new dates soon. > > Kind regards, > > Leo Vegoda, for the Address Policy WG co-chairs > -- Riccardo Gori e-mail:rgori@wirem.net

1 year, 8 months

2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by Angela Dall'Ara

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

2 years

Re: [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by Cynthia Revström

+1 makes sense to me -Cynthia On Mon, Sep 4, 2023 at 11:54 AM Angela Dall'Ara <adallara(a)ripe.net> wrote: > > 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 > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/address-policy-wg

2 years

Re: [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by André Pettersson

+1 Great proposal. I support this. Kind regards, André Den mån 4 sep. 2023 kl 11:54 skrev Angela Dall'Ara <adallara(a)ripe.net>: > 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 > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/address-policy-wg >

2 years

Re: [address-policy-wg] 2023-04 Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by Peter Hessler

I still support the proposal as-is. The proposed change does not weaken any data that is in the database, and in fact may allow it to be more obvious that these address ranges are used by end users rather than be unclear what their status is. Furthermore, I will state that Denis' objections are not relevant to the proposal. The proposers, various people on the lists (including myself), and the RIPE NCC themselves all state the opposite of what Denis is saying. In addition the proposers have, in my opinion, addressed the concerns stated. -peter On 2023 Nov 21 (Tue) at 11:13:57 +0100 (+0100), Angela Dall'Ara wrote: : :Dear colleagues, : :Policy proposal 2023-04, “Add AGGREGATED-BY-LIR status for IPv4 PA :assignments”, is now in the Review Phase. : :The goal of this proposal is to introduce the AGGREGATED-BY-LIR status for :IPv4 PA assignments to reduce LIR efforts in registration and maintenance. : :This proposal has been updated and it is now at version 2.0. The proposed :policy text did not change, the only difference is that the section :"Arguments opposing the proposal" includes a reference to the last round of :discussion. : :The RIPE NCC has prepared an impact analysis on this proposal to support the :community’s discussion. : :You can find the proposal and impact analysis at: :https://www.ripe.net/participate/policies/proposals/2023-04 :https://www.ripe.net/participate/policies/proposals/2023-04#impact-analysis :And the draft document at: :https://www.ripe.net/participate/policies/proposals/2023-04/draft : :As per the RIPE Policy Development Process (PDP), the purpose of this :four-week Review Phase is to continue the discussion of the proposal taking :the impact analysis into consideration, and to review the full draft RIPE :Policy Document. : :At the end of the Review Phase, the Working Group (WG) Chairs will determine :whether the WG has reached rough consensus. :It is therefore important to provide your opinion, even if it is simply a :restatement of your input from the previous phase. : :We encourage you to read the proposal, impact analysis and draft document and :to send any comments to address-policy-wg(a)ripe.net before 20 December 2023. : :Kind regards, :Angela Dall'Ara :Policy Officer :RIPE NCC

1 year, 8 months

Re: [address-policy-wg] 2023-04 Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)

by Tore Anderson

Hi Jan, On Fri, 2023-12-15 at 14:58 +0100, Jan Ingvoldstad wrote: > Can the proposers please clarify how a change, that is claimed to > change nothing, is a necessary change? > > Unless this is resolved, I oppose the change. Certainly - we are happy to clarify. We believe we are actually talking about two different changes here. The first one is intentional, as it is the actual intended goal of the proposal – namely to allow LIRs to aggregate multiple assignments with the same purpose and contact details into a single aggregated object. For example, if you are an LIR/ISP that today have the following two customer assignments in the database: inetnum: 192.0.2.0 - 192.0.2.127 netname: JAN-ISP country: NO admin-c: JAN-RIPE tech-c: JAN-RIPE status: ASSIGNED PA mnt-by: JAN-MNT source: RIPE inetnum: 192.0.2.128 - 192.0.2.255 netname: JAN-ISP country: NO admin-c: JAN-RIPE tech-c: JAN-RIPE status: ASSIGNED PA mnt-by: JAN-MNT source: RIPE If 2023-04 passes, you will be able to (but will not be required to) replace your above two objects in the database with the following aggregated object, similar to what you already can do in IPv6: inetnum: 192.0.2.0 - 192.0.2.255 netname: JAN-ISP country: NO admin-c: JAN-RIPE tech-c: JAN-RIPE status: AGGREGATED-BY-LIR mnt-by: JAN-MNT source: RIPE You cannot create such aggregated objects today, so that is clearly an intentional change that 2023-04 will bring about. There is no dispute that this change will take place. The second – alleged – change is the one that has been discussed the most on the mailing list. The argument here is that your two ASSIGNED PA objects above are actually in violation of *current* policy, because they delegate all the contact information to you (the ISP/LIR). The claim is that current policy requires non-delegated contact information for the End User to be published in the object (not necessarily in admin-c/tech-c, but “somewhere”). If 2023-04 passes, your two ASSIGNED PA assignments above will definitely be policy compliant (even before they are possibly replaced with an AGGREGATED-BY-LIR object). There is no disagreement about this, as far as we know. So the question is whether or not your two ASSIGNED PA objects are permitted under *current* policy. If they are, then 2023-04 does not change anything in this regard; the “legal status” of your objects will remain the same – i.e., they are not violating policy – after 2023-04 passes (or fails) as it is under current policy. We believe your two objects are not in violation of today’s policy, which means 2023-04 will exact no change to their “legal status”. We have elaborated on why in this message, under the heading «Does 2023-04 change the contact registration requirements for assignments?»: https://www.ripe.net/ripe/mail/archives/address-policy-wg/2023-December/013… We hope this provides the clarification you requested. Best regards, Jeroen and Tore

1 year, 8 months

address-policy-wg search results for query "2023-04"