[address-policy-wg] [policy-announce] 2012-04 New Draft Document Published (PI Assignments from the last /8)

Hello everyone,

I support this.

Also I can say the PI should be distributed as well. There are lot of
companies, educational entities, small networks can't become a LIR as
for money and/or formalities (bueracracy) issues.

PI can be limited to /24. It is quite enough for small and even medium
size organisation to maintain multihomed IPv4 connection.

16.09.12 10:24, ioakimoglou написав(ла):
> Hello everyone,
> This is my first post in any of the RIPE mailing lists, I'm not even sure if
> I'm qualified or even "allowed".
> So feel free to put me in place, if needed :)
> 
> I find Randy's post about the last /8 going to new entrants to be the most
> convincing one.
> Giving it away to us (LIRS who are already in possession of at least a /21)
> should be secondary to giving it to newcomers who really need it in order to
> get started.
> I don't mean that's the only group of companies/orgs that should be
> considered, but they DO need this the most.
> 
> It's one thing to be tight with the resources you already have, and another
> to not have them at all.
> 
> And anyway, how much would life change for an ISP, for example, just cause
> they got an extra /22?  How much time would it really buy?
> Is that time as valuable as the ability for the new guys to also get SOME
> ipv4 connectivity?
> 
> Sorry if I'm out of place, again, I just thought I should try this.
> 
> 
> Dimitris Ioakimoglou
> Skype: dioakimoglou
> Linkedin: http://gr.linkedin.com/pub/dimitris-ioakimoglou/43/510/12
> dioakimoglou at globoplc.com | globoplc.com
> 
> 
> 
> Experience GO!Enterprise Server on your mobile/tablet. Download a demo.
> 
> -----Original Message-----
> From: address-policy-wg-bounces at ripe.net
> [mailto:address-policy-wg-bounces at ripe.net] On Behalf Of Sebastian Wiesinger
> Sent: Saturday, September 15, 2012 5:58 PM
> To: address-policy-wg at ripe.net
> Subject: Re: [address-policy-wg] [policy-announce] 2012-04 New Draft
> Document Published (PI Assignments from the last /8)
> 
> * Randy Bush <randy at psg.com> [2012-09-10 16:00]:
>> i can not speak to the intent in the ripe region.  but the principal
>> intent of the final /8 policy in the apnic region was so that *new*
>> entrants could get one small piece of the pie.
>>
>> in the years when we have a mixed 6/4 internet, folk will need a wee
>> bit of v4 space for things such as nat64 and other ways face the dual
>> stack world.
>>
>> pissing it away in greed and/or arrogance is not responsible to our
>> children.
> 
> I agree with Randy and oppose this proposal. We should not use the last /8
> for PI space but for LIRs who need at least a bit of v4 space to get going.
> 
> Regards
> 
> Sebastian
> 
> --
> GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A  9D82 58A2 D94A 93A0 B9CE)
> 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE
> SCYTHE.
>             -- Terry Pratchett, The Fifth Elephant
> 
> 
> 
> ________________________________
> 
> This e-mail may contain information that is PRIVILEGED and/or CONFIDENTIAL. This e-mail is intended solely for the individual or entity to whom it is addressed. If you are not, or have reason to believe you are not the intended recipient of this e-mail please contact us by reply e-mail as soon as possible and delete the message (including attachment(s)) from your computer system(s) without disclosing it. Any unauthorized review, use, copying, disclosure or distribution of this e-mail (including attachment(s)) is prohibited. The content of this e-mail may contain personal views of its author and does therefore not necessarily reflect the views or policies of Globo (Globo Technologies S.A., Globo Mobile S.A., Profitel S.A, Globo Plc, Globo International LLC ).Globo hereby disclaims any and all liabilities which may arise in relation to any of its electronic communication. No obligation is entered into by virtue of this e-mail, unless confirmed in writing and duly signed by an authoriz
ed representative of Globo. All outgoing and incoming emails are scanned for malicious code and all malicious code infections are being automatically reported to the appropriate IS Administrators.
>