--- 1/draft-ietf-6lo-6lobac-03.txt 2016-02-22 16:15:21.539813995 -0800 +++ 2/draft-ietf-6lo-6lobac-04.txt 2016-02-22 16:15:21.591815253 -0800 @@ -1,23 +1,23 @@ 6Lo Working Group K. Lynn, Ed. Internet-Draft Verizon Labs Intended status: Standards Track J. Martocci -Expires: April 21, 2016 Johnson Controls +Expires: August 25, 2016 Johnson Controls C. Neilson Delta Controls S. Donaldson Honeywell - October 19, 2015 + February 22, 2016 Transmission of IPv6 over MS/TP Networks - draft-ietf-6lo-6lobac-03 + draft-ietf-6lo-6lobac-04 Abstract Master-Slave/Token-Passing (MS/TP) is a medium access control method for the RS-485 physical layer, which is used extensively 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 @@ -28,25 +28,25 @@ 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 http://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 April 21, 2016. + This Internet-Draft will expire on August 25, 2016. Copyright Notice - Copyright (c) 2015 IETF Trust and the persons identified as the + Copyright (c) 2016 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 @@ -63,23 +63,23 @@ 7. IPv6 Link Local Address . . . . . . . . . . . . . . . . . . . 8 8. Unicast Address Mapping . . . . . . . . . . . . . . . . . . . 9 9. Multicast Address Mapping . . . . . . . . . . . . . . . . . . 9 10. Header Compression . . . . . . . . . . . . . . . . . . . . . 10 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 12. Security Considerations . . . . . . . . . . . . . . . . . . . 10 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 Appendix A. Abstract MAC Interface . . . . . . . . . . . . . . . 13 Appendix B. Consistent Overhead Byte Stuffing [COBS] . . . . . . 16 - Appendix C. Encoded CRC-32K [CRC32K] . . . . . . . . . . . . . . 19 - Appendix D. Example 6LoBAC Packet Decode . . . . . . . . . . . . 21 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 + Appendix C. Encoded CRC-32K [CRC32K] . . . . . . . . . . . . . . 20 + Appendix D. Example 6LoBAC Packet Decode . . . . . . . . . . . . 22 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 1. Introduction Master-Slave/Token-Passing (MS/TP) is a medium access control (MAC) protocol for the RS-485 [TIA-485-A] physical layer, which is used extensively 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 @@ -344,25 +344,25 @@ |0 5|6 1|2 7|8 3| +----------------+----------------+----------------+----------------+ |0000000000000000|0000000011111111|1111111000000000|0000000001001111| +----------------+----------------+----------------+----------------+ This is the RECOMMENDED method of forming an IID for use in link- local addresses, as it affords the most efficient header compression provided by the LOWPAN_IPHC [RFC6282] format specified in Section 10. A 64-bit privacy IID is RECOMMENDED for routable addresses and SHOULD - be locally generated according to [I-D.ietf-6man-default-iids]. A - node that generates a 64-bit privacy IID MUST register it with its - local router(s) by sending a Neighbor Solicitation (NS) message with - the Address Registration Option (ARO) and process Neighbor - Advertisements (NA) according to [RFC6775]. + be locally generated according to one of the methods cited in + Section 12. A node that generates a 64-bit privacy IID MUST register + it with its local router(s) by sending a Neighbor Solicitation (NS) + message with the Address Registration Option (ARO) and process + Neighbor Advertisements (NA) according to [RFC6775]. An IPv6 address prefix used for stateless autoconfiguration [RFC4862] of an MS/TP interface MUST have a length of 64 bits. 7. IPv6 Link Local Address The IPv6 link-local address [RFC4291] for an MS/TP interface is formed by appending the Interface Identifier, as defined above, to the prefix FE80::/64. @@ -449,27 +449,30 @@ 11. IANA Considerations This document uses values previously reserved by [RFC4944] and [RFC6282] and makes no further requests of IANA. Note to RFC Editor: this section may be removed upon publication. 12. Security Considerations - The security and privacy implications of embedding a link-layer - address in an IPv6 IID are discussed in - [I-D.ietf-6man-ipv6-address-generation-privacy]. The issue most - relevant to MS/TP networks is address scanning. This is mainly an - issue for routable addresses and probably only for those hosted on - the global Internet. This specification RECOMMENDS mitigating this - threat according to [I-D.ietf-6man-default-iids]. + Routable addresses that contain IIDs generated using MS/TP node + addresses may expose a network to address scanning attacks. For this + reason, it is RECOMMENDED that a different (but stable) IID be + generated for each routable address in use according to, for example, + [RFC3315], [RFC3972], [RFC4941], [RFC5535], or [RFC7217]. + + MS/TP networks are by definition wired and not susceptible to to + casual eavesdropping. By the same token, MS/TP nodes are stationary + and correlation of activities or location tracking of individuals is + unlikely. 13. Acknowledgments We are grateful to the authors of [RFC4944] and members of the IETF 6LoWPAN working group; this document borrows liberally from their work. Ralph Droms and Brian Haberman provided indispensable guidance and support from the outset. Peter van der Stok, James Woodyatt, and Carsten Bormann provided detailed reviews. Stuart Cheshire invented the very clever COBS encoding. Michael Osborne made the critical observation that seperately encoding the data and CRC32K fields would @@ -495,54 +498,78 @@ [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, December 1998, . + [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, + C., and M. Carney, "Dynamic Host Configuration Protocol + for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July + 2003, . + + [RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)", + RFC 3972, DOI 10.17487/RFC3972, March 2005, + . + [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, DOI 10.17487/RFC4291, February 2006, . [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, DOI 10.17487/RFC4861, September 2007, . [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Address Autoconfiguration", RFC 4862, DOI 10.17487/RFC4862, September 2007, . + [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy + Extensions for Stateless Address Autoconfiguration in + IPv6", RFC 4941, DOI 10.17487/RFC4941, September 2007, + . + [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007, . + [RFC5535] Bagnulo, M., "Hash-Based Addresses (HBA)", RFC 5535, + DOI 10.17487/RFC5535, June 2009, + . + [RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, DOI 10.17487/RFC6282, September 2011, . [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C. Bormann, "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)", RFC 6775, DOI 10.17487/RFC6775, November 2012, . [RFC7136] Carpenter, B. and S. Jiang, "Significance of IPv6 Interface Identifiers", RFC 7136, DOI 10.17487/RFC7136, February 2014, . + [RFC7217] Gont, F., "A Method for Generating Semantically Opaque + Interface Identifiers with IPv6 Stateless Address + Autoconfiguration (SLAAC)", RFC 7217, + DOI 10.17487/RFC7217, April 2014, + . + [RFC7400] Bormann, C., "6LoWPAN-GHC: Generic Header Compression for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)", RFC 7400, DOI 10.17487/RFC7400, November 2014, . 14.2. Informative References [COBS] Cheshire, S. and M. Baker, "Consistent Overhead Byte Stuffing", IEEE/ACM TRANSACTIONS ON NETWORKING, VOL.7, NO.2 , April 1999, @@ -552,32 +579,20 @@ Applications", IEEE/IFIP International Conference on Dependable Systems and Networks (DSN 2002) , June 2002, . [EUI-64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority", March 1997, . - [I-D.ietf-6man-default-iids] - Gont, F., Cooper, A., Thaler, D., and S. LIU, - "Recommendation on Stable IPv6 Interface Identifiers", - draft-ietf-6man-default-iids-08 (work in progress), - October 2015. - - [I-D.ietf-6man-ipv6-address-generation-privacy] - Cooper, A., Gont, F., and D. Thaler, "Privacy - Considerations for IPv6 Address Generation Mechanisms", - draft-ietf-6man-ipv6-address-generation-privacy-08 (work - in progress), September 2015. - [IEEE.802.3] "Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CMSA/CD) Access Method and Physical Layer Specifications", IEEE Std 802.3-2012, December 2012, . [RFC2469] Narten, T. and C. Burton, "A Caution On The Canonical