Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt

Tim Chown <tjc@ecs.soton.ac.uk> Sat, 07 February 2004 23:16 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17819 for <dhcwg-archive@odin.ietf.org>; Sat, 7 Feb 2004 18:16:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApbgA-0000D7-CH for dhcwg-archive@odin.ietf.org; Sat, 07 Feb 2004 18:16:02 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i17NG2jn000781 for dhcwg-archive@odin.ietf.org; Sat, 7 Feb 2004 18:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Apbg9-0000Bw-K4 for dhcwg-web-archive@optimus.ietf.org; Sat, 07 Feb 2004 18:16:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17743 for <dhcwg-web-archive@ietf.org>; Sat, 7 Feb 2004 18:15:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Apbg6-00077Q-00 for dhcwg-web-archive@ietf.org; Sat, 07 Feb 2004 18:15:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Apbf7-00070s-00 for dhcwg-web-archive@ietf.org; Sat, 07 Feb 2004 18:14:58 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ApbeJ-0006uq-00 for dhcwg-web-archive@ietf.org; Sat, 07 Feb 2004 18:14:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApbeE-0007qX-FT; Sat, 07 Feb 2004 18:14:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Apbe7-0007np-Bo for dhcwg@optimus.ietf.org; Sat, 07 Feb 2004 18:13:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17491 for <dhcwg@ietf.org>; Sat, 7 Feb 2004 18:13:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Apbe4-0006tc-00 for dhcwg@ietf.org; Sat, 07 Feb 2004 18:13:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApbdA-0006nz-00 for dhcwg@ietf.org; Sat, 07 Feb 2004 18:12:56 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1ApbcH-0006ir-00 for dhcwg@ietf.org; Sat, 07 Feb 2004 18:12:01 -0500
Received: from tortoise.webcentre.net ([62.189.30.6]) by mx2.foretec.com with esmtp (Exim 4.24) id 1ApbT9-0000tZ-7v for dhcwg@ietf.org; Sat, 07 Feb 2004 18:02:35 -0500
Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1]) by tortoise.webcentre.net (8.9.3/8.9.3) with ESMTP id WAA07662 for <dhcwg@ietf.org>; Sat, 7 Feb 2004 22:58:37 GMT
Received: from pigeon.ecs.soton.ac.uk (pigeon [152.78.68.1]) by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i17Mr4Or028452 for <dhcwg@ietf.org>; Sat, 7 Feb 2004 22:53:04 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162]) by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id WAA09783 for <dhcwg@ietf.org>; Sat, 7 Feb 2004 22:53:01 GMT
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i17Mr1m30832 for dhcwg@ietf.org; Sat, 7 Feb 2004 22:53:01 GMT
Date: Sat, 07 Feb 2004 22:53:01 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: DHCPWG <dhcwg@ietf.org>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt
Message-ID: <20040207225301.GB30700@login.ecs.soton.ac.uk>
Mail-Followup-To: DHCPWG <dhcwg@ietf.org>
References: <4.3.2.7.2.20040204170501.04687cb0@flask.cisco.com> <4023D31C.5060206@india.hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4023D31C.5060206@india.hp.com>
User-Agent: Mutt/1.4i
X-ECS-MailScanner: Found to be clean
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

The issues draft will be submitted for Monday's deadline so will be
on the table in Seoul (Stig is presenting...)

So #2 might well lead to #1 soon...

Tim

On Fri, Feb 06, 2004 at 11:17:08PM +0530, Vijayabhaskar A K wrote:
> Solution 1 seems more logical to me.. I support solution 1
> 
> Vijay
> 
> Ralph Droms wrote:
> 
> >The IESG has one remaining comment on this draft (see 
> >https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=896&filename=draft-ietf-dhc-dhcpv6-opt-nisconfig): 
> >
> >
> >  what does a DHCPv6 server do when it wants to indicate that there's 
> >a NIS
> >  server available with an IPv4 address and another NIS server 
> >available with
> >  an IPv6 address?
> >
> >  The two reasons why this can be a silly question:
> >
> >  - NIS wouldn't work with such a config, so all the servers' addresses
> >    obviously have to be one address type
> >  - You can always encode a v4 address as a v6 address using the 
> >96-zeroes
> >    convention (or something else), so it's obvious how to do it
> >
> >  But I think the document should address the issue.
> >
> >We have a couple of alternatives to addressing the issue:
> >
> >1. Reserve DHCPv6 for IPv6 NIS servers and DHCPv4 for IPv4 NIS servers
> >2. Wait until the WG completes its work on DHCPv4/DHCPv6 issues
> >3. Use an encoding to carry IPv4 addresses in the DHCPv6 option; for
> >   example, Vijay suggests:
> >
> >   3. Network Information Service (NIS) Servers Option
> >
> >      The Network Information Service (NIS) Servers option provides a
> >      list of one or more IPv6 addresses of NIS servers available to the
> >      client. If any of the NIS servers is available with an IPv4 
> >address,
> >      then its address will be represented in "IPv4-mapped IPv6 
> >address" [RFC3513]
> >      format. Clients MUST treat the list of NIS servers as an ordered
> >      list.  The server MAY list the NIS servers in the order of
> >      preference.
> >
> >For the DHCPv6 DNS servers option, the WG opted for alternative 1, which
> >seems to me to be the right thing to do for the NIS servers option, as 
> >well.
> >
> >- Ralph
> >
> >
> >
> >_______________________________________________
> >dhcwg mailing list
> >dhcwg@ietf.org
> >https://www1.ietf.org/mailman/listinfo/dhcwg
> >
> >
> 
> 
> -- 
> __________________________________________________________
> Vijayabhaskar A K            Phone : +91-80-22053085
> Hewlett Packard              Mobile: +91-9845241382
> Bangalore, India             Email : vijayak@india.hp.com
> 
> Intellectuals solve problems: geniuses prevent them.
> -Albert Einstein, physicist, Nobel laureate (1879-1955)
> __________________________________________________________
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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