POST-TRANSFER ZONE MAINTENANCE

* The RIR that holds the registration should have the authoritative
  database record.

* The majority RIR should pull the data from the minority RIR at:
    0:00, 4:00, 8:00, 12:00, 16:00, 20:00  GMT - APNIC
    1:00, 5:00, 9:00, 13:00, 17:00, 21:00  GMT - ARIN
    2:00, 6:00, 10:00, 14:00, 18:00, 22:00  GMT - LACNIC
    3:00, 7:00, 11:00, 15:00, 19:00, 23:00  GMT - RIPE NCC

  - The majority RIR is responsible for sanity checking that all
    data provided is properly incorporated in the zone and that
    no data has been provided that is outside of the networks 
    residing in the minority RIR.
    -- email notification only when exceptions occur
    -- place zone files in public place 
       ftp site: ftp://ftp.<rir>.net/pub/zones/<octet>.in-addr.arpa

  - The eventual goal should be near real-time updates.

* Method of data transfer:

  o Each RIR should create a directory on its ftp site, from which the
    files will be pulled
     - ftp://ftp.<rir>.net/pub/zones/<zero-padded-slash8>-<rir>
     - ftp://ftp.<rir>.net/pub/zones/<zero-padded-slash8>-<rir>.md5
     - ftp://ftp.<rir>.net/pub/zones/<zero-padded-slash8>-<rir>.asc

[Lock file not needed.]

* Format and content of the data to be provided?

  o The data format will be in the format of DNS resource records, i.e.,
    $ORIGIN.
    <reverse IP>.in-addr.arpa.  [TTL] NS  <hostname>.

  o Initially, data transferred should only include NS resource records.
    If other RR types are provided, the majority RIR may ignore them.

  o File may also include BIND-style comments.

  o Last record being:

   <RIR>.<slash8>.in-addr.arpa. TXT "Generated at <ISO timestamp GMT> with <n> NS records."

* Set default minimum TTL across <octet>.in-addr.arpa zones at 2 days.