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>
Cc: Hesham Soliman <H.Soliman@flarion.com>, Vijay.Devarapalli@AzaireNet.com,
 ml-nemo WG <nemo@ietf.org>
Precedence: list
Errors-To: nemo-bounces@ietf.org


El 21/04/2006, a las 10:26, Pascal Thubert (pthubert) escribi=F3:
....

> 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     |
            |         =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DHAHA=3DTUNNEL=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D         |
            |         | ....           ;          .... |         |
            |         | .<- 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=20
announced belongs to the SITE and NOT to the provider. This i read as=20
PI for end sites being injected in the DFZ.

I couldn't find the concept of mobile ISP consortiums anywhere in the=20
draft, which seems to be a key role player in your supposed deployment=20=

model (but maybe i missed that...)

OTOH, i did see several emails from potential users that claimed that=20
mobile platforms needed PI addressing

now these are the users that will be deploying this stuff and they said=20=

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=20=

can i say, this is what i could infer from what i read in the draft and=20=

the comments in the mailing list.... probably i am too short...

regards, marcelo



> Pascal
>