[AfriNIC-rpd] Draft Policy: Anycast Assignments in the AfriNIC region

[Badru Ntege]

Sounds logical and seems to make sense

> -----Original Message-----
> From: rpd-bounces at afrinic.net [mailto:rpd-bounces at afrinic.net] On Behalf
> Of McTim
> Sent: Wednesday, April 18, 2012 1:52 AM
> To: AfriNIC Resource Policy Discussion List
> Subject: [AfriNIC-rpd] Draft Policy: Anycast Assignments in the AfriNIC
region
> 
> Dear RPD,
> 
> Below is the proposal on Anycast I submitted to pdwg last week.
> 
> It is somewhat of a "strawman" in that it gives us a starting point for
discussion.
> 
> I look forward to your feedback.
> 
> --
> Cheers,
> 
> McTim
> "A name indicates what we seek. An address indicates where it is. A route
> indicates how we get there."  Jon Postel
> 
> 
> > ===
> >
> >
> > Unique identifier:  AFPUB-2012-V4-001-DRAFT-01 Draft Policy Name:
> > Anycast Assignments in the AfriNIC region
> > Authors:
> > a)    Tim McGinnis | dogwallah at gmail.com | ISC/PDWG Co-Chair
> > b)    Mark J Elkins | <mje at posix.co.za  | Posix Systems - South Africa
> > c)    Mauritz Lewies | <mauritz at three6five.com  | Co-founder at
> > Three6Five Network Solutions
> >
> > Submission Date: April 17 2012
> > Related Policies: None
> > Obsoletes: None
> > Amends: AFPUB-2005-v4-001, AFPUB-2006-GEN-001,
> > AFPUB-2010-v4-005-draft-05
> >
> >
> >
> > 1.    Summary of the Problem Being Addressed by this Policy Proposal
> >
> > Unless one is in charge of "critical infrastructure" in the AfriNIC
> > region, an organization cannot get an allocation or assignment purely
> > for anycast or GPRS Roaming Exchange (GRX) usage. I understand there
> > are organizations that would like to use anycast/GRX for non-critical
> > infrastructure in the region, but cannot due to policy limitations.
> >
> > In addition, current anycast practice announces an entire /24.
> > AfriNIC's current IPv4 policy states that the minimum allocation size
> > on initial allocation is a /22. To use a /22 for anycast when you
> > potentially are only using a few addresses in the block is wasteful.
> >
> > Also, if an organisation uses some of its allocation (or assignment)
> > for anycast services, it may not be able to justify the use of it's
> > current allocation/assignment when requesting additional resources.
> >
> > 2.     Summary of How this Proposal Addresses the Problem
> >
> > This proposal allows the use of one (1) /24 of IPv4 for anycast
> > services from a PA allocation or end user assignment. These /24s will
> > be assumed to be "fully utilised" by AfriNIC staff when considering
> > utilisation for first allocation or for an additional allocation or
> > assignment.
> >
> > 3.    Proposal
> >
> > 3.1 An organization may obtain one (1) /24 IPv4 prefix for anycast or
> > GRX purposes from an allocation or end-user assignment. These prefixes
> > must be used for the sole purpose of anycasting web or authoritative
> > DNS servers as described in BCP126/RFC 4786
> > (http://www.ietf.org/rfc/rfc4786.txt or for GPRS Roaming Exchange.
> >
> > These prefixes will count as being fully utilised when an organization
> > applies for additional resources. The utilization criteria that apply
> > to all IPv4 initial allocation or assignment requests shall be waived
> > for anycast allocation or assignment requests.
> >
> > 3.2 Blocks used for anycast services cannot be further assigned or
> > sub-allocated. They shall be tagged with the status attribute in the
> > AfriNIC DB as "ASSIGNED ANYCAST".
> >
> >
> > ===
> _______________________________________________
> rpd mailing list
> rpd at afrinic.net
> https://lists.afrinic.net/mailman/listinfo.cgi/rpd