[RAM] Early version of Ivip I-D
Robin Whittle <rw@firstpr.com.au> Tue, 10 July 2007 19:47 UTC
Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1I8Lge-0006ru-9O; Tue, 10 Jul 2007 15:47:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Lgc-0006rm-Ik
for ram@iab.org; Tue, 10 Jul 2007 15:47:50 -0400
Received: from gair.firstpr.com.au ([150.101.162.123])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8LgY-0001lt-0W
for ram@iab.org; Tue, 10 Jul 2007 15:47:50 -0400
Received: from [10.0.0.8] (zita.firstpr.com.au [10.0.0.8])
by gair.firstpr.com.au (Postfix) with ESMTP
id 8EBAF59E47; Wed, 11 Jul 2007 05:47:43 +1000 (EST)
Message-ID: <4693E252.4090507@firstpr.com.au>
Date: Wed, 11 Jul 2007 05:47:30 +1000
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: ram@iab.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: [RAM] Early version of Ivip I-D
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>,
<mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>,
<mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org
Here is a draft version of the forthcoming Ivip I-D: http://www.firstpr.com.au/ip/ivip/temp/draft-whittle-ivip-arch-00-draft.txt http://www.firstpr.com.au/ip/ivip/temp/draft-whittle-ivip-arch-00-draft.html There are about 62 pages of text and diagrams. If anyone is keen enough to read some of this before the weekend and suggest any improvements, point out any blunders etc. I would really appreciate it. I plan to finalise version 00 on Sunday. The operation of Ivip ETRs is simple - they decapsulate. ITRs tunnel to a given address, for every Ivip-mapped destination address. That's it - there's no ITR to ETR communication, no information in the IP-in-IP header, multiple ETR addresses, no explicit mechanisms for TE or trying to determine reachability. There are two reasons why this I-D is relatively long. Firstly I cover an ambitious system by which end-user changes are intended to reach all the ITRs very quickly - in a few seconds ideally, but perhaps faster. Secondly, my explanation is pretty hands-on, with discussion and diagrams. I hope that RAM list members will be able to read it from one end to the other and understand it pretty well without much frustration or head scratching. - Robin http://www.firstpr.com.au/ip/ivip/ _______________________________________________ RAM mailing list RAM@iab.org https://www1.ietf.org/mailman/listinfo/ram
- [RAM] Early version of Ivip I-D Robin Whittle