Presentation is loading. Please wait.

Presentation is loading. Please wait.

KRNIC Development Plan of IPv6 Management System Korea Network Information Center Mar. 2002.

Similar presentations


Presentation on theme: "KRNIC Development Plan of IPv6 Management System Korea Network Information Center Mar. 2002."— Presentation transcript:

1 KRNIC Development Plan of IPv6 Management System hostmaster@nic.or.kr Korea Network Information Center Mar. 2002

2 2 Contents  Management structure  KRNIC scheme  System specification  Deployment scenario  Q & A

3 3 Management structure  IANA delegated the task of IPv6 address management to RIR  RIR make further Allocation to National Internet Registry(NIR) and Local Internet Registry(LIR)  KRNIC manage every Allocation and Assignment of /48 or lager size!!  LIR make Allocation to ISP and Assignment to end-user  ISP make only Assignment to end-user IANA ISP LIR End-Site RIR (RIPE-NCC) RIR (ARIN) RIR (APNIC) RIR (AFRINIC) RIR (LACNIC) NIR (KRNIC) Future RIRs LIR  According to RFC1881 Network Name Address Range Allocation Date KT-KR2001:0220::/35Oct. 6, 1999 ETRI-KRNIC-KR2001:0230::/35Nov. 24, 1999 DACOM-KR2001:0270::/35Sept. 8, 2000 HITEL-KRNIC-KR2001:0280::/35Sept. 27, 2000 HANARO-KRNIC-KR2001:0290::/35Oct. 30, 2000 KORNET-KRNIC-KR2001:02B0::/35Jan. 2, 2001 NGINET-KRNIC-KR2001:02B8::/35Jan. 15, 2001 SKTELECOMNET- KRNIC-KR 2001:02D8::/35Apr. 6, 2001 KREONET2-KRNIC-KR2001:0320::/35Aug. 23, 2001 UNITEL-KRNIC-KR2001:0330::/35Sept. 20, 2001 THRUNET-KRNIC-KR2001:0378::/35Dec. 18, 2001 HANINTERNET-KRNIC- KR 2001:0390::/35Feb. 07, 2002

4 4 KRNIC scheme – principles in development  KRNIC manage LIR & ISP with the local guide of IPv6 Global Unicast address space Allocation & Assignment at the initial stage to achieve 5 goals of Internet resources management oLIR make Allocation to member ISP and Assignment to end-user oISP make only Assignment to end-user  Slow Start mechanism and Assignment Window  The local guide of IPv6 Global Unicast address space Allocation & Assignment at the initial stage is under revision and adopted as RFC-KR Doc. soon  KRNIC provide Web Site of local Internet resources Allocation & Assignment status for APNIC’s evaluation oNIR information such as No. of members, holding IP addresses, and local Allocation & Assignment status oLIR information such as No. of members, holding IP addresses and its Allocation & Assignment status oISP information such as No. of holding IP addresses and its Assignment status  KRNIC manage LIR & ISP Whois DB oOvercome managerial problems of IPv4 Whois DB  cmh@nic.or.kr => hostmaster@nic.or.kr oCountermeasure against spamming & hacking  Responsible Contact for network abuse

5 5 KRNIC scheme - overall workflow Mail APNIC DB  Allocation & Assignment status of each LIR and ISP (/48 or lager size)  Member information of LIR and ISP  Contact of personnel full charged of spamming & hacking complaint at each ISP DB  LIR and ISP donot need a separate DB  LIR and ISP are able to upload or query information of end-user or ISP by accessing KRNIC DB through Web Interface Whois, DNS Request Allocation or Assignment Web Interface KRNIC ISP End-user LIR Mirroring /48

6 6 KRNIC scheme – with LIR DB Mirroring  Allocation to LIR oSame policy as Japan in IPv6 request evaluation  HD ratio, size calculation and etc. oWorkflow I.LIR must join as KRNIC member and register its general information to DB II.LIR request IPv6 through KRNIC Web Interface III.After confirming with APNIC, KRNIC makes Allocation to LIR IV.KRNIC register information of allocated IPv6 to DB LIR KRNIC APNIC

7 7 KRNIC scheme – with ISP and end-user end-user DB Registration (/48 or larger size)  LIR Allocation to ISP and Assignment to end-user oWorkflow I.ISP request IR through KRNIC Web Interface II.LIR proceed according to requested size with KRNIC  /48 or lager size : LIR must confirm with KRNIC  Smaller size than /48 : automatic DB registration  ISP Assignment to end-user oWorkflow I.End-user request IR by e-mail II.ISP proceed according to the requested size with KRNIC  /48 or lager size : ISP must confirm with KRNIC  Smaller than /48 size : automatic DB registration ISP end-user LIR KRNIC

8 8 System specification – overall system topology Korea Network Information Center Firewall Internet Resources Management System KRNIC Staffs High Speed Network Whois Service Inverse Service IPv6 DB IPv6 DNS Server LIR Registries and ISP Registries End-users Internet

9 9 System specification – H/W & S/W Staff PC IPv6 Whois service Web service IPv6 DB DNS serverIRMS serverIPv6 DB serverStaff PCTotal Hardware specification UltraSPARCII 300Mhz, 512MB Memory, 30GB HDD Sun Ultra 60 360Mhz×2, 512MB Memory, 18GB HDD PIIIXeon 550Mhz 512MB Memory 18GB HDD Pentium II class or a later type Software specification Solaris 8 Bind-9.2.0rc1 Solaris 8 Apache Web Server Apache Jserv Oracle Client Procmail,Sendmail Solaris 8 Oracle 8i Server Windows98 / NT / 2000 Oracle Client Estimated budget MAXMAX -Approx. $ 38,462 Equip. : Approx. $ 38,462 Oracle: Approx. $ 32,308 -Approx. $ 109,231 MINMIN -Use Current Internet Resource Management System Equip. : Use surplus system Oracle: Approx. $ 32,308 -Approx. $ 32,308 DNS / Inverse service

10 10 Deployment scenario  March - June, 2002 oIPv6 Allocation & Assignment details collection in text version oDifferences such as DB, development period, and etc  Internal discussion with KISPA & IPv6 WG  External discussion with APNIC & each NIR  July - November, 2002 oIPv6 Management System Development  The guide of local IPv6 Global Unicast address space Allocation & Assignment at the initial stage  December, 2002 oDeployment of IPv6 Management System  January - December, 2003 oStabilization & Improvement of IPv6 management system

11 11 Q & A Thank you for your attention


Download ppt "KRNIC Development Plan of IPv6 Management System Korea Network Information Center Mar. 2002."

Similar presentations


Ads by Google