Policies for ASN Management in the Asia Pacific Region – Revised Draft

Address Policy SIG APNIC14, Kitakyushu, Japan 4 Sept 2002

Motivation for Policy Document

• Improve management of resource – Clearer responsibilities through contractual framework with ‘custodian’ • Resources easier to track, database registrations kept up to date • Separate AS policy from IP policy – AS policy only previously documented in former IPv4 policy (APNIC-076) – Clarify applicable policies – Make it easier to locate policies

Document Structure

• Separate policy from operations and request process – Does not include • Request process information • • FAQ style information (Guidelines doc is ‘work in progress’)

History of Document Review

• First draft published for comment 11 February 2002 – Mailing list feedback received – Presented at APNIC13 • Community suggested minor amendments • Second draft published: final call for comments 21 June 2002 – Incorporates all community feedback – Revised proposal presented APNIC14

Summary of Revisions

• First draft – All ASNs to be directly assigned by APNIC/NIR, but not

via

LIRs to customers • Feedback this breaks ‘one-stop shop’ service of LIRs – Mandatory registration of routing policy in AS object • Second draft – LIRs can continue to assign ASNs on behalf of customers • Some restrictions added to policy framework – Registering routing policy is optional

Other RIRs

• ARIN – ASNs are only assigned directly to end users with contractual framework • RIPE NCC – ASNs are only assigned to or via LIRs • Current problem in tracking ASN’s ‘in use’ and discussion is taking place on lir-wg list

Policies - Eligibility

• • Eligibility for an ASN – Organisation is multihomed AND – Has a unique routing policy • Different from upstream providers Also eligible – If you can meet criteria in “reasonable timeframe” after receiving ASN • Approximately one month

Revised Policy - Portability

• Assigned by APNIC/NIR – ASN is portable • Assigned to LIR for end-user – LIR is custodian • Responsible for following policies – ASN is non-portable • If customer leaves LIR, ASN must be returned to APNIC/NIR by LIR • LIR expected to enter appropriate agreement with customer – Restriction on portability not retrospective

Revised Policy - Portability

• Resource ownership – ASNs are not owned, but licensed – Transfers must be approved • Unused ASNs – Must be returned to RIR/NIR • Closure of LIR – LIR must ensure ASN is returned to APNIC/NIR • Customer may take over LIRs responsibility or ask new LIR to do so

Policies

• Registration – Assignment should be registered in appropriate RIR/NIR database • LIR responsible for registration where assigned on behalf of customer • Routing considerations – Proper management of the AS • Limiting the number of prefixes announced and aggregating where possible

Implementation

• Category ‘B’ document – ‘Minor revisions affecting policies and procedures’ – ‘Final call’ has taken place • Implementation – Active date one month after consensus – Allow time to inform community – Secretariat to make necessary changes

Questions?

• Document Reference • http://www.apnic.net/docs/drafts/ • Presentation slides • http://www.apnic.net/meetings/address/index.html