IETF Logo Mail Archive

Re: [dhcwg] Rev of DHCPv6 spec

Ted Lemon <mellon@fugue.com> Tue, 16 October 2001 02:05 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 WAA17863; Mon, 15 Oct 2001 22:05:38 -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 WAA13496; Mon, 15 Oct 2001 22:00:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA13460 for <dhcwg@optimus.ietf.org>; Mon, 15 Oct 2001 22:00:28 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17820 for <dhcwg@ietf.org>; Mon, 15 Oct 2001 22:00:25 -0400 (EDT)
Received: from green.bisbee.fugue.com (user-2ivfjsl.dialup.mindspring.com [165.247.207.149]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id f9G1xIv06883; Mon, 15 Oct 2001 18:59:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id f9G20D100709; Mon, 15 Oct 2001 19:00:13 -0700 (PDT)
Date: Mon, 15 Oct 2001 19:00:13 -0700
Subject: Re: [dhcwg] Rev of DHCPv6 spec
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v472)
Cc: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>, "'skodati@in.ibm.com'" <skodati@in.ibm.com>, dhcwg@ietf.org, bsuparna@in.ibm.com, rsharada@in.ibm.com
To: Ralph Droms <rdroms@cisco.com>
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <Pine.GSO.4.33.0110151102480.21009-100000@funnel.cisco.com>
Message-Id: <893C8420-C1D9-11D5-AB61-00039317663C@fugue.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.472)
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

> It probably wouldn't hurt to add a sentence to the effect that a server
> MAY choose to accept unicast messages from clients to which the server has
> not sent a unicast option.  A server might want to reject those messages
> because they won't include relay agent options...

That sounds like a good plan.


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

v2.23.0 | Report a Bug | By Email