Thanks for pointing out the omission on the URI schemes. I'll add normative references to 2616 and 2818.
Use of DHCP option 15 has been the subject of much discussion [1]. I've proposed a small addition below that attempts to capture the essence of that discussion in the document.
On face value, it would seem that the new domain name option is redundant (in DHCPv4). The very frequent misconfiguration of option 15 is scant justification for a new option.
A new option was created to avoid any potential mismatch between the existing uses the option is being put to, and this new use.
Option 15 is commonly used to identify a domain search suffix for local users. In small enterprise, this might be used to identify the small handful of computers in the office - user PCs and maybe a web server. It is envisaged that a LIS is not necessarily within the same scope; a LIS is more likely provided by an ISP or the owner of the physical network infrastructure.
Section 3.4 might be the best place to insert text.
Section 3.4, OLD:
DHCPv4 option 15 [RFC2132] provides an indication of the domain name
that a host uses when resolving hostnames in DNS. This option is
used when the DHCPv4 access domain name is not available.
NEW:
DHCPv4 option 15 [RFC2132] provides an indication of the domain name
that a host uses when resolving hostnames in DNS. The value of
option 15 might have been set without considering its potential use
in discovering a LIS. Option 15 is only used when the DHCPv4 access
domain name is not available.
Cheers,
Martin
[1] <http://www.ietf.org/mail-archive/web/geopriv/current/msg06491.html>
> -----Original Message-----
> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
> Sent: Sunday, 14 February 2010 6:43 AM
> To: iesg@ietf.org
> Cc: geopriv-chairs@tools.ietf.org; draft-ietf-geopriv-lis-
> discovery@tools.ietf.org
> Subject: DISCUSS and COMMENT: draft-ietf-geopriv-lis-discovery
>
> Discuss:
> This is a fine document, I only have one issue that I would like to
> discuss before recommending its approval:
>
> 2. LIS Discovery Procedure
>
> A device MUST support discovery using the access network domain name
> DHCP option (Section 3) as input to U-NAPTR resolution (Section 4).
> If this option is not available, DHCPv4 option 15 [RFC2132] is used.
>
> I would like to see more justification of why the option 15 is not
> acceptable/sufficient for LIS discovery.
>
> Other domain names MAY be used, as described in Section 3.4.
>
> Comment:
> 1. Introduction and Overview
>
> This document describes a process that a device can use to discover
> a
> LIS. This process uses a DHCP option and the DNS. The product of
> this discovery process is an http: or https: URI, which identifies a
>
> URI schemes need references to the correponding RFCs.
>
> LIS.
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
