Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard]

2005-12-01 Thread David W. Hankins
On Thu, Dec 01, 2005 at 03:00:49PM +0200, Pekka Savola wrote: > On Wed, 30 Nov 2005, David W. Hankins wrote: > >Now, perhaps RFCs shouldn't read like "Choose your own Adventure" > >novels. > > My problem is that the spec leaves the algorithm completely open. > There is at least one simple algorit

Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard]

2005-12-01 Thread David W. Hankins
I haven't seen any replies in this corner of the thread. Apologies if this has been covered elsehwere. On Sat, Nov 26, 2005 at 04:27:27PM +0200, Pekka Savola wrote: > I have one major issue with 'Resolution of FQDN Conflicts among DHCP > Clients', the first issue below. It fails to properly de

Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard]

2005-12-01 Thread Pekka Savola
On Wed, 30 Nov 2005, David W. Hankins wrote: On Sat, Nov 26, 2005 at 04:27:27PM +0200, Pekka Savola wrote: I have one major issue with 'Resolution of FQDN Conflicts among DHCP Clients', the first issue below. It fails to properly describe the threats caused by DHCP clients requesting updating n

Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard]

2005-11-29 Thread David W. Hankins
On Mon, Nov 28, 2005 at 01:13:43PM -0500, Sam Hartman wrote: > You need to get sufficiently specific that in practice, the > implementation of this option is not influencing addressing plans. > For example if servers tend to get this wrong in a way that makes it > difficult for me to have multiple

Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard]

2005-11-28 Thread Sam Hartman
> "Bernie" == Bernie Volz (volz) <[EMAIL PROTECTED]> writes: Bernie> For DHCPv6 servers, depending on policy (such as if it is Bernie> the only server or if there is a one address/client Bernie> policy) it may delete everything and add back those that Bernie> are current or may

RE: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard]

2005-11-28 Thread Bernie Volz \(volz\)
tf.org; dhcwg@ietf.org; ietf@ietf.org > Subject: RE: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: > 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed > Standard] > > On Sun, 27 Nov 2005, Bernie Volz (volz) wrote: > > Regarding your one major issue, the up

RE: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard]

2005-11-28 Thread Pekka Savola
On Sun, 27 Nov 2005, Bernie Volz (volz) wrote: Regarding your one major issue, the updater is NOT the entity that gets to decide whether to allow any DNS update to occur or not. It is the DNS server that restricts who can do updates and what they can update. We're assuming that the most likely e

RE: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard]

2005-11-27 Thread Bernie Volz \(volz\)
ber 26, 2005 9:27 AM > To: iesg@ietf.org > Cc: dhcwg@ietf.org; ietf@ietf.org > Subject: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: > 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed > Standard] > > On Mon, 14 Nov 2005, The IESG wrote: > &