From andrea at ripe.net Mon Jul 16 16:29:30 2018 From: andrea at ripe.net (Andrea Cima) Date: Mon, 16 Jul 2018 16:29:30 +0200 Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) Message-ID: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> Dear All, Policy proposal 2018-03 aims at fixing outdated information in IPv4 Policy, like outdated references or values of inetnum objects in the RIPE Database. While I am aware this is not the most exciting of the current policy proposals, it is important to keep the content of the IPv4 policy up-to-date. The review phase for this proposed policy change will end this week, and in order to proceed with the PDP this proposal needs your input, whether you support or oppose the changes. You can find the full proposal here: https://www.ripe.net/participate/policies/proposals/2018-03 Thank you in advance for your support and best regards, Andrea Cima RIPE NCC From noc at ntx.ru Mon Jul 16 16:45:38 2018 From: noc at ntx.ru (Network Operation Center) Date: Mon, 16 Jul 2018 17:45:38 +0300 Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> References: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> Message-ID: Greetings! I support it. It's good idea to keep docs up to date. Nikolay On 16.07.2018 17:29, Andrea Cima wrote: > Dear All, > > Policy proposal 2018-03 aims at fixing outdated information in IPv4 > Policy, like outdated references or values of inetnum objects in the > RIPE Database. > > While I am aware this is not the most exciting of the current policy > proposals, it is important to keep the content of the IPv4 policy > up-to-date. > The review phase for this proposed policy change will end this week, and > in order to proceed with the PDP this proposal needs your input, whether > you support or oppose the changes. > > You can find the full proposal here: > https://www.ripe.net/participate/policies/proposals/2018-03 > > Thank you in advance for your support and best regards, > > Andrea Cima > > RIPE NCC > > > From mike at iptrading.com Mon Jul 16 16:48:10 2018 From: mike at iptrading.com (Mike Burns) Date: Mon, 16 Jul 2018 10:48:10 -0400 Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> References: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> Message-ID: <027101d41d14$0404ec90$0c0ec5b0$@iptrading.com> c. The RIPE NCC, in cooperation with the receiving party, and in compliance with RIPE Policies, will determine the status that the resources to be transferred will receive once they are registered in the RIPE Registry. Hi Andrea, Per the section of the Ripe policy regarding inter-regional transfers extracted above, we have seen recipients of inter-regional transfers into RIPE choose to designate their received space as Allocated-PI. Is this still allowed? The proposal under consideration obsoletes the designation Allocated-PI. Regards, Mike Burns -----Original Message----- From: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] On Behalf Of Andrea Cima Sent: Monday, July 16, 2018 10:30 AM To: address-policy-wg at ripe.net Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) Dear All, Policy proposal 2018-03 aims at fixing outdated information in IPv4 Policy, like outdated references or values of inetnum objects in the RIPE Database. While I am aware this is not the most exciting of the current policy proposals, it is important to keep the content of the IPv4 policy up-to-date. The review phase for this proposed policy change will end this week, and in order to proceed with the PDP this proposal needs your input, whether you support or oppose the changes. You can find the full proposal here: https://www.ripe.net/participate/policies/proposals/2018-03 Thank you in advance for your support and best regards, Andrea Cima RIPE NCC From andrea at ripe.net Tue Jul 17 14:29:57 2018 From: andrea at ripe.net (Andrea Cima) Date: Tue, 17 Jul 2018 14:29:57 +0200 Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <027101d41d14$0404ec90$0c0ec5b0$@iptrading.com> References: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> <027101d41d14$0404ec90$0c0ec5b0$@iptrading.com> Message-ID: <8a225d6b-d2e1-7ab8-06cd-4d2089d8a5ae@ripe.net> Hi Mike, Thank you for your question. During an Inter-RIR transfer we have never been asked to register resources with the status ALLOCATED PI. This is due to the fact that neither ARIN nor APNIC are using the status ALLOCATED PI in their databases. Furthermore holders of Legacy resources being transferred to the RIPE region can choose to retain to the Legacy status or convert the status to ALLOCATED PA or ASSIGNED PI. The RIPE Community decided that the status ALLOCATED PI is outdated and conflicts with current policies in regards to the registration requirements for independent resources. For this reason the RIPE NCC has been running a project converting, in cooperation with resource holders, all IPv4 ranges with status ALLOCATED PI to either ALLOCATED PA or ASSIGNED PI. As a consequence the RIPE Database does not contain anymore inetnum objects with the status ALLOCATED PI. This is one of the reasons why this proposal suggests removing such outdated information from the IPv4 policy. I hope this clarifies your question. Do you have an opinion about this policy proposal? Thank you again and best regards, Andrea Cima RIPE NCC On 16/07/2018 16:48, Mike Burns wrote: > c. The RIPE NCC, in cooperation with the receiving party, and in compliance with RIPE Policies, will determine the status that the resources to be transferred will receive once they are registered in the RIPE Registry. > > Hi Andrea, > > Per the section of the Ripe policy regarding inter-regional transfers extracted above, we have seen recipients of inter-regional transfers into RIPE choose to designate their received space as Allocated-PI. Is this still allowed? > > The proposal under consideration obsoletes the designation Allocated-PI. > > Regards, > Mike Burns > > > -----Original Message----- > From: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] On Behalf Of Andrea Cima > Sent: Monday, July 16, 2018 10:30 AM > To: address-policy-wg at ripe.net > Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) > > Dear All, > > Policy proposal 2018-03 aims at fixing outdated information in IPv4 Policy, like outdated references or values of inetnum objects in the RIPE Database. > > While I am aware this is not the most exciting of the current policy proposals, it is important to keep the content of the IPv4 policy up-to-date. > The review phase for this proposed policy change will end this week, and in order to proceed with the PDP this proposal needs your input, whether you support or oppose the changes. > > You can find the full proposal here: > https://www.ripe.net/participate/policies/proposals/2018-03 > > Thank you in advance for your support and best regards, > > Andrea Cima > > RIPE NCC > > > > From mike at iptrading.com Tue Jul 17 15:34:43 2018 From: mike at iptrading.com (Mike Burns) Date: Tue, 17 Jul 2018 09:34:43 -0400 Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <8a225d6b-d2e1-7ab8-06cd-4d2089d8a5ae@ripe.net> References: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> <027101d41d14$0404ec90$0c0ec5b0$@iptrading.com> <8a225d6b-d2e1-7ab8-06cd-4d2089d8a5ae@ripe.net> Message-ID: <000001d41dd2$ebeb6fc0$c3c24f40$@iptrading.com> Thanks Andrea, you're correct, I mixed up Allocated-PI and Assigned-PI. I support the 2018-03 and attempts to clarify the many status categories. Regards, Mike -----Original Message----- From: Andrea Cima [mailto:andrea at ripe.net] Sent: Tuesday, July 17, 2018 8:30 AM To: Mike Burns ; address-policy-wg at ripe.net Subject: Re: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) Hi Mike, Thank you for your question. During an Inter-RIR transfer we have never been asked to register resources with the status ALLOCATED PI. This is due to the fact that neither ARIN nor APNIC are using the status ALLOCATED PI in their databases. Furthermore holders of Legacy resources being transferred to the RIPE region can choose to retain to the Legacy status or convert the status to ALLOCATED PA or ASSIGNED PI. The RIPE Community decided that the status ALLOCATED PI is outdated and conflicts with current policies in regards to the registration requirements for independent resources. For this reason the RIPE NCC has been running a project converting, in cooperation with resource holders, all IPv4 ranges with status ALLOCATED PI to either ALLOCATED PA or ASSIGNED PI. As a consequence the RIPE Database does not contain anymore inetnum objects with the status ALLOCATED PI. This is one of the reasons why this proposal suggests removing such outdated information from the IPv4 policy. I hope this clarifies your question. Do you have an opinion about this policy proposal? Thank you again and best regards, Andrea Cima RIPE NCC On 16/07/2018 16:48, Mike Burns wrote: > c. The RIPE NCC, in cooperation with the receiving party, and in compliance with RIPE Policies, will determine the status that the resources to be transferred will receive once they are registered in the RIPE Registry. > > Hi Andrea, > > Per the section of the Ripe policy regarding inter-regional transfers extracted above, we have seen recipients of inter-regional transfers into RIPE choose to designate their received space as Allocated-PI. Is this still allowed? > > The proposal under consideration obsoletes the designation Allocated-PI. > > Regards, > Mike Burns > > > -----Original Message----- > From: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] On > Behalf Of Andrea Cima > Sent: Monday, July 16, 2018 10:30 AM > To: address-policy-wg at ripe.net > Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing > Outdated Information in the IPv4 Policy) > > Dear All, > > Policy proposal 2018-03 aims at fixing outdated information in IPv4 Policy, like outdated references or values of inetnum objects in the RIPE Database. > > While I am aware this is not the most exciting of the current policy proposals, it is important to keep the content of the IPv4 policy up-to-date. > The review phase for this proposed policy change will end this week, and in order to proceed with the PDP this proposal needs your input, whether you support or oppose the changes. > > You can find the full proposal here: > https://www.ripe.net/participate/policies/proposals/2018-03 > > Thank you in advance for your support and best regards, > > Andrea Cima > > RIPE NCC > > > > From Piotr.Strzyzewski at polsl.pl Tue Jul 17 20:42:19 2018 From: Piotr.Strzyzewski at polsl.pl (Piotr Strzyzewski) Date: Tue, 17 Jul 2018 20:42:19 +0200 Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> References: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> Message-ID: <20180717184219.GB12818@hydra.ck.polsl.pl> Dear Andrea, please do go forward with that. I support the proposal. Piotr -- Piotr Strzy?ewski Silesian University of Technology, Computer Centre Gliwice, Poland From dominik at clouvider.co.uk Tue Jul 17 21:55:17 2018 From: dominik at clouvider.co.uk (Dominik Nowacki) Date: Tue, 17 Jul 2018 19:55:17 +0000 Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <20180717184219.GB12818@hydra.ck.polsl.pl> References: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net>, <20180717184219.GB12818@hydra.ck.polsl.pl> Message-ID: <4469BAB5-9268-4601-9C3E-CE711114A3E3@clouvider.co.uk> Dear Colleagues, We support the proposal. With Kind Regards, Dominik Nowacki Clouvider Limited is a limited company registered in England and Wales. Registered number: 08750969. Registered office: 88 Wood Street, London, United Kingdom, EC2V 7RS. Please note that Clouvider Limited may monitor email traffic data and also the content of email for the purposes of security and staff training. This message contains confidential information and is intended only for the intended recipient. If you do not believe you are the intended recipient you should not disseminate, distribute or copy this e-mail. Please notify abuse at clouvider.net of this e-mail immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Clouvider Limited nor any of its employees therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. On 17 Jul 2018, at 19:42, Piotr Strzyzewski > wrote: Dear Andrea, please do go forward with that. I support the proposal. Piotr -- Piotr Strzy?ewski Silesian University of Technology, Computer Centre Gliwice, Poland -------------- next part -------------- An HTML attachment was scrubbed... URL: From sander at steffann.nl Wed Jul 18 00:31:57 2018 From: sander at steffann.nl (Sander Steffann) Date: Wed, 18 Jul 2018 00:31:57 +0200 Subject: [address-policy-wg] Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> References: <81ef8f8f-6e88-1343-9c78-e9355049b875@ripe.net> Message-ID: <326A5492-40DD-4A1A-869F-442AB8AAE236@steffann.nl> Hi Andrea, > Policy proposal 2018-03 aims at fixing outdated information in IPv4 Policy, like outdated references or values of inetnum objects in the RIPE Database. > > While I am aware this is not the most exciting of the current policy proposals, it is important to keep the content of the IPv4 policy up-to-date. > The review phase for this proposed policy change will end this week, and in order to proceed with the PDP this proposal needs your input, whether you support or oppose the changes. Strong support, keeping our policy documents clean and relevant is important. Outdated information needs to go or be fixed. Otherwise newcomers will have a hard time (ok, an even harder time) making sense of it all. Cheers! Sander From gert at space.net Thu Jul 19 13:53:09 2018 From: gert at space.net (Gert Doering) Date: Thu, 19 Jul 2018 13:53:09 +0200 Subject: [address-policy-wg] 2018-01 Last Call for Comments (Organisation-LIR Clarification in IPv6 Policy) In-Reply-To: <5E2565A2-CE1B-4499-9000-AFBE4BFD89B8@ripe.net> References: <5E2565A2-CE1B-4499-9000-AFBE4BFD89B8@ripe.net> Message-ID: <20180719115309.GA60038@Space.Net> Dear WG, On Wed, Jun 13, 2018 at 02:32:31PM +0200, Marco Schmidt wrote: > Proposal 2018-01, "Organisation-LIR Clarification in IPv6 Policy", is now in Concluding Phase. [..] > Any objection must be made by 12 July 2018 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 Chairs for consensus. No comment has been received in Last Call. As per the PDP, this is the only phase where "silence is consent" - so, no objections. I declare we have consensus on this proposal :-) thanks for all your input, Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From erik at bais.name Mon Jul 23 10:03:02 2018 From: erik at bais.name (Erik Bais) Date: Mon, 23 Jul 2018 08:03:02 +0000 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) Message-ID: Dear WG. While we are still getting used to switching hats/roles between Sander and myself, we are currently at the time of seeing the first official ML post in my new role as WG chair. With Sander stating his support on the 2018-03 policy and showing his ?renewed? community role again (and the support of : Mike, Piotr, Dominik and Nikolay), the review phase has come to an end. There were no objections or outstanding questions on the ML regarding the policy proposal and with that result we (The WG chairs) agree that we move the policy to Last Call. If there are specific questions that you might have regarding this policy proposal, please ask them on the ML. And if you (still) agree with the policy moving forward, please state your support here on our ML. Kind regards, Erik Bais APWG Chair -------------- next part -------------- An HTML attachment was scrubbed... URL: From mschmidt at ripe.net Mon Jul 23 14:42:54 2018 From: mschmidt at ripe.net (Marco Schmidt) Date: Mon, 23 Jul 2018 14:42:54 +0200 Subject: [address-policy-wg] 2018-01 Proposal Accepted (Organisation-LIR Clarification in IPv6 Policy) Message-ID: Dear colleagues, Consensus has been reached on 2018-01, "Organisation-LIR Clarification in IPv6 Policy". The goal of this proposal was to clarify the wording used in RIPE-699 regarding terms such as "organisation" and "LIR". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-01 The new RIPE Document is ripe-707 and is available at: https://www.ripe.net/publications/docs/ripe-707 We estimate that this proposal will take around two weeks 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 input. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From mschmidt at ripe.net Tue Jul 24 15:13:56 2018 From: mschmidt at ripe.net (Marco Schmidt) Date: Tue, 24 Jul 2018 15:13:56 +0200 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) Message-ID: Dear colleagues, Proposal 2018-03, "Fixing Outdated Information in the IPv4 Policy", is now in Concluding Phase. This proposal aims to fix outdated information in the RIPE Policy "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". The WG co-chair has 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 22 August 2018 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 Chairs for consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-03 Please e-mail any final comments about this proposal to before 22 August 2018. Regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum