IETF Logo Mail Archive

RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt

Pekka Savola <pekkas@netcore.fi> Mon, 16 May 2005 21:10 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DXmqp-0007nm-J5; Mon, 16 May 2005 17:10:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DXmql-0007n8-DA; Mon, 16 May 2005 17:10:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20865; Mon, 16 May 2005 17:10:04 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXn7M-0002GS-B7; Mon, 16 May 2005 17:27:17 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id j4GL8Wf31311; Tue, 17 May 2005 00:08:32 +0300
Date: Tue, 17 May 2005 00:08:32 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: RE: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt
In-Reply-To: <8E296595B6471A4689555D5D725EBB212B347C@xmb-rtp-20a.amer.cisco.com>
Message-ID: <Pine.LNX.4.61.0505170005250.30727@netcore.fi>
References: <8E296595B6471A4689555D5D725EBB212B347C@xmb-rtp-20a.amer.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: dhcwg@ietf.org, "Ralph Droms (rdroms)" <rdroms@cisco.com>, IPv6 WG <ipv6@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

On Mon, 16 May 2005, Bernie Volz (volz) wrote:
> BTW, if you want to look at this from the router administrator's
> perspective:
>
> Configure the router to send the M flag set in routing advertisements
> for a Link IF:
> 1. A stateful DHCP server is deployed for that link (either on it or
> reachable via a relay agent) AND

IMHO, you're making a significant leap of faith in assuming that 
whoever configures the router's M-flag advertisements has sufficient 
clue to grasp the different semantics that arise with:

  - M-flag and/or O-flag
  - stateless and stateful clients
  - stateless and stateful servers
  - stateless and stateful relay agents

Hence, if we want to build a robust system, we need to design it with 
care.



-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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

v2.23.0 | Report a Bug | By Email