[ppml] Allocation and reallocation

[Owen DeLong]

Michael,
        If your proposal does what you claim it will do below, it would be a
bad policy indeed.  There are good reasons for end-user assignments to exist
and not be treated entirely the same as allocations to LIRs.  I would support
a proposal clarifying the terminology and replacing assignment/allocation
distinctions with terms that provided a better description of what is really
going on, although, I would propose that we should include a reference translation
of the historical meaning of the obsoleted terms for people reviewing the archives.

Owen


--On Monday, October 27, 2003 11:29:28 AM -0500 Lee Howard <lee.howard at mci.com> wrote:

> On Mon, 27 Oct 2003 Michael.Dillon at radianz.com wrote:
>
>> Date: Mon, 27 Oct 2003 15:11:42 +0000
>> From: Michael.Dillon at radianz.com
>> To: ppml at arin.net
>> Subject: Re: [ppml] Allocation and reallocation
>>
> [. . .]
>>
>> For the next meeting in Vancouver, I intend to present
>> a policy proposal that will completely erase the distinction
>> between allocation and assignment as well as completely
>> erase the notion that there are two classes of address blocks.
>> I believe that a reasonable policy can clearly be expressed
>> using classes of organization (end user, ISP) and specific
>> characteristics attached to address blocks issued by ARIN.
>> Clearly the ability to allocate or assign or delegate subsets
>> of a block will be one of those characteristics.
>>
>> Think clarity and simplicity.
>
> Should ARIN harmonize with other RIRs towards the term "LIR"?
>
> I note that APNIC uses the same language as ARIN:
> http://www.apnic.net/info/faq/apnic_faq/using_address.html#1
>
> I look forward to reading your proposal.
>
> Lee
>
>
>
>>
>> --Michael Dillon
>>
>>
>



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20031027/67a92a74/attachment.sig>