IETF Logo Mail Archive

Re: [nemo] new requirement for draft-ietf-nemo-requirements

Jari Arkko <jari.arkko@piuha.net> Mon, 04 December 2006 17:24 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrHYd-0006Hx-CA; Mon, 04 Dec 2006 12:24:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrHYc-0006Cv-3c for nemo@ietf.org; Mon, 04 Dec 2006 12:24:46 -0500
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrHYa-0005HM-QX for nemo@ietf.org; Mon, 04 Dec 2006 12:24:46 -0500
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E5F5989865; Mon, 4 Dec 2006 19:24:39 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id C6A388985F; Mon, 4 Dec 2006 19:24:38 +0200 (EET)
Message-ID: <457459D2.6060100@piuha.net>
Date: Mon, 04 Dec 2006 19:24:34 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.8 (X11/20061117)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: [nemo] new requirement for draft-ietf-nemo-requirements
References: <45743493.3010403@piuha.net> <28F4D755-55C4-4DBD-AF93-729A30EE9E3B@gmail.com> <45744302.5030502@piuha.net> <3ff5d001ae78906b9c8337fc0378ae46@it.uc3m.es>
In-Reply-To: <3ff5d001ae78906b9c8337fc0378ae46@it.uc3m.es>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Ross Callon <rcallon@juniper.net>, IETF NEMO WG <nemo@ietf.org>
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

Hi Marcelo,
> I mean, we have discussed this before in this ml. If global HAHA is
> deployed as a global mobility provider i.e. there is a single home
> prefix that aggregates all the home networks from different end sites,
> then, this seems similar to the provider aggregation
> However, if each home network of each nemo is announced seaprately,
> then the number of announced routes increases considerably and i am
> not sure if thi contribution to the global routing tables is acceptable.
I see.
> Anyway, i think the requirement is perfectly ok, we just need to
> understand what is the intended deployment scenarios for global HAHA
> and if those scale well.
>
Ok.

--Jari

v2.23.0 | Report a Bug | By Email