[sig-policy] Experimental assignment for four-byte AS Numbers

To: sig-policy at lists dot apnic dot net
Subject: [sig-policy] Experimental assignment for four-byte AS Numbers
From: MAEMURA Akinori <maem at maem dot org>
Date: Wed, 26 Jul 2006 11:40:18 +0900
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>


Currently operations community in Japan is discussing about
four byte ASN with concern of slow deployment.

I heard that we have only a few implementations of this 
feature for very big boxes yet.  I'd like to know if we have
a further information about the implementation, but anyway
everyone need to be prepared to accept four byte ASN when 
they are assigned by default.

I think, as well as some other engineers around me, we need 
some experimental ASNs to allow the operators to try four-
byte ASN to check it it will work in the real Internet.


IMHO, [16bit-ASN].23456 , [16bit-ASN].0  and 
[16bit-ASN].[16bit-private-ASN] are obviously available and
once it is agreed among the Internet Operationss Community
it can be used for any trial, and we can do that through 
RIRs poliy process, or IETF/RFC process like RFC1797 net 39
experiment.


I'd like to have your ideas around this, and take some
actions toward this idea if needed.


Regards,
-----
MAEMURA Akinori                                maem at maem dot org