Re: [DMM] regarding the re-chartering..

Brian Haberman <brian@innovationslab.net> Wed, 03 September 2014 17:20 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91E131A0395 for <dmm@ietfa.amsl.com>; Wed, 3 Sep 2014 10:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4aWN4Wm0I1ZK for <dmm@ietfa.amsl.com>; Wed, 3 Sep 2014 10:20:01 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 299FB1A038F for <dmm@ietf.org>; Wed, 3 Sep 2014 10:19:47 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id F03EF88127; Wed, 3 Sep 2014 10:19:46 -0700 (PDT)
Received: from clemson.local (c-76-21-129-88.hsd1.md.comcast.net [76.21.129.88]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 763CF71B0001; Wed, 3 Sep 2014 10:19:46 -0700 (PDT)
Message-ID: <54074DAB.9020801@innovationslab.net>
Date: Wed, 03 Sep 2014 13:19:39 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya2012@gmail.com>
References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> <53EB4F10.1040502@gmail.com> <A02C6954-3EC9-443F-ACC3-4A635EC79EFC@yegin.org> <53F35B44.1090808@gmail.com> <1E1DFA1F-8BC5-474B-A792-A8681A99D094@yegin.org> <72DAF3D2-05D9-4A1E-9185-7265AA915075@gmail.com> <CAC8QAcegx1QPATsrPS-v-dkoLbaSTNqE3M+BbrYJPHrCFKMyXA@mail.gmail.com> <5404BC3D.1000406@gmail.com> <CAC8QAccqjXHogC44iOBO5bDccFBRixgcgrQU=hst8ZYGM3Y5xA@mail.gmail.com> <5406A20F.60604@gmail.com> <CAC8QAccBSXSsydagekNHnBbaYvmtTdm=xv5aEE64c+=9X2Fp9w@mail.gmail.com> <5407422F.2010700@innovationslab.net> <CAC8QAcdvdY1Kbys4a=dw9aQ4cUs8cnRcnfaujxm1Fjn6_EAvkg@mail.gmail.com>
In-Reply-To: <CAC8QAcdvdY1Kbys4a=dw9aQ4cUs8cnRcnfaujxm1Fjn6_EAvkg@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="LnMBqjNIDW5RoHvMfAf8hAEwX1PEw8wgR"
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/6J-0DixdLLfgpze2ZYRG9e6Die0
Cc: "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [DMM] regarding the re-chartering..
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 17:20:18 -0000


On 9/3/14 12:50 PM, Behcet Sarikaya wrote:
> Hi Brian,
> 
> On Wed, Sep 3, 2014 at 11:30 AM, Brian Haberman
> <brian@innovationslab.net> wrote:
>> Just for clarification...
>>
>> On 9/3/14 12:22 PM, Behcet Sarikaya wrote:
>>
>>>
>>> I am also concerned on the time DMM is taking on dressing up the
>>> charter text. I remind you on what Jari Arkko who is founding AD for
>>> DMM said in Toronto admin plenary:
>>> WGs should have  solution work from day 1.
>>
>> Not "should", but rather "could".  Not all WGs need to have
>> requirements, frameworks, architecture, etc. That is why this type of
>> discussion during charter development is important.
> 
> Here is the quote:
> WGs should have solution work from day 1
> 
> from page 22 of Jari's slides at:
> 
> http://www.ietf.org/proceedings/90/slides/slides-90-iesg-opsplenary-7.pdf

Yes, that is what the slide says.  The IESG discussed the contents of
this presentation and the overwhelming consensus (and what was
verbalized in the plenary) is that WGs should not be formed where the
*only* output is architecture, frameworks, and/or requirements
documents.  The charter should have protocol/solution work on the
charter from day one.  It does not mean that non-solution documents
should be skipped if they are needed or provide useful background.

The charter text that Jouni sent to the mailing has four (4) work items.
 By my read, three (3) of them are solutions to identified problem
areas.  So, I believe the charter is following the spirit of Jari's
plenary slides.

Your only complaint is about the first work item.  I have seen people
asking about clarifications on that work item, but you are the only one
who wants it removed.  I believe others are in favor of providing a
document of the high-level models being targeted for the solutions work.

At this point, the WG chairs need to determine if there is consensus for
the latest charter text.

Regards,
Brian