Re: [dhcwg] additional option for dhcpv6

Mark Stapp <mjs@cisco.com> Mon, 21 January 2002 14:54 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11132 for <dhcwg-archive@odin.ietf.org>; Mon, 21 Jan 2002 09:54:06 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA10051 for dhcwg-archive@odin.ietf.org; Mon, 21 Jan 2002 09:54:08 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09764; Mon, 21 Jan 2002 09:43:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09742 for <dhcwg@optimus.ietf.org>; Mon, 21 Jan 2002 09:43:51 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10892 for <dhcwg@ietf.org>; Mon, 21 Jan 2002 09:43:48 -0500 (EST)
Received: from goblet.cisco.com (mirapoint@goblet.cisco.com [161.44.168.80]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id JAA24010; Mon, 21 Jan 2002 09:43:21 -0500 (EST)
Received: from MJS-PC.cisco.com (mjs-pc.cisco.com [172.27.181.69]) by goblet.cisco.com (Mirapoint) with ESMTP id AAM58926; Mon, 21 Jan 2002 09:43:21 -0500 (EST)
Message-Id: <4.3.2.7.2.20020121092051.021d8468@goblet.cisco.com>
X-Sender: mjs@goblet.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 21 Jan 2002 09:44:31 -0500
To: Vijay Bhaskar A K <vijayak@india.hp.com>
From: Mark Stapp <mjs@cisco.com>
Subject: Re: [dhcwg] additional option for dhcpv6
Cc: dhcwg@ietf.org
In-Reply-To: <200201201434.UAA22474@dce.india.hp.com>
References: <4.3.2.7.2.20020118165044.019a0ef0@goblet.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

Vijay,

1) FQDN Option. I really think that we should use a single option that can 
convey both a complete FQDN or a partial 'hostname'. It's unnecessary to 
try to specify two options and the relationship between them. Certainly, 
there's no need to include the RCODE fields that were part of the v4 FQDN 
option: like the two name encodings in the v4 version, those fields were 
left in place because there was a large base of deployed clients who 
expected those fields to be present. I'd suggest that we specify the same 
method that's used in the v4 option to distinguish between fully-qualified 
and unqualified names: if the last label in the name field is null-length, 
the name is fully-qualified. If a client believes it knows a complete FQDN, 
it sends that name and terminates it accordingly. If it only knows a 
partial name, it sends the labels it knows.

 > There needs to be
 > specification about hosts who do not initially know their entire fqdn.
 > There needs to be a way to communicate about which party (if any) will be
 > updating DNS. It's probably on my plate to produce that, actually.

>For the  temporary  addresses,  DNS update is done by server.  So, these
>fields are not necessary.


As I said, I think that DNS updates will be performed by different parties 
in different environments, just as they are in IP4 networks. The option 
must contain enough information to permit a network's administrators to 
influence the choice of updater for zones that are under their control.

Like Bernie, I don't know what you mean here when you claim that no 
additional data is necessary. Your claim that temporary addresses' updates 
will be done by servers is a little confusing to me. Why do you assume 
that? You imply that non-temporary updates are clearly understood to be the 
responsibility of one party. I disagree: I think that the years of field 
experience we have demonstrates that there are a variety of valid dns 
update models.

> >
> > 2) The subnet-selection option text should not compel the server to 
> somehow
> > obey the client's suggestion. It should be explict that the server
> > administrator's configuration takes precedence, and that the client's
> > indication that it desires a specific subnet can only be a hint that's
> > considered along with all of the other information available to the server.
>
>This is the only way the client can tell its  prefernce  for the prefix.
>If the server is not supposed to allocate  address for that prefix, then
>it wont.  If the  client is not very  particular  about the  prefix,  it
>should not use this  option.  This  option  will be more  helpful in the
>network with two prefixes and the client wants a particular one.

I think that the specification must be clear about the behavior that the 
paragraph in your reply describes. The server MAY consider the subnet 
specified as it considers the other information available to it about its 
allocation policies and about the client.


> >
> > 4) The 'Service Location Protocol Directory Agent Option' places the
> > 'typed-scope-list-len' field before the 'DA address', rather than before
> > the 'typed scope list'. Couldn't the length of the list immediately 
> precede
> > the list?
>
>I think,  it won't  make any  difference.  Let me  know, if there are any
>serious issues on this.

There are so many examples of the field len/field value convention that I 
think it's much clearer to continue using that convention unless there's a 
very good reason not to. I don't think that there is such a reason in this 
case, and I think that it will make the specification and implementation of 
this option more robust if we retain that convention.

-- Mark


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg