Re: [DNSOP] Request for Comments on Internet Draft about IoT DNS Name Autoconf
Manning, I will add this thread to DNSOP WG and 6lo WG. This is because a good target application area of my draft is 6lo environment. Today I discussed my draft with Samita, who is a co-chair of 6lo WG. She recommended to me that I can announce my draft to 6lo WG. DNSOP WG and 6lo WG, if you have time and interest in DNS autoconfiguration for constrained nodes (e.g., IoT devices), please attend 6MAN WG meeting from 1PM to 3PM tomorrow (at Congress Hall III). My presentation will be the last one. My draft on DNS name autoconfiguration for constrained nodes can be found in https://tools.ietf.org/html/draft-jeong-homenet-device-name-autoconf-03 Also, you two WG people can give me your comments by email. Thanks. Paul On Fri, Jul 17, 2015 at 6:26 AM, manning wrote: > The reason I ask is that the title is about DNS name autoconfig. It might > be reasonable to run a parallel stream in DNSOPs, in the unlikely event of > problems. > manning > bmann...@karoshi.com > PO Box 12317 > Marina del Rey, CA 90295 > 310.322.8102 > > > > On 16July2015Thursday, at 12:19, Mr. Jaehoon Paul Jeong < > jaehoon.p...@gmail.com> wrote: > > > Hi Manning, > > Sure, my proposal can be discussed in DNSOPS WG. > > Since my proposal uses IPv6 ND(neighbor discovery) and NI(node > information) query, > > 6MAN WG will be a good place to discuss it first. > > After that, if needed, I will be able to introduce it to DNSOPS WG. > > > > Thanks. > > > > Paul > > > > On Fri, Jul 17, 2015 at 2:29 AM, manning wrote: > > Ted et.al. Is there a good reason this is not being discussed in the > DNSOPS WG? > > > > > > manning > > bmann...@karoshi.com > > PO Box 12317 > > Marina del Rey, CA 90295 > > 310.322.8102 > > > > > > > > On 14July2015Tuesday, at 11:16, Ted Hardie wrote: > > > > > Dear Professor Jeong, > > > > > > Thank you for sharing the update to your draft. I note that in the > security section of your draft that you make the following proposal: > > > to prevent the disclosure of location information for privacy > > > concern, the subdomains related to location can be encrypted by a > > > shared key or public-and-private keys. For example, a DNS name of > > > smartphone1.living_room.home can be represented as > > > smartphone1.xxx.home where xxx is a string of the encrypted > > > representation of the subdomain living_room. > > > > > > First, I believe that there are more privacy concerns here than > location privacy. The base format: > > > > > > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > >| > unique_id.device_model.device_category.mic_loc.mac_loc.domain_name| > > > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > > > > > > > proposes to include both the device model and a unique identifier. > > > A naive implementation could easily select its serial number, which > > > would clearly be problematic; even the device model may be an issue > for certain cases (e.g. a medical device). > > > > > > Second, the delegation model here seems to require a consistent view > of both device categories and location names. How do you see that being > produced? > > > > > > Lastly, the privacy mitigation given is not yet clear to me. How > would a user of the DNS determine how to decrypt the encrypted strings? If > the point of the effort is autoconfiguration, relying on out-of-band > configuration for this seems contrary to the goal. If you distribute the > decryption keys within the DNS, however, you are likely to lose whatever > privacy protection is provided. Can you explain this further? > > > regards, > > > > > > Ted Hardie > > > > > > > > > On Tue, Jul 14, 2015 at 6:31 AM, Mr. Jaehoon Paul Jeong < > jaehoon.p...@gmail.com> wrote: > > > Hi 6MAN WG, > > > This is Paul. > > > > > > I would like to let you know a draft for IoT Device DNS Name > Autoconfiguration: > > > > > > > > > > DNS Name Autoconfiguration for Internet of Things Devices > > > (draft-jeong-homenet-device-name-autoconf-03) > > > > > > > https://tools.ietf.org/html/draft-jeong-homenet-device-name-autoconf-03 > > > > > > Abstract > > >This document specifies an autoconfiguration scheme for DNS names of > > >Internet of Things (IoT) devices, such as appliances and sens
[DNSOP] Request for Comments on I-D about IoT DNS Name Autoconf
Hi 6man, 6lo and dnsop folks, There will be a talk about IoT DNS Name Autoconfiguration in 6man WG's morning session tomorrow, 11/4/2015. Title: DNS Name Autoconfiguration for Internet of Things Devices https://tools.ietf.org/html/draft-jeong-6man-iot-dns-autoconf-00 I hope we discuss how to configure the DNS names of IoT devices in networks, such as home network, enterprise network, road network, and factory network with the minimum configuration effort. Imagining that you have hundreds of IoT devices in your network, will you configure their DNS names manually one by one? To prepare for the new wave of IoT networks based on IPv6, we need to think of the DNS naming and auto-registration into DNS for IoT devices. We (SKKU and Jubix) implemented a prototype for a smart grid with electric meters Korea Electric Power Corporation (KEPCO) that is the main power delivery company in South Korea. Our meters are running on IPv6/6lo/Wi-SUN (IEEE 802.15.4g). Since I have 5 minutes for the presentation tomorrow, I will shortly introduce the motivation, the DNS name format based on the ITU-T/ISO object identifier, and our protocol. Please read my draft and slides in the 6man agenda link: https://datatracker.ietf.org/meeting/94/agenda.html The slides has the backup slides (as Appendix slides) that explain the implementation and demonstration, and also the comparison with mDNS. Thanks for reading this email. Best Regards, Paul ======= Mr. Jaehoon (Paul) Jeong, Ph.D. Assistant Professor Department of Software Sungkyunkwan University Office: +82-31-299-4957 Email: jaehoon.p...@gmail.com, paulje...@skku.edu Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Request for Comments on I-D about IoT DNS Name Autoconf
Dear Stuart, Thanks for your constructive comments below. I answer your comments in lines. On Thu, Nov 5, 2015 at 2:51 PM, Stuart Cheshire wrote: > On 3 Nov 2015, at 01:51, Mr. Jaehoon Paul Jeong > wrote: > > > Hi 6man, 6lo and dnsop folks, > > > > There will be a talk about IoT DNS Name Autoconfiguration > > in 6man WG's morning session tomorrow, 11/4/2015. > > > > Title: DNS Name Autoconfiguration for Internet of Things Devices > > https://tools.ietf.org/html/draft-jeong-6man-iot-dns-autoconf-00 > > This was not actually discussed in 6man, 6lo, or dnsop, so I’ll make some > comments here. > > It’s hard to know where to start. > > Your document confuses device discovery with service discovery. What a > device *is* tells you virtually nothing about what it *does*. The “device > category” of my computer being “laptop” or “tablet” tells you *nothing* > about what services it offers. > >> Device model (denoted as device_model) in my proposed DNS name format can let an IoT device refer to the specification of another device's functions, assuming that such the device model's specification is available publicly. Of course, we can use service discovery for device functions, such as dnssd. This is the next step in my draft. For example, for a given Samsung's refrigerator model, such as RF4287HARS (28 cu. ft. French Door Refrigerator Stainless Steel), we can know the functions with the specification. See Samsung's refrigerators: http://www.samsung.com/us/support/appliances/refrigerators > > Your document assumes that every search domain your tablet encounters ( > starbucks.com, narita-airport.co.jp, meeting.ietf.org, comcast.com) will > allow your tablet to create global records in that domain. Clearly this is > nonsense. > >> In Section 7 (DNS Name Management for Mobile IoT Devices), https://tools.ietf.org/html/draft-jeong-6man-iot-dns-autoconf-00#section-7, I discuss the mobility issue of an IoT device to receive multiple search domains. Whenever the IoT device recognizes the movement into another subnet, it can delete its DNS names by DNS dynamic update. In reality, in public areas (e.g., starbucks and narita airport), we can disable the automatic DNS name registration in routers because the registration in the public areas makes some privacy issues. We can enable such automatic > > Having put global address records into starbucks.com, your document > assumes then assumes that starbucks.com will then allow you do to a zone > transfer to fetch the entire zone to discover the names of all the other > address records in starbucks.com. Clearly this is nonsense too. > > Your document proposes global address records with names with this form: > > unique_id.device_model.device_category.mic_loc.mac_loc.domain_name. > > For example: > > > jkadjkhdsafhjlsadfjklkljdgajknsadf.Sungkyunkwan-1234.cleaning-robot.right-upper-corner.living-room.comcast.com > . > > The host name of the cleaning robot keeps changing as it moves around the > room, requiring continual updates and continual zone transfers to keep > track of the name as it changes. Clearly this is infeasible. > > I would, however, love to get one of these new flying cleaning robots, > which can be located (as it was in your example), “in the right-upper > corner of a living room.” > > Stuart Cheshire > > -- === Mr. Jaehoon (Paul) Jeong, Ph.D. Assistant Professor Department of Software Sungkyunkwan University Office: +82-31-299-4957 Email: jaehoon.p...@gmail.com, paulje...@skku.edu Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Request for Comments on I-D about IoT DNS Name Autoconf
Stuart, by mistake, my incomplete email was sent. Here is the complete email. On Thu, Nov 5, 2015 at 2:51 PM, Stuart Cheshire wrote: > On 3 Nov 2015, at 01:51, Mr. Jaehoon Paul Jeong > wrote: > > > Hi 6man, 6lo and dnsop folks, > > > > There will be a talk about IoT DNS Name Autoconfiguration > > in 6man WG's morning session tomorrow, 11/4/2015. > > > > Title: DNS Name Autoconfiguration for Internet of Things Devices > > https://tools.ietf.org/html/draft-jeong-6man-iot-dns-autoconf-00 > > This was not actually discussed in 6man, 6lo, or dnsop, so I’ll make some > comments here. > > It’s hard to know where to start. > > Your document confuses device discovery with service discovery. What a > device *is* tells you virtually nothing about what it *does*. The “device > category” of my computer being “laptop” or “tablet” tells you *nothing* > about what services it offers. > > Your document assumes that every search domain your tablet encounters ( > starbucks.com, narita-airport.co.jp, meeting.ietf.org, comcast.com) will > allow your tablet to create global records in that domain. Clearly this is > nonsense. > >>> Device model (denoted as device_model) in my proposed DNS name format can let an IoT device refer to the specification of another device's functions, assuming that such a device model's specification is available publicly. Of course, we can use service discovery for device functions through dnssd. This service discovery is the next step in my draft. For example, for a given Samsung's refrigerator model, such as RF4287HARS (28 cu. ft. French Door Refrigerator Stainless Steel), we can know the functions with the specification. See Samsung's refrigerators: http://www.samsung.com/us/support/appliances/refrigerators Having put global address records into starbucks.com, your document assumes > then assumes that starbucks.com will then allow you do to a zone transfer > to fetch the entire zone to discover the names of all the other address > records in starbucks.com. Clearly this is nonsense too. > >> In Section 7 (DNS Name Management for Mobile IoT Devices), https://tools.ietf.org/html/draft-jeong-6man-iot-dns-autoconf-00#section-7, I discuss the mobility issue of an IoT device to receive multiple search domains. Whenever the IoT device recognizes the movement into another subnet, it can delete its DNS names by DNS dynamic update. In reality, in public areas (e.g., starbucks and narita airport), we can disable the automatic DNS name registration in routers because the registration in the public areas makes some privacy issues. We can enable such automatic registration in our managed networks, such as home network, office network, smart grid, and factory network. Thus, we can prevent your concern for global DNS names from happening. > > Your document proposes global address records with names with this form: > > unique_id.device_model.device_category.mic_loc.mac_loc.domain_name. > > For example: > > > jkadjkhdsafhjlsadfjklkljdgajknsadf.Sungkyunkwan-1234.cleaning-robot.right-upper-corner.living-room.comcast.com > . > > The host name of the cleaning robot keeps changing as it moves around the > room, requiring continual updates and continual zone transfers to keep > track of the name as it changes. Clearly this is infeasible. > >> To prevent the frequent update of a mobile IoT device's DNS name, the IoT device can update its DNS name in a reasonable time interval. This is a further discussion issue. My point is that the physical location in the DNS name can help users easily track the position of an IoT device. > > I would, however, love to get one of these new flying cleaning robots, > which can be located (as it was in your example), “in the right-upper > corner of a living room.” > >> Me too :-) Thanks. Paul > > Stuart Cheshire > > -- === Mr. Jaehoon (Paul) Jeong, Ph.D. Assistant Professor Department of Software Sungkyunkwan University Office: +82-31-299-4957 Email: jaehoon.p...@gmail.com, paulje...@skku.edu Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
