I've just been advised that due to popular demand, this session will
now be streamed live.

Please ensure that if you would like to watch the stream or
participate that you register before hand.

There is a registration link on the top of the Programme page
https://2014.apricot.net/program


See you all there.

Dean

On Fri, Feb 21, 2014 at 1:31 PM, Dean Pemberton <d...@deanpemberton.com> wrote:
> Good Morning all,
>
> There will be a BoF on the subject of IP address leasing at the
> APRICOT 2014 meeting on Tuesday, 25th Feb 2014 at 17:30 - 19:00 in the
> Grand Caymans room on  Level 10.
>
> I will be chairing this BoF and I'd like to invite all interested
> parties to attend.
>
> While the concept of IP address leasing is not new, and has been the
> primary model for ISP sub-delegation to its customers, there is an
> assumption that some level of operational control is retained by the
> ISP. There is an expectation that the registry data reflects an
> operational hierarchy that makes it possible for people to look up
> 'parent' blocks and use the contact information at that level to
> resolve operational issues at a lower level network block.
>
> This model and assumptions may no longer be valid in the IPv4
> exhaustion state we're currently in. Addresses may be leased out with
> no operational service or control attached to it. How should the
> registry reflect this reality, to maintain its important role in
> facilitating operational trouble shooting? Policy-wise, should lessors
> be allowed to accumulate address space, using leasing demands as
> 'demonstrated need' in getting more IP addresses transferred to them?
>
> Voice your opinion in a healthy debate in this BoF, held to gauge the
> community's sentiment on these important issues.
>
>
> Regards,
>
> Dean



-- 
Regards,

Dean
*              sig-policy:  APNIC SIG on resource management policy           *
_______________________________________________
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy

Reply via email to