IPv6 over Controller Area Network
draft-wachter-6lo-can-00

Document Type Active Internet-Draft (individual)
Last updated 2019-10-17
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
6Lo Working Group                                             A. Wachter
Internet-Draft                             Graz University of Technology
Intended status: Standards Track                         17 October 2019
Expires: 19 April 2020

                   IPv6 over Controller Area Network
                        draft-wachter-6lo-can-00

Abstract

   Controller Area Network (CAN) is a fieldbus initially designed for
   automotive applications.  It is a multi-master bus with 11-bit or
   29-bit frame identifiers.  The CAN standard (ISO 11898 series)
   defines the physical and data-link layer.  This document describes
   how to transfer IPv6 packets over CAN using ISO-TP, a dedicated
   addressing scheme, and IP header compression (IPHC).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 19 April 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Wachter                   Expires 19 April 2020                 [Page 1]
Internet-Draft                   6LoCAN                     October 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Controller Area Network Overview  . . . . . . . . . . . .   3
     1.3.  ISO-TP Overview . . . . . . . . . . . . . . . . . . . . .   3
   2.  Addressing  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Unicast . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Multicast . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Address Generation  . . . . . . . . . . . . . . . . . . .   6
   3.  Link-Layer Duplicate Address Detection  . . . . . . . . . . .   6
   4.  Stateless Address Autoconfiguration . . . . . . . . . . . . .   7
   5.  IPv6 Link-Local Address . . . . . . . . . . . . . . . . . . .   8
   6.  ISO-TP  . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Multicast . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.2.  Unicast . . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.3.  Frame Format  . . . . . . . . . . . . . . . . . . . . . .  10
     6.4.  Single-Frame  . . . . . . . . . . . . . . . . . . . . . .  11
     6.5.  First-Frame . . . . . . . . . . . . . . . . . . . . . . .  11
     6.6.  Consecutive-Frame . . . . . . . . . . . . . . . . . . . .  12
     6.7.  Flow-Control-Frame  . . . . . . . . . . . . . . . . . . .  12
   7.  Frame Format  . . . . . . . . . . . . . . . . . . . . . . . .  13
   8.  Ethernet Border Translator  . . . . . . . . . . . . . . . . .  14
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  16
   11. Reference Implementation  . . . . . . . . . . . . . . . . . .  16
   12. Normative References  . . . . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Controller Area Network (CAN) is mostly known for its use in the
   automotive domain.  However, it is also used in industrial
   applications as CANopen, building automation and many more.

   It is a two-wire wired-AND multi-master bus that uses CSMA/CR in its
   arbitration field.  CAN uses 11-bit (standard ID) and 29-bit
   (extended ID) identifiers to identify frames.  The maximum payload
   data size is 8 octets for classical CAN and 64 octets for CAN-FD.

   The minimal MTU of IPv6 is 1280 octets, and therefore, a mechanism to
   support a larger payload is needed.  This document uses a slightly
   modified version of the ISO-TP protocol to transfer data up to 4095
   octets per packet.  Mapping addresses to identifiers uses an
Show full document text