ASN request ------------------------------------------------------------------------------------- Who will use the requested ASN?* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Which address prefix will originate from the new AS number?* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Peering contacts: Please list the email contact addresses of peering partners for the requested AS Number and their AS Number. At least two peering partners must be specified.* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 32-bit AS Numbers are assigned by default. If you require a 16-bit AS Number, please indicate this below and tell us why. For more information, see http://www.ripe.net/news/asn-32-guide.html <> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Contact details (this information will be published in the RIPE db): Specify contact details for the administrative contact person(s)*: Specify contact details for the technical contact person(s)*: Please specify an e-mail address for handeling of abuse reports*: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Any requests for the aut-num object may be added below (will be published in the RIPE db): aut-num: ASNEW as-name: descr: org: import: export: import: export: admin-c: tech-c: mnt-by: RIPE-NCC-END-MNT mnt-by: RESILANS-MNT mnt-by: mnt-routes: changed: hostmaster@ripe.net source: RIPE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Supplemental comments: Please add more information if you think it will help us understand this request. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Fields marked with * are mandatory.