idnits 2.17.1 draft-jaehwoon-autoconf-sera-01.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 21. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 422. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 433. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 440. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 446. 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** There are 23 instances of lines with control characters in the document. ** The abstract seems to contain references ([4]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 1 instance of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- 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 (October 30, 2008) is 5655 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) -- Looks like a reference, but probably isn't: '2-3' on line 104 -- Possible downref: Normative reference to a draft: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '4' Summary: 5 errors (**), 0 flaws (~~), 3 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 autoconf Working Group Jaehwoon Lee 2 Internet Draft Dongguk University 3 Expires: April 29, 2009 Sanghynn Ahn 4 University of Seoul 5 Younghan Kim 6 Soongsil University 7 Yuseon Kim 8 Sangeon Kim 9 KT 10 October 30, 2008 12 Scope-Extended Router Advertisement for Connected MANETs 13 draft-jaehwoon-autoconf-sera-01.txt 15 Status of this Memo 17 By submitting this Internet-Draft, each author represents that 18 any applicable patent or other IPR claims of which he or she is 19 aware have been or will be disclosed, and any of which he or she 20 becomes aware will be disclosed, in accordance with Section 6 of 21 BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html 38 This Internet-Draft will expire on April 29, 2009. 40 Copyright Notice 42 Copyright (C) The IETF Trust (2008). 44 Abstract 46 In the connected MANET, the MANET Border Router (MBR) is used to 47 connect the MANET with the external network and MANET nodes are 48 required to know the MBR address to communicate with hosts in the 49 external network. One way of acquiring the MBR address is to use the 50 Router Advertisement (RA) and the Router Solicitation (RS) messages. 51 In order to allow RA/RS messages to be delivered in the multi-hop 52 MANET, the modified RA/RS message has been defined [4]. However, 53 this approach may incur the duplicate packet reception problem due 54 to rebroadcasting of received RA/RS messages to its neighbors. 55 In this draft, we define the scope-extended Router Advertisement/ 56 Solicitation message for announcing/solicitating the MBR address in 57 the connected MANET. In the scope-extended RA/RS message, a new 58 message field, the sequence number field, is defined so that 59 duplicate RA/RS messages can be detected based on the sequence 60 number and the MBR address included in the message. 62 Table of Contents 64 1. Introduction..................................................3 65 2. Terminology...................................................3 66 3. Message Format................................................4 67 3.1 IPv4......................................................4 68 3.1.1 ICMP Scope-Extended Router Solicitation Message.....4 69 3.1.2 ICMP Scope-Extended Router Advertisement Message....5 70 3.2 IPv6......................................................6 71 3.2.1 ICMP Scope-Extended Router Solicitation Message.....6 72 3.2.2 ICMP Scope-Extended Router Advertisement Message....8 73 3.3 Source Manet Address Option...............................9 74 4. Security Considerations.......................................9 75 5. IANA Considerations...........................................10 76 References.......................................................10 77 Author's Addresses...............................................10 78 Intellectual Property and Copyright Statements ..................12 80 1. Introduction 82 The mobile ad hoc network (MANET) enabls mobile nodes to communicate 83 cia multiple wireless hops without the need of any wired 84 infrastructure[1]. in a MANET, two nodes not within their 85 transmission range have to deliver data to each other through other 86 intermediate nodes. For forwarding packets destined to other nodes, 87 each node mush have the routing capability, i.e., the mechanism for 88 establishing data delivery routes between any pair of source and 89 destination nodes, as well as acting as a source and/or a destination 90 node(s). In addition to that, the IP address auto-configuration 91 mechanism suitable for the MANET environment is required. 93 The MANET ca be classified into the autonomous MANET and the 94 subordinate MANET. For the subordinate MANET, the MANET Border Router 95 (MBR) which acts as the gateway connecting the MANET with the 96 Internet has been defined. Through the MBR, MANET nodes can 97 communicate with hosts located in the Internet. Therefore, MANET 98 nodes have to know the MBR address. Moreover IP address assigned to 99 the MANET node should be suitable to the Internet topology. 100 In other words, nodes within the MANET should have the IP address 101 with the same network prefix. 103 One way of obtaing the MBR address and network prefix is to use the 104 Router Advertisement (RA) and Router Solicitation (RS) messages[2-3]. 105 However, there RA and RS messages are delivered only upto 1 hop, so 106 can not be used in a multi-hop wireless networks such as the MANET. 107 In order to overcome this limitation, the modified RA message has 108 been defined for the multi-hop wireless MANET[4]. However, in this 109 approach, the duplicate packet reception problem can occur since, 110 if a node broadcasts a RA/RS message, it can receive the same RA/RS 111 message which was re-broadcasted by one of its neighbors. 113 In this draft, we define the scope-extended Router Advertisement/ 114 Solicitation message for announcing/solicitating the MBR address in 115 the connected MANET. In the scope-extended RA/RS message, a new 116 message field, the sequence number field, is defined so that 117 duplicate RA/RS messages can be detected based on the sequence 118 number and the IP address included in the message. 120 2. Terminology 122 No new terminology is defined in this draft. 124 3. Message Format 126 3.1 IPv4 128 In IPv4, the scope-extended router solicitation/advertisement 129 information is included in the ICMP message [2]. 131 3.1.1 ICMP Scope-Extended Router Solicitation Message 133 0 1 2 3 134 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 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Type | Code | Checksum | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 |Sequence Number| Cur hop limit | Reserved | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | Originator Address | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 IP Fields: 145 Source Address The IP address configured at the MANET 146 interface of the MANET router (MR) sending 147 this message. 149 Destination Address 224.0.0.1 or 255.255.255.255 151 Time-to-Live 1 153 ICMP Fields: 155 Type TBD 157 Code 0 159 Sequence Number This number is increased by 1 whenever the 160 originating MR sends a scope-extended RS 161 message. The sequence number and the 162 originator address (see below) are used for 163 the message duplication check. 165 Cur Hop Limit Initially set to 255. An intermediate route 166 reduces this value by 1 before 167 rebroadcasting it. If the reduced value is 168 0, this message is silently discarded. 170 Reserved Sent as 0; ignored on reception. 172 Originator Address The IP address assigned to the MANET 173 interface of the MR that originates the 174 message. 176 3.1.2 ICMP Scope-Extended Router Advertisement Message 178 0 1 2 3 179 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 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | Type | Code | Checksum | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 |Sequence Number| Cur Hop Limit | Prefix Length | Reserved | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | Reserved | Lifetime | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | MBR Address | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 IP Fields: 192 Source Address The IP address configured at the MANET 193 interface of the MR sending this message. 194 If this message is sent as a reply to a 195 scope-extended RS message, this field has 196 the IP address configured at the MANET 197 interface of the MBR originating this 198 scope-extended RA message. If it is a 199 proactively sent message, this field has the 200 IP address configured at the MANET interface 201 of the MR sending this message. 203 Destination Address The IP address of the MANET interface of the 204 MR originating the scope-extended RS message, 205 if this scope-extended RA message is sent as 206 a reply to the scope-extended RS message. 207 Otherwise, set to the broadcast address. 209 Time-to-Live 1 if the Destination Address is the 210 broadcast address; at least 1, otherwise. 212 ICMP Fields: 214 Type TBD 216 Code 0 218 Sequence Number If this message is sent as a reply to a 219 scope-extended RS message, this field is 220 set to the Sequence Number in the scope- 221 extended RS message. Otherwise, i.e., if 222 this message is sent proactively, the value 223 of this field is increased by 1 by the MBR. 224 The sequence number and the MBR address are 225 used for the message duplication check. 227 Cur hop limit Initially set to 255. An intermediate route 228 reduces this value by 1 before 229 rebroadcasting it. If the reduced value is 230 0, this message is silently discarded. 232 Prefix Length The prefix length of the IPv4 address 233 assigned to the MANET interface of the MBR. 235 MBR Address The IP address assigned to the MANET inter- 236 face of the MBR originating this message. 238 3.2 IPv6 240 In IPv6, the scope-extended router solicitation/advertisement 241 information is defined as a part of the neighbor discovery in [3]. 243 3.2.1 ICMP Scope-Extended Router Solicitation Message 244 0 1 2 3 245 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 246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 247 | Type | Code | Checksum | 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 |Sequence Number| Cur Hop Limit | Reserved | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | | 252 | Originator Address | 253 | | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 IP Fields: 258 Source Address The IP address configured at the MANET 259 interface of the MR sending this message. 261 Destination Address The all-routers multicast address or the 262 all-nodes multicast address. 264 Time-to-Live 1 266 ICMP Fields: 268 Type TBD 270 Code 0 272 Sequence Number This number is increased by 1 whenever the 273 originating MR sends a RS message. The 274 sequence number and the originator address 275 are used for the message duplication check. 277 Cur Hop Limit Initially set to 255. An intermediate route 278 reduces this value by 1 before 279 rebroadcasting it. If the reduced value is 280 0, this message is silently discarded. 282 Originator Address The IP address assigned to the MANET 283 interface of the MR originating the message. 285 3.2.2 ICMP Scope-Extended Router Advertisement Message 286 0 1 2 3 287 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 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 | Type | Code | Checksum | 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 |Sequence Number| Prefix Length | Reserved | 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 293 | Cur Hop Limit |M|O| Reserved | Router Lifetime | 294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 | Reachable Time | 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 | Retrans Timer | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 299 | | 300 | MBR Address | 301 | | 302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 IP Fields: 306 Source Address If this message is sent as a reply to a 307 scope-extended RS message, this field has 308 the IP address configured at the MANET 309 interface of the MBR originating this 310 message. If this messages is a proactively 311 sent message, this field has the IP address 312 configured at the MANET interface of the MR 313 sending this message. 315 Destination Address Typically the Source Address of the invoking 316 scope-extended Router Solicitation or the 317 all-nodes multicast address. 319 Hop Limit 1 if the Destination Address is the 320 all-routers multicast address or the 321 all-nodes multicast address; 322 at least 1, otherwise. 324 ICMP Fields: 326 Type TBD 328 Code 0 329 Sequence Number If this message is sent as a reply to a 330 scope-extended RS message, this field is 331 set to the Sequence Number in the scope- 332 extended RS message. Otherwise, i.e., if 333 this message is sent proactively, the value 334 of this field is increased by 1 by the MBR. 335 The sequence number and the MBR address are 336 used for the message duplication check. 338 Prefix Length The prefix length of the IPv6 address 339 assigned to the MANET interface of the MBR. 341 Cur Hop Limit Initially set to 255. An intermediate route 342 reduces this value by 1 before 343 rebroadcasting it. If the reduced value is 344 0, this message is silently discarded. 346 MBR Address The IPv6 address configured at the MANET 347 interface of the MBR originating this 348 message. 350 4. Security Consideration 352 There is no special security considerations in this draft. 354 5. IANA Considerations 356 This draft document defines a new type in the ICMP message. An Type 357 value for the scope-extended Router Discovery message for MANET must 358 be assigned by IANA. 360 References 362 [1] E. Baccelli, "Address Autoconfiguration for MANET: Terminology 363 and Problem Statement", draft-ietf-autoconf-statement-04, 364 Work in progress, Feb. 2008. 366 [2] S. Deering, "ICMP Router Discovery Messages", RFC 1256, 367 Sep. 1991. 369 [3] T. Narten, E. Nordmark, W. Simpson and H. Soliman, "Neighbor 370 Discovery for IP version 6 (IPv6)", RFC 3861, Sep. 2007. 372 [4] R. Wakikawa, J. Malinen, C. Perkins, A. NIlsson and A. Tuominen, 373 Global connectivity for IPv6 Mobile Ad Hoc Networks", Work in 374 progress, Oct. 2003. 376 Author's Addresses 378 Jaehwoon Lee 379 Dongguk University 380 26, 3-ga Pil-dong, Chung-gu 381 Seoul 100-715, KOREA 382 Email: jaehwoon@dongguk.edu 384 Sanghyun Ahn 385 University of Seoul 386 90, Cheonnong-dong, Tongdaemun-gu 387 Seoul 130-743, KOREA 388 Email: ahn@uos.ac.kr 390 Younghan Kim 391 Soongsil University 392 11F Hyungnam Engineering Bldg. 317, Sangdo-Dong, 393 Dongjak-Gu, Seoul 156-743 Korea 394 E-main: yhkim@dcn.ssu.ac.kr 396 Yuseon Kim 397 KT 398 17 Woomyeon-dong, Seocho-gu 399 Seoul 137-792, KOREA 400 Email: yseonkim@kt.co.kr 402 Sangeon Kim 403 KT 404 17 Woomyeon-dong, Seocho-gu 405 Seoul 137-792, KOREA 406 Email: sekim@kt.co.kr 408 Full Copyright Statement 410 Copyright (C) The IETF Trust (2008). 412 This document is subject to the rights, licenses and restrictions 413 contained in BCP 78, and except as set forth therein, the authors 414 retain all their rights. 416 This document and the information contained herein are provided on an 417 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 418 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 419 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 420 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 421 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 422 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 424 Intellectual Property 426 The IETF takes no position regarding the validity or scope of any 427 Intellectual Property Rights or other rights that might be claimed to 428 pertain to the implementation or use of the technology described in 429 this document or the extent to which any license under such rights 430 might or might not be available; nor does it represent that it has 431 made any independent effort to identify any such rights. Information 432 on the procedures with respect to rights in RFC documents can be 433 found in BCP 78 and BCP 79. 435 Copies of IPR disclosures made to the IETF Secretariat and any 436 assurances of licenses to be made available, or the result of an 437 attempt made to obtain a general license or permission for the use of 438 such proprietary rights by implementers or users of this 439 specification can be obtained from the IETF on-line IPR repository at 440 http://www.ietf.org/ipr. 442 The IETF invites any interested party to bring to its attention any 443 copyrights, patents or patent applications, or other proprietary 444 rights that may cover technology that may be required to implement 445 this standard. Please address the information to the IETF at 446 ietf-ipr@ietf.org. 448 Acknowledgment 450 Funding for the RFC Editor function is provided by the IETF 451 Administrative Support Activity (IASA).