Re: [nemo] new requirement for draft-ietf-nemo-requirements
Jari Arkko <jari.arkko@piuha.net> Mon, 04 December 2006 17:22 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrHWU-0004hH-TH; Mon, 04 Dec 2006 12:22:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrHWU-0004hC-CY for nemo@ietf.org; Mon, 04 Dec 2006 12:22:34 -0500
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrHWS-0004sI-2u for nemo@ietf.org; Mon, 04 Dec 2006 12:22:34 -0500
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 64CF989865; Mon, 4 Dec 2006 19:22:20 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id E21BF8985F; Mon, 4 Dec 2006 19:22:19 +0200 (EET)
Message-ID: <45745948.50508@piuha.net>
Date: Mon, 04 Dec 2006 19:22:16 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.8 (X11/20061117)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [nemo] new requirement for draft-ietf-nemo-requirements
References: <45743493.3010403@piuha.net> <45744331.90300@motorola.com>
In-Reply-To: <45744331.90300@motorola.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: IETF NEMO WG <nemo@ietf.org>, Ross Callon <rcallon@juniper.net>
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Errors-To: nemo-bounces@ietf.org
Alex, > This is also to mention that apart from the NEMOv6 protocol, and apart > from this requirements document, this requriement may be challenged in > certain contexts, especially knowing that network mobility with BGP has > been shown to be working for a small setting. It indeed works, and works quite well, in a small setting. There is no debate about that, but I think everyone agrees that when we have tens of thousands of networks like that then we have to do something else. My back-of-the-envelope calculations indicated that running all of commercial airliners with this scheme would roughly double global BGP update traffic. In any case, I don't think anyone needs to challenge the requirement as such -- the intention was not to claim that in small scale this would be a problem. --Jari
- [nemo] new requirement for draft-ietf-nemo-requir… Jari Arkko
- Re: [nemo] new requirement for draft-ietf-nemo-re… RYUJI WAKIKAWA
- Re: [nemo] new requirement for draft-ietf-nemo-re… Jari Arkko
- Re: [nemo] new requirement for draft-ietf-nemo-re… Alexandru Petrescu
- Re: [nemo] new requirement for draft-ietf-nemo-re… Alexandru Petrescu
- Re: [nemo] new requirement for draft-ietf-nemo-re… marcelo bagnulo braun
- Re: [nemo] new requirement for draft-ietf-nemo-re… Jari Arkko
- Re: [nemo] new requirement for draft-ietf-nemo-re… Jari Arkko
- Re: [nemo] new requirement for draft-ietf-nemo-re… RYUJI WAKIKAWA
- RE: [nemo] new requirement for draft-ietf-nemo-re… Davis, Terry L
- RE: [nemo] new requirement for draft-ietf-nemo-re… Hesham Soliman
- Re: [nemo] new requirement for draft-ietf-nemo-re… Vijay Devarapalli
- Re: [nemo] new requirement for draft-ietf-nemo-re… marcelo bagnulo braun
- Re: [nemo] new requirement for draft-ietf-nemo-re… Alexandru Petrescu
- Re: [nemo] new requirement for draft-ietf-nemo-re… Thierry Ernst
- RE: [nemo] new requirement for draft-ietf-nemo-re… Narayanan, Vidya
- RE: [nemo] new requirement for draft-ietf-nemo-re… Vijay Devarapalli
- Re: [nemo] new requirement for draft-ietf-nemo-re… Jari Arkko