Re: [OPSAWG] Coman Drafts v02

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Sun, 10 August 2014 16:47 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 46A4B1A07A7 for <opsawg@ietfa.amsl.com>; Sun, 10 Aug 2014 09:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.168
X-Spam-Level:
X-Spam-Status: No, score=-15.168 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.668, 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 3vMF0QPFMHJU for <opsawg@ietfa.amsl.com>; Sun, 10 Aug 2014 09:47:32 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494541A07A2 for <opsawg@ietf.org>; Sun, 10 Aug 2014 09:47:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12465; q=dns/txt; s=iport; t=1407689252; x=1408898852; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=zsqHqxFVprZl05vubbDAfLsnrs3wgdjSFLEW/2p+onk=; b=ZVU6W5jaHktKyTzjBuJEhbZ2T0pM05R1gN6Gy7kCOEHeJr/0pEpDO4Ke xjKlvSt71VAUOFcZ3VeExK2FDaJbi9+XSYd8FjbqCv+AHsesvXzKl2Miz TkXexzCPhMRqJ4pgp25iDZXsur9YFfRmsTou4y/U7ECwnbILsXGxdiEFz E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FANah51OtJV2d/2dsb2JhbABagkdGUlfLDIFZAQmGdVMBgQcWd4QDAQEBBAEBAWsLEAIBCBEDAQIoBycLFAkIAgQOBQmIOQ3BHxeOewEBPg0EBgEGgjJTJIEdBYYPhFCEJ4IThCWBboUDgVeTJINcbAGBDQ
X-IronPort-AV: E=Sophos;i="5.01,837,1400025600"; d="scan'208,217";a="346228294"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 10 Aug 2014 16:47:31 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s7AGlVDB014599 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 10 Aug 2014 16:47:31 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.109]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Sun, 10 Aug 2014 11:47:30 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Coman Drafts v02
Thread-Index: AQHPszQS4Abi5UfSxEGyzCCjcnfBlZvKDyWt
Date: Sun, 10 Aug 2014 16:47:30 +0000
Message-ID: <B8AF2D35-C529-42F2-AFAB-2FAEF9919ACA@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_B8AF2D35C52942F2AFAB2FAEF9919ACAciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/opsawg/RzE9T32FASJuBB4KonSDGbgnXYs
X-Mailman-Approved-At: Sun, 10 Aug 2014 11:11:30 -0700
Cc: "Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com>
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: Sun, 10 Aug 2014 16:47:34 -0000

Dear all:

About probstate/req.

This is a very complete and well written document, and I agree it is ripe for IESG.

Before submittung, though, I'd suggest to add text relevant to (radio) link and resources management.

The draft only discusses reporting a topology. In a radio mesh, it is important to assess reachability and interference domains so as to allow spatial reuse of.

Because some resources are shared there is a need to claim some and a need for arbitration/push from the network management down to the frequencies and in the case of TSCH, time slots.

6TiSCH has also isolated the need for traffic engineering (eg for industrial control loops) and though the network component is a PCE, I'd think that the requirement is still a management one.

Finally I'm not sure there is enough text on operator IoT networks (multi tenant management) eg a citywide IoAt backbone operated by an ISP or the city itself, or a home network with share mesh resources but multiple sinks for various utilities.

Cheers,

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