blob: ce340bf92cb03923ffb1e3382e089eb5da3ff803 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
<?xml version='1.0'?>
<!DOCTYPE rfc SYSTEM 'rfcXXXX.dtd'>
<rfc ipr='full3978' docName='draft-gsenger-anycast-relay-00'>
<front>
<title>Anycast stream relaying</title>
<author initials='O.G.' surname='Gsenger'
fullname='Othmar Gsenger'>
<organization></organization>
<address>
<postal>
<street>Sporgasse 6</street>
<city>Graz</city>
<code>8010</code>
<country>AT</country>
</postal>
<phone></phone>
<email>otti@wirdorange.org</email>
<uri>http://anytun.org/</uri>
</address>
</author>
<date month='March' year='2007' />
<area>General</area>
<workgroup></workgroup>
<keyword>anytun</keyword>
<keyword>Internet-Draft</keyword>
<keyword>Anycast tunneling / relaying</keyword>
<abstract>
<t>The anycast tunneling (anytun) protocol defines a protocol used for communication between unicast clients and anycast servers. It can be used for tunneling information between 2 clients or in relay mode to transmit data form the client over the servers to a third party not using the protocol and vice versa.
</t>
</abstract>
</front>
<middle>
<section title='Introduction'>
...
<section title='The section'>
...
<section title='inner section'>...</section>
</section>
<appendix title='The appan'></appendix>
</section>
</middle>
<back>
<references title='Normative References'>
&rfc3068;
</references>
</back>
</rfc>
|
