One document matched: draft-lee-its-ipv6-over-80211ocb-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!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-lee-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">
      Transmission of IPv6 Packets over the IEEE 802.11p OCB Mode
    </title>

<author fullname="Jong-Hyouk Lee" initials="J.-H." surname="Lee">
<organization>Sangmyung University</organization> <address>	<postal> <street>31, Sangmyeongdae-gil, Dongnam-gu</street> <code>31066</code> <city>Cheonan</city> <country>Republic of Korea</country>
</postal>	<email>jonghyouk@smu.ac.kr</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>
	This document describes the transmission of IPv6 packets over
	the IEEE 802.11p OCB mode.  In particular it sets the MTU
	parameter and describes two alternative frame formats.
      </t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>
	In the IEEE 802.11p OCB mode, all nodes in the wireless range can directly communicate with each other without authentication/association procedures, thus data exchange between nodes can be established in fractions of seconds. The IEEE 802.11p OCB mode has the following properties:

<list style="symbols">
<t> Wildcard BSSID (i.e., all bits are set to 1) used by each node </t>
<t> No beacons transmitted </t>
<t> No authentication required </t>
<t> No association needed </t>
<t> No encryption provided </t>
<t> dot11OCBActivated OID set to true </t>
</list>

	This document describes the transmission of IPv6 packets over the IEEE 802.11p OCB mode.
      </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 BSS.
      </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>
	The default MTU size for IPv6 packets on an 802.11-OCB link is
	1500 octets.  This size may be reduced by a Router
	Advertisement containing an MTU option which specifies a
	smaller MTU, or by manual (or DHCPv6) configuration of each
	node.  If a Router Advertisement received on an 802.11-OCB
	interface has an MTU option specifying an MTU larger than
	1500 octets, or larger than a manually configured value, that MTU
	option may be logged to system management but must be
	otherwise ignored.
      </t>
      <t>
	Non-IPv6 packets such as WAVE Short Message Protocol (WSMP) can be delivered on 802.11-OCB links. 
	Specifications of these packets are out of scope and do not impose any limit on the MTU size,
	allowing an arbitrary number of 'containers'.
      </t>
    </section>

    <section title="Frame Format">
      <t>
	IPv6 packets can be transmitted as "IEEE 802.11 Data" or
	alternatively as "IEEE 802.11 QoS Data".
      </t>
      <t> 
	<figure align="center">
	  <artwork align="center">
	    <![CDATA[
IEEE 802.11 Data                   IEEE 802.11 QoS Data
Logical-Link Control               Logical-Link Control
IPv6 Header                        IPv6 Header     
	    ]]>
	  </artwork>
	</figure>
      </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>
      </t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>
      </t>
    </section>    

    <section anchor="IANA" title="IANA Considerations">
      <t>
      </t>
    </section>

    <section anchor="Acknowledgements"
	     title="Acknowledgements">
      <t>
	The authors would like to acknowledge...
      </t>
    </section>
      

    </middle>

    <!--  *****BACK MATTER ***** -->

    <back>

      <references title="Normative References">
	<?rfc
	  include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119"
	?>
	<?rfc
	  include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2460"
	?>       
	<?rfc
	  include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2464"
	?>            
      </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>

	<?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.petrescu-its-scenarios-reqs" ?>      	
      </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>