IETF Logo Mail Archive

Re: [coman] are we there yet?

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Wed, 13 March 2013 16:49 UTC

Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: coman@ietfa.amsl.com
Delivered-To: coman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5D121F845D for <coman@ietfa.amsl.com>; Wed, 13 Mar 2013 09:49:54 -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 tf6Vg6XeJtSI for <coman@ietfa.amsl.com>; Wed, 13 Mar 2013 09:49:53 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id EB47721F8DF1 for <coman@ietf.org>; Wed, 13 Mar 2013 09:49:29 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r2DGnRUQ009396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 13 Mar 2013 17:49:28 +0100
Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r2DGnRpc015135 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Mar 2013 17:49:27 +0100
Received: from DEMUHTC007.nsn-intra.net (10.159.42.38) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 13 Mar 2013 17:49:27 +0100
Received: from DEMUMBX005.nsn-intra.net ([169.254.5.216]) by DEMUHTC007.nsn-intra.net ([10.159.42.38]) with mapi id 14.02.0328.009; Wed, 13 Mar 2013 17:49:27 +0100
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: ext Ulrich Herberg <ulrich@herberg.name>, Zach Shelby <zach@sensinode.com>
Thread-Topic: [coman] are we there yet?
Thread-Index: AQHOIAdRQq1aaE2MQ02p71ZdhReX95ij0zFA
Date: Wed, 13 Mar 2013 16:49:26 +0000
Message-ID: <E4DE949E6CE3E34993A2FF8AE79131F806E655@DEMUMBX005.nsn-intra.net>
References: <22677.1363008722@sandelman.ca> <E4DE949E6CE3E34993A2FF8AE79131F80655D7@DEMUMBX005.nsn-intra.net> <CAK=bVC8CuqxsPo+5ihHeJrfY6S5=jhpQz5oDf0L_qybg5r_B5Q@mail.gmail.com> <CANF4ybt0MmnQXR0ZQKSPJ8AjW-wF-hduyysmzVq9ebj2jsfsQw@mail.gmail.com> <34966E97BE8AD64EAE9D3D6E4DEE36F21EDDDD20@szxeml525-mbx.china.huawei.com> <20130312014021.GA64284@elstar.local> <34966E97BE8AD64EAE9D3D6E4DEE36F21EDDDF18@szxeml525-mbx.china.huawei.com> <BBD6E278-49FC-42FB-A342-E40086B6B364@sensinode.com> <8254.1363105006@sandelman.ca> <DA0F7870-F728-4E4C-8A70-F681FE2CF408@sensinode.com> <2D81839E-121C-49E6-ABC0-EE37558638D2@nsn.com> <36CE85CA-0ED6-48E7-8784-A107E5370795@sensinode.com> <CAK=bVC_SdX486G7+7ci9T1nrO+2c40qqtp_8qpivysOeH0NrXQ@mail.gmail.com>
In-Reply-To: <CAK=bVC_SdX486G7+7ci9T1nrO+2c40qqtp_8qpivysOeH0NrXQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1681
X-purgate-ID: 151667::1363193368-000050C9-49D6CA20/0-0/0-0
Cc: "coman@ietf.org" <coman@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: [coman] are we there yet?
X-BeenThere: coman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Management of Constrained Networks and Devices <coman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coman>, <mailto:coman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/coman>
List-Post: <mailto:coman@ietf.org>
List-Help: <mailto:coman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coman>, <mailto:coman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 16:49:54 -0000

As discussed in the last meeting, the precondition for a successful BOF is a gap analysis, which highlights potential new work and justifies at the end a new WG.

So, we need to go through this step first. And I see the discussion on and the review of the requirements as part of the gap analysis.

The question now is who is going to do such a gap analysis. Is it me alone or are other people going to write any drafts, which underline missing parts?

Cheers, 
Mehmet 


> -----Original Message-----
> From: ext Ulrich Herberg [mailto:ulrich@herberg.name]
> Sent: Wednesday, March 13, 2013 12:25 PM
> To: Zach Shelby
> Cc: Ersue, Mehmet (NSN - DE/Munich); coman@ietf.org; Michael Richardson
> Subject: Re: [coman] are we there yet?
> 
> Zach,
> 
> On Wed, Mar 13, 2013 at 11:37 AM, Zach Shelby <zach@sensinode.com> wrote:
> > [...]
> > We just need to figure out what the gaps are.
> 
> I agree with that. It would be the first step. Whether we need a new
> protocol, or can use and extend existing protocols would follow from
> the gap analysis.
> 
> I have no opinion yet whether OMA M2M would be fulfilling the
> requirements that we are defining, so I am looking forward to see your
> gap analysis for that protocol.
> 
> On Thursday, I think we should also talk about whether to request a
> BOF for Berlin or not. COMAN has been around for a few IETFs now and I
> see a good approach, but like Benoit said, we need to be sure there
> are enough people interested (and more importantly, willing to do the
> work). Also, we'd need a clear charter in case we want to apply for a
> BOF.
> 
> Thanks
> Ulrich

v2.46.0 | Report a Bug | By Email | System Status