<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" submissionType="IETF" category="std" consensus="true" docName="draft-ietf-6lo-nfc-22" number="9428" ipr="trust200902" obsoletes="" updates="" xml:lang="en" tocInclude="true" tocDepth="4" symRefs="true" sortRefs="true" prepTime="2023-07-20T16:13:48" indexInclude="true" scripts="Common,Latin">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-6lo-nfc-22" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9428" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="IPv6 over NFC">Transmission of IPv6 Packets over Near Field Communication</title>
    <seriesInfo name="RFC" value="9428" stream="IETF"/>
    <author fullname="Younghwan Choi" role="editor" initials="Y." surname="Choi">
      <organization abbrev="ETRI" showOnFrontPage="true">Electronics and Telecommunications Research Institute</organization>
      <address>
        <postal>
          <street>218 Gajeongno, Yuseung-gu</street>
          <street/>
          <city>Daejeon</city>
          <code>34129</code>
          <country>South Korea</country>
        </postal>
        <phone>+82 42 860 1429</phone>
        <email>yhc@etri.re.kr</email>
      </address>
    </author>
    <author fullname="Yong-Geun Hong" initials="Y-G." surname="Hong">
      <organization abbrev="Daejon Univ" showOnFrontPage="true">Daejon University</organization>
      <address>
        <postal>
          <street>62 Daehak-ro, Dong-gu</street>
          <city>Daejeon</city>
          <code>34520</code>
          <country>South Korea</country>
        </postal>
        <phone>+82 42 280 4841</phone>
        <email>yonggeun.hong@gmail.com</email>
      </address>
    </author>
    <author fullname="Joo-Sang Youn" initials="J-S." surname="Youn">
      <organization abbrev="Dongeui Univ" showOnFrontPage="true">DONG-EUI University</organization>
      <address>
        <postal>
          <street>176 Eomgwangno Busan_jin_gu</street>
          <city>Busan</city>
          <code>614-714</code>
          <country>South Korea</country>
        </postal>
        <phone>+82 51 890 1993</phone>
        <email>joosang.youn@gmail.com</email>
      </address>
    </author>
    <date month="07" year="2023"/>
    <area>int</area>
    <workgroup>6lo</workgroup>
    <keyword>Near Field Communication</keyword>
    <keyword>NFC</keyword>
    <keyword>6LowPAN</keyword>
    <keyword>IPv6</keyword>
    <keyword>Adaptation Layer</keyword>
    <keyword>IoT</keyword>
    <keyword>Internet of Things</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">Near Field Communication (NFC) is a set of standards for smartphones and portable devices to establish radio communication with each other by touching them together or bringing them into proximity, usually no more than 10 cm apart. NFC standards cover communication protocols and data exchange formats and are based on existing Radio Frequency Identification (RFID) standards, including ISO/IEC 14443 and FeliCa. The standards include ISO/IEC 18092 and those defined by the NFC Forum. The NFC technology has been widely implemented and available in mobile phones, laptop computers, and many other devices. This document describes how IPv6 is transmitted over NFC using IPv6 over           
Low-Power Wireless Personal Area Network (6LoWPAN) techniques.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            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.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9428" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2023 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) 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 Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions-and-terminology">Conventions and Terminology</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-overview-of-nfc-technology">Overview of NFC Technology</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2">
              <li pn="section-toc.1-1.3.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-peer-to-peer-mode-of-nfc">Peer-to-Peer Mode of NFC</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.2">
                <t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-protocol-stack-of-nfc">Protocol Stack of NFC</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.3">
                <t indent="0" pn="section-toc.1-1.3.2.3.1"><xref derivedContent="3.3" format="counter" sectionFormat="of" target="section-3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-nfc-enabled-device-addressi">NFC-Enabled Device Addressing</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.4">
                <t indent="0" pn="section-toc.1-1.3.2.4.1"><xref derivedContent="3.4" format="counter" sectionFormat="of" target="section-3.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-mtu-of-nfc-link-layer">MTU of NFC Link Layer</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-specification-of-ipv6-over-">Specification of IPv6 over NFC</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-protocol-stack">Protocol Stack</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.2">
                <t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-stateless-address-autoconfi">Stateless Address Autoconfiguration</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.3">
                <t indent="0" pn="section-toc.1-1.4.2.3.1"><xref derivedContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-ipv6-link-local-address">IPv6 Link-Local Address</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.4">
                <t indent="0" pn="section-toc.1-1.4.2.4.1"><xref derivedContent="4.4" format="counter" sectionFormat="of" target="section-4.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-neighbor-discovery">Neighbor Discovery</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.5">
                <t indent="0" pn="section-toc.1-1.4.2.5.1"><xref derivedContent="4.5" format="counter" sectionFormat="of" target="section-4.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-dispatch-header">Dispatch Header</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.6">
                <t indent="0" pn="section-toc.1-1.4.2.6.1"><xref derivedContent="4.6" format="counter" sectionFormat="of" target="section-4.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-header-compression">Header Compression</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.7">
                <t indent="0" pn="section-toc.1-1.4.2.7.1"><xref derivedContent="4.7" format="counter" sectionFormat="of" target="section-4.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-fragmentation-and-reassembl">Fragmentation and Reassembly Considerations</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.8">
                <t indent="0" pn="section-toc.1-1.4.2.8.1"><xref derivedContent="4.8" format="counter" sectionFormat="of" target="section-4.8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-unicast-and-multicast-addre">Unicast and Multicast Address Mapping</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-internet-connectivity-scena">Internet Connectivity Scenarios</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
              <li pn="section-toc.1-1.5.2.1">
                <t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-nfc-enabled-device-network-">NFC-Enabled Device Network Connected to the Internet</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.2">
                <t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-isolated-nfc-enabled-device">Isolated NFC-Enabled Device Network</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.8.2">
              <li pn="section-toc.1-1.8.2.1">
                <t indent="0" pn="section-toc.1-1.8.2.1.1"><xref derivedContent="8.1" format="counter" sectionFormat="of" target="section-8.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.2">
                <t indent="0" pn="section-toc.1-1.8.2.2.1"><xref derivedContent="8.2" format="counter" sectionFormat="of" target="section-8.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">NFC is a set of short-range wireless technologies, typically requiring a distance between a sender and receiver of 10 cm or less. NFC operates at 13.56 MHz and at rates ranging from 106 kbps to 424 kbps, as per the ISO/IEC 18000-3 air interface <xref target="ECMA-340" format="default" sectionFormat="of" derivedContent="ECMA-340"/>. NFC builds upon RFID systems by allowing two-way communication between endpoints. NFC always involves an initiator and a target; the initiator actively generates a radio frequency (RF) field that can power a passive target. This enables NFC targets to take very simple form factors, such as tags, stickers, key fobs, or cards, while avoiding the need for batteries. NFC peer-to-peer communication is possible, provided that both devices are powered.</t>
      <t indent="0" pn="section-1-2">NFC has a very short transmission range of 10 cm or less; thus, the other hidden NFC devices outside of that range cannot receive NFC signals. Therefore, NFC is often regarded as a secure communications technology.</t>
      <t indent="0" pn="section-1-3">In order to benefit from Internet connectivity, it is desirable for NFC-enabled devices to support IPv6 because of its large address space and the availability of tools for unattended operation, along with other advantages. This document specifies how IPv6 is supported over NFC by using 6LoWPAN techniques <xref target="RFC4944" format="default" sectionFormat="of" derivedContent="RFC4944"/> <xref target="RFC6282" format="default" sectionFormat="of" derivedContent="RFC6282"/> <xref target="RFC6775" format="default" sectionFormat="of" derivedContent="RFC6775"/>. 6LoWPAN is suitable, considering that it was designed to support IPv6 over IEEE 802.15.4 networks <xref target="IEEE802.15.4" format="default" sectionFormat="of" derivedContent="IEEE802.15.4"/> and some of the characteristics of the latter are similar to those of NFC.</t>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-conventions-and-terminology">Conventions and Terminology</name>
      <t indent="0" pn="section-2-1">
    The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
    described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> 
    when, and only when, they appear in all capitals, as shown here.
      </t>
      <t indent="0" pn="section-2-2">This specification requires readers to be familiar with all the terms and concepts that are discussed in "IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals" <xref target="RFC4919" format="default" sectionFormat="of" derivedContent="RFC4919"/>, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks" <xref target="RFC4944" format="default" sectionFormat="of" derivedContent="RFC4944"/>, and "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) <xref target="RFC6775" format="default" sectionFormat="of" derivedContent="RFC6775"/>.</t>
      <dl newline="true" spacing="normal" indent="3" pn="section-2-3">
        <dt pn="section-2-3.1">6LoWPAN Node (6LN):</dt>
        <dd pn="section-2-3.2">A 6LoWPAN node is any host or router participating in a LoWPAN. This term is used when referring to situations in which either a host or router can play the role described.</dd>
        <dt pn="section-2-3.3">6LoWPAN Router (6LR):</dt>
        <dd pn="section-2-3.4">An intermediate router in the LoWPAN that is able to send and receive Router Advertisements (RAs) and Router Solicitations (RSs), as well as forward and route IPv6 packets.  6LoWPAN routers are present only in route-over topologies.</dd>
        <dt pn="section-2-3.5">6LoWPAN Border Router (6LBR):</dt>
        <dd pn="section-2-3.6">A border router located at the junction of separate 6LoWPAN networks or between a 6LoWPAN network and another IP network. There may be one or more 6LBRs at the 6LoWPAN network boundary. A 6LBR is the responsible authority for IPv6 prefix propagation for the 6LoWPAN network it is serving.  An isolated LoWPAN also contains a 6LBR in the network that provides the prefix(es) for the isolated network.</dd>
      </dl>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-overview-of-nfc-technology">Overview of NFC Technology</name>
      <t indent="0" pn="section-3-1">This section presents an overview of NFC, focusing on the characteristics of NFC that are most relevant for supporting IPv6.</t>
      <t indent="0" pn="section-3-2">NFC enables a simple, two-way interaction between two devices, allowing users to perform contactless transactions, access digital content, and connect electronic devices with a single touch. NFC utilizes key elements in existing standards for contactless card technology, such as ISO/IEC 14443 A&amp;B and JIS-X 6319-4. NFC allows devices to share information at a distance up to 10 cm with a maximum physical layer bit rate of 424 kbps. </t>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-3.1">
        <name slugifiedName="name-peer-to-peer-mode-of-nfc">Peer-to-Peer Mode of NFC</name>
        <t indent="0" pn="section-3.1-1">NFC defines three modes of operation: card emulation, peer-to-peer, and reader/writer. Only the peer-to-peer mode allows two NFC-enabled devices to communicate with each other to exchange information bidirectionally. The other two modes do not support two-way communication between two devices. Therefore, the peer-to-peer mode <bcp14>MUST</bcp14> be used for IPv6 over NFC.</t>
      </section>
      <section anchor="protocol-stack-sec" numbered="true" toc="include" removeInRFC="false" pn="section-3.2">
        <name slugifiedName="name-protocol-stack-of-nfc">Protocol Stack of NFC</name>
        <t indent="0" pn="section-3.2-1">NFC defines a protocol stack for the peer-to-peer mode (<xref target="protocol-stack-fig" format="default" sectionFormat="of" derivedContent="Figure 1"/>). The peer-to-peer mode is offered by the Activities Digital Protocol at the NFC Physical Layer. The NFC Logical Link Layer comprises the Logical Link Control Protocol (LLCP), and when IPv6 is used over NFC, it also includes an IPv6-LLCP Binding. IPv6 and its underlying adaptation layer (i.e., IPv6-over-NFC Adaptation Layer) are placed directly on the top of the IPv6-LLCP Binding. 
An IPv6 datagram is transmitted by the LLCP with guaranteed delivery and two-way transmission of information between the peer devices.</t>
        <figure anchor="protocol-stack-fig" align="left" suppress-title="false" pn="figure-1">
          <name slugifiedName="name-protocol-stack-of-nfc-2">Protocol Stack of NFC</name>
          <artwork align="center" name="" type="" alt="" pn="section-3.2-2.1">
+----------------------------------------+ - - - - - - - - -
|      Logical Link Control Protocol     |   NFC Logical
|                 (LLCP)                 |   Link Layer
+----------------------------------------+ - - - - - - - - -
|               Activities               |         
|            Digital Protocol            |   NFC Physical
+----------------------------------------+   Layer
|               RF Analog                |         
+----------------------------------------+ - - - - - - - - -
</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-3.2-3"/>
        <t indent="0" pn="section-3.2-4">The LLCP consists of Logical Link Control (LLC) and MAC Mapping. 
The MAC Mapping integrates an existing radio frequency (RF) protocol into the LLCP architecture. The LLC contains three components: Link Management, Connection-oriented Transmission, and Connectionless Transmission. 
The Link Management is responsible for serializing all connection-oriented and connectionless LLC PDU (Protocol Data Unit) exchanges; it is also responsible for the aggregation and disaggregation of small PDUs. The Connection-oriented Transmission is responsible for maintaining all connection-oriented data exchanges, including connection setup and termination. However, NFC links do not guarantee perfect wireless link quality, so some types of delay or variation in delay would be expected in any case. The Connectionless Transmission is responsible for handling 
unacknowledged data exchanges.</t>
        <t indent="0" pn="section-3.2-5">In order to send an IPv6 packet over NFC, the packet <bcp14>MUST</bcp14> be passed down to the LLCP layer of NFC and carried by an Information field in an LLCP Protocol Data Unit (I PDU). The LLCP does not support fragmentation and reassembly. For IPv6 addressing or address configuration, the LLCP <bcp14>MUST</bcp14> provide related information, such as link-layer addresses, to its upper layer. 

IPv6-LLCP Binding <bcp14>MUST</bcp14> transfer the Source Service Access Point (SSAP) and Destination Service Access Point (DSAP) values to the IPv6-over-NFC Adaptation Layer. The SSAP is an LLC address of the source NFC-enabled device with a size of 6 bits, while the DSAP is an LLC address of the destination NFC-enabled device. Thus, the SSAP is a source address and the DSAP is a destination address.</t>
        <t indent="0" pn="section-3.2-6">In addition, NFC links and hosts do not need to consider IP header bits for QoS signaling or utilize these meaningfully.</t>
      </section>
      <section anchor="nfc-addressing-sec" numbered="true" toc="include" removeInRFC="false" pn="section-3.3">
        <name slugifiedName="name-nfc-enabled-device-addressi">NFC-Enabled Device Addressing</name>
        <t indent="0" pn="section-3.3-1">According to <xref target="LLCP-1.4" format="default" sectionFormat="of" derivedContent="LLCP-1.4"/>, NFC-enabled devices have two types of 6-bit addresses (i.e., SSAP and DSAP) to identify service access points. Several service access points can be installed on an NFC device. However, the SSAP and DSAP can be used as identifiers for NFC link connections with the IPv6-over-NFC Adaptation Layer. Therefore, the SSAP can be used to generate an IPv6 Interface Identifier (IID). Address values between 00h and 0Fh of SSAP and DSAP are reserved for identifying the well-known service access points that are defined in the NFC Forum Assigned Numbers Register. Address values between 10h and 1Fh are assigned by the local LLC to services registered by a local service environment. In addition, address values between 0x2 and 0x3f are assigned by the local LLC as a result of an upper-layer service request. Therefore, the address values between 0x2 and 0x3f can be used for generating IPv6 IIDs.</t>
      </section>
      <section anchor="nfc-mtu-sec" numbered="true" toc="include" removeInRFC="false" pn="section-3.4">
        <name slugifiedName="name-mtu-of-nfc-link-layer">MTU of NFC Link Layer</name>
        <t indent="0" pn="section-3.4-1">As mentioned in <xref target="protocol-stack-sec" format="default" sectionFormat="of" derivedContent="Section 3.2"/>, when an IPv6 packet is transmitted, the packet <bcp14>MUST</bcp14> be passed down to LLCP of NFC and transported to an I PDU of LLCP of the NFC-enabled peer device.</t>
        <t indent="0" pn="section-3.4-2">The Information field of an I PDU contains a single service data unit. The maximum number of octets in the Information field is determined by the Maximum Information Unit (MIU) for the data link connection. The default value of the MIU for I PDUs is 128 octets. The local and remote LLCs each establish and maintain distinct MIU values for each data link connection endpoint. Also, an LLC may announce a larger MIU for a data link connection by transmitting an optional Maximum Information Unit Extension (MIUX) parameter within the Information field. If no MIUX parameter is transmitted, the MIU value is 128 bytes. Otherwise, the MTU size in NFC LLCP <bcp14>MUST</bcp14> be calculated from the MIU value as follows: </t>
        <artwork align="center" name="" type="" alt="" pn="section-3.4-3">
MTU = MIU = 128 + MIUX
</artwork>
        <t indent="0" pn="section-3.4-4">According to <xref target="LLCP-1.4" format="default" sectionFormat="of" derivedContent="LLCP-1.4"/>, <xref target="nfc-format-miux-fig" format="default" sectionFormat="of" derivedContent="Figure 2"/> shows an example of the MIUX parameter TLV. The Type and Length fields of the MIUX parameter TLV have each a size of 1 byte. The size of the TLV Value field is 2 bytes.</t>
        <figure anchor="nfc-format-miux-fig" align="left" suppress-title="false" pn="figure-2">
          <name slugifiedName="name-example-of-miux-parameter-t">Example of MIUX Parameter TLV</name>
          <artwork align="center" name="" type="" alt="" pn="section-3.4-5.1">
 0          0          1     2         3
 0          8          6     1         1
+----------+----------+-----+-----------+
|   Type   |  Length  |      Value      |
+----------+----------+-----+-----------+
|   0x02   |   0x02   | 0x0 |   0x480   |
+----------+----------+-----+-----------+
</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-3.4-6"/>
        <t indent="0" pn="section-3.4-7">
When the MIUX parameter is used, the TLV Type field is 0x02 and the TLV Length field is 0x02. The MIUX parameter is encoded into the least significant 11 bits of the TLV Value field. The unused bits in the TLV Value field are set to zero by the sender and ignored by the receiver. The maximum possible value of the TLV Value field is 0x7FF, and the maximum size of the LLCP MTU is 2175 bytes. As per the present specification <xref target="LLCP-1.4" format="default" sectionFormat="of" derivedContent="LLCP-1.4"/>, the MIUX value <bcp14>MUST</bcp14> be 0x480 to support the IPv6 MTU requirement (1280 bytes) <xref target="RFC8200" format="default" sectionFormat="of" derivedContent="RFC8200"/>.</t>
      </section>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-specification-of-ipv6-over-">Specification of IPv6 over NFC</name>
      <t indent="0" pn="section-4-1">NFC technology has requirements owing to low power consumption and allowed protocol overhead. 6LoWPAN standards <xref target="RFC4944" format="default" sectionFormat="of" derivedContent="RFC4944"/>
        <xref target="RFC6775" format="default" sectionFormat="of" derivedContent="RFC6775"/> <xref target="RFC6282" format="default" sectionFormat="of" derivedContent="RFC6282"/> provide useful functionality for reducing the overhead of IPv6 over NFC. This functionality consists of link-local IPv6 addresses and stateless IPv6 address autoconfiguration (see Sections <xref target="addr-conf-sec" format="counter" sectionFormat="of" derivedContent="4.2"/> and <xref target="link-local-addr-sec" format="counter" sectionFormat="of" derivedContent="4.3"/>), Neighbor Discovery (see <xref target="nd-sec" format="default" sectionFormat="of" derivedContent="Section 4.4"/>), and header compression (see <xref target="hc-sec" format="default" sectionFormat="of" derivedContent="Section 4.6"/>).</t>
      <section anchor="IPv6-over-NFC-protocol-stack-sec" numbered="true" toc="include" removeInRFC="false" pn="section-4.1">
        <name slugifiedName="name-protocol-stack">Protocol Stack</name>
        <t indent="0" pn="section-4.1-1"> <xref target="IPv6-over-NFC-protocol-stack-fig" format="default" sectionFormat="of" derivedContent="Figure 3"/> illustrates the IPv6-over-NFC protocol stack.  Upper-layer protocols can be transport-layer protocols (e.g., TCP and UDP), application-layer protocols, and other protocols capable of running on top of IPv6. </t>
        <figure anchor="IPv6-over-NFC-protocol-stack-fig" align="left" suppress-title="false" pn="figure-3">
          <name slugifiedName="name-protocol-stack-for-ipv6-ove">Protocol Stack for IPv6 over NFC</name>
          <artwork align="center" name="" type="" alt="" pn="section-4.1-2.1">
+----------------------------------------+
|         Upper-Layer Protocols          |
+----------------------------------------+
|                 IPv6                   |
+----------------------------------------+
|   Adaptation Layer for IPv6 over NFC   |
+----------------------------------------+
|          NFC Logical Link Layer        |
+----------------------------------------+
|           NFC Physical Layer           |
+----------------------------------------+
</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-4.1-3"/>
        <t indent="0" pn="section-4.1-4">  The Adaptation Layer for IPv6 over NFC supports Neighbor Discovery, stateless address autoconfiguration, header compression, and fragmentation and reassembly, based on 6LoWPAN. Note that 6LoWPAN header compression <xref target="RFC6282" format="default" sectionFormat="of" derivedContent="RFC6282"/> does not define header compression for TCP. 
The latter can still be supported by IPv6 over NFC, albeit without the performance optimization of header compression.
        </t>
      </section>
      <section anchor="addr-conf-sec" numbered="true" toc="include" removeInRFC="false" pn="section-4.2">
        <name slugifiedName="name-stateless-address-autoconfi">Stateless Address Autoconfiguration</name>
        <t indent="0" pn="section-4.2-1">An NFC-enabled device performs stateless address autoconfiguration per <xref target="RFC4862" format="default" sectionFormat="of" derivedContent="RFC4862"/>.  A 64-bit IID for an NFC interface is formed by utilizing the 6-bit NFC SSAP (see <xref target="nfc-addressing-sec" format="default" sectionFormat="of" derivedContent="Section 3.3"/>). In the viewpoint of address configuration, such an IID should guarantee a stable IPv6 address during the course of a single connection because each data link connection is uniquely identified by the pair of DSAP and SSAP included in the header of each LLC PDU in NFC.</t>
        <t indent="0" pn="section-4.2-2">Following the guidance of <xref target="RFC7136" format="default" sectionFormat="of" derivedContent="RFC7136"/>, IIDs of all unicast addresses for NFC-enabled devices are 64 bits long and constructed by using the generation algorithm of random identifiers (RIDs) that are stable <xref target="RFC7217" format="default" sectionFormat="of" derivedContent="RFC7217"/>.</t>
        <t indent="0" pn="section-4.2-3">The RID is an output created by the F() algorithm with input parameters. One of the parameters is Net_Iface, and the NFC Link-Layer Address (i.e., the SSAP) <bcp14>MUST</bcp14> be a source of the Net_Iface parameter. The 6-bit address of the SSAP of NFC is short and can easily be targeted by attacks from a third party (e.g., address scanning). The F() algorithm with SHA-256 can provide secured and stable IIDs for NFC-enabled devices.  
In addition, an optional parameter, Network_ID, is used to increase the randomness of the generated IID with the NFC Link-Layer Address (i.e., SSAP). The secret key <bcp14>SHOULD</bcp14> be at least 128 bits.  It <bcp14>MUST</bcp14> be initialized to a pseudorandom number <xref target="RFC4086" format="default" sectionFormat="of" derivedContent="RFC4086"/>.</t>
      </section>
      <section anchor="link-local-addr-sec" numbered="true" toc="include" removeInRFC="false" pn="section-4.3">
        <name slugifiedName="name-ipv6-link-local-address">IPv6 Link-Local Address</name>
        <t indent="0" pn="section-4.3-1">The IPv6 Link-Local Address for an NFC-enabled device is formed by appending the IID to the prefix fe80::/64, as depicted in <xref target="IPv6-over-NFC-link-addr-fig" format="default" sectionFormat="of" derivedContent="Figure 4"/>.</t>
        <figure anchor="IPv6-over-NFC-link-addr-fig" align="left" suppress-title="false" pn="figure-4">
          <name slugifiedName="name-ipv6-link-local-address-in-">IPv6 Link-Local Address in NFC</name>
          <artwork align="center" name="" type="" alt="" pn="section-4.3-2.1">
 0          0                  0                          1
 0          1                  6                          2 
 0          0                  4                          7 
+----------+------------------+----------------------------+
|1111111010|       zeros      |    Interface Identifier    |
+----------+------------------+----------------------------+
.                                                          .
. &lt;- - - - - - - - - - - 128 bits - - - - - - - - - - - -&gt; .
.                                                          .
</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-4.3-3"/>
        <t indent="0" pn="section-4.3-4">The "Interface Identifier" can be a random and stable IID.</t>
      </section>
      <section anchor="nd-sec" numbered="true" toc="include" removeInRFC="false" pn="section-4.4">
        <name slugifiedName="name-neighbor-discovery">Neighbor Discovery</name>
        <t indent="0" pn="section-4.4-1">Neighbor Discovery Optimization for 6LoWPANs <xref target="RFC6775" format="default" sectionFormat="of" derivedContent="RFC6775"/> describes the Neighbor Discovery approach in several 6LoWPAN topologies, such as mesh topology. NFC supports  mesh topologies, but most applications would use a simple multi-hop network topology or directly connected peer-to-peer network because the NFC RF range is very short.</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.4-2">
          <li pn="section-4.4-2.1">	When an NFC 6LN is directly connected to a 6LBR, the 6LN <bcp14>MUST</bcp14> register its address with the 6LBR by sending Neighbor Solicitation (NS) with the Extended Address Registration Option (EARO) <xref target="RFC8505" format="default" sectionFormat="of" derivedContent="RFC8505"/>; then Neighbor Advertisement (NA) is started. When the 6LN and 6LBR are linked to each other, an address is assigned to the 6LN. In this process, Duplicate Address Detection (DAD) is not required.</li>
          <li pn="section-4.4-2.2">	
When two or more NFC 6LNs are connected to the 6LBR, two cases of topologies can be formed. One is a multi-hop topology, and the other is a star topology based on the 6LBR. In the multi-hop topology, 6LNs that have two or more links with neighbor nodes may act as routers. In star topology, any of 6LNs can be a router.</li>
          <li pn="section-4.4-2.3">For receiving RSs and RAs, the NFC 6LNs <bcp14>MUST</bcp14> follow Sections <xref target="RFC6775" section="5.3" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6775#section-5.3" derivedContent="RFC6775"/> and <xref target="RFC6775" section="5.4" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6775#section-5.4" derivedContent="RFC6775"/> of <xref target="RFC6775" format="default" sectionFormat="of" derivedContent="RFC6775"/>.</li>
          <li pn="section-4.4-2.4">When an NFC device is a 6LR or 6LBR, the NFC device <bcp14>MUST</bcp14> follow Sections <xref target="RFC6775" section="6" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6775#section-6" derivedContent="RFC6775"/> and <xref target="RFC6775" section="7" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6775#section-7" derivedContent="RFC6775"/> of <xref target="RFC6775" format="default" sectionFormat="of" derivedContent="RFC6775"/>.</li>
        </ul>
      </section>
      <section anchor="dh-sec" numbered="true" toc="include" removeInRFC="false" pn="section-4.5">
        <name slugifiedName="name-dispatch-header">Dispatch Header</name>
        <t indent="0" pn="section-4.5-1">All IPv6-over-NFC encapsulated datagrams are prefixed by an encapsulation header stack consisting of a dispatch value <xref target="IANA-6LoWPAN" format="default" sectionFormat="of" derivedContent="IANA-6LoWPAN"/>. The only sequence currently defined for IPv6 over NFC <bcp14>MUST</bcp14> be the LOWPAN_IPHC compressed IPv6 header (see <xref target="hc-sec" format="default" sectionFormat="of" derivedContent="Section 4.6"/>) followed by a payload, as depicted in  <xref target="IPv6-over-NFC-encap-format-fig" format="default" sectionFormat="of" derivedContent="Figure 5"/> and <xref target="dispatchvaluestable" format="default" sectionFormat="of" derivedContent="Table 1"/>.</t>
        <figure anchor="IPv6-over-NFC-encap-format-fig" align="left" suppress-title="false" pn="figure-5">
          <name slugifiedName="name-an-ipv6-over-nfc-encapsulat">An IPv6-over-NFC Encapsulated LOWPAN_IPHC Compressed IPv6 Datagram</name>
          <artwork align="center" name="" type="" alt="" pn="section-4.5-2.1">
+---------------+---------------+--------------+
| IPHC Dispatch |  IPHC Header  |    Payload   |
+---------------+---------------+--------------+
</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-4.5-3"/>
        <t indent="0" pn="section-4.5-4">The dispatch value (1 octet in length) is treated as an unstructured namespace. Only a single pattern is used to represent current IPv6-over-NFC functionality.</t>
        <table anchor="dispatchvaluestable" align="center" pn="table-1">
          <name slugifiedName="name-dispatch-values">Dispatch Values</name>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Pattern</th>
              <th align="left" colspan="1" rowspan="1">Header Type</th>
              <th align="left" colspan="1" rowspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">01  1xxxxx</td>
              <td align="left" colspan="1" rowspan="1">LOWPAN_IPHC</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC6282" format="default" sectionFormat="of" derivedContent="RFC6282"/> <xref target="RFC8025" format="default" sectionFormat="of" derivedContent="RFC8025"/></td>
            </tr>
          </tbody>
        </table>
        <t keepWithPrevious="true" indent="0" pn="section-4.5-6"/>
        <t indent="0" pn="section-4.5-7">Other IANA-assigned 6LoWPAN dispatch values do not apply to this specification.</t>
      </section>
      <section anchor="hc-sec" numbered="true" toc="include" removeInRFC="false" pn="section-4.6">
        <name slugifiedName="name-header-compression">Header Compression</name>
        <t indent="0" pn="section-4.6-1">Header compression as defined in <xref target="RFC6282" format="default" sectionFormat="of" derivedContent="RFC6282"/>, which specifies the compression format for IPv6 datagrams on top of IEEE 802.15.4, is <bcp14>REQUIRED</bcp14> in this document as the basis for IPv6 header compression on top of NFC. All headers <bcp14>MUST</bcp14> be compressed according to the encoding formats described in <xref target="RFC6282" format="default" sectionFormat="of" derivedContent="RFC6282"/>.  </t>
        <t indent="0" pn="section-4.6-2">Therefore, IPv6 header compression in <xref target="RFC6282" format="default" sectionFormat="of" derivedContent="RFC6282"/> <bcp14>MUST</bcp14> be implemented. Further, implementations <bcp14>MUST</bcp14> also support Generic Header Compression (GHC) as described in <xref target="RFC7400" format="default" sectionFormat="of" derivedContent="RFC7400"/>.</t>
        <t indent="0" pn="section-4.6-3">If a 16-bit address is required as a short address, it <bcp14>MUST</bcp14> be formed by padding the 6-bit NFC SSAP (NFC Link-Layer Node Address) to the left with zeros as shown in <xref target="shortaddr-fig" format="default" sectionFormat="of" derivedContent="Figure 6"/>.</t>
        <figure anchor="shortaddr-fig" align="left" suppress-title="false" pn="figure-6">
          <name slugifiedName="name-nfc-short-address-format">NFC Short Address Format</name>
          <artwork align="center" name="" type="" alt="" pn="section-4.6-4.1">
 0                   1
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Padding(all zeros)| NFC Addr. | 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-4.6-5"/>
      </section>
      <section anchor="FAR-sec" numbered="true" toc="include" removeInRFC="false" pn="section-4.7">
        <name slugifiedName="name-fragmentation-and-reassembl">Fragmentation and Reassembly Considerations</name>
        <t indent="0" pn="section-4.7-1">IPv6 over NFC <bcp14>MUST NOT</bcp14> use fragmentation and reassembly (FAR) at the adaptation layer for the payloads as discussed in <xref target="nfc-mtu-sec" format="default" sectionFormat="of" derivedContent="Section 3.4"/>. The NFC link connection for IPv6 over NFC <bcp14>MUST</bcp14> be configured with an equivalent MIU size to support the IPv6 MTU requirement (1280 bytes). To this end, the MIUX value is 0x480.</t>
        <t indent="0" pn="section-4.7-2"/>
      </section>
      <section anchor="unicasting-sec" numbered="true" toc="include" removeInRFC="false" pn="section-4.8">
        <name slugifiedName="name-unicast-and-multicast-addre">Unicast and Multicast Address Mapping</name>
        <t indent="0" pn="section-4.8-1">The address resolution procedure for mapping IPv6 non-multicast addresses into NFC Link-Layer Addresses follows the general description in Sections <xref target="RFC4861" section="4.6.1" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4861#section-4.6.1" derivedContent="RFC4861"/> and <xref target="RFC4861" section="7.2" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4861#section-7.2" derivedContent="RFC4861"/> of <xref target="RFC4861" format="default" sectionFormat="of" derivedContent="RFC4861"/>, unless otherwise specified.</t>
        <t indent="0" pn="section-4.8-2">The Source/Target Link-Layer Address option has the following form when the addresses are 6-bit NFC SSAP/DSAP (NFC Link-Layer Node Addresses).</t>
        <figure anchor="unicasting-fig" align="left" suppress-title="false" pn="figure-7">
          <name slugifiedName="name-unicast-address-mapping">Unicast Address Mapping</name>
          <artwork align="center" name="" type="" alt="" pn="section-4.8-3.1">
 0                   1
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|      Type     |   Length=1    | 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                               | 
+-     Padding (all zeros)     -+ 
|                               | 
+-                  +-+-+-+-+-+-+ 
|                   | NFC Addr. | 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-4.8-4"/>
        <dl spacing="normal" newline="true" indent="3" pn="section-4.8-5">
          <dt pn="section-4.8-5.1">Option fields:</dt>
          <dd pn="section-4.8-5.2">
            <dl spacing="normal" newline="true" indent="3" pn="section-4.8-5.2.1">
              <dt pn="section-4.8-5.2.1.1">Type:</dt>
              <dd pn="section-4.8-5.2.1.2">
                <dl newline="false" spacing="normal" indent="3" pn="section-4.8-5.2.1.2.1">
                  <dt pn="section-4.8-5.2.1.2.1.1">1:</dt>
                  <dd pn="section-4.8-5.2.1.2.1.2">This is for the Source Link-Layer Address.</dd>
                  <dt pn="section-4.8-5.2.1.2.1.3">2:</dt>
                  <dd pn="section-4.8-5.2.1.2.1.4">This is for the  Target Link-Layer Address.</dd>
                </dl>
              </dd>
              <dt pn="section-4.8-5.2.1.3">Length:</dt>
              <dd pn="section-4.8-5.2.1.4">This is the length of this option (including the Type and Length fields) in units of 8 bits.  The value of this field is 1 for 6-bit NFC node addresses.</dd>
              <dt pn="section-4.8-5.2.1.5">NFC address:</dt>
              <dd pn="section-4.8-5.2.1.6">The 6-bit address in canonical bit order. This is the unicast address the interface currently responds to.</dd>
            </dl>
          </dd>
        </dl>
        <t indent="0" pn="section-4.8-6"> The NFC Link Layer does not support multicast. Therefore, packets are always transmitted 
unicast between two NFC-enabled devices. Even in the case where a 6LBR is attached to multiple 6LNs, 
the 6LBR cannot multicast to all the connected 6LNs. If the 6LBR needs to send a multicast packet to all its 6LNs, it has to replicate the packet and unicast it on each link. However, this is not energy-efficient; the central node, which is battery-powered, must take particular care of power consumption. To further conserve power, the 6LBR <bcp14>MUST</bcp14> keep track of multicast listeners at NFC link-level granularity (not at subnet granularity), and it <bcp14>MUST NOT</bcp14> forward multicast packets to  6LNs that have not registered as listeners for multicast groups the packets belong to. In the opposite direction, a 6LN always has to send packets to or through the 6LBR.  Hence, when a 6LN needs to transmit an IPv6 multicast packet, the 6LN will unicast the corresponding NFC packet to the 6LBR.</t>
      </section>
    </section>
    <section anchor="connection-scenario-sec" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-internet-connectivity-scena">Internet Connectivity Scenarios</name>
      <section anchor="internet-conn-scenario-sec" numbered="true" toc="include" removeInRFC="false" pn="section-5.1">
        <name slugifiedName="name-nfc-enabled-device-network-">NFC-Enabled Device Network Connected to the Internet</name>
        <t indent="0" pn="section-5.1-1"><xref target="IPv6-over-NFC-Internet-conn-fig" format="default" sectionFormat="of" derivedContent="Figure 8"/> illustrates an example of an NFC-enabled device network connected to the Internet. The distance between 6LN and 6LBR is typically 10 cm or less. For example, a laptop computer that is connected to the Internet (e.g., via Wi-Fi, Ethernet, etc.) may also support NFC and act as a 6LBR. Another NFC-enabled device may run as a 6LN and communicate with the 6LBR, as long as both are within each other's range.</t>
        <figure anchor="IPv6-over-NFC-Internet-conn-fig" align="left" suppress-title="false" pn="figure-8">
          <name slugifiedName="name-nfc-enabled-device-network-c">NFC-Enabled Device Network Connected to the Internet</name>
          <artwork align="center" name="" type="" alt="" pn="section-5.1-2.1">
         NFC link   
6LN ------------------- 6LBR -------( Internet )--------- CN 
 .                        .                                .
 . &lt;- - - - Subnet - - -&gt; . &lt; - - - IPv6 connection - - -&gt; . 
 .                        .         to the Internet        .
</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-5.1-3"/>
        <t indent="0" pn="section-5.1-4">Two or more 6LNs may be connected with a 6LBR, but each connection uses a different IPv6 prefix. The 6LBR is acting as a router and forwarding packets between 6LNs and the Internet. Also, the 6LBR <bcp14>MUST</bcp14> ensure address collisions do not occur because the 6LNs are connected to the 6LBR like a start topology, so the 6LBR checks whether or not IPv6 addresses are duplicates, since 6LNs need to register their addresses with the 6LBR.</t>
      </section>
      <section anchor="adhoc-conn-scenario-sec" numbered="true" toc="include" removeInRFC="false" pn="section-5.2">
        <name slugifiedName="name-isolated-nfc-enabled-device">Isolated NFC-Enabled Device Network</name>
        <t indent="0" pn="section-5.2-1">In some scenarios, the NFC-enabled device network may permanently be a simple isolated network as shown in <xref target="IPv6-over-NFC-isolated-net-fig" format="default" sectionFormat="of" derivedContent="Figure 9"/>.</t>
        <figure anchor="IPv6-over-NFC-isolated-net-fig" align="left" suppress-title="false" pn="figure-9">
          <name slugifiedName="name-isolated-nfc-enabled-device-">Isolated NFC-Enabled Device Network</name>
          <artwork align="center" name="" type="" alt="" pn="section-5.2-2.1">
                           6LN                        6LN - - - - -
                            |                          |      .
                NFC link - &gt;|              NFC link - &gt;|      .
                            |                          |      .
6LN ---------------------- 6LR ---------------------- 6LR   Subnet
 .         NFC link                    NFC link        |      .
 .                                                     |      .
 .                                         NFC link - &gt;|      .
 .                                                    6LN - - - - -
 .                                                     .
 . &lt; - - - - - - - - - -  Subnet - - - - - - - - - - &gt; .
</artwork>
        </figure>
        <t keepWithPrevious="true" indent="0" pn="section-5.2-3"/>
        <t indent="0" pn="section-5.2-4">In multihop (i.e., more complex) topologies, the 6LR can also do the same task. DAD requires the extensions for multihop networks, such as the ones in <xref target="RFC6775" format="default" sectionFormat="of" derivedContent="RFC6775"/>.</t>
      </section>
    </section>
    <section anchor="IANA" numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-6-1">This document has no IANA actions.</t>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-7">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-7-1">Neighbor Discovery in unencrypted wireless device networks may be susceptible to various threats as described in <xref target="RFC3756" format="default" sectionFormat="of" derivedContent="RFC3756"/>.</t>
      <t indent="0" pn="section-7-2">Per the NFC Logical Link Control Protocol <xref target="LLCP-1.4" format="default" sectionFormat="of" derivedContent="LLCP-1.4"/>:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-7-3">
        <li pn="section-7-3.1">LLCP of NFC provides protection of user data to ensure confidentiality of communications. The confidentiality mechanism involves the encryption of user service data with a secret key that has been established during link activation.</li>
        <li pn="section-7-3.2">LLCP of NFC has two modes (i.e., ad hoc mode and authenticated mode) for secure data transfer. Ad hoc secure data transfer can be established between two communication parties without any prior knowledge of the communication partner. Ad hoc secure data transfer can be vulnerable to on-path attacks. Authenticated secure data transfer provides protection against on-path attacks. In the initial bonding step, the two communicating parties store a shared secret along with a Bonding Identifier.</li>
        <li pn="section-7-3.3">For all subsequent interactions, the communicating parties reuse the shared secret and compute only the unique encryption key for that session. Secure data transfer is based on the cryptographic algorithms defined in the NFC Authentication Protocol <xref target="NAP-1.0" format="default" sectionFormat="of" derivedContent="NAP-1.0"/>.</li>
      </ul>
      <t indent="0" pn="section-7-4">Furthermore, NFC is considered by many to offer intrinsic security properties due to its short link range. When IIDs are generated, devices and users are required to consider mitigating various threats, such as correlation of activities over time, location tracking, device-specific vulnerability exploitation, and address scanning. However, IPv6 over NFC uses an RID <xref target="RFC7217" format="default" sectionFormat="of" derivedContent="RFC7217"/> as an IPv6 IID; NFC applications use short-lived connections and a different address is used for each connection where the latter is of extremely short duration.</t>
    </section>
  </middle>
  <back>
    <references pn="section-8">
      <name slugifiedName="name-references">References</name>
      <references pn="section-8.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="LLCP-1.4" target="https://nfc-forum.org/build/specifications" quoteTitle="true" derivedAnchor="LLCP-1.4">
          <front>
            <title>Logical Link Control Protocol Technical Specification</title>
            <author>
              <organization showOnFrontPage="true">NFC Forum</organization>
            </author>
            <date month="December" year="2022"/>
          </front>
          <refcontent>Version 1.4</refcontent>
        </reference>
        <reference anchor="NAP-1.0" target="https://nfc-forum.org/build/specifications" quoteTitle="true" derivedAnchor="NAP-1.0">
          <front>
            <title>NFC Authentication Protocol Technical Specification</title>
            <author>
              <organization showOnFrontPage="true">NFC Forum</organization>
            </author>
            <date month="December" year="2022"/>
          </front>
          <refcontent>Version 1.0</refcontent>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t indent="0">In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC4086" target="https://www.rfc-editor.org/info/rfc4086" quoteTitle="true" derivedAnchor="RFC4086">
          <front>
            <title>Randomness Requirements for Security</title>
            <author fullname="D. Eastlake 3rd" initials="D." surname="Eastlake 3rd"/>
            <author fullname="J. Schiller" initials="J." surname="Schiller"/>
            <author fullname="S. Crocker" initials="S." surname="Crocker"/>
            <date month="June" year="2005"/>
            <abstract>
              <t indent="0">Security systems are built on strong cryptographic algorithms that foil pattern analysis attempts. However, the security of these systems is dependent on generating secret quantities for passwords, cryptographic keys, and similar quantities. The use of pseudo-random processes to generate secret quantities can result in pseudo-security. A sophisticated attacker may find it easier to reproduce the environment that produced the secret quantities and to search the resulting small set of possibilities than to locate the quantities in the whole of the potential number space.</t>
              <t indent="0">Choosing random quantities to foil a resourceful and motivated adversary is surprisingly difficult. This document points out many pitfalls in using poor entropy sources or traditional pseudo-random number generation techniques for generating such quantities. It recommends the use of truly random hardware techniques and shows that the existing hardware on many systems can be used for this purpose. It provides suggestions to ameliorate the problem when a hardware solution is not available, and it gives examples of how large such quantities need to be for some applications. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="106"/>
          <seriesInfo name="RFC" value="4086"/>
          <seriesInfo name="DOI" value="10.17487/RFC4086"/>
        </reference>
        <reference anchor="RFC4861" target="https://www.rfc-editor.org/info/rfc4861" quoteTitle="true" derivedAnchor="RFC4861">
          <front>
            <title>Neighbor Discovery for IP version 6 (IPv6)</title>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
            <author fullname="W. Simpson" initials="W." surname="Simpson"/>
            <author fullname="H. Soliman" initials="H." surname="Soliman"/>
            <date month="September" year="2007"/>
            <abstract>
              <t indent="0">This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4861"/>
          <seriesInfo name="DOI" value="10.17487/RFC4861"/>
        </reference>
        <reference anchor="RFC4862" target="https://www.rfc-editor.org/info/rfc4862" quoteTitle="true" derivedAnchor="RFC4862">
          <front>
            <title>IPv6 Stateless Address Autoconfiguration</title>
            <author fullname="S. Thomson" initials="S." surname="Thomson"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <author fullname="T. Jinmei" initials="T." surname="Jinmei"/>
            <date month="September" year="2007"/>
            <abstract>
              <t indent="0">This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4862"/>
          <seriesInfo name="DOI" value="10.17487/RFC4862"/>
        </reference>
        <reference anchor="RFC4919" target="https://www.rfc-editor.org/info/rfc4919" quoteTitle="true" derivedAnchor="RFC4919">
          <front>
            <title>IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals</title>
            <author fullname="N. Kushalnagar" initials="N." surname="Kushalnagar"/>
            <author fullname="G. Montenegro" initials="G." surname="Montenegro"/>
            <author fullname="C. Schumacher" initials="C." surname="Schumacher"/>
            <date month="August" year="2007"/>
            <abstract>
              <t indent="0">This document describes the assumptions, problem statement, and goals for transmitting IP over IEEE 802.15.4 networks. The set of goals enumerated in this document form an initial set only. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4919"/>
          <seriesInfo name="DOI" value="10.17487/RFC4919"/>
        </reference>
        <reference anchor="RFC4944" target="https://www.rfc-editor.org/info/rfc4944" quoteTitle="true" derivedAnchor="RFC4944">
          <front>
            <title>Transmission of IPv6 Packets over IEEE 802.15.4 Networks</title>
            <author fullname="G. Montenegro" initials="G." surname="Montenegro"/>
            <author fullname="N. Kushalnagar" initials="N." surname="Kushalnagar"/>
            <author fullname="J. Hui" initials="J." surname="Hui"/>
            <author fullname="D. Culler" initials="D." surname="Culler"/>
            <date month="September" year="2007"/>
            <abstract>
              <t indent="0">This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4944"/>
          <seriesInfo name="DOI" value="10.17487/RFC4944"/>
        </reference>
        <reference anchor="RFC6282" target="https://www.rfc-editor.org/info/rfc6282" quoteTitle="true" derivedAnchor="RFC6282">
          <front>
            <title>Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks</title>
            <author fullname="J. Hui" initials="J." role="editor" surname="Hui"/>
            <author fullname="P. Thubert" initials="P." surname="Thubert"/>
            <date month="September" year="2011"/>
            <abstract>
              <t indent="0">This document updates RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks". This document specifies an IPv6 header compression format for IPv6 packet delivery in Low Power Wireless Personal Area Networks (6LoWPANs). The compression format relies on shared context to allow compression of arbitrary prefixes. How the information is maintained in that shared context is out of scope. This document specifies compression of multicast addresses and a framework for compressing next headers. UDP header compression is specified within this framework. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6282"/>
          <seriesInfo name="DOI" value="10.17487/RFC6282"/>
        </reference>
        <reference anchor="RFC6775" target="https://www.rfc-editor.org/info/rfc6775" quoteTitle="true" derivedAnchor="RFC6775">
          <front>
            <title>Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)</title>
            <author fullname="Z. Shelby" initials="Z." role="editor" surname="Shelby"/>
            <author fullname="S. Chakrabarti" initials="S." surname="Chakrabarti"/>
            <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="November" year="2012"/>
            <abstract>
              <t indent="0">The IETF work in IPv6 over Low-power Wireless Personal Area Network (6LoWPAN) defines 6LoWPANs such as IEEE 802.15.4. This and other similar link technologies have limited or no usage of multicast signaling due to energy conservation. In addition, the wireless network may not strictly follow the traditional concept of IP subnets and IP links. IPv6 Neighbor Discovery was not designed for non- transitive wireless links, as its reliance on the traditional IPv6 link concept and its heavy use of multicast make it inefficient and sometimes impractical in a low-power and lossy network. This document describes simple optimizations to IPv6 Neighbor Discovery, its addressing mechanisms, and duplicate address detection for Low- power Wireless Personal Area Networks and similar networks. The document thus updates RFC 4944 to specify the use of the optimizations defined here. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6775"/>
          <seriesInfo name="DOI" value="10.17487/RFC6775"/>
        </reference>
        <reference anchor="RFC7136" target="https://www.rfc-editor.org/info/rfc7136" quoteTitle="true" derivedAnchor="RFC7136">
          <front>
            <title>Significance of IPv6 Interface Identifiers</title>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
            <author fullname="S. Jiang" initials="S." surname="Jiang"/>
            <date month="February" year="2014"/>
            <abstract>
              <t indent="0">The IPv6 addressing architecture includes a unicast interface identifier that is used in the creation of many IPv6 addresses. Interface identifiers are formed by a variety of methods. This document clarifies that the bits in an interface identifier have no meaning and that the entire identifier should be treated as an opaque value. In particular, RFC 4291 defines a method by which the Universal and Group bits of an IEEE link-layer address are mapped into an IPv6 unicast interface identifier. This document clarifies that those two bits are significant only in the process of deriving interface identifiers from an IEEE link-layer address, and it updates RFC 4291 accordingly.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7136"/>
          <seriesInfo name="DOI" value="10.17487/RFC7136"/>
        </reference>
        <reference anchor="RFC7217" target="https://www.rfc-editor.org/info/rfc7217" quoteTitle="true" derivedAnchor="RFC7217">
          <front>
            <title>A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)</title>
            <author fullname="F. Gont" initials="F." surname="Gont"/>
            <date month="April" year="2014"/>
            <abstract>
              <t indent="0">This document specifies a method for generating IPv6 Interface Identifiers to be used with IPv6 Stateless Address Autoconfiguration (SLAAC), such that an IPv6 address configured using this method is stable within each subnet, but the corresponding Interface Identifier changes when the host moves from one network to another. This method is meant to be an alternative to generating Interface Identifiers based on hardware addresses (e.g., IEEE LAN Media Access Control (MAC) addresses), such that the benefits of stable addresses can be achieved without sacrificing the security and privacy of users. The method specified in this document applies to all prefixes a host may be employing, including link-local, global, and unique-local prefixes (and their corresponding addresses).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7217"/>
          <seriesInfo name="DOI" value="10.17487/RFC7217"/>
        </reference>
        <reference anchor="RFC7400" target="https://www.rfc-editor.org/info/rfc7400" quoteTitle="true" derivedAnchor="RFC7400">
          <front>
            <title>6LoWPAN-GHC: Generic Header Compression for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <date month="November" year="2014"/>
            <abstract>
              <t indent="0">RFC 6282 defines header compression in 6LoWPAN packets (where "6LoWPAN" refers to "IPv6 over Low-Power Wireless Personal Area Network"). The present document specifies a simple addition that enables the compression of generic headers and header-like payloads, without a need to define a new header compression scheme for each such new header or header-like payload.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7400"/>
          <seriesInfo name="DOI" value="10.17487/RFC7400"/>
        </reference>
        <reference anchor="RFC8025" target="https://www.rfc-editor.org/info/rfc8025" quoteTitle="true" derivedAnchor="RFC8025">
          <front>
            <title>IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Paging Dispatch</title>
            <author fullname="P. Thubert" initials="P." role="editor" surname="Thubert"/>
            <author fullname="R. Cragie" initials="R." surname="Cragie"/>
            <date month="November" year="2016"/>
            <abstract>
              <t indent="0">This specification updates RFC 4944 to introduce a new context switch mechanism for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) compression, expressed in terms of Pages and signaled by a new Paging Dispatch.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8025"/>
          <seriesInfo name="DOI" value="10.17487/RFC8025"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t indent="0">RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8200" target="https://www.rfc-editor.org/info/rfc8200" quoteTitle="true" derivedAnchor="RFC8200">
          <front>
            <title>Internet Protocol, Version 6 (IPv6) Specification</title>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <date month="July" year="2017"/>
            <abstract>
              <t indent="0">This document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="86"/>
          <seriesInfo name="RFC" value="8200"/>
          <seriesInfo name="DOI" value="10.17487/RFC8200"/>
        </reference>
        <reference anchor="RFC8505" target="https://www.rfc-editor.org/info/rfc8505" quoteTitle="true" derivedAnchor="RFC8505">
          <front>
            <title>Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery</title>
            <author fullname="P. Thubert" initials="P." role="editor" surname="Thubert"/>
            <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
            <author fullname="S. Chakrabarti" initials="S." surname="Chakrabarti"/>
            <author fullname="C. Perkins" initials="C." surname="Perkins"/>
            <date month="November" year="2018"/>
            <abstract>
              <t indent="0">This specification updates RFC 6775 -- the Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery specification -- to clarify the role of the protocol as a registration technique and simplify the registration operation in 6LoWPAN routers, as well as to provide enhancements to the registration capabilities and mobility detection for different network topologies, including the Routing Registrars performing routing for host routes and/or proxy Neighbor Discovery in a low-power network.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8505"/>
          <seriesInfo name="DOI" value="10.17487/RFC8505"/>
        </reference>
      </references>
      <references pn="section-8.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="ECMA-340" target="https://www.ecma-international.org/wp-content/uploads/ECMA-340_3rd_edition_june_2013.pdf" quoteTitle="true" derivedAnchor="ECMA-340">
          <front>
            <title>Near Field Communication - Interface and Protocol (NFCIP-1)</title>
            <author>
              <organization showOnFrontPage="true">ECMA International</organization>
            </author>
            <date month="June" year="2013"/>
          </front>
          <seriesInfo name="ECMA" value="340"/>
          <refcontent>3rd Edition</refcontent>
        </reference>
        <reference anchor="IANA-6LoWPAN" target="https://www.iana.org/assignments/_6lowpan-parameters" quoteTitle="true" derivedAnchor="IANA-6LoWPAN">
          <front>
            <title>IPv6 Low Power Personal Area Network Parameters</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="IEEE802.15.4" target="https://ieeexplore.ieee.org/document/9144691" quoteTitle="true" derivedAnchor="IEEE802.15.4">
          <front>
            <title>IEEE Standard for Low-Rate Wireless Networks</title>
            <author>
              <organization showOnFrontPage="true">IEEE</organization>
            </author>
            <date month="July" year="2020"/>
          </front>
          <seriesInfo name="IEEE Std" value="802.15.4-2020"/>
          <seriesInfo name="DOI" value="10.1109/IEEESTD.2020.9144691"/>
        </reference>
        <reference anchor="RFC3756" target="https://www.rfc-editor.org/info/rfc3756" quoteTitle="true" derivedAnchor="RFC3756">
          <front>
            <title>IPv6 Neighbor Discovery (ND) Trust Models and Threats</title>
            <author fullname="P. Nikander" initials="P." role="editor" surname="Nikander"/>
            <author fullname="J. Kempf" initials="J." surname="Kempf"/>
            <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
            <date month="May" year="2004"/>
            <abstract>
              <t indent="0">The existing IETF standards specify that IPv6 Neighbor Discovery (ND) and Address Autoconfiguration mechanisms may be protected with IPsec Authentication Header (AH). However, the current specifications limit the security solutions to manual keying due to practical problems faced with automatic key management. This document specifies three different trust models and discusses the threats pertinent to IPv6 Neighbor Discovery. The purpose of this discussion is to define the requirements for Securing IPv6 Neighbor Discovery. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3756"/>
          <seriesInfo name="DOI" value="10.17487/RFC3756"/>
        </reference>
      </references>
    </references>
    <section anchor="Acknowledgements" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1">We are grateful to the members of the IETF 6lo Working Group.</t>
      <t indent="0" pn="section-appendix.a-2"><contact fullname="Michael Richardson"/>, <contact fullname="Suresh       Krishnan"/>, <contact fullname="Pascal Thubert"/>, <contact fullname="Carsten Bormann"/>, <contact fullname="Alexandru Petrescu"/>,
      <contact fullname="James Woodyatt"/>, <contact fullname="Dave Thaler"/>,
      <contact fullname="Samita Chakrabarti"/>, <contact fullname="Gabriel       Montenegro"/>, <contact fullname="Erik Kline"/>, and <contact fullname="Carles Gomez Montenegro"/> have provided valuable feedback for
      this document.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="Younghwan Choi" role="editor" initials="Y." surname="Choi">
        <organization abbrev="ETRI" showOnFrontPage="true">Electronics and Telecommunications Research Institute</organization>
        <address>
          <postal>
            <street>218 Gajeongno, Yuseung-gu</street>
            <street/>
            <city>Daejeon</city>
            <code>34129</code>
            <country>South Korea</country>
          </postal>
          <phone>+82 42 860 1429</phone>
          <email>yhc@etri.re.kr</email>
        </address>
      </author>
      <author fullname="Yong-Geun Hong" initials="Y-G." surname="Hong">
        <organization abbrev="Daejon Univ" showOnFrontPage="true">Daejon University</organization>
        <address>
          <postal>
            <street>62 Daehak-ro, Dong-gu</street>
            <city>Daejeon</city>
            <code>34520</code>
            <country>South Korea</country>
          </postal>
          <phone>+82 42 280 4841</phone>
          <email>yonggeun.hong@gmail.com</email>
        </address>
      </author>
      <author fullname="Joo-Sang Youn" initials="J-S." surname="Youn">
        <organization abbrev="Dongeui Univ" showOnFrontPage="true">DONG-EUI University</organization>
        <address>
          <postal>
            <street>176 Eomgwangno Busan_jin_gu</street>
            <city>Busan</city>
            <code>614-714</code>
            <country>South Korea</country>
          </postal>
          <phone>+82 51 890 1993</phone>
          <email>joosang.youn@gmail.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
