idnits 2.17.1 draft-ietf-6lowpan-btle-04.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 -- The document date (November 23, 2011) is 4509 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) == Missing Reference: 'RFC4861' is mentioned on line 291, but not defined == Missing Reference: 'RFC3610' is mentioned on line 426, but not defined == Unused Reference: 'RFC4994' is defined on line 474, but no explicit reference was found in the text == Outdated reference: A later version (-21) exists of draft-ietf-6lowpan-nd-18 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 6LoWPAN Working Group J. Nieminen, Ed. 2 Internet-Draft B. Patil 3 Intended status: Standards Track T. Savolainen 4 Expires: May 26, 2012 M. Isomaki 5 Nokia 6 Z. Shelby 7 Sensinode 8 C. Gomez 9 Universitat Politecnica de 10 Catalunya/i2CAT 11 November 23, 2011 13 Transmission of IPv6 Packets over Bluetooth Low Energy 14 draft-ietf-6lowpan-btle-04 16 Abstract 18 Bluetooth Low Energy is a low power air interface technology defined 19 by the Bluetooth Special Interest Group (BT SIG). The standard 20 Bluetooth radio has been widely implemented and available in mobile 21 phones, notebook computers, audio headsets and many other devices. 22 The low power version of Bluetooth is a new specification and enables 23 the use of this air interface with devices such as sensors, smart 24 meters, appliances, etc. The low power variant of Bluetooth is 25 commonly specified in revision 4.0 of the Bluetooth specifications 26 and commonly refered to as Bluetooth 4.0. This document describes 27 how IPv6 is transported over Bluetooth Low Energy 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 26, 2012. 47 Copyright Notice 48 Copyright (c) 2011 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 65 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 66 2. Bluetooth Low Energy . . . . . . . . . . . . . . . . . . . . . 4 67 2.1. Bluetooth Low Energy stack . . . . . . . . . . . . . . . . 4 68 2.2. Link layer roles and topology . . . . . . . . . . . . . . 5 69 2.3. BT-LE device addressing . . . . . . . . . . . . . . . . . 5 70 2.4. BT-LE packets sizes and MTU . . . . . . . . . . . . . . . 5 71 3. Specification of IPv6 over Bluetooth Low Energy . . . . . . . 6 72 3.1. Protocol stack . . . . . . . . . . . . . . . . . . . . . . 6 73 3.2. Link model . . . . . . . . . . . . . . . . . . . . . . . . 7 74 3.2.1. IPv6 Address configuration . . . . . . . . . . . . . . 7 75 3.2.2. Header compression . . . . . . . . . . . . . . . . . . 8 76 3.2.3. Unicast and Multicast address mapping . . . . . . . . 9 77 3.3. Internet connectivity scenarios . . . . . . . . . . . . . 9 78 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 79 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 80 6. Additional contributors . . . . . . . . . . . . . . . . . . . 10 81 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 82 8. Normative References . . . . . . . . . . . . . . . . . . . . . 10 83 Appendix A. Bluetooth Low Energy fragmentation and L2CAP Modes . 11 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 86 1. Introduction 88 Bluetooth Low Energy (BT-LE) is a radio technology targeted for 89 devices that operate with coin cell batteries or minimalistic power 90 sources, which means that low power consumption is essential. BT-LE 91 is an especially attractive technology for the Internet of Things 92 applications, such as health monitors, environmental sensing, 93 proximity applications and many others. 95 Considering the potential for the exponential growth in the number of 96 sensors and Internet connected devices and things, IPv6 is an ideal 97 protocol due to the large address space it provides. In addition, 98 IPv6 provides tools for autoconfiguration, which is particularly 99 suitable for sensor network applications and nodes which have very 100 limited processing power or a full-fledged operating system. 102 [RFC4944] specifies the transmission of IPv6 over IEEE 802.15.4. The 103 Bluetooth Low Energy link in many respects has similar 104 characteristics to that of IEEE 802.15.4. Many of the mechanisms 105 defined in [RFC4944] can be applied to the transmission of IPv6 on 106 Bluetooth Low Energy links. This document specifies the details of 107 IPv6 transmission over Bluetooth Low Energy links. 109 1.1. Requirements Language 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in RFC 2119 [RFC2119]. 115 1.2. Terminology 117 Bluetooth Low Energy 119 Bluetooth Low Energy is a low power air interface technology 120 specified by the Bluetooth Special Interest Group (SIG). BT-LE is 121 specified in Revision 4.0 of the Bluetooth specifications (BT 122 4.0). 124 Gateway 126 Network element connecting the BT-LE sensors to the Internet. Can 127 be e.g a home gateway or a mobile device. 129 6LR and 6LBR 131 These terms correspond to those defined in [I-D.ietf-6lowpan-nd] 133 2. Bluetooth Low Energy 135 BT-LE is designed for transferring small amounts of data infrequently 136 at modest data rates at a very low cost per bit. 138 BT-LE is an integral part of the BT 4.0 specification [BTCorev4.0]. 139 Devices such as mobile phones, notebooks, tablets and other handheld 140 computing devices which include BT 4.0 chipsets also have the low- 141 energy functionality of Bluetooth. BT-LE is also included in many 142 different types of accessories that collaborate with mobile devices 143 such as phones, tablets and notebook computers. An example of a use 144 case for a BT-LE accessory is a heart rate monitor that sends data 145 via the mobile phone to a server on the Internet. 147 2.1. Bluetooth Low Energy stack 149 The lower layer of the BT-LE stack consists of the Physical (PHY) and 150 the Link Layer (LL). The Physical Layer transmits and receives the 151 actual packets. The Link Layer is responsible for providing medium 152 access, connection establishment, error control and flow control. 153 The upper layer consists of the Logical Link Control and Adaptation 154 Protocol (L2CAP), Generic Attribute protocol (GATT) and Generic 155 Access Profile (GAP) as shown in Figure 1. GATT and BT-LE profiles 156 together enable the creation of applications in a standardized way 157 without using IP. L2CAP provides multiplexing capability by 158 multiplexing the data channels from the above layers. L2CAP also 159 provides fragmentation and reassembly for large data packets. 161 +----------------------------------------+------------------+ 162 | Applications | 163 +----------------------------------------+------------------+ 164 | Generic Attribute Profile | Generic Access | 165 +----------------------------------------+ Profile | 166 | Attribute Protocol |Security Manager | | 167 +--------------------+-------------------+------------------+ 168 | Logical Link Control and Adaptation | 169 +--------------------+-------------------+------------------+ 170 | Host Controller Interface | 171 +--------------------+-------------------+------------------+ 172 | Link Layer | Direct Test Mode | 173 +--------------------+-------------------+------------------+ 174 | Physical Layer | 175 +--------------------+-------------------+------------------+ 177 Figure 1: BT-LE Protocol Stack 179 2.2. Link layer roles and topology 181 BT-LE defines two Link Layer roles: the Master Role and the Slave 182 Role. A device in the Master Role, which is called master, can 183 manage multiple simultaneous connections with a number of devices in 184 the Slave Role, called slaves. A slave can only be connected to a 185 single master. Hence, a BT-LE network (i.e. a BT-LE piconet) follows 186 a star topology. 188 [BTLE-Slave]-----\ /-----[BTLE-Slave] 189 \ / 190 [BTLE-Slave]-----/[BTLE-Master]/-----[BTLE-Slave] 191 / \ 192 [BTLE-Slave]-----/ \-----[BTLE-Slave] 194 Figure 2: BT-LE Star Topology 196 A master is assumed to be less constrained than a slave. Hence, 197 master and slave can correspond with 6LoWPAN Border Router (6LBR) and 198 host, respectively. 200 In BT-LE, communication only takes place between a master and a 201 slave. Hence, in a BT-LE network using IP, a radio hop is equivalent 202 to an IP link and vice versa. 204 2.3. BT-LE device addressing 206 Every BT-LE device is identified by a unique 48 bit Bluetooth Device 207 Address (BD_ADDR). An BT-LE-only device such as a sensor may use a 208 public (obtained from IEEE Registration Authority) or a random device 209 address (generated internally). The public address is created 210 according to the IEEE 802-2001 standard and using a valid 211 Organizationally Unique Identifier (OUI) obtained from the IEEE 212 Registration Authority. This specification mandates that the 213 Bluetooth Device Address MUST be a public address. 215 2.4. BT-LE packets sizes and MTU 217 Maximum size of the payload in a BT-LE data channel PDU is 27 bytes. 218 Depending on the L2CAP mode in use, the amount of data available for 219 transporting IP bytes in a single BT-LE data channel PDU ranges 220 between 19 and 27 octets. For power efficient communication between 221 two BT-LE devices, data and its header should fit in a single BT-LE 222 data channel PDU. MTU larger than the above mentioned values can be 223 supported by the L2CAP specification. The Basic L2CAP Mode allows a 224 maximum payload size (i.e. IP datagram size) of 65535 bytes per 225 L2CAP PDU. The rest of L2CAP modes allow a maximum payload size that 226 ranges between 65527 and 65533 bytes per L2CAP PDU. 228 3. Specification of IPv6 over Bluetooth Low Energy 230 BT-LE technology sets strict requirements for low power consumption 231 and thus limits the allowed protocol overhead. 6LoWPAN standard 232 [RFC4944], [I-D.ietf-6lowpan-nd] and [RFC6282] provides useful 233 generic functionality like header compression, link-local IPv6 234 addresses, Neighbor Discovery and stateless IP-address 235 autoconfiguration for reducing the overhead in 802.15.4 networks. 236 This functionality can be partly applied to BT-LE. 238 A significant difference between IEEE 802.15.4 and BT-LE is that the 239 former supports the mesh topology (and requires a routing protocol), 240 whereas BT-LE does not currently support the formation of multihop 241 networks. In consequence, the mesh header defined in [RFC4944] for 242 mesh under routing MUST NOT be used in BT-LE networks. On the other 243 hand, a BT-LE device MUST NOT play the role of a 6LoWPAN Router 244 (6LR). 246 The maximum payload size of a BT-LE data channel PDU is 27 bytes, 247 from which L2CAP headers may consume additional bytes. However, IP 248 data packets may be much larger and IPv6 requires support for an MTU 249 of 1280 bytes. Fragmentation and Recombination (FAR) functionality 250 is an inherent function of the BT-LE L2CAP layer. Larger L2CAP 251 packets can be transferred with the assistance of the FAR 252 functionality. Appendix A describes FAR operation and five L2CAP 253 Modes. This specification requires that FAR functionality MUST be 254 provided in the L2CAP layer up to the IPv6 minimum MTU of 1280 bytes. 255 The corresponding L2CAP Mode MUST be Basic Mode. Since FAR in BT-LE 256 is a function of the L2CAP layer, fragmentation functionality as 257 defined in [RFC4944] MUST NOT be used in BT-LE networks. 259 3.1. Protocol stack 261 In order to enable transmission of IPv6 packets over BT-LE, a new 262 fixed L2CAP channel ID MUST be reserved for IPv6 traffic by the BT- 263 SIG. A request for allocation of a new fixed channel ID for IPv6 264 traffic by the BT-SIG should be submitted through the liaison process 265 or formal communique from the 6lowpan chairs and respective area 266 directors. This specification defines the use of channel ID 0x0007 267 for this purpose. Figure 3 illustrates IPv6 over BT-LE stack. 269 +-------------------+ 270 | UDP/TCP | 271 +-------------------+ 272 | IPv6 | 273 +-------------------+ 274 | 6LoWPAN adapted | 275 | to BT-LE | 276 +-------------------+ 277 | BT-LE L2CAP | 278 +-------------------+ 279 | BT-LE Link Layer | 280 +-------------------+ 281 | BT-LE Physical | 282 +-------------------+ 284 Figure 3: IPv6 over BT-LE Stack 286 3.2. Link model 288 The concept of IP link (layer 3) and the physical link (combination 289 of PHY and MAC) needs to be clear and the relationship has to be well 290 understood in order to specify the addressing scheme for transmitting 291 IPv6 packets over the BT-LE link. [RFC4861] defines a link as "a 292 communication facility or medium over which nodes can communicate at 293 the link layer, i.e., the layer immediately below IP." 295 In the case of BT-LE, L2CAP is an adaptation layer that supports the 296 transmission of IPv6 packets. L2CAP also provides multiplexing 297 capability in addition to FAR functionality. 299 The BT-LE link between two communicating nodes can be considered to 300 be a point-to-point or point-to-multipoint link. When one of the 301 communicating nodes is in the role of a master, then the link can be 302 viewed as a point-to-multipoint link. 304 When a host connects to another BT-LE device the link is up and IP 305 address configuration and transmission can occur. 307 3.2.1. IPv6 Address configuration 309 The Interface Identifier (IID) for a BT-LE interface MUST be formed 310 from the 48-bit public device Bluetooth address as per the "IPv6 over 311 Ethernet" specification [RFC2464]. An IPv6 prefix used for stateless 312 autoconfiguration [RFC4862] of a BT-LE interface MUST have a length 313 of 64 bits. Thus, this prefix is EUI-64 compliant. 315 The IPv6 link-local address [RFC4291] for a BT-LE interface is formed 316 by appending the IID, as defined above, to the prefix FE80::/64, as 317 depicted in Figure 4. 319 10 bits 54 bits 64 bits 320 +----------+-----------------+----------------------+ 321 |1111111010| zeros | Interface Identifier | 322 +----------+-----------------+----------------------+ 324 Figure 4: IPv6 link-local address in BT-LE 326 3.2.2. Header compression 328 This document assumes [RFC6282], which specifies the compression 329 format for IPv6 datagrams on top of IEEE 802.15.4, as the basis for 330 IPv6 header compression on top of BT-LE. It is required that all 331 headers MUST be compressed according to HC base encoding. The 332 following text describes the principles of IPv6 address compression 333 on top of BT-LE. 335 In a link-local communication, both the IPv6 source and destination 336 addresses MUST be elided. In this type of communication, a node that 337 receives a data channel PDU containing an IPv6 packet (or a part of 338 it) can infer that the IPv6 destination address of the packet is its 339 own IPv6 address. On the other hand, a node SHALL learn the IID of 340 the other endpoint of each L2CAP connection it participates in. By 341 exploiting this information, a node that receives a data channel PDU 342 containing an IPv6 packet (or a part of it) can infer the 343 corresponding IPv6 source address. A device MAY learn the IID of the 344 other endpoint of an L2CAP connection e.g. from the RS/RA/NS/NA 345 Neighbor Discovery (ND) message exchange [I-D.ietf-6lowpan-nd]. A 346 device MAY also derive the IID of the other endpoint of a L2CAP 347 connection from the Link Layer connection establishment messages. 348 The device MUST maintain a Neighbor Cache, in which the entries 349 include both the IID of the neighbor and the Device Address that 350 identifies the neighbor. 352 When a BT-LE slave transmits an IPv6 packet to a remote destination 353 using global IPv6 addresses, the slave MUST elide the IPv6 source 354 address. The 6LBR/master can infer the elided IPv6 source address 355 since 1) the master/6LBR has previously assigned the prefix to the 356 slaves; and 2) the master/6LBR maintains a Neighbor Cache that 357 relates the Device Address and the IID of the corresponding slave. 358 If a context is defined for the IPv6 destination address, the slave 359 MUST also elide the prefix of the destination IPv6 address. In that 360 case, the 6LBR/master can infer the elided destination prefix by 361 using the context. 363 When a master/6LBR receives an IPv6 packet sent by a remote node 364 outside the BT-LE network, and the destination of the packet is a 365 slave, the master/6LBR MUST elide the IPv6 destination address of the 366 packet before forwarding it to the slave. The slave can infer that 367 the IPv6 destination address of the packet is its own IPv6 address. 368 If a context is defined for the prefix of the IPv6 source address, 369 the master/6LBR MUST elide that prefix as well. 371 3.2.3. Unicast and Multicast address mapping 373 The BT-LE link layer does not support multicast. Hence traffic is 374 always unicast between two BT-LE devices. Even in the case where a 375 master is attached to multiple slave BT-LE devices, the master device 376 cannot do a multicast to all the connected slave devices. If the 377 master device needs to send a multicast packet to all its slave 378 devices, it has to replicate the packet and unicast it on each link. 379 However, this may not be energy-efficient and particular care must be 380 taken if the master is battery-powered. In the opposite direction, a 381 slave can only transmit data to a single destination (i.e. the 382 master). Hence, if a slave transmits an IPv6 multicast packet, the 383 slave can unicast the corresponding BT-LE packet to the master. It 384 is required that the master MUST provide a table for mapping 385 different types of multicast addresses (all-nodes, all-routers and 386 solicited-node multicast addresses) to the corresponding IIDs and 387 Device Addresses. 389 3.3. Internet connectivity scenarios 391 In a typical scenario, BT-LE network is connected to the Internet. 393 h ____________ 394 \ / \ 395 h ---- 6LBR --- | Internet | 396 / \____________/ 397 h 398 h: host 399 <-- BT-LE --> 6LBR: 6LoWPAN Border Router 401 Figure 5: BT-LE network connected to the Internet 403 In some scenarios, the BT-LE network may transiently or permanently 404 be an isolated network. 406 h h h: host 407 \ / 6LBR: 6LoWPAN Border Router 408 h --- 6LBR -- h 409 / \ 410 h h 412 Figure 6: Isolated BT-LE network 414 4. IANA Considerations 416 While there are no actions for IANA, we do expect BT SIG to allocate 417 an L2CAP channel ID. 419 5. Security Considerations 421 The transmission of IPv6 over BT-LE links has similar requirements 422 and concerns for security as for IEEE 802.15.4. IPv6 over BT-LE 423 SHOULD be protected by using BT-LE Link Layer security. 425 BT-LE Link Layer supports encryption and authentication by using the 426 Counter with CBC-MAC (CCM) mechanism [RFC3610] and a 128-bit AES 427 block cipher. Upper layer security mechanisms may exploit this 428 functionality when it is available. (Note: CCM does not consume 429 bytes from the maximum per-packet L2CAP data size, since the link 430 layer data unit has a specific field for them when they are used.) 432 Key management in BT-LE is provided by the Security Manager Protocol 433 (SMP). 435 6. Additional contributors 437 Kanji Kerai, Jari Mutikainen, David Canfeng-Chen and Minjun Xi from 438 Nokia have contributed significantly to this document. 440 7. Acknowledgements 442 Samita Chakrabarti and Erik Nordmark have provided valuable feedback 443 for this draft. 445 8. Normative References 447 [BTCorev4.0] 448 "Bluetooth Core Specification v4.0, http:// 449 www.bluetooth.com/English/Technology/Building/Pages/ 450 Specification.aspx". 452 [I-D.ietf-6lowpan-nd] 453 Shelby, Z., Chakrabarti, S., and E. Nordmark, "Neighbor 454 Discovery Optimization for Low Power and Lossy Networks 455 (6LoWPAN)", draft-ietf-6lowpan-nd-18 (work in progress), 456 October 2011. 458 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 459 Requirement Levels", BCP 14, RFC 2119, March 1997. 461 [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet 462 Networks", RFC 2464, December 1998. 464 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 465 Architecture", RFC 4291, February 2006. 467 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 468 Address Autoconfiguration", RFC 4862, September 2007. 470 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 471 "Transmission of IPv6 Packets over IEEE 802.15.4 472 Networks", RFC 4944, September 2007. 474 [RFC4994] Zeng, S., Volz, B., Kinnear, K., and J. Brzozowski, 475 "DHCPv6 Relay Agent Echo Request Option", RFC 4994, 476 September 2007. 478 [RFC6282] Hui, J. and P. Thubert, "Compression Format for IPv6 479 Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, 480 September 2011. 482 Appendix A. Bluetooth Low Energy fragmentation and L2CAP Modes 484 This section provides an overview of Fragmentation and Recombination 485 (FAR) method and L2CAP modes in Bluetooth Low Energy. FAR is an 486 L2CAP mechanism, in which an L2CAP entity can take the (large) upper 487 layer PDU, prepend the L2CAP header (4 bytes in the Basic L2CAP mode) 488 and break the resulting L2CAP PDU into fragments which can then be 489 directly encapsulated into Data channel PDUs. There are bits in the 490 Data channel PDUs which identify whether the payload is a complete 491 L2CAP PDU or the first of a set of fragments, or one of the rest of 492 the fragments. 494 There are five L2CAP modes defined in the BT 4.0 spec. These modes 495 are: Retransmission Mode (a Go-Back-N mechanism is used), Enhanced 496 Retransmission Mode (includes selective NAK among others), Flow 497 Control Mode (PDUs are numbered, but there are no retransmissions), 498 Streaming Mode (PDUs are numbered, but there are no ACKs of any kind) 499 and Basic L2CAP Mode. 501 Authors' Addresses 503 Johanna Nieminen (editor) 504 Nokia 505 Itaemerenkatu 11-13 506 FI-00180 Helsinki 507 Finland 509 Email: johanna.1.nieminen@nokia.com 511 Basavaraj Patil 512 Nokia 513 6021 Connection drive 514 Irving, TX 75039 515 USA 517 Email: basavaraj.patil@nokia.com 519 Teemu Savolainen 520 Nokia 521 Hermiankatu 12 D 522 FI-33720 Tampere 523 Finland 525 Email: teemu.savolainen@nokia.com 527 Markus Isomaki 528 Nokia 529 Keilalahdentie 2-4 530 FI-02150 Espoo 531 Finland 533 Email: markus.isomaki@nokia.com 534 Zach Shelby 535 Sensinode 536 Hallituskatu 13-17D 537 FI-90100 Oulu 538 Finland 540 Email: zach.shelby@sensinode.com 542 Carles Gomez 543 Universitat Politecnica de Catalunya/i2CAT 544 C/Esteve Terradas, 7 545 Castelldefels 08860 546 Spain 548 Email: carlesgo@entel.upc.edu