Transcript Draft AS Policy Proposal Address Policy SIG APRICOT, Bangkok 6 March 2002 Motivation • Incomplete documentation – One paragraph only in • ‘Policies for managing address.

Draft AS Policy Proposal
Address Policy SIG
APRICOT, Bangkok
6 March 2002
Motivation
• Incomplete documentation
– One paragraph only in
• ‘Policies for managing address space in the Asia
Pacific region’ (APNIC-076)
• This document is now obsolete
• Did not “fit”
– Within policy document on address space
• Dedicated AS policy document
– Clarify applicable policies
– Easier to locate policies
Policy Proposal
• New document
– Minimal change to existing framework
• Currently following RFC1930
• Structure of draft
– Separate policy from operations and
request process
– Not included
• Information to assist in request process
• FAQ style information
– Guidelines doc is ‘work in progress’
• RFC2270, RFC1997
Reference
• ‘Policies for Autonomous System
Number management in the Asia
Pacific region’
– Posted to mailing lists for public
comment, February 11, 2002
• http://www.apnic.net/docs/drafts/
– No comments received so far
Policy Environment
• Resource ownership
– Resources are not owned, but licensed
– Transfers must be approved
• Routing considerations
– Proper management of the AS
• Limiting the number of prefixes announced
and aggregating where possible
• Resource portability
– Resource can be moved to connect to a
different AS
Policies
•
Criteria determine eligibility for ASN
–
Based on demonstrated need
•
•
Must be multihomed
–
•
To more than one other AS and
Have a unique routing policy
–
•
Avoid unnecessary prefixes in routing structure
Different from upstream providers
‘Bootstrap’ problem if not multihomed
–
Eligible if can meet above criteria in
“reasonable timeframe” after receiving ASN
•
Approximately one month
Policies
• Source of ASN assignments
– Only to be made by RIR/NIR
• LIRs can request for own networks
• Customers of LIR will request directly from
RIR/NIR and sign appropriate agreement
• Important change
– Consistent with responsible management
of resources
– Resources assigned via LIRs are difficult
to track/manage
Policies
• Registration
– Assignment should be registered in
appropriate RIR/NIR database
• Necessary to ensure goal of ‘uniqueness’
– Must include routing policy
• Provides information for troubleshooting
• Return of unused ASNs
– To appropriate RIR/NIR
• Resources allocated for documented need
• Condition that resources be returned if no
longer used
Implementation
• Category ‘B’ document
– ‘Minor revisions affecting policies and
procedures’
• Implementation
– Active date one month after consensus
– Allow time to inform community
– Secretariat to make necessary changes
Questions?
• Useful links
– Presentation slides
• http://www.apnic.net/meetings/13/sigs/
address/index.html
– Draft policy document
• http://www.apnic.net/docs/drafts/asn-policy.html