Re: [mif] Call for volunteers about architecture design

Ted Lemon <Ted.Lemon@nominum.com> Tue, 19 March 2013 15:10 UTC

Return-Path: <Ted.Lemon@nominum.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 3287D21F8D1F for <mif@ietfa.amsl.com>; Tue, 19 Mar 2013 08:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.585
X-Spam-Level:
X-Spam-Status: No, score=-106.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 RQQHjJc+N+6K for <mif@ietfa.amsl.com>; Tue, 19 Mar 2013 08:10:12 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 8E6BE21F8D1E for <mif@ietf.org>; Tue, 19 Mar 2013 08:10:12 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUUh/0oixgEav3Lao5hDsR4NgVtTon1YY@postini.com; Tue, 19 Mar 2013 08:10:12 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 628201B8802 for <mif@ietf.org>; Tue, 19 Mar 2013 08:10:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 58331190043; Tue, 19 Mar 2013 08:10:10 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 08:10:10 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [mif] Call for volunteers about architecture design
Thread-Index: AQHOIng3nl1AuYp4zEafdnXCiS3KaJipRaGAgAAB9ACAAEkXAIAAqygAgAHGjICAATIvgIAAWVyAgAAKLoA=
Date: Tue, 19 Mar 2013 15:10:10 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775114E93@mbx-01.win.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>
In-Reply-To: <51487747.20506@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <3E2484DDFED52A40B8B5BE1070F3F4C2@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:10:13 -0000

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.