Re: [mif] The formation of the design team

Ted Lemon <Ted.Lemon@nominum.com> Wed, 03 April 2013 23:48 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 59ED421F87B7 for <mif@ietfa.amsl.com>; Wed, 3 Apr 2013 16:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 0si+q2CxshuX for <mif@ietfa.amsl.com>; Wed, 3 Apr 2013 16:48:46 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id BCB7321F8771 for <mif@ietf.org>; Wed, 3 Apr 2013 16:48:46 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUVy/3syvTB9CRoRCEOx7pkReQApJBYdq@postini.com; Wed, 03 Apr 2013 16:48:46 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 676A5108A8B for <mif@ietf.org>; Wed, 3 Apr 2013 16:48:46 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (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 6092519005D; Wed, 3 Apr 2013 16:48:46 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 3 Apr 2013 16:48:46 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [mif] The formation of the design team
Thread-Index: AQHOMGNRrf9AO51xqECY6nyMtYZtkZjFHeIAgAAGvwCAAHuAAA==
Date: Wed, 03 Apr 2013 23:48:46 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775130765@mbx-01.win.nominum.com>
References: <CANF0JMAkCPYHotZ_j5YEDsB+CWPcjE2j1_sqO5iQ156-ebGbXQ@mail.gmail.com> <28783.1365004956@sandelman.ca> <515C5844.1020802@gmail.com>
In-Reply-To: <515C5844.1020802@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="us-ascii"
Content-ID: <21D6604F32434743BD2F1B5D8AF3C68F@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: MIF Mailing List <mif@ietf.org>
Subject: Re: [mif] The formation of the design team
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: Wed, 03 Apr 2013 23:48:47 -0000

On Apr 3, 2013, at 12:26 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> I think the real question is whether the architecture issue
> that underlies MIF can actually be solved within the limits
> of an IETF WG. But certainly the first stage is to produce a
> clear statement of what the issue is, and I would press the
> design team to bring that statement back to the WG *before*
> considering possible solutions.

Work that the IETF does has to be done in working groups, or as individual submissions, or by the IAB or the IESG.   Are you proposing that this work should be done in one of those other ways, rather than by the MIF working group, which was chartered to do this work and has already written a problem statement?   I don't think you were at the MIF meeting, so you may not have heard my presentation on this, but the slides are available, and I think the session was recorded.

Ultimately, we definitely need something for the rest of the IETF, not just MIF, to review, but we have to have something for the IETF *to* review; that is the point.

Michael did raise the question of whether this is really a design team, or the entire working group.   This is something that I discussed with the MIF chairs as well.   It's difficult to say; if everybody on the list winds up being an active participant, then maybe Michael is correct.   I personally doubt that's so.

However, it may be that you or Michael are concerned that process isn't being followed.   It could be argued that the meeting Hui announced is really an interim working group meeting and not a design team meeting.   If that's the case, then the two week notice requirement applies.

I don't have a strong preference for keeping this as a design team thing if people object.   I doubt the chairs do either.   It's certainly easier to schedule meetings if it's just a design team, and I think it's legitimate to claim that it's a design team.   But, frankly, you have more experience with this sort of thing than I do; if in your expert opinion this is an interim working group meeting and not a design team meeting, I think we ought to take that seriously.

But as for the question of where to do the work, I think at least for the moment, unless you have some serious proposal to make, MIF is in fact the right place.