[ppml] Policy Proposal 2005-7: Rationalize Multi-Homing Definitionand Requirement
Jim McBurnett
jim at tgasolutions.com
Mon Sep 5 19:27:23 EDT 2005
Interesting...
I called the helpdesk a little while back and asked for a multi-homing
block for a customer that was about to dump their primary carrier and
become multi-homed and was denied.
I was told the denial was because the customer was not currently
multi-homed and at face value could not justify a /22.
So under this policy, I believe the customer would have been approved.
With HIPPA, Sarbox, and the financial equivilent, our customers are
moving to multi-homing.
Most want a /23 or /24, and from my experience I have seen 1 to 2 week
delays in getting IP's from some ISPs.
This may really help the SMB market that wants to multi-home.
Thanks,
Jim
-----Original Message-----
From: Robert E.Seastrom [mailto:rs at seastrom.com]
Sent: Saturday, September 03, 2005 9:52 AM
To: Jim McBurnett
Cc: Member Services; ppml at arin.net
Subject: Re: [ppml] Policy Proposal 2005-7: Rationalize Multi-Homing
Definitionand Requirement
"Jim McBurnett" <jim at tgasolutions.com> writes:
> Sorry all for the late question.
You're not late at all - 2005-7 is newly released and this is the first
public comment I've made on it.
> Am I to understand that this policy should prevent a requesting end
> user from getting X space from an ISP to multi-home just so they can
> prove they are multi-homed in order to request ARIN direct IP space?
It should prevent the requester and their ARIN analyst from having to go
through the intricate dance currently required to get PI space from ARIN
for multihoming purposes.
The intent is to harmonize the requirements for getting PI space for
multihoming purposes with the requirements for getting an ASN, in the
interests of eliminating needless extra steps (principally benefitting
the requesting end user, but I'm sure the ARIN analysts won't complain
about eliminating the extra steps). We don't, for instance, make people
who wish to multihome "borrow" an ASN from some other organization and
demonstrate that they have circuits in place - simply providing
contracts or verification from two or more upstream ISPs is deemed
sufficient.
Nothing in 2005-7 is meant to be construed to prevent a requesting end
user from getting delegated space from his ISP for the purposes of
multihoming if that is how they wish to proceed. Those who require a
block of address space that is large enough that it would represent a
hardship to their ISP probably already qualify for space directly from
ARIN under another existing policy anyway (for instance, 4.2.1.6 -
Immediate Need).
> Thanks,
> Jim
Hope this has been of some clarification.
Best,
---Rob
>
>
> -----Original Message-----
> From: Member Services [mailto:memsvcs at arin.net]
> Sent: Thursday, September 01, 2005 3:55 PM
> To: ppml at arin.net
> Subject: [ppml] Policy Proposal 2005-7: Rationalize Multi-Homing
> Definitionand Requirement
>
> On August 31, 2005, the ARIN Advisory Council (AC) concluded its
> review of proposed policy "Rationalize Multi-Homing Definition and
Requirement"
> and agreed to forward it as a formal proposal for discussion by the
> community. This proposal is designated 2005-7: Rationalize
> Multi-Homing Definition and Requirement. The policy proposal text is
> below and can be found at:
> http://www.arin.net/policy/proposals/2005_7.html
>
> All persons in the community are encouraged to discuss Policy Proposal
> 2005-7 in the weeks leading to the ARIN Public Policy Meeting in Los
> Angeles, CA, scheduled for October 26-27. Both the discussion on the
> PPML and at the public policy meeting will be used to determine the
> community consensus regarding this policy proposal.
>
> The ARIN Internet Resource Policy Evaluation Process can be found at:
> http://www.arin.net/policy/irpep.html
>
> ARIN's Policy Proposal Archive can be found at:
> http://www.arin.net/policy/proposal_archive.html
>
> Regards,
>
> Member Services
> American Registry for Internet Numbers (ARIN)
>
> ### * ###
>
> Policy Proposal 2005-7: Rationalize Multi-Homing Definition and
> Requirement
>
> Author: Robert Seastrom
>
> Policy statement: In existing policy 4.2.2.2, replace the phrase
> "multi-homed organizations must:" with the phrase "organizations
> applying under the multi-homed policy must:" In existing policy
> 4.2.2.2.2, replace "Provide information showing that the
requested
> IP address space will be utilized within three months." with
> "Provide information showing that the requested IP address space
> will be utilized within three months and demonstrating an intent
> to
> announce the requested space in a multi-homed fasion."
>
> Rationale: Presently, organizations wishing to apply for their first
> address space under the multi-homed policy must demonstrate that
> they have ALREADY announced a DIFFERENT address block via
> multi-homing, while simultaneously promising to renumber out of
> that same block. This creates needless make-work for ISPs which
> are
> planning to multi-home, related to old resources which they're
> already trying to get out of. Likewise, it creates needless
work
> for both of their upstream providers, who have to temporarily
> announce a prefix which DOESN'T NEED to be multi-homed, solely
to
> demonstrate to ARIN analysts that the applying ISP is
multi-homed.
> However, this same criterion can be demonstrated just as
> effectively by the applying ISP showing the analyst contracts
with
> multiple ISPs under which the newly-applied-for block WILL BE
> multi-homed, and this more accurately reflects the intent of the
> original policy, while removing needless make-work at a time
when
> the applicant is surely already quite busy with the real
> requirements of their change-over.
>
>
>
> _______________________________________________
> PPML mailing list
> PPML at arin.net
> http://lists.arin.net/mailman/listinfo/ppml
>
> _______________________________________________
> PPML mailing list
> PPML at arin.net
> http://lists.arin.net/mailman/listinfo/ppml
More information about the ARIN-PPML
mailing list