idnits 2.17.1 draft-ietf-lisp-nexagon-04.txt: -(10): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding 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: ---------------------------------------------------------------------------- == There are 2 instances of lines with non-ascii characters in the document. == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 1020 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 227 instances of too long lines in the document, the longest one being 54 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 113 has weird spacing: '...receive consi...' == Line 218 has weird spacing: '...through cloud...' == Line 636 has weird spacing: '...unneled and i...' == Line 868 has weird spacing: '...vehicle on ti...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.ietf-lisp-rfc6833bis' is defined on line 885, but no explicit reference was found in the text == Unused Reference: 'RFC8378' is defined on line 901, but no explicit reference was found in the text == Outdated reference: A later version (-31) exists of draft-ietf-lisp-rfc6833bis-07 ** Obsolete normative reference: RFC 6830 (Obsoleted by RFC 9300, RFC 9301) Summary: 2 errors (**), 0 flaws (~~), 11 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 LISP Working Group S. Barkai 2 Internet-Draft B. Fernandez-Ruiz 3 Intended status: Informational S. ZionB 4 Expires: December 30, 2020 R. Tamir 5 Nexar Inc. 6 A. Rodriguez-Natal 7 F. Maino 8 Cisco Systems 9 A. Cabellos-Aparicio 10 J. Paillissé Vilanova 11 Technical University of Catalonia 12 D. Farinacci 13 lispers.net 14 July 30,2020 16 Network-Hexagons: H3-LISP GeoState & Mobility Network 17 draft-ietf-lisp-nexagon-04 19 Abstract 21 This document specifies use of H3 and LISP to publish subscribe and reflect 22 the real-time state and status of public spaces and public roads: 23 - Tile by tile, indexed annotation of streets & curbs in near real time 24 - Sharing hazards, blockages, parking, weather, maintenance, inventory.. 25 - Between MobilityClients who produce and consume geo-state information 26 - Using geo-spatial IP channels of current state of the physical world 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at https://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on October 4, 2019. 45 Copyright Notice 47 Copyright (c) 2019 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (https://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 64 3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3 65 4. Deployment Assumptions . . . . . . . . . . . . . . . . . . . 4 66 5. Mobility Clients Network Services . . . . . . . . . . . . . . 4 67 6. Mobility Unicast-Multicast . . . . . . . . . . . . . . . . . 5 68 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 69 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 70 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 71 10. Normative References . . . . . . . . . . . . . . . . . . . . 8 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 74 1. Introduction 76 (1) The Locator/ID Separation Protocol (LISP) [RFC6830] splits current IP 77 addresses in two different namespaces, Endpoint Identifiers (EIDs) and 78 Routing Locators (RLOCs). LISP uses a map-and-encap approach that relies on 79 (1) a Mapping System (distributed database) that stores and disseminates 80 EID-RLOC mappings and on (2) LISP tunnel routers (xTRs) that encapsulate 81 and decapsulate data packets based on the content of those mappings. 83 (2) H3 is a geospatial indexing system using a hexagonal grid that can be 84 (approximately) subdivided into finer and finer hexagonal grids, 85 combining the benefits of a hexagonal grid with hierarchical subdivisions. 86 H3 supports sixteen resolutions. Each finer resolution has cells with one 87 seventh the area of the coarser resolution. Hexagons cannot be perfectly 88 subdivided into seven hexagons, so the finer cells are only approximately 89 contained within a parent cell. Each cell is identified by a 64bit HID. 91 (3) The Berkeley Deep Drive (BDD) Industry Consortium investigates state-of- 92 the-art technologies in computer vision and machine learning for automotive 93 applications, and, for taxonomy of published automotive scene classification. 95 These standards are combined to create an in-network state which reflects the 96 condition of each hexagonal tile (~1sqm) in every road. The lisp network maps 97 & encapsulates traffic between MobilityClient endpoint identifiers (EID), and 98 addressable tile-objects (HID=>EID). objects are aggregated by H3Service EIDs. 100 The H3-LISP mobility network bridges timing and location gaps between the 101 production and consumption of information by MobilityClients: 102 o vision, sensory, LIADR, AI applications -- information producers 103 o driving-apps, map-apps, command & control -- information consumers 105 This is achieved by putting the physical world on a shared addressable 106 state-grid typically at the edge. Tile by tile geo-state sharing using a 107 brokered-network solves key issues in vehicle to vehicle information sharing. 108 Challenges such as vision sensors when there are multiple perspectives, 109 privacy and cyber when clients are directly communicating when they do not have 110 to, and global geo pub-sub scenarios. 112 Given a situation observable by some end-points, it is unclear if the relevant 113 end-points which need to know will receive consistent, conflicting, multiple, 114 or no indications whatsoever. For example, when a vehicle experiences a sudden 115 highway slow-down,"sees" many brake lights or "feels" accelerometer, there is 116 no clear way for it to share this annotation with vehicles 20-30sec away to 117 prevent a potential pile-up. Or, when a vehicle crosses an intersection, 118 observing opposite-lane obstruction, construction, double-park, commercial 119 loading, garbage truck, or stopped school-bus, there is no clear way for it to 120 alert vehicles approaching that situation as it drives away. 122 Geo-state indirection also helps communicate advanced machine vision and/or 123 radar annotations. These are constantly evolving technologies, and relaying 124 road enumerations they produce, using peer-to-peer protocols, poses a 125 significant interoperability challenge. It is hard to test each new 126 annotation of any sensor or OEM vendor with any other driving application. 127 Brokered IP multicast channels are themed, subscribing means interoperating. 129 These peer-to-peer limitations are inherent yet unnecessary, as in most road 130 situations vehicles are not really proper peers. They just happen to be in the 131 same place at the same time. H3-LISP mobility network solves the limitations 132 of direct vehicle-to-vehicle communication by anchor brokers per geo-tile: 133 timing, security, privacy, interoperability. Anchor brokering is achieved by 134 MobilityClients communicating through in-network addressable geo-states. 135 Addressable tiles are aggregated and maintained by LISP H3ServiceEIDs. 137 MobilityClients can provide drivers with heads-up alerts on hazards and obstacles 138 beyond the line of sight of the driver and the in-car sensors: over traffic, 139 around blocks, far-side junction, beyond road turns or surface curvatures. 140 This highlights the importance of networks in providing road safety and the 141 role networks play in future AV operation support systems (AV-OSS). 143 Beyond sharing use cases like finding freed-up curb-parking and help avoid 144 construction zones, a mission critical use case for global geo-pub-sub has to 145 do with supporting autonomous vehicle (AV) fleets. 147 Its now a consensus that as specific AV fleets start to role out, or regular 148 cars with AV abilities become more perversive, that they need remote operations 149 and remote take-over support. This means that for every M such cars there needs 150 to be N human remote drivers ready to take over. These AV-OSS are put together 151 by consortiums of multiple companies and are measured by their N/M. 153 Nexagon geo-channels role in this context is two fold: 155 1. flag tiles where the AV got confused because of current condition which is 156 requiring remote intervention, so to steer other AVs away from this tile. 157 This so not to pull-in more and more humans to intervene as more cars arrive. 158 2. fleets will heavily rely on platoons, convoys assembled on the road on the 159 fly, driven at the head by a remote operator or human driver. AVs need to 160 lock-on. Geo channels are used pub-sub these platoons as they drive by. 162 To summarize the H3-LISP solution outline: 164 (1) MicroPartition: 64bit indexed geo-spatial H3.r15 road-tiles 165 (2) EnumState: 64bit state values compile tile condition representation 166 (3) Aggregation: H3.r9 H3ServiceEID group individual H3.r15 road-tiles 167 (4) Channels: H3ServiceEIDs function as multicast state update channels 168 (5) Scale: H3ServiceEIDs distributed for in-network for latency-throughput 169 (6) Mapped Overlay: tunneled-network routes the mobility-network traffic 170 (7) Signal-free: tunneled overlay is used to map-register for mcast channels 171 (8) Aggregation: tunnels used between MobilityClients/H3ServiceEIDs <> edge 172 (9) Access: ClientXTRs/ServerXTRs tunnel traffic to-from the LISP EdgeRTRs 173 (10) Control: EdgeRTRs register-resolve H3ServiceEIDs and mcast subscription 175 |-0-|-1-|-2-|-3-|-4-|-5-|-6-|-7-|-8-|-9-|-A-|-B-|-C-|-D-|-E-|-F-| 176 | H3 Hexagon ID Key | 177 |-0-|-1-|-2-|-3-|-4-|-5-|-6-|-7-|-8-|-9-|-A-|-B-|-C-|-D-|-E-|-F-| 178 | H3 Hexagon State-Value | 179 |---------------------------------------------------------------| 181 ___ ___ 182 H3ServiceEIDs ___ / \ H3ServiceEIDs ___ / \ 183 ___ / | H3.r9 | ___ / | H3.r9 | 184 / | H3.r9 \ ___ / / | H3.r9 \ ___ / 185 | H3.r9 \ ___ / sXTR | H3.r9 \ ___ / sXTR 186 \ ___ / sXTR | \ ___ / sXTR | 187 sXTR | | sXTR | | 188 | | | | | | 189 | | | | | | 190 + - - + - - EdgeRTR EdgeRTR - + - + - - + 191 || ( ( (( || 192 ( ) 193 ( Network Hexagons ) 194 ( H3-LISP ) 195 ( Mobility Network ) 196 (( ) 197 || (( (()) () || 198 || || 199 = = = = = = = = = = = = = = 200 || || 201 EdgeRTR EdgeRTR 202 .. .. .. .. 203 .. .. .. .. 204 ((((|)))) ((((|)))) ((((|)))) ((((|)))) 205 /|\ RAN /|\ /|\ RAN /|\ 206 .. .. 207 .. .. 208 .. Road tiled by 1 sqm H3.r15 ID-Ed Geo-States .. 209 .. .. 210 .. ___ ___ ___ .. 211 .. .............. / \/ \/ \ << cXTR::MobilityClientB 212 .. - - - - - - - H3.r15 H3.r15 H3.r15 - - - - - - - 213 MobilityClientA::cXTR >> \ ___ /\ ___ /\ ___ /.......... 215 - MobilityClientA has seen MobilityClientB near future, and, vice versa 216 - Clients share information using addressable shared-state routed by LISP Edge 217 - ClientXTR (cXTR): tunnel encapsulation through access network to LISP Edge 218 - ServerXTR (sXTR): tunnel encapsulation through cloud network to LISP Edge 219 - The H3-LISP Mobility overlay starts in the cXTR and terminates in the sXTR 220 - The updates are routed to the appropriate tile geo-state by the LISP network 221 - EdgeRTRs perform multicast replication to edges and then native or to cXTRs 222 - Clients receive tile-by-tile geo-state updates via the multicast channels 224 Each H3.r9 hexagon is an EID Service with corresponding H3 hexagon ID. 225 Bound to that service is a LISP xTR, called a ServerXTR, specified to deliver 226 encapsulated packets to and from the H3ServiceEID and LISP Edge. EdgeRTRs are 227 used to re-tunnel packets from MobilityClients to H3ServiceEIDs. Each 228 H3ServiceEID is also a multicast source for updating MobilityClients 229 on the state of the H3.r15 tiles aggregated by the H3ServiceEID. 231 2. Requirements Language 233 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 234 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 235 document are to be interpreted as described in [RFC2119]. 237 3. Definition of Terms 239 H3ServiceEID: Is an addressable aggregation of H3.r15 state-tiles. It is a 240 designated source for physical world reported annotations, and an (s,g) 241 source of multicast public-safety update channels. H3ServiceEID is itself 242 an H3 hexagon, large enough to provide geo-spatial conditions context, but 243 not too large as to over-burden (battery powered, cellular connected) 244 subscribers with too much information. For Mobility Network it is H3.r9. 245 It has a light-weight LISP protocol stack to tunnel packets aka ServerXTR. 246 The EID is an IPv6 EID that contains the H3 64-bit address numbering 247 scheme. See IANA consideration for details. 249 ServerXTR: Is a light-weight LISP protocol stack implementation that co-exists 250 with H3ServiceEID process. When the server roams, the xTR roams with it. 251 The ServerXTR encapsulates and decapsulates packets to/from EdgeRTRs. 253 MobilityClient: Is a roaming application that may be resident as part of an 254 automobile, as part of a navigation application, part of municipal, state, 255 of federal government command and control application, or part of live 256 street view consumer type of application. It has a light-weight LISP 257 protocol stack to tunnel packets aka ClientXTR. 259 MobilityClient EID: Is the IPv6 EID used by the Mobility Client applications 260 to source packets. The destination of such packets are only H3ServiceEIDs. 261 The EID format is opaque and is assigned as part of the MobilityClient 262 network-as-a-service (NaaS) authorization. 264 ClientXTR: Is the light-weight LISP protocol stack implementation that is 265 co-located with the Mobility Client application. It encapsulates packets 266 sourced by applications to EdgeRTRs and decapsulates packets from EdgeRTRs. 268 EdgeRTR: Is the core scale and structure of the LISP mobility network. 269 EdgeRTRs proxy H3ServiceEIDs and MobilityClient H3ServiceEID channel 270 registration. EdgeRTRs aggregate MobilityClients and H3Services using 271 tunnels to facilitate hosting-providers and mobile-hosting flexibility - 272 for accessing the nexagon mobility network. 273 EdgeRTRs decapsulate packets from ClientXTRs, ServerXTRs and re-encapsulates 274 packets to the clients and servers tunnels. EdgeRTRs glean H3ServiceEIDs 275 and glean MobilityClient EIDs when it decapsulates packets. EdgeRTRs store 276 H3ServiceEIDs and their own RLOC of where the H3ServiceEID is currently 277 reachable from in the map-cache. These mappings are registered to the LISP 278 mapping system so other EdgeRTRs know where to encapsulate for such EIDs. 279 EdgeRTRs do not register MobilityClients' EIDs at the mapping service as 280 these are temporary-renewed while using the mobility network. Enterprises 281 may provide their own client facing EdgeRTRs to mask their clients geo- 282 whereabouts while using the mobility network. 284 4. Deployment Assumptions 286 The specification described in this document makes the following 287 deployment assumptions: 289 (1) Unique 64-bit HID is associated with each H3 geo-spatial tile 290 (2) MobilityClients and H3ServiceEIDs share this well known index 291 (3) 64-bit BDD state value is associated with each H3-indexed tile 292 (4) Tile state is compiled 16 fields of 4-bits, or max 16 enums 294 |-0-|-1-|-2-|-3-|-4-|-5-|-6-|-7-|-8-|-9-|-A-|-B-|-C-|-D-|-E-|-F-| 295 0123012301230123012301230123012301230123012301230123012301230123 297 Subscription of MobilityClients to the mobility network is constantly renewed 298 while on the move and is not intended as a means of basic connectivity. This 299 is why MobilityClients use DNS/AAA to obtain temporary EIDs and EdgeRTRs 300 and why they use (LISP) data-plane tunnels to communicate using their 301 temporary EIDs with the dynamically assigned EdgeRTRs. 303 MobilityClient are otherwise unaware of the LISP network mechanism or mapping 304 system and simply regard the data-plane tunnels as an application-specific 305 virtual private network (VPN) that supports IPv6 EID addressable geo-state to 306 publish (Ucast), Subscribe (Mcast) H3Services. 308 In order to get access to the MobilityVPN, MobilityClients first authenticate 309 with the MobilityVPN AAA Server. DIAMETER based AAA is typically done at the 310 provider edge (PE) by edge gateways. However, the typical case involves several 311 types of customer equipment connected by wireline, or by wireless to a 312 specific service provider. The Mobility VPN, on the other hand, 313 potentially overlays a number of wireless networks and cloud-edge 314 providers. It also involves dozens of Car-OEM, Driving-Applications, 315 Smart-infrastructure vendors. This is why we require clients to first go 316 through AAA in order to get both a MobilityClientEID and EdgeRTR gateway RLOC 317 opened. 319 ClientXTR performs the following steps in order to use the mobility network: 320 1) obtain the address of the mobility network AAA server using DNS 321 2) obtain MobilityClientEID and EdgeRTR(s) from AAA server using DIAMETER 322 3) renew authorization from AAA while using the mobility network T1 minutes 324 MobilityClient Domain Name Server DIAMETER AAA Mobility EdgeRTR 325 | | | | 326 | nslookup nexagon | | | 327 |------------------->| | | 328 |<-------------------| | | 329 | Mobility AAA IP | | | 330 | | | | 331 | AAR(AVP:IMSI/User/Password/Toyota) | | 332 |--------------------------------------->| | 333 | | | ACR(AVP ClientEID)| 334 | | |------------------>| 335 | | |<------------------| 336 | | | ACA(AVP ClientEID)| 337 | AAA (Client::EID,EdgeRTR::RLOC) | | 338 |<---------------------------------------| | 339 | | | | 340 . . 341 . . 342 . . 343 | Publish IPv6 H3ServiceEID, Subscribe MLDv2 H3ServiceEID | . 344 |----------------------------------------------------------->| 345 . . 346 . . 347 |<-----------------------------------------------------------| 348 | Signal freeing multicast Updates from H3ServiceEIDs | 349 . . 350 . . 351 . . 352 | | | | 353 | AAR(Interim) | | 354 |--------------------------------------->| ACR (Interim) | 355 | | |------------------>| 356 | | |<------------------| 357 | | | ACA (Interim) | 358 |<---------------------------------------| | 359 | AAA (Interim) | | 361 Using this network login and re-login method we ensure that: 362 - the MobilityClientEIDs serve as credentials with the specific EdgeRTRs 363 - EdgeRTRs are not tightly coupled to H3.r9 areas for privacy/load-balance 364 - Mobility Clients do not need to update EdgeRTRs while roaming in an area 366 The same EdgeRTR may serve several H3.r9 areas for smooth ride continuity, 367 and, several EdgeRTRs may load balance an H3.r9 area with high density of 368 originating MobilityClient rides. When a MobilityClient ClientXTR is homed 369 to EdgeRTR, it is able to communicate with H3ServiceEIDs. 371 5. Mobility Clients Network Services 373 The mobility network functions as a standard LISP VPN overlay. 374 The overlay delivers unicast and multicast packets across: 375 - multiple access-networks and radio-access specifications 376 - multiple edie providers, public, private, and hybrid clouds 378 We use data-plane XTRs in the stack of each mobility client and server. 379 ClientXTRs and ServerXTRs are homed to one or more EdgeRTRs at the LISP edge. 380 This structure allows for MobilityClients to "show up" at any time, 381 behind any network provider in a given mobility network administrative 382 domain, and for any H3ServiceEID to be instantiated, moved, or 383 failed-over to any rack in any cloud-provider. The LISP overlay enables 384 these roaming mobility network elements to communicate uninterrupted. 385 This quality is insured by the LISP RFCs. The determination of identities for 386 MobilityClients to always refer to the correct H3ServiceEID is insured by H3 387 geo-spatial HIDs. 389 There are two options for how we associate ClientXTRs with LISP EdgeRTRs: 391 I. Semi-random load-balancing by DNS/AAA 393 In this option we assume that in a given metro edge, a pool of EdgeRTRs can 394 distribute the Mobility Clients load randomly between them and that EdgeRTRs 395 are topologically more or less equivalent. Each RTR uses LISP to tunnel 396 traffic to and from other EdgeRTRs for MobilityClient with H3Service exchanges. 397 MobilityClients can (multi) home to EdgeRTRs while moving. 399 II. Topological by anycast 401 In this option we align an EdgeRTR with topological aggregation like in 402 Evolved Packet or 5GCore aggregation. Mobility Clients are roaming in an 403 area home to that RTR and so is the H3 Server. There is only one hop across 404 the edge overlay between clients and servers and mcast replication is more 405 focused, but clients need to keep re-homing as they move. 407 To summarize the H3LISP mobility network layout: 409 (1) Mobility-Clients traffic is tunneled via data-plane ClientXTRs 410 ClientXTRs are (multi) homed to EdgeRTR(s) 411 (2) H3ServiceEID traffic is tunneled via data-plane ServerXTR 412 ServerXTRs are (multi) homed to EdgeRTR(s) 413 (3) EdgeRTRs use mapping service to resolve Ucast HIDs to RTR RLOCs 414 EdgeRTRs also register to (Source, Group) H3ServiceEID multicasts 416 MobilityClients <> ClientXTR EdgeRTR v 417 v 418 v << Map-Assisted Mobility-Network Overlay << v 419 v 420 >> EdgeRTR ServerXTR <> H3ServiceEID 422 6. Mobility Unicast and Multicast 424 Regardless of the way a given ClientXTR was associated with an EdgeRTR, 425 an authenticated MobilityClient EID can send: [64bitH3.15ID :: 64bitState] 426 annotations to the H3.r9 H3ServiceEID. The H3.r9 EID can be calculated by 427 clients algorithmically from the H3.15 localized annotation snapped-to-tile. 429 The ClientXTR encapsulates MobilityClient EID and H3ServiceEID in a packet 430 sourced from the ClientXTR with the destination of the EdgeRTR RLOC LISP port. 431 EdgeRTRs then re-encapsulate annotation packets either to remote EdgeRTR 432 (option 1) or to homed H3ServiceEID ServerXTR (option 2). 433 The remote EdgeRTR aggregating H3ServiceEIDs re-encapsulates MobilityClient 434 EID to the ServerXTR and from there to the H3ServiceEID. 436 0 1 2 3 437 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 438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ 439 |Version| Traffic Class | Flow Label | | 440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 441 | Payload Length | Next Header | Hop Limit | | 442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 443 | | | 444 + + | 445 | | | 446 + Source MobilityClientEID + | 447 | | IPv6 448 + + | 449 | | | 450 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 451 | | | 452 + + | 453 | | | 454 + Dest H3ServiceEID + | 455 | | | 456 + + | 457 | | / 458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 459 | Source Port = xxxx | Dest Port = xxxx | \ 460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ UDP 461 | UDP Length | UDP Checksum | / 462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ 463 | Type |gzip | Reserved | Pair Count = X| Nexgon Header 464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / 465 | | 466 + 64 Bit H3-R15 ID + 467 | | 468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 | | 470 + 64 Bit State + 471 | | 472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 473 | | 474 + 64 Bit H3-R15 ID + 475 | | 476 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 477 | | 478 + 64 Bit State + 479 | | 480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 482 To Summarize Unicast: 484 (1) MobilityClients can send annotations which are localized to an H3.r15 tile 485 These annotations are sent to an H3.r9 mobility H3ServiceEIDs 486 (2) MobilityClient EID and H3ServiceEID HID are encapsulated: 487 XTR <> RTR <> RTR <> XTR 488 * RTRs can map-resolve re-tunnel HIDs 489 (3) RTRs re-encapsulate original source-dest to ServerXTRs 490 ServerXTRs decapsulate packets to H3ServiceEID 492 Each H3.r9 Server is also an IP Multicast channel Source used to update 493 subscribers on the aggregate state of the H3.r15 tiles in the H3.r9 Server. 494 This forms a multipoint to multipoint state channel per H3 geo-location, where 495 the H3 hairpin aggregation point has programable propagation functionality. 497 We use rfc8378 signal-free multicast to implement mcast channels in the 498 overlay. The mobility network has many channels, with only a few thousands of 499 subscribers per channel. MobilityClients driving through or subscribing to an 500 H3.r9 area can explicitly issue an rfc4604 MLDv2 in order to subscribe, or, 501 may be subscribed implicitly by the EdgeRTR gleaning to ucast HID destination. 503 The advantage of an explicit client MLDv2 registration as a trigger to rfc8378 504 is that the clients manage their own mobility mcast handover according to their 505 location-direction vectors, and that it allows for otherwise silent, or, 506 non annotating clients. The advantage of EdgeRTR implicit registration is 507 less signaling required. 509 MLDv2 signaling messages are encapsulated between the ClientXTR and the LISP 510 EdgeRTR, therefore there is no requirement for the underlying network to 511 support native multicast. If native access multicast is supported (for example 512 native 5G multicast), then MobilityClient registration to H3ServiceEID 513 safety channels may be integrated with it, in which case the mobile packet-core 514 (EPC) element supporting it (eNB) will use this standard to register with the 515 appropriate H3.r9 channels in its area. 517 Multicast update packets are of the following structure: 519 0 1 2 3 520 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 521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ 522 |Version| Traffic Class | Flow Label | | 523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 524 | Payload Length | Next Header | Hop Limit | | 525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 526 | | | 527 + + | 528 | | | 529 + Source H3-R9 EID Address + | 530 | | IPv6 531 + + | 532 | | | 533 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 534 | | | 535 + + | 536 | | | 537 + Group Address + | 538 | | | 539 + + | 540 | | / 541 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 542 | Source Port = xxxx | Dest Port = xxxx | \ 543 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ UDP 544 | UDP Length | UDP Checksum | / 545 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ 546 | | Nexagons Header 547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / 548 ~ Nexagons Payload ~ 549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 551 Outer headers = 40 (IPv6) + 8 (UDP) + 8 (LISP) = 56 552 Inner headers = 40 (IPv6) + 8 (UDP) + 4 (Nexagon Header) = 52 554 1500 (MTU) - 56 - 52 = 1392 bytes of effective payload 556 Type 1:key-value, key-value.. 1392 / (8 + 8) = 87 pairs 557 Type 2:value, key,key,key.. (1392 - 8) / 8 = 173 H3-R15 IDs 559 0 1 2 3 560 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 561 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ 562 | Type = 1 |gzip | Reserved | Pair Count = X| Nexagon Header 563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / 564 | | 565 + 64 Bit H3-R15 ID + 566 | | 567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 | | 569 + 64 Bit State + 570 | | 571 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 572 | | 573 + 64 Bit H3-R15 ID + 574 | | 575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 576 | | 577 + 64 Bit State + 578 | | 579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 581 0 1 2 3 582 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 583 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ 584 | Type = 2 |gzip | Reserved |H3R15 Count = X| Nexagon Header 585 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / 586 | | 587 + 64 Bit State + 588 | | 589 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 590 | | 591 + 64 Bit H3-R15 ID + 592 | | 593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 594 | | 595 + 64 Bit H3-R15 ID + 596 | | 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 | | 599 + 64 Bit H3-R15 ID + 600 | | 601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 603 ` The remote EdgeRTRs homing MobilityClients in turn replicate the packet to the 604 MobilityClients registered with them. 606 We expect an average of 600 H3.r15 tiles of the full 7^6 (~100K) possible in 607 H3.r9 to be part of any road. The H3.r9 server can transmit the status of all 608 600 or just those with meaningful states based on updated SLA and policy. 610 To Summarize: 612 (1) H3LISP Clients tune to H3.r9 mobility updates using rfc8378 613 H3LISP Client issue MLDv2 registration to H3.r9 HIDs 614 ClientXTRs encapsulate MLDv2 to EdgeRTRs who register (s,g) 616 (2) ServerXTRs encapsulate updates to EdgeRTRs who map-resolve (s,g) RLOCs 617 EdgeRTRs replicate mobility update and tunnel to registered EdgeRTRs 618 Remote EdgeRTRs replicate updates to registered ClientXTRs 620 7. Security Considerations 622 The nexagon layer3 v2v/v2i/v2x network is inherently more secure and private 623 then alternatives because of the indirection. No car or infrastructure element 624 ever communicates directly with MobilityClients. All information is conveyed 625 using shared addressable geo-state. MobilityClients are supposed to receive 626 information only from network channels as a trusted broker without indication 627 as to the origin of the information. This is an important step towards better 628 privacy, security, extendability, and interoperability. 630 In order to be able to use the nexagon mobility network for a given period, 631 the mobility clients go through a DNS/AAA stage by which they obtain their 632 clientEID identifiers-credentials and the RLOCs of EdgeRTRs they may use as 633 gateways to the network. This MobilityClient <> EdgeRTR interface is the most 634 sensitive in this network to privacy and security considerations. 636 The traffic on the MobilityClient<>EdgeRTR interface is tunneled and its UDP 637 content may be encrypted; still, the EdgeRTR will know based on the LISP 638 headers alone the MobilityClient RLOC and H3-R9 (~0.1sqkm) geo-spatial area 639 to which a given client publishes or subscribes to. 641 For this reason we envision the ability of enterprise or groups of users to 642 "bring their own" EdgeRTRs. BYO-RTR masks individual clients' IP-RLOC to 643 H3-R9 association and is pre-provisioned to be able to use the mapping system 644 and be on a white-list of EdgeRTRs aggregating H3ServiceEIDs. 646 Beyond this sensitive hop, the mapping system does not hold MobilityClientEIDs, 647 and remote EdgeRTRs are only aware of MobilityClient ephemeral EIDs, not their 648 actual IP RLOC or any other mobile-device identifiers. EdgeRTRs register in the 649 mapping (s,g) H3-R9 multicast groups, but which clients reside beyond which 650 EdgeRTR is not in the mapping system, only the AAA server is aware of that. 651 The H3ServiceEIDs themselves decrypt and parse actual H3-R15 annotations; 652 they also consider during this the MobilityClientEID credentials to avoid 653 "fake-news", but again these are only temporary EIDs allocated to clients 654 in order to be able to use the mobility network and not for their actual IP. 656 8. Acknowledgments 658 This work is partly funded by the ANR LISP-Lab project #ANR- 659 13-INFR-009 (https://lisplab.lip6.fr). 661 9. IANA Considerations 663 I. Formal H3 to IPv6 EID mapping 665 II. State enum fields of H3 tiles: 667 Field 0x: Traffic Direction { 668 0x - null 669 1x - Lane North 670 2x - Lane North + 30 671 3x - Lane North + 60 672 4x - Lane North + 90 673 5x - Lane North + 120 674 6x - Lane North + 150 675 7x - Lane North + 180 676 8x - Lane North + 210 677 9x - Lane North + 240 678 Ax - Lane North + 270 679 Bx - Lane North + 300 680 Cx - Lane North + 330 681 Dx - junction 682 Ex - shoulder 683 Fx - sidewalk 684 } 686 field 1x: Persistent or Structural { 687 0x - null 688 1x - pothole light 689 2x - pothole severe 690 3x - speed-bump low 691 4x - speed-bump high 692 5x - icy 693 6x - flooded 694 7x - snow-cover 695 8x - snow-deep 696 9x - construction cone 697 Ax - gravel 698 Bx - choppy 699 Cx - blind-curve 700 Dx - steep-slope 701 Ex - low-bridge 702 } 704 field 2x: Transient Condition { 705 0x - null 706 1x - pedestrian 707 2x - bike scooter 708 3x - stopped car / truck 709 4x - moving car / truck 710 5x - first responder vehicle 711 6x - sudden slowdown 712 7x - oversized over-height vehicle 713 8x - red-light-breach 714 9x - light collision (fender bender) 715 Ax - hard collision / casualty 716 Bx - collision course car/structure 717 Cx - recent collision residues 718 Dx - hard brake 719 Ex - sharp cornering 720 Fx - freeing-parking 721 } 723 field 3x: Traffic-light Cycle { 724 0x - null 725 1x - 1 seconds to green 726 2x - 2 seconds to green 727 3x - 3 seconds to green 728 4x - 4 seconds to green 729 5x - 5 seconds to green 730 6x - 6 seconds to green 731 7x - 7 seconds to green 732 8x - 8 seconds to green 733 9x - 9 seconds to green 734 Ax - 10 seconds or less 735 Bx - 20 seconds or less 736 Cx - 30 seconds or less 737 Dx - 60 seconds or less 738 Ex - green now 739 Fx - red now 740 } 742 field 4x: Impacted Tile from Neighboring { 743 0x - null 744 1x - epicenter 745 2x - light yellow 746 3x - yellow 747 4x - light orange 748 5x - orange 749 6x - light red 750 7x - red 751 8x - light blue 752 9x - blue 753 Ax - green 754 Bx - light green 755 } 757 field 5x: Transient, Cycle, Impacted, Valid for Next{ 758 0x - null 759 1x - 1sec 760 2x - 5sec 761 3x - 10sec 762 4x - 20sec 763 5x - 40sec 764 6x - 60sec 765 7x - 2min 766 8x - 3min 767 9x - 4min 768 Ax - 5min 769 Bx - 10min 770 Cx - 15min 771 Dx - 30min 772 Ex - 60min 773 Fx - 24hours 774 } 776 field 6x: LaneRightsSigns { 777 0x - null 778 1x - yield 779 2x - speedLimit 780 3x - straightOnly 781 4x - noStraight 782 5x - rightOnly 783 6x - noRight 784 7x - rightStraight 785 8x - leftOnly 786 9x - leftStraight 787 Ax - noLeft 788 Bx - noUTurn 789 Cx - noLeftU 790 Dx - bikeLane 791 Ex - HOVLane 792 Fx - Stop 793 } 795 field 7x: MovementSigns { 796 0x - null 797 1x - keepRight 798 2x - keepLeft 799 3x - stayInLane 800 4x - doNotEnter 801 5x - noTrucks 802 6x - noBikes 803 7x - noPeds 804 8x - oneWay 805 9x - parking 806 Ax - noParking 807 Bx - noStandaing 808 Cx - noPassing 809 Dx - loadingZone 810 Ex - railCross 811 Fx - schoolZone 812 } 814 field 8x: CurvesIntersectSigns { 815 0x - null 816 1x - turnsLeft 817 2x - turnsRight 818 3x - curvesLeft 819 4x - curvesRight 820 5x - reversesLeft 821 6x - reversesRight 822 7x - windingRoad 823 8x - hairPin 824 9x - pretzelTurn 825 Ax - crossRoads 826 Bx - crossT 827 Cx - crossY 828 Dx - circle 829 Ex - laneEnds 830 Fx - roadNarrows 831 } 833 field 9x: Current Tile Speed { 834 0x - null 835 1x - < 5kmh 836 2x - < 10kmh 837 3x - < 15kmh 838 4x - < 20kmh 839 5x - < 30kmh 840 6x - < 40kmh 841 7x - < 50kmh 842 8x - < 60kmh 843 9x - < 80kmh 844 Ax - < 100kmh 845 Bx - < 120kmh 846 Cx - < 140kmh 847 Dx - < 160kmh 848 Ex - > 160kmh 849 Fx - queuedTraffic 850 } 852 field Ax: Vehicle / Pedestrian Traffic { 853 0x - null 854 1x - probability of ped/vehicle on tile close to 100% 855 2x - 95% 856 3x - 90% 857 4x - 85% 858 5x - 80% 859 6x - 70% 860 7x - 60% 861 8x - 50% 862 9x - 40% 863 Ax - 30% 864 Bx - 20% 865 Cx - 15% 866 Dx - 10% 867 Ex - 5% 868 Fx - probability of ped/vehicle on tile close to 0%, empty 869 } 871 filed Bx - reserved AV problem type in tile { 872 0x - null 873 1x - stall 874 } 875 field Cx - reserved 876 field Dx - reserved 877 field Ex - reserved 878 field Fx - reserved platoon identifier types { 879 0x - null 880 1x - US 7Char plate, 881 } 883 10. Normative References 885 [I-D.ietf-lisp-rfc6833bis] 886 Fuller, V., Farinacci, D., and A. Cabellos-Aparicio, 887 "Locator/ID Separation Protocol (LISP) Control-Plane", 888 draft-ietf-lisp-rfc6833bis-07 (work in progress), December 889 2017. 891 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 892 Requirement Levels", BCP 14, RFC 2119, 893 DOI 10.17487/RFC2119, March 1997, 894 . 896 [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The 897 Locator/ID Separation Protocol (LISP)", RFC 6830, 898 DOI 10.17487/RFC6830, January 2013, 899 . 901 [RFC8378] Farinacci, D., Moreno, V., "Signal-Free Locator/ID Separation 902 Protocol (LISP) Multicast", RFC8378, 903 DOI 10.17487/RFC8378, May 2018, 904 . 906 Authors' Addresses 908 Sharon Barkai 909 Nexar 910 CA 911 USA 913 Email: sbarkai@gmail.com 915 Bruno Fernandez-Ruiz 916 Nexar 917 London 918 UK 920 Email: b@getnexar.com 922 S ZionB 923 Nexar 924 Israel 926 Email: sharon@fermicloud.io 928 Rotem Tamir 929 Nexar 930 Israel 932 rotem.tamir@getnexar.com 934 Alberto Rodriguez-Natal 935 Cisco Systems 936 170 Tasman Drive 937 San Jose, CA 938 USA 940 Email: natal@cisco.com 942 Fabio Maino 943 Cisco Systems 944 170 Tasman Drive 945 San Jose, CA 946 USA 948 Email: fmaino@cisco.com 950 Albert Cabellos-Aparicio 951 Technical University of Catalonia 952 Barcelona 953 Spain 955 Email: acabello@ac.upc.edu 957 Jordi Paillissé-Vilanova 958 Technical University of Catalonia 959 Barcelona 960 Spain 962 Email: jordip@ac.upc.edu 964 Dino Farinacci 965 lispers.net 966 San Jose, CA 967 USA 969 Email: farinacci@gmail.com