<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" []>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>

<rfc category="info"
     docName="draft-ernst-its-ipv6-over-80211ocb-00.txt"
     ipr="trust200902">

  <!-- category values: std, bcp, info, exp, and historic ipr values:
       trust200902, noModificationTrust200902,
       noDerivativesTrust200902, or pre5378Trust200902 you can add the
       attributes updates="NNNN" and obsoletes="NNNN" they will
       automatically be output with "(if approved)" -->

  <front>

    <title abbrev="IPv6-over-80211OCB-mcast">
      Transmission of IPv6 Packets over IEEE 802.11-OCB Networks
    </title>

    <author initials="T." surname="Ernst" fullname="Thierry Ernst">
      <organization>YoGoKo</organization>
      <address>
	<postal>
	  <street>
	  </street>
	  <city>
	  </city>
	  <region>
	  </region>
	  <code>
	  </code>
	  <country>
	    France
	  </country>
	</postal>
	<phone>
	</phone>
	<email>
	  thierry.ernst@yogoko.fr
	</email>
      </address>
    </author>

    <author initials='A.' surname="Petrescu" fullname='Alexandre Petrescu'>
      <organization>CEA, LIST</organization>
      <address>
	<postal>
	  <street>
	    Communicating Systems Laboratory
	  </street>
	  <city>
	    Gif-sur-Yvette
	  </city>
	  <region>
	    Ile-de-France
	  </region>
	  <code>
	    91190
	  </code>
	  <country>
	    France
	  </country>
	</postal>
	<phone>
	  +33169089223
	</phone>
	<email>
	  Alexandre.Petrescu@cea.fr
	</email>
      </address>
    </author>

    <date/>

    <!-- Meta-data Declarations -->

    <area>Internet</area>

    <workgroup>Network Working Group</workgroup>

    <!-- WG name at the upperleft corner of the doc, IETF is fine for
         individual submissions.  If this element is not present, the
         default is "Network Working Group", which is used by the RFC
         Editor as a nod to the history of the IETF. -->

    <keyword>
      IPv6 over 802.11 OCB
    </keyword>

    <!-- Keywords will be incorporated into HTML output files in a
         meta tag but they have no effect on text or nroff output. If
         you submit your draft to the RFC Editor, the keywords will be
         used for the search engine. -->

    <abstract>
      <t>
	In this document the mapping of multicast IPv6 addresses to
	MAC addresses of 802.11-OCB is proposed.
      </t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>
	In this document the mapping of link-scoped multicast IPv6
	addresses to MAC addresses of 802.11-OCB is proposed.
      </t>
      <t>
	IPv6 protocols often make use of IPv6 multicast addresses in
	the destination field of IPv6 headers.  For example, an ICMPv6
	link-scoped Neighbor Advertisement is sent to the IPv6 address
	ff02::1 denoted "all-nodes" address.  When transmitting these
	packets on 802.11-OCB links it is necessary to map the IPv6
	address to a MAC address.
      </t>
      <t>
	The same mapping requirement applies to the link-scoped
	multicast addresses of other IPv6 protocols as well.  In
	DHCPv6, the "All_DHCP_Servers" IPv6 multicast address
	ff02::1:2, and in OSPF the "All_SPF_Routers" IPv6 multicast
	address ff02::5, need to be mapped on a multicast MAC address.
      </t>
      <t>
	Other than link-scope addressing, it may be possible to
	conceive other IPv6 multicast addresses for specific use in
	vehicular communication scenarios.  For example, certain
	vehicle types (or road infrastructure equipment) in a zone can
	be denoted by an IPv6 multicast address:
	"all-yellow-taxis-in-street", or "all-uber-cars".  This helps
	sending a message to these particular types of vehicles,
	instead of sending to all vehicles in that same street.  The
	protocols SDP and LLDP could further be used in managing this
	as a service.
      </t>
      <t>
	It may be possible to map parts of other-than-link-scope IPv6
	multicast address (e.g. parts of a global-scope IPv6 multicast
	address) into parts of a 802.11-OCB MAC address.  This may
	help certain IPv6 operations.
      </t>
    </section>
    
    <section title="Terminology">
      <t>
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
        document are to be interpreted as described in
	<xref target="RFC2119">RFC 2119</xref>.
      </t>
      <t>
	OCB - Outside the Context of a Basic-Service Set ID (BSSID).
      </t>
      <t>
	802.11-OCB - IEEE 802.11-2012 text flagged by
	"dot11OCBActivated".  This means: IEEE 802.11e for quality of
	service; 802.11j-2004 for half-clocked operations; and 802.11p
	for operation in the 5.9 GHz band and in mode OCB.
      </t>
    </section>

    <section title="Maximum Transmission Unit">
      <t>
	MTU is
      </t>
    </section>

    <section title="Frame Format">
      <t>
      </t>
    </section>

    <section title="Stateless Autoconfiguration">
      <t>
      </t>
    </section>

    <section title="Link-Local Addresses">
      <t>
      </t>
    </section>

    <section title="Address Mapping -- Unicast">
      <t>
      </t>
    </section>

    <section title="Address Mapping -- Multicast">
      <t>
	An IPv6 packet with a multicast destination address DST,
	consisting of the sixteen octets DST[1] through DST[16], is
	transmitted to the IEEE 802.11-OCB MAC multicast address whose
	first two octets are the value 0x3333 and whose last four
	octets are the last four octets of DST.
      </t>

      <t> 
	<figure align="center">
	  <artwork align="center">
	    <![CDATA[
                     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                     |0 0 1 1 0 0 1 1|0 0 1 1 0 0 1 1|
                     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                     |   DST[13]     |   DST[14]     |
                     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                     |   DST[15]     |   DST[16]     |
                     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	    ]]>
	  </artwork>
	</figure>
      </t>
	
      <t>	  
	A Group ID TBD of length 112bits may be requested from IANA;
	this Group ID signifies "All 80211OCB Interfaces Address".
	Only the least 32 significant bits of this "All 80211OCB
	Interfaces Address" will be mapped to and from a MAC multicast
	address.
      </t>
      <t>
	Alternatively, instead of 0x3333 address other addresses
	reserved at IEEE can be considered.  The Group MAC addresses
	reserved at IEEE are listed at
	https://standards.ieee.org/develop/regauth/grpmac/public.html
	(address browsed in July 2016).
      </t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>
	the security section
      </t>

    </section>    

    <section anchor="IANA" title="IANA Considerations">
      <t>
	The Group ID for "All 80211OCB Interfaces Address" is TBD.
      </t>
    </section>

    <section anchor="Acknowledgements"
	     title="Acknowledgements">
      <t>
	The authors would like to acknowledge Owen DeLong, Joe Touch,
	Jen Linkova, Erik Kline and participants to discussions in
	network working groups.
      </t>
    </section>
      

    </middle>

    <!--  *****BACK MATTER ***** -->

    <back>

      <references title="Normative References">
	<?rfc
	  include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119"
	?>
      </references>

      <references title="Informative References">
	<reference anchor="ieee802.11p-2010" >
	  <front>
	    <title>
	      IEEE Std 802.11p(TM)-2010, IEEE Standard for Information
	      Technology - Telecommunications and information exchange
	      between systems - Local and metropolitan area networks -
	      Specific requirements, Part 11: Wireless LAN Medium
	      Access Control (MAC) and Physical Layer (PHY)
	      Specifications, Amendment 6: Wireless Access in
	      Vehicular Environments; document freely available at URL
	      http://standards.ieee.org/getieee802/download/802.11p-2010.pdf
	      retrieved on September 20th, 2013.
	    </title>
	    <author/>
	    <date/>
	  </front>
	</reference>

      </references>

      <section anchor='changelog'
	       title='ChangeLog'>
	<t>
	  The changes are listed in reverse chronological order, most
	  recent changes appearing at the top of the list.
	</t>

	<t>
	  From -00.txt to -00.txt:
	  <list style='symbols'>
	    <t>
	      first version.
	    </t>
	  </list>	
	</t>      
      </section>
  </back>
</rfc>
