diff options
| author | Christian Pointner <equinox@anytun.org> | 2009-12-05 13:37:34 +0000 |
|---|---|---|
| committer | Christian Pointner <equinox@anytun.org> | 2009-12-05 13:37:34 +0000 |
| commit | 62774a5d9ede8c9c23dc4208022508c2308404f2 (patch) | |
| tree | 8bd563df4554f41fdbc8c5bc8ab99d05846c7b6a /ripe-request | |
| parent | initial checkin (tags, trunk, branches) (diff) | |
added all common stuff from anytun repo
Diffstat (limited to 'ripe-request')
| -rw-r--r-- | ripe-request/ripe-390.txt | 156 | ||||
| -rw-r--r-- | ripe-request/ripe-406.txt | 172 | ||||
| -rw-r--r-- | ripe-request/ripe-410.txt | 106 |
3 files changed, 434 insertions, 0 deletions
diff --git a/ripe-request/ripe-390.txt b/ripe-request/ripe-390.txt new file mode 100644 index 0000000..47ccce7 --- /dev/null +++ b/ripe-request/ripe-390.txt @@ -0,0 +1,156 @@ +RIPE NCC
+
+Document ID: ripe-390
+Date: September 2006
+
+% ADDRESSES WILL BE USED FOR
+% AN INTERNET EXPERIMENT
+%
+% Anycast Assignment Request Form
+
+% RIPE NCC members can use this form to request an anycast assignment.
+% Please see ripe-391 for instructions on how to complete this form.
+
+#[GENERAL INFORMATION]#
+%
+% Please add your RegID.
+
+request-type: anycast-assignment
+form-version: 1.0
+x-ncc-regid: at.mur
+
+#[ADDRESS SPACE USER]#
+%
+% Which TLD operator will use the requested address space?
+
+legal-organisation-name: Othmar Gsenger
+tld(s): n/a
+organisation-location: Graz, Austria
+website-if-available: http://www.gsenger.com/satp/
+
+% Does this End User already have address space in use for
+% anycast? (Yes/No)
+
+space-available: No
+
+ % Will the End User return any address space?
+
+address-space-returned:
+
+#[INITIAL INFORMATION]#
+%
+% Does the End User accept the policies on anycast assignments?
+% http://www.ripe.net/ripe/docs/ipv4-policies.html
+% http://www.ripe.net/ripe/docs/ipv6policy.html (Yes/No)
+
+confirmation: Yes
+
+
+% Can the End Users TLD nameserver set pass the IANA
+% Administrative Procedure for Root Zone Name Server Delegation
+% and Glue Data without using anycast technology?
+% http://www.iana.org/procedures/delegation-data.html (Yes/No)
+
+iana-procedure: No
+
+% Is the End User requesting an IPv4 assignment, an IPv6
+% assignment, or both? (IPv4/IPv6/Both)
+
+ip-version: Both
+
+% If the End User is requesting an IPv4 assignment, will the TLD
+% nameserver set apply anycasting as described in RFC3258?
+% http://www.ietf.org/rfc/rfc3258.txt (Yes/No)
+
+rfc3258: Yes
+% as far as appropriate
+
+#[ANYCAST NODE PLAN]#
+%
+% Which anycast nodes will be used?
+
+ Node Name Peers Location
+
+node: 0xff Graz AS42729 Graz, Austria
+node: mur.at Graz AS39837 Graz, Austria
+node: 0xff Wien AS35492 Vienna, Austria
+
+number-of-nodes: 3
+
+#[NETWORK DESCRIPTION]#
+%
+% Please add more information if you think it will help us understand
+% this request.
+
+The IP addresses will be used for an internet experiment.
+
+The experimental assignments will not be used for commericial purposes during or
+after the experiment.
+
+The reference implementation of the secure anycast tunneling protocol will be used to build a highly redundant and scaleable voice over ip media relay cluster.
+
+All results of the internet experiment will be published online.
+
+We plan to finish the experiment at the end of february 2008.
+
+secure anycast tunneling protocol:
+http://www.ietf.org/internet-drafts/draft-gsenger-secure-anycast-tunneling-protocol-00.txt
+
+description of the internet experiment:
+http://www.gsenger.com/satp/internet-experiment-proposal.txt
+
+#[NETWORK DIAGRAM]#
+%
+% Have you attached a network diagram to this request? (Yes/No)
+
+diagram-attached: No
+
+#[DATABASE TEMPLATE(S)]#
+%
+% IPv4
+% Please complete all of the fields below.
+
+inetnum:
+netname: SECANY-NET
+descr: experimental anycast network used
+descr: for testing the
+descr: secure anycast tunneling protocol
+descr: see http://www.anytun.org
+country: EU
+country: AT
+org: ORG-OTTI1-RIPE
+admin-c: OG674-RIPE
+tech-c: OG674-RIPE
+status: ASSIGNED ANYCAST
+mnt-by: RIPE-NCC-HM-MNT
+mnt-lower: RIPE-NCC-HM-MNT
+mnt-by: OTTI-MNT
+mnt-routes: OTTI-MNT
+mnt-domains: OTTI-MNT
+changed: hostmaster@ripe.net
+source: RIPE
+
+% IPv6
+% Please complete all of the fields below.
+
+inet6num:
+netname: SECANY-NET
+descr: experimental anycast network used
+descr: for testing the
+descr: secure anycast tunneling protocol
+descr: see http://www.anytun.org
+country: EU
+country: AT
+org: ORG-OTTI1-RIPE
+admin-c: OG674-RIPE
+tech-c: OG674-RIPE
+status: ASSIGNED ANYCAST
+mnt-by: RIPE-NCC-HM-MNT
+mnt-lower: RIPE-NCC-HM-MNT
+mnt-by: OTTI-MNT
+mnt-routes: OTTI-MNT
+mnt-domains: OTTI-MNT
+changed hostmaster@ripe.net
+source: RIPE
+
+#[END of REQUEST]#
diff --git a/ripe-request/ripe-406.txt b/ripe-request/ripe-406.txt new file mode 100644 index 0000000..44c197e --- /dev/null +++ b/ripe-request/ripe-406.txt @@ -0,0 +1,172 @@ +Supporting Notes for the Autonomous System Number Request Form
+
+RIPE NCC
+
+Document ID: ripe-395
+Date: November 2006
+Obsoletes: ripe-335, ripe-355
+
+
+
+This document contains instructions for LIRs on how to complete the "Autonomous System Number Request Form"
+http://www.ripe.net/ripe/docs/asnrequestform.html
+
+The instructions are based on the "Autonomous System (AS) Number Assignment Policies and Procedures"
+http://www.ripe.net/ripe/docs/asn-assignment.html
+
+For an explanation on when an AS Number is needed,
+please see: "Guidelines for Creation, Selection and Registration of an Autonomous System" (RFC 1930)
+ftp://ftp.ripe.net/rfc/rfc1930.txt
+
+For more information on language specifications,
+please see "Routing Policy Specification Language (RPSL)" (RFC 2622) and "RPSL extensions for 32 bit AS Numbers".
+ftp://ftp.ripe.net/rfc/rfc2622.txt and http://www.ietf.org/internet-drafts/draft-uijterwaal-rpsl-4byteas-ext-02.txt
+
+
+General Information
+AS Number User
+Address Space to be Announced
+Peering Contacts
+Database Template(s)
+Insert Supplemental Comments
+End of Request
+
+
+General Information
+
+#[GENERAL INFORMATION]#
+
+%
+% Please add your RegID.
+
+request-type: as-number
+form-version: 1.1
+x-ncc-regid:
+
+Please do not change the value of the "request-type:" and "form-version:" fields.
+
+Enter your Registry Identifier (RegID) in the "x-ncc-regid:" field. RegIDs have the following format: <country code>.<name>.
+
+If you do not know your RegID, please contact <ncc@ripe.net>.
+
+AS Number User
+
+#[AS NUMBER USER]#
+%
+% Who will use the requested AS Number?
+
+legal-organisation-name: North SantaBank
+website-if-available: http://www.nsb.nn
+
+Enter the legal name of the organisation that will use this AS Number in the "legal-organisation-name:" field. If this organisation has a website, enter the URL in the "website-if-available:" field. Otherwise, enter "none" in this field.
+
+Address Space to be Announced
+
+#[ADDRESS SPACE TO BE ANNOUNCED]#
+%
+% Which address prefix will originate from the new AS Number?
+
+prefix: 192.0.2.0/24
+
+% If the address assignment is waiting for approval, please
+% include the ticket number of the request below.
+
+pending-ticket-ID:
+
+You must include either an address prefix or a pending RIPE NCC ticket number (for example, NCC#xxxxxxxx).
+
+Please specify address prefixes using slash notation (for example, x.x.x.x/xx ). The address space must be a valid assignment to the organisation that will use the AS number.
+
+Peering Contacts
+
+#[PEERING CONTACTS]#
+%
+% Please list the e-mail contact addresses of peering
+% partners for the requested AS Number.
+
+peering: noddy@grottoinvestments.nn
+peering: mary@northernbanking.nn
+
+You must list the email addresses of at least two peering partners in the "peering:" fields. You can repeat the "peering:" field as many times as needed.
+
+Database Template(s)
+
+#[DATABASE TEMPLATE(S)]#
+%
+% Please complete all of the fields below.
+
+aut-num: ASNEW
+as-name: NSB-AS
+descr: North SantaBank's AS Number
+org: ORG-NS31-RIPE
+import: from AS64532 accept ANY
+export: to AS64532 announce ASNEW
+import: from AS64518 accept ANY
+export: to AS64518 announce ASNEW
+admin-c: ACM2-RIPE
+tech-c: HOHO1-RIPE
+mnt-by: SANTA-MNT
+mnt-routes: SANTA-MNT
+changed: hostmaster@ripe.net
+source: RIPE
+
+The "aut-num:" field must be ASNEW as we (RIPE NCC) will choose the AS number.
+
+The "as-name:" should be a short name associated with the Autonomous System. We recommend that the name reflects the name of the organisation that will use the AS Number.
+
+Enter a short description of the Autonomous System in the "descr:" field.
+
+Enter the org-ID of the AS Number user's organisation object in the "org:" field.
+
+The "import:" and "export:" fields should contain the complete routing policy. Both fields may be repeated as many times as needed.
+
+Basic syntax entries are as follows:
+
+ import: from <peer1> accept <filter>
+ export: to <peer1> announce <filter>
+ import: from <peer2> accept <filter>
+ export: to <peer2> announce <filter>
+
+For further details of language specifications, please refer to RFC 2622 and "RPSL extensions for 32 bit AS Numbers".
+ftp://ftp.ripe.net/rfc/rfc2622.txt and http://www.ietf.org/internet-drafts/draft-uijterwaal-rpsl-4byteas-ext-02.txt.
+
+The nic-handle of the role or person object in the "admin-c:" field should reflect someone who is administratively responsible for the network.
+
+The nic-handle of the role or person object in the "tech-c:" field should reflect someone who has technical knowledge of the network.
+
+The "mnt-by" field shows which maintainer authenticates object updates. The "mnt-routes:" field shows which maintainer authenticates the creation of route objects.
+
+You can put the LIR's or AS Number User's maintainers in the "mnt-by:" and "mnt-routes:" fields.
+
+The RIPE Database must contain all of the objects that you use.
+
+The "changed:" field must be hostmaster@ripe.net.
+
+The "source:" field must be RIPE.
+
+Insert Supplemental Comments
+#[INSERT SUPPLEMENTAL COMMENTS]#
+%
+% Please add more information if you think it will help
+% us understand this request.
+
+Our peering agreements are provisional and will be confirmed when the new AS Number is assigned.
+We would like a 4-byte AS Number.
+
+You can use this space for additional information that you think will be helpful for us when we evaluate your request. For example, if you would like a 4-byte AS Number, use this field to let us know.
+
+From 1 January 2007 you can request a 4-byte AS Number. If you would like a 4-byte AS Number, use the Supplemental Comments field to let us know. If you give no preference, we will assign a 2-byte AS Number.
+
+From 1 January 2009, you can use the Supplemental Comments field to let us know if you would like a 2-byte AS Number. If you give no preference, we will assign a 4-byte AS Number.
+
+From 1 January 2010 we will assign 4-byte AS Numbers only.
+
+End of Request
+
+#[END of REQUEST]#
+
+Best Regards,
+Jan Janssen, Bluelight Admin
+
+Please write your full name below the " #[END of REQUEST]# " header.
+
diff --git a/ripe-request/ripe-410.txt b/ripe-request/ripe-410.txt new file mode 100644 index 0000000..966bf35 --- /dev/null +++ b/ripe-request/ripe-410.txt @@ -0,0 +1,106 @@ +RIPE NCC
+
+Doc-ID: ripe-410
+Date: October 2005
+Obsolete: ripe-334, ripe-354, ripe-396
+
+
+% ADDRESSES WILL BE USED FOR
+% AN INTERNET EXPERIMENT
+%
+
+% RIPE NCC members can use this form to request an Autonomous System (AS) Number.
+% Please see ripe-406 for instructions on how to complete this form.
+
+
+#[GENERAL INFORMATION]#
+%
+% Please add your RegID.
+
+request-type: as-number
+form-version: 1.1
+x-ncc-regid: at.mur
+
+
+#[AS NUMBER USER]#
+%
+% Who will use the requested AS Number?
+
+legal-organisation-name: Othmar Gsenger
+website-if-available: http://www.gsenger.com/satp/
+
+
+#[ADDRESS SPACE TO BE ANNOUNCED]#
+%
+% Which address prefix will originate from the new AS Number?
+
+prefix: 77.87.240.0/21
+prefix: 2001:7fc::/32
+
+% If the address assignment is waiting for approval, please
+% include the ticket number of the request below.
+
+pending-ticket-ID:
+
+
+#[PEERING CONTACTS]#
+%
+% What are the e-mail addresses of the peering
+% partners for the requested AS Number?
+
+peering: noc@mur.at
+peering: ripe@wirdorange.org
+peering: ripe-tech@funkfeuer.at
+
+
+#[DATABASE TEMPLATE(S)]#
+%
+% Please complete all of the fields below.
+
+aut-num: ASNEW
+as-name: OTTI-AS
+descr: Othmar Gsenger
+descr: experimental anycast AS
+org: ORG-OTTI1-RIPE
+import: from AS42729 action pref=1; accept ANY
+export: to AS42729 announce ASNEW
+import: from AS39837 action pref=1; accept ANY
+export: to AS39837 announce ASNEW
+import: from AS35492 action pref=1; accept ANY
+export: to AS35492 announce ASNEW
+admin-c: OG674-RIPE
+tech-c: OG674-RIPE
+mnt-by: OTTI-MNT
+mnt-routes: OTTI-MNT
+changed: hostmaster@ripe.net
+source: RIPE
+
+
+#[INSERT SUPPLEMENTAL COMMENTS]#
+%
+% Please add more information if you think it will help
+% us understand this request.
+
+The AS number will be used for an internet experiment.
+
+The reference implementation of the secure anycast tunneling protocol will be used to build a highly redundant and scaleable voice over ip media relay cluster.
+
+The experimental assignments will not be used for commericial purposes during or
+after the experiment.
+
+All results of the internet experiment will be published online.
+
+We plan to finish the experiment at the end of february 2008.
+
+secure anycast tunneling protocol:
+http://www.ietf.org/internet-drafts/draft-gsenger-secure-anycast-tunneling-protocol-00.txt
+
+description of the internet experiment:
+http://www.gsenger.com/satp/internet-experiment-proposal.txt
+
+Our peering agreements are provisional and
+will be confirmed when the new AS Number is assigned.
+
+
+#[END of REQUEST]#
+
|