Anatomy of a Legacy Network Transfer What is transferred? (allocations, assignments, reassignments) - Whois data - In-addr data - Paperwork -- Any existing paperwork regarding the network -- Letter of transfer from ARIN Miscellaneous: o Manage transfer of 192/8 network registrations separately Preliminary Steps: o RIRs establish erx@.net mailing lists . AS: o RIRs establish websites with FAQs about transfer process - Generate list of question by June 19 - Generate answers by June 28 - Ordered list of the ASNs that will be transferred by Jun 7 - Revised list of the ASNs that will be transferred by Jul 1 o RIRs to draft notification letters by Jun 21 o RIRs to produce final notification letters by July 1 o RIRs to send notification letters by July 3 o Transfer of records occurs no later than Friday, Aug 2 NET o RIRs establish websites with FAQs about transfer process by July o RIRs to draft notification letters by July - Generate list of question by July - Generate answers by July - Ordered list of the /8s that will be transferred by July o RIRs to finalize notification letters by August o Devise and test post-transfer zone maintenance procedure by Sept per /8: Step 0: Pre-Notification o Identify and resolve conflicts where ARIN's registration either does not exist or is smaller than RIPE or APNIC's registration for a block. o ARIN will provide candidate listing with contact info to RIPE and APNIC. Step 1: Notification o RIPE or APNIC provide a list of contacts to include in the notification mailing. o Per /8, notification email from ARIN. o RIRs post candidate transfer data to websites. o Allow 30 days after notification to resolve issues regarding transfer -- Opt out? -- Network registration postal address correction Step 2: o Recipient RIR sends a notification email that record has been transferred. o ARIN will provide a "final" candidate list of network transfer records to recipient RIRs and pull in-addr nameservers off of networks. o Final candidate list posted on websites. o Perform initial transfer (per /8), eventually handling up to 4-/8s simultaneously. o Recipient RIR should supply zone information to be incorporated into /8 zone back. o Lock out changes to candidate transfer records for no more than 30 days. o Recipient RIR should use time to place records in Whois o Respond to requests to change locked records with canned message and cc appropriate RIR on reply. Step 3: o Pull actual transferred networks o Replace with collapsed placeholder records (see ) Step 4: o Remove placeholder records from ARIN db (Timeframe?) Website: o FAQs o per /8, addresses only (top level allocations and assignments only; not reassignments)