Policy Update ARM 3/bdNOG 1

632 views
538 views

Published on

Latest policy implementations and discussion from the third APNIC Regional Meeting and first bdNOG conference in Dhaka, Bangladesh.

Published in: Internet, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
632
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Policy Update ARM 3/bdNOG 1

  1. 1. Issue Date: Revision: APNIC Policy Update May, 2014 Vivek Nigam bdNOG1 [19 May 2014] [3]
  2. 2. Overview • How are policies developed? • Why is policy development important? • Policy updates 2 “Function as the Regional Internet Registry for the Asia Pacific, in the service of the community of Members and others”
  3. 3. How Are Policies Developed? 3 Open, transparent, bottom-up Consensus based Policy SIG mailing list
  4. 4. Policy Cycle 4
  5. 5. Why is Policy Development Important? •  Fair and consistent distribution of Internet Number resources •  Anyone can participate in how Internet number resources are managed –  How much Internet number resources you can get –  How IP addresses are transferred 5 Policy SIG Charter: Develop policies and procedures which relate to the management and use of Internet address resources by APNIC, NIRs and ISPs within the Asia Pacific region
  6. 6. Policy Development •  APNIC Policy Development Process www.apnic.net/policy/policy-development •  SIG Guidelines www.apnic.net/community/sigs/sig-guidelines •  Mailing list archive mailman.apnic.net/mailing-lists/sig-policy •  Mailing list subscription mailman.apnic.net/mailman/listinfo/sig-policy •  Mail to list sig-policy@apnic.net 6
  7. 7. Recently Implemented Policies Implemented •  prop-108: Suggested changes to the APNIC Policy Development Process - Changes the duration of comment period from 8 weeks to no shorter then 4 weeks but no longer then 8 weeks •  prop-107: AS Number transfer policy proposal - Permits the transfer of Autonomous System Numbers (ASNs) 7
  8. 8. Recently Implemented Policies •  prop-109: Allocate 1.0.0.0/24 and 1.1.1.0/24 to APNIC Labs as Research Prefixes - Allocate 1.0.0.0/24 and 1.1.1.0/24 to APNIC Labs as Research Prefixes to be used as passive traffic collectors Pending Implementation •  prop-105: Distribution of returned IPv4 address (Modification of prop-088) - Permits the delegation of an additional /22 IPv4 address to APNIC account holders 8
  9. 9. Policy Proposals at APNIC 37 •  prop-111: Request-based expansion of IPv6 default allocation size –  Proposal did not reach consensus at the Policy SIG and was returned to the author for further development •  prop-110: Designate 1.2.3.0/24 as Anycast to support DNS Infrastructure –  The proposal reached consensus at the Policy SIG, but failed to reach consensus at the AMM •  Returned to mailing list for further consideration, but later withdrawn by the author and abandoned 9
  10. 10. You’re Invited! •  APNIC 38: Brisbane, Australia, 9-19 Sep 2014 •  APRICOT 2015: Fukuoka, Japan, 24 Feb-6 Mar 2015 10
  11. 11. THANK YOU www.facebook.com/APNIC www.twitter.com/apnic www.youtube.com/apnicmultimedia www.flickr.com/apnic www.weibo.com/APNICrir

×