< draft-ietf-6lo-nfc-08.txt   draft-ietf-6lo-nfc-09.txt >
6Lo Working Group Y. Choi, Ed. 6Lo Working Group Y. Choi, Ed.
Internet-Draft Y-G. Hong, Ed. Internet-Draft Y-G. Hong
Intended status: Standards Track ETRI Intended status: Standards Track ETRI
Expires: May 2, 2018 J-S. Youn Expires: July 12, 2018 J-S. Youn
Dongeui Univ Dongeui Univ
D-K. Kim D-K. Kim
KNU KNU
J-H. Choi J-H. Choi
Samsung Electronics Co., Samsung Electronics Co.,
October 29, 2017 January 8, 2018
Transmission of IPv6 Packets over Near Field Communication Transmission of IPv6 Packets over Near Field Communication
draft-ietf-6lo-nfc-08 draft-ietf-6lo-nfc-09
Abstract Abstract
Near field communication (NFC) is a set of standards for smartphones Near field communication (NFC) is a set of standards for smartphones
and portable devices to establish radio communication with each other and portable devices to establish radio communication with each other
by touching them together or bringing them into proximity, usually no by touching them together or bringing them into proximity, usually no
more than 10 cm. NFC standards cover communications protocols and more than 10 cm. NFC standards cover communications protocols and
data exchange formats, and are based on existing radio-frequency data exchange formats, and are based on existing radio-frequency
identification (RFID) standards including ISO/IEC 14443 and FeliCa. identification (RFID) standards including ISO/IEC 14443 and FeliCa.
The standards include ISO/IEC 18092 and those defined by the NFC The standards include ISO/IEC 18092 and those defined by the NFC
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 2, 2018. This Internet-Draft will expire on July 12, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 40 skipping to change at page 2, line 40
4.1. Protocol Stacks . . . . . . . . . . . . . . . . . . . . . 7 4.1. Protocol Stacks . . . . . . . . . . . . . . . . . . . . . 7
4.2. Link Model . . . . . . . . . . . . . . . . . . . . . . . 7 4.2. Link Model . . . . . . . . . . . . . . . . . . . . . . . 7
4.3. Stateless Address Autoconfiguration . . . . . . . . . . . 8 4.3. Stateless Address Autoconfiguration . . . . . . . . . . . 8
4.4. IPv6 Link Local Address . . . . . . . . . . . . . . . . . 9 4.4. IPv6 Link Local Address . . . . . . . . . . . . . . . . . 9
4.5. Neighbor Discovery . . . . . . . . . . . . . . . . . . . 9 4.5. Neighbor Discovery . . . . . . . . . . . . . . . . . . . 9
4.6. Dispatch Header . . . . . . . . . . . . . . . . . . . . . 10 4.6. Dispatch Header . . . . . . . . . . . . . . . . . . . . . 10
4.7. Header Compression . . . . . . . . . . . . . . . . . . . 10 4.7. Header Compression . . . . . . . . . . . . . . . . . . . 10
4.8. Fragmentation and Reassembly . . . . . . . . . . . . . . 11 4.8. Fragmentation and Reassembly . . . . . . . . . . . . . . 11
4.9. Unicast Address Mapping . . . . . . . . . . . . . . . . . 11 4.9. Unicast Address Mapping . . . . . . . . . . . . . . . . . 11
4.10. Multicast Address Mapping . . . . . . . . . . . . . . . . 12 4.10. Multicast Address Mapping . . . . . . . . . . . . . . . . 12
5. Internet Connectivity Scenarios . . . . . . . . . . . . . . . 12 5. Internet Connectivity Scenarios . . . . . . . . . . . . . . . 13
5.1. NFC-enabled Device Connected to the Internet . . . . . . 12 5.1. NFC-enabled Device Connected to the Internet . . . . . . 13
5.2. Isolated NFC-enabled Device Network . . . . . . . . . . . 13 5.2. Isolated NFC-enabled Device Network . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
NFC is a set of short-range wireless technologies, typically NFC is a set of short-range wireless technologies, typically
requiring a distance of 10 cm or less. NFC operates at 13.56 MHz on requiring a distance of 10 cm or less. NFC operates at 13.56 MHz on
ISO/IEC 18000-3 air interface and at rates ranging from 106 kbit/s to ISO/IEC 18000-3 air interface and at rates ranging from 106 kbit/s to
424 kbit/s. NFC always involves an initiator and a target; the 424 kbit/s. NFC always involves an initiator and a target; the
initiator actively generates an RF field that can power a passive initiator actively generates an RF field that can power a passive
target. This enables NFC targets to take very simple form factors target. This enables NFC targets to take very simple form factors
skipping to change at page 9, line 37 skipping to change at page 9, line 37
4.5. Neighbor Discovery 4.5. Neighbor Discovery
Neighbor Discovery Optimization for 6LoWPANs ([RFC6775]) describes Neighbor Discovery Optimization for 6LoWPANs ([RFC6775]) describes
the neighbor discovery approach in several 6LoWPAN topologies, such the neighbor discovery approach in several 6LoWPAN topologies, such
as mesh topology. NFC does not support a complicated mesh topology as mesh topology. NFC does not support a complicated mesh topology
but only a simple multi-hop network topology or directly connected but only a simple multi-hop network topology or directly connected
peer-to-peer network. Therefore, the following aspects of RFC 6775 peer-to-peer network. Therefore, the following aspects of RFC 6775
are applicable to NFC: are applicable to NFC:
o In a case that an NFC-enabled device (6LN) is directly connected o When an NFC-enabled device (6LN) is directly connected to a 6LBR,
to a 6LBR, an NFC 6LN MUST register its address with the 6LBR by an NFC 6LN MUST register its address with the 6LBR by sending a
sending a Neighbor Solicitation (NS) message with the Address Neighbor Solicitation (NS) message with the Address Registration
Registration Option (ARO) and process the Neighbor Advertisement Option (ARO) and process the Neighbor Advertisement (NA)
(NA) accordingly. In addition, if DHCPv6 is used to assign an accordingly. In addition, if DHCPv6 is used to assign an address,
address, Duplicate Address Detection (DAD) MAY not be required. Duplicate Address Detection (DAD) MAY not be required.
o In a case that two or more NFC 6LNs meet within a sigle hop range o When two or more NFC 6LNs meet, there MAY be two cases. One is
(e.g., isolated network), one of them can become a router for that they meet with multi-hop connections, and the other is that
6LR/6LBR. If they have the same properties, any of them can be a they meet within a sigle hop range (e.g., isolated network). In a
router. Unless they are the same (e.g., different MTU, level of case of multi-hops, all of 6LNs, which have two or more
remaining energy, connectivity, etc.), a performance-outstanding connections with different neighbors, MAY be a router for
device can become a router. 6LR/6LBR. In a case that they meet within a single hop and they
have the same properties, any of them can be a router. Unless
they are the same (e.g., different MTU, level of remaining energy,
connectivity, etc.), a performance-outstanding device can become a
router. Also, they MAY deliver their own information (e.g., MTU
and energy level, etc.) to neighbors with NFC LLCP protocols
during connection initialization.
o For sending Router Solicitations and processing Router o For sending Router Solicitations and processing Router
Advertisements, the NFC 6LNs MUST follow Sections 5.3 and 5.4 of Advertisements, the NFC 6LNs MUST follow Sections 5.3 and 5.4 of
RFC 6775. RFC 6775.
4.6. Dispatch Header 4.6. Dispatch Header
All IPv6-over-NFC encapsulated datagrams are prefixed by an All IPv6-over-NFC encapsulated datagrams are prefixed by an
encapsulation header stack consisting of a Dispatch value followed by encapsulation header stack consisting of a Dispatch value followed by
zero or more header fields. The only sequence currently defined for zero or more header fields. The only sequence currently defined for
skipping to change at page 16, line 16 skipping to change at page 16, line 37
Younghwan Choi (editor) Younghwan Choi (editor)
Electronics and Telecommunications Research Institute Electronics and Telecommunications Research Institute
218 Gajeongno, Yuseung-gu 218 Gajeongno, Yuseung-gu
Daejeon 34129 Daejeon 34129
Korea Korea
Phone: +82 42 860 1429 Phone: +82 42 860 1429
Email: yhc@etri.re.kr Email: yhc@etri.re.kr
Yong-Geun Hong (editor) Yong-Geun Hong
Electronics and Telecommunications Research Institute Electronics and Telecommunications Research Institute
161 Gajeong-Dong Yuseung-gu 161 Gajeong-Dong Yuseung-gu
Daejeon 305-700 Daejeon 305-700
Korea Korea
Phone: +82 42 860 6557 Phone: +82 42 860 6557
Email: yghong@etri.re.kr Email: yghong@etri.re.kr
Joo-Sang Youn Joo-Sang Youn
DONG-EUI University DONG-EUI University
176 Eomgwangno Busan_jin_gu 176 Eomgwangno Busan_jin_gu
Busan 614-714 Busan 614-714
Korea Korea
Phone: +82 51 890 1993 Phone: +82 51 890 1993
Email: joosang.youn@gmail.com Email: joosang.youn@gmail.com
Dongkyun Kim Dongkyun Kim
 End of changes. 13 change blocks. 
27 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/