draft-ietf-6lo-nfc-11.txt   draft-ietf-6lo-nfc-12.txt 
6Lo Working Group Y. Choi, Ed. 6Lo Working Group Y. Choi, Ed.
Internet-Draft Y-G. Hong Internet-Draft Y-G. Hong
Intended status: Standards Track ETRI Intended status: Standards Track ETRI
Expires: April 4, 2019 J-S. Youn Expires: May 9, 2019 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 1, 2018 November 5, 2018
Transmission of IPv6 Packets over Near Field Communication Transmission of IPv6 Packets over Near Field Communication
draft-ietf-6lo-nfc-11 draft-ietf-6lo-nfc-12
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 April 4, 2019. This Internet-Draft will expire on May 9, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
skipping to change at page 11, line 9 skipping to change at page 11, line 9
of remaining energy, connectivity, etc.), a performance- of remaining energy, connectivity, etc.), a performance-
outstanding device can become a router. Also, they MUST deliver outstanding device can become a router. Also, they MUST deliver
their MTU information to neighbors with NFC LLCP protocols during their MTU information to neighbors with NFC LLCP protocols during
connection initialization. The router MAY also communicate other connection initialization. The router MAY also communicate other
capabilities which is out of scope of this document. capabilities which is out of scope of this document.
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
[RFC6775]. [RFC6775].
o When a NFC device becomes a 6LR or a 6LBR, the NFC device MUST
follow Section 6 and 7 of [RFC6775].
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
IPv6-over-NFC is the LOWPAN_IPHC header followed by payload, as IPv6-over-NFC is the LOWPAN_IPHC header followed by payload, as
depicted in Figure 6. depicted in Figure 6.
+---------------+---------------+--------------+ +---------------+---------------+--------------+
| IPHC Dispatch | IPHC Header | Payload | | IPHC Dispatch | IPHC Header | Payload |
 End of changes. 5 change blocks. 
4 lines changed or deleted 7 lines changed or added

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