Re: [Coma] (no subject)

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Fri, 08 June 2012 11:07 UTC

Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: coma@ietfa.amsl.com
Delivered-To: coma@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2546E21F85E5 for <coma@ietfa.amsl.com>; Fri, 8 Jun 2012 04:07:00 -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, HTML_MESSAGE=0.001, 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 EZWwUiiQiBri for <coma@ietfa.amsl.com>; Fri, 8 Jun 2012 04:06:57 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 0D98921F8582 for <coma@ietf.org>; Fri, 8 Jun 2012 04:06:54 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q58B6r8E000830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 8 Jun 2012 13:06:53 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q58B6rJI015855; Fri, 8 Jun 2012 13:06:53 +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:06:50 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD4566.CD9E6095"
Date: Fri, 8 Jun 2012 13:06:49 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6403DFB84E@DEMUEXC006.nsn-intra.net>
In-Reply-To: <21853_1339013084_4FCFB7DC_21853_10870_1_11027135CD0DCE41B9C193E3D7257738EE73@PEXCVZYM12.corporate.adroot.infra.ftgroup>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Coma] (no subject)
Thread-Index: Ac1EH5yYe7jjov2hS8OHDdlrqb9W9ABNz7dA
References: <21853_1339013084_4FCFB7DC_21853_10870_1_11027135CD0DCE41B9C193E3D7257738EE73@PEXCVZYM12.corporate.adroot.infra.ftgroup>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: <tayeb.benmeriem@orange.com>, <coma@ietf.org>
X-OriginalArrivalTime: 08 Jun 2012 11:06:50.0916 (UTC) FILETIME=[CE070640:01CD4566]
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: 17047
X-purgate-ID: 151667::1339153613-0000425E-54A2173F/0-0/0-0
Subject: Re: [Coma] (no subject)
X-BeenThere: coma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Management of Constrained Networks and Devices <coma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coma>, <mailto:coma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/coma>
List-Post: <mailto:coma@ietf.org>
List-Help: <mailto:coma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coma>, <mailto:coma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 11:07:00 -0000

Dear Tayeb,

 

your contribution as an operator is very valuable.

 

I agree we should look at the business needs and requirements. I would
appreciate it if you could provide some text on this.

Let's see how the document evolves and whether we can plan a gap
analysis already for the first release.

 

Cheers, 
Mehmet 

 

From: coma-bounces@ietf.org [mailto:coma-bounces@ietf.org] On Behalf Of
ext tayeb.benmeriem@orange.com
Sent: Wednesday, June 06, 2012 10:05 PM
To: coma@ietf.org
Subject: [Coma] (no subject)

 

Dear all,

 

It's an excellent idea to investigate this domain. From my perspective,
the first requirements related to the management aspect of such devices
in their particular environment are auto-configuration which is
addressed by design. When it comes to standardization for sure there is
some work to do accordingly.

 

Within operator's environment, could be Fixed or Mobile networks, the
Home Gateway and its attached devices, BBF protocol TR-69 is adopted and
used for managing (configuration) of HomeNodeB and HomeeNodeBs. Netconf
and its associated modeling language Yang have reached a maturity and
are implemented in vendors' solutions. Some extensions are considered in
order to address management aspects beyond simple configuration. 

 

The requirements and associated solutions should be business driven, and
then we address the technical solutions. That means, we should look at
the vertical market needs (Health, Digital Home, ...) in terms of
expectation of SLAs. Then the question is how to translate these SLAs
into SLOs, metrics and how to track, measure, collect and report them
(the needed management models and tools) in order to meet the SLAs.

 

The question related to the management is 3-fold:

- Which protocol: should we adapt the existing ones (TR-69, Netconf, )
to this constrained devices and network, or should designnew ones as
IETF did for routing protocols.

- Which interface:  We should not re-invente the wheel

- Which Data model:  We should not re-invente the wheel. 

 

So, this first draft should contain at least the following sections

-    Problem statement

-    Business needs and requirements

-    Technical requirements

-    Gap analysis: missing pieces to be covered by IETF and other SDOs

-    New topics to be investigated

 

 

Regards

 

Tayeb

 

 

________________________________________________________________________
_________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete
altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for
messages that have been modified, changed or falsified.
Thank you.