idnits 2.17.1 draft-hong-6lo-ipv6-over-nfc-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: All IPv6 multicast packets MUST be sent to NFC Destination Address, 0x3F (broadcast) and filtered at the IPv6 layer. When represented as a 16-bit address in a compressed header, it MUST be formed by padding on the left with a zero. In addition, the NFC Destination Address, 0x3F, MUST not be used as a unicast NFC address of SSAP or DSAP. -- The document date (November 27, 2014) is 3438 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '10' is defined on line 588, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3633 (ref. '8') (Obsoleted by RFC 8415) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6Lo Working Group Y-G. Hong 3 Internet-Draft Y-H. Choi 4 Intended status: Informational ETRI 5 Expires: May 31, 2015 J-S. Youn 6 DONG-EUI Univ 7 D-K. Kim 8 KNU 9 J-H. Choi 10 Samsung Electronics Co., 11 November 27, 2014 13 Transmission of IPv6 Packets over Near Field Communication 14 draft-hong-6lo-ipv6-over-nfc-03 16 Abstract 18 Near field communication (NFC) is a set of standards for smartphones 19 and portable devices to establish radio communication with each other 20 by touching them together or bringing them into proximity, usually no 21 more than 10 cm. NFC standards cover communications protocols and 22 data exchange formats, and are based on existing radio-frequency 23 identification (RFID) standards including ISO/IEC 14443 and FeliCa. 24 The standards include ISO/IEC 18092 and those defined by the NFC 25 Forum. The NFC technology has been widely implemented and available 26 in mobile phones, laptop computers, and many other devices. This 27 document describes how IPv6 is transmitted over NFC using 6LowPAN 28 techniques. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at http://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on May 31, 2015. 47 Copyright Notice 49 Copyright (c) 2014 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 65 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 4 66 3. Overview of Near Field Communication Technology . . . . . . . 4 67 3.1. Peer-to-peer Mode for IPv6 over NFC . . . . . . . . . . . 4 68 3.2. Protocol Stacks in IPv6 over NFC . . . . . . . . . . . . 5 69 3.3. NFC-enabled Device Addressing . . . . . . . . . . . . . . 6 70 3.4. NFC Packet Size and MTU . . . . . . . . . . . . . . . . . 6 71 4. Specification of IPv6 over NFC . . . . . . . . . . . . . . . 7 72 4.1. Protocol Stack . . . . . . . . . . . . . . . . . . . . . 7 73 4.2. Link Model . . . . . . . . . . . . . . . . . . . . . . . 8 74 4.3. Stateless Address Autoconfiguration . . . . . . . . . . . 8 75 4.4. Neighbor Discovery . . . . . . . . . . . . . . . . . . . 9 76 4.5. Header Compression . . . . . . . . . . . . . . . . . . . 9 77 4.6. Fragmentation and Reassembly . . . . . . . . . . . . . . 10 78 4.7. Unicast Address Mapping . . . . . . . . . . . . . . . . . 10 79 4.8. Multicast Address Mapping . . . . . . . . . . . . . . . . 11 80 5. Internet Connectivity Scenarios . . . . . . . . . . . . . . . 11 81 5.1. NFC-enabled Device Connected to the Internet . . . . . . 11 82 5.2. Isolated NFC-enabled Device Network . . . . . . . . . . . 12 83 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 84 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 85 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 86 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 87 8.2. Informative References . . . . . . . . . . . . . . . . . 13 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 90 1. Introduction 92 NFC is a set of short-range wireless technologies, typically 93 requiring a distance of 10 cm or less. NFC operates at 13.56 MHz on 94 ISO/IEC 18000-3 air interface and at rates ranging from 106 kbit/s to 95 424 kbit/s. NFC always involves an initiator and a target; the 96 initiator actively generates an RF field that can power a passive 97 target. This enables NFC targets to take very simple form factors 98 such as tags, stickers, key fobs, or cards that do not require 99 batteries. NFC peer-to-peer communication is possible, provided both 100 devices are powered. NFC builds upon RFID systems by allowing two- 101 way communication between endpoints, where earlier systems such as 102 contactless smart cards were one-way only. It has been used in 103 devices such as mobile phones, running Android operating system, 104 named with a feature called "Android Beam". In addition, it is 105 expected for the other mobile phones, running the other operating 106 systems (e.g., iOS, etc.) to be equipped with NFC technology in the 107 near future. 109 Considering the potential for exponential growth in the number of 110 heterogeneous air interface technologies, NFC would be widely used as 111 one of the other air interface technologies, such as Bluetooth Low 112 Energy (BT-LE), Wi-Fi, and so on. Each of the heterogeneous air 113 interface technologies has its own characteristics, which cannot be 114 covered by the other technologies, so various kinds of air interface 115 technologies would be existing together. Therefore, it is required 116 for them to communicate each other. NFC also has the strongest point 117 (e.g., secure communication distance of 10 cm) to prevent the third 118 party from attacking privacy. 120 When the number of devices and things having different air interface 121 technologies communicate each other, IPv6 is an ideal internet 122 protocols owing to its large address space. Also, NFC would be one 123 of the endpoints using IPv6. Therefore, This document describes how 124 IPv6 is transmitted over NFC using 6LoWPAN techiques with following 125 scopes. 127 o Overview of NFC technologies; 129 o Specifications for IPv6 over NFC; 131 * Neighbor Discovery; 133 * Addressing and Configuration; 135 * Header Compression; 137 * Fragmentation & Reassembly for a IPv6 datagram; 139 RFC4944 [1] specifies the transmission of IPv6 over IEEE 802.15.4. 140 The NFC link also has similar characteristics to that of IEEE 141 802.15.4. Many of the mechanisms defined in the RFC4944 [1] can be 142 applied to the transmission of IPv6 on NFC links. This document 143 specifies the details of IPv6 transmission over NFC links. 145 2. Conventions and Terminology 147 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 148 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 149 document are to be interpreted as described in [2]. 151 3. Overview of Near Field Communication Technology 153 NFC technology enables simple and safe two-way interactions between 154 electronic devices, allowing consumers to perform contactless 155 transactions, access digital content, and connect electronic devices 156 with a single touch. NFC complements many popular consumer level 157 wireless technologies, by utilizing the key elements in existing 158 standards for contactless card technology (ISO/IEC 14443 A&B and 159 JIS-X 6319-4). NFC can be compatible with existing contactless card 160 infrastructure and it enables a consumer to utilize one device across 161 different systems. 163 Extending the capability of contactless card technology, NFC also 164 enables devices to share information at a distance that is less than 165 10 cm with a maximum communication speed of 424 kbps. Users can 166 share business cards, make transactions, access information from a 167 smart poster or provide credentials for access control systems with a 168 simple touch. 170 NFC's bidirectional communication ability is ideal for establishing 171 connections with other technologies by the simplicity of touch. In 172 addition to the easy connection and quick transactions, simple data 173 sharing is also available. 175 3.1. Peer-to-peer Mode for IPv6 over NFC 177 NFC-enabled devices are unique in that they can support three modes 178 of operation: card emulation, peer-to-peer, and reader/writer. Peer- 179 to-peer mode enables two NFC-enabled devices to communicate with each 180 other to exchange information and share files, so that users of NFC- 181 enabled devices can quickly share contact information and other files 182 with a touch. Therefore, a NFC-enabled device can securely send IPv6 183 packets to any corresponding node on the Internet when a NFC-enabled 184 gateway is linked to the Internet. 186 3.2. Protocol Stacks in IPv6 over NFC 188 The IP protocol can use the services provided by Logical Link Control 189 Protocol (LLCP) in the NFC stack to provide reliable, two-way 190 transport of information between the peer devices. Figure 1 depicts 191 the NFC P2P protocol stack with IPv6 bindings to the LLCP. 193 For data communication in IPv6 over NFC, an IPv6 packet SHALL be 194 received at LLCP of NFC and transported to an Information Field in 195 Protocol Data Unit (I PDU) of LLCP of the NFC-enabled peer device. 196 Since LLCP does not support fragmentation and reassembly, Upper 197 Layers SHOULD support fragmentation and reassembly. For IPv6 198 addressing or address configuration, LLCP SHALL provide related 199 information, such as link layer addresses, to its upper layer. LLCP 200 to IPv6 protocol Binding SHALL transfer the SSAP and DSAP value to 201 the IPv6 over NFC protocol. SSAP stands for Source Service Access 202 Point, which is 6-bit value meaning a kind of Logical Link Control 203 (LLC) address, while DSAP means a LLC address of destination NFC- 204 enabled device. 206 | | 207 | | Application Layer 208 | Upper Layer Protocols | Transport Layer 209 | | Network Layer 210 | | | 211 +----------------------------------------+ <------------------ 212 | IPv6-LLCP Binding | | 213 +----------------------------------------+ NFC 214 | | Logical Link 215 | Logical Link Control Protocol | Layer 216 | (LLCP) | | 217 +----------------------------------------+ <------------------ 218 | | | 219 | Activities | | 220 | Digital Protocol | NFC 221 | | Physical 222 +----------------------------------------+ Layer 223 | | | 224 | RF Analog | | 225 | | | 226 +----------------------------------------+ <------------------ 228 Figure 1: Protocol Stack of NFC 230 3.3. NFC-enabled Device Addressing 232 NFC-enabled devices are identified by 6-bit LLC address. In other 233 words, Any address SHALL be usable as both an SSAP and a DSAP 234 address. According to NFCForum-TS-LLCP_1.1 [3], address values 235 between 0 and 31 (00h - 1Fh) SHALL be reserved for well-known service 236 access points for Service Discovery Protocol (SDP). Address values 237 between 32 and 63 (20h - 3Fh) inclusively, SHALL be assigned by the 238 local LLC as the result of an upper layer service request. 240 3.4. NFC Packet Size and MTU 242 As mentioned in Section 3.2, an IPv6 packet SHALL be received at LLCP 243 of NFC and transported to an Information Field in Protocol Data Unit 244 (I PDU) of LLCP of the NFC-enabled peer device. The format of the I 245 PDU SHALL be as shown in Figure 2. 247 0 0 1 1 2 2 248 0 6 0 6 0 4 249 +------+----+------+----+----+---------------------------------+ 250 |DDDDDD|1100|SSSSSS|N(S)|N(R)| Service Data Unit | 251 +------+----+------+----+----+---------------------------------+ 252 | <------- 3 bytes --------> | | 253 | <------------------- 128 bytes (default) ------------------> | 254 | | 256 Figure 2: Format of the I PDU in NFC 258 The I PDU sequence field SHALL contain two sequence numbers: The send 259 sequence number N(S) and the receive sequence number N(R). The send 260 sequence number N(S) SHALL indicate the sequence number associated 261 with this I PDU. The receive sequence number N(R) value SHALL 262 indicate that I PDUs numbered up through N(R) - 1 have been received 263 correctly by the sender of this I PDU and successfully passed to the 264 senders SAP identified in the SSAP field. These I PDUs SHALL be 265 considered as acknowledged. 267 The information field of an I PDU SHALL contain a single service data 268 unit. The maximum number of octets in the information field SHALL be 269 determined by the Maximum Information Unit (MIU) for the data link 270 connection. The default value of the MIU for I PDUs SHALL be 128 271 octets. The local and remote LLCs each establish and maintain 272 distinct MIU values for each data link connection endpoint. Also, An 273 LLC MAY announce a larger MIU for a data link connection by 274 transmitting an MIUX extension parameter within the information 275 field. 277 4. Specification of IPv6 over NFC 279 NFC technology sets also has considerations and requirements owing to 280 low power consumption and allowed protocol overhead. 6LoWPAN 281 standards RFC4944 [1], RFC6775 [4], and RFC6282 [5] provide useful 282 functionality for reducing overhead which can be applied to BT-LE. 283 This functionality comprises of link-local IPv6 addresses and 284 stateless IPv6 address auto-configuration (see Section 4.3), Neighbor 285 Discovery (see Section 4.4) and header compression (see Section 4.5). 287 One of the differences between IEEE 802.15.4 and NFC is that the 288 former supports both star and mesh topology (and requires a routing 289 protocol), whereas NFC can support direct peer-to-peer connection and 290 simple mesh-like topology depending on NFC application scenarios 291 because of very short RF distance of 10 cm or less. 293 4.1. Protocol Stack 295 Figure 3 illustrates IPv6 over NFC. Upper layer protocols can be 296 transport protocols (TCP and UDP), application layer, and the others 297 capable running on the top of IPv6. 299 | | Transport & 300 | Upper Layer Protocols | Application Layer 301 +----------------------------------------+ <------------------ 302 | | | 303 | IPv6 | | 304 | | Network 305 +----------------------------------------+ Layer 306 | Adaptation Layer for IPv6 over NFC | | 307 +----------------------------------------+ <------------------ 308 | IPv6-LLCP Binding | 309 | Logical Link Control Protocol | NFC Link Layer 310 | (LLCP) | | 311 +----------------------------------------+ <------------------ 312 | | | 313 | Activities | NFC 314 | Digital Protocol | Physical Layer 315 | RF Analog | | 316 | | | 317 +----------------------------------------+ <------------------ 319 Figure 3: Protocol Stack for IPv6 over NFC 321 Adaptation layer for IPv6 over NFC SHALL support neighbor discovery, 322 address auto-configuration, header compression, and fragmentation & 323 reassembly. 325 4.2. Link Model 327 In the case of BT-LE, Logical Link Control and Adaptation Protocol 328 (L2CAP) supports fragmentation and reassembly (FAR) functionality; 329 therefore, adaptation layer for IPv6 over BT-LE do not have to 330 conduct the FAR procedure. However, NFC link layer is similar to 331 IEEE 802.15.4. Adaptation layer for IPv6 over NFC SHOULD support FAR 332 functionality. Therefore, fragmentation functionality as defined in 333 RFC4944 [1] SHALL be used in NFC-enabled device networks. 335 The NFC link between two communicating devices is considered to be a 336 point-to-point link only. Unlike in BT-LE, NFC link does not 337 consider star topology and mesh network topology but peer-to-peer 338 topology and simple multi-hop topology. Due to this characteristics, 339 6LoWPAN functionality, such as addressing and auto-configuration, and 340 header compression, is specialized into NFC. 342 4.3. Stateless Address Autoconfiguration 344 A NFC-enabled device (i.e., 6LN) performs stateless address 345 autoconfiguration as per RFC4862 [6]. A 64-bit Interface identifier 346 (IID) for a NFC interface MAY be formed by utilizing the 6-bit NFC 347 LLCP address (i.e., SSAP or DSAP) (see Section 3.3). In the 348 viewpoint of address configuration, such an IID MAY guarantee a 349 stable IPv6 address because each data link connection is uniquely 350 identified by the pair of DSAP and SSAP included in the header of 351 each LLC PDU in NFC. 353 In the case of NFC-enabled device address, the "Universal/Local" bit 354 MUST be set to 0 RFC4291 [7]. Only if the NFC-enabled device address 355 is known to be a public address the "Universal/Local" bit can be set 356 to 1. As defined in RFC4291, the IPv6 link-local address for a NFC- 357 enabled device is formed by appending the IID, to the prefix 358 FE80::/64, as depicted in Figure 4. 360 0 0 0 1 1 361 0 1 6 2 2 362 0 0 4 2 7 363 +----------+------------------+---------------------+------+ 364 |1111111010| zeros | zeros | SSAP | 365 +----------+------------------+---------------------+------+ 366 | | 367 | <---------------------- 128 bits ----------------------> | 368 | | 370 Figure 4: IPv6 link-local address in NFC 372 The tool for a 6LBR to obtain an IPv6 prefix for numbering the NFC 373 network is can be accomplished via DHCPv6 Prefix Delegation (RFC3633 374 [8]). 376 4.4. Neighbor Discovery 378 Neighbor Discovery Optimization for 6LoWPANs (RFC6775 [4]) describes 379 the neighbor discovery approach in several 6LoWPAN topologies, such 380 as mesh topology. NFC does not consider complicated mesh topology 381 but simple multi-hop network topology or directly connected peer-to- 382 peer network. Therefore, the following aspects of RFC6775 are 383 applicable to NFC: 385 1. In a case that a NFC-enabled device (6LN) is directly connected 386 to 6LBR, A NFC 6LN MUST register its address with the 6LBR by 387 sending a Neighbor Solicitation (NS) message with the Address 388 Registration Option (ARO) and process the Neighbor Advertisement 389 (NA) accordingly. In addition, DHCPv6 is used to assigned an 390 address, Duplicate Address Detection (DAD) is not required. 392 2. For sending Router Solicitations and processing Router 393 Advertisements the NFC 6LNs MUST follow Sections 5.3 and 5.4 of 394 the RFC6775. 396 4.5. Header Compression 398 Header compression as defined in RFC6282 [5] , which specifies the 399 compression format for IPv6 datagrams on top of IEEE 802.15.4, is 400 REQUIRED in this document as the basis for IPv6 header compression on 401 top of NFC. All headers MUST be compressed according to RFC6282 402 encoding formats. 404 If a 16-bit address is required as a short address of IEEE 802.15.4, 405 it MUST be formed by padding the 6-bit NFC link-layer (node) address 406 to the left with zeros as shown in Figure 5. 408 0 1 409 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 | Padding(all zeros)| NFC Addr. | 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 414 Figure 5: NFC short adress format 416 4.6. Fragmentation and Reassembly 418 Fragmentation and reassembly (FAR) as defined in RFC4944, which 419 specifies the fragmentation methods for IPv6 datagrams on top of IEEE 420 802.15.4, is REQUIRED in this document as the basis for IPv6 datagram 421 FAR on top of NFC. All headers MUST be compressed according to 422 RFC4944 encoding formats, but the default MTU of NFC is 128 bytes. 423 This MUST be considered. 425 4.7. Unicast Address Mapping 427 The address resolution procedure for mapping IPv6 non-multicast 428 addresses into NFC link-layer addresses follows the general 429 description in Section 7.2 of RFC4861 [9], unless otherwise 430 specified. 432 The Source/Target link-layer Address option has the following form 433 when the addresses are 6-bit NFC link-layer (node) addresses. 435 0 1 436 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 437 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 438 | Type | Length=1 | 439 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 440 | | 441 +- Padding (all zeros) -+ 442 | | 443 +- +-+-+-+-+-+-+ 444 | | NFC Addr. | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 447 Figure 6: Unicast address mapping 449 Option fields: 451 Type: 453 1: for Source Link-layer address. 455 2: for Target Link-layer address. 457 Length: 459 This is the length of this option (including the type and 460 length fields) in units of 8 octets. The value of this field 461 is 1 for 6-bit NFC node addresses. 463 NFC address: 465 The 6-bit address in canonical bit order. This is the unicast 466 address the interface currently responds to. 468 4.8. Multicast Address Mapping 470 All IPv6 multicast packets MUST be sent to NFC Destination Address, 471 0x3F (broadcast) and filtered at the IPv6 layer. When represented as 472 a 16-bit address in a compressed header, it MUST be formed by padding 473 on the left with a zero. In addition, the NFC Destination Address, 474 0x3F, MUST not be used as a unicast NFC address of SSAP or DSAP. 476 0 1 477 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 478 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 479 | Padding(all zeros)|1 1 1 1 1 1| 480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 482 Figure 7: Multicast address mapping 484 5. Internet Connectivity Scenarios 486 As two typical scenarios, the NFC network can be isolated and 487 connected to the Internet. 489 5.1. NFC-enabled Device Connected to the Internet 491 One of the key applications by using adaptation technology of IPv6 492 over NFC is the most securely transmitting IPv6 packets because RF 493 distance between 6LN and 6LBR SHOULD be within 10 cm. If any third 494 party wants to hack into the RF between them, it MUST come to nearly 495 touch them. Applications can choose which kinds of air interfaces 496 (e.g., BT-LE, Wi-Fi, NFC, etc.) to send data depending 497 characteristics of data. NFC SHALL be the best solution for secured 498 and private information. 500 Figure 8 illustrates an example of NFC-enabled device network 501 connected to the Internet. Distance between 6LN and 6LBR SHOULD be 502 10 cm or less. If there is any of close laptop computers to a user, 503 it SHALL becomes the 6LBR. Additionally, When the user mounts a NFC- 504 enabled air interface adapter (e.g., portable small NFC dongle) on 505 the close laptop PC, the user's NFC-enabled device (6LN) can 506 communicate the laptop PC (6LBR) within 10 cm distance. 508 ************ 509 6LN ------------------- 6LBR -----* Internet *------- CN 510 | (dis. 10 cm or less) | ************ | 511 | | | 512 | <-------- NFC -------> | <----- IPv6 packet ------> | 513 | (IPv6 over NFC packet) | | 515 Figure 8: NFC-enabled device network connected to the Internet 517 5.2. Isolated NFC-enabled Device Network 519 In some scenarios, the NFC-enabled device network may transiently be 520 a simple isolated network as shown in the Figure 9. 522 6LN ---------------------- 6LR ---------------------- 6LN 523 | (10 cm or less) | (10 cm or less) | 524 | | | 525 | <--------- NFC --------> | <--------- NFC --------> | 526 | (IPv6 over NFC packet) | (IPv6 over NFC packet) | 528 Figure 9: Isolated NFC-enabled device network 530 In mobile phone markets, applications are designed and made by user 531 developers. They may image interesting applications, where three or 532 more mobile phones touch or attach each other to accomplish 533 outstanding performance. For instance, three or more mobile phones 534 can play multi-channel sound of music together. In addition, 535 attached three or more mobile phones can make an extended banner to 536 show longer sentences in a concert hall. 538 6. IANA Considerations 540 There are no IANA considerations related to this document. 542 7. Security Considerations 544 The method of deriving Interface Identifiers from 6-bit NFC Link 545 layer addresses is intended to preserve global uniqueness when it is 546 possible. Therefore, it is to required to protect from duplication 547 through accident or forgery. 549 8. References 551 8.1. Normative References 553 [1] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 554 "Transmission of IPv6 Packets over IEEE 802.15.4 555 Networks", RFC 4944, September 2007. 557 [2] Bradner, S., "Key words for use in RFCs to Indicate 558 Requirement Levels", BCP 14, RFC 2119, March 1997. 560 [3] "Logical Link Control Protocol version 1.1", NFC Forum 561 Technical Specification , June 2011. 563 [4] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, 564 "Neighbor Discovery Optimization for IPv6 over Low-Power 565 Wireless Personal Area Networks (6LoWPANs)", RFC 6775, 566 November 2012. 568 [5] Hui, J. and P. Thubert, "Compression Format for IPv6 569 Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, 570 September 2011. 572 [6] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 573 Address Autoconfiguration", RFC 4862, September 2007. 575 [7] Hinden, R. and S. Deering, "IP Version 6 Addressing 576 Architecture", RFC 4291, February 2006. 578 [8] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 579 Host Configuration Protocol (DHCP) version 6", RFC 3633, 580 December 2003. 582 [9] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 583 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 584 September 2007. 586 8.2. Informative References 588 [10] "Near Field Communication - Interface and Protocol (NFCIP- 589 1) 3rd Ed.", ECMA-340 , June 2013. 591 Authors' Addresses 593 Yong-Geun Hong 594 ETRI 595 161 Gajeong-Dong Yuseung-Gu 596 Daejeon 305-700 597 Korea 599 Phone: +82 42 860 6557 600 Email: yghong@etri.re.kr 601 Younghwan Choi 602 ETRI 603 218 Gajeongno, Yuseong 604 Daejeon 305-700 605 Korea 607 Phone: +82 42 860 1429 608 Email: yhc@etri.re.kr 610 Joo-Sang Youn 611 DONG-EUI University 612 176 Eomgwangno Busan_jin_gu 613 Busan 614-714 614 Korea 616 Phone: +82 51 890 1993 617 Email: joosang.youn@gmail.com 619 Dongkyun Kim 620 Kyungpook National University 621 80 Daehak-ro, Buk-gu 622 Daegu 702-701 623 Korea 625 Phone: +82 53 950 7571 626 Email: dongkyun@knu.ac.kr 628 JinHyouk Choi 629 Samsung Electronics Co., 630 129 Samsung-ro, Youngdong-gu 631 Suwon 447-712 632 Korea 634 Phone: +82 2 2254 0114 635 Email: jinchoe@samsung.com