Re: [6tisch] Comment to draft-wang-6tisch-6top-coapie-01.txt

Thomas Watteyne <watteyne@eecs.berkeley.edu> Fri, 25 September 2015 10:32 UTC

Return-Path: <twatteyne@gmail.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 A2A2D1A8A3C for <6tisch@ietfa.amsl.com>; Fri, 25 Sep 2015 03:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.277
X-Spam-Level:
X-Spam-Status: No, score=-3.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, 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 K1MKnWsZIIHv for <6tisch@ietfa.amsl.com>; Fri, 25 Sep 2015 03:32:21 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (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 2FA741A8A29 for <6tisch@ietf.org>; Fri, 25 Sep 2015 03:32:21 -0700 (PDT)
Received: by wicge5 with SMTP id ge5so14509423wic.0 for <6tisch@ietf.org>; Fri, 25 Sep 2015 03:32:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=jBsPbXgh7JrWznaa9adoD1k9A8sW/dQHg9GZtqstUDM=; b=hXHRN8nZfcRVWl99jE4agxA3oPgLKzys19REbnwrJMog2Yg5hiL47vwfcrQYlRCGnW agHzzGw/Qs8prb2ACb5tPx1lSbhhmhwgUzbfnx5S8gqKEYrO0EWw3Opo9xir3Sd0K2AA jlAQr55OdopuLKtcOTAC/6H1vuBanJhnEVz/6JqphLHGHVlPSEsiSuUFKWYLmf0MsWXz 3UySRNX94dG+oraQq8WcRVk4iOfABUKVbKBN4vvt4Cf8P+vCaCT2BqAwC581YhEMaqyP upOUmsHe9gRCASSlymmeQutxLf9G2LSrMdUYlSfgaDwyl+gaNC2l7VncgZXW0hoDxgQL KEbA==
X-Received: by 10.194.121.202 with SMTP id lm10mr5144183wjb.98.1443177139739; Fri, 25 Sep 2015 03:32:19 -0700 (PDT)
MIME-Version: 1.0
Sender: twatteyne@gmail.com
Received: by 10.28.25.199 with HTTP; Fri, 25 Sep 2015 03:31:59 -0700 (PDT)
In-Reply-To: <50838770.1280677.1437661723389.JavaMail.yahoo@mail.yahoo.com>
References: <21934.16929.897976.905775@fireball.acr.fi> <50838770.1280677.1437661723389.JavaMail.yahoo@mail.yahoo.com>
From: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Date: Fri, 25 Sep 2015 12:31:59 +0200
X-Google-Sender-Auth: 0VCSNq2O0IeewfamC2E0fDszgAI
Message-ID: <CADJ9OA-n9jtP1P75zhP0TyCPiHOoFb0z9EKbM0tHYaHKaAHjnA@mail.gmail.com>
To: Qin Wang <qinwang6top@yahoo.com>
Content-Type: multipart/alternative; boundary="089e0118451cc3246305208fdc80"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/LVDRedqa9yd4CD7FOPV8ILoazHA>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, Tero Kivinen <kivinen@iki.fi>
Subject: Re: [6tisch] Comment to draft-wang-6tisch-6top-coapie-01.txt
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, 25 Sep 2015 10:32:24 -0000

We need to discuss this point urgently, and do the work to ask the IEEE for
carve out some IE space for IETF/6TISCH if applicable.

On Thu, Jul 23, 2015 at 4:28 PM, Qin Wang <qinwang6top@yahoo.com> wrote:

> Hi Pat,
>
> Since there are two approaches mentioned in the discussion, i.e. (1)
> containing 6top-to-6top message in a specific payload IE (coapie), (2)
> using the mechanism provided by IEEE802.15.9 to convey the 6top-to-6top
> message, I would like to do more evaluation. I couldn't find the
> IEEE802.15.9 spec on IEEE802 website. Can you tell me how to get it?
>
> Thanks
> Qin
>
>
>
> On Tuesday, July 21, 2015 8:59 PM, Tero Kivinen <kivinen@iki.fi> wrote:
>
>
> This draft plans to put the coap messages directly on the payload IEs
> in the 802.15.4. The problem is that we only have 16 payload IE types
> in total for 802.15.4, so reserving one number for coap might be hard.
>
> On the other hand IEEE 802.15.9 needed to have solution to this same
> problem, i.e how to multiplex upper layer data packet over 802.15.4
> frames and how to fragment them so they can fit on the 802.15.4
> frames.
>
> The 802.15.9 is split in two layers, first one is the multiplexed data
> service, which takes 16-bit MultiplexId and the data packet to be sent
> to the other end, and it will fragment and deliver it to the other
> end. The MultiplexId is used to separate different protocols using
> this mechanism. One of those protocols is the key management protocols
> providing KMP for 802.15.4, which is the second part of the 802.15.9.
>
> Instead putting the coap messages in the payload IEs, it would
> possible to allocate one MultiplexId for coap messages, and then coap
> messages could be transmitted using multiplexing layer of 802.15.9.
> This would also take care of fragmentting the messages (with PHY using
> 127 octet PSDU, the maximum size of the data packet is around 24kB).
>
> The 802.15.9 recommended practice is already past the working group
> letter ballots, and is starting its sponsor ballot soon. It is
> expected to come out around the end of year. The draft will be
> available on the ieee document store after the sponsor ballot starts,
> i.e. very soon.
> --
> kivinen@iki.fi
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>
>
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>
>