Re: [OPSAWG] Coman Drafts v02

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Sat, 09 August 2014 12:42 UTC

Return-Path: <pthubert@cisco.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 E4B351A03A1 for <opsawg@ietfa.amsl.com>; Sat, 9 Aug 2014 05:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 lF1uDBjDiqZm for <opsawg@ietfa.amsl.com>; Sat, 9 Aug 2014 05:42:22 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC4101A0394 for <opsawg@ietf.org>; Sat, 9 Aug 2014 05:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12375; q=dns/txt; s=iport; t=1407588142; x=1408797742; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=f+gNV5t0wSTuHvCu2c6q120GgQaQ8sCyCB5Rump8LGg=; b=DtLD/WolbSqI8ma/l1YuOzQnsotr05DbEiTp2T6MWLRI4MzDfmYT46/T uJYqrxoWOE92aWUZ+9wfFk9Zac4CKXXnh6Ge47Gg6JQCMv+ve8bfizT8d hKzprP4fLPhSjBV86AnbBtXLnC/EzwDTDrOZXcV4tgyGb57uI6jAJOKtu c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAPsV5lOtJV2Y/2dsb2JhbABZgkdGUk3LOIFZAQmGdVMBgQsWd4QDAQEBBAEBAWsLEAIBCBEDAQIoBycLFAkIAgQOBQmIOQ3FFReOewEBPg0EBgEGgymBHQWGD4RQhCeCE4QlhnGBV5Mkg1xsAYEN
X-IronPort-AV: E=Sophos;i="5.01,832,1400025600"; d="scan'208,217";a="346361442"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 09 Aug 2014 12:42:20 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s79CgKmC030850 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 9 Aug 2014 12:42:20 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.109]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Sat, 9 Aug 2014 07:42:19 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com>
Thread-Topic: [OPSAWG] Coman Drafts v02
Thread-Index: AQHPszQS4Abi5UfSxEGyzCCjcnfBlZvIOE5W
Date: Sat, 09 Aug 2014 12:42:19 +0000
Message-ID: <FDF761D6-A96B-4192-9FF6-51224F9123FA@cisco.com>
References: <D00A6075.8C6B%rsudhaak@cisco.com>
In-Reply-To: <D00A6075.8C6B%rsudhaak@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_FDF761D6A96B41929FF651224F9123FAciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/opsawg/0esbRxQc2xeZoRTMD38C_zZKqBU
X-Mailman-Approved-At: Sat, 09 Aug 2014 05:43:14 -0700
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "P.Zand@utwente.nl" <P.Zand@utwente.nl>
Subject: Re: [OPSAWG] Coman Drafts v02
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: Sat, 09 Aug 2014 12:42:25 -0000

Dear all:

On coman use cases 02

Really excellent work! Fits my own understanding in every scenario I am familiar with.

Issues:

The security section is absent yet security concerns are correctly discussed throughout. As it goes, security concerns for management flows are correctly expressed but often apply to many other use cases where the question is not discussed. Maybe a table in the security section could summarize case by case who manages the network and the devices, and what kind of security is in place.

There is a great discussion on light bulbs commissioning in the building section. I was actually missing that same discussion in the factory automation section.

Who manages the network during the factory setup/commissioning? Specific threats are associated to the transition to operational/trusted, and the process of handover exists in multiple scenarios.

Thanks again for this great document. Really useful, and I support its publication.

Pascal

Le 8 août 2014 à 20:10, "Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com<mailto:rsudhaak@cisco.com>> a écrit :

Dear ML users,
I read both the documents your mentioned below. Both are well written and address their scope quite well.
Only a few minor typos here and there.

On a general note, both these documents do not address the actual management protocol. It seems to me that these documents will typically be referenced by some other drafts (like our draft-ietf-6tisch-coap) that specify the protocol.


-raghuram

From: Thomas Watteyne <watteyne@eecs.berkeley.edu<mailto:watteyne@eecs.berkeley.edu>>
Date: Tuesday, August 5, 2014 at 11:15 PM
To: raghuram sudhaakar <rsudhaak@cisco.com<mailto:rsudhaak@cisco.com>>
Subject: Fwd: [6lo] Fwd: [OPSAWG] Coman Drafts v02

Raghuram,
These drafts, which introduce the use cases and problem statement for constrained management, are very related to the CoAP draft you co-authored. I believe it would be very useful if you could review them and submit your review to the OPSAWG ML, as detailed below. Would that be possible?
Thomas

---------- Forwarded message ----------
From: Thomas Watteyne <watteyne@eecs.berkeley.edu<mailto:watteyne@eecs.berkeley.edu>>
Date: Sat, Jul 26, 2014 at 10:32 PM
Subject: Fwd: [6lo] Fwd: [OPSAWG] Coman Drafts v02
To: "6tisch@ietf.org<mailto:6tisch@ietf.org>" <6tisch@ietf.org<mailto:6tisch@ietf.org>>


All,

The OPSWAG chairs have kindly agreed to extend the WGLC period for the following drafts [1] to August 11:

http://tools.ietf.org/html/draft-ietf-opsawg-coman-use-cases-02
http://tools.ietf.org/html/draft-ietf-opsawg-coman-probstate-reqs-01

Pascal and myself believe those two drafts to be important for the ongoing work on managing a 6TiSCH network, and directly in line with e.g. draft-ietf-6tisch-coap. We therefore ask authors of draft-ietf-6tisch-coap, draft-ietf-6tisch-6top-interface, and any other 6TiSCH WG member to send reviews of this document to OPSAWG ML [2].

Thomas

[1] http://www.ietf.org/mail-archive/web/6tisch/current/msg02465.html
[2] https://www.ietf.org/mailman/listinfo/opsawg


---------- Forwarded message ----------
From: Warren Kumari <warren@kumari.net<mailto:warren@kumari.net>>
Date: Fri, Jul 25, 2014 at 3:03 PM
Subject: Re: [coman] FW: [OPSAWG] Coman Drafts v02
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com<mailto:mehmet.ersue@nsn.com>>
Cc: "coman@ietf.org<mailto:coman@ietf.org>" <coman@ietf.org<mailto:coman@ietf.org>>, "opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>"
<opsawg-chairs@tools.ietf.org<mailto:opsawg-chairs@tools.ietf.org>>


Hi all.

With apologies to the authors...

The chairs of 6LoWPAN and 6TSCH have asked if we can delay the end of
this WGLC so that their communities can review and comment on these 2
documents.

As we have not received very much feedback, this seems relevant to
their WGs, and they asked nicely, we have decided to extend the
deadline to August 11th.

Now, many folk will be traveling back to their homes over the next few
days - this probably means a few, or many hours on an airplane. May I
suggest copying these documents on your computer or reading device of
choice and reviewing the documents on the way home?

Thanks,
W

_______________________________________________
6lo mailing list
6lo@ietf.org<mailto:6lo@ietf.org>
https://www.ietf.org/mailman/listinfo/6lo