idnits 2.17.1 draft-bi-savi-wlan-14.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 (March 25, 2018) is 2214 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) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Bi 3 Internet-Draft J. Wu 4 Intended status: Standards Track Y. Wang 5 Expires: September 26, 2018 Tsinghua University 6 T. Lin 7 New H3C Technologies Co. Ltd 8 March 25, 2018 10 A SAVI Solution for WLAN 11 draft-bi-savi-wlan-14 13 Abstract 15 This document describes a source address validation solution for WLAN 16 enabling 802.11i or other security mechanisms. This mechanism snoops 17 NDP and DHCP packets to bind IP address to MAC address, and relies on 18 the security of MAC address guaranteed by 802.11i or other mechanisms 19 to filter IP spoofing packets. It can work in the special situations 20 described in the charter of SAVI(Source Address Validation 21 Improvements) workgroup, such as multiple MAC addresses on one 22 interface. This document describes three different deployment 23 scenarios, with solutions for migration of binding entries when hosts 24 move from one access point to another. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on September 26, 2018. 43 Copyright Notice 45 Copyright (c) 2018 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. Conventions used in this document . . . . . . . . . . . . . . 3 63 3. IP-MAC Binding . . . . . . . . . . . . . . . . . . . . . . . 3 64 3.1. Data Structures . . . . . . . . . . . . . . . . . . . . . 3 65 3.1.1. IP-MAC Mapping Table . . . . . . . . . . . . . . . . 3 66 3.1.2. MAC-IP Mapping Table . . . . . . . . . . . . . . . . 4 67 3.2. Pre-conditions for binding . . . . . . . . . . . . . . . 4 68 3.3. Binding IP addresses to MAC addresses . . . . . . . . . . 5 69 3.4. Binding Migration . . . . . . . . . . . . . . . . . . . . 5 70 3.5. Binding Clearing . . . . . . . . . . . . . . . . . . . . 6 71 4. Source Address Validation . . . . . . . . . . . . . . . . . . 6 72 5. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . 7 73 5.1. Centralized WLAN . . . . . . . . . . . . . . . . . . . . 7 74 5.1.1. AP Filtering . . . . . . . . . . . . . . . . . . . . 7 75 5.1.2. AC Filtering . . . . . . . . . . . . . . . . . . . . 11 76 5.2. Autonomous WLAN . . . . . . . . . . . . . . . . . . . . . 12 77 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 78 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 79 7.1. Issues with Triggerring Establishment of Binding Entries 80 by Data Packets . . . . . . . . . . . . . . . . . . . . . 12 81 7.2. Privacy Considerations . . . . . . . . . . . . . . . . . 13 82 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 83 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 84 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 85 9.2. Informative References . . . . . . . . . . . . . . . . . 14 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 88 1. Introduction 90 This document describes a mechanism to perform per packet IP source 91 address validation in WLAN. This mechanism performs ND snooping or 92 DHCP snooping to bind allocated IP address with authenticated MAC 93 address. Static addresses are bound to the MAC addresses of 94 corresponding hosts manually. Then the mechanism can check validity 95 of source IP address in local packets according to the binding 96 association. The security of MAC address is assured by 802.11i or 97 other mechanisms, thus the binding association is secure. 99 The situation that one interfaces with multiple MAC addresses is a 100 special case mentioned in the charter of SAVI. And this situation is 101 the only special case that challenges MAC-IP binding. The mechanism 102 to handle this situation is specified in the document. 104 There are three deployment scenarios specified in this document. The 105 mechanism is deployed on different devices in different scenarios. 106 The deployment detail is described in the document. 108 When hosts move from one access point to another, the migration of 109 binding entries may be triggered according to the specific mobility 110 scenario. The mechanism to handle host mobility is specified in the 111 document according to different deployment scenarios. 113 1.1. Terminology 115 FIT Access Points: the name of Access Points in Centralized WLAN 116 deployment scenario. 118 FAT Access Points: the name of Access Points in Autonomous WLAN 119 deployment scenario. 121 2. Conventions used in this document 123 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 124 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 125 document are to be interpreted as described in RFC-2119 [RFC2119]. 127 3. IP-MAC Binding 129 This section specifies the operations for creating and clearing of 130 bindings between IP addresses to MAC addresses. 132 3.1. Data Structures 134 3.1.1. IP-MAC Mapping Table 136 This table maps IP addresses to corresponding MAC addresses. IP 137 address is the index of the table. One IP address can only have one 138 corresponding MAC address, while different IP addresses can be mapped 139 to the same MAC address. 141 This table is used in control process. Before creating new IP-MAC 142 bindings, this table must first be consulted in case of conflict in 143 binding entries. Also, this table must be consulted before doing any 144 packet filtering. This table must be synchronized with the MAC-IP 145 table specified in Section 3.1.2. 147 Each entry in IP-MAC mapping table must also record the binding state 148 of the IP address. Addresses snooped in DHCP address assignment 149 procedure must record its state as "DHCPv6", and addresses snooped in 150 Duplicate Address Detection procedure must record its state as 151 "SLAAC". 153 Each entry in IP-MAC mapping table has its lifetime. According to 154 RFC3315 [RFC3315], the address allocated by DHCP has a limited 155 lifetime, so the related entry records its lifetime the same as that 156 of the address. According to RFC4862 [RFC4862], stateless address 157 also has a limited lifetime, and the host set this lifetime by 158 itself. Thus the related entry also records its lifetime the same as 159 that of the address. 161 3.1.2. MAC-IP Mapping Table 163 This table maps MAC addresses to corresponding IP addresses. MAC 164 address is the index of the table. It is a one-to-many mapping 165 table, which means a MAC address can be mapped to multiple IP 166 addresses. Though multiple MAC addresses may exist on one interface, 167 these MAC addresses must be mapped to different IP addresses. 169 This table is used for filtering. Different from wired network, MAC- 170 IP mapping table and IP-MAC mapping table can be maintained 171 separately on different devices. Mechanisms for synchronization 172 between the two tables must be employed for the consistency of the 173 bindings. We will specify the details in Section 5 according to 174 different deployment scenarios. 176 3.2. Pre-conditions for binding 178 In the binding based mechanism, the security of IP address is based 179 on the security of the binding anchor. In WLAN, a number of security 180 mechanisms on link layer make MAC address a strong enough binding 181 anchor, for instance, 802.11i, WAPI, WEP. 183 If MAC address has no protection, attackers can spoof MAC address to 184 succeed in validation. However, in general cases, if MAC address is 185 not protected, more serious attack can be launched than IP spoofing 186 attack. 188 3.3. Binding IP addresses to MAC addresses 190 All the static IP-MAC address pairs are configured into the IP-MAC 191 Mapping Table with the mechanism enabled. 193 An individual procedure handles binding DHCP addresses to MAC 194 addresses. This procedure snoops the DHCP address assignment 195 procedure between attached hosts and DHCP server. DHCP snooping in 196 WLAN is the same as that in wired network specified in RFC7513 197 [RFC7513]. 199 An individual procedure handles binding stateless addresses to MAC 200 addresses. This procedure snoops Duplicate Address Detection 201 procedure. ND snooping in WLAN is the same as that in wired network 202 specified in [RFC6620] [RFC6620]. 204 Data packets MAY also trigger the establishment of new IP-MAC binding 205 entries. Data packet with non-bound source IP address with a limited 206 rate is collected to handle DAD message loss in SLAAC procedure, 207 which can be quite frequent in wireless network. The detail of the 208 procedure is specified in Section 4. However, this mechanism will 209 bring potential security risks (e.g. attacks that aimed at exhausting 210 available IP addresses). Thus, it is optional whether to enable the 211 mechanism, and if it is enabled, additional security mechanisms MUST 212 also be employed to cope with the risks. Related security 213 considerations are discussed in Section 6. 215 In some deployment scenarios, the function of address snooping and 216 IP-MAC table maintaining may also be separated onto different 217 devices. Thus to prevent conflictions in binding entries, the device 218 snoops addresses must have interactions with the device maintains the 219 IP-MAC table. We will specify the details in Section 5.1.1. 221 3.4. Binding Migration 223 Different from wired network, SAVI for WLAN must handle migration of 224 binding entries when mobile hosts move from one access point to 225 another. After movement, hosts will not perform another address 226 allocation procedure to obtain new IP addresses, but continue to use 227 the existing IP address. Thus binding entries in the foreign device 228 that the mobile hosts access to cannot be established by snooping. A 229 new mechanism is needed to correctly migrate the binding entry 230 related to the IP address of the mobile host from the home device to 231 the foreign device. We will specify the details in Section 5, 232 according to different deployment scenarios. 234 3.5. Binding Clearing 236 Three kinds of events will trigger binding clearing: 238 1. The lifetime of an IP address in one entry has expired. This IP 239 entry in IP-MAC mapping table and corresponding entries in MAC-IP 240 mapping table MUST be cleared. 242 2. A host leaves this access point. The entries for all related MAC 243 addresses in MAC-IP table MUST be cleared. 245 3. A DHCP RELEASE message is received from the owner of 246 corresponding IP address. This IP entry in IP-MAC mapping table 247 and corresponding entries in MAC-IP mapping table MUST be 248 cleared. 250 4. Source Address Validation 252 This section describes source address validation procedure on packet. 253 In this procedure, all the frames are assumed to have passed the 254 verifications of 802.11i or other security mechanisms. 256 This procedure has the following steps: 258 1. Extract the IP source and MAC source from the frame. Lookup the 259 MAC address in the MAC-IP Mapping Table and check if the MAC-IP 260 pair exists. If yes, forward the packet. Or else go to step 2. 262 2. Lookup the IP address in the IP-MAC Mapping Table and check if 263 the IP address exists. If no, go to step 3. If yes, check 264 whether The MAC address in the entry is the same as that in the 265 frame. If yes, forward the packet. Else drop the packet. 267 3. If the mechanism that allows data packets to trigger the 268 establishment of new IP-MAC binding entries is enabled, insert a 269 new entry into the IP-MAC Mapping Table and forward the packet. 270 Otherwise drop the packet. 272 In step 2, after the packet is judged valid and forwarded, 273 synchronization between the MAC-IP and IP-MAC mapping table should be 274 triggered. The MAC-IP binding of the packet should be synchronized 275 from IP-MAC mapping table to MAC-IP mapping table and thus the 276 following packets with the same MAC-IP pair will be forwarded without 277 going to step 2. 279 Also in step 3, if a new IP-MAC binding entry is established, it 280 should be synchronized to MAC-IP mapping table. 282 5. Deployment Scenarios 284 This section specifies three deployment scenarios including two under 285 centralized WLAN and one under autonomous WLAN. The deployment 286 details and solutions for host mobility between access points are 287 described respectively in each scenario. 289 5.1. Centralized WLAN 291 Centralized WLAN is comprised of FIT Access Points (AP) and Access 292 Controllers (AC). In this scenario, this document proposes the 293 following two deployment solutions. 295 5.1.1. AP Filtering 297 With this deployment solution, data packets received by the APs do 298 not go through the ACs and only control packets (including 299 questionable data packets) go through the ACs. In this scenario, AC 300 maintains IP-MAC Mapping Table while AP maintains MAC-IP Mapping 301 Table and perform address snooping. 303 5.1.1.1. Candidate Binding 305 AP executes the procedure specified in Section 3.3. Candidate 306 binding is generated after snooping procedure. Candidate binding 307 must be confirmed by AC to be valid. 309 After a candidate binding is generated, AC is notified and checks 310 whether the binding is valid or not. The validity of a candidate 311 binding is determined if the binding does not violate any existing 312 bindings in the IP-MAC Mapping Table. Otherwise if an address is not 313 suitable for a host to use, AC notifies the corresponding AP. If the 314 candidate binding is valid, AC adds an entry into the IP-MAC Mapping 315 Table and notifies AP. Afterwards AP also adds an entry into the 316 local MAC-IP Mapping Table. 318 5.1.1.2. Packet Filtering 320 As specified in Section 4, for incoming data packets, AP looks up the 321 MAC address in the local MAC-IP Mapping Table and check if the MAC-IP 322 pair exists. If yes, AP forwards the packet. Or else AP delivers 323 the packet to AC for further processing. 325 When receiving data packets from AP, AC Looks up the IP address in 326 the local IP-MAC Mapping Table and checks if the IP address exists. 327 If no, according to whether the AC is configured to allow data 328 packets to trigger binding entry creations, AC establishes a new IP- 329 MAC entry then forwards the packet, or drop the packet. If yes, AC 330 checks whether The MAC address in the entry is the same as that in 331 the frame. If yes, AC forwards the packet. Else AC drops the 332 packet. 334 After AC forwards a valid packet, it synchronizes related MAC-IP 335 binding to the MAC-IP mapping table on the AP from which the packet 336 comes. Following packets with the same MAC-IP pair will be forwarded 337 directly by AP without going to AC. 339 5.1.1.3. Negative Entries 341 In the AP Filtering scenario, APs MAY drop packets directly without 342 sending them to AC by enabling the establishment of negative entries 343 on APs. Specifically, APs may establish negative entries in the 344 following circumstances. 346 1. When AP receives a certain amount of packets within a certain 347 amount of time with the same MAC-IP pair that does not exist in 348 the local MAC-IP Table, it establishes a negative entry for this 349 MAC-IP pair. Then AP drops all following packets that have the 350 same MAC-IP pair as indicated in this negative entry without 351 sending them to AC for further processing. 353 2. When AP receives a certain amount of packets within a certain 354 amount of time with the same MAC address but different MAC-IP 355 pairs and none of these MAC-IP pairs exist in the local MAC-IP 356 Table, it establishes a negative entry for this MAC address. 357 Then AP drops all following packets that have the same MAC 358 address as indicated in this negative entry without sending them 359 to AC for further processing. 361 Each negative entry has a limited lifetime. The number of packets 362 and duration of time to trigger the establishment of the negative 363 entry, and the lifetime of the negative entry are configurable. 365 5.1.1.4. CAPWAP Extension 367 CAPWAP protocol is used for communication between AP and AC. A new 368 CAPWAP protocol message element is introduced, which extends RFC5415 369 [RFC5415]. The host IP message element is used by both AP and AC to 370 exchange the binding information of hosts. 372 The host IP message element can be used in the process of 373 confirmation of candidate binding. When AP generates a candidate 374 binding, it reports the MAC address and related IP addresses to AC 375 using this message, with suggestions of the state and lifetime of 376 each IP address as specified in Section 3.1.1. After AC checks the 377 validation of the candidate binding, it replies using a message of 378 the same format to inform AP the validation of each IP address with 379 suggestions of its state and lifetime. 381 The host IP message element can be used in the process of binding 382 migration. When migration happens, the source device reports the MAC 383 address and related IP addresses to the destination device using this 384 message, with suggestions of the state and lifetime of each IP 385 address as specified in Section 3.1.1. After the destination device 386 checks the validation of the candidate binding, it replies using a 387 message of the same format to inform the source device the validation 388 of each IP address with suggestions of its state and lifetime. 390 0 1 2 3 391 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 392 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 393 | Radio ID | Total Length + 394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 395 | Sender ID | Length | Description + 396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 397 | MAC flag | Length | MAC Address... + 398 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 399 | MAC Address... + 400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 401 | IPv4 flag | Length | blank ... + 402 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 403 | IPv4 Address 1(32 bit) + 404 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 405 | State | blank ... + 406 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 407 | lifetime + 408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 409 | IPv4 Address 2(32 bit) + 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 | State | blank ... + 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | lifetime + 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 | ........ + 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 | IPv4 Address n(32 bit) + 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 | State | blank ... + 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | lifetime + 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | IPv6 flag | Length | IPv6 Address... + 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | IPv6 Address 1(128 bit) + 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 427 | State | blank ... + 428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 | lifetime + 430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 431 | IPv6 Address 2(128 bit) + 432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 433 | State | blank ... + 434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 435 | lifetime + 436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 437 | ........ + 438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 439 | IPv6 Address n(128 bit) + 440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 441 | State | blank ... + 442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 443 | lifetime + 444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 Radio ID: An 8-bit value representing the radio, whose value is 447 between 1 and 31. 449 Total Length: Total length of the following fields. 451 Sender ID: An 8-bit value representing the sender of the message. AP 452 is represented by value 1 and AC is represented by value 2. 454 Length: The length of the Value field. 456 Description: A 16-bit value for descriptions of the sender (AP or 457 AC). 459 MAC flag: An 8-bit value representing that the sub-field's type is 460 MAC address, whose value is 1. 462 Length: The length of the MAC Address field. The formats and lengths 463 specified in EUI-48 [EUI-48] and EUI-64 [EUI-64] are supported. 465 MAC Address: A MAC address of the host. At least one MAC address 466 block MUST appear in the message, otherwise the message is considered 467 as invalid. 469 IPv4 flag: An 8-bit value representing that the sub-field's type is 470 IPv4 address, whose value is 2. 472 Length: The length of the IPv4 Address field. 474 IPv4 Address: An IPv4 address of the host. There may exist many 475 entries, and each entry is comprised of an IPv4 address, an 8-bit 476 value for address state (value 1 means available, value 0 means 477 obsoluted), and a 32-bit value for lifetime. It is required to list 478 all IPv4 addresses before IPv6 address blocks. 480 IPv6 flag: An 8-bit value representing that the sub-field's type is 481 IPv6 address, whose value is 3. 483 Length: The length of the IPv6 Address field. 485 IPv6 Address: An IPv6 address of the host. There may exist many 486 entries, and each entry is comprised of an IPv6 address, an 8-bit 487 value of address state (value 1 means available, value 0 means 488 obsoluted), and a 32-bit value lifetime. All IPv4 and IPv6 addresses 489 bind to the MAC address that appears before them in the message. 491 5.1.1.5. Mobility Solution 493 When a host moves from one AP to another, layer-2 association happens 494 before IP packet transfer. Home AP deletes the binding when mobile 495 host is disconnected, and foreign AP immediately requests the bound 496 addresses with the associated MAC from AC. AC returns the binding 497 with suggestions of its state and lifetime. After AP get the 498 addresses should be bound, the binding migration is completed. The 499 protocol used for communication between foreign AP and AC is the same 500 as described in Section 5.1.1.3, while in this scenario AC serves the 501 role of the source device and foreign AP serves the role of the 502 destination device. 504 In WLAN, a host can move from an AC to another AC while keeping using 505 the same IP address. To be compatible with such scenario, ACs must 506 communicate to perform the binding migration. The protocol used for 507 communication between ACs is the same as described in 508 Section 5.1.1.3, while in this scenario home AC serves the role of 509 the source device and foreign AC serves the role of the destination 510 device. 512 5.1.2. AC Filtering 514 In this scenario, AC maintains both MAC-IP and IP-MAC Mapping 515 Table and performs both address snooping and packet filtering. So 516 all the packets must be forwarded to AC firstly. 518 AC executes the procedure specified in Section 3.3 and check the 519 validity of IP-MAC pairs by consulting the local IP-MAC mapping 520 table. No extra procedure is needed to establish the IP-MAC 521 bindings. 523 AC executes the procedure specified in Section 4 for packet filtering 524 and no extra procedure is involved. 526 Mobility within one AC does not trigger any binding migration. 527 Mobility between different ACs triggers binding migration. ACs must 528 communicate to perform the binding migration. The protocol used for 529 communication between ACs is the same as described in 530 Section 5.1.1.3, while in this scenario home AC serves the role of 531 the source device and foreign AC serves the role of the destination 532 device. 534 5.2. Autonomous WLAN 536 Autonomous WLAN is comprised of FAT Access Points. In this scenario, 537 FAT AP maintains both MAC-IP and IP-MAC Mapping Table and performs 538 both address snooping and packet filtering. 540 FAT AP executes the procedure specified in Section 3.3 and check the 541 validity of IP-MAC pairs by consulting the local IP-MAC mapping 542 table. No extra procedure is needed to establish the IP-MAC 543 bindings. 545 FAT AP executes the procedure specified in Section 4 for packet 546 filtering and no extra procedure is involved. 548 Mobility between different FAT APs will trigger binding migration. 549 FAT APs must communicate to perform the binding migration. The 550 protocol used for communication between FAT APs is the same as 551 described in Section 5.1.1.3, while in this scenario home FAT AP 552 serves the role of the source device and foreign FAT AP serves the 553 role of the destination device. 555 6. IANA Considerations 557 There is no IANA Consideration currently. 559 7. Security Considerations 561 The security of address allocation methods matters the security of 562 this mechanism. Thus it is necessary to improve the security of 563 stateless auto-configuration and DHCP firstly. 565 7.1. Issues with Triggerring Establishment of Binding Entries by Data 566 Packets 568 In Section 3.3, a mechanism is described to allow data packets to 569 trigger the establishment of new binding entries. If the mechanism 570 is enabled, it can be used to launch attacks which may finally leads 571 to exhaustion of available IP addresses. If no restriction is taken, 572 the attacker can make as many IP-MAC bindings as possible with the 573 same MAC address. In this way, other hosts may fail to trigger any 574 binding entry establishment and thus cannot get their packets pass 575 the SAVI device. To cope with the potential security risks, 576 additional mechanism MUST be employed, e.g. to limit the maximum 577 number of IP addresses that one MAC address can bind to. 579 7.2. Privacy Considerations 581 A SAVI device MUST delete binding anchor information as soon as 582 possible, except where there is an identified reason why that 583 information is likely to be involved in the detection, prevention, or 584 tracing of actual source-address spoofing. Information about hosts 585 that never spoof (probably the majority of hosts) SHOULD NOT be 586 logged. 588 8. Acknowledgements 590 The authors would like to thank Guang Yao, Yang Shi and Hao Wang for 591 their contributions to this document. 593 9. References 595 9.1. Normative References 597 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 598 Requirement Levels", BCP 14, RFC 2119, March 1997. 600 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, 601 C., and M. Carney, "Dynamic Host Configuration Protocol 602 for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 603 2003, . 605 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 606 Address Autoconfiguration", RFC 4862, DOI 10.17487/ 607 RFC4862, September 2007, . 610 [RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley, 611 Ed., "Control And Provisioning of Wireless Access Points 612 (CAPWAP) Protocol Specification", RFC 5415, DOI 10.17487/ 613 RFC5415, March 2009, . 616 [RFC6620] Nordmark, E., Bagnulo, M., and E. Levy-Abegnoli, "FCFS 617 SAVI: First-Come, First-Served Source Address Validation 618 Improvement for Locally Assigned IPv6 Addresses", RFC 619 6620, DOI 10.17487/RFC6620, May 2012, . 622 [RFC7513] Bi, J., Wu, J., Yao, G., and F. Baker, "Source Address 623 Validation Improvement (SAVI) Solution for DHCP", RFC 624 7513, DOI 10.17487/RFC7513, May 2015, . 627 9.2. Informative References 629 [EUI-48] "Guidelines For 48-bit Global Identifier (EUI-48)", 630 http://standards.ieee.org/develop/regauth/tut/eui48.pdf 632 [EUI-64] "Guidelines For 64-bit Global Identifier (EUI-64)", 633 http://standards.ieee.org/develop/regauth/tut/eui64.pdf 635 Authors' Addresses 637 Jun Bi 638 Tsinghua University 639 Network Research Center, Tsinghua University 640 Beijing 100084 641 China 643 Email: junbi@cernet.edu.cn 645 Jianping Wu 646 Tsinghua University 647 Computer Science, Tsinghua University 648 Beijing 100084 649 China 651 Email: jianping@cernet.edu.cn 653 You Wang 654 Tsinghua University 655 Network Research Center, Tsinghua University 656 Beijing 100084 657 China 659 Email: wangyou10@mails.tsinghua.edu.cn 660 Tao Lin 661 New H3C Technologies Co. Ltd 662 466 Changhe Road, Binjiang District 663 Hangzhou, Zhejiang Province 310052 664 China 666 Email: lintao@h3c.com