idnits 2.17.1 draft-brew-intarea-underground-01.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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 127 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 2020) is 1562 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) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Area Working Group Rob Brew 2 Internet Draft Rydal Inc. 3 Intended status: Standards Track January 2020 4 Expires: July 16, 2020 6 GPS Over WiFi. 7 draft-brew-intarea-underground-01 9 Abstract 11 When users are at known underground locations, such as tube stations 12 they often do not have a GPS signal, as the radio waves from the 13 satellites required cannot penetrate the earth, this draft suggests 14 providing GPS locations over WiFI using remote IP detection for a 15 server to respond with the correct name of clients location and 16 the clients GPS location.IP address. 18 Extending this to those without WiFI access the standard goes one 19 stage further, by offering a hidden WiFI network with a standard name, 20 such as .location. The principle being that mobile devices can 21 look for this network in cases where GPS data cannot be collected. It 22 is hoped that this will allow those using mapping services to know 23 where they are when travelling on underground trains etc. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six 36 months and may be updated, replaced, or obsoleted by other documents 37 at any time. It is inappropriate to use Internet-Drafts as 38 reference material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on August 13, 2018. 42 Copyright Notice 44 Copyright (c) 2020 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF 48 Trust's Legal Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with 52 respect to this document. Code Components extracted from this 53 document must include Simplified BSD License text as described in 54 Section 4.e of the Trust Legal Provisions and are provided without 55 warranty as described in the Simplified BSD License. 57 1. Introduction 59 1.1 Motivation 61 Those travelling underground networks, such as the London underground 62 or the German autobahn do know where they are when underground. At 63 best apps such as citymapper will estimate where people are based 64 on the time the carridge takes to get to their location. It would 65 be convenient for them to know where they are. This protocol resolves 66 this problem, not just to those who have a wireless location but also 67 to those who do not. 69 1.2 The code for this servlet, implemented in Java running on tomcat8 70 is available at https://www.github.com/rydal/underground. 72 1.3 Security considerations: In order to prevent spoofing of the 73 location https can be used. 75 1.4 IANA Considerations: 76 This document has no actions for IANA. 78 2. Mechanisms. 79 2.1 80 The Server, with the aforementioned outline code, knows the IP 81 address of the WiFi hot spot. It holds a list of GPS locations, 82 related to the IP address of the provided underground network. 83 Using this list it responds to the client (the Wireless 84 network of the underground network), with the relevant GPS 85 co-ordinates of the physical site being referenced by the 86 incoming IP address. The server responds with a name of the 87 location, it's GPS latitude and GPS longitude in a JSON array. 89 2.2: 90 Making this more accessible, including to user's not currently 91 connected to a WiFi network, we can implement a hidden wireless 92 network with a standardized name, such as ".location". 94 The operating system's of mobile phones can then search for 95 such a wireless network when GPS is unavailable. The hidden 96 wireless network can then act in the same manner as described 97 in section 2.1. 99 2.3: 100 As referenced in section 1.3. Standard https encryption can 101 prevent location spoofing. 103 3. 104 Interested parties: 105 The transport organisations for the relevant underground locations 106 would need to be involved in this to provide said wireless 107 networks. The mobile manufacturers would need to add a function 108 to their GPS location code. 110 Author's Address 111 Rob Brew 112 flat 5, Rydal mount, 20 hayne road, beckenham, kent, br3 4hy 113 UK 114 Phone: +44 7782200684 116 EMail: sputnik2012@gmail.com