idnits 2.17.1 draft-baryun-manet-technology-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 183 has weird spacing: '...ireless devic...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: a) Link MTU, so the MANET packet SHOULD not exceed. b) Reliable services provided. c) consider RFC5548 while using LLNs technologies. d) single or multi-relay switching technique. e) physical link quality depends on the NI and relay protocol. f) etc. -- The document date (July 30, 2012) is 4282 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC4903' is mentioned on line 300, but not defined == Missing Reference: 'RFC5867' is mentioned on line 242, but not defined == Missing Reference: 'RFC5826' is mentioned on line 242, but not defined == Missing Reference: 'RFC5548' is mentioned on line 243, but not defined == Unused Reference: 'RFC1677' is defined on line 334, but no explicit reference was found in the text == Outdated reference: A later version (-29) exists of draft-ietf-manet-dlep-02 Summary: 0 errors (**), 0 flaws (~~), 11 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IETF MANET Working Group A. Baryun 3 Internet-Draft UoG 4 Intended status: Informational July 30, 2012 5 Expires: Jan 31, 2013 7 MANET Subnet Technologies Considerations 8 draft-baryun-manet-technology-00.txt 10 Abstract 12 This documents describes three subnet technologies requirements, 13 and considerations. These subnets are at layer 2 of the Mobile 14 Ad hoc Network (MANET) protocols, which have some implications on 15 router protocols and interfaces considerations. For example Packet 16 Radio subnets (PRNETs), Low power and Lossy subnets (LLNs), and 17 Satellite subnets (SNETs), have different service requirements 18 which needs considerations when designing MANET routing protocols. 19 This document also outlines use-case of these MANET subnets, and 20 requirements that may be considered in MANET routing, for the users 21 and designers information. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six 34 months and may be updated, replaced, or obsoleted by other documents 35 at any time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 31, 2013. 40 Copyright Notice 42 Copyright (c) 2012 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with 50 respect to this document. Code Components extracted from this 51 document must include Simplified BSD License text as described in 52 Section 4.e of the Trust Legal Provisions and are provided without 53 warranty as described in the Simplified BSD License. 55 This document may contain material from IETF Documents or IETF 56 Contributions published or made publicly available before November 57 10, 2008. The person(s) controlling the copyright in some of this 58 material may not have granted the IETF Trust the right to allow 59 modifications of such material outside the IETF Standards Process. 61 Without obtaining an adequate license from the person(s) controlling 62 the copyright in such materials, this document may not be modified 63 outside the IETF Standards Process, and derivative works of it may 64 not be created outside the IETF Standards Process, except to format 65 it for publication as an RFC or to translate it into languages other 66 than English. 68 Table of Contents 70 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 71 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 72 2.1. Requirement Level Language . . . . . . . . . . . . . . . . . 4 73 2.2. The Document Terminology . . . . . . . . . . . . . . . . . . 4 74 3. MANET Technologies Applicability . . . . . . . . . . . . . . . 5 75 4. MANET Technologies Considerations . . . . . . . . . . . . . . . 5 76 4.1. NET Link Models . . . . . . . . . . . . . . . . . . . . . . . 5 77 4.2. MANET Link Status and Quality . . . . . . . . . . . . . . . . 5 78 5. Subnet Technology Requirements . . . . . . . . . . . . . . . . 5 79 5.1. PRNET subnet Requirements . . . . . . . . . . . . . . . . . . 5 80 5.2. LLN subnet Requirements . . . . . . . . . . . . . . . . . . . 6 81 5.3. SNET subnet Requirements . . . . . . . . . . . . . . . . . . 6 82 6. The Technology implication on Interfaces and protocols . . . . 6 83 6.1. NET Link Status and Quality . . . . . . . . . . . . . . . . . 6 84 6.2. Protocol Link at Layer 2.5 . . . . . . . . . . . . . . . . . 7 85 6.3. Main Requirements of the L2 Technology. . . . . . . . . . . . 7 86 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 87 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 88 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 7 89 10. References . . . . . . . . . . . . . . . . . . . . . . . . 8 90 10.1. Normative References . . . . . . . . . . . . . . . . . . . 8 91 10.2. Informative References . . . . . . . . . . . . . . . . . . 8 93 1. Introduction 95 The Mobile Ad hoc Network (MANET) technology characteristics and 96 considerations were described in [RFC2501] which include networks as 97 Packet Radio networks (PRNET), Energy-constrained networks (e.g. LLN), 98 and Satellite based networks (SNET). However, these subnets have 99 different implications on MANET protocols. 101 The input wrok of [COLE] demonstrated the different implications of 102 two MANET subnets if considering the need of interaction between the 103 layer 2 technology [DLEP] and the router. PRNET radio terminals may 104 relay packets among them without routing functions, and SNET radio 105 terminals communicate through satellite switchings. Due to multihop 106 relay in some subnets, [DLEP] technology may not be suitable to be 107 used. Furthermore, it was mentioned by [HARES] that node rapid mobility 108 causes either the physical or logical connectivity within a single 109 domain to split. Therefore, it is recommended that logical and physical 110 link connectivity to be distinguished [HARES][NPSISG]. In addition, 111 MANET routing over different technologies may have different 112 requirements. 114 For LLN subnets [NPSISG], and [MP] describe how some IP packets can be 115 transported over LLN technologies. However, it should be realised that 116 a MANET routing tends to be well-suited for particular network contexts 117 and less well suited for others. In [RFC2501] it was considered that 118 routing protocol SHOULD be able to accommodate such technology sleep 119 periods by coupling with the link-layer protocol through a standardized 120 interface. 122 This document intends to provide examples of three subnets for MANET 123 scenarios [RFC2501]. There are other MANET subnet technologies, which 124 are not presented nor envisioned by this document. 126 2. Terminology 128 This section provides definitions for the terminology used 129 throughout this document. 131 2.1 Requirement Level Language 133 This specification uses capitalized words defined in [RFC2119] to 134 signify requirements. In this document these words are printed in 135 small if not related to requirement level language. The document 136 uses some defined terms from other RFCs which will be noted with 137 each used term. 139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 140 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL", in this 141 document are to be interpreted as described in the RFC 2119. 143 2.2 The Document Terminology 145 Additionally, this document uses some terminology of [BARYUN], and 146 some terminology from [RFC2501]. 148 L2: 150 Layer 2 as specified by ISO OSI Model. 152 Transmission Link Types: (TBD) 154 point-to-point, point-to-Many, broadcast, MIMO, SIMO, etc. 156 NET Link (NL): 158 Communication facility/medium (physical or logical) at L2. The NL is 159 established between at least two NET Interfaces. In SNET the NET 160 link MUST be unidirectional, either uplink or downlink, and it often 161 builds a star subnet. In PRNET the NET link MAY be bidirectional or 162 unidirectional which MAY builds a mesh network. MANET links [BARYUN] 163 are at layer 3 which MAY be in different status from NET links. 165 NET Interface (NI): (TBD) 167 A device's point of attachment to a NET link. Each device MUST have 168 at least one interface that SHOULD be assigned a MAC address. 169 Any NET interface at L2 (data, control, and management planes) MUST 170 have only one transmission link type. 172 Protocol Link: 174 Is the NET link that is defined/specified by the protocol 175 specification. This link MAY differ from NET link, as the logical 176 link between the peers. 178 Transceiver Medium Access: (TBD) 180 The access scheme at L2 that depend on the transmission link types 181 used per NET link and transceiver medium. The Medium Access Control 182 protocol (MAC) is designed to facilitate the use of NET link 183 resources among wireless devices. (BMA, NBMA [RFC4903], etc.) 185 NET hop: 187 The protocol link hop at L2 (this protocol may provide the NET 188 link status to IP layer or routers). MANET hop [BARYUN] is at 189 layer 3 which each MANET hop MAY contain more than one NET hop. 191 Link MTU: as specified in [BARYUN]. 193 Variable Link MTU: 195 A link protocol that does not have a well-defined MTU. Most 196 protocols' link have a standard MTU defined to specify the maximum 197 and minimum MANET packet allowed. 199 3. MANET Technologies Applicability (TBD) 201 MANET technologies applications was described in [RFC2501]. However, 202 there are applications for MANET subnet technologies which are 203 not presently realized or envisioned in this document. This document 204 is intended to simplify three subnets: PRNET, LLN, and SNET to be 205 considered as examples of MANET technologies models. 207 4. MANET Technologies Considerations (TBD) 209 The wireless consideration and limitations [RFC2501]: noise, 210 bandwidth, transmission power, interference, fading, 211 jitter [RFC5148], etc. However, at layer 2 usually reliable 212 mechanisms are used for MANET technologies, to maintain link 213 connectivity. 215 4.1. NET Link Models 217 NET Link Models considerations have been described in [RFC4903] as 218 multi-access link models. 220 4.2. MANET Link Status and Quality 222 The MANET Link status MAY be determined from the neighbor router's 223 information exchange of the status of the link connectivity 224 between their interfaces. 226 5. Subnet Technology Requirements: (TBD) 228 5.1. PRNET subnet Requirements (TBD) 230 One radio-subnet model example [COLE] Figure at page-4, 231 centeralised or distributed PRNET can be considered in PAN, 232 LAN, MAN. 234 5.2. LLN subnet Requirements 236 LLN link MTU is 102 bytes [RFC4919] which requires a small MANET 237 packet. Some LLN technologies have sleep periods that upper protocol 238 need to consider. 240 The IETF ROLL working group has defined application-specific routing 241 requirements for Low-power and Lossy Networks (LLNs) routing 242 protocol, specified in [RFC4944], [RFC5867], [RFC5826], [RFC5673], 243 and [RFC5548]. 245 5.3. SNET subnet Requirements (TBD) 247 one SatCom-subnet model example [COLE], Figure at page-3. 249 5.4. General Requirements at L2 (TBD) 251 a) Link MTU, so the MANET packet SHOULD not exceed. 252 b) Reliable services provided. 253 c) consider RFC5548 while using LLNs technologies. 254 d) single or multi-relay switching technique. 255 e) physical link quality depends on the NI and relay protocol. 256 f) etc. 258 6. The Technology implication on Interfaces and protocols (TBD) 260 MANET protocol and interfaces [COLE], Figure at page-6. 262 6.1. Two level Network Model (TBD) 264 The Fig.1 distinguishes two different topological levels: the 265 logical network topology and physical network topology: 267 +-----------+ 268 Logical Topology (RIB) | Router | IP and/or MANET address 269 +-----------+ 270 Router Interfaces | | Interface ID (i) 271 +--------------+ +----------------+ 272 Logical Level | Interface i | | Interface i+1 | IP Address(es) 273 +--------------+ +----------------+ 274 (Plane Type: Data, | | 275 or Control) | | 276 +-----------------+ +-------------------+ 277 Physical Level| L2 Technology i | | L2 Technology i+1 | MAC Address 278 +-----------------+ +-------------------+ 280 Figure (1) Logical and Physical Technologies at two levels 282 - Logical technology level- This is concerned with intra-domain 283 routers' functions and connectivity. 285 - Physical technology level- This is concerned with L2 technology 286 functions and connectivity. 288 The routers use the logical network topology to communicate through 289 the network. The link layer protocols use the physical topology to 290 communicate through the network. MANET routing protocols consideres 291 the logical link behavior and may include the physical link. 293 There are two types of technologies:Communication Technology 294 [BARYUN], and Control technology [DLEP][RFC5673]. 295 (usually another type as network management technology may not 296 be useful at L2). 298 6.2. The Protocol at Layer 2.5 (TBD) 300 In some multi-access models [RFC4903] the protocol designers should 301 define some mechanism such that it appears as either the 302 multi-access link model or point-to-point link model at layer 3. 304 At Layer 2.5 a link protocol MAY provide layer 3 with the 305 physical link quality between its local neighbors and represent 306 the quality of the logical link between layer 3 peer neighbors. 307 If there is more than one NET hop between router neighbors then, 308 layer 2.5 protocol MAY provide to the layer 3 the correct link 309 metric and/or neighbor metric. 311 6.3. MANET Protocol Applicability (TBD) 313 7. Security Considerations (TBD) 315 This section will include security issues of the three subnets PRNET, 316 LLNs, and SNET. 318 8. IANA Considerations 319 This document does not require any IANA. 321 9. Acknowledgments (TBD) 323 I would like to thank Robert Cole, Teco Bo, Charlie Perkins, Susan 324 Hares, Emmanual Baccelli, and Ulrich Herburg, because their input 325 influenced this document's approach. 327 10. References 329 10.1. Normative References 331 [COLE] Cole, R. "Radio, SatCom and Consideration", Presentation, 332 IETF 82, Taipei, Nov., 2011, pp1-7. 334 [RFC1677] Adamson, B., "Tactical Radio Frequency Communication 335 Requirements for IPng", RFC 1677, August 1994. 337 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 338 Requirement Levels", BCP 14, RFC 2119, March 1997. 340 [RFC2501] Macker, J. and S. Corson, "Mobile Ad hoc Networking 341 (MANET): Routing Protocol Performance Issues and 342 Evaluation Considerations", RFC 2501, January 1999. 344 [RFC5148] Clausen, T., Dearlove, C., and B. Adamson, "Jitter 345 considerations in MANETs", RFC 5148, February 2008. 347 10.2. Informative References 349 [BARYUN] Baryun, A, "Terminology in MANET", Work in Progress, 2012. 351 [DLEP] Ratliff, S., Berry, B., Harrison, G., Satterwhite, D., 352 and Jury, S., "Dynamic Link Exchange Protocol (DLEP)", 353 work in progress, draft-ietf-manet-dlep-02, Feb. 2012. 355 [RFC4919] Kushalnagar, N., Montenegro, G., Schumacher, C., "IPv6 356 over Low-Power Wireless Personal Area Networks (6LoWPANs): 357 Overview, Assumptions, Problem Statement, and Goals", 358 RFC4919, Aug. 2007. 360 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., Culler, D., 361 Transmission of IPv6 Packets over IEEE 802.15.4 Networks, 362 RFC4944, Sep. 2007. 364 [RFC5673] Pister, et al."Industrial Routing Requirements in Low-Power 365 and Lossy Networks", RFC5673, 367 [HARES] Hares, S., Arbor, A., and White, R., "BGP Dynamic AS 368 Reconfiguration", IEEE MILCOM, 2007. 370 [NPSISG] Nieminen, J., Patil, B., Savolainen, T., Isomaki, 371 M., Shelby, Z., and Gomez, C., "Transmission of IPv6 372 Packets over Bluetooth Low Energy", work in progress, 373 June 2012. 375 [MP] Mariager, P., Petersen, J., "Transmission of IPv6 Packets 376 over DECT Ultra Low Energy", work in progress, May 2012. 378 Author Address 380 Abdussalam Nuri Baryun 381 University of Glamorgan, 382 Treforest, Wales, 383 CF37 1DL, UK 384 Email: abdussalambaryun@gmail.com