idnits 2.17.1 draft-ernst-its-ipv6-over-80211ocb-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 8, 2016) is 2842 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 128 -- Looks like a reference, but probably isn't: '16' on line 138 -- Looks like a reference, but probably isn't: '13' on line 136 -- Looks like a reference, but probably isn't: '14' on line 136 -- Looks like a reference, but probably isn't: '15' on line 138 == Unused Reference: 'ieee802.11p-2010' is defined on line 176, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Ernst 3 Internet-Draft YoGoKo 4 Intended status: Informational A. Petrescu 5 Expires: January 9, 2017 CEA, LIST 6 July 8, 2016 8 Transmission of IPv6 Packets over IEEE 802.11-OCB Networks 9 draft-ernst-its-ipv6-over-80211ocb-00.txt 11 Abstract 13 In this document the mapping of multicast IPv6 addresses to MAC 14 addresses of 802.11-OCB is proposed. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on January 9, 2017. 33 Copyright Notice 35 Copyright (c) 2016 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 3. Maximum Transmission Unit . . . . . . . . . . . . . . . . . . 3 53 4. Frame Format . . . . . . . . . . . . . . . . . . . . . . . . 3 54 5. Stateless Autoconfiguration . . . . . . . . . . . . . . . . . 3 55 6. Link-Local Addresses . . . . . . . . . . . . . . . . . . . . 3 56 7. Address Mapping -- Unicast . . . . . . . . . . . . . . . . . 3 57 8. Address Mapping -- Multicast . . . . . . . . . . . . . . . . 3 58 9. Security Considerations . . . . . . . . . . . . . . . . . . . 4 59 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 60 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 61 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 12.1. Normative References . . . . . . . . . . . . . . . . . . 4 63 12.2. Informative References . . . . . . . . . . . . . . . . . 4 64 Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 5 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 67 1. Introduction 69 In this document the mapping of link-scoped multicast IPv6 addresses 70 to MAC addresses of 802.11-OCB is proposed. 72 IPv6 protocols often make use of IPv6 multicast addresses in the 73 destination field of IPv6 headers. For example, an ICMPv6 link- 74 scoped Neighbor Advertisement is sent to the IPv6 address ff02::1 75 denoted "all-nodes" address. When transmitting these packets on 76 802.11-OCB links it is necessary to map the IPv6 address to a MAC 77 address. 79 The same mapping requirement applies to the link-scoped multicast 80 addresses of other IPv6 protocols as well. In DHCPv6, the 81 "All_DHCP_Servers" IPv6 multicast address ff02::1:2, and in OSPF the 82 "All_SPF_Routers" IPv6 multicast address ff02::5, need to be mapped 83 on a multicast MAC address. 85 Other than link-scope addressing, it may be possible to conceive 86 other IPv6 multicast addresses for specific use in vehicular 87 communication scenarios. For example, certain vehicle types (or road 88 infrastructure equipment) in a zone can be denoted by an IPv6 89 multicast address: "all-yellow-taxis-in-street", or "all-uber-cars". 90 This helps sending a message to these particular types of vehicles, 91 instead of sending to all vehicles in that same street. The 92 protocols SDP and LLDP could further be used in managing this as a 93 service. 95 It may be possible to map parts of other-than-link-scope IPv6 96 multicast address (e.g. parts of a global-scope IPv6 multicast 97 address) into parts of a 802.11-OCB MAC address. This may help 98 certain IPv6 operations. 100 2. Terminology 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC 2119 [RFC2119]. 106 OCB - Outside the Context of a Basic-Service Set ID (BSSID). 108 802.11-OCB - IEEE 802.11-2012 text flagged by "dot11OCBActivated". 109 This means: IEEE 802.11e for quality of service; 802.11j-2004 for 110 half-clocked operations; and 802.11p for operation in the 5.9 GHz 111 band and in mode OCB. 113 3. Maximum Transmission Unit 115 MTU is 117 4. Frame Format 119 5. Stateless Autoconfiguration 121 6. Link-Local Addresses 123 7. Address Mapping -- Unicast 125 8. Address Mapping -- Multicast 127 An IPv6 packet with a multicast destination address DST, consisting 128 of the sixteen octets DST[1] through DST[16], is transmitted to the 129 IEEE 802.11-OCB MAC multicast address whose first two octets are the 130 value 0x3333 and whose last four octets are the last four octets of 131 DST. 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 |0 0 1 1 0 0 1 1|0 0 1 1 0 0 1 1| 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | DST[13] | DST[14] | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | DST[15] | DST[16] | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 A Group ID TBD of length 112bits may be requested from IANA; this 142 Group ID signifies "All 80211OCB Interfaces Address". Only the least 143 32 significant bits of this "All 80211OCB Interfaces Address" will be 144 mapped to and from a MAC multicast address. 146 Alternatively, instead of 0x3333 address other addresses reserved at 147 IEEE can be considered. The Group MAC addresses reserved at IEEE are 148 listed at https://standards.ieee.org/develop/regauth/grpmac/ 149 public.html (address browsed in July 2016). 151 9. Security Considerations 153 the security section 155 10. IANA Considerations 157 The Group ID for "All 80211OCB Interfaces Address" is TBD. 159 11. Acknowledgements 161 The authors would like to acknowledge Owen DeLong, Joe Touch, Jen 162 Linkova, Erik Kline and participants to discussions in network 163 working groups. 165 12. References 167 12.1. Normative References 169 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 170 Requirement Levels", BCP 14, RFC 2119, 171 DOI 10.17487/RFC2119, March 1997, 172 . 174 12.2. Informative References 176 [ieee802.11p-2010] 177 "IEEE Std 802.11p(TM)-2010, IEEE Standard for Information 178 Technology - Telecommunications and information exchange 179 between systems - Local and metropolitan area networks - 180 Specific requirements, Part 11: Wireless LAN Medium Access 181 Control (MAC) and Physical Layer (PHY) Specifications, 182 Amendment 6: Wireless Access in Vehicular Environments; 183 document freely available at URL 184 http://standards.ieee.org/getieee802/ 185 download/802.11p-2010.pdf retrieved on September 20th, 186 2013.". 188 Appendix A. ChangeLog 190 The changes are listed in reverse chronological order, most recent 191 changes appearing at the top of the list. 193 From -00.txt to -00.txt: 195 o first version. 197 Authors' Addresses 199 Thierry Ernst 200 YoGoKo 201 France 203 Email: thierry.ernst@yogoko.fr 205 Alexandre Petrescu 206 CEA, LIST 207 Communicating Systems Laboratory 208 Gif-sur-Yvette , Ile-de-France 91190 209 France 211 Phone: +33169089223 212 Email: Alexandre.Petrescu@cea.fr