Transcript A Proposal for IPv4 Essential Infrastructure Address Policy SIG APNIC14, Kitakyushu, Japan 5 Sept 2002

A Proposal for IPv4 Essential
Infrastructure
Address Policy SIG
APNIC14, Kitakyushu, Japan
5 Sept 2002
Background and Problem
• No specific policy exists for infrastructure
which is critical to Internet operation
– Resources for ‘critical infrastructure’ important to
protect stability of core Internet functions
• Current policy regime only recognises ‘need’
rather than type of organisation
– Most critical infrastructure unlikely to qualify for
routable address space allocation
– Addresses from upstream LIR: risk of widespread
instability when renumbering
Proposal
• Allow portable addresses to be assigned to
‘critical infrastructure’
– Minimum assignment of /24
• “Critical Infrastructure” to be defined
unambiguously
– Definition could change over time
• Address assignments specifically for
servers and services comprising critical
infrastructure
– Not for other purposes by receiving organisation
Proposal Continued
• Critical Infrastructure includes:
– Domain registry infrastructure (whois and
DNS servers)
• Root DNS
• Generic top-level domain (gTLD)
• “Country Code” top-level domain (ccTLD)
– Address registry infrastructure (whois
and reverse DNS servers)
• RIRs and NIRs
• IANA
Other RIRs
• ARIN
– ‘critical infrastructure’ assignments recognised
to: ccTLD, gTLD, RIRs, IANA, IXes
– Recent modification: minimum assignment /24
• RIPE NCC
– No special policy for critical infrastructure
– LIRs can request portable address space on
behalf of their customers – no minimum size
• LACNIC
– No policy, but a proposal will be made at next
policy meeting
Source of Address Space - Options
• Allocate a single large block for all
assignments
– Allows easy configuration of ISP filters
• May be necessary to ensure routability
– More open to DOS attacks OR
• Use existing ‘swamp’ space
– Utilise existing free space
– Likely to be routable in small blocks
– Assignments not contiguous or easily
recognisable
Implementation
• Secretariat to implement policy from
three months after consensus
– Documentation
– Request forms and process
– Inform community
• Secretariat to report activity at future
meetings
• Review of policy as needed
– Including definition of critical infrastructure
A Proposal for IPv4 Essential
Infrastructure
Questions?