[sig-policy] APNIC policy implementation update

To: sig-policy at apnic dot net
Subject: [sig-policy] APNIC policy implementation update
From: Son Tran <son at apnic dot net>
Date: Tue, 02 Jan 2007 13:58:50 +1000
Cc:
List-archive: <http://www.apnic.net/mailing-lists/sig-policy>
List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>
List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
List-post: <mailto:sig-policy@lists.apnic.net>
List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
User-agent: Thunderbird 1.5.0.9 (Windows/20061207)



Dear colleagues

The APNIC Secretariat has now implemented the following policy
proposals:

    prop-032: Four-byte AS number policy
    prop-038: Amending APNIC's lame DNS reverse delegation policy

------------------------------------
prop-032: Four-byte AS number policy
------------------------------------

APNIC has began the transition to allocating four-byte AS numbers.
The policy specifies three important dates:

  1 January 2007      Two-byte ASNs assigned by default
                      Four-byte ASNs assigned on request

  1 January 2009      Four-byte ASNs assigned by default
                      Two-byte ASNs assigned on request

  1 January 2010      No distinction made between two-byte
                      and four-byte ASNs


The comment period for the draft document incorporating this policy
has now finished and the updated document is now officially active:

    Policies for Autonomous System number management in the Asia
    Pacific region
    http://www.apnic.net/policy/asn-policy.html


For more information on the history of the four-byte AS number
policy proposal, please see:

    http://www.apnic.net/policy/proposals/prop-032-v002.html


-------------------------------------------------------------
prop-038: Amending APNIC's lame DNS reverse delegation policy
-------------------------------------------------------------

On 1 January 2007,  APNIC's lame DNS reverse delegation policy was
modified to make the definition of lame DNS consistent with the
definitions used by the other RIRs. Under the revised policy, if a
delegated nameserver for a domain fails to return a valid
authoritative answer for the domain's SOA, it will be considered to
be lame. The process for monitoring and removing lame reverse DNS
delegations has also been simplified.

APNIC's lame DNS procedures are detailed at:

    http://www.apnic.net/services/rev-del/lame-del/


For more information on the history of the lame DNS reverse
delegation policy proposal, please see:

    http://www.apnic.net/policy/proposals/prop-038-v001.html


Regards
--------------------------------------------------------------------
Son Tran                              email:           son at apnic dot net
Policy Development Manager, APNIC     sip:        son at voip dot apnic dot net
http://www.apnic.net                  phone:         +61 7 3858 3100
                                      fax:           +61 7 3858 3199
--------------------------------------------------------------------