Re: [dhcwg] Rev of DHCPv6 spec

Ralph Droms <rdroms@cisco.com> Fri, 12 October 2001 10:07 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 GAA21023; Fri, 12 Oct 2001 06:07:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA18251; Fri, 12 Oct 2001 06:05:26 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA18215 for <dhcwg@optimus.ietf.org>; Fri, 12 Oct 2001 06:05:24 -0400 (EDT)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20971 for <dhcwg@ietf.org>; Fri, 12 Oct 2001 06:05:18 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (rtp-vpn1-65.cisco.com [10.82.224.65]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id GAA04931; Fri, 12 Oct 2001 06:04:48 -0400 (EDT)
Message-Id: <4.3.2.7.2.20011012055814.03a64ec8@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 12 Oct 2001 06:06:08 -0400
To: skodati@in.ibm.com
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Rev of DHCPv6 spec
Cc: dhcwg@ietf.org, bsuparna@in.ibm.com, rsharada@in.ibm.com
In-Reply-To: <CA256AE3.00254C4A.00@d73mta01.au.ibm.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

1./2. the unicast option is an administrative policy;

3. I don't see any text in 16.1.1 that requires the
client to check that the server is on the same link

In response to your last question, the use of unicast
isn't dependent on whether the client and server
are on the same link.  A client could use unicast to
deliver DHCP messages to an off-link router.

The draft doesn't specify how a server should react
to a unicast message received from a client to which the
server has not sent a unicast option.  I imagine the
right thing to do is to allow the server to process
such messages.

- Ralph

At 12:18 PM 10/12/2001 +0530, skodati@in.ibm.com wrote:

>I would like to get clarification on when does a server send an unicast
>option,
>1. does the server send unicast option  whenever the client is on the same
>link (20.11 is not clear about it) (or)
>2. Is it an administrative policy that decides if the client can
>unicast/multicast of messages. If it is so, is there any example of the
>scenario where the server would not specify the option despite being on the
>same link.
>3. why is the client required to check if the client and server are on the
>same link if  unicast option is already obtained from the server ( 16.1.1 )
>
>And also,
>  Is it not sufficient to have both client and server to be on the same link
>to unicast client's message ?, if so what is the server response to
>client's unicast if it didn't send unicast option to the client and still
>gets messages unicast'ed to it.
>-suresh
>
>
>Ralph Droms <rdroms@cisco.com> on 10/11/2001 07:31:31 AM
>
>Please respond to Ralph Droms <rdroms@cisco.com>
>
>To:   dhcwg@ietf.org
>cc:    (bcc: Suresh Kodati/India/IBM)
>Subject:  [dhcwg] Rev of DHCPv6 spec
>
>
>I've finished another rev of the DHCPv6 spec (-20d), which is available at
>http://www.dhcp.org/dhcpv6.tty  I plan to submit this draft of the spec to
>the IETF for publication on 10/12.  The list of issues addressed by this
>draft is included below; these issues were discussed at the DHC WG meeting
>in London (8/2001).  The -20d draft does not include any changes related to
>IAs.  The changes related to IAs will appear in the next published rev of
>the draft.
>
>- Ralph


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