Re: RO approaches and the proposed charter (was Re: About the proposed charter and global HAHA (was Re: [nemo] RE: About route aggregation in global HAHA
marcelo bagnulo braun <marcelo@it.uc3m.es> Fri, 21 April 2006 08:32 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWr4L-0000h0-TS; Fri, 21 Apr 2006 04:32:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWr4J-0000gu-EA for nemo@ietf.org; Fri, 21 Apr 2006 04:32:47 -0400
Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWr4H-0000Ui-Un for nemo@ietf.org; Fri, 21 Apr 2006 04:32:47 -0400
Received: from n2.nomadiclab.com (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 1A749212C59; Fri, 21 Apr 2006 11:32:45 +0300 (EEST)
Received: from outside.nomadiclab.com (d146.nomadiclab.com [193.234.218.146]) by n2.nomadiclab.com (Postfix) with ESMTP id D6662212C44; Fri, 21 Apr 2006 11:32:44 +0300 (EEST)
Received: from outside.nomadiclab.com (localhost [127.0.0.1]) by outside.nomadiclab.com (Postfix) with ESMTP id 874F7BDC40; Fri, 21 Apr 2006 11:32:44 +0300 (EEST)
Received: from [193.234.219.179] (w179.nomadiclab.com [193.234.219.179]) by outside.nomadiclab.com (Postfix) with ESMTP id 4FF7FBDC38; Fri, 21 Apr 2006 11:32:44 +0300 (EEST)
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC021512A9@xmb-ams-337.emea.cisco.com>
References: <7892795E1A87F04CADFCCF41FADD00FC021512A9@xmb-ams-337.emea.cisco.com>
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Message-Id: <0da912b0ea840b7bf37244ac1d384d6b@it.uc3m.es>
Content-Transfer-Encoding: quoted-printable
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
Subject: Re: RO approaches and the proposed charter (was Re: About the proposed charter and global HAHA (was Re: [nemo] RE: About route aggregation in global HAHA
Date: Fri, 21 Apr 2006 11:32:43 +0300
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
X-Mailer: Apple Mail (2.623)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: Hesham Soliman <H.Soliman@flarion.com>, Vijay.Devarapalli@AzaireNet.com, ml-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
El 21/04/2006, a las 10:26, Pascal Thubert (pthubert) escribió:
....
> In fact, there could be a very limited set of mobile ISP consortiums,
> and a single prefix in the DFZ for each of those.
Interesting....
However, this is NOT presented anywhere in the draft
actually what it is actually in the draft is
5.1 Initial routing
5.1.1 External routing
Sites are expected to be connected locally to the internet, via the
network of one or more service provider. Each site has a default
route to the internet via that connection.
. .. /
--------- ........ ..;. ---------
| | .. / ..... | |
| ::/0 -> .... ; ... <- ::/0 |
| ============HAHA=TUNNEL=========== |
| | .... ; .... | |
| | .<- Home::/32 / Home::/32 ->..| |
--------- ... ; ... ---------
..... / ..
. ;.... ......
/ ..........
In return, each site advertises the aggregation that encompasses the
Distributed Home Network aggregation back into the service provider
network, to the outside world (the internet).
Please note that we have sites and providers here and the prefix
announced belongs to the SITE and NOT to the provider. This i read as
PI for end sites being injected in the DFZ.
I couldn't find the concept of mobile ISP consortiums anywhere in the
draft, which seems to be a key role player in your supposed deployment
model (but maybe i missed that...)
OTOH, i did see several emails from potential users that claimed that
mobile platforms needed PI addressing
now these are the users that will be deploying this stuff and they said
they want PI for this...
> So yes, like anything else, global HAHA could be deployed stupidly,
> but guess what, people will know better.
>
Now maybe may idea about how to deploy this is indeed stupid, but what
can i say, this is what i could infer from what i read in the draft and
the comments in the mailing list.... probably i am too short...
regards, marcelo
> Pascal
>
- RE: RO approaches and the proposed charter (was R… Pascal Thubert (pthubert)
- Re: RO approaches and the proposed charter (was R… marcelo bagnulo braun
- RE: RO approaches and the proposed charter (was R… Pascal Thubert (pthubert)
- [nemo] Re: globalHAHA can not guarantee shorter p… Alexandru Petrescu