idnits 2.17.1 draft-ahn-its-geo-architecture-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 5 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 19, 2016) is 2678 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 68, but not defined == Missing Reference: 'WGS-84' is mentioned on line 94, but not defined -- Possible downref: Normative reference to a draft: ref. 'Geo-Problem' Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 MANET Working Group Sanghyun Ahn 2 Internet Draft University of Seoul 3 Expires: June 11, 2017 December 19, 2016 5 Architectural Framework of IPv6-based Geographical Forwarding for ITS 6 draft-ahn-its-geo-architecture-00.txt 8 Status of this Memo 10 This Internet-Draft is submitted to IETF in full conformance with the 11 provisions of BCP 78 and BCP 79. This document may not be modified, 12 and derivative works of it may not be created, except to format it 13 for publication as an RFC or to translate it into languages other 14 than English. 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 June 11, 2017. 34 Copyright Notice 36 Copyright (c) 2016 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 (http://trustee.ietf.org/ 41 license-info) in effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. 45 Abstract 47 For IPv6-based ITS applications, ITS data packets are required to be 48 delivered based on the geographical location information of 49 the destination ITS node or area. In this draft, we describe 50 the architecture of the IPv6-based Geographical Forwarding System 51 (IGFS). 53 Table of Contents 55 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 56 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4. IPv6-based Geographical Forwarding System . . . . . . . . . . 4 59 5. Other Considerations . . . . . . . . . . . . . . . . . . . . . 4 60 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 1. Requirements notation 65 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 66 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 67 document are to be interpreted as described in [RFC2119]. 69 2. Introduction 71 For the support of IPv6-based ITS (Intelligent Transportation System) 72 applications, ITS data packets are required to be delivered based 73 on the geographical location (longitude and latitude) information of 74 the destination ITS node or area. 76 From the considerations in [Geo-Problem], in this draft, we describe 77 the architecture of the IPv6-based Geographical Forwarding System 78 (IGFS). 80 3. Terminology 82 IPv6-based Geographical Forwarding System (IGFS) 83 The conceptual system consisting of ITS nodes, Location Databases 84 (LDBs), Geographical Forwarding DHCPs (G-DHCPs), etc. 86 ITS node 87 A vehicle or a device (e.g., roadside unit (RSU)) that may 88 generate ITS-related data in the form of IPv6 datagrams. 90 Geographical Location (Geo-location) 91 The location of an ITS node represented in the form of 92 longitude and latitude. The geo-location information 93 is represented in the form of the World Geodetic System 1984 94 (WGS84) [WGS-84] formatted coordinates. 96 Geographical Forwarding 97 IPv6 datagram forwarding based on the geo-location information 98 of the source and the destination ITS node or area. 100 Geographical Forwarding Address (Geo-Address) 101 An IPv6 address for geographical forwarding that belongs to 102 a geographical forwarding address range assigned by IANA. 103 An ITS node should have a geo-address to be involved in 104 geographical forwarding of IPv6 datagrams. 106 Geographical Forwarding DHCP (G-DHCP) Server 107 A DHCP server with geo-addresses to be assigned to ITS nodes. 109 Location Database (LDB) 110 The database with geo-location information of ITS nodes; 111 that is, the database with mapping information of 112 geo-locations and geo-addresses of its associated ITS nodes; 113 there can be more than one LDBs which may form a hierarchy. 115 Destination Area 116 The rectangular area in which this IPv6 datagram needs to be 117 forwarded; that is, all the ITS nodes in the destination area are 118 supposed to receive this IPv6 datagram. 120 4. IPv6-based Geographical Forwarding System 122 The main entities of the IPv6-based Geographical Forwarding System 123 (IGFS) are ITS nodes, Location Databases (LDBs), Geographical 124 Forwarding DHCP (G-DHCP) servers (TBD more, if needed). 126 If a node wishes to involve in geographical forwarding of IPv6 127 datagrams, it SHOULD get a geographical forwarding address 128 (geo-address) from a G-DHCP server with the IPv6 addresses for 129 geographical forwarding. 131 An ITS node SHOULD register its geo-address in the LDB that it is 132 associated with. The association with an LDB is to be defined later. 134 When an ITS node has ITS data to send by geographical forwarding, 135 the geographical location information of the destination ITS node or 136 area can be obtained by referring to one or more LDBs or 137 from the upper layer (e.g., the coordinate information from a map 138 in the application layer). 140 5. Other Considerations 142 TBD. 144 References 146 [Geo-Problem] S. Ahn, "Problem Statements of IPv6-based Geographical 147 Forwarding for ITS", IETF Draft draft-ahn-its-geo-problem-00.txt, 148 2016. 150 Author's Address 152 Sanghyun Ahn 153 University of Seoul 154 90, Cheonnong-dong, Tongdaemun-gu 155 Seoul 130-743 156 Korea 157 Email: ahn@uos.ac.kr