Re: [OPSAWG] Comments on draft-opsawg-ersue-coman-probstate-reqs
James Nguyen <james.huy.nguyen@gmail.com> Wed, 15 January 2014 21:47 UTC
Return-Path: <james.huy.nguyen@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5341AE167 for <opsawg@ietfa.amsl.com>; Wed, 15 Jan 2014 13:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 2_eMFffmBMLn for <opsawg@ietfa.amsl.com>; Wed, 15 Jan 2014 13:47:37 -0800 (PST)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBC71AE197 for <opsawg@ietf.org>; Wed, 15 Jan 2014 13:47:29 -0800 (PST)
Received: by mail-qc0-f174.google.com with SMTP id x13so1583223qcv.33 for <opsawg@ietf.org>; Wed, 15 Jan 2014 13:47:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kSOFgAZzEGxQ5HWH4LZFqndqdttmAwKOIPHzJ5nOxtI=; b=aSsB5z6OyFimkULgtK0TYk3bdp/uQb51ZAH9aG6xKIUBrALw4aHdcCu6x/EIYkCS3z 3SjSdKSOw6wR+EczVqV0/MGRPD6rJrS4iVqU5OI+SbrQ3Yg9Gzhc+rbQGSS5ZSYf3Iab Yhty99E8sq1MKIRtIWuS7Ggl/6+Y6n04lO4q3ju+JKAts4XF4qg85RK2sWph+WC2/OEu E6dzfYXwCKTt60rCPyjNsJmpzHxOSymXbKAiesPvddXsai3milY+Mxa56E6NbRNRFoZN rJ4C0alqzG3ybyRKI/7y86FzWONFTrf3OHfIETOy2AZLHABx4zFDQWDD9EQuRxIIKKZR pdTw==
MIME-Version: 1.0
X-Received: by 10.140.94.246 with SMTP id g109mr1819332qge.19.1389822437387; Wed, 15 Jan 2014 13:47:17 -0800 (PST)
Received: by 10.96.131.11 with HTTP; Wed, 15 Jan 2014 13:47:17 -0800 (PST)
In-Reply-To: <E4DE949E6CE3E34993A2FF8AE79131F8249B2D@DEMUMBX005.nsn-intra.net>
References: <CANF0JMCZzziqvjvTJ0WaJ8Wo3kSNHDhhurmcYmX4FpcqWfq2+g@mail.gmail.com> <E4DE949E6CE3E34993A2FF8AE79131F8249B2D@DEMUMBX005.nsn-intra.net>
Date: Wed, 15 Jan 2014 16:47:17 -0500
Message-ID: <CANF4ybvR47wHioN61meNiR6b-DgXue0EnDy2gmHSQ=P4sSgkhA@mail.gmail.com>
From: James Nguyen <james.huy.nguyen@gmail.com>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Content-Type: multipart/alternative; boundary="001a113a81d6aeb8a304f00940fb"
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Comments on draft-opsawg-ersue-coman-probstate-reqs
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 21:47:41 -0000
Hi, I really enjoy reading this draft. In general, in my opinion is very useful for managing constrained devices. I have a couple of questions/suggestions: (1) Req-ID 4.3.002 Title: Capacity Discovery I don't quite understand this req. Please be more specific. (2) Section 3.3 Configuration Management Session-oriented configuration protocol may be expensive for managing a large number of similar devices. In a case when common redundant configurations is issued, reliable multicast with negative acknowledgement (e.g. Negative ACKnowledgement (NACK)-Oriented Reliable Multicast (NORM)) would work best. I suggest to add a reliable transport requirement in this section. Moreover, a common data model would be needed. Stateless configuration update solution would also work well for constrained networks. (3) Section 3.8 Group-based provisioning As I mentioned in (2), a common data model would be required for common redundant configurations. I suggest to add this requirement here. Hope this helps. James On Mon, Jan 6, 2014 at 1:56 PM, Ersue, Mehmet (NSN - DE/Munich) < mehmet.ersue@nsn.com> wrote: > Hi Hui, > > > > thank you for your kind review. > > > > > 1. in section 3., a section of ‘IPv4/v6 address management’ could be > helpful, including the discussion of different types of ip addresses on > devices, link-local, global, private, etc.. > > Concerning IPv4/v6 addresses which requirements do you have in mind from > management pov.? > > > > > 2. in Appendix A, any relevant discussion in ‘oneM2M’? > > I would need your help for this as I’m not involved in oneM2M. Thanks. > > > > Cheers, > Mehmet > > > > *From:* OPSAWG [mailto:opsawg-bounces@ietf.org] *On Behalf Of *ext Hui > Deng > *Sent:* Monday, January 06, 2014 8:49 AM > *To:* opsawg@ietf.org > *Subject:* [OPSAWG] Comments on draft-opsawg-ersue-coman-probstate-reqs > > > > Hi Authors, > > > > This document is very useful for service providers and operators that are > managing their constrained devices. > > > > Two cents for authors to consider, > > 1. in section 3., a section of ‘IPv4/v6 address management’ could be > helpful, including the discussion of different types of ip addresses on > devices, link-local, global, private, etc.. > > 2. in Appendix A, any relevant discussion in ‘oneM2M’? > > > Regards, > > > > -Hui > > > > > 2014/1/4 Ersue, Mehmet (NSN - DE/Munich) <mehmet.ersue@nsn.com> > > Hi Dan, > > thank you for your review and comments. See below. > > Cheers, > Mehmet > > > -----Original Message----- > > From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of ext > Romascanu, Dan > > (Dan) > > Sent: Thursday, December 12, 2013 2:23 PM > > To: Warren Kumari; opsawg@ietf.org > > Subject: Re: [OPSAWG] Call for reviewers of draft-ersue-opsawg-coman-* > > > > Hi, > > > > I do not know if I really should be included in the reviewers count, as > I am a participant > > in the coman work since it started, and my name shows up on the list of > authors, > > although in all sincerity most of the credits go to Mehmet, who hold the > pen for most > > of the time, including this latest wound which split the original > document into two > > separate documents - one for use cases, the other for problem statement > and > > requirements. Anyway, FWIW I obviously believe this work is useful and I > support > > doing it in the OPSAWG. I have a few comments recorded below: > > > > draft-ersue-opsawg-coman-use-cases > > > > 1. I do not believe that we can get away with a zero-content security > considerations > > section. The described use cases mention the need to secure information > collected by > > constrained devices, some other (like security cameras) carry > information related to > > personal or public security that needs to be protected by robust > mechanisms. These > > kind of threats need to be mentioned IMO. > > You are right a dummy security considerations section is not sufficient. > Coman was not planning to address security exhaustively. Solace, now ACE, > has > been started where security for constrained devices will be discussed. > We discussed the security requirements in section 3.6 of the problem > statement draft. > > I agree, a discussion of the security threads should be provided in a > security considerations section. > > > draft-ersue-opsawg-coman-probstate-reqs > > > > 1. The draft uses the 'adjective' small device in association with > constrained device in a > > few place. I suggest to remove this. There is no automatic association > of a device > > being small implying that it is also constrained. Nor are all > constrained devices small in > > size. > > Agree. We should be more precise with the terminology. > > > 2. We have made an effort in the last few versions and especially in > this one to > > distinguish between the constrained devices and constrained networks, > but the clean-up > > on this issue is not complete. For example section 1.6 still has text > about constrained > > networks - this section and other in which constrained networks are > mentioned should > > be carefully examined to make sure that the focus of the document stays > with > > constrained devices, and that if constrained networks are mentioned at > all this is in the > > context of their relationship with the constrained devices. > > Why strictly devices? We also have requirements discussing the > organization of constrained networks from management pov. in section 3.1. > > > 3. I do not believe that we can get away with a zero-content security > considerations > > section here either. The document even says: > > > > If specific requirements for > > security will be identified, they will be described in future > > versions of this document. > > > > This is not accurate - section 3.6 already speaks about requirments for > security and > > access control, and section 1.6 mentions limitations that would prevent > the > > implementation of strong scryptographic algorythms. The text needs to be > reviewed > > and revised from this perspective. > > I think the "future" is now and the current text in the security > considerations section needs to be replaced. I would suggest to provide a > security considerations section by listing and discussing threads in the > problem statement draft and refer to it from the use cases draft. > Comments? > > > > > Regards, > > > > Dan > > > > > -----Original Message----- > > > From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Warren > Kumari > > > Sent: Wednesday, December 04, 2013 6:49 PM > > > To: opsawg@ietf.org > > > Subject: [OPSAWG] Call for reviewers of draft-ersue-opsawg-coman-* > > > > > > Hi all, > > > > > > Hopefully you all had a good Thanksgiving -- if you are in the US, > > > hopefully you had good turkey, stuffing / whatever. > > > If you are not US based, hopefully you enjoyed the decrease in email > > > volume while everyone recovered form eating too much. :-) > > > > > > One of the action items from Vancouver was for us to call for reviewers > > > for: > > > > http://datatracker.ietf.org/doc/draft-ersue-opsawg-coman-probstate-reqs/ > > > and > > > http://datatracker.ietf.org/doc/draft-ersue-opsawg-coman-use-cases/ > > > > > > So, can we get some volunteers please? According to our new guidelines > > > we require sufficient reviewers before adopting new work. > > > > > > The documents are (IMO) interesting and easy to read. Constrained > > > devices have some interesting requirements and limitations. > > > If you would like a quick reminder / refresher from the meeting, slides > > > are here: > http://tools.ietf.org/agenda/88/slides/slides-88-opsawg-11.pdf > > > > > > Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> indicated > > > that one of his Ph.D. students had read the draft a couple of weeks > ago. > > > So they just have to review the changes to the latest version. > > > > > > > > > W > > > -- > > > "I think it would be a good idea." > > > - Mahatma Ghandi, when asked what he thought of Western civilization > > > > > > > > > > > > _______________________________________________ > > > OPSAWG mailing list > > > OPSAWG@ietf.org > > > https://www.ietf.org/mailman/listinfo/opsawg > > _______________________________________________ > > OPSAWG mailing list > > OPSAWG@ietf.org > > https://www.ietf.org/mailman/listinfo/opsawg > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg > > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg > > -- James Nguyen Email: james.huy.nguyen@gmail.com
- [OPSAWG] Comments on draft-opsawg-ersue-coman-pro… Hui Deng
- Re: [OPSAWG] Comments on draft-opsawg-ersue-coman… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] Comments on draft-opsawg-ersue-coman… James Nguyen
- Re: [OPSAWG] Comments on draft-opsawg-ersue-coman… Juergen Schoenwaelder
- Re: [OPSAWG] Comments on draft-opsawg-ersue-coman… James Nguyen
- Re: [OPSAWG] Comments on draft-opsawg-ersue-coman… Juergen Schoenwaelder
- Re: [OPSAWG] Comments on draft-opsawg-ersue-coman… James Nguyen
- Re: [OPSAWG] Comments on draft-opsawg-ersue-coman… Andy Bierman
- Re: [OPSAWG] Comments on draft-opsawg-ersue-coman… James Nguyen