Re: [Lwip] Discussion about IoT Device Classes

Zhen Cao <zhencao.ietf@gmail.com> Thu, 26 January 2017 06:32 UTC

Return-Path: <zhencao.ietf@gmail.com>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60FBD129448 for <lwip@ietfa.amsl.com>; Wed, 25 Jan 2017 22:32:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9HP8fd4zwWKp for <lwip@ietfa.amsl.com>; Wed, 25 Jan 2017 22:32:13 -0800 (PST)
Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::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 702B312948D for <lwip@ietf.org>; Wed, 25 Jan 2017 22:32:13 -0800 (PST)
Received: by mail-ua0-x22c.google.com with SMTP id y9so177000484uae.2 for <lwip@ietf.org>; Wed, 25 Jan 2017 22:32:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=sUbb8H7pbVQxtEixdvFVGzIDX+1yMrnu8PQSihHJ4gQ=; b=oK3kKIi436lYXfD6L3+dLt1ztGLS/DKaeRKGs5dTc+T8dPoyY7on28HgEsZgEuK8wp 5+uCLOtrRIhXILUp43YoOavrRXaGeB0T920hdhug2+TMPsQI1cv+G8otyAwNxJyHxEe8 Hpim3IHWVmqQasZhbrY9DwxqBBPioI1nDv6Sn4oKG9XA3b4gS5S9iqtm12ApZlvUlP9X Rs7eodkuheMJwsYts38ReD8EhRaQrWuKhCgtVAJoK3PjsmE0PLLBsYau674GnH0PCMoR 1tVL/5dk+gscKFNrCER5zHs2YBPqXWcDNnJbyRwRu5toR/FgVtFVJo8gMFnMzshO03sm jiQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=sUbb8H7pbVQxtEixdvFVGzIDX+1yMrnu8PQSihHJ4gQ=; b=ZkpWIJq3vJUG4z1KOkdVqg00F42wml7RQf3NjI5O9v1bRahW1IM2mK+Woq5EV1pDWy JyIZCkTk2tyWkq58rU1dTvA28cCtBSBE61tmjmo2tN4AsRiRrEM4Ua5yasI0jJkrOgct lqGlUnnQCjAnFbTnDBR2fooRKXY5sDbMpS7hkN1qt9fEnJA6YcoogBZr/Uk6BKeO40sK k3uBwENxX78QnumsZNHZd/3dE4R+RSocWhtAOe6nasiKJQrdKnJ/dP7Lf0T53qDIXOr/ EiP8G97waTl8/0s5Z+He8ImEpvqV4yRhasa3eELSOxUj13bcvrRR0tuv+AwKcjccc38F uldA==
X-Gm-Message-State: AIkVDXJxKxASbYoMfRsSB3N7J+RCkiSzgQN6Pp0t3gXsMUbMGGNTg0xOb/Tkja7rTfg54jDeg4q0QRy90UUSBw==
X-Received: by 10.176.23.81 with SMTP id k17mr668680uaf.99.1485412332580; Wed, 25 Jan 2017 22:32:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.65.3 with HTTP; Wed, 25 Jan 2017 22:32:12 -0800 (PST)
In-Reply-To: <132DAB99-A623-47CD-9636-7DF67D75C188@tzi.org>
References: <2e19e2da-f86d-3889-690d-4d624a2c4489@gmx.net> <132DAB99-A623-47CD-9636-7DF67D75C188@tzi.org>
From: Zhen Cao <zhencao.ietf@gmail.com>
Date: Thu, 26 Jan 2017 14:32:12 +0800
Message-ID: <CAFxP68zuUp3q95cBSt1sVeB7LjtXQbWDNhhreYoSN1KQqJFjpA@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/vjuxRbnpmtDuwIGe0OeLB2KYgnQ>
Cc: "lwip@ietf.org" <lwip@ietf.org>
Subject: Re: [Lwip] Discussion about IoT Device Classes
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Lightweight IP stack <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jan 2017 06:32:15 -0000

On Thu, Jan 26, 2017 at 7:38 AM, Carsten Bormann <cabo@tzi.org> wrote:
> Sure.  We started that discussion a few IETFs ago and have a bis draft out at
> draft-bormann-lwig-7228bis.
>
> (I’m not sure that I will be in Chicago, but I could join from remote.)
>
> One thing that needs to be added before even discussing these device classes is the difference between micro controllers (which you have been calling M-class) and general purpose computing platforms (A-class).  Proposed text for that should be in the next version of 7228bis.
>

If I get it right, the M-class and A-class are mirroring to the modem-
and application- core.  But I am not sure what are the major
difference in implementing an IP layer stack on the two different
architectures. (that's something possible of interest to a larger
audience)

Best regards,
Zhen

>
>> On 25 Jan 2017, at 23:12, Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>>
>> Hi all,
>>
>> https://tools.ietf.org/html/rfc7228#section-3 defines these three
>> classes of IoT devices:
>>
>>     +-------------+-----------------------+-------------------------+
>>     | Name        | data size (e.g., RAM) | code size (e.g., Flash) |
>>     +-------------+-----------------------+-------------------------+
>>     | Class 0, C0 | << 10 KiB             | << 100 KiB              |
>>     |             |                       |                         |
>>     | Class 1, C1 | ~ 10 KiB              | ~ 100 KiB               |
>>     |             |                       |                         |
>>     | Class 2, C2 | ~ 50 KiB              | ~ 250 KiB               |
>>     +-------------+-----------------------+-------------------------+
>>
>> Is there an interest to get together at the next IETF meeting and to
>> talk about re-working on these classes and to provide more details about
>> the functionality that is included in this calculation based on ongoing
>> implementation work?
>>
>> Ciao
>> Hannes
>>
>> _______________________________________________
>> Lwip mailing list
>> Lwip@ietf.org
>> https://www.ietf.org/mailman/listinfo/lwip
>
> _______________________________________________
> Lwip mailing list
> Lwip@ietf.org
> https://www.ietf.org/mailman/listinfo/lwip