idnits 2.17.1 draft-jeong-ipwave-iot-dns-autoconf-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 : ---------------------------------------------------------------------------- ** 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.) == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 232 has weird spacing: '...ntifier devic...' == Line 402 has weird spacing: '...ntifier devic...' -- The document date (March 13, 2017) is 2573 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) ** Obsolete normative reference: RFC 6106 (Obsoleted by RFC 8106) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 3736 (Obsoleted by RFC 8415) Summary: 4 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Jeong 3 Internet-Draft Sungkyunkwan University 4 Intended status: Standards Track S. Lee 5 Expires: September 14, 2017 KETI 6 J. Park 7 ETRI 8 March 13, 2017 10 DNS Name Autoconfiguration for Internet of Things Devices 11 draft-jeong-ipwave-iot-dns-autoconf-00 13 Abstract 15 This document specifies an autoconfiguration scheme for device 16 discovery and service discovery. Through the device discovery, this 17 document supports the global (or local) DNS naming of Internet of 18 Things (IoT) devices, such as sensors, actuators, and in-vehicle 19 units. By this scheme, the DNS name of an IoT device can be 20 autoconfigured with the device's model information in wired and 21 wireless target networks (e.g., vehicle, road network, home, office, 22 shopping mall, and smart grid). Through the service discovery, IoT 23 users (e.g., drivers, passengers, home residents, and customers) in 24 the Internet (or local network) can easily identify each device for 25 monitoring and remote-controlling it in a target network. 27 Status of This Memo 29 This Internet-Draft is submitted to IETF in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF), its areas, and its working groups. Note that 34 other groups may also distribute working documents as Internet- 35 Drafts. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 The list of current Internet-Drafts can be accessed at 43 http://www.ietf.org/ietf/1id-abstracts.txt. 45 The list of Internet-Draft Shadow Directories can be accessed at 46 http://www.ietf.org/shadow.html. 48 This Internet-Draft will expire on September 14, 2017. 50 Copyright Notice 52 Copyright (c) 2017 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 1.1. Applicability Statements . . . . . . . . . . . . . . . . . 4 69 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 70 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 5. DNS Name Autoconfiguration . . . . . . . . . . . . . . . . . . 5 73 5.1. DNS Name Format with Object Identifier . . . . . . . . . . 5 74 5.2. Procedure of DNS Name Autoconfiguration . . . . . . . . . 6 75 5.2.1. DNS Name Generation . . . . . . . . . . . . . . . . . 6 76 5.2.2. DNS Name Collection . . . . . . . . . . . . . . . . . 7 77 5.2.3. DNS Name Retrieval . . . . . . . . . . . . . . . . . . 8 78 6. Location-Aware DNS Name Configuration . . . . . . . . . . . . 9 79 7. Macro-Location-Aware DNS Name . . . . . . . . . . . . . . . . 10 80 8. Micro-Location-Aware DNS Name . . . . . . . . . . . . . . . . 10 81 9. DNS Name Management for Mobile IoT Devices . . . . . . . . . . 10 82 10. Service Discovery for IoT Devices . . . . . . . . . . . . . . 11 83 11. Security Considerations . . . . . . . . . . . . . . . . . . . 11 84 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 85 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 86 13.1. Normative References . . . . . . . . . . . . . . . . . . . 12 87 13.2. Informative References . . . . . . . . . . . . . . . . . . 13 88 Appendix A. Changes from draft-jeong-its-iot-dns-autoconf-01 . . 14 90 1. Introduction 92 Many Internet of Things (IoT) devices (e.g., sensors, actuators, and 93 in-vehicle units) have begun to have wireless communication 94 capability (e.g., WiFi, Bluetooth, and ZigBee) for monitoring and 95 remote-controlling in a local network or the Internet. According to 96 the capacity, such IoT devices can be categorized into high-capacity 97 devices and low-capacity devices. High-capacity devices have a high- 98 power processor and a large storage, such as vehicles, road 99 infrastructure devices (e.g., road-side unit, traffic light, and 100 loop-detector), appliances (e.g., television, refrigerator, air 101 conditioner, and washing machine), and smart devices (smartphone and 102 tablet). They are placed in environments (e.g., vehicle, road 103 network, home, office, shopping mall, and smart grid) for the direct 104 use for human users, and they require the interaction with human 105 users. Low-capacity devices have a low-power processor and a small 106 storage, such as sensors (e.g., in-vehicle units, light sensor, 107 meter, and fire detector) and actuators (e.g., vehicle engine, signal 108 light, street light, and room temperature controller). They are 109 installed for the easy management of environments (e.g., vehicle, 110 road network, home, office, store, and factory), and they do not 111 require the interaction with human users. 113 For the Internet connectivity of IoT devices, a variety of parameters 114 (e.g., address prefixes, default routers, and DNS servers) can be 115 automatically configured by Neighbor Discovery (ND) for IP Version 6, 116 IPv6 Stateless Address Autoconfiguration, and IPv6 Router 117 Advertisement (RA) Options for DNS Configuration [RFC4861][RFC4862] 118 [RFC6106]. 120 For these IoT devices, the manual configuration of DNS names will be 121 cumbersome and time-consuming as the number of them increases rapidly 122 in a network. It will be good for such DNS names to be automatically 123 configured such that they are readable to human users. 125 Multicast DNS (mDNS) in [RFC6762] can provide DNS service for 126 networked devices on a local link (e.g., home network and office 127 network) without any conventional recursive DNS server. mDNS also 128 supports the autoconfiguration of a device's DNS name without the 129 intervention of the user. mDNS aims at the DNS naming service for the 130 local DNS names of the networked devices on the local link rather 131 than the DNS naming service for the global DNS names of such devices 132 in the Internet. However, for IoT devices accessible from the 133 Internet, mDNS cannot be used. Thus, a new autoconfiguration scheme 134 becomes required for the global DNS names of IoT devices. 136 This document proposes an autoconfiguration scheme for the global (or 137 local) DNS names of IoT devices. Since an autoconfigured DNS name 138 contains the model identifier (ID) of a device, IoT users in the 139 Internet (or local network) can easily identify the device. With 140 this model ID, they will be able to monitor and remote-control each 141 device with mobile smart devices (e.g., smartphone and tablet) by 142 resolving its DNS name into the corresponding IPv6 address. 144 1.1. Applicability Statements 146 It is assumed that IoT devices have networking capability through 147 wired or wireless communication media, such as Ethernet [IEEE-802.3], 148 WiFi [IEEE-802.11][IEEE-802.11a][IEEE-802.11b][IEEE-802.11g] 149 [IEEE-802.11n], Dedicated Short-Range Communications (DSRC) 150 [IEEE-802.11p], Bluetooth [IEEE-802.15.1], and ZigBee [IEEE-802.15.4] 151 in a local area network (LAN) or personal area network (PAN). 153 Also, it is assumed that each IoT device has a factory configuration 154 (called device configuration) having device model information by 155 manufacturer ID and model ID (e.g., vehicle, road-side unit, smart 156 TV, smartphone, tablet, and refrigerator). This device configuration 157 can be read by the device for DNS name autoconfiguration. 159 2. Requirements Language 161 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 162 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 163 document are to be interpreted as described in RFC 2119 [RFC2119]. 165 3. Terminology 167 This document uses the terminology described in [RFC4861] and 168 [RFC4862]. In addition, four new terms are defined below: 170 o Device Configuration: A factory configuration that has device 171 model information by manufacturer ID and model ID (e.g., vehicle, 172 road-side unit, smart TV, smartphone, tablet, and refrigerator). 174 o DNS Search List (DNSSL): The list of DNS suffix domain names used 175 by IPv6 hosts when they perform DNS query searches for short, 176 unqualified domain names [RFC6106]. 178 o DNSSL Option: IPv6 RA option to deliver the DNSSL information to 179 IPv6 hosts [RFC6106]. 181 4. Overview 183 This document specifies an autoconfiguration scheme for an IoT device 184 using device configuration and DNS search list. Device configuration 185 has device model information (e.g., device's manufacturer and model). 187 DNS search list has DNS suffix domain names that represent the DNS 188 domains of a network having the IoT device [RFC6106]. 190 As an IPv6 host, the IoT device can obtain DNS search list through 191 IPv6 Router Advertisement (RA) with DNS Search List (DNSSL) Option 192 [RFC4861][RFC6106] or DHCPv6 with Domain Search List Option 193 [RFC3315][RFC3736][RFC3646]. 195 The IoT device can construct its DNS name with the concatenation of 196 manufacturer ID, model ID, and domain name. Since there exist more 197 than one device with the same model, the DNS name should have a 198 unique identification (e.g., unique ID or serial ID) to differentiate 199 multiple devices with the same model. 201 Since both RA and DHCPv6 can be simultaneously used for the parameter 202 configuration for IPv6 hosts, this document considers the DNS name 203 autoconfiguration in the coexistence of RA and DHCP. 205 5. DNS Name Autoconfiguration 207 The DNS name autoconfiguration for an IoT device needs the 208 acquisition of DNS search list through either RA [RFC6106] or DHCPv6 209 [RFC3646]. Once the DNS search list is obtained, the IoT device 210 autonomously constructs its DNS name(s) with the DNS search list and 211 its device information. 213 5.1. DNS Name Format with Object Identifier 215 A DNS name for an IoT device can have the following format with 216 object identifier (OID), which is defined in [oneM2M-OID], as in 217 Figure 1: 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | unique_id.object_identifier.OID.domain_name | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 Figure 1: IoT Device DNS Name Format with OID 225 Fields: 227 unique_id unique identifier to guarantee the uniqueness 228 of the DNS name in ASCII characters. The 229 identifier MAY be alphanumeric with readability, 230 e.g., product name plus a sequence number. 232 object_identifier device's object identifier that consists of a 233 higher arc, that is, M2M node indication ID ( 234 i.e., the concatenation of the managing 235 organization, administration, data country 236 code, and M2M node) and a sequence of four 237 arcs (i.e., manufacturer ID, model ID, serial 238 ID, and expanded ID) as defined in 239 [oneM2M-OID]. The fields are seperated by an 240 underscore '_'. 242 OID subdomain for the keyword of OID to indicate 243 that object_identifier is used. 245 domain_name domain name that represents a DNS domain for 246 the network having the IoT devices. 248 Note each subdomain (i.e., unique_id, object_identifier, OID, and 249 domain_name) in the domain name format in Figure 1 is expressed using 250 the name syntax described in [RFC1035]. 252 5.2. Procedure of DNS Name Autoconfiguration 254 The procedure of DNS name autoconfiguration is performed through a 255 DNSSL option delivered by either RA [RFC6106] or DHCPv6 [RFC3646]. 257 5.2.1. DNS Name Generation 259 When as an IPv6 host a device receives a DNSSL option through either 260 RA or DHCPv6, it checks the validity of the DNSSL option. If the 261 option is valid, the IPv6 host performs the DNS name 262 autoconfiguration with each DNS suffix domain name in the DNSSL 263 option as follows: 265 1. The host constructs its DNS name with the DNS suffix domain name 266 along with device configuration (i.e., manufacturer ID, model ID, 267 and serial ID) and a selected identifier (as unique_id) that is 268 considered unique, which is human-friendly, as shown in Figure 1. 270 2. The host constructs an IPv6 unicast address as a tentative 271 address with a 64-bit network prefix and the last 64 bits of the 272 MD5 hashed value of the above DNS name. 274 3. The host constructs the solicited-node multicast address in 275 [RFC4861] corresponding to the tentative IPv6 address. 277 4. The host performs Duplicate Address Detection (DAD) for the IPv6 278 address with the solicited-node multicast address [RFC4861] 279 [RFC4862]. 281 5. If there is no response from the DAD, the host sets the IPv6 282 tentative address as its IPv6 unicast address and regards the 283 constructed DNS name as unique on the local link. Otherwise, 284 since the DAD fails because of DNS name conflict, go to Step 1 285 for a new DNS name generation with another identifier for 286 unique_id. 288 6. Since the DNS name is proven to be unique, it is used as the 289 device's DNS name and the DNS autoconfiguration is done for the 290 given DNS suffix domain name. Also, the host joins the 291 solicited-node multicast address for the verified DNS name in 292 order to prevent other hosts from using this DNS name. 294 When the DNS search list has more than one DNS suffix domain name, 295 the IPv6 host repeats the above procedure until all of the DNS 296 suffixes are used for the DNS name autoconfiguration along with the 297 IPv6 unicast autoconfiguration corresponding to the DNS name. 299 5.2.2. DNS Name Collection 301 Once as IPv6 hosts the devices have autoconfigured their DNS names, 302 as a collector, any IPv6 node (i.e., router or host) in the same 303 subnet can collect the device DNS names using IPv6 Node Information 304 (NI) protocol [RFC4620]. 306 For a collector to collect the device DNS names without any prior 307 node information, a new NI query needs to be defined. That is, a new 308 ICMPv6 Code (e.g., 3) SHOULD be defined for the collection of the 309 IPv6 host DNS names. The Data field is not included in the ICMPv6 310 header since the NI query is for all the IPv6 hosts in the same 311 subnet. The Qtype field for NI type is set to 2 for Node Name. 313 The query SHOULD be transmitted by the collector to a link-local 314 multicast address for this NI query. Assume that a link-local scope 315 multicast address (e.g., all-nodes multicast address, FF02::1) SHOULD 316 be defined for device DNS name collection such that all the IPv6 317 hosts join this link-local multicast address for the device DNS name 318 collection service. 320 When an IPv6 host receives this query sent by the collector in 321 multicast, it transmits its Reply with its DNS name with a random 322 interval between zero and Query Response Interval, as defined by 323 Multicast Listener Discovery Version 2 [RFC3810]. This randomly 324 delayed Reply allows the collector to collect the device DNS names 325 with less frame collision probability by spreading out the Reply time 326 instants. 328 After the collector collects the device DNS names, it resolves the 329 DNS names into the corresponding IPv6 addresses by NI protocol 330 [RFC4620] with the ICMPv6 Code 1 of NI Query. This code indicates 331 that the Data field of the NI Query has the DNS name of an IoT 332 device. The IoT device that receives this NI query sends the 333 collector an NI Reply with its IPv6 address in the Data field. 335 For DNS name resolution service, the collector can register the 336 pair(s) of DNS name and IPv6 address for each IPv6 host into an 337 appropriate designated DNS server for the DNS domain suffix of the 338 DNS name. It is assumed that the collector is configured to register 339 DNS names into the designated DNS server in a secure way based on 340 DNSSEC [RFC4033][RFC6840]. This registration of the DNS name and 341 IPv6 address can be performed by DNS dynamic update [RFC2136]. 342 Before registering the DNS name into the designated DNS server, the 343 collector SHOULD verify the uniqueness of the DNS name in the 344 intended DNS domain by sending a DNS query for the resolution of the 345 DNS name. If there is no corresponding IPv6 address for the queried 346 DNS name, the collector registers the DNS name and the corresponding 347 IPv6 address into the designated DNS server. On the other hand, if 348 there is such a corresponding IPv6 address, the DNS name is regarded 349 as duplicate (i.e., not unique), and so the corresponder notifies the 350 corresponding IoT device with the duplicate DNS name of an error 351 message of DNS name duplication using NI protocol. When an IoT 352 device receives such a DNS name duplication error, it needs to 353 construct a new DNS name and repeats the procedure of device DNS name 354 generation along with the uniqueness test of the device DNS name in 355 its subnet. 357 The two separate procedures of the DNS name collection and IPv6 358 address resolution in the above NI protocol can be consolidated into 359 a single collection for the pairs of DNS names and the corresponding 360 IPv6 addresses. For such an optimization, a new ICMPv6 Code (e.g., 361 4) is defined for the NI Query to query the pair of a DNS name and 362 the corresponding IPv6 address. With this code, the collector can 363 collect the pairs of each IoT device's DNS name and IPv6 address in 364 one NI query message rather than two NI query messages. 366 5.2.3. DNS Name Retrieval 368 A smart device like smartphone can retrieve the DNS names of IoT 369 devices by contacting a global (or local) DNS server having the IoT 370 device DNS names. If the smart device can retrieve the zone file 371 with the DNS names, it can display the information of IoT devices in 372 a target network, such as home network and office network. With this 373 information, the user can monitor and control the IoT devices in the 374 Internet (or local network). 376 6. Location-Aware DNS Name Configuration 378 If the DNS name of an IoT device includes location information, it 379 allows users to easily identify the physical location of each device. 380 This document proposes the representation of a location in a DNS 381 name. In this document, the location in a DNS name consists of two 382 levels for a detailed location specification, such as macro-location 383 for a large area and micro-location for a small area. 385 To denote both macro-location (i.e., mac_loc) and micro-location 386 (i.e., mic_loc) into a DNS name, the following format is described as 387 in Figure 2: 389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 390 | unique_id.object_identifier.OID.mic_loc.mac_loc.LOC.domain_name | 391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 393 Figure 2: Location-Aware Device DNS Name Format 395 Fields: 397 unique_id unique identifier to guarantee the uniqueness 398 of the DNS name in ASCII characters. The 399 identifier MAY be alphanumeric with readability, 400 such as product name plus a sequence number. 402 object_identifier device's object identifier that consists of a 403 higher arc, that is, M2M node indication ID ( 404 i.e., the concatenation of the managing 405 organization, administration, data country 406 code, and M2M node) and a sequence of four 407 arcs (i.e., manufacturer ID, model ID, serial 408 ID, and expanded ID) as defined in 409 [oneM2M-OID]. The fields are seperated by an 410 underscore '_'. 412 OID subdomain for the keyword of OID to indicate 413 that object_identifier is used. 415 mic_loc device's micro-location, such as center, edge, 416 and corner. 418 mac_loc device's macro-location, such as road segment. 420 LOC subdomain for the keyword of LOC to indicate 421 that mac_loc and mic_loc are used. 423 domain_name domain name that represents a DNS domain for 424 the network having the IoT devices. 426 Note each subdomain (e.g., mic_loc and mac_loc) in the domain name 427 format in Figure 2 is expressed using the name syntax described in 428 [RFC1035]. 430 7. Macro-Location-Aware DNS Name 432 If location information (such as cross area, intersection, and road 433 segment in a road network) is available to an IoT device, a keyword, 434 coordinate, or location ID for the location information can be used 435 to construct a DNS name as subdomain name. This location information 436 lets users track the position of mobile devices (such as vehicle, 437 smartphone, and tablet). The physical location of the device is 438 defined as macro-location for DNS naming. 440 A subdomain name for macro-location (denoted as mac_loc) MAY be 441 placed between micro-location (denoted as mic_loc) and the keyword 442 LOC of the DNS name format in Figure 2. For the localization of 443 macro-location, a localization scheme for indoor or outdoor can be 444 used [SALA]. 446 8. Micro-Location-Aware DNS Name 448 An IoT device can be located in the center or edge in a place that is 449 specified by macro-location. For example, assume that a loop- 450 detector is located in the start or end position of a road segment. 451 If the DNS name for the loop-detector contains the start or end 452 position of the road segment, a road network administrator can find 453 it easily. In this document, for this DNS naming, the detailed 454 location for an IoT device can be specified as a micro-location 455 subdomain name. 457 A subdomain name for micro-location (denoted as mic_loc) MAY be 458 placed between the keyword OID and macro-location (denoted as 459 mac_loc) of the DNS name format in Figure 2. For the localization of 460 micro-location, a localization scheme for indoor or outdoor can be 461 used [SALA]. 463 9. DNS Name Management for Mobile IoT Devices 465 Some IoT devices can have mobility, such as vehicle, smartphone, 466 tablet, laptop computer, and cleaning robot. This mobility allows 467 the IoT devices to move from a subnet to another subnet where subnets 468 can have different domain suffixes, such as 469 coordinate.road_segment.road, coordinate.intersection.road, 470 living_room.home and garage.home. The DNS name change (or addition) 471 due to the mobility should be considered. 473 To deal with DNS name management in mobile environments, whenever an 474 IoT device enters a new subnet and receives DNS suffix domain names, 475 it generates its new DNS names and registers them into a designated 476 DNS server, specified by RDNSS option. 478 When the IoT device recognizes the movement to another subnet, it can 479 delete its previous DNS name(s) from the DNS server having the DNS 480 name(s), using DNS dynamic update [RFC2136]. For at least one DNS 481 name to remain in a DNS server for the location management in Mobile 482 IPv6 [RFC6275], the IoT device does not delete its default DNS name 483 in its home network in Mobile IPv6. 485 10. Service Discovery for IoT Devices 487 DNS SRV resource record (RR) can be used to support the service 488 discovery of the services provided by IoT devices [RFC2782]. This 489 SRV RR specifies a service name, a transport layer protocol, the 490 corresponding port number, and an IP address of a process running in 491 an IP host as a server to provide a service. An instance for a 492 service can be specified in this SRV RR in DNS-based service 493 discovery [RFC6763]. After the DNS name registration in Section 5.2, 494 IoT devices can register their services in the DNS server via a 495 router with DNS SRV RRs for their services. 497 After the service registration, an IoT user can retrieve services 498 available in his/her target network through service discovery, which 499 can fetch the SRV RRs from the DNS server in the target network. 500 Once (s)he retrieves the list of the SRV RRs, (s)he can remote- 501 monitor or remote-control the devices or their services by the 502 protocol and domain of the servers. 504 11. Security Considerations 506 This document shares all the security issues of the NI protocol that 507 are specified in the "Security Considerations" section of [RFC4620]. 509 To prevent the disclosure of location information for privacy 510 concern, the subdomains related to location can be encrypted by a 511 shared key or public-and-private keys. For example, a DNS name of 512 vehicle1.oid1.OID.coordinate1.road_segment_id1.LOC.road can be 513 represented as vehicle1.oid1.OID.xxx.yyy.LOC.road where vehicle1 is 514 unique ID, oid1 is object ID, xxx is a string of the encrypted 515 representation of the coordinate (denoted as coordinate1) in a road 516 segment, and yyy is a string of the encrypted representation of the 517 road segment ID (denoted as road_segment_id1). Thus, the location of 518 the vehicle1 can be protected from unwanted users by encryption. 520 12. Acknowledgements 522 This work was supported by Basic Science Research Program through the 523 National Research Foundation of Korea (NRF) funded by the Ministry of 524 Science, ICT & Future Planning (2014006438). This work was supported 525 in part by Institute for Information & communications Technology 526 Promotion (IITP) grant funded by the Korea government (MSIP) 527 (10041244, Smart TV 2.0 Software Platform). 529 This document has greatly benefited from inputs by Keuntae Lee and 530 Seokhwa Kim. 532 13. References 534 13.1. Normative References 536 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 537 Requirement Levels", BCP 14, RFC 2119, March 1997. 539 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. 540 Soliman, "Neighbor Discovery for IP Version 6 541 (IPv6)", RFC 4861, September 2007. 543 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 544 Stateless Address Autoconfiguration", RFC 4862, 545 September 2007. 547 [RFC6106] Jeong, J., Park, S., Beloeil, L., and S. 548 Madanapalli, "IPv6 Router Advertisement Options for 549 DNS Configuration", RFC 6106, November 2010. 551 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., 552 Perkins, C., and M. Carney, "Dynamic Host 553 Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, 554 July 2003. 556 [RFC3736] Droms, R., "Stateless Dynamic Host Configuration 557 Protocol (DHCP) Service for IPv6", RFC 3736, 558 April 2004. 560 [RFC3646] Droms, R., Ed., "DNS Configuration options for 561 Dynamic Host Configuration Protocol for IPv6 562 (DHCPv6)", RFC 3646, December 2003. 564 [RFC1035] Mockapetris, P., "Domain Names - Implementation and 565 Specification", RFC 1035, November 1987. 567 [RFC4033] Arends, R., Ed., Austein, R., Larson, M., Massey, 568 D., and S. Rose, "DNS Security Introduction and 569 Requirements", RFC 4033, March 2005. 571 [RFC6840] Weiler, S., Ed. and D. Blacka, Ed., "Clarifications 572 and Implementation Notes for DNS Security (DNSSEC)", 573 RFC 6840, February 2013. 575 13.2. Informative References 577 [RFC6762] Cheshire, S. and M. Krochmal, "Multicast DNS", 578 RFC 6762, February 2013. 580 [RFC4620] Crawford, M. and B. Haberman, Ed., "IPv6 Node 581 Information Queries", RFC 4620, August 2006. 583 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 584 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 586 [RFC2136] Vixie, P., Ed., Thomson, S., Rekhter, Y., and J. 587 Bound, "Dynamic Updates in the Domain Name System 588 (DNS UPDATE)", RFC 2136, April 1997. 590 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, 591 "Mobility Support in IPv6", RFC 6275, July 2011. 593 [IEEE-802.3] IEEE Std 802.3, "IEEE Standard for Ethernet", 594 December 2012. 596 [IEEE-802.11] IEEE Std 802.11, "Part 11: Wireless LAN Medium 597 Access Control (MAC) and Physical Layer (PHY) 598 Specifications", March 2012. 600 [IEEE-802.11a] IEEE Std 802.11a, "Part 11: Wireless LAN Medium 601 Access Control (MAC) and Physical Layer (PHY) 602 specifications - High-speed Physical Layer in the 5 603 GHZ Band", September 1999. 605 [IEEE-802.11b] IEEE Std 802.11b, "Part 11: Wireless LAN Medium 606 Access Control (MAC) and Physical Layer (PHY) 607 specifications - Higher-Speed Physical Layer 608 Extension in the 2.4 GHz Band", September 1999. 610 [IEEE-802.11g] IEEE P802.11g/D8.2, "Part 11: Wireless LAN Medium 611 Access Control (MAC) and Physical Layer (PHY) 612 specifications - Further Higher Data Rate Extension 613 in the 2.4 GHz Band", April 2003. 615 [IEEE-802.11n] IEEE P802.11n/D9.0, "Part 11: Wireless LAN Medium 616 Access Control (MAC) and Physical Layer (PHY) 617 specifications - Amendment 5: Enhancements for 618 Higher Throughput", March 2009. 620 [IEEE-802.11p] IEEE Std 802.11p, "Part 11: Wireless LAN Medium 621 Access Control (MAC) and Physical Layer (PHY) 622 Specifications - Amendment 6: Wireless Access in 623 Vehicular Environments", July 2010. 625 [IEEE-802.15.1] IEEE Std 802.15.1, "Part 15.1: Wireless Medium 626 Access Control (MAC) and Physical Layer (PHY) 627 specifications for Wireless Personal Area Networks 628 (WPANs)", June 2005. 630 [IEEE-802.15.4] IEEE Std 802.15.4, "Part 15.4: Low-Rate Wireless 631 Personal Area Networks (LR-WPANs)", September 2011. 633 [oneM2M-OID] oneM2M, "Object Identifier based M2M Device 634 Identification Scheme", February 2014. 636 [SALA] Jeong, J., Yeon, S., Kim, T., Lee, H., Kim, S., and 637 S. Kim, "SALA: Smartphone-Assisted Localization 638 Algorithm for Positioning Indoor IoT Devices", 639 Springer Wireless Networks , June 2016. 641 [RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR 642 for specifying the location of services (DNS SRV)", 643 RFC 2782, February 2000. 645 [RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service 646 Discovery", RFC 6763, February 2013. 648 Appendix A. Changes from draft-jeong-its-iot-dns-autoconf-01 650 The following changes are made from 651 draft-jeong-its-iot-dns-autoconf-01: 653 o In Section 10, service discovery is added to let IoT users 654 retrieve the services provided by IoT devices. 656 Authors' Addresses 658 Jaehoon Paul Jeong 659 Department of Software 660 Sungkyunkwan University 661 2066 Seobu-Ro, Jangan-Gu 662 Suwon, Gyeonggi-Do 16419 663 Republic of Korea 665 Phone: +82 31 299 4957 666 Fax: +82 31 290 7996 667 EMail: pauljeong@skku.edu 668 URI: http://iotlab.skku.edu/people-jaehoon-jeong.php 670 Sejun Lee 671 Korea Electronics Technology Institute 672 25, Saenari-Ro, Bundang-Gu 673 Seongnam-Si, Gyeonggi-Do 13509 674 Republic of Korea 676 Phone: +82 31 789 7535 677 EMail: prosejun14@gmail.com 679 Jung-Soo Park 680 Electronics and Telecommunications Research Institute 681 218 Gajeong-Ro, Yuseong-Gu 682 Daejeon, 34129 683 Republic of Korea 685 Phone: +82 42 860 6514 686 EMail: pjs@etri.re.kr