[members-discuss] Fwd: Executive Board Resolution on Legacy Internet Resource Holders

Hi,

Please remove me from this e-mail list
roger.baakki at n4.nu <mailto:roger.baakki at n4.nu>




> Vidarebefordrat brev:
> 
> Från: Lu Heng <h.lu at outsideheaven.com>
> Ämne: Re: [members-discuss] Executive Board Resolution on Legacy Internet Resource Holders
> Datum: 27 september 2016 08:58:55 CEST
> Till: Hank Nussbacher <hank at efes.iucc.ac.il>
> Kopia: "members-discuss at ripe.net" <members-discuss at ripe.net>
> 
> Hi
> 
> On Tue, Sep 27, 2016 at 8:30 AM, Hank Nussbacher <hank at efes.iucc.ac.il <mailto:hank at efes.iucc.ac.il>> wrote:
> On 26/09/2016 23:47, Radu-Adrian Feurdean wrote:
> > On Wed, Sep 14, 2016, at 17:16, Hank Nussbacher wrote:
> >> Acquiring small bits of legacy IP space to bypass LIR membership dues
> >> and to then be entitled to get more IP address space goes totally
> >> against the spirit of RIPE and I totally approve the Executive Board's
> >> decision and would recommend even further sanctions against those that
> >> have done it.
> > Could someone remind us why in the first place:
> >  - a legacy block can be broken into smaller pieces (which can then be
> >  transferred)
> >  - after the transfer, the parts of the old legacy block still remain
> >  tagged as legacy
> >  - what stops the "convert to PA" (or PI, whatever) from being a
> >  prerequisite to a transfer (or even to a split of the original legacy
> >  block)
> >  - more generally why the stance of "giving full rights to legacy
> >  holders", but with only voluntary respect of the obligations
> >
> > I can understand that a legacy space holder can keep the space
> > "received" before the existence of the NCC, but not the fact that others
> > can acquire that kind of space and pretend to the same treatment.
> I agree with you.  If a legacy owner sells all or part of their legacy
> IP space, that IP space should lose its legacy status.
> 
> How technically possible to "loss" its legacy status if it's status was not given by RIPE. 
> 
> It is not an treatment by RIPE NCC, so they don't have to pretend to have it, they have it, period.
> 
> Unless an newly established contract relation that specifically state that they give up such status voluntarily, in which is what we are discussing here now.
> 
> But for my personal view, as long as legacy holder update their whois record(RIPE NCC pay for the database maintenance), I agree with Erik, there is no need to bring them into the LIR system.
> 
> 
>  
> -Hank
> >
> 
> 
> ----
> If you don't want to receive emails from the RIPE NCC members-discuss
> mailing list, please log in to your LIR Portal account and go to the general page:
> https://lirportal.ripe.net/general/ <https://lirportal.ripe.net/general/>
> 
> Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.
> 
> 
> 
> -- 
> This transmission is intended solely for the addressee(s) shown above. It may contain information that is privileged, confidential or otherwise protected from disclosure. Any review, dissemination or use of this transmission or its contents by persons other than the intended addressee(s) is strictly prohibited. If you have received this transmission in error, please notify this office immediately and e-mail the original at the sender's address above by replying to this message and including the text of the transmission received.
> ----
> If you don't want to receive emails from the RIPE NCC members-discuss
> mailing list, please log in to your LIR Portal account and go to the general page:
> https://lirportal.ripe.net/general/ <https://lirportal.ripe.net/general/>
> 
> Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.



Mvh/RegardsRoger Baakki                                                     Direkt +46 8 546 144 01Växel +46 8 546 144 00roger.baakki at n4.nu
 Forskargatan 20J151 36 Södertälje, SwedenBesök: Kvarnbergagatan 14A, B401 pl.3www.n4.nu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160927/2cef2a5d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: f793e786.720efef4.png
Type: image/
Size: 0 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160927/2cef2a5d/attachment.bin>