GEONET Brainstorming Document

Content Purpose of the document Brainstorming process / plan Proposed charter Assumptions Use cases Problem description Solutioning Security and Privacy Issues Related protocols Action items. Plans to go forward GEONET Brainstorming Document

Purpose of the document The purpose of this document is to facilitate the brainstorming related to the GEONET IETF BOF. The goals of the brainstorming exercise is to iterate over use cases, problem statements, and potential solutions. At the end of this exercise we should get to: A better definition of the problem statement A more complete set of use cases An updated proposed charter A potential list of documents that the eventual working group would consider. GEONET Brainstorming Document

Brainstorming Process / Plan Proposed Plan: Use the mailing list to discuss the content of the document. Seek volunteers to provide material for the different sections in the document Consolidate the contributed material Set up a number of web conferences to discuss the document (online BOF) GEONET Brainstorming Document

Pre BOF Proposed Charter The group is concerned with Internet-wide geonetworking. Internet-wide Geo-Networking is a location-aware solution that provides packet delivery using geographical coordinates for packet dissemination over the Internet. The challenges associated with Internet-wide Geonetworking that can be addressed by IETF are: o support of geographical addressing: geographical information should be available in the addressing mechanism; o support of Internet-wide geo-routing: data packets are forwarded over multiple hops by using geographical position of destination node(s); o precision in representing geographical areas. Two main scenarios are: o Environmental Monitoring involves querying devices such as sensors located in specific geographic areas, for applications such as fire hazard prevention. o Vehicular networking used in Intelligent Transportation Systems (ITS) is required to offer a myriad of applications related to vehicles, vehicle traffic, drivers, passengers and pedestrians. Open design issues to be addressed by IETF are: o Geo-addressing in the wired Internet: standard Internet routers are not aware of geo-networking functionality: the addresses used must be regular addresses that are topologically correct and can be routed to / via the first geo-aware access router, e.g. a Road-Side Unit. o Geo-routing forwarding from source node to the correct immediate geo-aware access router, e.g., RSU, (over existing Internet) o Exchanging/communicating destination area information o Lookup and translation of destination (geographical) area to IP address o Updating the location database Security aspects will be considered: influence of the absence of link-layer security in the operation outside the context of a BSS (IEEE p), security of multicast distribution, authenticity of routing message exchanges, and more. GEONET Brainstorming Document The WG will consider and, if necessary - profile, existing IPv6 network protocols: LoST, geopriv WG results, MANET protocols, ICMPv6, MLDv2, DNS. Several Standards Development Organizations external to IETF work towards developing protocols for vehicular communications. In some cases IP protocols are used for transport, in other cases IP protocols are modified for purposes particular to vehicular communications. The WG will survey the following extra-IETF groups: IEEE TGp, IEEE P1609, ETSI TC ITS Networking Group, ISO TC204 WG16, GENIVI Network Experts Group, AUTOSAR Work Package A2, IPSO. When possible, liaisons will be established with these organizations. Work Items Problem statement, use cases, scenarios and requirements of using geonetworking for vehicular communications, as well as Internet-wide geonetworking. Practices and gap analysis for geonetworking for IP vehicular communications: document practices for the deployment of existing IP protocols and identify any limitation of the existing IP protocols to fulfill the scenarios and requirements for geonetworking in IP vehicular communications. The use of IPv6 over p involving a minimum number of intermediary layers. Milestones: Sep Submit individual draft on Internet-wide geonetworking problem statement. (done) Oct Submit individual draft on the use of IPv6-over p link layer. Feb Submit Internet-wide geonetworking requirements Jun Submit Internet-wide geonetworking gap analysis Nov Submit Internet-wide geonetworking framework/architecture Mar Submit Internet-wide geonetworking protocol.

Assumption In any solution there has to be a network element that keeps a real time mapping between IP addresses and geographical area. In one solution I think it was called a Geoserver. In the other solution it was called EDNS. But seems to have the same overall function There has to be a mechanism for a source to find the Geoserver to retrieve the IP addresses for the area of interest There has to be a mechanism for a device or an intermediary (Router) to register IP addresses at the Geoserver. Just like there is a concept of source node that would send packets to Ips in a geographic areas, is there the concept of destination node that receives information from IP addresses in a geographic areas GEONET Brainstorming Document

Problem Description How do we define a geographic area? Is it a point and a radius, or is it more complex? How do we handle overlap and devices that exist in multiple areas Is the Geoserver global? Or are there many regional Geoservers? How does a device opt in to receive the communication? Do we support proxies that register other devices? (RAN, Router in front of a private network) Do we need to worry about these packets traversing private networks or do we only worry about public IP addresses? What is the frequency of updates to the geomapping? Does it depend on device? GEONET Brainstorming Document

Use Cases Environmental Monitoring involves querying devices such as sensors located in specific geographic areas, for applications such as fire hazard prevention. Vehicular networking used in Intelligent Transportation Systems (ITS) is required to offer a myriad of applications related to vehicles, vehicle traffic, drivers, passengers and pedestrians. Looking for a webcam in an area Localized Marketing offers (attractive Business case) Social Networking, Locating friends Locating Services GEONET Brainstorming Document

Security and Privacy Since this traffic is not a response to a direct request, and unless there are laws to allow the sending of the packets. There must be some sort of Optin to the communication, Also that Opt In should include some details about what we the device is Opting in to. Should there be some mechanism for tagging of sources who abuse the Opt in rules. Will there be a mechanism to scrape to reduce abuse? Should sources be authenticate and authorized for types of traffic? GEONET Brainstorming Document

Related Protocols draft-hain-ipv6-pi-addr-10 LOST protocol results of geopriv WG ILNP, LISP, SHIM6 LOC (and RLOC?) record of DNS DHCP options location RFC6225 draft-google-self-published-geofeeds-02 GEONET Brainstorming Document

Action Items (1) a focused problem scope, with an updated problem statement draft (2) the answers to the questions listed in the below o What are the scaling points? o What components need to be involved? o What are the security and privacy considerations? o What existing work is applicable and what existing work is not applicable? o What problems we do NOT want to solve? Most importantly, of course, who will implement and who will deploy? (3) a charter GEONET Brainstorming Document