Re: [6tisch] [core] [CoMI] multiple operations in a single request

Andy Bierman <andy@yumaworks.com> Fri, 26 June 2015 22:51 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AF21B2A11 for <6tisch@ietfa.amsl.com>; Fri, 26 Jun 2015 15:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
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 szeD9xRWL0yq for <6tisch@ietfa.amsl.com>; Fri, 26 Jun 2015 15:51:09 -0700 (PDT)
Received: from mail-la0-f47.google.com (mail-la0-f47.google.com [209.85.215.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C8501B2A03 for <6tisch@ietf.org>; Fri, 26 Jun 2015 15:51:09 -0700 (PDT)
Received: by lagi2 with SMTP id i2so71622278lag.2 for <6tisch@ietf.org>; Fri, 26 Jun 2015 15:51:07 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=U69BvcgbNO1hlZtXSy89FC7m4EPSBi5JNFJJyN2hAP8=; b=OIzC3geILHkq9QsiVcvuEDvrO8L23lFUmPRSlB+7zHa8lxmodI1fQokbYUbcZQlT/p /Xp/WMgNU9dRQvoeIuEpTqSxwJKudKsFvRHi1s/LAKuAwe0Q4kfVI3gkNXvjwgn9dI7e 7TUr4S/D0aH+jsG9TGlh021qRaXoNHlFBqDD13EqekgH6zFAV7S9DHHG33V/3rkgOeE1 WLmbB7Z989NtcqUSk8Cco4Voz2b7aLw3A1AvQ/PiKogUF7VpBf7I8rNwT+DFHSbR9lsI fv9q3bjSkZL1M60EbDoMgSJmiFQOIyJsuDpkq8Hs/UcJEjRSJJzWdOnvXfCMge/Qrk+g R8+Q==
X-Gm-Message-State: ALoCoQnz49+CAl9kllervpGr1lrt6kAdwG7oyMk6nbfW0F0uVMVr/ELHExV0SODtEta8W2vCzUAt
MIME-Version: 1.0
X-Received: by 10.112.164.66 with SMTP id yo2mr3646339lbb.33.1435359067800; Fri, 26 Jun 2015 15:51:07 -0700 (PDT)
Received: by 10.112.200.102 with HTTP; Fri, 26 Jun 2015 15:51:07 -0700 (PDT)
In-Reply-To: <CADJ9OA-g5ijXJQz_uPiz2482yeD3wY9EZPkD+h1N47aa21ioDQ@mail.gmail.com>
References: <CADJ9OA-g5ijXJQz_uPiz2482yeD3wY9EZPkD+h1N47aa21ioDQ@mail.gmail.com>
Date: Fri, 26 Jun 2015 15:51:07 -0700
Message-ID: <CABCOCHTwXuVs+LLMbANrL+RMrODcGDyPxgZBTZqAnDROVSqzzw@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Content-Type: multipart/alternative; boundary="001a11c32d5c5c9eff0519739326"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/9Kw5mullJ2-1XPTF-hZWQgj3sWw>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, core <core@ietf.org>
Subject: Re: [6tisch] [core] [CoMI] multiple operations in a single request
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2015 22:51:12 -0000

On Fri, Jun 26, 2015 at 3:32 PM, Thomas Watteyne <watteyne@eecs.berkeley.edu
> wrote:

> In the 6TiSCH context, CoMI can be used to manage a TSCH schedule, which
> involves adding/removing cells (atomic layer 2 resources).
>
> Cells are represented in the 6top YANG model as a list called "CellList" (
> https://tools.ietf.org/html/draft-ietf-6tisch-6top-interface-03#section-4.1).
> The way CoMI is written now (draft-vanderstok-core-comi-06), one CoMI
> request is needed for each operation. That is, if I want to schedule 10
> cells between nodes A and B, I will need 10 PUT requests to node A, and 10
> to node B. If these are confirmable CoAP packets, that's a lot of packets.
> These will be short requests, but will eat up an enormous amount of
> bandwidth.
>
> I'd like to be able to issue a single request to node A and a single
> request to node B to carry out all of these operations, by aggregating
> multiple "operations" in a single CoMI request (a single/small number of
> CoAP packets).
>
> What does CoMI offer me today to do this? Should we write the YANG model
> in some particular way? What is envisioned in a future revision of CoMI to
> answer this need.
>
>
I think the YANG Patch media type could be used with CoMI.
This allows multiple edits on different target resources.


You could also do a plain PATCH on the datastore root, and provide
the subtrees you want to change.




> Thanks,
> Thomas
>


Andy


>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>
>