Transmission of IPv6 over Master-Slave/Token-Passing (MS/TP) Networks
RFC 8163

Document Type RFC - Proposed Standard (May 2017; No errata)
Last updated 2017-05-05
Replaces draft-ietf-6man-6lobac
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Mar 2015 - WG last call for dra... )
Document shepherd Samita Chakrabarti
Shepherd write-up Show (last changed 2016-07-28)
IESG IESG state RFC 8163 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to draft-ietf-6lo-6lobac@ietf.org, 6lo-chairs@ietf.org, "Samita Chakrabarti" <samitac.ietf@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                      K. Lynn, Ed.
Request for Comments: 8163                                  Verizon Labs
Category: Standards Track                                    J. Martocci
ISSN: 2070-1721                                         Johnson Controls
                                                              C. Neilson
                                                          Delta Controls
                                                            S. Donaldson
                                                               Honeywell
                                                                May 2017

 Transmission of IPv6 over Master-Slave/Token-Passing (MS/TP) Networks

Abstract

   Master-Slave/Token-Passing (MS/TP) is a medium access control method
   for the RS-485 physical layer and is used primarily in building
   automation networks.  This specification defines the frame format for
   transmission of IPv6 packets and the method of forming link-local and
   statelessly autoconfigured IPv6 addresses on MS/TP networks.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8163.

Lynn, et al.                 Standards Track                    [Page 1]
RFC 8163                IPv6 over MS/TP (6LoBAC)                May 2017

Copyright Notice

   Copyright (c) 2017 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
   (http://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Profile for IPv6 over MS/TP . . . . . . . . . . . . . . . . .   6
   3.  Addressing Modes  . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Maximum Transmission Unit (MTU) . . . . . . . . . . . . . . .   8
   5.  LoBAC Adaptation Layer  . . . . . . . . . . . . . . . . . . .   8
   6.  Stateless Address Autoconfiguration . . . . . . . . . . . . .   9
   7.  IPv6 Link-Local Address . . . . . . . . . . . . . . . . . . .  10
   8.  Unicast Address Mapping . . . . . . . . . . . . . . . . . . .  10
   9.  Multicast Address Mapping . . . . . . . . . . . . . . . . . .  11
   10. Header Compression  . . . . . . . . . . . . . . . . . . . . .  11
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  12
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Appendix A.  Abstract MAC Interface . . . . . . . . . . . . . . .  15
   Appendix B.  Consistent Overhead Byte Stuffing (COBS) . . . . . .  17
   Appendix C.  Encoded CRC-32K (CRC32K) . . . . . . . . . . . . . .  20
   Appendix D.  Example 6LoBAC Frame Decode  . . . . . . . . . . . .  22
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  27
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  27

Lynn, et al.                 Standards Track                    [Page 2]
RFC 8163                IPv6 over MS/TP (6LoBAC)                May 2017

1.  Introduction

   Master-Slave/Token-Passing (MS/TP) is a Medium Access Control (MAC)
   protocol for the RS-485 [TIA-485-A] physical layer and is used
   primarily in building automation networks.  This specification
   defines the frame format for transmission of IPv6 [RFC2460] packets
   and the method of forming link-local and statelessly autoconfigured
   IPv6 addresses on MS/TP networks.  The general approach is to adapt
   elements of the 6LoWPAN specifications ([RFC4944], [RFC6282], and
   [RFC6775]) to constrained wired networks, as noted below.

   An MS/TP device is typically based on a low-cost microcontroller with
   limited processing power and memory.  These constraints, together
Show full document text