<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
unsubscribe<br>
<br>
David Song wrote:
<blockquote
cite="mid:!&!AAAAAAAAAAAYAAAAAAAAAMCkYUjR5HlDles4EAnPTN7CgAAAEAAAAO%2F5kYLuaXxEtklDHxdjpLMBAAAAAA==@nexgit.com"
type="cite">
<pre wrap="">Unsubscribe
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:arin-discuss-bounces@arin.net">arin-discuss-bounces@arin.net</a> [<a class="moz-txt-link-freetext" href="mailto:arin-discuss-bounces@arin.net">mailto:arin-discuss-bounces@arin.net</a>]
On Behalf Of rob servis
Sent: Wednesday, July 22, 2009 11:29 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:arin-discuss@arin.net">arin-discuss@arin.net</a>
Subject: Re: [arin-discuss] ARIN-discuss Digest, Vol 26, Issue 6
</pre>
<blockquote type="cite">
<pre wrap=""> On Tue, 21 Jul 2009, Carl Peterson wrote:
> I was just going to post the same thing but it is only fair that we
> develop a consensus as to when it is ok to blacklist a block for
</pre>
</blockquote>
<pre wrap=""><!---->unfair
</pre>
<blockquote type="cite">
<pre wrap=""> > use of ip space. Once we have a quorum of sorts, like minded
admins
</pre>
</blockquote>
<pre wrap=""><!---->and
</pre>
<blockquote type="cite">
<pre wrap=""> > companies should act as a group.
> As a basic rule I would start by saying that if a company or
group
</pre>
</blockquote>
<pre wrap=""><!---->is
</pre>
<blockquote type="cite">
<pre wrap=""> > holding a large block of ipv4 which they know they will never
use,
</pre>
</blockquote>
<pre wrap=""><!---->the
</pre>
<blockquote type="cite">
<pre wrap=""> > part that will never be used should be returned. The ip space
that
</pre>
</blockquote>
<pre wrap=""><!---->they
</pre>
<blockquote type="cite">
<pre wrap=""> > are holding only has value because the rest of us route to it.
How do you propose to know the difference between space which is
unused, and space which is in use on networks which are not directly
routed to the portions of the Internet that you can see?
Presuming you cannot see the use that people are putting space to, how
would your black-holing them penalize them?
Once you and your compatriots black-hole them, presuming they comply
with your desires and return the space, and it gets doled out to
someone else, how do you propose to get the space un-black-holed, so
you don't just penalize the subsequent recipient?
I see a heck of a lot more complaints from people who've recently
received new space that they can't get people to stop black-holing,
than I see complaints from people unable to get space.
-Bill
</pre>
</blockquote>
<pre wrap=""><!---->
I concur --- this could end up a mess if routes started getting blackholed.
Although a controlled use of a coordinated facility like the BOGON system
could be okay if it is BGP based.
There is a presumption here that the 'unused' space is somehow contiguous
and therefore even possible to return in any meaningful size chunks.
Telcos and NPA/NXX assignments had a similar problem to solve. CLECs were
given entire exchanges (10,000 blocks of numbers) until NANPA realized this
was not going to be sustainable with the number of new CLECs asking for
numbers. They then cut assignments back to 1,000 blocks of numbers and in
some cases asked CLECs to give back 9,000 phone numbers. By then the CLECs
had given out numbers throughout the entire 10,000 number range (everyone
wants 1111 or 2222). It caused some customer service issues and definitely
a lot of time and energy to accomplish that relinquishment.
Returning IPs from these big blocks may be just as problematic ... a /22
here, a /24 there. This could be a mess.
Rob Servis
RASER, Inc.
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to the ARIN
Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
</body>
</html>