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

Re: [address-policy-wg] 2014-04 New Policy Proposal (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
by George Giannousopoulos 05 May '14

05 May '14

Hi, I support the proposal. I'll agree with the previous about the distinction between PI and PA. In my mind both were valid in order to get the last /22.. Regards, George On Mon, May 5, 2014 at 4:17 PM, Marco Schmidt <mschmidt(a)ripe.net> wrote: > > Dear colleagues, > > > A proposed change to RIPE Document ripe-606, "IPv4 Address Allocation > and Assignment Policies for the RIPE NCC Service Region", is now > available for discussion. > > > You can find the full proposal at: > > http://www.ripe.net/ripe/policies/proposals/2014-04 > > We encourage you to review this proposal and send your comments to > <address-policy-wg(a)ripe.net> before 3 June 2014. > > > Regards > > Marco Schmidt > Policy Development Officer > RIPE NCC > > >

1 0

Re: [address-policy-wg] 2014-04 New Policy Proposal (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
by Richard Hartmann 05 May '14

05 May '14

+1 for the reasons listed in the proposal. Richard

1 0

Re: [address-policy-wg] 2014-04 New Policy Proposal (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
by Elvis Daniel Velea 05 May '14

05 May '14

Hi, I support this policy proposal. That being said, I do not understand why is this policy proposal making a difference between IPv6 PA and IPv6 PI assignments. I would say that someone can request the last /22 if they have an IPv6 block registered on their name - be it an allocation (ALLOCATED-BY-RIR), a sub-allocation (ALLOCATED-BY-LIR), using an aggregated block (AGGREGATED-BY-LIR) or an IPv6 PI or PA assignment. Regards, Elvis On 05/05/14 15:17, Marco Schmidt wrote: > Dear colleagues, > > > A proposed change to RIPE Document ripe-606, "IPv4 Address Allocation > and Assignment Policies for the RIPE NCC Service Region", is now > available for discussion. > > > You can find the full proposal at: > > http://www.ripe.net/ripe/policies/proposals/2014-04 > > We encourage you to review this proposal and send your comments to > <address-policy-wg(a)ripe.net> before 3 June 2014. > > > Regards > > Marco Schmidt > Policy Development Officer > RIPE NCC > > -- <http://v4escrow.net> Elvis Daniel Velea Chief Business Analyst Email: elvis(a)V4Escrow.net <mailto:elvis@v4escrow.net> US Phone: +1 (702) 475 5914 EU Phone: +3 (161) 458 1914 Recognised IPv4 Broker/Facilitator in: This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received this email in error, please notify the sender immediately and delete the original.Any other use of this email is strictly prohibited.

1 0

Re: [address-policy-wg] Support of https://www.ripe.net/ripe/policies/proposals/2014-03
by lir＠elisa.fi 05 May '14

05 May '14

+1 I support this proposal. Rgds, Ray From: address-policy-wg-bounces(a)ripe.net [mailto:address-policy-wg-bounces@ripe.net] On Behalf Of Elvis Daniel Velea Sent: 5. toukokuuta 2014 14:06 To: address-policy-wg(a)ripe.net Subject: Re: [address-policy-wg] Support of https://www.ripe.net/ripe/policies/proposals/2014-03 Hi, you have my support for this policy change proposal. While the current policy was/is working fine, the RIPE NCC has no tools to actually enforce and/or verify the multihoming of an AS Number once it is issued. cheers, elvis On 05/05/14 12:58, Sander Steffann wrote: Hi Johan, Yes, apologies for voting in the wrong place. Then again, isn't a fake vote the strongest sign of support? I genuinely feel this proposal would strongly benefit the community, and it is one of those "why has this not been written before"-moments for me. Thank you for your very useful message. While the common '+1' messages are useful to determine the difference between 'nobody cares enough to comment' and 'people think this is a useful proposal', actually having comments that show the reasons and/or feelings for supporting a proposal are much much more valuable. Thanks for the welcome. I hope I can contribute. You seem to have started well :) Welcome! Cheers, Sander APWG co-chair -- ************************************************************ Raymond Jetten Phone: +358 3 41024 139 Senior System Specialist Fax: +358 3 41024 199 Elisa Oyj / Network Management Mobile: +358 45 6700 139 Hermiankatu 3A raymond.jetten(a)elisa.fi FIN-33720, TAMPERE http://www.elisa.fi ************************************************************

2 1

2014-04 New Policy Proposal (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 05 May '14

05 May '14

Dear colleagues, A proposed change to RIPE Document ripe-606, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-04 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 3 June 2014. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

Support of https://www.ripe.net/ripe/policies/proposals/2014-03
by Johan Boger 05 May '14

05 May '14

Dear Colleagues, I hereby vote YES on the proposal linked at https://www.ripe.net/ripe/policies/proposals/2014-03 Best Regards, -- Johan Boger, Project Manager (AS48285) e: johan(a)robtex.com w: http://www.robtex.com l: cy.robtex

6 6

Re: [address-policy-wg] 2014-03 New Policy Proposal (Remove Multihoming Requirement for AS Number Assignments)
by Tore Anderson 05 May '14

05 May '14

* Marco Schmidt > https://www.ripe.net/ripe/policies/proposals/2014-03 Makes sense to me. Tore

1 0

Fwd: Updates to RIPE-500: Policy Development in RIPE
by Sander Steffann 04 May '14

04 May '14

Hello WG, Work is being done on ripe-500, the Policy Development Process (PDP). As the PDP is quite important to the Address _Policy_ Working Group this is probably of interest to you. Hans Petter Holen, our RIPE Deputy Chair, has posted the proposed new revision on the RIPE list. For those of you who are not subscribed to the RIPE list: here is a copy of his message. If you want to comment on this proposed new text please do so on the RIPE list. Sincerely, Sander APWG Co-chair Begin doorgestuurd bericht: > Van: Hans Petter Holen <hph(a)oslo.net> > Onderwerp: Updates to RIPE-500: Policy Development in RIPE > Datum: 4 mei 2014 13:55:55 CEST > Aan: ripe-list(a)ripe.net > > Dear colleagues, > The Working-group chairs have for some time been discussing how to improve the Policy Development Process as described in RIPE-500. A small task force with Brian Nisbet as the coordinator and Ondrej Filip, Nick Hilliard and Hans Petter Holen as members has worked out the final details in the text. > > The wg-chairs have reached consensus on the attached proposal. > > The main change in the PDP is to allow the Working-group Chairs of the working-group developing the policy to declare consensus. > > This allows for a more timely conclusion of the PDP, but also allows for the Working-group chairs collectively to act as an appeals body. > > I am circulating the new text now for community review and the intent is to put this in place at the coming RIPE meeting. > > > Yours Sincerely, > > Hans Petter Holen > RIPE Deputy Chair > >

1 0

Re: [address-policy-wg] 2014-03 New Policy Proposal (Remove Multihoming Requirement for AS Number Assignments)
by James Blessing 01 May '14

01 May '14

On 30 April 2014 14:28, Marco Schmidt <mschmidt(a)ripe.net> wrote: > https://www.ripe.net/ripe/policies/proposals/2014-03 > Other than the use cases suggested in the document (which could be achieved using private ASNs) is there a reason for this that I'm missing? With other discussions about recovering non globally routed ASNs this just seem odd J -- James Blessing 07989 039 476

5 4

Re: [address-policy-wg] 2014-03 New Policy Proposal (Remove Multihoming Requirement for AS Number Assignments)
by Fredy Kuenzler 01 May '14

01 May '14

Am 30.04.2014 15:28, schrieb Marco Schmidt: > A proposed change to RIPE Document ripe-525, "Autonomous System (AS) > Number Assignment Policies" is now available for discussion. > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2014-03 I support this proposal. However I suggest a small change in the text: "A new AS Number should only be assigned when there is a technical requirement that cannot be satisfied with an existing or private AS Number." should be "A new AS Number should only be assigned when there is a technical requirement that cannot be satisfied with an existing AS Number." Since we arrived in the 32bit-ASN century, private ASN should not matter anymore, i.e. noone should be forced to use private ASN permanently. Re hoarding: If someone thinks hoarding of AS206832 to AS207363 is useful, so be it... -- Fredy Kuenzler Init7 (Switzerland) Ltd. AS13030 St. Georgen-Strasse 70 CH-8400 Winterthur Skype: flyingpotato Phone: +41 44 315 4400 Fax: +41 44 315 4401 Twitter: @init7 / @kuenzler http://www.init7.net/

1 0