120 likes | 263 Views
Operational Policies for NIRs in the APNIC Region. NIR Meeting APNIC14, Kitakyushu, Japan 4 Sept 2002. New Definitions. NIR-LIR member Describes the LIR member of an NIR Delegation Transfer of Internet resources from one organisation to another through assignment or allocation.
E N D
Operational Policies for NIRs in the APNIC Region NIR Meeting APNIC14, Kitakyushu, Japan4 Sept 2002
New Definitions • NIR-LIR member • Describes the LIR member of an NIR • Delegation • Transfer of Internet resources from one organisation to another through assignment or allocation
Request Process ‘Allocation Request‘ (New) • NIR sends APNIC ‘allocation request’ when it approves allocation ≤ NIRs AW • Specific instruction to APNIC to make an allocation for NIR-LIR member • Needs to include all necessary database information • NIR has sole authority on request approval • Allocation will be made within one working day (could be automated in future) • Objective to promote aggregation • NIR does not receive separate allocation as allocations now selected from APNIC pool
Request Process ‘Second Opinion’ • Existing procedures apply • NIR sends APNIC ‘second opinion’ when request > NIRs AW • APNIC evaluates request and recommendation from NIR • Small change: allocation made from APNIC pool rather than NIR pool • Objective to promote aggregation • Both procedures depend on NIR implementing APNIC policies
Other Procedures • Database Registration • NIR responsible for maintaining registration records for address delegations • In-addr.arpa • Uses ‘domain’ objects • One zone file for each IANA IPv4 /8 • /16 and /24 zones in same (flat) file • Identical process in IPv6 • One zone file for /16 IANA allocation boundary • /36 and /32 directly in same (flat) file
In-addr.arpa Continued • Update cycle currently 2-hourly 24/7 • Fast propagation to external DNS • Direct allocation by APNIC • APNIC creates ‘inetnum’ object and ‘domain’ object for NIR on /16 or /24 boundaries • ‘Domain’ objects will be inactive • ‘mnt-by’ attribute will reflect NIR for both domain and inetnum objects
NIRs and DNS Management Procedures continued • Either use APNIC whois • Activate ‘domain’ objects with correct NS information • Using APNIC whois guarantees 2hr update cycle • OR APNIC mirrors NIR whois domain objects • Add zones to APNIC zonefile • Timely zone updates dependant on mirroring schedule • Future: using RPSL compatible live mirror retains data management in NIR
Pipelined process with external NIR whois data New filter to only accept NIR managed zone information Get NIR Whois data Sort & Collate Check For zone change Get Whois data Sort & collate Filter Filter Make zones Notify DNS
Transfer of Membership APNIC-NIR • APNIC allows members to join NIRs in their country • LIRs address space holdings transferred to NIR and contributes towards NIRs fee assessment • No ‘per address fee’ charged on NIR • No further charges on LIR by APNIC
Transfer of Membership NIR-APNIC • NIRs allow members to join APNIC • Management of address space and records transferred to APNIC • Member no longer receives service from NIR • Membership tier assessed at next renewal according to all NIR & APNIC allocated space • NIR impose no charges relating to resources previously allocated
Next Steps • Finalise NIR Operational Policy Document • Incorporating any amendments • Merge document with ‘Criteria for the Recognition of NIRs in the APNIC Region’ • Secretariat to implement document within 3 months of consensus on document