Re: [Coma] Possible topics?
"Ersue, Mehmet (NSN - DE/Munich)" <email@example.com> Fri, 08 June 2012 11:27 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C990521F86D0 for <firstname.lastname@example.org>; Fri, 8 Jun 2012 04:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 ([184.108.40.206]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3kvm18Mb2XMl for <email@example.com>; Fri, 8 Jun 2012 04:27:13 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [220.127.116.11]) by ietfa.amsl.com (Postfix) with ESMTP id 1B1F921F8786 for <firstname.lastname@example.org>; Fri, 8 Jun 2012 04:27:12 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (18.104.22.16860308/8.12.11) with ESMTP id q58BRA3Y015060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 8 Jun 2012 13:27:10 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (22.214.171.12460308/8.12.11) with ESMTP id q58BRA2h032027; Fri, 8 Jun 2012 13:27:10 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 8 Jun 2012 13:27:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 8 Jun 2012 13:27:07 +0200
Thread-Topic: [Coma] Possible topics?
From: "Ersue, Mehmet (NSN - DE/Munich)" <email@example.com>
To: "ext Ulrich Herberg" <firstname.lastname@example.org>, <email@example.com>
X-OriginalArrivalTime: 08 Jun 2012 11:27:10.0158 (UTC) FILETIME=[A4C096E0:01CD4569]
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
Subject: Re: [Coma] Possible topics?
List-Id: Management of Constrained Networks and Devices <coma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coma>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coma>, <mailto:email@example.com?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 11:27:14 -0000
Hi Ulrich, > I just discovered this mailing list. Some aspects I have in mind about > the topic of managing constrained devices and networks: > > - Do we actually manage single devices or whole networks (or groups of > devices)? At least in MANETs, it may be of equal interest to monitor > (and manage) the performance of a whole network, rather than just a > single router. Our aim is to look also at constrained networks and groups of devices. > - Should we support a distributed approach or a enforce a centralized > NMS? (or support both modes of operation?) Based on the size and type of the network both approaches could make sense. > - Which transport protocols do we want to use? TCP/UDP or something like COAP? As Benoit stated we are talking on requirements and not on solutions; especially we will not propose to use a specific protocol or solution. > - Do we need efficient, reliable multicast (like NORM, but > lightweight) to distribute control traffic more efficiently? > - Can we provide sufficient levels of security without putting too > much burden on constrained devices? Which authentication modes do we > need? > - Should there be a proxy functionality like RMON (or something like > the currently developed REPORT-MIB in MANET), in order to record > performance related values locally and then send to a NMS later? > - Will there be a mapping to existing management protocols like SNMP > for border gateways? > - Is there any assumption for this work about the reliability of the > channel, the kind of the link layer (e.g., wireless/wired), mobility > etc? Or is the only assumption that the devices are "constrained" (in > terms of memory? CPU? network connection?) Good questions. It would be helpful if you could start a discussion by stating why you think these should be requirements on constrained networks. > Best > Ulrich Cheers, Mehmet > > > [Coma] Subject: New Non-WG Mailing List: coma -- Management of > Constrained Networks and Devices > > From: IETF Secretariat <ietf-secretariat at ietf.org> > To: IETF Announcement List <ietf-announce at ietf.org> > Cc: bclaise at cisco.com, coma at ietf.org > Date: Wed, 16 May 2012 10:39:36 -0700 > List-id: Management of Constrained Networks and Devices <coma.ietf.org> > > A new IETF non-working group email list has been created. > > List address: coma at ietf.org > Archive: http://www.ietf.org/mail-archive/web/coma/ > To subscribe: https://www.ietf.org/mailman/listinfo/coma > > Purpose: This list is for the discussion related to the management of > constrained networks and devices. The IETF so far has not developed > specific technologies for the management of constrained networks. > There is a need to > understand the requirements for the management of such a constrained > network and its devices. > > For additional information, please contact the list administrators. > _______________________________________________ > Coma mailing list > Coma@ietf.org > https://www.ietf.org/mailman/listinfo/coma