IETF Logo Mail Archive

Re: Brokenness of specs w.r.t. client behavior with M&O bits

Iljitsch van Beijnum <iljitsch@muada.com> Mon, 13 October 2008 16:02 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 219BB28C122; Mon, 13 Oct 2008 09:02:28 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 124443A69FE; Mon, 13 Oct 2008 09:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mxJhjnvVVuoZ; Mon, 13 Oct 2008 09:02:23 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 12CC83A6809; Mon, 13 Oct 2008 09:02:22 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb] ([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9DG2wvj035983 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Oct 2008 18:02:58 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <BA6C47AC-1668-47CE-94D0-49C4F7A6775E@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Thomas Narten <narten@us.ibm.com>
In-Reply-To: <200810131540.m9DFeRGR009155@rotala.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Brokenness of specs w.r.t. client behavior with M&O bits
Date: Mon, 13 Oct 2008 18:03:14 +0200
References: <7182010.12431219366974773.JavaMail.weblogic@epml09> <200809171517.m8HFHaaV009346@cichlid.raleigh.ibm.com> <9A613C72-E818-410B-9769-8C34E8A78AE1@cisco.com> <200810131540.m9DFeRGR009155@rotala.raleigh.ibm.com>
X-Mailer: Apple Mail (2.929.2)
Cc: DHC WG <dhcwg@ietf.org>, IPV6 List Mailing <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

On 13 okt 2008, at 17:40, Thomas Narten wrote:

> OK, I'm going to wade back into this and say that I believe we've
> botched things. Let's take a typical client implementor, who looks at,
> say, RFCs 4861, 4862 and/or RFC 3315 (the DHCPv6 spec).
>
> Question: just when are they supposed to invoke DHCPv6? All the time?
> Only if the M or O bits are set? This simply isn't clearly
> defined. This is broken and teh IETF really needs to make a
> recommendation.

Seems to me that this is simple enough: no bits, no DHCP. "Always" is  
not an acceptable out of the box behavior. (!!!)

Then if there is M you do stateful DHCPv6, if there is O stateless.  
The only problem would be if bot O and M are set.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.46.0 | Report a Bug | By Email | System Status