[6lo] Updating the subject, and some comments (Re: Call for adoption of draft-wachter-6lo-can-00 by 6Lo WG)

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Thu, 17 October 2019 16:16 UTC

Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 05B5D1209C9 for <6lo@ietfa.amsl.com>; Thu, 17 Oct 2019 09:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id U5ZnXxx3wecw for <6lo@ietfa.amsl.com>; Thu, 17 Oct 2019 09:16:38 -0700 (PDT)
Received: from dash.upc.es (dash.upc.es []) (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 DB59B120118 for <6lo@ietf.org>; Thu, 17 Oct 2019 09:16:35 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es []) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id x9HGGXFR043611; Thu, 17 Oct 2019 18:16:33 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu []) by entelserver.upc.edu (Postfix) with ESMTP id 3146F1D53C1; Thu, 17 Oct 2019 18:16:32 +0200 (CEST)
Received: from by webmail.entel.upc.edu with HTTP; Thu, 17 Oct 2019 18:16:33 +0200
Message-ID: <d76a963526245134d3f2d2d4f8941f5e.squirrel@webmail.entel.upc.edu>
In-Reply-To: <7de413c1-726e-8595-fe21-0a6f3fe97dcd@wachter.cloud>
References: <7de413c1-726e-8595-fe21-0a6f3fe97dcd@wachter.cloud>
Date: Thu, 17 Oct 2019 18:16:33 +0200
From: "Carles Gomez Montenegro" <carlesgo@entel.upc.edu>
To: "Alexander Wachter" <alexander@wachter.cloud>
Cc: 6lo@ietf.org
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.100.3 at dash
X-Virus-Status: Clean
X-Greylist: Delayed for 09:54:44 by milter-greylist-4.3.9 (dash.upc.es []); Thu, 17 Oct 2019 18:16:33 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/2uylHci0lYFWjU8X3sF8VXmXPzA>
Subject: [6lo] Updating the subject, and some comments (Re: Call for adoption of draft-wachter-6lo-can-00 by 6Lo WG)
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2019 16:16:41 -0000

Dear Alexander,

Thanks for your new Internet Draft submission!

As a chair, I would like to clarify one procedural detail. When working
group (WG) chairs want to verify whether there exists WG consensus for
adopting a document as a WG document, the chairs issue a (somewhat) formal
"Call for adoption" email. It must be noted that your email below does not
correspond to a "Call for adoption" in the usual terms, and at this stage
you rather *mean* "Call for feedback".

Other than that, and with or without a particular hat, I think that what
you wrote below (and in the draft) is already useful to start assessing
whether 6Lo is the appropriate WG for your document. By the way, the CAN
MTU characteristics do correspond to significant constrainedness!

It is very positive that there exists already a reference implementation

I have a few clarifying questions:

- What type of power sources can we expect for CAN devices?

- What bit rate/rates is/are typical in CAN?

- What kind of errors (e.g. due to BER) can we expect? Would CAN be
categorized as a lossy technology, or rather as a very low error rate
technology (e.g. Ethernet-like)?



> Dear 6Lo WG,
> I recently submitted a draft for IPv6 over Controller Area Network and
> would like to call for adoption by the 6Lo WG.
> The title of the document is draft-wachter-6lo-can-00 [1].
> Controller Area Network (CAN) is a widely used field bus initially
> designed for the automotive domain. It has a payload length of eight
> bytes for classic CAN and 64 bytes for CAN-FD. CAN only describes the
> data-link-layer, but various protocols already exist on top. The
> submitted draft introduces IPv6 over CAN (6LoCAN),  a 6lo-adaption-layer
> to send IPv6 packets over the constrained CAN-bus. 6LoCAN uses a subset
> of the already widely used ISO-TP standard for fragmentation and
> reassembly to meet the 1280 minimum MTU requirement of IPv6. It also
> uses the IPHC (RFC6282) to reduce the protocol overhead of IPv6.
> A broad range of devices, from small and cheap MCUs to big application
> processors, already have CAN controllers onboard. With 6LoCAN, it is
> possible to create networks of resource-constrained MCUs that can
> leverage the broad range of protocols and security mechanisms built on
> top of the IP.
> Additionally, multiple 6LoCAN networks can be connected together or even
> to the internet by utilizing the routing capabilities of IP networks.
> A reference implementation of 6LoCAN already exists in the mainline
> Zephyrproject RTOS [2] tree. It includes a sample server-client
> application. The source for it is located under [3] and can be used on
> any boards supporting CAN.
> I am looking forward to your comments on the draft.
> Kind regards,
> Alexander
> [1] https://datatracker.ietf.org/doc/draft-wachter-6lo-can/
> [2] https://www.zephyrproject.org/
> [3]
> https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/net/sockets/echo_client
> --
> Alexander Wachter, BSc
> Student of Information and Computer Engineering
> Graz University of Technology
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo