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

Qin Wang <qinwang6top@yahoo.com> Tue, 21 July 2015 14:56 UTC

Return-Path: <qinwang6top@yahoo.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 2D45E1B2EC7 for <6tisch@ietfa.amsl.com>; Tue, 21 Jul 2015 07:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.709
X-Spam-Level:
X-Spam-Status: No, score=-4.709 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, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 oFFC9EIukg6S for <6tisch@ietfa.amsl.com>; Tue, 21 Jul 2015 07:56:26 -0700 (PDT)
Received: from nm31.bullet.mail.bf1.yahoo.com (nm31.bullet.mail.bf1.yahoo.com [72.30.239.198]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45CB61A8973 for <6tisch@ietf.org>; Tue, 21 Jul 2015 07:56:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1437490574; bh=bqVgkFYlwlUXaH7WohpGOz9nxZ6tKxDi9rKHtZgq76Q=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=JUhKyIK1doEFJOc92AByp1rPYHMjoOnmX52Ih2SGdtSwG1SF6o2+piBuJ6jhKkbQyYToaqJTSEwvWBLOJC3QE5kXq5oj3L5pKU4mf9ASHQYVFrkdKSRoPB7+mXeW2CJtxI6MCisQ6CGpcY4XbZovF9NSjDe4ZoQsF3ginAaXnBWa3G3LPF6rf7UAXhakvdH6ugCFHK00vJshV+J5ub6NWzmyqDP9FjUQUP8ewnBzG9URGR0FwaFQvA5KnPLWdxmegXnjIOhR4ZxN9YpECjdky/zq3OV4Od8FEBnU9WkoUZe6B8pP7xC7og7hFhzK/P97cEVYPHmz3MHQ0oFoR/UFHA==
Received: from [98.139.170.180] by nm31.bullet.mail.bf1.yahoo.com with NNFMP; 21 Jul 2015 14:56:14 -0000
Received: from [98.139.215.229] by tm23.bullet.mail.bf1.yahoo.com with NNFMP; 21 Jul 2015 14:56:14 -0000
Received: from [127.0.0.1] by omp1069.mail.bf1.yahoo.com with NNFMP; 21 Jul 2015 14:56:14 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 338300.41211.bm@omp1069.mail.bf1.yahoo.com
X-YMail-OSG: WpCdA7kVM1lBA1aok5POAr383jyTHvEpsj4hobM9ktX1sQfRiXxPGDmIcezC48c M2Lz0tW6.SuociBTbe3TB_lPhsZT_hT.hVVg1ClbSbTnzWDNGi6gAP1nBs23MlRomYblmNllGmi6 dQyXXcVBGgYRkCx2WPqzTHgiRql5QbqI2m1_ryGuEyVlsfMYlqQL788_N.tVMivKAkA5biAFMbM5 PpEnf6nIRD_KGMbwHmp2RNQaVoZG0S4DJqrDSnbVSKBIjmlH_e9RD2TEtsaKyIRfco0jHtgi8pHU C8efq9gQeG.2VAlsVLE9Vv5YwHYnnwHuZRFpO0SfD.qss83Q0ep5DCbYMAiwDgZwcASbXE8sh0Nk 3OEDjoSz0fEzDDNh2ppFcspIXQUguSTHlOwMhytx9mpQ0xW3eYR4uDeEQDCXjUFRKmQyMBrrSlp8 yHdDfFmioAW5d1De4HvWWiqx6YM1tkyO25IKEhTBQHjO9j47Is9A34JoO
Received: by 66.196.80.144; Tue, 21 Jul 2015 14:56:13 +0000
Date: Tue, 21 Jul 2015 14:54:32 +0000
From: Qin Wang <qinwang6top@yahoo.com>
To: Tero Kivinen <kivinen@iki.fi>, "6tisch@ietf.org" <6tisch@ietf.org>
Message-ID: <11134325.1860961.1437490472600.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <21934.16929.897976.905775@fireball.acr.fi>
References: <21934.16929.897976.905775@fireball.acr.fi>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_1860960_225557660.1437490472595"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/BzxqZFF5ngLmEMVNb8-vkdZ7pD4>
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
Reply-To: Qin Wang <qinwang6top@yahoo.com>
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: Tue, 21 Jul 2015 14:56:28 -0000

Hi Tero,
Thank you for your comments.
Before going to 802.15.9, I would like to discuss more about the coapie approach. In the 802.15.4e, the range (0x2-0x9) of group ID for payload IE is unmanaged. I thought IEEE802.15.4 WG had discussed how to use those Group ID, and also taken the requirement from 6tisch into consideration, and IEEE802.15.4 WG will assign a group ID to 6tisch. Am I wrong?
ThanksQin   


     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