idnits 2.17.1 draft-sijeon-mext-nemo-pmip6-00.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC3963], [RFC5213]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors 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 date (October 2010) is 4932 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: 'RFC2119' is mentioned on line 139, but not defined ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) == Outdated reference: A later version (-02) exists of draft-bernardos-netext-pmipv6-nemo-ps-01 ** Downref: Normative reference to an Informational draft: draft-bernardos-netext-pmipv6-nemo-ps (ref. 'PROB-STAT') == Outdated reference: A later version (-12) exists of draft-ietf-netext-bulk-re-registration-01 Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Seil Jeon 3 Internet-Draft Younghan Kim 4 Intended status: Standards Track Jiwon Jang 5 Expires: April 18, 2011 Soongsil University, Korea 6 October 2010 8 Network Mobility Support in the Proxy Mobile IPv6 Domain 9 draft-sijeon-mext-nemo-pmip6-00.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on February 8, 2011. 34 Copyright Notice 36 Copyright (c) 2010 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Please review these documents carefully, as they 45 describe your rights and restrictions with respect to this document. 46 Code Components extracted from this document must include Simplified 47 BSD License text as described in Section 4.e of the Trust Legal 48 Provisions and are provided without warranty as described in the 49 Simplified BSD License. 51 Abstract 53 Network mobility (NEMO) enables all the nodes within a mobile network 54 to provide session continuity without requiring their involvement 55 when the mobile network moves. To provide NEMO support, the NEMO 56 basic support protocol (NEMO-BSP) is specified in [RFC 3963]. 58 With the advances of the network-based mobility management protocol 59 referred to as Proxy Mobile IPv6 (PMIPv6), interest in applicable 60 NEMO support in the PMIPv6 domain is increasing however, the standard 61 PMIPv6, defined in [RFC 5213], handles only a single mobile node. 63 This document presents a NEMO-enabled PMIPv6 using a Proxy Router 64 (PR) rather than the MR defined in [RFC 3963] and describes detailed 65 operations for network/node mobility support in the PMIPv6 domain. 67 Table of Contents 69 1. Introduction.....................................................4 70 2. Terminology and Functional Components............................5 71 3. Protocol Operation...............................................6 72 3.1. PR's Attachment..............................................6 73 3.2. MNN's Attachment.............................................7 74 3.3. PR's Handoff from P-MAG to N-MAG.............................9 75 3.4. MNN's Handoff from the PR to the outer PMIPv6 domain........10 76 4. Binding Entry Information.......................................12 77 4.1. Extended Proxy Binding Update List in MAG...................12 78 4.2. Extended Binding Cache Entry in LMA.........................12 79 5. IANA Considerations.............................................13 80 6. Security Considerations.........................................13 81 7. References......................................................13 82 7.1. Normative References........................................13 83 7.2. Informative References......................................14 84 Author's Address...................................................15 86 1. Introduction 88 Network mobility (NEMO) is a novel concept for handling a group of 89 nodes within a moving vehicular area. The recent rapid propagation of 90 Wi-Fi handheld devices and increasing demand for Internet access 91 everywhere have made NEMO technology much noticeable. To enable 92 support for NEMO, the NEMO basic support protocol (NEMO-BSP) is 93 specified in [RFC 3963]. 95 The NEMO-BSP employs the Mobile Router (MR), which connects a mobile 96 network node (MNN) and access router (AR) and has the functionality 97 of host-based Mobile IPv6 (MIPv6) [RFC 3775] client protocol. Due to 98 the host-based features, the MIPv6 has essential performance issues 99 (e.g., handover latency, inefficient packet delivery, multiple 100 tunneling overhead). To resolve the performance issues found in 101 MIPv6, the network-based Proxy Mobile IPv6 (PMIPv6) has been proposed 102 [RFC 5213]. The PMIPv6 provides improved performance to mobile nodes 103 (MNs), but current specification handles only a single MN. 105 In order to deploy the NEMO in the PMIPv6 domain, [PROB-STAT] 106 presents a problem statement and applicability of NEMO-BSP. [NEMO-BS- 107 PMIPv6] describes PMIPv6-NEMO scenarios and operations when MR is 108 based on Mobile IPv6 protocol. [NESTED-NEMO] presents a nested NEMO 109 case, and [NEMO-BSP-PMIPv6] presents several scenarios for applying 110 NEMO-BSP to the PMIPv6 domain. 112 We present a NEMO-enabled PMIPv6 using a Proxy Router (PR) than the 113 MR defined in [RFC 3963]. Within the context of this document, the 114 PR, which is located between the MNN and mobile access gateway (MAG), 115 has no mobility function. It detects the MNN's movement and delivers 116 corresponding information to a MAG on behalf of MNNs within its 117 coverage. 119 The PR and MNNs within a specified mobile network are managed with 120 the same group ID by the local mobility anchor (LMA). When a PR moves 121 to another MAG, the LMA then changes the binding cache entries for 122 the PR and MNNs at the same time. This feature enables all the nodes 123 within mobile network to provide session continuity without the MNNs' 124 involvement. 126 All the information in the MNNs is managed by the MAG as well as the 127 LMA. As a result, when an LMA delivers packets to an MNN, no 128 additional tunnel is used except for the PMIPv6 tunnel between the 129 MAG and the LMA. 131 The remainder of this document describes detailed operations for 132 network/node mobility in the PMIPv6 domain. 134 2. Terminology and Functional Components 136 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 137 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 138 document are to be interpreted as described in [RFC2119] 140 o Mobile Network Node (MNN) - The node that has an address 141 containing the MNP, as defined in [RFC 3963]. 143 o Mobile Router (MR) - It is extended from Mobile IPv6 client 144 protocol and in charge of mobility management on behalf of MNN 145 within a mobile network, as defined in [RFC 3963]. 147 o Proxy Router (PR) - It detects the MNN's movement and delivers the 148 information to the MAG behalf of MNNs within its coverage. It also 149 emulates the MNN's home network on the access link. 151 o PR Group ID (PR-GID) - A unique ID that is assigned from LMA and 152 used for efficient NEMO. 154 3. Protocol Operation 156 3.1. PR's Attachment 158 PR MAG AAA LMA 159 | | | | 160 |------ L2 ------>| | | 161 | Attach | | | 162 | | | | 163 |------ RS ------>| | | 164 | (PR-ID) | | | 165 | | | | 166 | |<- AAA Req/Res ->| | 167 | | | | 168 | |--------------- PBU -------------->| 169 | | (PR-ID,'B','N') | 170 | | | | 171 | | | Create the group 172 | | | (PR-GID) for PR 173 | | | | 174 | |<-------------- PBA ---------------| 175 | | (PR-ID,'B','N',PR-HNP,PR-GID) | 176 | | | | 177 | Store the group | | 178 | info. (PR-GID) | | 179 | | | | 180 |<----- RA -------| | | 181 | (PR-HNP) | | | 182 | | | | 184 Figure 1. PR Attachment to the PMIPv6 Domain 186 When a PR approaches the PMIPv6 domain, this event is detected by the 187 MAG. The MAG then sends a proxy binding update (PBU) message 188 containing 'B' and 'N' flags set to 1 toward the LMA. The 'B' flag, 189 which is derived from the bulk re-registration mechanism [BULK-REG], 190 requests the allocation of a group ID (GID) and reduces the excessive 191 signaling cost required to extend the binding lifetime of individual 192 mobile hosts. To the 'B' flag, we add an 'N' flag, which is defined 193 in this document, to denote that this node is not an ordinary mobile 194 host but a proxy router. This information can be obtained from the 195 security association between the MAG and the AAA. 197 3.2. MNN's Attachment 199 MNN PR MAG AAA LMA 200 | | | | | 201 |---- L2 ---->| | | | 202 | Attach | | | | 203 | | | | | 204 |---- RS ---->| | | | 205 | (MNN-ID) | | | | 206 | |------ RS ------>| | | 207 | | ('P', MNN-ID) | | | 208 | | | | | 209 | | |<--- AAA --->| | 210 | | | Req/Res | | 211 | | | | | 212 | | |----------- PBU ---------->| 213 | | | (MNN-ID,'B',PR-ID) | 214 | | | | | 215 | | | | MNN is joined 216 | | | | to the PR-GID 217 | | | | | 218 | | |<---------- PBA -----------| 219 | | | (MNN-ID,'B',MN-HNP,PR-GID)| 220 | | | | | 221 | | Store MNN's info | | 222 | | | | | 223 | |<----- RA -------| | | 224 | | ('P',MNN-HNP) | | | 225 |<--- RA -----| | | | 226 | (MNN-HNP) | | | | 228 Figure 2. MNN Attachment to the PR in the Mobile Network 230 When an MNN approaches the PR, it sends its MNN-ID to the PR by means 231 of a router solicitation (RS) message. The PR delivers the RS message 232 with a 'P' flag denoting proxy, which is defined in this document, 233 set to 1. After receiving the RS message, the MAG learns that the 234 attached MNN belongs to the PR by examining the 'P' flag of the 235 received RS message and link-layer address of the PR. To manage the 236 attached node under the PR, a PBU message sent by the MAG includes 237 the MNN-ID, the PR-ID of the attached PR, and a 'B' flag set to 1. 238 The LMA allocates the home network prefix (HNP) for the MNN and 239 groups the MNN around the group ID of the PR (PR-GID). After 240 receiving the PBA message, the MAG also adds the MNN to the PR-GID. 241 The allocated HNP is delivered to the PR through a router 242 advertisement (RA) message with a 'P' flag set to 1. Then, the RA 243 message with a 'P' flag set to 0 is finally delivered to the MNN. 245 When LMA receives the packets that are destined for the MNN from a 246 CN, it looks up the corresponding MAG IP address to which the MNN 247 belongs in BCE. Next, the packets, combined with only the PMIPv6 248 tunnel header, are sent to the MAG. When the MAG sends packets to the 249 MNN via the PR, no tunnel is used because MAG knows the next hop 250 address to deliver packets toward the MNN. 252 3.3. PR's Handoff from P-MAG to N-MAG 254 MNN PR P-MAG N-MAG AAA LMA 255 | | | | | | 256 | | Detection of | | | 257 | | PR's movement | | | 258 | | | | | | 259 | | |----- PBU (PR-ID, Lifetime=0) ---->| 260 | | | | | | 261 | | |<---- PBA (PR-ID, Lifetime=0) -----| 262 | | | | | | 263 | Handoff | | | | 264 | | | | | | 265 | |------ L2 Attach ----->| | | 266 | | | | | | 267 | |------ RS (PR-ID) ---->| | | 268 | | | | | | 269 | | | |<--- AAA Req/Res ----->| 270 | | | | | | 271 | | | |--------- PBU -------->| 272 | | | | (PR-ID, 'B', 'N') | 273 | | | | | | 274 | | | |<-------- PBA ---------| 275 | | | | (PR-ID,'B','N',PR-HNP,| 276 | | | |PR-GID,MNN-IDs,MNN-HNPs) 277 | | | | | | 278 | |<-------- RA ----------| | | 279 | | (PR-HNP, MNN-HNPs) | | | 280 | | | | | | 282 Figure 3. PR's Handover operation from MAG_A to MAG_B 284 When the PR moves to the next MAG (N-MAG) from the previous MAG (P- 285 MAG), the P-MAG detects the PR's movement from a layer-2 event and 286 then initiates a de-registration process for the PR. The N-MAG, which 287 detects a PR's attachment, sends a PBU message for registration. The 288 LMA receives the PBU message, finds that this node is the proxy 289 router from the 'N' flag, and verifies that there exists the PR-GID 290 for the corresponding PR in BCE. If the LMA has the PR-GID, it sends 291 the PBA message, including the MNN-IDs and MNN-HNPs as well as PR-HNP 292 and PR-GID, because the N-MAG has no information about the MNNs that 293 belong to the PR. 295 3.4. MNN's Handoff from the PR to the outer PMIPv6 Domain 297 MNN PR MAG AAA LMA 298 | | | | | 299 | Detection of | | | 300 | MNN's movement | | | 301 | | | | | 302 | |------ RS ----->| | | 303 | |('P','D',MNN-ID)| | | 304 | | | | | 305 | | |----------- PBU ---------->| 306 | | | (MNN-ID, Lifetime=0) | 307 | | | | | 308 | | | | Remove the MNN 309 | | | | from the group 310 | | | | to which the PR 311 | | | | belongs | 312 | | | | | 313 | | |<---------- PBA -----------| 314 | | | (MNN-ID, Lifetime=0) | 315 | | | | | 316 | | Remove the MNN | | 317 | | from the group to which | | 318 | | the PR belongs | | 319 | | | | | 320 |---------- L2 Attach -------->| | | 321 | | | | | 322 | | |<-AAA Req/Res->| | 323 | | | | | 324 | | |------ PBU (MNN-ID) ------>| 325 | | | | | 326 | | |<-- PBA (MNN-ID,MNN-HNP) --| 327 | | | | | 328 |<-- ------- RA ---------------| | | 329 | (MNN-HNP) | | | 331 When an MNN moves out from a mobile network, the PR detects the MNN's 332 detachment from a layer-2 signal and then sends an RS message to the 333 current MAG. This RS message includes 'P' and 'D' flags set to 1 and 334 MNN-ID. The 'D' flag, which is defined in this document, to announce 335 MNN's movement to the MAG. When the MAG receives the RS message with 336 'P' and 'D' flags set to 1, it determines that the corresponding MNN- 337 ID in received RS message moved out from the PR, and it sends a PBU 338 message for de-registration to the LMA defined in [RFC 5213]. The LMA 339 performs de-registration and removes the MNN from the group to which 340 the PR belongs; then, it sends a PBA message to the MAG. When the MAG 341 receives the PBA message from the LMA, it also removes the MNN from 342 the group to which the PR belongs and MNN-related entry information 343 in the proxy binding update list (PBUL). When the MNN approaches the 344 MAG, the MAG detects the node's movement and performs the node 345 attachment procedure defined in [RFC 5213]. 347 4. Binding Entry Information 349 4.1. Extended Proxy Binding Update List in MAG 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | ID | HNP | PR | GID | LMA | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 | PR | Pref1::/64 | | PR-GID1 | LMA A | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 | MNN | Pref2::/64 | Pref1::/64 | PR-GID1 | LMA A | 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 | MN | Pref3::/64 | | | LMA A | 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 4.2. Extended Binding Cache Entry in LMA 363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 364 | ID | HNP | PR | GID | MAG | 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 366 | PR | Pref1::/64 | | PR-GID1 | MAG_A | 367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 | MNN | Pref2::/64 | Pref1::/64 | PR-GID1 | MAG_A | 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 370 | MN | Pref3::/64 | | | MAG_A | 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 373 5. IANA Considerations 375 TBD. 377 6. Security Considerations 379 TBD. 381 7. References 383 7.1. Normative References 385 [RFC 3963] 386 V. Devarapalli, R.Wakikawa, A. Petrescu, and P. Thubert, 387 "Network Mobility (NEMO) Basic Support Protocol," IETF RFC 388 3963, January, 2005. 390 [RFC 3775] 391 D. Johnson, C. Perkins, and J. Arkko, "Mobility support in 392 IPv6," IETF RFC 3775, June 2004. 394 [RFC 5213] 395 S. Gundavelli, K. Leung, V. Devarapalli, K. Chowdhury, and 396 B. Patil, "Proxy Mobile IPv6," IETF RFC 5213, August 2008. 398 [PROB-STAT] 399 CJ. Bernardos, M. Calderon, and I. Soto, "PMIPv6 and 400 Network Mobility Problem Statement," draft-bernardos- 401 netext-pmipv6-nemo-ps-01.txt, October 2009. 403 7.2. Informative References 405 [NESTED-NEMO] 406 H. Zhang et al., "Consideration of Network Mobility in 407 PMIPv6," draft-zhang-netlmm-nemo-01.txt, (work in 408 progress), March 2010. 410 [NEMO-BSP-PMIPv6] 411 J. -H. Lee et al., "Network Mobility Basic Support within 412 Proxy Mobile IPv6: scenarios and analysis," draft-jhlee- 413 netlmm-nemo-scenarios-01.txt, (work in progress), 414 September 2008. 416 [BULK-REG] 417 F. Abinader et al., "Bulk Re-registration for Proxy Mobile 418 IPv6," draft-ietf-netext-bulk-re-registration-01.txt, 419 (work in progress), July 2010. 421 Author's Addresses 423 Seil Jeon 424 Soongsil University 425 4F Hyungnam Engineering Bldg. 424, 426 (156-743) 511 Sangdo-Dong, Dongjak-Gu, Seoul, Korea 427 Phone: +82-2-820-0841 428 E-mail: sijeon@dcn.ssu.ac.kr 430 Younghan Kim 431 Soongsil University 432 11F Hyungnam Engineering Bldg. 1107, 433 (156-743) 511 Sangdo-Dong, Donajak-Gu, Seoul, Korea 434 Phone: +82-2-820-0904 435 E-mail: younghak@ssu.ac.kr 437 Jiwon Jang 438 Soongsil University 439 4F Hyungnam Engineering Bldg. 424, 440 (156-743) 511 Sangdo-Dong, Dongjak-Gu, Seoul, Korea 441 Phone: +82-2-820-0841 442 E-mail: jwjang84@dcn.ssu.ac.kr