prop-007-v001 privacy of customer assignment records project update db sig apnic 19 24 february 2005...
DESCRIPTION
Motivation Privacy issues –Long-term member/customer concerns about publication of customer information –Increasing Government concern for privacy APNIC legal risk –Legal responsibility for accuracy and advice –Damages caused by maintaining inaccurate personal data Customer data is poorly maintained –APNIC has no direct control over accuracy –Expensive for member to maintainTRANSCRIPT
prop-007-v001Privacy of customer assignment
recordsProject Update
DB SIG APNIC 1924 February 2005
Kyoto, Japan
Sanjaya, Project Manager, APNIC Secretariat
Overview
• Motivation• What needs to be visible?• Systems configuration• Implementation schedule• Migration stages and result• New tools• Feedback received• Q & A
Motivation
• Privacy issues– Long-term member/customer concerns about
publication of customer information – Increasing Government concern for privacy
• APNIC legal risk– Legal responsibility for accuracy and advice– Damages caused by maintaining inaccurate
personal data• Customer data is poorly maintained
– APNIC has no direct control over accuracy– Expensive for member to maintain
What needs to be visible?
IANA Range
Non-APNIC Range APNIC Range
NIR RangeAPNIC Allocations & Assignments
NIR Allocations & Assignments
Customer Assignments Infrastructure Sub-Allocations
must bevisible
visibleoptional
LIR/ISP
PORTABLE addresses
NON-PORTABLE addresses
Systems configuration
Public DB(whois)
Private DB
auto-dbm
web-update
MyAPNIC Alloc Manager
•Customer assignments•Infrastructure•Sub-Allocations
•IANA•APNIC•NIR•Portable Allocations•Portable Assignments
Implementation Schedule
No Task Aug Sep Oct
1.1 Systems development
1.2 Prototype demo (APNIC 18)
1.3 Internal testing
1.4 Migration announcement
1.5 Data migration
1.6 Completion announcement
1.7 Prepare report for APNIC 19
Migration stages
Thursday Friday Monday Tuesday
30 Sep 1 Oct 4 Oct 5 Oct
copy
to p
riva
te d
b
delet
e fro
m w
hois
MyAPNICmodule
installation
MyAPNICpatch
installation
HM tools- usage
- private query
Migration result
0
20000
40000
60000
80000
100000
120000
140000
160000
Public Private
Assign NonAlloc NonAssign PortAlloc Port
New tools
• MyAPNIC– private record management
• MyAPNIC scripted interface (under development)– allow automated scripts to update and
query private data– uses SSL protection and client certificate
authentication just like MyAPNIC
Feedback received
• Customer queries/complaints during first week: 10+– Requests to move objects to public whois
• Some issues with historical resource holders– Did not receive announcement (non
contactable)• Loss of statistical information from the
whois database– JPNIC to present a proposed solution in APNIC
19
Q & A