<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [arin-ppml] Draft Policy 2011-6: Returned IPv4 Addresses</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Marty,<BR>
<BR>
Your statement of "is likely to result in confusion" is no less an opinion that Chris' counter assessment.<BR>
<BR>
I don't see the merit of the point?<BR>
<BR>
bd<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: arin-ppml-bounces@arin.net on behalf of Martin Hannigan<BR>
Sent: Tue 2/22/2011 9:34 PM<BR>
To: Chris Grundemann<BR>
Cc: arin-ppml@arin.net<BR>
Subject: Re: [arin-ppml] Draft Policy 2011-6: Returned IPv4 Addresses<BR>
<BR>
On Tue, Feb 22, 2011 at 10:33 PM, Chris Grundemann<BR>
<cgrundemann@gmail.com> wrote:<BR>
>> merging legacy<BR>
>> considerations with address space that is clearly controlled by ARIN<BR>
>> is likely to result in confusion.<BR>
><BR>
> Actually the opposite is true. Separating IPv4 address space along<BR>
> substantially arbitrary lines is likely to cause much more confusion<BR>
> than making clear policy that applies to all IPv4 addresses.<BR>
><BR>
<BR>
That wouldn't be a fact, it would be an opinion.<BR>
<BR>
Best,<BR>
<BR>
<BR>
-M<<BR>
_______________________________________________<BR>
PPML<BR>
You are receiving this message because you are subscribed to<BR>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<BR>
Unsubscribe or manage your mailing list subscription at:<BR>
<A HREF="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</A><BR>
Please contact info@arin.net if you experience any issues.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>