summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOthmar Gsenger <otti@anytun.org>2007-03-02 20:06:30 +0000
committerOthmar Gsenger <otti@anytun.org>2007-03-02 20:06:30 +0000
commit7527ec79ff342505237fbee8d410baf7af2a3541 (patch)
treecd60b021162374e8307016dfdd07b2fc4453600c
parentinitial check in (diff)
minimal version of internet draft
-rw-r--r--draft-gsenger-anycast-relay-00.txt280
-rw-r--r--internet-draft-anytun.xml52
2 files changed, 332 insertions, 0 deletions
diff --git a/draft-gsenger-anycast-relay-00.txt b/draft-gsenger-anycast-relay-00.txt
new file mode 100644
index 0000000..c3064f4
--- /dev/null
+++ b/draft-gsenger-anycast-relay-00.txt
@@ -0,0 +1,280 @@
+
+
+
+Network Working Group O. Gsenger
+Internet-Draft March 2, 2007
+Expires: September 3, 2007
+
+
+ Anycast stream relaying
+ draft-gsenger-anycast-relay-00
+
+Status of this Memo
+
+ By submitting this Internet-Draft, each author represents that any
+ applicable patent or other IPR claims of which he or she is aware
+ have been or will be disclosed, and any of which he or she becomes
+ aware will be disclosed, in accordance with Section 6 of BCP 79.
+
+ Internet-Drafts are working documents of the Internet Engineering
+ Task Force (IETF), its areas, and its working groups. Note that
+ other groups may also distribute working documents as Internet-
+ Drafts.
+
+ Internet-Drafts are draft documents valid for a maximum of six months
+ and may be updated, replaced, or obsoleted by other documents at any
+ time. It is inappropriate to use Internet-Drafts as reference
+ material or to cite them other than as "work in progress."
+
+ The list of current Internet-Drafts can be accessed at
+ http://www.ietf.org/ietf/1id-abstracts.txt.
+
+ The list of Internet-Draft Shadow Directories can be accessed at
+ http://www.ietf.org/shadow.html.
+
+ This Internet-Draft will expire on September 3, 2007.
+
+Copyright Notice
+
+ Copyright (C) The IETF Trust (2007).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger Expires September 3, 2007 [Page 1]
+
+Internet-Draft Anycast stream relaying March 2007
+
+
+Abstract
+
+ Anycast tunneling
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger Expires September 3, 2007 [Page 2]
+
+Internet-Draft Anycast stream relaying March 2007
+
+
+1. The Middle
+
+1.1. The section
+
+1.1.1. inner section
+
+Appendix A. The appan
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger Expires September 3, 2007 [Page 3]
+
+Internet-Draft Anycast stream relaying March 2007
+
+
+Author's Address
+
+ Othmar Gsenger
+ Sporgasse 6
+ Graz 8010
+ AT
+
+ Phone:
+ Email: otti@wirdorange.org
+ URI: http://anytun.org/
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger Expires September 3, 2007 [Page 4]
+
+Internet-Draft Anycast stream relaying March 2007
+
+
+Full Copyright Statement
+
+ Copyright (C) The IETF Trust (2007).
+
+ This document is subject to the rights, licenses and restrictions
+ contained in BCP 78, and except as set forth therein, the authors
+ retain all their rights.
+
+ This document and the information contained herein are provided on an
+ "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
+ OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
+ THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
+ OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
+ THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
+ WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+
+
+Intellectual Property
+
+ The IETF takes no position regarding the validity or scope of any
+ Intellectual Property Rights or other rights that might be claimed to
+ pertain to the implementation or use of the technology described in
+ this document or the extent to which any license under such rights
+ might or might not be available; nor does it represent that it has
+ made any independent effort to identify any such rights. Information
+ on the procedures with respect to rights in RFC documents can be
+ found in BCP 78 and BCP 79.
+
+ Copies of IPR disclosures made to the IETF Secretariat and any
+ assurances of licenses to be made available, or the result of an
+ attempt made to obtain a general license or permission for the use of
+ such proprietary rights by implementers or users of this
+ specification can be obtained from the IETF on-line IPR repository at
+ http://www.ietf.org/ipr.
+
+ The IETF invites any interested party to bring to its attention any
+ copyrights, patents or patent applications, or other proprietary
+ rights that may cover technology that may be required to implement
+ this standard. Please address the information to the IETF at
+ ietf-ipr@ietf.org.
+
+
+Acknowledgment
+
+ Funding for the RFC Editor function is provided by the IETF
+ Administrative Support Activity (IASA).
+
+
+
+
+
+Gsenger Expires September 3, 2007 [Page 5]
+
diff --git a/internet-draft-anytun.xml b/internet-draft-anytun.xml
new file mode 100644
index 0000000..fc116e4
--- /dev/null
+++ b/internet-draft-anytun.xml
@@ -0,0 +1,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>RFC</keyword>
+ <keyword>Request for Comments</keyword>
+ <keyword>I-D</keyword>
+ <keyword>Internet-Draft</keyword>
+ <keyword>XML</keyword>
+ <keyword>Extensible Markup Language</keyword>-->
+ <abstract>
+ <t>Anycast tunneling
+ </t>
+ </abstract>
+ </front>
+ <middle>
+ <section title='The Middle'>
+ ...
+ <section title='The section'>
+ ...
+ <section title='inner section'>...</section>
+ </section>
+ <appendix title='The appan'></appendix>
+ </section>
+ </middle>
+ <back>
+ </back>
+ </rfc>