Re: [address-policy-wg] 2013-03 Proposal Accepted (Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text)
Dear all, I'm unsure now. Is ripe-583 (Provider Aggregatable (PA) Assignment Request Form) still valid? Regarding the new policy-text and the discussion before it's now unclear. At least for me. ;-) Thank you in advance for a clarification. Best regards, Robert Robert Güntensperger Swisscom (Switzerland) Ltd.
-----Original Message----- From: address-policy-wg-bounces@ripe.net [mailto:address-policy-wg- bounces@ripe.net] On Behalf Of Marco Schmidt Sent: Tuesday, February 04, 2014 4:36 PM To: policy-announce@ripe.net Cc: address-policy-wg@ripe.net Subject: [address-policy-wg] 2013-03 Proposal Accepted (Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text)
Dear colleagues,
Consensus has been reached, and the proposal for a change to RIPE Document ripe-599, "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:
https://www.ripe.net/ripe/policies/proposals/2013-03
The new RIPE Document is called ripe-604 and is available at:
https://www.ripe.net/ripe/docs/ripe-604
The RIPE NCC has already begun preparations to implement this policy proposal, which will require updating many internal and external procedures and related tools to ensure we continue to provide efficient service. We estimate it may take up to three months to make these changes and fully implement the policy proposal. In the meantime, the current procedures will remain in effect. The RIPE NCC will send another announcement once the implementation is complete and the new procedures are in place.
Thank you to everyone who provided input.
Regards
Marco Schmidt Policy Development Officer RIPE NCC
On 05/02/2014 10:25, Robert.Guentensperger@swisscom.com wrote:
I'm unsure now. Is ripe-583 (Provider Aggregatable (PA) Assignment Request Form) still valid? Regarding the new policy-text and the discussion before it's now unclear. At least for me. ;-)
I think it probably is still required. The policy announcement said:
We estimate it may take up to three months to make these changes and fully implement the policy proposal. In the meantime, the current procedures will remain in effect.
Nick
* Nick Hilliard
I think it probably is still required. The policy announcement said:
We estimate it may take up to three months to make these changes and fully implement the policy proposal. In the meantime, the current procedures will remain in effect.
Question is, may the LIRs update their procedures right away? Or are LIRs expected to wait until the NCC has updated procedures, at which point the LIRs are permitted to follow suit? My expectation would be the former. Otherwise, publishing ripe-604 as the current policy at this point in time would just be confusing LIRs and others who might not follow policy development closely. How are they to know that they should ignore ripe-604 for now, and instead operate according to «obsoleted» ripe-599? Tore
On 06/02/2014 09:48, Tore Anderson wrote:
Question is, may the LIRs update their procedures right away?
that would be very good indeed. Nick
Dear colleagues, Thank you for your queries. The RIPE NCC is now applying the new policy described in the updated RIPE Document, “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”. LIRs may update their processes accordingly. While the new policy now applies, there will be an implementation period as we update our own internal processes and procedures. As the new policy makes a big change to the way the RIPE NCC handles IPv4, this will mean updating our supporting software and documentation, and reviewing how we ensure correct registrations and explain our processes externally. Implementing the new policy will also mean updating the forms that LIRs send in to the RIPE NCC. This will take some time, and so for now, while the evaluation criteria are new, the processes will remain the same. The RIPE NCC will send another announcement when the implementation is complete and the new forms and procedures are in place. We hope this answers your questions. Kind regards Marco Schmidt Policy Development Officer RIPE NCC On 2/5/14 11:25 AM, Robert.Guentensperger@swisscom.com wrote:
Dear all,
I'm unsure now. Is ripe-583 (Provider Aggregatable (PA) Assignment Request Form) still valid? Regarding the new policy-text and the discussion before it's now unclear. At least for me. ;-)
Thank you in advance for a clarification.
Best regards, Robert
Robert Güntensperger Swisscom (Switzerland) Ltd.
-----Original Message----- From: address-policy-wg-bounces@ripe.net [mailto:address-policy-wg- bounces@ripe.net] On Behalf Of Marco Schmidt Sent: Tuesday, February 04, 2014 4:36 PM To: policy-announce@ripe.net Cc: address-policy-wg@ripe.net Subject: [address-policy-wg] 2013-03 Proposal Accepted (Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text)
Dear colleagues,
Consensus has been reached, and the proposal for a change to RIPE Document ripe-599, "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:
https://www.ripe.net/ripe/policies/proposals/2013-03
The new RIPE Document is called ripe-604 and is available at:
https://www.ripe.net/ripe/docs/ripe-604
The RIPE NCC has already begun preparations to implement this policy proposal, which will require updating many internal and external procedures and related tools to ensure we continue to provide efficient service. We estimate it may take up to three months to make these changes and fully implement the policy proposal. In the meantime, the current procedures will remain in effect. The RIPE NCC will send another announcement once the implementation is complete and the new procedures are in place.
Thank you to everyone who provided input.
Regards
Marco Schmidt Policy Development Officer RIPE NCC
participants (4)
-
Marco Schmidt -
Nick Hilliard -
Robert.Guentensperger＠swisscom.com -
Tore Anderson