[75468] in North American Network Operators' Group
Re: I want my own IPs
daemon@ATHENA.MIT.EDU (Owen DeLong)
Sat Nov 13 12:12:26 2004
Date: Sat, 13 Nov 2004 09:11:55 -0800
From: Owen DeLong <owen@delong.com>
To: Marshall Eubanks <tme@multicasttech.com>,
Michael Loftis <mloftis@wgops.com>, nanog <nanog@merit.edu>
In-Reply-To: <web-2547049@multicasttech.com>
Errors-To: owner-nanog-outgoing@merit.edu
--==========4BD2480D0845F8D000A5==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Actually, that's not true. The requirement for a direct end-user =
assignment
of any size includes multihoming. Since RFC-compliant multihoming requires
an ASN (consistent origin AS), one of the metrics used to determine if an
organization is multihomed is the possession of (or application for) an =
ASN.
This applies to any prefix size. Initially, there were going to be =
separate
more stringent rules for obtaining a /24 microallocation, but, in the
process of watering 2002-3 down to a /22, most of these additional
requirements were also removed. The resulting policy is, in fact,=20
essentially
identical to the current policy except for the minimum allocation unit, =
and,
the specification that /22 and /21 assignments and allocations will be =
taken
from a different address pool than the larger ones.
Owen
--On Saturday, November 13, 2004 4:38 AM -0500 Marshall Eubanks=20
<tme@multicasttech.com> wrote:
>
> On Fri, 12 Nov 2004 15:57:46 -0700
> Michael Loftis <mloftis@wgops.com> wrote:
>>
>
> The original intent of 2002-3 : Micro-Assignments for Multihomed Networks
> was to give a /24 to any party with an ASN, as it was possible to become
> an AS without having the ability to get your own address space.
> In the year+ before it was approved last Fall
> in Chicago, this was watered down to a /22. (FWIW, I opposed that.)
>
> However, to become an AS means that you have to be multi homed, i.e., =
have
> a connection to 2 or more providers. Since it is not hard to get a /24
> from a provider if you are paying for a connection with them, then my
> understanding of the intent was that any ASN with two /24's should be
> able to get a /22. (I.e., for the microassignment, having an ASN was the
> crucial factor.) This is not the same as requesting an assignment for a
> /20 or smaller prefix, where different rules apply.
>
> If you are an ASN with two address blocks, I think that you qualify and
> should apply.
>
> Regards
> Marshall Eubanks
>
>
>>
>>
>> --On Friday, November 12, 2004 14:14 -0500 Alex Kamantauskas
>> <alexk@tugger.net> wrote:
>>
>> >
>> > Yep, I blinked while going through the small town of ARIN Policy and
>> > missed it :)
>> >
>> > ARIN Number Resource Policy Manual, 4.2.2.2: "When requesting a /22,
>> > demonstrate the efficient utilization of a minimum contiguous or
>> > noncontiguous /23 (two /24s) from an upstream."
>>
>> I'm still not exactly clear on the definition of 'efficient utilization'
>> --- in other places it' mentions 80%, but that's only as ISP allocation
>> and request for additional space...
>>
>> Anyone have a pointer as to the ARIN official definition of this
>> language?
>
--=20
If it wasn't crypto-signed, it probably didn't come from me.
--==========4BD2480D0845F8D000A5==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)
iD8DBQFBlkBbn5zKWQ/iqj0RAg8xAJ9rE2thNr4lVj+QTViLXF8leS/d3wCfVPRo
3gXhXR7QprYM4FH8wemo0NY=
=m+TM
-----END PGP SIGNATURE-----
--==========4BD2480D0845F8D000A5==========--
