DHCPv6 address used when M or O bit is set

Dominik Elsbroek <dominik.elsbroek@gmail.com> Wed, 04 April 2012 13:55 UTC

Return-Path: <dominik.elsbroek@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D911821F8795 for <ipv6@ietfa.amsl.com>; Wed, 4 Apr 2012 06:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id q4sMH+V2qRCs for <ipv6@ietfa.amsl.com>; Wed, 4 Apr 2012 06:55:04 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 59C5E21F8470 for <ipv6@ietf.org>; Wed, 4 Apr 2012 06:55:04 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so159054ggm.31 for <ipv6@ietf.org>; Wed, 04 Apr 2012 06:55:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=4DMbw4E7dbnHBYNsgxyQF2xcUgSrhyHRc/Sk35/x1Po=; b=jDP15O9CGMXu+I4KFWfCbw5xFt/uXv+/Qrxbs+SnWo3IfugOqgv4Ai39oRCBn0UAeI W6Xvp97kdXp6BTIQAI8Z3HGgzE1QKmg77MJcIhVToIyxR/PHIuQS+Fvn99+oH5sV+w+8 gbygWzGd92+HWJsC+ZpNv+IAzSzeQLecB/wNKUlwLrKKqcTJEwt4FZwj6DLgQTqWooUP /CxX1s5qKnKnZdr3VLYcDLu2QiKt4boDZPoVXHdAOJ/GxZa94xQtf9cxnWDIaJipVeGq SkpJ4ptpHiV/MoCaiY4Wk04T+Ynaog5qU4yO9KaSk8SL0KoojW7d6sJhyOT9LcsAbQQt IQnw==
MIME-Version: 1.0
Received: by with SMTP id oy9mr1654424igc.31.1333547703305; Wed, 04 Apr 2012 06:55:03 -0700 (PDT)
Received: by with HTTP; Wed, 4 Apr 2012 06:55:03 -0700 (PDT)
Date: Wed, 4 Apr 2012 15:55:03 +0200
Message-ID: <CAAVMDnVNUaXBwi5cU87+0PkB71kdT+e4BaLUW7Ai39hCWitUrw@mail.gmail.com>
Subject: DHCPv6 address used when M or O bit is set
From: Dominik Elsbroek <dominik.elsbroek@gmail.com>
To: ipv6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Wed, 04 Apr 2012 13:55:04 -0000

Hi all,

the discussion on the mailing list titled "RA "requires" DHCPv6 ?" is
quite confusingto me since RFC 4862 states, the flags M and O are
removed, but not deprecated. They don't even longer exist, but still

But what should a client do now? Is a client asked to request further
information from a DHCPv6 server if it receives a router advertisement
with these bits set? And if, which address should the client use? The
link local FF02:0:0:0:0:0:1:2 (All-dhcp-agents) or the site-local
FF05:0:0:0:0:0:1:3 (All-dhcp-servers)?

Kind regards,