Re: [mif] Call for volunteers about architecture design

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 19 March 2013 15:38 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47B3821F8DA2 for <mif@ietfa.amsl.com>; Tue, 19 Mar 2013 08:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level:
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NrSor3sUTDg for <mif@ietfa.amsl.com>; Tue, 19 Mar 2013 08:38:02 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 51B1821F8D60 for <mif@ietf.org>; Tue, 19 Mar 2013 08:38:02 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2JFc1L3021783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 19 Mar 2013 16:38:01 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2JFc0XN027209; Tue, 19 Mar 2013 16:38:00 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2JFc0OR010267; Tue, 19 Mar 2013 16:38:00 +0100
Message-ID: <51488631.3000400@gmail.com>
Date: Tue, 19 Mar 2013 16:37:21 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CANF0JMBvHtg1Zhu-ZBnH-iYWuM29==T_-Yi2OK+vNa9F2SQmag@mail.gmail.com> <8C48B86A895913448548E6D15DA7553B7D7894@xmb-rcd-x09.cisco.com> <8D23D4052ABE7A4490E77B1A012B63077510F9D3@mbx-01.win.nominum.com> <51451E98.1020007@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775110D54@mbx-01.win.nominum.com> <51472B79.9030809@gmail.com> <22538_1363684433_51482C51_22538_54_1_81C77F07008CA24F9783A98CFD706F710B4285@PEXCVZYM12.corporate.adroot.infra.ftgroup> <51487747.20506@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775114E93@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775114E93@mbx-01.win.nominum.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "<mif@ietf.org>" <mif@ietf.org>
Subject: Re: [mif] Call for volunteers about architecture design
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 15:38:03 -0000

Le 19/03/2013 16:10, Ted Lemon a écrit :
> On Mar 19, 2013, at 10:33 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>>> Except the problem of access discovery and selection, I'm not
>>> sure there are multiple provisioning domains issues with
>>> sequential use of interfaces.
>>
>> I am not sure either.
>
> My take on this, for what it's worth, is that the work MIF is doing
> will be useful, but not central, to what you are trying to do.   MIF
> is focusing on what happens when all the interfaces are on at the
> same time, but we also want to enable the provision sufficient
> functionality that you can set up a connection manager that makes
> choices about which interfaces to keep alive when.
>
> I am not _convinced_ that we need to do a lot of work in that
> space—we may be able to leverage work that IEEE has already done, for
> example, in which case our job would be filling in the gaps that IEEE
> has not already addressed, or getting IEEE to do it, whichever makes
> the most sense.
>
> But the point is that I think you should probably be interested in
> what MIF is doing, but I suspect that the work MIF is doing is not
> crucial to the work you are doing.

I agree.  I am interested in what MIF is doing.

Alex

>
>
>