3 Document ID: ripe-390
\r
6 % ADDRESSES WILL BE USED FOR
\r
7 % AN INTERNET EXPERIMENT
\r
9 % Anycast Assignment Request Form
\r
11 % RIPE NCC members can use this form to request an anycast assignment.
\r
12 % Please see ripe-391 for instructions on how to complete this form.
\r
14 #[GENERAL INFORMATION]#
\r
16 % Please add your RegID.
\r
18 request-type: anycast-assignment
\r
22 #[ADDRESS SPACE USER]#
\r
24 % Which TLD operator will use the requested address space?
\r
26 legal-organisation-name: Othmar Gsenger
\r
28 organisation-location: Graz, Austria
\r
29 website-if-available: http://www.gsenger.com/satp/
\r
31 % Does this End User already have address space in use for
\r
36 % Will the End User return any address space?
\r
38 address-space-returned:
\r
40 #[INITIAL INFORMATION]#
\r
42 % Does the End User accept the policies on anycast assignments?
\r
43 % http://www.ripe.net/ripe/docs/ipv4-policies.html
\r
44 % http://www.ripe.net/ripe/docs/ipv6policy.html (Yes/No)
\r
49 % Can the End Users TLD nameserver set pass the IANA
\r
50 % Administrative Procedure for Root Zone Name Server Delegation
\r
51 % and Glue Data without using anycast technology?
\r
52 % http://www.iana.org/procedures/delegation-data.html (Yes/No)
\r
56 % Is the End User requesting an IPv4 assignment, an IPv6
\r
57 % assignment, or both? (IPv4/IPv6/Both)
\r
61 % If the End User is requesting an IPv4 assignment, will the TLD
\r
62 % nameserver set apply anycasting as described in RFC3258?
\r
63 % http://www.ietf.org/rfc/rfc3258.txt (Yes/No)
\r
66 % as far as appropriate
\r
68 #[ANYCAST NODE PLAN]#
\r
70 % Which anycast nodes will be used?
\r
72 Node Name Peers Location
\r
74 node: 0xff Graz AS42729 Graz, Austria
\r
75 node: mur.at Graz AS39837 Graz, Austria
\r
76 node: 0xff Wien AS35492 Vienna, Austria
\r
80 #[NETWORK DESCRIPTION]#
\r
82 % Please add more information if you think it will help us understand
\r
85 The IP addresses will be used for an internet experiment.
\r
87 The experimental assignments will not be used for commericial purposes during or
\r
88 after the experiment.
\r
90 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.
\r
92 All results of the internet experiment will be published online.
\r
94 We plan to finish the experiment at the end of february 2008.
\r
96 secure anycast tunneling protocol:
\r
97 http://www.ietf.org/internet-drafts/draft-gsenger-secure-anycast-tunneling-protocol-00.txt
\r
99 description of the internet experiment:
\r
100 http://www.gsenger.com/satp/internet-experiment-proposal.txt
\r
102 #[NETWORK DIAGRAM]#
\r
104 % Have you attached a network diagram to this request? (Yes/No)
\r
106 diagram-attached: No
\r
108 #[DATABASE TEMPLATE(S)]#
\r
111 % Please complete all of the fields below.
\r
114 netname: SECANY-NET
\r
115 descr: experimental anycast network used
\r
116 descr: for testing the
\r
117 descr: secure anycast tunneling protocol
\r
118 descr: see http://www.anytun.org
\r
121 org: ORG-OTTI1-RIPE
\r
122 admin-c: OG674-RIPE
\r
124 status: ASSIGNED ANYCAST
\r
125 mnt-by: RIPE-NCC-HM-MNT
\r
126 mnt-lower: RIPE-NCC-HM-MNT
\r
128 mnt-routes: OTTI-MNT
\r
129 mnt-domains: OTTI-MNT
\r
130 changed: hostmaster@ripe.net
\r
134 % Please complete all of the fields below.
\r
137 netname: SECANY-NET
\r
138 descr: experimental anycast network used
\r
139 descr: for testing the
\r
140 descr: secure anycast tunneling protocol
\r
141 descr: see http://www.anytun.org
\r
144 org: ORG-OTTI1-RIPE
\r
145 admin-c: OG674-RIPE
\r
147 status: ASSIGNED ANYCAST
\r
148 mnt-by: RIPE-NCC-HM-MNT
\r
149 mnt-lower: RIPE-NCC-HM-MNT
\r
151 mnt-routes: OTTI-MNT
\r
152 mnt-domains: OTTI-MNT
\r
153 changed hostmaster@ripe.net
\r