idnits 2.17.00 (12 Aug 2021) /tmp/idnits54759/draft-ietf-6lo-nfc-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == 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 (March 2, 2015) is 2637 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '11' is defined on line 605, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '3' ** Obsolete normative reference: RFC 3633 (ref. '8') (Obsoleted by RFC 8415) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). 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: Standards Track ETRI 5 Expires: September 3, 2015 J-S. Youn 6 DONG-EUI Univ 7 D-K. Kim 8 KNU 9 J-H. Choi 10 Samsung Electronics Co., 11 March 2, 2015 13 Transmission of IPv6 Packets over Near Field Communication 14 draft-ietf-6lo-nfc-00 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 September 3, 2015. 47 Copyright Notice 49 Copyright (c) 2015 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 86 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 87 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 88 9.2. Informative References . . . . . . . . . . . . . . . . . 14 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 91 1. Introduction 93 NFC is a set of short-range wireless technologies, typically 94 requiring a distance of 10 cm or less. NFC operates at 13.56 MHz on 95 ISO/IEC 18000-3 air interface and at rates ranging from 106 kbit/s to 96 424 kbit/s. NFC always involves an initiator and a target; the 97 initiator actively generates an RF field that can power a passive 98 target. This enables NFC targets to take very simple form factors 99 such as tags, stickers, key fobs, or cards that do not require 100 batteries. NFC peer-to-peer communication is possible, provided both 101 devices are powered. NFC builds upon RFID systems by allowing two- 102 way communication between endpoints, where earlier systems such as 103 contactless smart cards were one-way only. It has been used in 104 devices such as mobile phones, running Android operating system, 105 named with a feature called "Android Beam". In addition, it is 106 expected for the other mobile phones, running the other operating 107 systems (e.g., iOS, etc.) to be equipped with NFC technology in the 108 near future. 110 Considering the potential for exponential growth in the number of 111 heterogeneous air interface technologies, NFC would be widely used as 112 one of the other air interface technologies, such as Bluetooth Low 113 Energy (BT-LE), Wi-Fi, and so on. Each of the heterogeneous air 114 interface technologies has its own characteristics, which cannot be 115 covered by the other technologies, so various kinds of air interface 116 technologies would be existing together. Therefore, it is required 117 for them to communicate each other. NFC also has the strongest point 118 (e.g., secure communication distance of 10 cm) to prevent the third 119 party from attacking privacy. 121 When the number of devices and things having different air interface 122 technologies communicate each other, IPv6 is an ideal internet 123 protocols owing to its large address space. Also, NFC would be one 124 of the endpoints using IPv6. Therefore, This document describes how 125 IPv6 is transmitted over NFC using 6LoWPAN techiques with following 126 scopes. 128 o Overview of NFC technologies; 130 o Specifications for IPv6 over NFC; 132 * Neighbor Discovery; 134 * Addressing and Configuration; 136 * Header Compression; 138 * Fragmentation & Reassembly for a IPv6 datagram; 140 RFC4944 [1] specifies the transmission of IPv6 over IEEE 802.15.4. 141 The NFC link also has similar characteristics to that of IEEE 142 802.15.4. Many of the mechanisms defined in the RFC4944 [1] can be 143 applied to the transmission of IPv6 on NFC links. This document 144 specifies the details of IPv6 transmission over NFC links. 146 2. Conventions and Terminology 148 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 149 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 150 document are to be interpreted as described in [2]. 152 3. Overview of Near Field Communication Technology 154 NFC technology enables simple and safe two-way interactions between 155 electronic devices, allowing consumers to perform contactless 156 transactions, access digital content, and connect electronic devices 157 with a single touch. NFC complements many popular consumer level 158 wireless technologies, by utilizing the key elements in existing 159 standards for contactless card technology (ISO/IEC 14443 A&B and 160 JIS-X 6319-4). NFC can be compatible with existing contactless card 161 infrastructure and it enables a consumer to utilize one device across 162 different systems. 164 Extending the capability of contactless card technology, NFC also 165 enables devices to share information at a distance that is less than 166 10 cm with a maximum communication speed of 424 kbps. Users can 167 share business cards, make transactions, access information from a 168 smart poster or provide credentials for access control systems with a 169 simple touch. 171 NFC's bidirectional communication ability is ideal for establishing 172 connections with other technologies by the simplicity of touch. In 173 addition to the easy connection and quick transactions, simple data 174 sharing is also available. 176 3.1. Peer-to-peer Mode for IPv6 over NFC 178 NFC-enabled devices are unique in that they can support three modes 179 of operation: card emulation, peer-to-peer, and reader/writer. Peer- 180 to-peer mode enables two NFC-enabled devices to communicate with each 181 other to exchange information and share files, so that users of NFC- 182 enabled devices can quickly share contact information and other files 183 with a touch. Therefore, a NFC-enabled device can securely send IPv6 184 packets to any corresponding node on the Internet when a NFC-enabled 185 gateway is linked to the Internet. 187 3.2. Protocol Stacks in IPv6 over NFC 189 The IP protocol can use the services provided by Logical Link Control 190 Protocol (LLCP) in the NFC stack to provide reliable, two-way 191 transport of information between the peer devices. Figure 1 depicts 192 the NFC P2P protocol stack with IPv6 bindings to the LLCP. 194 For data communication in IPv6 over NFC, an IPv6 packet SHALL be 195 received at LLCP of NFC and transported to an Information Field in 196 Protocol Data Unit (I PDU) of LLCP of the NFC-enabled peer device. 197 Since LLCP does not support fragmentation and reassembly, Upper 198 Layers SHOULD support fragmentation and reassembly. For IPv6 199 addressing or address configuration, LLCP SHALL provide related 200 information, such as link layer addresses, to its upper layer. LLCP 201 to IPv6 protocol Binding SHALL transfer the SSAP and DSAP value to 202 the IPv6 over NFC protocol. SSAP stands for Source Service Access 203 Point, which is 6-bit value meaning a kind of Logical Link Control 204 (LLC) address, while DSAP means a LLC address of destination NFC- 205 enabled device. 207 | | 208 | | Application Layer 209 | Upper Layer Protocols | Transport Layer 210 | | Network Layer 211 | | | 212 +----------------------------------------+ <------------------ 213 | IPv6-LLCP Binding | | 214 +----------------------------------------+ NFC 215 | | Logical Link 216 | Logical Link Control Protocol | Layer 217 | (LLCP) | | 218 +----------------------------------------+ <------------------ 219 | | | 220 | Activities | | 221 | Digital Protocol | NFC 222 | | Physical 223 +----------------------------------------+ Layer 224 | | | 225 | RF Analog | | 226 | | | 227 +----------------------------------------+ <------------------ 229 Figure 1: Protocol Stack of NFC 231 3.3. NFC-enabled Device Addressing 233 NFC-enabled devices are identified by 6-bit LLC address. In other 234 words, Any address SHALL be usable as both an SSAP and a DSAP 235 address. According to NFCForum-TS-LLCP_1.1 [3], address values 236 between 0 and 31 (00h - 1Fh) SHALL be reserved for well-known service 237 access points for Service Discovery Protocol (SDP). Address values 238 between 32 and 63 (20h - 3Fh) inclusively, SHALL be assigned by the 239 local LLC as the result of an upper layer service request. 241 3.4. NFC Packet Size and MTU 243 As mentioned in Section 3.2, an IPv6 packet SHALL be received at LLCP 244 of NFC and transported to an Information Field in Protocol Data Unit 245 (I PDU) of LLCP of the NFC-enabled peer device. The format of the I 246 PDU SHALL be as shown in Figure 2. 248 0 0 1 1 2 2 249 0 6 0 6 0 4 250 +------+----+------+----+----+---------------------------------+ 251 |DDDDDD|1100|SSSSSS|N(S)|N(R)| Service Data Unit | 252 +------+----+------+----+----+---------------------------------+ 253 | <------- 3 bytes --------> | | 254 | <------------------- 128 bytes (default) ------------------> | 255 | | 257 Figure 2: Format of the I PDU in NFC 259 The I PDU sequence field SHALL contain two sequence numbers: The send 260 sequence number N(S) and the receive sequence number N(R). The send 261 sequence number N(S) SHALL indicate the sequence number associated 262 with this I PDU. The receive sequence number N(R) value SHALL 263 indicate that I PDUs numbered up through N(R) - 1 have been received 264 correctly by the sender of this I PDU and successfully passed to the 265 senders SAP identified in the SSAP field. These I PDUs SHALL be 266 considered as acknowledged. 268 The information field of an I PDU SHALL contain a single service data 269 unit. The maximum number of octets in the information field SHALL be 270 determined by the Maximum Information Unit (MIU) for the data link 271 connection. The default value of the MIU for I PDUs SHALL be 128 272 octets. The local and remote LLCs each establish and maintain 273 distinct MIU values for each data link connection endpoint. Also, An 274 LLC MAY announce a larger MIU for a data link connection by 275 transmitting an MIUX extension parameter within the information 276 field. 278 4. Specification of IPv6 over NFC 280 NFC technology sets also has considerations and requirements owing to 281 low power consumption and allowed protocol overhead. 6LoWPAN 282 standards RFC4944 [1], RFC6775 [4], and RFC6282 [5] provide useful 283 functionality for reducing overhead which can be applied to BT-LE. 284 This functionality comprises of link-local IPv6 addresses and 285 stateless IPv6 address auto-configuration (see Section 4.3), Neighbor 286 Discovery (see Section 4.4) and header compression (see Section 4.5). 288 One of the differences between IEEE 802.15.4 and NFC is that the 289 former supports both star and mesh topology (and requires a routing 290 protocol), whereas NFC can support direct peer-to-peer connection and 291 simple mesh-like topology depending on NFC application scenarios 292 because of very short RF distance of 10 cm or less. 294 4.1. Protocol Stack 296 Figure 3 illustrates IPv6 over NFC. Upper layer protocols can be 297 transport protocols (TCP and UDP), application layer, and the others 298 capable running on the top of IPv6. 300 | | Transport & 301 | Upper Layer Protocols | Application Layer 302 +----------------------------------------+ <------------------ 303 | | | 304 | IPv6 | | 305 | | Network 306 +----------------------------------------+ Layer 307 | Adaptation Layer for IPv6 over NFC | | 308 +----------------------------------------+ <------------------ 309 | IPv6-LLCP Binding | 310 | Logical Link Control Protocol | NFC Link Layer 311 | (LLCP) | | 312 +----------------------------------------+ <------------------ 313 | | | 314 | Activities | NFC 315 | Digital Protocol | Physical Layer 316 | RF Analog | | 317 | | | 318 +----------------------------------------+ <------------------ 320 Figure 3: Protocol Stack for IPv6 over NFC 322 Adaptation layer for IPv6 over NFC SHALL support neighbor discovery, 323 address auto-configuration, header compression, and fragmentation & 324 reassembly. 326 4.2. Link Model 328 In the case of BT-LE, Logical Link Control and Adaptation Protocol 329 (L2CAP) supports fragmentation and reassembly (FAR) functionality; 330 therefore, adaptation layer for IPv6 over BT-LE do not have to 331 conduct the FAR procedure. However, NFC link layer is similar to 332 IEEE 802.15.4. Adaptation layer for IPv6 over NFC SHOULD support FAR 333 functionality. Therefore, fragmentation functionality as defined in 334 RFC4944 [1] SHALL be used in NFC-enabled device networks. 336 The NFC link between two communicating devices is considered to be a 337 point-to-point link only. Unlike in BT-LE, NFC link does not 338 consider star topology and mesh network topology but peer-to-peer 339 topology and simple multi-hop topology. Due to this characteristics, 340 6LoWPAN functionality, such as addressing and auto-configuration, and 341 header compression, is specialized into NFC. 343 4.3. Stateless Address Autoconfiguration 345 A NFC-enabled device (i.e., 6LN) performs stateless address 346 autoconfiguration as per RFC4862 [6]. A 64-bit Interface identifier 347 (IID) for a NFC interface MAY be formed by utilizing the 6-bit NFC 348 LLCP address (i.e., SSAP or DSAP) (see Section 3.3). In the 349 viewpoint of address configuration, such an IID MAY guarantee a 350 stable IPv6 address because each data link connection is uniquely 351 identified by the pair of DSAP and SSAP included in the header of 352 each LLC PDU in NFC. 354 Following the guidance of RFC7136 [10], interface IIDs of all unicast 355 addresses for NFC-enabled devices are formed on the basis of 64 bits 356 long and constructed in a modified EUI-64 format. Therefore, this 357 document provides a stateless address autoconf formation which 358 suggests 58 zeros and 6 bit SSAP in the IID as shown in Figure 4. In 359 addition, the "Universal/Local" bit in the case of NFC-enabled device 360 address MUST be set to 0 RFC4291 [7]. Only if the NFC-enabled device 361 address is known to be a public address the "Universal/Local" bit can 362 be set to 1. The IPv6 link-local address for a NFC-enabled device is 363 formed by appending the IID, to the prefix FE80::/64, as depicted in 364 Figure 4. 366 0 0 0 1 1 367 0 1 6 2 2 368 0 0 4 2 7 369 +----------+------------------+---------------------+------+ 370 |1111111010| zeros | zeros | SSAP | 371 +----------+------------------+---------------------+------+ 372 | | 373 | <---------------------- 128 bits ----------------------> | 374 | | 376 Figure 4: IPv6 link-local address in NFC 378 The tool for a 6LBR to obtain an IPv6 prefix for numbering the NFC 379 network is can be accomplished via DHCPv6 Prefix Delegation (RFC3633 380 [8]). 382 4.4. Neighbor Discovery 384 Neighbor Discovery Optimization for 6LoWPANs (RFC6775 [4]) describes 385 the neighbor discovery approach in several 6LoWPAN topologies, such 386 as mesh topology. NFC does not consider complicated mesh topology 387 but simple multi-hop network topology or directly connected peer-to- 388 peer network. Therefore, the following aspects of RFC6775 are 389 applicable to NFC: 391 1. In a case that a NFC-enabled device (6LN) is directly connected 392 to 6LBR, A NFC 6LN MUST register its address with the 6LBR by 393 sending a Neighbor Solicitation (NS) message with the Address 394 Registration Option (ARO) and process the Neighbor Advertisement 395 (NA) accordingly. In addition, DHCPv6 is used to assigned an 396 address, Duplicate Address Detection (DAD) is not required. 398 2. For sending Router Solicitations and processing Router 399 Advertisements the NFC 6LNs MUST follow Sections 5.3 and 5.4 of 400 the RFC6775. 402 4.5. Header Compression 404 Header compression as defined in RFC6282 [5] , which specifies the 405 compression format for IPv6 datagrams on top of IEEE 802.15.4, is 406 REQUIRED in this document as the basis for IPv6 header compression on 407 top of NFC. All headers MUST be compressed according to RFC6282 408 encoding formats. 410 If a 16-bit address is required as a short address of IEEE 802.15.4, 411 it MUST be formed by padding the 6-bit NFC link-layer (node) address 412 to the left with zeros as shown in Figure 5. 414 0 1 415 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 | Padding(all zeros)| NFC Addr. | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 420 Figure 5: NFC short adress format 422 4.6. Fragmentation and Reassembly 424 Fragmentation and reassembly (FAR) as defined in RFC4944, which 425 specifies the fragmentation methods for IPv6 datagrams on top of IEEE 426 802.15.4, is REQUIRED in this document as the basis for IPv6 datagram 427 FAR on top of NFC. All headers MUST be compressed according to 428 RFC4944 encoding formats, but the default MTU of NFC is 128 bytes. 429 This MUST be considered. 431 4.7. Unicast Address Mapping 433 The address resolution procedure for mapping IPv6 non-multicast 434 addresses into NFC link-layer addresses follows the general 435 description in Section 7.2 of RFC4861 [9], unless otherwise 436 specified. 438 The Source/Target link-layer Address option has the following form 439 when the addresses are 6-bit NFC link-layer (node) addresses. 441 0 1 442 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 443 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 444 | Type | Length=1 | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 | | 447 +- Padding (all zeros) -+ 448 | | 449 +- +-+-+-+-+-+-+ 450 | | NFC Addr. | 451 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 453 Figure 6: Unicast address mapping 455 Option fields: 457 Type: 459 1: for Source Link-layer address. 461 2: for Target Link-layer address. 463 Length: 465 This is the length of this option (including the type and 466 length fields) in units of 8 octets. The value of this field 467 is 1 for 6-bit NFC node addresses. 469 NFC address: 471 The 6-bit address in canonical bit order. This is the unicast 472 address the interface currently responds to. 474 4.8. Multicast Address Mapping 476 All IPv6 multicast packets MUST be sent to NFC Destination Address, 477 0x3F (broadcast) and filtered at the IPv6 layer. When represented as 478 a 16-bit address in a compressed header, it MUST be formed by padding 479 on the left with a zero. In addition, the NFC Destination Address, 480 0x3F, MUST not be used as a unicast NFC address of SSAP or DSAP. 482 0 1 483 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 485 | Padding(all zeros)|1 1 1 1 1 1| 486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 488 Figure 7: Multicast address mapping 490 5. Internet Connectivity Scenarios 492 As two typical scenarios, the NFC network can be isolated and 493 connected to the Internet. 495 5.1. NFC-enabled Device Connected to the Internet 497 One of the key applications by using adaptation technology of IPv6 498 over NFC is the most securely transmitting IPv6 packets because RF 499 distance between 6LN and 6LBR SHOULD be within 10 cm. If any third 500 party wants to hack into the RF between them, it MUST come to nearly 501 touch them. Applications can choose which kinds of air interfaces 502 (e.g., BT-LE, Wi-Fi, NFC, etc.) to send data depending 503 characteristics of data. NFC SHALL be the best solution for secured 504 and private information. 506 Figure 8 illustrates an example of NFC-enabled device network 507 connected to the Internet. Distance between 6LN and 6LBR SHOULD be 508 10 cm or less. If there is any of close laptop computers to a user, 509 it SHALL becomes the 6LBR. Additionally, When the user mounts a NFC- 510 enabled air interface adapter (e.g., portable small NFC dongle) on 511 the close laptop PC, the user's NFC-enabled device (6LN) can 512 communicate the laptop PC (6LBR) within 10 cm distance. 514 ************ 515 6LN ------------------- 6LBR -----* Internet *------- CN 516 | (dis. 10 cm or less) | ************ | 517 | | | 518 | <-------- NFC -------> | <----- IPv6 packet ------> | 519 | (IPv6 over NFC packet) | | 521 Figure 8: NFC-enabled device network connected to the Internet 523 5.2. Isolated NFC-enabled Device Network 525 In some scenarios, the NFC-enabled device network may transiently be 526 a simple isolated network as shown in the Figure 9. 528 6LN ---------------------- 6LR ---------------------- 6LN 529 | (10 cm or less) | (10 cm or less) | 530 | | | 531 | <--------- NFC --------> | <--------- NFC --------> | 532 | (IPv6 over NFC packet) | (IPv6 over NFC packet) | 534 Figure 9: Isolated NFC-enabled device network 536 In mobile phone markets, applications are designed and made by user 537 developers. They may image interesting applications, where three or 538 more mobile phones touch or attach each other to accomplish 539 outstanding performance. For instance, three or more mobile phones 540 can play multi-channel sound of music together. In addition, 541 attached three or more mobile phones can make an extended banner to 542 show longer sentences in a concert hall. 544 6. IANA Considerations 546 There are no IANA considerations related to this document. 548 7. Security Considerations 550 The method of deriving Interface Identifiers from 6-bit NFC Link 551 layer addresses is intended to preserve global uniqueness when it is 552 possible. Therefore, it is to required to protect from duplication 553 through accident or forgery. 555 8. Acknowledgements 557 We are grateful to the members of the IETF 6lo working group. 559 Michael Richardson, Suresh Krishnan, Pascal Thubert, Carsten Bormann, 560 and Alexandru Petrescu have provided valuable feedback for this 561 draft. 563 9. References 565 9.1. Normative References 567 [1] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 568 "Transmission of IPv6 Packets over IEEE 802.15.4 569 Networks", RFC 4944, September 2007. 571 [2] Bradner, S., "Key words for use in RFCs to Indicate 572 Requirement Levels", BCP 14, RFC 2119, March 1997. 574 [3] "Logical Link Control Protocol version 1.1", NFC Forum 575 Technical Specification , June 2011. 577 [4] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, 578 "Neighbor Discovery Optimization for IPv6 over Low-Power 579 Wireless Personal Area Networks (6LoWPANs)", RFC 6775, 580 November 2012. 582 [5] Hui, J. and P. Thubert, "Compression Format for IPv6 583 Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, 584 September 2011. 586 [6] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 587 Address Autoconfiguration", RFC 4862, September 2007. 589 [7] Hinden, R. and S. Deering, "IP Version 6 Addressing 590 Architecture", RFC 4291, February 2006. 592 [8] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 593 Host Configuration Protocol (DHCP) version 6", RFC 3633, 594 December 2003. 596 [9] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 597 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 598 September 2007. 600 [10] Carpenter, B. and S. Jiang, "Significance of IPv6 601 Interface Identifiers", RFC 7136, February 2014. 603 9.2. Informative References 605 [11] "Near Field Communication - Interface and Protocol (NFCIP- 606 1) 3rd Ed.", ECMA-340 , June 2013. 608 Authors' Addresses 610 Yong-Geun Hong 611 ETRI 612 161 Gajeong-Dong Yuseung-Gu 613 Daejeon 305-700 614 Korea 616 Phone: +82 42 860 6557 617 Email: yghong@etri.re.kr 619 Younghwan Choi 620 ETRI 621 218 Gajeongno, Yuseong 622 Daejeon 305-700 623 Korea 625 Phone: +82 42 860 1429 626 Email: yhc@etri.re.kr 628 Joo-Sang Youn 629 DONG-EUI University 630 176 Eomgwangno Busan_jin_gu 631 Busan 614-714 632 Korea 634 Phone: +82 51 890 1993 635 Email: joosang.youn@gmail.com 637 Dongkyun Kim 638 Kyungpook National University 639 80 Daehak-ro, Buk-gu 640 Daegu 702-701 641 Korea 643 Phone: +82 53 950 7571 644 Email: dongkyun@knu.ac.kr 645 JinHyouk Choi 646 Samsung Electronics Co., 647 129 Samsung-ro, Youngdong-gu 648 Suwon 447-712 649 Korea 651 Phone: +82 2 2254 0114 652 Email: jinchoe@samsung.com