idnits 2.17.1 draft-sarikaya-6lowpan-forwarding-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 288. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 265. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 272. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 278. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 20, 2006) is 6633 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) No issues found here. Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Sarikaya 3 Internet-Draft Futurewei Technologies 4 Expires: August 24, 2006 February 20, 2006 6 Serial forwarding approach to connecting TinyOS-based sensors to IPv6 7 Internet 8 draft-sarikaya-6lowpan-forwarding-00 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on August 24, 2006. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 This document describes a simple approach to interconnect IEEE 42 802.15.4 sensor nodes to IPv6 Internet. The technique requires a 43 gateway node that is connected to both the sensor network and the 44 IPv6 Internet. The gateway node runs the serial forwarder over IPv6. 45 Sensor nodes run the open-source TinyOS operating system and generate 46 TinyOS packets. The sensor network can be accessed from IPv6 47 Internet using a Web interface and the serial forwarder that runs in 48 the applets enables reception/transmission of TinyOS packets over 49 IPv6. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 3. Serial Forwarder . . . . . . . . . . . . . . . . . . . . . . . 5 56 4. Experimental Work . . . . . . . . . . . . . . . . . . . . . . 6 57 5. TinyOS Packet Details . . . . . . . . . . . . . . . . . . . . 7 58 6. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 8 59 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 60 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 61 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 62 9.1. Normative References . . . . . . . . . . . . . . . . . . . 11 63 9.2. Informative References . . . . . . . . . . . . . . . . . . 11 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 65 Intellectual Property and Copyright Statements . . . . . . . . . . 13 67 1. Introduction 69 This document describes the serial forwarding architecture that 70 allows interconnection of sensor networks with IPv6 Internet. 72 Serial forwarding is a different approach than the native approach 73 described in [draft-ietf-6lowpan-format-01]. In the native approach, 74 the sensor nodes are connected to IPv6 network, configure an address 75 and receive/ transmit IPv6 packets. An adaptation layer is defined 76 for 802.15.4 frame fragmentation and reassembly. The sensor node 77 that is natively connected has the option of delivering IPv6 packet 78 in the sensor network using mesh routing. 80 In this document we assume the base forwarding architecture shown in 81 Figure 1. Stargate [platformx] is a PDA with an XScale board that 82 has a serial port or USB connection to the sensor network as well as 83 802.3 interface to IPv6 Internet. This architecture is commonly used 84 to connect TinyOS [tinyos] based sensor nodes such as Telos motes. 85 Telos motes have 802.15.4 radios. TinyOS is an open-source operating 86 system designed to run on sensor nodes. 88 TinyOS IPv6 89 packet +-+ datagrams (TCP) +-+ 90 -------| |--------------------------------| | 91 ------ | | -------- | | 92 |sensor |--| |-----------| IPv6 |-----------| | 93 |network| | | |Internet| | | 94 ------ | | | | | | 95 +-+ -------- +-+ 96 Stargate IPv6 Internet Web Client 97 SFv6 server SFv6 client 99 Figure 1: Base Forwarding Architecture 101 Stargate software includes apache Web server and serial forwarder 102 which is originally developed to run in IPv4. Applications such as 103 TinyDB, an environmental monitoring application are developed using 104 Java and include an applet which is client of the serial forwarder. 105 In TinyDB, the application sends queries to the sensor network to 106 inquire about things like sensor readings and the sensor nodes send 107 replies such as their sensor readings. 109 In this document, we present an extension to the base architecture 110 for IPv6. Section 3 describes the serial forwarder, Section 4 111 presents our architecture for an IPv6 extension, Section 5 describes 112 TinyOS packet format and Section 6 presents our conclusions. 114 2. Terminology 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in BCP 14 RFC 2119 119 [STANDARDS]. 121 3. Serial Forwarder 123 Serial forwarder runs on Stargate as a TCP-based socket application. 124 Serial forwarder was originally developed as part of TinyOS project 125 and IPv4 version of the software is available in the TinyOS source 126 tree. 128 Serial forwarder (SFv4) opens a TCP port and then forwards TinyOS 129 packets from the serial port of Stargate to which an interface card 130 to the sensor network is connected to the TCP port and vice versa. 131 Web based applications such as TinyDB running on hosts contain an 132 applet which is a client of the serial forwarder. The applet 133 connects to the TCP port opened by SFv4 running on Stargate. The 134 applet receives TinyOS packets encapsulated as IPv4 TCP data. The 135 applet can also send the user queries encapsulated in TinyOS packet 136 payload as TCP data to SFv4 on Stargate and the Stargate's TinyDB 137 application is responsible for routing the query to the sensor 138 network. Routing protocol is application-dependent and is mesh- 139 oriented. 141 4. Experimental Work 143 The base architecture has two deficiencies: Stargate can not 144 efficiently run a webserver and an IPv6 version of apache for 145 Stargate was not available. The proposed extension to the base 146 architecture is shown in Figure 2. 148 TinyOS IPv6 149 packet +-+ +-+ datagrams (TCP) +-+ 150 -------| |------| |--------------------------| | 151 ------ | | | | -------- | | 152 |sensor |--| |------| |-----| IPv6 |-----------| | 153 |network| | | | | |Internet| | | 154 ------ | | | | | | | | 155 +-+ +-+ -------- +-+ 156 Stargate Web Server IPv6 Web Client 157 SFv6 Server SFv6 Client Internet 158 SFv6 Server SFv6 Client 160 Figure 2: Experimental Forwarding Architecture 162 We first ported SFv4 into IPv6 and the resulting software is called 163 serial forwarder v6 (SFv6). SFv6 running on Stargate opens a TCP 164 port and forwards TinyOS packets back and fort from the serial port 165 to TCP port. 167 We developed a serial forwarder v6 to be run on an IPv6 host. This 168 version of SFv6 connects to the TCP port at Stargate and opens a TCP 169 port itself. 171 Applications in IPv6 Internet need to run a serial forwarder that 172 connects to the TCP port of SFv6 that runs on the host. We modified 173 TinyDB Java applet for this purpose and obtained the applet that runs 174 as SFv6 client. 176 5. TinyOS Packet Details 178 TinyOS packet has the format shown in Figure 3. 180 +----------------------------------------------+ 181 | FCF | DSN | Dest |Source| Type|Group ID| Data| 182 +----------------------------------------------+ 183 | 2 | 1 | 2 | 2 | 1 | 1 | 28 | 184 +----------------------------------------------+ 186 Figure 3: TinyOS Packet Format 188 where FCF is the frame control field and is 2 octets, DSN is 1 octet 189 and is the destination sequence number. The Dest and Source fields 190 are 2 octets and Dest is destination PAN identifier and Source is 191 source sensor node ID (MAC address). Type field is 1 octet long and 192 is the message type. Group ID is 1 octet long. User data (payload) 193 is placed in the data field and is 28 octets long. 195 This format is used for IEEE 802.15.4 based sensor nodes such as 196 Telos motes. Some fields like FCF, DSN, Dest and Group ID are Zigbee 197 MAC layer specific. 199 6. Conclusions 201 We presented an alternative architecture for connecting Zigbee based 202 sensor nodes to IPv6 Internet. Our architecture is based on a PDA 203 that connects both the sensor network and IPv6 Internet. There is no 204 need for an adaptation layer on sensor nodes in order to fragment/ 205 reassemble 802.15.4 MAC frames. The application has to be aware of 206 the frame format and be capable of receiving the data and generating 207 queries to the sensor network. 209 7. Security Considerations 211 Security of the serial forwarder can be divided into two parts: IPv6 212 Internet and the sensor network. The security in the sensor network 213 can be provided using link-layer mechanisms defined by IEEE 802.15.4. 214 IPv6 Internet communication is on TCP and application-oriented. Such 215 a communication should be secured using TLS. 217 8. Acknowledgements 219 The author gratefully acknowledges the contributions of Abbie Zheng 220 of UNBC. 222 9. References 224 9.1. Normative References 226 [STANDARDS] 227 "Key words for use in RFCs to Indicate Requirement 228 Levels", RFC 2119, March 1997, 229 . 231 9.2. Informative References 233 [draft-ietf-6lowpan-format-01] 234 Montenegro, G. and N. Kushalnagar, "Transmission of IPv6 235 Packets over IEEE 802.15.4 Networks", October 2005, . 239 [platformx] 240 "Stargate: A PlatformX Project", February 2006, 241 . 243 [tinyos] "TinyOS CVS Source Tree", February 2006, 244 . 246 Author's Address 248 Behcet Sarikaya 249 Futurewei Technologies 250 1700 Alma Dr. Suite 100 251 Plano, TX 75075 253 Phone: +1 972-509-5599 254 Email: bsarikaya@huawei.com 256 Intellectual Property Statement 258 The IETF takes no position regarding the validity or scope of any 259 Intellectual Property Rights or other rights that might be claimed to 260 pertain to the implementation or use of the technology described in 261 this document or the extent to which any license under such rights 262 might or might not be available; nor does it represent that it has 263 made any independent effort to identify any such rights. Information 264 on the procedures with respect to rights in RFC documents can be 265 found in BCP 78 and BCP 79. 267 Copies of IPR disclosures made to the IETF Secretariat and any 268 assurances of licenses to be made available, or the result of an 269 attempt made to obtain a general license or permission for the use of 270 such proprietary rights by implementers or users of this 271 specification can be obtained from the IETF on-line IPR repository at 272 http://www.ietf.org/ipr. 274 The IETF invites any interested party to bring to its attention any 275 copyrights, patents or patent applications, or other proprietary 276 rights that may cover technology that may be required to implement 277 this standard. Please address the information to the IETF at 278 ietf-ipr@ietf.org. 280 Disclaimer of Validity 282 This document and the information contained herein are provided on an 283 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 284 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 285 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 286 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 287 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 288 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 290 Copyright Statement 292 Copyright (C) The Internet Society (2006). This document is subject 293 to the rights, licenses and restrictions contained in BCP 78, and 294 except as set forth therein, the authors retain all their rights. 296 Acknowledgment 298 Funding for the RFC Editor function is currently provided by the 299 Internet Society.