Re: [MEXT] mext-cga-01

Julien Laganier <julien.ietf@gmail.com> Thu, 17 February 2011 06:41 UTC

Return-Path: <julien.ietf@gmail.com>
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 438143A6CE6 for <mext@core3.amsl.com>; Wed, 16 Feb 2011 22:41:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.182
X-Spam-Level:
X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[AWL=0.417, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGuZthKnXjjp for <mext@core3.amsl.com>; Wed, 16 Feb 2011 22:41:02 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 277C63A6CDB for <mext@ietf.org>; Wed, 16 Feb 2011 22:41:01 -0800 (PST)
Received: by fxm9 with SMTP id 9so2380275fxm.31 for <mext@ietf.org>; Wed, 16 Feb 2011 22:41:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=jtBWRl6yue4zWmmgl3bXbDOymycqser4YNsHOhB1Z+g=; b=QlDh+Vz+KXnDV4uCl8tqWAqV9h2p8tVVSsdzIkTROKx6wMbwEybXHlZCibec2DK8BP /UIxnFvjCz3o65qmjX5ELfZQibf5F73Ok0S7BWHeb76NJHxk1ELKzrXPb3f4tCEz/xxJ 9K4lTWNquA0pArsw9eFBdD0yQMQOx/PAWkub8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=URNqOMmkf7jdmC/BIPioWJ3bHm0nQm3SIwwMB64tS0ndMtOpazuhkqA3/3e+7y2CZj L2kf06lbWW/ZPaqLzbr3i0cAQW0VwavWRJ19OT1owveDUHOTna07yA5NbyDBySwvCHVg ChoTseGK+stV1DqRVmRrJT/AsHVjg55k6PZaQ=
MIME-Version: 1.0
Received: by 10.223.71.200 with SMTP id i8mr1905793faj.142.1297924890345; Wed, 16 Feb 2011 22:41:30 -0800 (PST)
Received: by 10.223.74.142 with HTTP; Wed, 16 Feb 2011 22:41:30 -0800 (PST)
In-Reply-To: <6734441090350776921@unknownmsgid>
References: <AcvKlbYpTSAY67aUS3Gy33tPKL0w4w==> <6734441090350776921@unknownmsgid>
Date: Wed, 16 Feb 2011 22:41:30 -0800
Message-ID: <AANLkTi=QuC3HtcZSi4npOzZSfZG0-90kuCOwHc80UXpd@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: Alper Yegin <alper.yegin@yegin.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: julienl@qualcomm.com, mext@ietf.org
Subject: Re: [MEXT] mext-cga-01
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 06:41:06 -0000

Hello Alper,

This is an important point about how we authorize a MN to create a BCE
in the first place. I've hinted at a couple of ways of doing so during
the IETF meeting:

- only MN that is on-home-link can create initial BCE, and then it can
update from wherever. This would be applicable when we know the MN
(almost) always has attachment to home link, e.g., dual mode MN with
always on cellular.
- only MN that has CoA in some prefix block can create initial BCE,
and then it can update from wherever. This would be applicable when we
know the MN at some point booted-up in its provider network.

We can and should discuss this more.

--julien

On Sat, Feb 12, 2011 at 1:17 AM, Alper Yegin <alper.yegin@yegin.org> wrote:
> Hello Julien, and MEXT members,
>
>
>
>
>
> I can have a MN that simply generates a CGA-based HoA by knowing the prefix
> served by the HA implementing this I-D, and get its BU accepted.
>
> The HA has no way to know whether this MN is authorized to be served
> (irrespective of the choice of HoA) or not.
>
>
>
> So, although I see this I-D serves a purpose by ensuring HoA ownership, I
> don’t see how it achieves general “BU authorization”.
>
>
>
> Probably this solution’s applicability shall reflect that, or some
> complimentary technique needs to be identified in order to complete the
> picture.
>
>
>
> Alper
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
>
>